Service plans
Maintenance, support and extensions after go-live.
A solution nobody maintains lasts about eighteen months. Not because it breaks on its own, but because the world around it shifts: systems update, APIs change, and the business starts doing something other than what it did when the thing was built.
A service plan is the difference between a system you trust and one you hold your breath around.
Maintenance
Updates, security fixes and the small adjustments needed when something outside changes.
Monitoring
We keep an eye on it running, so failures are caught by us rather than by your customers.
Support with a response time
Somewhere to turn when something misbehaves — with an agreed response time, not just a hope.
Hours set aside monthly
For what you think of along the way. Most good ideas about a system only arrive after it has run for a couple of months.
Regular review
A couple of times a year we look at whether the level fits — including when the answer is that it should come down.
Handover to you
If you want to bring operations in-house, we help with that. Documentation and handover are part of the plan, not an extra.
We do not build things that only work while you keep paying us
You own the code, it runs on infrastructure you choose, and the documentation comes with it. A service plan is something you choose because it is easier, not because you are locked in. It is also why we would rather lower the level than invoice for hours that go unused.
See the levels and pricingHow we deliver
The same approach whatever the area. You can stop after each phase, and you know what the next step costs before agreeing to it.
We map it out first
Ninety minutes going through your processes to work out what can genuinely be automated. You get a clear picture of what is possible and what it would cost.
We build on a fixed price
One- to two-week sprints, each ending in a demo. You know the cost before we start, and you own the code afterwards. No lock-in, no long contract.
We keep it running
Service plans covering maintenance, support and extensions as the business changes.
Is this the right place to start?
If two or more of these sound familiar, there is usually something to gain. If none do, we would rather say so now than after a proposal.
- The solution has become critical to operations
- Nobody internally can fix it if something goes wrong
- You have already had an integration stop working
- You would rather have a fixed monthly cost than a surprise
Questions we get asked
Is a service plan required?+
No. You own the code and can run it yourself or have someone else do it. We recommend one, but we do not build anything that only works as long as you keep paying us.
What if we do not use the hours?+
Then you have paid for peace of mind rather than work, and you should be able to see that. We review the level a couple of times a year — including when the answer is that it should come down.
Does it cover solutions someone else built?+
Sometimes. We need to see the code first. If it is reasonably built and documented, we can take over running it. If it is not, we say so rather than promise something we cannot hold.