Letting the vendor pick the architecture
If you let a custom software consultant run Architect, every answer will include custom software. Architect must be tool-agnostic until the analysis demands a specific tool.
III.Flame
02 · Ember · Two to three weeks
Architect
The drawings. Not the code.
Architect is where we decide how the transformation will be built — the system of record, the integration spine, the SI surfaces, the human-in-the-loop boundaries. No code is written. The output is a one-page system diagram every operator can read and agree on before anyone opens an IDE.
What it is
Two to three weeks of technical design work following a completed Diagnose. We specify the architecture of the target-state operating model: where data lives, how tools talk to each other, where SI plugs in, and where humans stay in the loop. Think of it as the blueprint stage of a building — boring, short, and the single thing that prevents million-dollar mistakes later.
What it is not
A few things Architect is specifically not:
- Not code. We don't open n8n, Make, or custom software during Phase 2.
- Not a tool sales pitch. Tool selection is a conclusion of the architecture, not a starting point.
- Not an RFP exercise. We don't hand you a 40-page requirements document and ask vendors to bid.
- Not hypothetical. The architecture is drawn against your actual Diagnose findings — no generic reference implementations.
You leave with
The Architecture Brief
A one-page target-state system diagram plus a written architectural rationale. Names your system of record, integration patterns, automation platform, SI surfaces, and human checkpoints. Any competent operator should be able to read it and agree or disagree clearly — no ambiguity.
What we decide in Architect
The five core decisions: the <strong>system of record</strong> (usually the software — where the ground-truth customer data lives); the <strong>integration spine</strong> (how the software, billing, comms, and ops tools exchange data); the <strong>automation platform</strong> (n8n, custom software workflows, Make, Zapier — picked based on who maintains it long-term); the <strong>SI surfaces</strong> (which workflows get an LLM reasoning layer, and which stay rule-based); and the <strong>human-in-the-loop boundaries</strong> (where people review before send, and where the system ships autonomously).
Each of those decisions is documented with the tradeoffs we considered and the reason for the call. You should be able to read the rationale six months later and still understand why we chose what we chose.
Why no code is written in Phase 2
Teams that skip Architect and jump to Build almost always rebuild the same workflow two or three times. The cost of rework is 5–10x the cost of doing Architect properly. The deliberate boredom of Phase 2 is the single most ROI-positive time you'll spend in the engagement.
Where it fails
Over-designing
A 60-page architecture document is a sign of a consultant padding the invoice. A good Architecture Brief is short because the decisions are clear.
Under-specifying human checkpoints
The failure mode we see most often: automation ships without a human-review step on sensitive outputs. Architect is where those boundaries get drawn — retrofitting them later is painful.
Phase 2 Architect — FAQ
Can you run Architect without having run Diagnose with us first?
Yes, if you have a recent, credible Diagnose document from another firm or from an in-house process. We'll spend the first few days pressure-testing it before starting the design work.
Do you recommend specific tools in Architect, or stay tool-agnostic?
We name specific tools, because an architecture that doesn't commit to tools isn't an architecture — it's a wish list. The commitment is justified in writing so the decision is auditable.
What if we disagree with the architecture?
Push back. The Architecture Brief is deliberately designed to be legible enough that any competent operator can agree or disagree with it clearly. We'd rather argue in Phase 2 than rebuild in Phase 3.
Have a Diagnose but no architecture?
If you've been through a discovery with another firm but never got a one-page architecture out of it, we can run Architect as a standalone engagement.
Get your time back.
Nicholas runs this studio on it. Mobile speed went from 49 to 92. We run on it too.