How it works
What a build looks like, start to finish.
Here is one example, from the first meeting to a client paying you for access every month. The details change from client to client. The steps don't.
-
1Monday morning
The meeting
You meet with Dana, who runs a 12-person bookkeeping firm. You get curious about her week. The answer: every month, her team chases clients by email for missing documents.
Meeting transcript
YouIf this worked perfectly, what would it look like?
DanaClients would upload everything in one place, and we'd see who's missing what without asking.
-
2Monday, after the meeting
Hand Ambrose the transcript
You drop the transcript into Ambrose and say what you want, the way you'd brief a colleague. That's the whole brief. No specs, no technical words.
You, to Ambrose
Here's my meeting with Dana. Build what she described.
dana-meeting-transcript.txt
-
3Overnight
Ambrose builds it
A portal where Dana's clients upload documents, a checklist for each client, and a reminder that goes out when something is missing. Hosted, secure, and signed off by a senior engineer before it goes live.
Built overnight
- Client portal
- Document uploads
- Checklist per client
- Missing-document reminders
- Security checks
- Engineer sign-off
-
4Tuesday
Steer it by talking
You look it over like you'd review a designer's work. Anything you'd change, you just say, and the new version is ready to look at. Got several changes? Ask for them all in one message. Ambrose works through each one.
Your conversation
Make the reminders friendlier, and only send them on Mondays. Also, can the portal use Dana's brand colors?
Done, all three:
- Friendlier reminders
- Sent on Mondays only
- Portal in Dana's brand colors
The new version is live. Take a look.
-
5Wednesday
Show Dana, sell her access
Dana opens her working portal from a live link. She signs up for access, and when she's ready, Ambrose walks you through moving it to an address on her own domain. Her website stays exactly as it is. From then on, any change she wants is a sentence away. You're paid every month she uses it.
Dana's portal
danas-portal.vercel.appLiveWhen she's ready
portal.danasbooks.comMonthly access: recurring revenue for you.
Dana and her firm are an example. You never touch the technical side. You may have heard words like GitHub, Supabase, or Vercel. Ambrose sets all of that up for you. Your job is the conversation, and judging whether what comes back is on the right path.
Isn't this just Claude?
Building is the easy part. Everything around it is what's done for you.
Ambrose runs on the same kind of AI. The difference is what surrounds it: the setup, safeguards, and habits it takes months to put together on your own.
Say you want to build a landing page for a client.
Same motion, different result. You say what you want in both. Only one hands you something you can give a client today.