Step 3 of 4 · $2,500 to $7,500 per system

Build: one AI system, one fixed price, live in 2 to 4 weeks.

The Blueprint sets the price. The build delivers it. You know the number before I start.

What's included

  • The system, built to the plan in your Blueprint. One system means one job, end to end, such as lead follow-up.
  • Connections to the tools named in the plan.
  • A person in the loop wherever the plan says a person decides.
  • Testing on real examples from your business before go-live.
  • Go-live, and fixes after launch for 30 days, even if you don't take Run.
  • Plain-English notes: what it does, how to pause it, and who to call.

The timeline: 2 to 4 weeks

The clock starts at kickoff, once the deposit is paid and I have access to the tools.

  1. Kickoff. You approve the plan, the deposit is paid, and I get access to the tools in the plan.
  2. Build. I build the system and connect it. You see working pieces as they come together.
  3. Test. We run it on real examples together. You see what it does before your customers do.
  4. Go live. It starts doing the work.
  5. Handover. The notes, the logins and a walkthrough. Then you run it, or I run it for you on Run.

Builds stay on schedule when the logins are ready at kickoff.

How pricing works

  • One fixed price per system, from $2,500 to $7,500, set in your Blueprint.
  • What moves the price: how many tools it connects to, how many kinds of work it handles, and how much of it needs a person's review.
  • Half is invoiced up front, at kickoff, and the second half at go-live.
  • If you go ahead within 60 days of your Blueprint, the $500 comes off the price.
  • New requests during the build get a written quote first. The price changes only if you approve one.
  • Not included: the monthly fees for the software and AI services the system runs on. You pay those directly, on your own accounts, and the Blueprint estimates them.

What I need from you

  • One person who can say yes: to the plan, the test results and go-live.
  • Access to the tools in the plan, at kickoff.
  • A batch of real examples: the emails, forms or documents the system will handle.
  • A little time each week to test and answer questions.
  • Someone who will use it. A system nobody uses is a cost, not a tool.

Who owns what

  • You own the system. It runs on accounts in your business's name, with logins you control.
  • You own the data: what goes in, what comes out, and the record of what it did. I don't sell it, and I don't use it to train AI models.
  • You own the setup. The configuration, the code and the notes built for you are yours.
  • The plan names every outside service the system uses, so you know where your data goes.
  • Nothing gets switched off if we part ways. You keep the system, the logins and the notes.

I learned this on my first client. If someone else can turn your business off, it isn't your business. It's theirs, on loan.

Every build starts with a Blueprint.

The Blueprint sets the scope and the fixed price. It costs $500, credited toward your build within 60 days.