Run
Your software, kept running and improving by the people who built it — for one flat monthly fee.
- Price
- Flat monthly fee, agreed with the build
- Duration
- Monthly, rolling
- Commitment
- Rolling, 30 days' notice — no annual lock-in
The problem it solves
Off-the-shelf software is built for a thousand clients, so your team works its way — and the change you actually need waits months on the vendor's roadmap. Custom software used to fix that and create a new problem: the developer who built it moved on, and nobody dared touch it again.
What you get
-
Your software, kept running
Hosting, monitoring, backups and security updates, in a cloud account in your company's name. You pay the hosting provider directly, at cost — we do not mark it up.
-
Small changes, live in days
A new field, a new report, a rule change, a fix. Ask on Monday, use it by Thursday. Anything bigger — a new tool, or a new system to connect — becomes a fixed-price sprint, quoted before we start.
-
The people who built it
The person who understands your operation is the person who changes the code. Nothing is passed to a team you have never met.
-
A monthly look at what's next
What changed, what broke, and the one thing worth building next. One page, one conversation.
Timeline
-
Month 1
Take it over
Monitoring and access in place, and the line between a small change and a sprint agreed in writing — in your words, not ours.
-
Every month
Run and improve
Changes as they come in, the monthly look, and the next thing worth building.
What moves the price
- How many tools we look after
- How many systems they read from or write to
- Whether anything needs a response outside office hours
What we need from you
- A cloud account in your company's name — we help set it up
- A named person in operations who can say what matters this month
- Access to the systems the software reads from
- A data processing agreement, signed before we run anything that holds your data
A good fit if
- We have built something together and it went well
- Your team works around off-the-shelf tools that were never built for your operation
- The changes you need wait months on a vendor's roadmap
- You want software that keeps up with the operation, without hiring a team to own it
Not a fit if
- We have never worked together — start with a diagnostic
- You need someone on call around the clock — that is a real requirement, and we are not that supplier
- You want your ERP or core operations platform replaced — we build around it, not instead of it
- The work really needs a full-time development team — we will tell you, and help you hire one
What the fee is for
Not our hours. Your software — running, and changing as fast as the operation does. A representative month:
- Keeping what runs, running. The collector that broke because a vendor changed a page. The export that started failing quietly three weeks ago. Nobody notices these until a number looks wrong in a meeting; we notice them first.
- The small changes. A column somebody has been copying by hand. A report that should exist. A rule that ought to have been adjustable from the start. None of these would ever justify a project, which is precisely why they never got done.
- The monthly look. One page: what moved, what did not, and the one thing worth building next.
Where small stops
A small change is one we can ship within a few days. Anything bigger — a new tool, a new system to connect, a new team using it — is a sprint, quoted at a fixed price before we start.
The line is written into the agreement in your words, and we say which side of it a request falls on before we start, not after. A flat fee only works if neither side has to wonder what it covers.
Why a flat fee, not days
A day rate prices speed as a penalty: the faster we ship your change, the less it would be worth to us. A flat fee does the opposite — shipping on Thursday instead of next month is simply the job.
It also sits where your software already sits in the budget: a monthly line for a tool. The difference is that this one was built for your operation, and it is yours.
Sold after a build, never cold
There has to be something to run. Run follows a Build Sprint, or the prototype a diagnostic leaves behind — essentially never a first engagement.
Rolling monthly, 30 days’ notice, no annual lock-in. If it stops being worth it, stop.
When it should change
The monthly look is also the test of whether the fee is still right. If the changes stop coming, the fee should come down to just keeping it running — and we will be the ones to raise it.
Common questions
Who maintains the system after you hand it over?
That is exactly why the handover is part of the deliverable rather than an optional extra. You hold the code, the documentation and the walkthrough recording, so any competent developer can pick it up. If you would rather we kept it running and improving, that is what Run is for — a flat monthly fee, and the code stays yours.
How do you price?
Fixed price for a defined scope, never an hourly rate. You agree the number before work starts and carry no overrun risk. Ranges are published on each service page along with what moves them, so you can estimate before we speak.
We're small. Are we too small for this?
Probably not — small companies are the ones with no analyst and no spare engineering capacity, which is the whole reason this exists. If a diagnostic is more than the problem is worth, we will tell you on the call and suggest something cheaper, including doing nothing.
We reply within one business day.