Services · 02 · BLUEPRINT
Stop guessing. Start with the math.
The Blueprint is what comes between 'this could work' and 'we're building this.' It's a workflow audit, an ROI model with three scenarios, and an architecture document that makes the build obvious before anyone writes a line of code.
Spec before build
Two to six weeks to a decision-grade plan.
The Blueprint sits between Workshop alignment and Build commitment. By the end, you know exactly what we'd build, how it integrates, what it costs to run, and what to expect in the first quarter of operation.
You can take the Blueprint and run it yourself, hand it to your internal team, or move into a Build with us. The document is yours either way.
What you walk away with
What's inside the Blueprint.
Every deliverable is concrete, named, and either yours by the end of the engagement or running in your account.
- 01
Workflow audit
We map the real workflow against the documented one. The gaps are where the project usually lives.
- 02
ROI model — three scenarios
Conservative / expected / optimistic. With the assumptions called out so a CFO can argue with them.
- 03
Architecture document
What runs where, what integrates with what, where the data sits, who has access.
- 04
Build spec
Acceptance criteria written before any code. The build doesn't ship until each criterion is signed off.
- 05
Risk register
Where the build can fail, what we'd do about it, what's reversible if it does.
- 06
Sequenced roadmap
Module one, two, three. What ships when. What each module unlocks for the next.
How it ships
Same shape, every engagement.
- Week 1
Walk the workflow
We shadow the operators. We read the documents. We catalogue the systems.
- Week 2
Model the math
Three-scenario ROI with the assumptions written down. CFO-defensible.
- Week 3
Design the system
Architecture, integrations, data flow, access. Diagrams a builder can implement.
- Week 4+
Spec and review
Acceptance criteria, risk register, roadmap. Walkthrough with your team before signoff.
Is this the right fit?
Honest about who this is for.
We say no often enough that this list isn't decoration. Most "not right for" cases are early-funnel, not unsolvable — start with the stage above.
Right for you if
- Workshop is done or you already know the workflow you want to attack
- You have to justify the build to a board, a partner, or yourself
- The build is non-trivial enough that scoping it wrong costs more than scoping it carefully
Not right for you if
- You're still in 'is AI even the right tool' territory (start with Workshop)
- You want a vendor-agnostic recommendation (we're not vendor-agnostic — we recommend what we'd build)
- The workflow is simple enough that a competent engineer could spec it in a week
Where this fits
Blueprint is where most engagements crystallise. Roughly seven in ten Blueprints move directly into a Build with us; the rest run the spec internally or hand it to an existing team.
Get started
The first call is free. The first conversation matters.
You'll talk to Sam directly. We'll map the highest-leverage workflow in your business — no preamble, no slide deck.
Path A
Book a 30-minute discovery call
Pick a time that works. We'll use the 30 minutes to map the highest-leverage workflow in your business.
Path B
Send a message
Prefer async? Describe what you're working on and we'll respond within one business day.