Home Services Work About Blog FAQ Contact
← Back to blog

One-off project or retainer: how to pick when hiring automation help.

A Reddit thread this week asked how to price automation work — project or retainer — and how to land a first client doing it. That's the seller's version of a question most business owners never think to ask before they sign anything.

Short answer: pay for a one-off build when the job has a clean edge — one workflow, one integration, a finish line you can point to and call done. Pay for a retainer when the job doesn't end at launch, because something has to keep working while your volume, your vendors, or the AI model underneath it all change without asking your permission first.

That question showed up this week in r/smallbusiness, asked from the other side of the table: someone weighing whether to start selling n8n and AI agent builds to small businesses, and whether to charge per project or put clients on a retainer from day one. Fair thing to work out before you sell automation work. It's also the exact thing to work out before you buy it, and almost nobody does — most owners just sign whatever structure the agency defaults to.

What a one-off build actually buys you

A one-off is a transaction with a finish line. You scope a workflow — route form leads into your CRM, sync orders between Shopify and a fulfillment partner, draft replies from a shared inbox — someone builds it, you test it, it ships. Support after that usually caps at a short bug-fix window, 30 or 60 days is typical. After that, the thing is yours. If it breaks because a vendor changed something on their end, that's now your problem to notice and your money to fix.

That's fine, genuinely, for the right job. A single, well-defined automation sitting on a vendor that doesn't change its API every quarter is a good candidate for a one-off. You shouldn't pay a monthly fee to have someone babysit something that mostly runs itself.

Where a retainer earns the extra cost

Retainers make sense the moment "it keeps working" becomes a job of its own instead of a one-time deliverable. Automations built on AI models especially don't hold still — providers retire model versions, change pricing, rename endpoints — and someone has to be watching for that before it fails quietly instead of after.

A one-off build is a bet that nothing changes after launch. A retainer is an admission that something always does.

We've written before about how an automation can run green and still do nothing and why "time saved" alone doesn't justify the spend — both are retainer-shaped problems. Nobody notices a workflow quietly dropping rows, or a trigger that stopped firing after a daylight-saving shift, unless someone's watching for it on purpose, on a schedule, as part of the job they're paid to do.

What this looks like with real numbers

Here's how we structure it ourselves. A $500 AI audit comes first, and that fee gets credited toward month one if you move forward. Past that it's a build-and-monitor retainer on a 6- or 12-month term — the build fee folded into the retainer instead of billed as a separate chunk up front, support and training included rather than metered by the hour. The audit is the only number we post without a conversation first. Everything past it depends on what's actually getting built.

Compare that to something that's genuinely more one-off in shape, like our AI phone receptionist add-on: a flat setup fee ($500 or $750 depending on the tier) plus a flat monthly minute allowance. You're paying monthly, so it looks like a retainer on the invoice, but it's closer to a subscription for a fixed capability than an ongoing-watch arrangement. The billing cadence isn't what makes something a retainer. What you're actually getting each month is.

The middle option most people skip

You don't have to pick one model for the whole relationship. A common pattern that works well: pay for a one-off build, then separately decide whether you want a lighter monitoring-only arrangement on top of it — someone who gets paged if the thing stops working, without the full build-and-iterate scope of a real retainer. It costs less than a full retainer and it's more than nothing, which is where most unmonitored one-off builds quietly end up a year later.

Three questions worth asking before you sign either one

  1. What exactly ends when the build is marked "done"? Get the bug-fix window in writing, and ask what counts as a bug versus a change request you'll pay for separately.
  2. If it's a retainer, what do you get in a normal month beyond "monitoring"? A specific number of hours, a response-time commitment, someone who actually tells you when an underlying model gets deprecated — not just a vague promise that someone's keeping an eye on it.
  3. What happens if you cancel? Do you keep the workflow you paid to build, or does access end with the contract? This should be answered before you sign, not discovered on your way out.

Ask those three whichever side of the table you're on. If you've got a specific workflow and aren't sure which model actually fits it, ask us directly — we'll give you a straight answer, even when the straight answer is that you don't need either one yet.

— Cole

Sources

Not sure if your automation idea needs a build or a retainer?

30-minute call. We'll tell you honestly which one actually fits, even if it's neither yet.

Book a Discovery Call →