Learn
Everything you need to bring AI to your clients.
Watch how it's done, print a guide for your next meeting, and look up any term you hear along the way. New material lands here first.
Training videos
A library of recorded walkthroughs.
Watch exactly how we do it, start to finish, and come back whenever you need a refresher.
- How we build a website with AmbroseComing soon
- How we move an existing website onto AmbroseComing soon
- How to price what you sellComing soon
Take it into the room
Guides you can print.
Glossary
The words you'll hear, in plain English.
No jargon required. If a client asks what something means, the answer is here.
- Partner
- An agency, professional services firm, or business coach who sells Ambrose builds to the clients they already have. You keep the relationship and a share of every build.
- Build
- A custom system Ambrose creates from a client conversation. It runs live at a working link, not as a file of code.
- Transcript
- The written record of your client meeting. Ambrose builds from it, which is why the conversation matters so much.
- Module
- One job the system does, like scheduling, a client portal, or invoicing. Build sizes are counted in modules.
- Feature
- A smaller addition to something already built, like a new report or an extra step in a process.
- Small, Standard, and Large
- The three build sizes. Small is up to 3 modules, Standard is 4 to 7, and Large is 8 to 12.
- Builder seat
- A login for one person at your firm who builds with Ambrose. Your first one is included.
- Monthly access
- What your client pays each month to keep their system live and ask for changes. Your share of it is recurring revenue.
- Live link
- The working web address a build runs at as soon as it's built, so your client can open it and try it.
- Custom domain
- An address on your client's own domain, like portal.theirfirm.com. A build moves there when they're ready, and their website stays exactly as it is.
- DNS record
- A setting at the company where a domain is registered that points an address somewhere. Moving a build to a custom domain takes one, and Ambrose walks you through it.
- Engineer sign-off
- A senior engineer reviews every build before it goes live.
- Automatic rollback
- If a change ever breaks something, the live system goes back to its last working version on its own.
- GitHub, Supabase, and Vercel
- Tools that store the code, hold the data, and host the system. Ambrose sets all of them up. You never have to touch them.
Tips
What the best builds have in common.
Small habits that make a big difference in what Ambrose hands back.
Get curious. Ask for the best case.
Don't stop at the problem in front of you. Ask what the ideal version would look like, then aim for that.
Go deep before you go wide.
"Walk me through the last time that happened" gets you the details Ambrose builds from.
Use their words, not yours.
If they call it a job sheet, so should the system. It's theirs.
Ask for several changes at once.
One message can carry three requests. Ambrose works through each one.
Show something early.
A working link a few days after the meeting does more than any proposal.
Add AI on top.
Once it works, make it smart: have it explain itself, flag what matters, and suggest what to do next.