How It Works

I learn your work.
I build it. I hand you the keys.

Three phases. Most projects launch in 2–6 weeks. What happens after launch is a conversation, not a contract.

The Process

Three phases. One partnership.

01

I learn your work.

You tell me what you're building — or what you've already built — and where it needs to go. I learn the methodology, the people you serve, the way you actually teach.

  • A 30–60 minute conversation about your work, your people, and your current setup
  • I research your space — what exists, what's missing, what the architecture needs to look like
  • If it's a fit, I send a proposal within a few days: scope, timeline, deal shape
  • Not every project is the right fit. But stage isn't the filter — the work is
02

I build.

Custom platform, real code, your brand. You see it come together week by week. Most projects launch in 2–6 weeks depending on scope.

  • Weekly progress updates — you see the platform taking shape in real time
  • Your content, your logic, your brand. I handle the engineering
  • Iterative — I adjust as we go based on what we learn
  • You're involved in key decisions but never managing a developer
03

I hand you the keys.

You own the code, the data, the domain. Whether I stay on after launch is a conversation, not a contract.

  • You own everything from day one — code, data, domain, content
  • Some clients keep me on for ongoing maintenance and new feature work
  • Some take the keys and run it themselves
  • Either is fine. The work shapes the relationship, not the other way around

Week by week

What happens in six weeks.

A typical engagement, week by week. Yours might be shorter or longer. The shape stays the same — discovery, architecture, build, work-specific layer, AI substrate, launch.

01

What happens

Discovery + research + proposal

Deliverable

Scoped proposal, deal shape, timeline you can sign or push back on

Who owns

me

02

What happens

Architecture + content modeling + brand tokens

Deliverable

Data schema, page map, design tokens, the bones of the system

Who owns

me · you review

03

What happens

Core build — auth, bookings, payments, the unglamorous spine

Deliverable

Working booking flow, Stripe integration, login, your data model live

Who owns

me

04

What happens

The work-specific layer — what makes your offering yours

Deliverable

Cohort logic, intake-per-offering, edition data, retreat capacity — whatever your shape needs

Who owns

me · you review

05

What happens

AI substrate + automations

Deliverable

Trained model in your voice, automated sequences, integrations to email + calendar

Who owns

me

06

What happens

Launch + handoff

Deliverable

Live platform on your domain, repo access, deploy keys, documentation, runbook

Who owns

both

You see weekly progress throughout — not a six-month silence followed by a launch reveal. Most weeks include a 30-minute review call where I show you what shipped and what's next.

The bus factor

What if I stop building?

Honest answer: the platform keeps running.

Your code lives in your GitHub from day one. Your domain is in your name. Your data is in your database, on a server you own. The AI model is yours, the training data is yours, the customer list is yours. If I disappear tomorrow, any senior full-stack engineer can pick up the codebase — it's standard React + TypeScript + Node, documented as I build, no proprietary lock-in.

What you're paying for is not access to me. It's the architecture I build. The rev share is 18 months because that's how long it takes for the platform to outearn the build. After that, we keep working together because the work calls for it — not because you're locked in.

You don't need an exit clause. You already have the keys.

FAQ

Common questions.

Ready to talk?

No pitch. No pressure. Tell me about your work and let's figure out if this is the right fit.

Start a Conversation