Fixed-price automation vs open-ended retainer
Retainers reward slow work. Fixed-price automation projects align incentives for Australian SMBs.
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 a fixed price after a free call and a working sample. 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.
- Nothing locks you in. Your data is always yours, you get a permanent licence to use and change the system, and the documentation comes with it. If you never call me again, nothing breaks.
- Risk sits with me. If the integration turns out harder than estimated, that is my problem, not a variation order.
- The working sample comes first. You see it running on demo data before you pay anything.
How I scope so fixed price is honest
Fixed price only works if the discovery is real. On the free call I map how a job moves from enquiry to paid invoice, which systems touch each field, and where data is re-keyed. Then I pick the one fix that pays back fastest, and the working sample shows you its shape before you commit.
I will tell you when something should not be fixed price — genuinely open-ended R&D, or work that depends on a third party I cannot control. In those cases a capped time-and-materials block with a clear review point is more honest than a number I 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
- What exactly ships, and what is out of scope?
- Who owns the workflows and credentials afterwards?
- What documentation comes with handover?
- What happens if the estimate is wrong?