The situations we take on
Solve With Software takes over business systems in four situations, each with its own page: no documentation and the developer gone, a system too risky to change, a choice between replacing and modernising, and an AI-built app that stalled. Each page describes the situation as it usually presents, what can be established in the first few days, and the route out. The free consultation is where you say which one is yours.
Free · 1 hour · no obligation
Which page is yours
The developer has gone and nothing is written down: no documentation. Every change breaks something else, so nobody changes anything: too risky to change. The system works, but the question of replacing it keeps coming back: replace or modernise. Most of an app exists, built in Lovable, Replit, Cursor or Bubble, and the last part won't come: stalled AI-built app.
Two of these often apply at once. An undocumented system is usually also the one nobody dares change, and the replace-or-modernise question follows from both. Start with the page that matches the day you are having; each links to the others.
What the four have in common
The system is unmapped rather than broken. The rules the business depends on are in the code, the database and the people who use it, and not yet written down in one place. The first job in every case is to do that: read the code, read the data, sit with the users, and put what the system does on paper with the risks and the options against it. That is the assessment, from £395 + VAT, and it ends in a fixed price for each option.
From there the work is staged whichever situation you started in: the system kept running, changes built and tested on a copy, then run in staging alongside live with the data reconciled, then live, with the old version as the fallback.
Four situations
We have no documentation for our software
No documentation and the developer has gone. We work out what the system does from the code, the database and its users.
Our system is too risky to change
Every change breaks something? The answer is stages, not a leap: modernised alongside the live system, tested in staging first.
Should we replace or modernise our system?
Keep, modernise in stages, or replace? The six questions we put to an ageing system, and why the hard part is already paid for.
Our AI-built app has stalled
Built most of an app in Lovable, Replit, Cursor or Bubble and it stalled? What's recoverable, what isn't, and how we take one over.
What the first days establish in each situation
| Situation | Established first | Usual route |
|---|---|---|
| No documentation | What the system does, from the code, the database and its users, written down with the dependencies | Stabilise, then modernise in stages |
| Too risky to change | A test environment and the map of what depends on what, so a change can be tried without touching live | Small safe changes, then stages |
| Replace or modernise | The six questions: what is sound, what is not, what the data is worth, what the business needs next | Keep, modernise or replace, each priced as a fixed number |
| Stalled AI-built app | What the platform exports, what is missing underneath, whether the data model holds | Finish on your own technology, or rebuild from the screens |
Each row is the assessment's output for that situation, and each page shows what the report contains.
Questions
What people ask before they book.
What if our situation is more than one of these?
That is the usual case. An undocumented system is often the one nobody dares change. Start from whichever page matches today, and the assessment covers the whole system regardless.
Do we need to know what the system is built in?
No. Knowing helps, and the technology pages go into the detail for each stack, but the first days of the assessment establish it if nobody is sure.
What if the system is fine and we just need someone to look after it?
Then the answer is support rather than modernisation: stabilised first, then a care plan. The legacy software support page covers it.
Where do we start?
A free one-hour consultation, online or by phone, about your system. From there we size the assessment, from £395 + VAT, and give you an exact price before you commit.
Start with a free consultation
An hour on your system, online or by phone. From there we size the assessment, from £395 + VAT, and give you an exact price before you commit.
Want the numbers first? See how pricing works.
Written by Marc Allington, founder. .