Services
We built it. We keep it running.
The unglamorous half: updates, backups, the second step at sign-in, and somebody who answers when it breaks at four on a Friday.
Free · Ten minutes · The report is yours either way
The week after it went live
The people who wrote it are the ones who keep it running.
A release going out in the evening. An error in the application that reports itself before anybody thinks to ring. A small change asked for on Monday and in use by Thursday — by the team that knows why the code does that.
- The release screen — release · thursday. This week's release. Going out. 19:52 Tests passed. 19:58 Copy of the database taken. 20:00 Out to your screens. Live. Out of hours, so nobody loses what they were typing.
- The application's own error report — errors. Save quote — failed, 06:12. quote › save · empty date field. 06:12 It reported itself. 06:31 Cause found in the code. 09:20 Fix went out. Nobody had to report it.
- The application, with the new button on it — yourcompany.com. Quotes. New quote. Copy last quote — New. Last week's quote: Sent. The same job again: Draft. Asked Monday · Live Thursday.
- Overnight: 02:14 — The overnight run stopped halfway. Started again — a note waiting at nine.
- A message and the reply: “The totals page is blank.” “That's the filter from June — fix out today.”
- A restore: Copy of the database, 03:00, Restored into a test copy, Every row still there.
- Updates: The pieces underneath, updated, Tested on a copy first, One step back the same day.
This week's release, going out
Tested first, a copy of the database taken, and out in the evening — not at eleven on a Tuesday morning while everyone is mid-sentence.
An error found before you find it
The application reports its own failures the moment they happen. We read them, find the cause and put the fix out the same morning.
Asked on Monday, in use by Thursday
Small changes do not wait for a big project. They go out the same week, on the screen where you asked for them.
Caught at two in the morning
It is watched overnight, so most trouble is handled before your first person signs in.
The people who built it answer
Not a queue and not a form. Whoever wrote the thing knows why it does that.
Backups you have seen restored
A backup nobody has tested is a hope. We restore one on a schedule and tell you it worked.
Updates that happen without a meeting
Patched on a schedule, tested first, and rolled back the same day if something moves.
No handover, no ticket number, no new supplier reading your code for the first time. The software keeps getting better in small pieces, the errors get found by us before they get found by you, and the person who answers is the person who wrote it.
Ten minutes on a call, then a written plan: what we watch, and what happens the day it breaks.
Plenty of firms will build you something. Rather fewer will still be there in November when it stops working.
So the thing gets built, handed over, and quietly becomes nobody's job.
Same team
builds it and keeps it running
In pieces
shipped so you can use them
Same day
a person answers
If you hire us
How the first build goes.
01First weeks
We read what is there
Whatever runs your work today keeps running while we learn how it is actually used.
02The first piece
Something you can use
One useful part, shipped early, instead of one delivery at the end you cannot see until it lands.
03After that
The people who built it
The same team keeps it running, so a change is a conversation rather than a project.
Ten minutes on a call. You keep the plan either way.
What we handle
What that actually covers.
Not a list of products — the things that change for you.
Caught at two in the morning
It is watched overnight, so most trouble is handled before your first person signs in.
Backups you have seen restored
A backup nobody has tested is a hope. We restore one on a schedule and tell you it worked.
A second step at sign-in
On every account that touches your data. It is not optional and it is not an upsell.
Updates that happen without a meeting
Patched on a schedule, tested first, and rolled back the same day if something moves.
The people who built it answer
Not a queue and not a form. Whoever wrote the thing knows why it does that.
A straight answer in writing
When an insurer or an auditor asks what you have, you get a document, not a shrug.
Start with the review. Ten minutes.
Start with a scoping call: ten minutes, then a written plan with what it does, what it costs and how long it takes.
Or ten minutes on the phone first
About half the reports say you’re in decent shape. If that’s you, we say so and leave.