Build Blueprint
A short, fixed-price engagement that ends in a build plan or a clear no.
Terms
CAD 3,500
- Length
- 7 business days
- Credit
- CAD 1,750 of the fee is credited toward a build over CAD 25,000 that starts within 30 days.
Who it is for
You know something in the business is slow, manual or broken. You do not yet know what to build, or whether to build anything.
The Blueprint is the step before a build. It turns a vague problem into a written plan you can act on, with a fixed price and a fixed length.
It is not for you if you already have a scoped specification and only need someone to build it.
What we map
People
Who does the work, who decides, and who is affected.
Workflow
The steps from request to result, as they really run.
Software
The tools already in use and how they connect.
Repeated tasks
The work someone does again and again.
Data
Where information lives, who can see it and how reliable it is.
Handoffs
Where work passes between people or systems and stalls.
Customer interactions
Where customers wait, ask or drop out.
Manual processes
Copying, re-keying, chasing and checking by hand.
Security and privacy
What must stay private, and which rules apply.
Cost
What the current way costs in time and money.
Bottlenecks
The places where work queues up.
Workflow map
One clear picture of how the work runs today, with the gaps marked.
Ranked opportunities
Where automation, software or AI would pay back most, in order, and what would not.
Recommended architecture
How the pieces fit together, and which of them should run privately.
Constraints
The security, privacy, data, integration and budget limits that shape what is possible.
Scope
What a first build includes and what it leaves out.
Cost range
A range for the build, with what moves it up or down.
Build or no-build decision
A plain recommendation. If the answer is do not build, it says so and gives the reasons.
How it runs
Kickoff to readout takes 7 business days.
Kickoff
You tell us the problem and introduce the people who do the work. We agree what is in scope and what is not.
Mapping
We ask how the work really runs and collect the tools and data involved.
Analysis
We rank the opportunities, sketch the architecture and estimate the cost.
Readout
We walk you through the document and give the build or no-build recommendation.
Summary and recommendation
Build, build less, or do not build, in one page.
How the business runs today
The workflow map.
Where time and money leak
Bottlenecks, repeated tasks, manual processes and handoffs.
Ranked opportunities
Each with expected benefit, effort and risk.
Recommended architecture
Components, integrations and where each one runs.
Constraints
Security, privacy, data and existing tools.
Scope and phases
What the first build contains and what waits.
Cost range
What drives it up or down.
Decision and next step
What we recommend and what happens if you say yes.
Appendix
Tool inventory and interview notes.
Questions about the Blueprint
What if you recommend not building anything?
Then that is the answer you paid for, and a useful one. The document says so plainly and gives the reasons. You keep the workflow map and the ranked list, and you have not spent build money on something that would not pay back.
Who does the work?
The founder, from the first conversation to the readout. There is no handoff to a team you have not met.
Do we have to hire you to build it afterwards?
No. The document is yours. You can build from it with us, with another team or in house.
How does the credit work?
CAD 1,750 of the fee is credited toward a build over CAD 25,000 that starts within 30 days.
What do you need from us?
Time with the people who do the work, a view of the tools they use, and any document that describes how things run today. We ask for the least access that lets us map the work.
Is the price fixed?
Yes. The price is CAD 3,500 for 7 business days, agreed before we start.
Bring us the bottleneck.
Tell us what is slow. We will say whether a Blueprint is the right first step.
Bring us a bottleneck