Every Phase Has a Deliverable You Keep

The /ai engagement page breaks the work into four phases. Each one has a deliverable listed at the bottom. That's not formatting for clarity. It's the sales mechanism.

Phase 01: Operations Map (yours to keep)

The first phase is a 90-minute working session and a written document by Friday. The deliverable isn't "we'll talk about your workflow." It's a specific document: your top 10 manual workflow leaks, scored by impact and effort, the top 3 flagged, and an ROI estimate per workflow.

"Yours to keep" is doing specific work in that line. Not "we'll share notes." The document has value independent of whether you hire us for the build. You can take it to another vendor. You can hand it to an internal team. You can do nothing with it. The audit produces a real output, and the prospect keeps it regardless.

That's a lower-stakes ask than "sign a six-week engagement." The ask is: let us do a 90-minute session and we'll show you what we find.

Phase 02: Build spec + ROI model per workflow

If the engagement continues, we write a technical spec and ROI projection for each of the top three fixes. Two deliverables with specific shapes. The prospect isn't agreeing to "a build." They're agreeing to a described system with a projected return.

This is the moment to stop if the numbers don't make sense. We'd rather have that conversation at phase 2 than at phase 4.

Phase 03: Live engine + 1 trained team member

The install phase has two deliverables: the working system, and one person on the client's team who knows how to operate it. We don't want clients who can't touch the engine without calling us. An owner who understands how to extend a workflow is a better outcome than a dependency relationship.

Phase 04: Monthly retainer (optional)

The fourth phase is explicitly optional. The copy says it. If the engine runs and the team can maintain it, there's no lock-in. The retainer exists for ongoing tune-ups and one new automation per month. It's an option, not a default.

What naming deliverables actually does

A six-week custom build sounds like a large, open-ended commitment. Broken into four phases with four named outputs, it becomes a series of bounded engagements with known endpoints.

Small business owners have been burned by open-ended consulting. The scope inflated, the timeline stretched, the invoice arrived, and nothing shipped on a schedule they understood. Naming the deliverable changes the contract from "trust us to do good work" to "here is what you get by the end of this phase."

Each phase is a natural stopping point. After phase 1, the prospect has the Operations Map. After phase 2, they have a spec they could take anywhere. The ask at each stage is bounded: decide whether to take the next step, not whether to trust a six-week black box.

That's how you sell a complex custom build to a service business owner who's already skeptical of consultants. You don't sell the engagement. You sell the next deliverable.