The project finished, the developer moved on, and now nobody will touch it.

Keep a running system running, and keep changing it, without hiring a developer.

The commercial shape of it

Timeline: 2 weeks to your systems under a written agreement
Cost: Scoped per engagement rather than sold from a price list, and quoted in writing before anything starts. How pricing works
Built for: Manufacturing · Distribution and wholesale · Professional services · Healthcare · Education

What you get

A named response time for each kind of problem, agreed in writing
One person who knows your setup, not a queue
Security and dependency updates applied and reported
Backups tested by restoring them, not by checking a box
A monthly allowance of small changes that actually ship
A written handover, kept current, so you are never locked in

The room it happens in

A build ends and the attention goes with it. Six months later there is a bug nobody owns, a library that stopped being updated, and a change everybody agrees is small that has been waiting since March. The person who built it has moved on. So the system slowly stops matching the business, and the workarounds start.

Any of this sound familiar?

A small change has been waiting three months for somebody free.
The person who built it has left, and nothing was written down.
You do not know whether your backups actually restore.
Something breaks and nobody is sure whose job it is.
You are paying for a system the team has quietly stopped using.

If two or more of those are yours, this page is about you.

Most systems do not fail. They drift. The business changes, the software does not, and people build spreadsheets around the gap until the spreadsheets are the real system.

What support actually means here

A person, not a queue. The same engineer sees your setup every month, so the third request does not need the whole story again.

Response times in writing. What counts as urgent, and what happens then, agreed before anything goes wrong rather than argued about during.

Backups proved by restoring them. A backup nobody has restored is a belief, not a backup. We test yours and tell you how long a real restore took.

The small changes are the point

Uptime is the easy half. The reason systems get abandoned is that changing them became slow, so people stopped asking. A monthly allowance of small changes keeps the software matching the business, which is the only thing that stops the workarounds starting.

What we will not do

We will not take on a system we believe cannot be kept safe. And we will not stay quiet about one that is drifting toward a rebuild. Both are easier to say early. Neither gets easier to say later.

Four weeks covers a first working version, agreed in writing before we start. Very large programmes, work spanning many systems, and moving data out of software that cannot export it are all priced separately. Read what four weeks includes.

On every engagement

You own it, and you can leave. Your code, your data, your accounts. Taking it in-house or to another supplier is a handover, not a negotiation.
Built for India's DPDP Act. Identity kept separate from the consent and audit record, no personal data in URLs, and none in logs.
Security enforced by the build. Secrets scanned on every commit, payloads size-checked before parsing, every write endpoint rate limited. If a check fails, nothing ships.
Anything with AI in it is measured. An evaluation set, a human review step wherever a wrong answer costs money, and drift monitoring after go-live.

How we build, where your data lives, and exactly where we stand on certification — all of it is on our security page.

Asked and answered

Will you support something you did not build?

Often, yes. We review it first at our cost and tell you what we find. If the honest answer is that it needs rebuilding rather than supporting, we will say so, and we will not quietly take a retainer for something we cannot keep alive.

What counts as a small change?

A new field, a report column, a changed rule, a fixed label. Anything with a design decision in it is a piece of work with its own estimate. We tell you which one you are asking for before we start, not after.

Are we locked in if we sign this?

No. The handover document stays current, the code and the data are yours, and you can take them to anyone. A supplier who is hard to leave is a supplier who stops trying.

The other 11

Next step

Start with the one that hurts most

Tell us what is running, who supports it today, and what has been waiting longest. On the call we go through what would have to be true for us to take it on, and what we would not take on.

Book a call Ask us to call you