From one automation to a system: honest upsell paths

The honest path from one automation to a system runs through adjacency: the next build uses the same data or the next step of the same process the first already touched, proposed only after the first has run for a month and produced its number, it comes from a pain the owner named or the logs showed, and it is priced as its own fixed-scope piece, not folded into the retainer. Five steps over a year give a small business a system it understands; five in a month give it a mess and you a reputation for pushing.

Why adjacency?

Because trust and data both accumulate along the process. The lead-reply automation already knows the calendar and the WhatsApp number; reminders are a small step. The reminders know who attended; follow-ups are a small step. Each new piece reuses systems the owner has already opened and approvals they've already designed. A jump to an unrelated department starts from zero again.

Where the next step comes from

Three honest sources, in order of strength:

1. The logs. "Twelve of the forty leads this month asked about parking" is an FAQ automation waiting to be proposed. "Eight reminders got no reply" is a confirmation button.
2. The monthly note. The "next" line, written every month, is where the owner sees the path before you propose anything.
3. The audit list. The tasks you set aside in the first discovery call; the owner has been waiting for them.

Not a source: your quarter. If the proposal answers your revenue need rather than their pain, it will feel like it, and it will cost you the retainer.

Proposing without pushing

One paragraph, in the monthly note or on the retainer call: what you noticed, what it would take, what it would change, and the price as its own piece. Then silence. Owners who have watched one automation work for a month usually say "yes, when?"; the ones who say "not now" are telling you the truth and will come back.

Pricing the second piece

Its own brief, its own "done", its own price from the pricing method, and a short timeline because the systems are already connected. Never absorbed into the retainer "since we're already working together"; that trade gives away the value and blurs what the retainer is for.

Paths by business type

Each row is a year of work for one client, each step small enough to be a pilot.

When to stop

When the next step would need daily ownership, a team, or judgement per case, say so and stop. A client with three reliable automations and an honest builder is worth more than one with six and doubts about the sixth.

Best fit and not a good fit

Best fit: builders with a client on a retainer whose first automation has run for a month. Not a good fit: proposing the system in the first call; sell the pilot, then let the logs sell the rest.

What to do this week

Open the logs of your longest-running automation and find the adjacent step. Write the one-paragraph proposal and put it in next month's note, priced as its own piece.