← BackAI Therapy Concept · 2026

Be Your Own Freud

Six thinkers, six different ways of listening

Sole designer and engineer · concept, persona and safety prompt design, build (concept, not a clinical product) · 2026

Be Your Own Freud

Problem

AI therapy keeps converging on the same agreeable chatbot.

Working through the current crop of LLM wellness products, they all arrive at one shape: a single assistant, warm, accommodating, with no position of its own. Agreeableness is treated as a safety property, and it does remove one class of risk, but it also means the product never says anything the user did not already believe. There is nothing to choose between and nothing to push against. This is a concept build, not a client project and not a clinical product. I designed and coded it to test one question: if an AI is given a real point of view instead of neutrality, does the exchange become more useful, and what has to be built around it to keep that safe.

Apple-TV chrome, not chatbot chrome

Apple-TV chrome, not chatbot chrome

Full-bleed portrait of this week's advisor, one line of their thinking, one button. The interface borrows from a media library because choosing a film is a less stigmatised gesture than asking a chatbot for help.

Each advisor has a point of view

Each advisor has a point of view

Sigmund Freud reads everything as conflict between conscious and unconscious. Aurelius reframes through duty and impermanence. Laozi answers with paradox. Same user message, meaningfully different replies, because the prompts are doing real work, not styling.

Voice first, words second

Voice first, words second

Sessions open with 'What is troubling you?' and a single tap-to-speak microphone. Writing is the secondary input. The framing borrows from being heard rather than being assisted. The advisor is listening, not problem-solving.

Process · Decision Points

The hard calls, and what they cost.

Three calls, one of which is the reason the product can exist at all.

Decision · 01

Six opinionated advisors, or one assistant that adapts?

An adaptive single assistant is the obvious build and the easier sell. I chose six fixed advisors with incompatible worldviews instead, because the choice itself is the product. Picking Nietzsche over Laozi is the user deciding what kind of resistance they want today, and that decision does work no amount of tone-matching can do. Each advisor is a separate system prompt describing worldview, register, and the specific way that thinker pushes back, so the same message returns genuinely different answers.

Considered and dropped

One adaptive voice

A single assistant that adjusts its tone to the user. Simpler to build and to moderate, and it collapses back into the agreeable default this project exists to argue with.

Six opinionated advisors, or one assistant that adapts?, Built. Six fixed positions

Built. Six fixed positions

Freud reads for what is repressed, Aurelius for what is outside your control, Laozi answers by inversion. The prompts carry the difference, not the styling.

Six opinionated advisors, or one assistant that adapts?, Built. The choice is the interface

Built. The choice is the interface

The library screen makes selecting a worldview the first and most consequential action.

Trade-off

Fixed personas cannot adapt to who is actually in front of them. Nietzsche's register is the wrong instrument for someone fragile, and the product currently relies on the user choosing well, with only the crisis rule underneath as a floor.

Decision · 02

Content library chrome, or chat chrome?

The interaction underneath is a language model answering a message, which by default looks like every chat product on the phone. I built the shell as an editorial content library, full-bleed portrait, name in display weight, one Begin button, closer to choosing a film than opening a support tool. Asking a chatbot for help carries a stigma that browsing a library does not, and the framing changes what someone thinks they are about to do.

Considered and dropped

Chat-first shell

Message list, input bar, advisor as a name at the top. Familiar, and it puts the product in the same category as every other assistant.

Content library chrome, or chat chrome?, Built, library chrome

Built, library chrome

Editorial covers and a single focused action per screen. The advisor is presented as something you sit with, not something you query.

Content library chrome, or chat chrome?, Built. Voice first

Built. Voice first

Sessions open on 'What is troubling you?' with tap-to-speak as the primary input and writing as the fallback.

Trade-off

Library chrome oversells continuity. It looks like an ongoing relationship with an advisor, while each session is a single exchange with no memory of the last one. That gap between what the interface promises and what the product does is the sharpest unresolved problem in it.

Decision · 03

How do you give an AI a hard point of view without it becoming dangerous?

An advisor instructed never to reassure and to push back is the entire premise, and it is also the risk. I split the system prompt in two. The persona half carries worldview and register and differs per advisor. The shared half carries the rules and is identical for all six, so nothing a persona says can loosen it. That shared half is where the product's safety actually lives, and it was written before any of the personas were.

Considered and dropped

Persona-only prompts

Voice and rules written together per advisor. Six places for the same safety language to drift, and six chances to get it wrong.

Split prompt · built

Persona and shared rules kept apart. The register changes per advisor, the boundaries do not. This one has nothing to show because it lives entirely in the system prompt.

How do you give an AI a hard point of view without it becoming dangerous?, Built, bounded scope

Built, bounded scope

One response per session, 100 to 170 words, no diagnosis, no medication advice, no claim to clinical authority.

Trade-off

All of this is prompt-level. The model is still the thing deciding whether a message is a crisis, and a system prompt is an instruction rather than a guarantee. A product carrying real clinical risk would need a deterministic check that never depends on the model's judgement.

The library

Six thinkers, six different ways of listening

Freud, Psychoanalysis

Freud, Psychoanalysis

Jung, Analytical psychology

Jung, Analytical psychology

Aurelius, Stoicism

Aurelius, Stoicism

Key Insight

The chrome reframes the interaction

Visual register matters more than the engine. The underlying LLM call could be identical across all six advisors and the experience would still differ, because the user opens the app expecting a session, not a query. Editorial scaffolding does work that prompt engineering alone cannot.

The Journal, every insight you saved, kept in the voice of the advisor who delivered it. Filter by advisor to see how each one of them speaks differently inside your own life.

The Journal, every insight you saved, kept in the voice of the advisor who delivered it. Filter by advisor to see how each one of them speaks differently inside your own life.

Safety

What happens when someone is in crisis

The advisors are built to withhold reassurance, so the crisis path had to be the one place that behaviour is cancelled outright rather than softened. When a message suggests self-harm, suicide, abuse, or danger to the person or someone else, the instruction is to set the persona aside entirely: two or three warm plain sentences saying this exercise is not the right place for what they are carrying, and a push toward emergency services or a crisis line, 988 in the US and the local equivalent elsewhere. The signature move every advisor otherwise ends on, one probing question, is explicitly suppressed there. Nietzsche does not get to be Nietzsche at that moment.

Safety

Where the persona is fenced in, and where the handoff goes

Four boundaries hold regardless of advisor, and they live in the shared half of the system prompt rather than in any persona. No diagnosis, no medication advice, no claim to clinical authority, and an explicit statement that this is not therapy. The scope is deliberately small: one response per session, capped at 100 to 170 words, with the input rejected outright below eight characters or above 4,000. Sessions are not stored on a server and the journal stays on the device. Two standing disclaimers sit in the interface, one in the persistent footer and one directly beneath each response. The honest limit is the handoff. There is no human on the other side of this product and no escalation to one. It routes outward to external crisis services, which is the correct behaviour for a concept build with no clinical staffing, and it is the first thing that would have to change before this could be put in front of vulnerable users. A production version would also want the crisis check running deterministically before the model is called, not as a rule the model is asked to follow.

Stack & Tools

AI

Claude (Sonnet)Claude Code

design

Figma

code

Vite + React + TypeScriptReact RouterTailwind CSSMediaPipe (Phase 2)

Reflection

What I’d revisit

The 'Mirror' phase, a planned moment where the user's face is shown alongside a ghosted overlay of the advisor's visage during the session. Is currently a styled placeholder. Real MediaPipe face-tracking would change the emotional weight of the session in ways the static comp can only hint at. Phase 2 work.

More client and product design case studies at hannadevries.com