The 4 phases of every build — and the 3 points where projects die.

New agency owners think a $45K build requires a 10-person team. We've shipped dozens of them. Every single one moves through the same four phases.

The four phases

1. Foundations — database, tables, relationships, permissions. The backbone everything sits on.
2. Workflow automations — intake, routing, approvals, notifications. The skeleton.
3. AI layer — agents, decision logic, and intelligence on top of clean workflows.
4. QA and handoff — edge cases, documentation, training. Where projects live or die.

The order is the doctrine. AI comes third for a reason: agents sit on top of working workflows, never instead of them. If the foundation and workflows aren't clean, the AI layer amplifies the mess instead of removing it.

The three failure points

Every project that fails, fails at one of three points:

• Built before mapping the process. Automating chaos makes faster chaos. Map every workflow with the people actually doing the work — not just leadership.
• Skipped edge-case testing. The happy path is a fraction of the system. Bad inputs, failure modes, and permission gaps are where builds die in production.
• Handed off with zero documentation. No docs, no training, no maintenance plan — the system collects dust within a month and the old way creeps back.

Four phases with three failure points. That's the entire delivery model. The team size people think they need doesn't exist.

Before any of it: the map

Steps one through three of our method never change: map every workflow across the company, cut the processes that shouldn't exist, and wireframe the entire build before a line of code gets written. Phases four and five depend on what's already there — if a company has a clean ERP, we build on top of it, as long as keeping it costs less than replacing it.

The full week-by-week process — onboarding through handoff — is on our method page.