How to run a two-week pilot that turns into a retainer

A two-week pilot converts into a retainer when it has a signed one-page brief, a baseline number taken before you build, at least five working days running on real inputs with every run logged, a hand-over the client can open themselves, and a last-day conversation that reads the number together and proposes what happens next. The retainer sells itself because by day fourteen the owner has watched something work, seen what breaks, and knows who fixes it.

Why two weeks?

Long enough to run on real data for a week, short enough that an owner will say yes without a committee. Anything shorter never meets a real input; anything longer stops being a pilot and starts being a project without a decision behind it.

Days 1–2: access, brief, baseline

Get the access you listed in the brief on day one; a pilot that waits a week for a password is a three-week pilot. Confirm the brief is approved in writing. Then take the baseline reading of your number, before anything is built: reply times from the CRM, no-shows from the calendar, whatever you agreed. Without a baseline there is nothing to compare on day fourteen.

Days 3–5: build in their tools

Build in the client's accounts, in a tool they can open, with a scenario or workflow named plainly. Keep the exception path visible: the step where unusual inputs go to a person is the step the owner will look for. Don't polish; get to real inputs.

Days 6–10: run on real inputs, log everything

Turn it on for real. Keep a simple log: each run, what came in, what went out, anything odd. Message the owner briefly every second day: "42 leads handled, 2 went to the front desk as designed, one duplicate we fixed." The messages are the product as much as the automation; they show the owner what a retainer would feel like.

When something breaks, and something will, tell them the same day with what you changed. This is the moment trust is built or lost.

Days 11–12: fix, document, hand over

Fix what the week exposed. Write a one-page hand-over: what it does, where it lives, how to pause it, what to do if X, who to call. Walk the owner through it on a call, with them driving. If they can pause the scenario and change one message template on their own, the hand-over is done.

Days 13–14: read the number, propose the retainer

Read the number together, against the baseline, honestly. Then the retainer conversation, in this order:

1. What you've been doing for two weeks that they now expect: watching the runs, fixing quickly, telling them what happened.
2. What that costs to keep: the retainer's four items with numbers: monitoring, response time, small changes per month, the monthly note.
3. What comes next: the second task from the audit list, as a fixed-price add-on when they're ready.

Say the price plainly and stop talking. Most owners who have just watched two weeks of logs say yes; the ones who don't usually name the real objection, which you can address.

If the number is disappointing

Lead with it. "Reply time dropped from nine hours to under a minute, but no-shows didn't move; the reminder message needs a confirmation button. Here's what I'd change." A candid miss plus a plan is a strong retainer pitch because it demonstrates exactly what the retainer buys.

Best fit and not a good fit

Best fit: first engagements with small businesses and any builder who wants recurring revenue without selling big projects. Not a good fit: work that can't produce a number in two weeks; scope it as a longer fixed project instead and say why.

What to do this week

Write your pilot as a fixed offer: what's included, the five-day real-data rule, the hand-over, and the last-day review. Put it on your profile. It is the easiest thing you sell.