Working together
What do you need help with?
Choose the closest match. Each service explains how we start and what you will get.
Build a focused first version.
For a customer portal, an internal tool or a product you need to put in front of users.
How we start
Choose one complete user journey, check the dependencies and agree what the first release must do.
When spreadsheets, emails or disconnected tools no longer fit, I help turn one important workflow into working web or mobile software.
What you walk away with
A working release, an agreed way to judge it, and a clear handover.
- A scope with a clear purpose and boundaries
- Working software in your environment
- Source code, release notes and ownership explained
Launched product
How starting smaller saved the client thousandsA free 30 minute conversation to explore the next step.
Get a stalled project moving.
For a release that will not ship, unreliable software or a codebase your team has inherited.
How we start
Start with a defined review of the failing journey, the relevant code and the release setup.
I investigate the code and release process around the problem, then set out what needs fixing and in what order.
What you walk away with
A prioritised plan with clear acceptance criteria. Implementation is an agreed next stage, not an assumed part of the audit.
- What is blocking progress and the evidence behind it
- Risks and recommended changes in priority order
- A scope your team or I can use for the next stage
Completed assessment
What the completed iOS audit deliveredA free 30 minute conversation to explore the next step.
Add AI where it earns its place.
For a repetitive task, such as finding information, drafting routine text or sorting incoming requests.
How we start
Agree one task to assess, the data it may use and how a useful result would be judged.
Start with the task and examples of real inputs. I help assess whether AI is useful, what can go wrong and where a person still needs to make the decision.
What you walk away with
A recommendation on whether to proceed and what to test. Any prototype or integration is scoped separately.
- A defined use case and the data it needs
- Checks for reliability, running costs and human oversight
- A proposed scope for the next step, if justified
Related engineering experience
Software QA on the Mayflower Autonomous ShipA free 30 minute conversation to explore the next step.
An ongoing
development partner.
For software already in use, with fixes, improvements and recurring work to manage.
How we start
Review the system, access and current priorities before agreeing an ongoing commitment.
Work with someone who knows your software and business, helps prioritise improvements and carries them through.
What you walk away with
A defined support arrangement, agreed priorities and continuity from someone who understands the code and the business context.
- The work covered and the capacity available for it
- Support hours, response expectations and how urgent issues are handled
- Agreed documentation, access and handover requirements
Continuing client relationship
How one client chose a retainerA free 30 minute conversation to explore the next step.
Project fit
Start with one useful piece of work.
For businesses and product teams that want hands on engineering with a clear scope.
Send me your brief- Starting small
- A focused software review, a defined improvement or a first release. You do not have to commit to a full rebuild.
- Working together
- Work directly with me, independently or alongside your existing developers. We agree responsibilities and how to review progress.
- Budget and timing
- Share any budget range and target date. We confirm capacity, scope, price and a start date before you commit. If there are technical unknowns, the first proposal can be for a review rather than a full build.
A straightforward process
You always know
what happens next.
- 01
Talk it through.
Understand the problem, the constraints and what a useful outcome would look like.
- 02
Agree the first paid step.
A written scope, deliverables, price and start date. That might be a review, a discovery stage or a defined build, without committing to every later stage.
- 03
Do the work.
Review progress against the agreed outcome, with clear communication and a practical handover.
Before we start
A few practical questions.
What would I pay for first?
The first thirty minute conversation is free. After that, we agree a paid piece of work with a clear output: a review and plan, a discovery stage to resolve unknowns, or a defined build. You can decide on any further work separately.
Can you work with my existing developer or team?
Yes. Before I join, we agree responsibilities, code access, who reviews changes and who handles releases. We also confirm working overlap, communication and how progress will be reviewed, so the work fits your team.
Can you help with an urgent problem?
Send the problem, its impact and the date you need help by. We need to confirm availability and the access required before agreeing a start date or committing to the work.
How do you price the work?
Against an agreed scope and deliverables. Share the outcome, current setup, target date and any budget range. If unknowns make a build estimate unreliable, we can scope a smaller investigation first. Further work is priced and agreed separately.
Who owns the code and accounts?
Ownership, access and handover are made explicit in the agreement. You should understand where your code and data live, who controls the accounts and how the software is released.
What happens if you are unavailable?
For ongoing support, we agree covered hours, response expectations, escalation and arrangements for planned absence. Documentation and handover requirements are agreed too. Any additional cover needs to be explicitly arranged.
Talk directly to the engineer
Let’s talk about
your project.
Share what the software needs to do, what is already in place and any deadline. We can talk it through, or you can send a brief.
We agree the scope, deliverables and price before any work begins.