Fixed-price automation vs open-ended retainer

Bottom line: Open-ended retainers make sense for ongoing creative, support, or maintenance work. Automation and internal-tool projects should be fixed-scope with an agreed price and a ship date.

Neutrino quotes builds after a Discovery & Opportunities Assessment. You know the fee before anyone writes code.

Why retainers quietly fail SMB automation

A retainer is a contract for time. Automation is a problem that should end. Those two things pull in opposite directions, and the failure mode is predictable:

• Scope creeps because every request sounds small. "While you're in there, could you also…" is how a four-week integration becomes a permanent line item.
• Nobody owns the finish line. With hours billed monthly, there is no moment where the vendor has to say "this is done and working".
• ROI becomes unmeasurable. You cannot compare the cost of a fix to the hours it saved when the cost never stops.
• The knowledge stays with the vendor. Documentation is the first thing dropped when the relationship is open-ended.

None of this requires a bad vendor. It is what the incentive structure produces.

What fixed price changes

• A defined deliverable in production. The scope is written down, including what is explicitly out.
• Ownership transfers on ship. Workflows, credentials, and documentation are yours. If you never call us again, nothing breaks.
• Risk sits with us. If the integration turns out harder than estimated, that is our problem, not a variation order.
• The assessment fee is credited toward the build if you proceed within 90 days.

How we scope so fixed price is honest

Fixed price only works if the discovery is real. The assessment maps how a job moves from enquiry to paid invoice, which systems touch each field, and where data is re-keyed. That produces a ranked list of opportunities with rough effort against impact, so you can choose the first build knowing what the second and third would cost.

We will tell you when something should not be fixed price — genuinely open-ended R&D, or work that depends on a third party we cannot control. In those cases a capped time-and-materials block with a clear review point is more honest than a number we would have to pad.

When a retainer is genuinely better

• Ongoing monitoring and support for systems already in production
• Continuous improvement where the backlog is real and prioritised monthly
• Fractional technical leadership rather than delivery

A sensible pattern for many SMBs: fixed price to build, small support arrangement to keep it healthy, and no retainer in between.

What to ask any automation vendor

1. What exactly ships, and what is out of scope?
2. Who owns the workflows and credentials afterwards?
3. What documentation comes with handover?
4. What happens if the estimate is wrong?

Book an assessment · Workflow automation service · Free scorecard