Insights · Running software · August 5, 2026 · 4 min

The price isn’t the project. It’s the first year.

What to ask any studio about year three, and why maintenance is in every proposal we write.

What to ask any studio about year three, and why maintenance is in every proposal we write.

Software needs investment the day after launch: dependencies age, certificates expire, a browser update breaks a date picker, the ERP changes an API. None of this is dramatic. All of it is someone’s job.

What year three actually takes

We run our own products, so we know. The work is small, constant and unglamorous, and it does not go away because nobody budgeted for it.

Where a maintenance month goes
Dependency and security updates
38%
Third-party API changes
24%
Small fixes and requests
22%
Monitoring and incidents
16%
Example figures. Unflow retainer log, average across Standard-tier clients.

The question to ask any vendor

Who is paged when it breaks at 2am in year three? If the answer is a shrug, the price you were quoted is not the price.

That is why every proposal we write includes a maintenance retainer, and why declining it is done in writing. Not because we want the revenue, though we do, but because "we will figure it out later" is how systems get abandoned.

The layer that ages fastest
Integrations

Connect your CRM, ERP, warehouse, finance and carrier systems so nobody retypes a thing, and a named person hears first when something breaks.

See the service →
Not sure what to do next?

Should you build it at all?

Answer a few questions about how your team works, and we’ll tell you which way we’d go, with the reasoning and a playbook sent to your inbox.