The Architecture Blueprint
A fixed-scope, senior-led architecture phase that de-risks your build before you commit to it — and you keep every artefact, whether or not we build it together.
- Investment
- From R60,000
- Timeline
- 2–3 weeks
- The build fee
- Credited 100%
- You own the IP outright
- No lock-in, no black box
- Senior-led, start to finish
Why start here
Software fails at the architecture, not the code.
The expensive failures — the transaction that double-charges under load, the cache key that serves one client's data to another, the background job that runs with no idea whose tenant it belongs to — are decided long before anyone writes a feature. They're decided in the data model, the boundaries, and the security posture.
Most engagements skip straight to building because building is what looks like progress. The Blueprint slows down at exactly the point where a mistake is cheap to fix and later becomes catastrophic. You get a complete, costed design — and the freedom to build it with us, with someone else, or to sit on it. Either way, you leave knowing exactly what you're committing to.
What you get
A complete architecture — and every artefact is yours to keep.
System & data model
Entity-relationship diagrams and a schema designed for how your data actually behaves — the structural decisions made before the first migration runs.
API contracts & service boundaries
Explicit request/response contracts and clean service boundaries, so the build has an unambiguous spec and teams don't trip over each other.
Tenant & security model
Row-level isolation, RBAC, and audit logging designed in from the start — the failure modes that quietly leak one client's data to another, engineered out.
Fixed-scope build plan
A milestone-by-milestone plan with estimates and a fixed price for the build itself. You see exactly what it costs and how it runs before you commit.
Tech-stack recommendation
The right stack for the problem, justified — the tools we'd reach for and why, drawn from the same vetted toolsets we publish openly.
See our toolsetsRisk & failure-mode analysis
The architectural blindspots that turn a working demo into system debt, named up front — the forensic thinking behind our published post-mortems.
See the blueprintsHow it runs
2–3 weeks, four phases.
- 01
Kickoff
A working session to map the domain, the constraints, and what success actually means. We leave with a shared definition of the problem.
- 02
Discovery
We interrogate the edge cases and the load — the concurrent writes, the money paths, the tenant boundaries — and document what will bite in production.
- 03
Architecture
ERDs, schema, API contracts, and the security model come together into a coherent design, with the tech-stack decisions justified.
- 04
Readout & handoff
A walkthrough of the whole design plus a costed, fixed-scope build plan — and every artefact handed over to you to keep.
A good fit if…
- You're about to commit real budget to a build and want to de-risk it first.
- The system is genuinely complex — multi-tenant, real-time, payments, or regulated data.
- You've been burned by a vague quote or a build that drifted, and want a fixed scope.
- You want the architecture to be yours — no lock-in, no black box.
Probably not if…
- You need a quick brochure site or a template you can buy off the shelf.
- The scope is trivial and well-understood — you don't need an architecture phase to start.
- You're looking for the cheapest possible hourly team, not a de-risked outcome.
This is how we think
“Their team demonstrated a strong understanding of both the technical and operational side of our business, delivering a solution that is efficient, scalable, and easy to manage.”
Philip Kotze — PE Management
The same engineering judgement that goes into every Blueprint is on open display in The Threshold — our library of specs, runbooks, and forensic post-mortems from production work.
Questions
The honest answers.
What if we don't build with you?
You keep 100% of the artefacts — the ERDs, API contracts, security model, and the costed build plan — with no strings attached. It's real engineering work you own outright, so you could hand it to any competent team and they could start building. The Blueprint stands on its own.
How is this different from a free proposal?
A proposal is a sales document written to win your business. The Blueprint is paid engineering work: senior architects actually design your system, surface the edge cases, and cost the build. You're paying for the design and the artefacts, not a pitch — which is exactly why it de-risks what comes next.
Is the fee really credited toward the build?
Yes. If you proceed with the full build with us, 100% credited toward the build — it's deducted from the build price. In effect, the Blueprint becomes risk-free: you either walk away owning a complete architecture, or you roll it straight into the build at no extra cost.
What do you need from us?
Access to the people who understand the problem (usually a founder or product lead), any existing docs, data, or systems, and a couple of short working sessions over the engagement. We do the heavy lifting; we just need the domain knowledge that lives in your team.
Do you sign an NDA?
Yes — happily, before we see anything sensitive. Confidentiality and careful data handling are baseline for us, not an afterthought.
How much does it cost and how long does it take?
From R60,000, depending on scope and complexity, over 2–3 weeks. You'll get a firm number after a short scoping call — no surprises.
De-risk the build before you commit to it.
Start with the Blueprint. From R60,000, over 2–3 weeks, 100% credited toward the build if you proceed — and yours to keep either way.
Start your Blueprint