Skip to content
Calango Lab — homeCalango Lab
04 Recurring revenue

So the system ages well.

A monthly contract for a site, a store or a system. Six-month minimum — below that there’s no time to fix anything structural, only to put out fires.

Month 01↑ minimum commitmentMonth 12

Fixes and improvements

Targeted fixes plus a monthly block of hours for whatever the company wants to move forward.

Monitoring and backups

Uptime watched, automated backups and security updates applied.

Support and reporting

A response time written into the contract and a monthly report of what was done.

Software without maintenance turns into technical debt. Within two years, rebuilding costs more than maintaining would have.

Questions

What people usually ask

Why is the minimum six months?

Below that there’s no time to fix anything structural, only to put out fires. The first months go into putting the house in order — backups, updates, the things that were broken and nobody was counting on. The payoff comes after that, and charging for a single month would be selling the problem without the solution.

Do you maintain sites someone else built?

Yes, and it’s common. When there’s no documentation and no contact left with whoever built it, the starting point is an audit — that’s the legacy rescue service. Once the audit is done, the monthly contract runs as normal.

What counts against the block of hours?

Whatever the company wants to move forward: a new page, a change to a flow, a report, a small integration. What doesn’t count is a rebuild — a new project is a new project, with its own scope and proposal, so the monthly fee doesn’t turn into an endless building site.

Commitment
6 months minimum
Talk about maintenance