Understand the problem
Find when it happens, who it affects and how to reproduce it. Review the parts worth keeping.
Services
Fix the problem. Keep what works.
An existing product may need a defined repair rather than a fresh start. I investigate the problem and propose what can be improved while preserving the useful parts.
From the cause to a checked repair
Agree the change
Define what will be repaired, what stays outside the scope and how the result will be checked.
Repair and test
Check the fix alongside related journeys, then hand over the changes and known remaining limitations.
Indicative budget: €4,000–12,000 for a larger repair project. Scope and timing follow the initial review.
Inspect the work behind the offer.
My own projects show work with native iOS, data and complete user journeys. The work collection describes the implemented behavior and the limits of each example.
These are product and demonstration examples, not separate client repair case studies.
Before we start
What if a repair is not worthwhile?
The initial investigation may show that a repair is not economical. I explain that before proposing a larger build.
Will you change the live system immediately?
Production changes and data access need an agreed scope and permission. The first message should describe the problem without passwords or private customer data.
What is handed over?
The agreed code changes and handover information. Ongoing support and third-party costs are agreed separately.
A useful next step
What would you like to build?
Tell me what you need or what's getting in the way. We can work through the details together.