Here's the build, laid out.
This isn't a portfolio or a case study. A blueprint is what I'd build for you, written out like a spec — before you commit to anything.
Pick the one that matches what you're stuck on.
Every one has two layers. You can do layer one yourself in a sitting. Layer two is where I build it in.
I don't list prices here, and there's no pitch. Just the steps.
start here → then thisFind the one that's yours.
Read the problem, not the industry.
Nothing's published here yet — I'm still writing these up. See the free workshop instead →
Before you ask.
What people want to know before they bring one of these to a call.
Is this a real thing or a mockup?
Every blueprint here can be built with what's on the market today — that's the bar for one going on this page. What you're reading is a spec, not a case study. It describes what would be running in your business, not what happened in somebody else's. If you want proof of work already delivered, that's what the stories page is for. If one of these is your Tuesday, book a call and I'll tell you straight what layer one looks like for you. See work already running →
What does a blueprint cost to build?
You'll hear a number on the call, once I know which layer you want and what you already have. Layer one is small on purpose. It's written so somebody with no automation at all and nothing beyond one AI chat can start it. You can stand it up yourself after a session. Layer two is where I quote a build. I don't put a number on this page because the same blueprint is two different jobs in two different businesses.
How long before one of these is actually running?
Layer one is a sitting's work, not a quarter's — that's the rule every blueprint here is written to. If it can't be started in one session, it isn't layer one and the blueprint is wrong. Layer two takes as long as it takes to wire the thing into where your messages and your customers already are. You'll get a real timeline on the call, not a range on a web page.
What do you need from me to build one?
Less than you'd think, and none of it is technical. I need the way you talk: a few voice notes, a handful of emails you've already sent, the answers you give on the phone. That's what makes the thing sound like you instead of like a machine. After that I need one person who can say yes. Nobody has to learn anything, and you don't buy software before we've talked.
My business isn't one of the ones listed here. Now what?
The industry on a blueprint is a label, not a limit. Most of what's on this page is the same handful of problems wearing different clothes. A quote that goes out three days late is the same problem whether you're roofing or bookkeeping. Read the ones that aren't your industry and find the problem you recognize. That's the one to bring to the call. If none of them fit, say so on the call — that's useful to me. Book a call →
Something else on your mind?
Know you want more than a blueprint?