Proposal · Private & Confidential

The Art of Unwinding
Phased MVP Proposal, Timeline & Budgetary Roadmap

A buildable, emotionally intelligent product roadmap for a guided transformation platform. Protecting the soul of the work while making it real.

Prepared For
Katerina Hellebore & Co-Creator
Prepared By
Daniel Nicholls
Version
v1.0 · 2026
Mobile mockup of The Art of Unwinding home screen, showing a daily affirmation, emotional weather check-in, and suggested daily path.
Directional sketch of the Daily Path experience. Not a final visual.
i. Executive Summary

The opportunity is real. The path is clear, if we phase it properly.

The Art of Unwinding is not a wellness app. It is a guided transformation platform, a daily return-to-self experience built on structured reflection, emotional responsiveness, and an AI guide that feels like a consistent presence rather than a product feature. That ambition is exactly what makes it commercially interesting, and exactly why scope discipline matters.

The right first move is to protect the emotional core of the product, build a lean web-first MVP, and use the first six to twelve months to validate the thing that actually matters: whether users feel genuinely supported, return day after day, and describe this as a relationship, not an app. Everything else (the rituals, the mythology, the symbolic progression) can be layered in once that core is proven.

01

Protect the emotional core

Guided Daily Path, tone-consistent AI, and a light Chronicle layer are non-negotiable in v1.

02

Ship web-first

Responsive web app reduces cost and risk, and gets us to proof of concept fastest.

03

Phase the ambition

Ritual systems, mythology engine, and symbolic depth are deferred, not discarded.

04

Validate, then scale

First twelve months prove retention and emotional resonance, not vanity growth.

ii. What This Product Actually Is

A guided internal system, not a content library.

Most apps in this space sell the user a library and call it a journey. The Art of Unwinding is the opposite. It is a structured, emotionally responsive system designed to help people build awareness of their internal patterns and slowly shift their relationship to themselves. The product isn’t the content. The product is the experience of being guided.

The Daily Path sits at the centre. An emotional check-in actively influences what the user sees next. Reflection leads to insight. Insight leads to a small, embodied practice. Over time, a light Chronicle layer surfaces patterns that the user couldn’t see on their own, which is where the sense of relationship begins.

Everything else (lessons, guides, paths) serves that core loop. This is a product about return behaviour and felt change, not passive consumption.

Journey · Structure

A Daily Path you return to

The spine of the product. A guided arc, not a menu of options. Where the user is in their path shapes everything they experience that day.

Guide · Tone

A consistent presence, not a chatbot

The AI guide adapts tone to the user’s emotional state without becoming clinical or preachy. It leads intentional flows (reflection, insight, practice) rather than waiting to be prompted.

Pacing · Delivery

A Chronicle that reflects growth

More than journal storage. A light memory layer that surfaces emotional patterns and quiet progress over time. This is the feature that turns usage into relationship.

“This is a product designed to support real internal change. That has to be felt in the first session, or the premise doesn’t hold.”
iii. How The MVP Experience Works

The session loop, in six moves.

Everything described in this proposal comes back to a single repeatable loop. This is what the user actually feels when they open the app, and what the system is quietly doing underneath.

  1. 01

    The user opens the app

    The Daily Path is already there, ready. No dashboard, no menu to navigate. The product greets them by name and holds the space.

  2. 02

    Emotional check-in captures state, need, and available time

    A short, low-friction input. Not a questionnaire. The user signals how they arrive (heavy, neutral, open, tender), what they’re looking for, and how much time they have today.

  3. 03

    The system selects tone and guide posture

    The AI guide adjusts its register based on the check-in. Gentler when the user is tender, steadier when they’re seeking clarity. The voice stays recognisable; only the posture shifts.

  4. 04

    The Daily Path presents one guided sequence

    A single, coherent arc for today. Teaching, reflection, practice. No overwhelm, no content buffet. The user is led rather than left to choose.

  5. 05

    Reflection creates insight capture

    Structured prompts that move from reflection to insight to a small embodied practice. What the user writes or says is captured into the Chronicle as a light, usable memory.

  6. 06

    The Chronicle updates light pattern awareness over time

    Across sessions, the Chronicle surfaces gentle patterns: what the user tends to feel, what they return to, what’s shifting. This is the layer that turns usage into relationship.

This is the loop we’re protecting in the MVP. Every scope decision, every deferred feature, every budget line ladders back to keeping this sequence clean, felt, and honest.

iv. The Strategic Recommendation

Build the MVP as a responsive web app first. Then let the data tell us when to go native.

“Ship a web-first MVP, optimised for both browser and mobile. Prove the emotional core works and people come back. Native comes later, when it’s earned.”

A web-first launch is the most commercially sensible route for a self-funded, early-stage product of this ambition. It protects runway, shortens the path to real user feedback, and keeps iteration cheap while we learn what actually creates retention. Native apps are a multiplier, but multiplying something unvalidated is how good products die early.

Faster to proofWeeks, not quarters, to first real user feedback.
Lower cost floorLean build, lean ops, no app store overhead.
Rapid iterationShip fixes the same day. No review cycles.
Retention firstValidate the loop before scaling reach.
Native-ready laterThe architecture ports cleanly when justified.
v. MVP Definition

Protect the soul. Defer the ornamentation.

The MVP is not the full mythology-powered ecosystem. It is the smallest possible version of this product that still delivers the felt experience you want users to have. Everything on the “In” side protects that. Everything on the “Not In” side is a later phase. Intentional, not forgotten.

In MVP · Non-negotiable

The emotional core, fully intact

  • Guided Daily Path as the primary experience
  • Emotional check-in that actively changes what is shown
  • Structured reflection → insight → practice flow
  • Tone-consistent AI guide with emotional responsiveness
  • Light Chronicle / insight memory layer
  • Starter content arc. A contained first pathway, not a full library
  • Read-aloud support for reflective content
  • Talk-to-text reflection capture (optional, subject to scope & budget)
  • Content management approach for ongoing lessons
  • Subscription & paywall readiness
  • Admin essentials & product analytics
Not In MVP · Phased later

Intentionally deferred

  • Ritual and ceremony systems
  • Deeper gamification and reward structures
  • Symbolic progression depth & archetypal mapping
  • Advanced mythology generation engine
  • Broad content universe & expansive libraries
  • Open-ended chatbot / conversational mode
  • Complex multi-guide orchestration
  • Deep spiral-map navigation complexity
  • Richer narrative synthesis outputs
  • Advanced personalisation layers beyond tone & pace
AI Behaviour · Version One

A guide, not an assistant. A presence, not a product feature.

What the guide should do

  • Lead structured, intentional reflection flows
  • Adapt tone based on emotional check-in input
  • Feel like a consistent, recognisable presence
  • Read content aloud with calm, spacious delivery
  • Stay reflective, steady, and non-preachy
  • Hold the architecture of each session gently but clearly

What the guide must not do in v1

  • Over-direct, prescribe, or hand out advice
  • Bypass, rush, or invalidate emotion
  • Overwhelm users with too much content at once
  • Drift into clinical, therapy-adjacent language
  • Sound like a motivational hype machine
  • Behave like a general-purpose assistant or chatbot
vi. Phased Roadmap

From concept to launch in three intentional phases.

Each phase ends with a clear decision point. You never have to commit to the next phase before the current one has answered its questions.

01Phase One

Architecture, Product Definition & Prototype

Before a single line of production code, we lock the MVP scope, shape the AI behaviour boundaries, and design a clickable experience that the whole team can feel and react to. This is the phase that de-risks everything after it.

Timeline · 2 to 5 weeksInvestment · $7k – $15kLow risk · High leverage

Exactly what you receive

  • Locked MVP definition & scope boundaries
  • End-to-end user journey map
  • Key screen map & information architecture
  • Technical stack recommendation
  • AI behaviour scope & tone framework
  • Content structure & product logic
  • Clickable prototype direction
  • Scoped build roadmap & estimate
  • Launch assumptions document
02Phase Two

Lean MVP Build

The first real version of the product, with the emotional core intact. Built with scope discipline, shipped in working increments, and tested against the felt experience at every milestone, not just the feature list.

Timeline · 14 to 20 weeksInvestment · $65k – $110kKickoff to MVP · ~4 to 6 months
  • Onboarding & emotional check-in
  • Daily Path home experience
  • Structured reflection flow
  • Lesson → insight → practice delivery
  • AI guide with tone adaptation
  • Light Chronicle & insight memory
  • Read-aloud baseline; talk-to-text optional, scope-dependent
  • Content management approach
  • Subscription / paywall layer
  • Admin essentials & analytics
  • Internal QA & beta preparation
03Phase Three

Beta, Refinement & Go-Live

A controlled beta with real users. We watch where they drop off, where they feel held, where the onboarding falters, and where the paywall sits wrong. Then we refine, and launch with intention rather than noise.

Timeline · 3 to 6 weeksOutcome · Market-ready launch
  • Closed beta cohort & structured feedback loop
  • UX refinement based on real usage
  • Bug triage & performance tuning
  • Onboarding & paywall optimisation
  • Analytics review & retention baseline
  • Launch readiness & go-live support
While the architecture phase is relatively contained, the full journey from concept to a polished, market-ready product is realistically a six-figure-plus build over time, depending on the final MVP scope and how much sophistication is brought into version one.
vii. Investment Overview

Planning ranges, not marketing numbers.

These are honest budgetary ranges, not fixed quotes for the full future platform. Final numbers depend on feature scope, content readiness, voice/audio depth, and the level of polish we agree on for version one.

Phase One
$7k to $15k

Architecture & Prototype

Scope definition, journey & screen maps, AI behaviour framework, clickable prototype direction, and a scoped build roadmap.

Phase Two · Lean
$65k to $110k

Lean MVP Build

Core emotional loop, AI guide, Daily Path, Chronicle layer, subscription readiness, and analytics, all shipped as a responsive web app.

Phase Two · Richer v1
$130k to $220k

Extended Version One

For a more sophisticated launch: deeper content scope, richer voice, more nuanced personalisation, and tighter production polish from day one.

This is a budgetary proposal, not a fixed-price quote for the entire future platform. Every estimate here is shaped by the principle that we scope tightly, build honestly, and don’t pad numbers to look safe. If something comes in under range, you’ll know. If something needs more, we’ll have the conversation before it becomes a problem.
viii. Ongoing Operating Costs

What it costs to keep the product alive and breathing.

These are operational cost ranges for hosting, AI usage, storage, analytics, voice features, and support overhead. They do not include major new feature development.

StageMonthly RangeWhat drives it
Early-stage operations$500 – $1,500 / moLean traffic, modest AI usage, core hosting & analytics.
Growing usage & AI$1,500 – $4,000 / moHigher AI interaction volume, voice features, storage, support.

Costs scale primarily with AI interaction volume and voice generation. Both are managed through clear usage budgets and sensible defaults so there are no surprises.

ix. Go-Live Approach

Build intentionally. Launch with trust already inside the product.

The go-live plan is deliberately paced. We validate internally, then with a small cohort, then refine, before any broader push. Nothing here is rushed for the sake of a launch date.

1

Architecture & Prototype

2

MVP Build

3

Internal Review

4

Beta Cohort

5

Refinement

6

Soft Launch

7

Growth Testing

x. Who This Is For

A self-aware audience that is already looking for something deeper.

The initial audience is US-first but globally accessible. These are people already familiar with personal development, somatic work, or coaching, and quietly frustrated by the shallow end of the wellness market. They will pay for depth, quality, and emotional resonance when they find it.

Self-aware & growth-oriented
Already somewhat reflective
Fluent in personal development
Seeking depth, not noise
Willing to pay for resonance
Commercial Goal · First 6–12 months

Proof of concept and retention validation.

The primary job of the first year is to prove that users feel genuinely supported and changed by the experience, return to the Daily Path, and describe the product as a relationship rather than a tool. That is the data that earns the right to scale.

Secondary Goals
  • Early recurring revenue from a self-selecting audience
  • Audience growth through resonance, not scale tactics
  • Testimonials and qualitative signal to guide Phase Two investment
  • A foundation for later native apps and deeper content systems

This stage is not primarily about investor theatre. It is about proving that the product works deeply, which is the only thing that makes later scale defensible.

xi. Success Criteria

What proof of concept actually looks like.

Proof of concept is a phrase that usually hides a lack of measurement. These are the specific signals we’ll watch over the first six to twelve months, so we know whether the product is working at the level it needs to.

Behavioural

Daily Path return rate

How often users come back to the Daily Path within a week. The most honest signal that the experience is being felt, not just opened.

Retention

Week-1 & Week-4 retention

Classic retention curves. Week one tells us whether onboarding lands. Week four tells us whether the product has genuinely become part of the user’s life.

Engagement

Reflection completion rate

How often users complete the reflection flow, not just start it. A direct read on whether the AI guide is holding them well enough to finish.

Depth

Chronicle engagement

Do users return to review their own Chronicle? This is the tell for whether we’ve created relationship or just storage.

Qualitative

“I feel supported” signal

Structured qualitative feedback from beta users. The language they use matters as much as the numbers. If they describe a relationship, we’re on.

Commercial

Trial-to-paid conversion

If we monetise in the first twelve months, this is the signal for pricing and positioning. If we don’t, we still track intent signals (favourites, save-for-later, return visits).

We’ll set specific targets for each of these during Phase One, once we’ve scoped the MVP and can anchor numbers to real cohort sizes. Targets set before scope is locked are decoration, not discipline.

xii. Lean Marketing & Growth Roadmap

Validate resonance before spending to scale it.

A measured, staged go-to-market approach. Year one is not about vanity growth; it is about learning what creates trust, usage, and return behaviour. Once those signals are clear, paid acquisition becomes a multiplier rather than a gamble.

Year One

Validation & First Cohort

Build the audience that will tell us what the product really is.

  • Positioning & messaging architecture
  • Landing page & waitlist
  • Founder-led content & credibility building
  • Beta recruitment & early testimonials
  • ASO / discoverability basics where relevant
  • Creator seeding with aligned voices
  • Light paid testing once messaging is proven
Lean range$50k – $80kRecommended$80k – $140k
Year Two

Scale What Works

Put real money behind the channels that have already proven themselves.

  • Scale best-performing acquisition channels
  • Deepen creator partnerships
  • Referral loops built into the product
  • Lifecycle email & retention systems
  • Stronger paid acquisition once unit economics hold
Annual range$150k – $300k
Year Three

Brand & Strategic Expansion

Move from product marketing to cultural presence.

  • Strategic partnerships & distribution
  • Broader brand presence & PR
  • Deeper content engine & editorial
  • Community flywheel & membership depth
  • Wider authority positioning for the founder
Annual range$300k+
xiii. Assumptions & Exclusions

Clear boundaries so we don’t discover them later.

This proposal is scoped with intent. The items below are deliberately not assumed in the numbers above. They’re noted so there are no surprises, and so we can make conscious decisions about when to bring them in.

i

Final scope will be locked during the architecture phase before build begins.

ii

Budget ranges assume a lean first release, not the full long-term ecosystem.

iii

Ritual systems, full mythology generation, deeper symbolic progression, and broader content ecosystems are not assumed in MVP unless explicitly scoped in.

iv

Heavy native mobile functionality is not assumed for the initial version.

v

Major post-launch feature expansion is not included in the early operational cost estimates.

vi

Timeline depends on timely feedback, content access, and a clear decision-making flow from the founding team.

vii

Kat is expected to remain the final approver for content and tone throughout the build.

viii

Voice and audio scope (including talk-to-text and richer narration) are optional and agreed in Phase One. Deeper production is a separate conversation.

Next Steps

A clear first step, not a leap.

Phase One is a short, focused engagement that locks the MVP, shapes the AI behaviour, and gives you a clickable prototype you can feel. It’s the phase that quietly decides whether the rest goes well, and it’s the only decision being asked for today.

01

Approve the Architecture Phase and align on its objectives.

02

Align on MVP scope. What is in, what waits.

03

Move into product definition & prototype together.

04

Transition into the build with a grounded, realistic roadmap.