Care plans, testing and second opinions
Get a clear view of existing software, a plan for the next changes and a named person to help maintain it.
You might ask for
- Our developer disappeared
- It keeps breaking after updates
- Is this quote fair
- Are we ready for GDPR or SOC 2
- Review our developer’s work
Who it is for
- Businesses taking over software from a developer or agency
- Teams whose releases or dependency updates keep causing problems
- Owners seeking an independent review before a technical decision
What you get
- A clear account of the system, its risks and the next useful steps
- Checks for the important journeys before changes are released
- Updates and monitoring with a documented recovery path
- Findings your team can use to assess a proposal or plan improvements
Approach
Your developer leaves, an update breaks an important workflow or an agency proposal raises questions you cannot answer. The business still depends on the software, so you need to understand its condition before agreeing to more changes.
We start by reviewing the code, accounts, documentation and the tasks your team needs to complete. We explain the findings in plain language and agree on the most useful next step. The written plan separates immediate repairs, ongoing care and larger changes.
We make the agreed fixes, add checks for important workflows and prepare updates in a test environment. An independent review produces written findings and questions you can take to your developer or supplier. Monitoring and recovery instructions fit the system your team actually runs.
We test the agreed changes and walk your team through the result before handover. Your accounts and code stay yours, and the documentation helps another engineer continue the work. If ongoing care is useful, we agree on what it covers and how new requests are handled.
Deliverables
- A review of the code, accounts and existing operating instructions
- Written findings with priorities and an agreed improvement scope
- The agreed tests, upgrades, fixes or independent review
- Monitoring and recovery instructions for the agreed system
- Documentation and a team walkthrough
Technology
Playwright, Cypress, pytest, Dependabot, Sentry, Uptime monitoring, Backups, OWASP reviews, Framework upgrades, GDPR and SOC 2 readiness
Ways to work together
- Model 01
Roadmap
A one to two week review of your software or proposal, ending in written findings, a scope and a fixed quote for the agreed improvements.
- Model 02
Starter build
One defined repair, upgrade or testing improvement to your existing system, released in two to four weeks.
- Model 03
Care plan
Monitoring, security and dependency updates, backup checks and small improvements each month.
Questions
Can you take over software someone else built?
We first review the code, licenses, account access and operating instructions. Then we explain what can be maintained, what needs repair and any limits before agreeing on the work.
Can you review a quote before we sign it?
Yes. We compare the proposal with your actual requirements and identify unclear scope, dependencies and questions to raise. You get written findings you can use when deciding how to proceed.
Can you help us prepare for GDPR or SOC 2?
We can review the technical controls and evidence in the agreed system and identify engineering work to discuss with your advisers. A readiness review does not certify compliance or replace legal advice or an independent audit.
What does a care plan include?
We agree on the system covered, monitoring, update checks and time for small improvements before the plan starts. You get a reply within one business day, and larger changes are scoped separately in writing.
Start here
Tell me about the work that slows your team down.
A 20-minute call, no obligation. You leave with a written next step whether or not we work together. Plain language is fine; you do not need a technical brief.
Prefer to write? [email protected]
I read every message myself and usually reply within one business day.