Stabilise & modernize
Software Maintenance, Support & Modernization
A stabilised, documented codebase and a plan for keeping it that way — or, at minimum, an honest answer about what state it's actually in.
Who it's for
Owners of a system nobody currently understands
The person who built it is gone, and nobody wants to touch it.
Teams that had a bad experience with a previous vendor
You want an honest assessment, not a sales pitch.
Anyone worried about downtime, data loss or security gaps
You'd rather find out now than after something breaks.
What's included
How we work on this
We start with an audit, not an assumption — a written report of what's actually wrong, what's a real risk, and what can wait, before any fix work begins. We don't spend the report blaming whoever built it before us; we spend it telling you where you stand.
Built with
Every fix ships through version control and a staging environment, even on a legacy codebase.
Indicative pricing
Code audit
€2,500 per project
2–4 weeks
- Full codebase review
- Security & dependency check
- A written report
- No obligation to continue
Support retainer
€1,200 per month
ongoing, 30 days' notice
- Monthly hours for fixes
- Monitoring
- Priority response
- Monthly summary of work
What we commit to
You own the code and the IP.
Everything we build transfers to you on completion and payment — no licensing traps, no dependency on us to keep running your own product.
Senior engineers only.
Every person on your engagement is senior. Nobody junior is billed at a senior rate, and nobody senior pitches the work only to hand it to a team you never meet.
EU-based, GDPR-native.
We operate under Portuguese and EU law, in your timezone, with data handling that's GDPR-compliant by construction, not by afterthought.
A written estimate before we start.
You get a written, fixed-scope estimate before any work begins — not a verbal ballpark, not a moving target.
Stabilising and modernising a legacy retail management system
The system now runs on supported dependencies with a documented codebase, and the client has a written record of what the system does and doesn’t do, instead of institutional guesswork.
Common questions
What exactly do we get from a code audit?
A written report covering the codebase and its dependencies: what's broken, what's a real security or stability risk, what's fine to leave alone, and a prioritised recommendation for what to do next. There's no obligation to continue into a retainer afterward — the audit stands on its own.
Will you tell us if our previous developer did a bad job?
We'll tell you what we find, in plain terms — what's solid, what's fragile, and why. We won't build the report around blaming whoever worked on it before us; most inherited codebases are the result of reasonable decisions made under a deadline, not incompetence, and that framing doesn't help you fix anything.
What happens to our data and access after the engagement ends?
Access we were given to build or maintain your system is handed back or revoked as agreed at handover — we don't retain standing access to a client's production systems once an engagement ends, unless you've asked us to under an active support retainer.
Do your prices include VAT?
No — the published bands are VAT-excluded. Your written estimate will state the applicable VAT treatment for your engagement.
Tell us what you're worried about.
Start with an audit — you'll get a written answer, not a sales pitch.