From the first sketch
Marketing sites and landing pages
Problem
The site exists, but it is slow to load, doesn't explain what the company does and gives the visitor no clear next step.
Solution
A lean, fast site that reads well on a phone, with the message organised around the action you want people to take.
Possible deliverables
- Page structure and organised copy
- Responsive, accessible implementation
- Performance work and technical SEO
- Deployment and domain setup
Web applications
Problem
The operation runs on spreadsheets or on a system that no longer matches the process, and every exception turns into manual work.
Solution
A tailored application with your business rules inside the system and screens designed for the people using it every day.
Possible deliverables
- Data modelling and business rules
- Web interface with authentication and permissions
- Reporting and admin screens
- Supporting technical documentation
Mobile apps
Problem
Your users are on their phones, but the current experience is a reduced version of the website, with friction at every step.
Solution
A React Native app for iOS and Android, built for one-handed use and for the connection your users actually have.
Possible deliverables
- App for iOS and Android
- Integration with your existing APIs
- Store submission preparation
- Adjustments after the first real usage
APIs and integrations
Problem
Two or more systems hold the same information and someone has to copy data from one to the other by hand.
Solution
An integration layer that moves data between systems predictably, with a record of what went through and what failed.
Possible deliverables
- Documented REST or GraphQL API
- Third-party service integration
- Synchronisation and data migration routines
- Error monitoring
Maintenance and system evolution
Problem
The system works, but nobody touches it with confidence any more — and every small change feels like a risk.
Solution
I take on the existing codebase, make the environment understandable, and move the product forward in safe steps.
Possible deliverables
- Review and diagnosis of the current code
- Bug fixes and dependency updates
- Performance improvements
- New features in continuous delivery
How it works
- 01
Understand
What the problem is, who uses it and what has to change.
- 02
Plan
Scope, priorities and the technical decisions ahead.
- 03
Build
Implementation in usable pieces, not in one leap.
- 04
Validate
Testing, review and adjustment with the product in front of you.
- 05
Deliver
Deployment, follow-up and evolution of what went live.