Understand
Before deciding what to build, we learn how the work actually gets done. We measure where things stand today and agree the KPIs this software should move.
Services
Maintenance, takeover and renewal
We take over maintenance of systems built by others, including Windows software that has been in use for years. We first work out how it is built and document it, fix problems without stopping the business, and renew it piece by piece where it matters most.
Who this is for
- The original developer can't be reached, or has declined to maintain it
- Maintenance is expensive, and still slow
- Your business runs on VB6, VB.NET, .NET Framework, Access or Excel macro software
- The person who understood the system has left
- Your OS or servers are approaching end of support
Common problems
Nobody understands how it works
There is no documentation, and nobody knows what a small change might break.
Too important to touch
It sits at the center of daily work, so it can't be stopped long enough to rebuild.
The platform is ageing
Support for the OS, browser or database is ending, and the security risk keeps growing.
Rebuild quotes are too big
The only proposals on the table replace everything at once, with high cost and high risk.
What we deliver
Assessment and takeover
We study the code, database, servers and runbooks, and document how the system works and where the risks are.
Maintenance and operation
Bug fixes, user questions, monitoring, backups and security updates.
Keeping Windows software alive, then moving it
VB6, .NET Framework, WinForms, WPF and Access software: we keep it running first, then move it to modern .NET or the web where that makes sense.
Step-by-step renewal
We renew the parts with the biggest payoff first, running old and new side by side until it is safe to switch.
How we work
From understanding your work to making the software stick and improving it — eight steps, with AI at every one. Hire us for all of it, or just the step you need.
Build
We build in short cycles and check each one against real work early, so the budget goes into what actually matters.
Grow
Software only creates value once it's in use. We make it stick, measure what changed, and keep improving — until your own team can run it.
Why work with us
KPIs before code
We agree what success looks like before we start, and check it in numbers after launch.
Product people, not order-takers
We build, ship and run our own products, so we think like the owner — and we'll push back on features that won't pay off.
Deep in your business
We learn how the work really happens before deciding what to build — including whether to build at all.
In use, running smoothly
Rollout, training, maintenance and improvement are part of the job. Software nobody uses creates nothing.
You're never locked in
We leave the know-how with your team. Keep us on, or take it over — your choice.
How we measure the result
When work gets faster, the time saved is quickly filled by other work — and unless someone measures it, the value the software created simply disappears. So we measure the same process before and after, and you can see exactly what changed.
- Incidents, and time to recover
- Time to answer user questions
- Maintenance cost
- Time spent on manual workarounds
FOR ENGINEERS
For engineers
How we take over
We first reproduce the production environment and confirm the build and deployment steps, then put the code under Git so every change is recorded.
Old code without tests
We don't rewrite straight away. We first add tests that pin down today's behavior, then make changes, starting with the flows that matter most to the business.
Gradual migration
Rather than replacing everything at once, we move screen by screen or feature by feature, sharing the database while old and new run in parallel, and switch over once the new part is proven.
Technologies we take on
VB6, VB.NET, C# (.NET Framework and .NET), WinForms, WPF, ASP.NET Web Forms and MVC, SQL Server, Access and more. We usually move to modern .NET and Azure.
How we use AI
AI helps us read old code, write documentation and create tests, which shortens a takeover. People check everything AI produces before it is used.
Deliverables and handover
- Documentation of the system's structure and how it works
- Source code under Git, with build and deployment steps
- A record of all maintenance work
- A renewal plan, with an estimate for each step
First step and contract options
Start by telling us about the system and what is going wrong. From there we begin in one of two ways.
Assessment
We study the code and environment, and set out how it works, the risks, and the options for maintenance and renewal.
Take over maintenance
We take over maintenance alongside the assessment, keeping today's work running first.
Contract options
Fixed-scope contracts that deliver an agreed scope, or time-and-materials engagements for ongoing maintenance and improvement. We do both.
Frequently asked questions
Can you help if we don't have the source code?
Tell us the situation first. We'll check together what can be done with what you have: executables, the database and the servers.
Do we have to rebuild everything?
Usually not. Keeping what works and renewing the most valuable parts first costs less and carries less risk.