A supplier you cannot take over from
They built it, and you are not confident you could run or change it without them. Renewal is coming.
Software rescue and takeover, UKBook the exploratory call
Software project rescue. Take over the software you cannot run.
A supplier built your software. Renewal is coming, and nobody in the building can run or change it without them. Or your agency has gone silent. Or your AI-built first version broke on the second customer.
After a free thirty-minute call, the work starts with a paid code read: keep, repair or rebuild. Simon Piscitelli, technology director and founder of PIMASI, owns the judgement and the plan to take control.
01 · Who it is for
You need control of the software your business depends on.
A launch nobody senior owns
Most of it works, but you need someone senior enough to own the last mile and actually launch it. The demo works. You need to know it is ready for real customers.
Moving the work in-house
The agency got you here. Now you need to own the capability yourself without stopping delivery.
02 · What rescue involves
Read it. Stabilise it. Put you in control.
Keep, repair or rebuild
A paid code read comes first, inside the two-week discovery. Simon reads the code, checks access and ownership, and gives you a recommendation before more work starts.
Stabilise in weeks
The plan sets the work, the sequence and the time to stabilise. Simon owns the technical calls and the delivery date.
Run it or hand it over
PIMASI runs the software by the month, or hands it to your own people with the documentation to run and change it. The plan says which.
03 · How it starts
A call, a code read, a plan and a price.
- 01
The exploratory call
Free. Thirty minutes.
Bring the software, the supplier situation and the date in front of you. Simon decides with you whether a two-week discovery is the right next step.
- 02
A two-week discovery
Fixed fee, agreed on the call.
The code read is the first part. You get a plan you keep whether or not PIMASI does the work, and a price for the path it recommends.
- The verdict: keep, repair or rebuild
- Access and ownership checks
- Scope, estimate and architecture
- Team shape and costed milestones
- A price for the path it recommends
- 03
The engagement
The discovery fee is credited in full.
The plan names the work and who does it: Simon himself, or a team under his management. You know who owns the scope, the sequence, the quality and the date.
If your decision is already made, we start with a scoped proposal.
04 · Who does the work
Simon's judgement. A team when the work needs one.
When the code read is the whole job, Simon does it himself. He also leads the stabilisation and works with your own engineers or the supplier's team.
When the work needs a team, you get engineers sourced and managed by PIMASI, embedded in your processes or run as a separate function. Simon owns the scope, the sequence, the quality and the date. The team always comes with him.
05 · Proof
Simon's work with teams that needed a turnaround.
A product the founder could demo again
Simon fixed the engine with the founder's team. In under two months, the founder went from avoiding the codebase to demoing it to customers.
A late project with outside capacity under Simon
A 27-engineer project about a year behind schedule. As interim engineering director, Simon brought in an outside engineering company and specialists under him. Inside four months it shipped on the date the business had set.
06 · Code and ownership
Your business must be able to run its own software.
Yours, always. On a project, PIMASI hands over the code and the accounts on the final payment. With a team by the month, what they build is yours in real time. The discovery lists what your business needs to run and change its own software.
07 · Not a fit
The work comes with an accountable owner.
The cheapest hands, a team without Simon, or a rebuild with nobody accountable are not a fit for PIMASI.
Questions we get asked
Frequently asked
Can you work with our current supplier?
Yes. Simon works with your own engineers or a supplier's team. The code read checks the software, access and ownership, then the plan states what stays with the supplier and what needs to transfer.
What if the code read says rebuild?
The plan gives the reasons, the scope, the sequence, the team shape and costed milestones, with a price for the path it recommends. You keep that plan whether or not PIMASI builds it.
How long does it take to stabilise the software?
Weeks, set in the plan. The code read establishes the state of the software and what needs to change. The discovery sets the stabilisation work and its date.
Who owns the code and accounts?
Yours, always. On a project, PIMASI hands over the code and the accounts on the final payment. With a team by the month, what they build is yours in real time. The discovery lists what your business needs to run and change its own software.
What if the discovery says do not touch it?
Then the plan says so, in writing, with the reasons. You keep the findings whether or not PIMASI does any further work.
Bring the software you need to take control of.
A free thirty-minute call with Simon. Bring the supplier situation, the launch or the handover. We decide whether a two-week discovery is the right next step.