Phased Delivery

Ship in phases.

Useful on day one.

Framework 06

Six phases. Each self-contained. Each ends with the team actually using what was built — not a demo, not a "soft launch," a genuine handoff. Nobody waits twelve months to see value. We can stop after any phase and the work done already stands on its own.

By the numbers

In one look.

6

Phases

400–500 hrs

Typical total

36 hrs

Shortest first phase

Every phase

Usable after

REX BLACK · PHASED DELIVERY
Why this is a framework

Big-bang AI projects kill themselves.

The default shape of an AI transformation engagement is: six months of integration work, three months of model work, one big cutover, followed by a month of on-the-ground firefighting while operators learn the new system. That shape fails, consistently, because it puts every risk in the last mile.

The framework inverts this. We sequence so the least-risky, most-visible wins ship first — data model, pipeline stages, intake migration — and the AI work comes after the ground is clean. If the program gets defunded in month four, the client still has a working pipeline. Every phase ends with a hard usable-after milestone we'll sign our names to.

Contract clause — Every phase has a written "usable after" line in the statement of work. If what shipped doesn't deliver that outcome, we fix it before starting the next phase. No exceptions.

REX BLACK · PHASED DELIVERY
The six phases

Sequenced for value, not for convenience.

Indicative hour totals are for a pipeline-heavy services firm with one active pipeline and a roster of 5–10 operators. Scales linearly with additional pipelines.

  1. Foundation & board · 53 hrs — The data model, the stages, and the card view. The least glamorous phase; the phase everything else builds on.
  2. Intake + deal creation · 36 hrs — Kill the spreadsheet. Wire the log-meeting trigger. Operators never open Drive again.
  3. Pre-submission workflows · 67 hrs — Strategy review, contract delivery, document collection, rotting alerts, timeout cleanup.
  4. AI document processor · 102 hrs — The 11-step AI pipeline that owns the "client signed documents" stage end-to-end.
  5. Post-submission + AI router · 138 hrs — The full case lifecycle. Post-submission cadence plus the AI router that reads inbound notifications and moves the deal.
  6. Reporting & dashboards · 70 hrs — Seventeen KPIs across pre- and post-submission, role-based dashboards for every persona.
REX BLACK · PHASED DELIVERY
Phase 1 · 53 hrs

Foundation & board

The data model, the stages, and the card view. The least glamorous phase; the phase everything else builds on.

  • 21 custom properties on the Deal and Contact objects
  • Pipeline definition + 8 deal stages with stage gates and rotting-timer configuration
  • Deal-card view (doc progress bar, conditions, owner, gate status) + Contact-record layout
  • 4 core email templates (Step 1, Expectations, Final Warning, Timeline)
  • Board walkthrough with operators — create test deals, verify layouts

Usable after — Kanban boards visible. Operators create deals manually. No automation yet — but the board is authoritative.

REX BLACK · PHASED DELIVERY
Phase 2 · 36 hrs

Intake + deal creation

Kill the spreadsheet. Wire the log-meeting trigger. Operators never open Drive again.

  • Field audit, CRM Contact properties, CRM-native intake form on the Contact record
  • Legacy Drive template deprecated and archived
  • W0b enhanced deal-creation workflow — trigger on log-meeting, auto-populate deal fields, Step 1 + 24h Expectations emails
  • Google Chat webhook for deal-created alert
  • End-to-end testing + operator training on the new intake flow

Usable after — Auto-deal on log-meeting. Google Drive spreadsheet retired. Operators stop copy-pasting data.

REX BLACK · PHASED DELIVERY
Phase 3 · 67 hrs

Pre-submission workflows

Strategy review, contract delivery, document collection, rotting alerts, timeout cleanup.

  • W1 Strategy Session entry + rotting (Round 2+ re-entries only)
  • W2 Contract delivery on stage move
  • W3 Document-collection email sequence (4-week cadence with re-enrollment — the most complex workflow in this phase)
  • W4 Rotting-timer alerts across all stages (5d / 30d / 2d / 15d / 10d)
  • W5 30-day document timeout + lead-status flip
  • 3 document-reminder templates + Google Chat webhook wiring + UAT

Usable after — S1–S2 fully automated — reminders run themselves, rotting alerts fire, stale deals clean themselves up.

REX BLACK · PHASED DELIVERY
Phase 4 · 102 hrs

AI document processor

The 11-step AI pipeline that owns the "client signed documents" stage end-to-end.

  • E-signing platform API integration (daily polling + webhook) + CRM API tooling for the agent
  • Source-document PDF extraction — conditions, service-connection status, dates
  • Condition reconciliation + mismatch detection with Contact-note updates
  • Form-population engine — PDF form-field mapping across the three forms
  • Client-email drafting + LangGraph orchestration + dead-letter queue
  • UAT with 5+ real test clients + operator training on AI-form review

Usable after — The AI-owned stage runs. Operators stop checking the e-signing platform. Senior operators review AI work, not AI input.

REX BLACK · PHASED DELIVERY
Phase 5 · 138 hrs

Post-submission + AI router

The full case lifecycle. Post-submission cadence plus the AI router that reads inbound notifications and moves the deal.

  • W6 Submitted cadence (Timeline, exam scheduling, Day 40, Day 70)
  • W7 Close-date automation · W8 Round X re-entry setup
  • 3 post-submission email templates
  • W10 integrations: Trello webhook + shared-folder watcher
  • Notification PDF parsing — classifier for 4 notification types
  • 4 notification branches: Dependent · Exam · Favorable (invoice) · Adverse (escalation)
  • Routing logic (Won / Lost / Deferred / no-change) + idempotency + UAT

Usable after — Full case lifecycle running end-to-end. AI routes to Won / Lost / Deferred. Invoices generated for approval. Operators only touch cases that need judgment.

REX BLACK · PHASED DELIVERY
Phase 6 · 70 hrs

Reporting & dashboards

Seventeen KPIs across pre- and post-submission, role-based dashboards for every persona.

  • 11 pre-submission KPI reports (meetings booked, deals created, deal value, time per stage, lead source…)
  • 6 post-submission KPI reports (time in Pending, Won / Lost / Deferred counts, submission-to-close duration)
  • 4 role-based dashboards — Operator, Manager, Finance, Senior Operator
  • Event-tracking hooks at critical stage transitions
  • Report UAT + management dashboard walkthrough

Usable after — All KPIs live. Management sees what they could never see before. Operators see the same board they already use — plus their own performance.

REX BLACK · PHASED DELIVERY
The delivery rules

Four rules we do not break.

These are contract-level commitments. They go in the SOW, not in a slide deck.

01

Usable-after is signed

Every phase has a written usable-after milestone in the SOW. If we don't deliver that outcome, we fix it before the next phase starts. No "we'll come back to it."

02

UAT ends every phase

Hands-on UAT with real operators and real cases, not a demo. The phase is "complete" when the operators use it, not when we say it's done.

REX BLACK · PHASED DELIVERY
Four rules we do not break. · continued
03

We ship data before AI

The AI-owned phases are always 3+. We don't put an agent on top of a messy data model, ever. Garbage in, expensive garbage out.

04

Stop is a valid outcome

After every phase, the client can stop the program. The work already done stands. We've never held a final phase hostage to force a renewal.

REX BLACK · PHASED DELIVERY
Reporting framework

17 KPIs shipped with the build.

Management dashboards are not an afterthought — they're Phase 6. Every KPI below is live, role-based, and tied to the same data the operators see on their board.

Pre-submission (11)

  1. Meetings booked by operator, by day
  2. Meetings rescheduled / no-show by operator
  3. Deals created by day / month, by operator
  4. Round 1 first-time deals
  5. Round 2+ supplemental deals
  6. Deal value by operator (R1 vs. R2+ mix)
  7. Time spent per stage by operator (bottleneck view)
REX BLACK · PHASED DELIVERY
17 KPIs shipped with the build. · continued

17 KPIs shipped with the build.

Pre-submission (11)

  1. Time from session to signed contract
  2. Customer interactions per deal, per operator
  3. Contacts by lead source (paid, organic, referral)
  4. Lead-to-client conversion by channel
REX BLACK · PHASED DELIVERY
17 KPIs shipped with the build. · continued

17 KPIs shipped with the build.

Post-submission (6)

  1. Time in Pending Submission by operator
  2. Submissions per operator, per day / month
  3. Supplemental submissions per operator
  4. Time spent per stage, stages 4–8
  5. Deals Won / Lost / Deferred per operator
  6. Submission-date to close-date duration by operator
REX BLACK · PHASED DELIVERY
Partners

We build on the stack we hold partner status in.

AWS Select Consulting Partner · Anthropic-aligned for Claude · HubSpot Solutions Partner · Salesforce · Google Cloud · Microsoft Azure · Shopify · ISTQB.

AWS Anthropic HubSpot Salesforce Google Cloud Microsoft Azure Shopify ISTQB

REX BLACK · PHASED DELIVERY
Next step

Six phases.

Useful from phase one.

This is how we run every pipeline-automation + AI engagement. Written into the SOW, signed on both sides, shipped phase by phase. If we scope it, you get the usable-after.

Scope your engagement · rexblack.com/lets-talk
See the framework index · rexblack.com/frameworks

REX BLACK · PHASED DELIVERY