run
Run the clock
Kickoff as realignment, land a week-1-2 quick win, run a midpoint review, and keep closing through the pilot.
Momentum beats magic
Signing-to-kickoff energy dies in a lull. A first visible success in the opening weeks keeps the committee engaged. Midpoint is where you adjust or confirm trajectory against written criteria.
| Window | Proof work | Close work |
|---|---|---|
| Weeks 1–2 | Install, train, first live run | Quick-win memo to EB |
| Midpoint | Criteria scorecard | Adjust or confirm; invite EB to final |
| Final week | Evidence pack | Ask for the PO |
Always be closing
By the commercial conversation you should already know what security review and procurement look like. Finding that out at the end is too late. Verticalized pain beats we also use AI.
In this phase
- Kickoff is realignmentRun kickoff as stakeholder realignment.
- Week 1-2 quick winLand a visible success in the first two weeks.
- Midpoint reviewHold a formal midpoint against written criteria.
- Always be closingKeep security, procurement, and commercial path moving.
- Vertical pain vs generic AIWin with workflow-specific language and proof.
FounderNexus
If the pilot worked and the PO is stuck, bring it to FounderNexus. Operators who have closed this motion will pressure-test the ask — not cheerlead.
Join FounderNexusClaims and patterns on this page are paraphrased from practitioner session notes and the Startup Bible pilots page. See Sources.
Continue the journey
- Set the termsScope the pilot like an MVP, write measurable success criteria, price it, and lock an agreement with a path to a PO.
- Close for the POAsk for the purchase order, reduce scope instead of discounting, diagnose stalls, and use ROI to restart stuck deals.
- Kickoff agendaA kickoff agenda that realigns stakeholders.