Skipping it entirely
The single most common failure. Teams jump straight to Build, automate the wrong workflows, and burn 60–90 days discovering they've hardened the wrong process.
III.Flame
01 · Ashes · Two weeks
Diagnose
Two weeks of founder-led discovery.
Diagnose is the founder-led discovery phase of the Phoenix Methodology. Two weeks. No build work. The single output is a prioritized diagnosis of the highest-leverage operational changes in your business.
What it is
A structured two-week sprint in which we interview your team, trace three or four real customer journeys end-to-end, read your internal channels, and map how work actually flows inside your business — not how the org chart says it does. Nicholas runs it personally.
What it is not
Diagnose is deliberately not several things that other firms will call discovery:
- It is not a slide-deck audit. No consultant deliverables that look like McKinsey pitch ware.
- It is not a tool recommendation. We don't name a single tool in Phase 1.
- It is not a growth-strategy workshop. Growth is downstream of operational clarity; we do clarity first.
- It is not optional. Every engagement begins here, including condensed Phoenix Sprints.
You leave with
The Diagnosis Document
A written artifact naming the top five leverage points in your business, ranked by effort, dependency, and expected operational return. Includes the workflows we recommend you do not automate, and why. Roughly 12–20 pages of specific, operator-grade findings tied to named people and named processes.
How we actually run it
Week one is pure intake. We sit on calls with the five to eight people closest to the operational surface — the salesperson, the bookkeeper, the operations lead, the person who quietly runs customer support on their phone at 9pm. We read your Slack, your software, and your inbox templates. We trace inbound leads, onboarding flows, and billing cycles end-to-end, stopping every time there's a handoff.
Week two is synthesis. We surface the silent bottlenecks — the workflows where the business is paying human attention to do what a system should do. We rank them. We write the document. We present it back, with every recommendation tied to a specific observation from week one.
What you actually walk away with
The Diagnosis Document is useful whether or not you continue with us. Founders have used it to brief internal hires, pitch board members on a transformation budget, and negotiate with other consultants. It is written to be portable.
- Top five leverage points, ranked.
- Named workflows we recommend you do not automate.
- A short-list of the systems (categories, not brands) that should change.
- A one-page executive summary a board member can read in four minutes.
- Clear go/no-go signal on whether Phase 2 Architect is the right next step.
When Diagnose is the right next step
If you're a 5–150 person business, you can feel that your operations are limiting you, and you can name three to five workflows that seem obviously broken — Diagnose is the right start. If you already have in-house technical leadership and you just need a scoped automation build, skip Diagnose and engage us for Architect and Build.
If you're pre-revenue or under five people, Diagnose is probably too heavy. Build your first workflow yourself with a free weekend and n8n.
Where it fails
Running it without the founder
Diagnose surfaces political realities — who owns what, who actually runs which process. If the founder isn't in the interviews, the findings won't survive the first internal pushback.
Treating it as a deck
If the deliverable is a slide deck instead of a written document, the detail gets stripped out in the name of readability. The detail is the point.
Phase 1 Diagnose — FAQ
How long does Diagnose take?
Two weeks from kickoff to delivery of the written Diagnosis Document. No exceptions — a shorter timeline compromises the quality of the synthesis.
Who runs Diagnose?
Nicholas Will runs every Diagnose personally. This is the phase where the judgement is the product, and we do not delegate it.
Can I skip Diagnose and go straight to Build?
Only if we've already run a Diagnose with you previously, or if your scope is narrow enough that it's really a single-workflow build. For any full transformation, skipping Diagnose is the single most reliable way to automate the wrong thing.
What does Diagnose cost?
The 15-minute call is free. Published starting prices are on /pricing. Custom software starts at $7,500, with a $2,500 deposit. The call sets the final quote. Nothing on this page is a blank price.
Know what you'd actually fix first?
A Strategy Session is a 30-minute version of Phase 1 Diagnose. Walk away with two named bottlenecks and a clear view of whether a full Diagnose is worth booking.
Get your time back.
Nicholas runs this studio on it. Mobile speed went from 49 to 92. We run on it too.