Door 2 of 3 — Blueprint
The Implementation Plan. The exact recipe — minus our hands on the keyboard.
A written, sequenced blueprint for your top 1–2 workflows: which models, which prompts, which integrations, and what breaks in week one.
Sample blueprint page · 12 pages total
Six concrete deliverables. Page-numbered.
The blueprint is a real document — section headers, page numbers, tables, prompt blocks. Not a Notion dump. Designed for a developer or generalist to read in a single sitting and start building the next morning.
- 01
12-page implementation blueprint
PDF + editable Google Doc. Cover, exec summary, sequenced steps, prompt library, schema diff, week-one risk list, cost projections, rollback plan.
- 02
Sequenced steps: trigger → output
Each step names the tool, the API call (or no-code action), the input, the expected output, and the failure case. Diagram included.
- 03
Copy-paste prompt library
Every model prompt the workflow needs, with 4-shot examples, role framing, and output-format constraints. Versioned so you can roll back.
- 04
Stack diagram + integration map
Which models, which integrations, which auth scopes, which rate limits. One page your developer or builder can reference without re-asking.
- 05
Cost projection + break-even math
Cost-per-run, expected monthly volume, break-even leads or tickets. So month one isn't a billing surprise.
- 06
Two 30-min follow-ups (in 30 days)
Your team implements; you ping us when stuck. Real answers, no scope creep, no upsell. After 30 days the engagement is closed.
10 business days. Five checkpoints.
60-min Zoom — workflow walked end-to-end with the person who runs it today.
We pick models, draft prompts, sketch the schema diff, and red-team the failure cases.
Sequenced steps, integration map, cost math, week-one risks — all written down.
We pressure-test our own plan against the original goal before sending it.
60-min walkthrough. You leave with the PDF and editable doc.
Operators who already know the workflow they want to automate and would rather pay once for a written plan than pay an engineer to figure it out by trial and error.
- 12-page implementation blueprint (PDF + editable doc)
- Sequenced steps: trigger → API calls → prompts → review → output
- Copy-paste-ready prompts with 4-shot examples per step
- Stack diagram naming every tool, model, and integration
- Cost-per-run projections with break-even volume
- Week-one risk list — auth, rate limits, schema diffs
- Two 30-minute follow-up calls during the next 30 days
What this isn’t
The Plan stops at the doc. On purpose.
- We do not write production code. No deploys, no zaps, no API integrations on our end.
- We do not come back to re-plan if your scope shifts after delivery — that's a new engagement.
- We do not provide ongoing implementation support beyond the two 30-min follow-ups.
- We do not warrant the implementation if a third party builds it. The doc is the deliverable.
- We do not extend the 30-day support window. If you want hands-on, upgrade to Build.
Five questions every buyer asks before commissioning the Plan.
Can we plan just one workflow instead of two?
Yes — most Plans cover one workflow at $120–$180. Two workflows lands closer to $250–$300 because we have to think through how they share data, queues, and review steps. We'll quote the exact dollar number after a 5-min email.
Do we have to buy the audit first?
No. If you already know the workflow you want to plan, skip straight to this tier. The audit is for figuring out which workflow is worth planning. If you bought the audit first, the audit fee is credited toward this Plan.
Can our developer actually implement from your plan?
Yes. The blueprint is written to be implemented by a generalist developer, an ops person comfortable with Zapier or n8n, or a contractor you bring in. We name every API call, every prompt, every auth scope. If your team can copy-paste, they can ship from this doc.
What if our scope changes mid-plan?
If the workflow you described turns out to be three workflows, we tell you that on day 2 — not day 10 — and re-quote. We don't silently expand scope. The Plan is a written deliverable; if it grows, the price has to grow with it.
What happens after the 30-day support window?
Engagement is closed. You own the doc, you own the prompts, you own the implementation. If you want us to actually build it, that's the Build tier. If you want occasional check-ins, the optional monthly tune-up retainer is available — never required.
A blueprint instead of trial-and-error.
$120–$300, paid once. 10 business days to delivery. No retainer, no platform fee, no follow-up drip.