Product development
More of your roadmap.In customers’ hands.
A customer needs an integration. A feature is ready for design but waiting on engineering. An internal tool keeps losing its place in the queue. I take a defined piece of that work from the first product decision through release, with agents supporting research, implementation and testing.
AI agent
Talk product delivery with my AI agent.
Ask how I scope a release, work with your engineers and use agents from brief to production.
Three conversations a day. Two minutes with my AI agent on Google Gemini. No sign-up. How it’s handled
Alongside 100+ client engagements.
A few teams I’ve worked with:
The approach
The work starts with what needs to change for the person using the product. We look at the existing system, the decisions already made and the dependencies that could hold up a release. That gives us a scope your team can review and a useful first version to aim for.
I own the product decisions and engineering within that scope. Agents work from bounded briefs, with the relevant code, constraints and checks. I review what comes back, integrate the changes and verify the release in the environment where it will be used.
Your team sees working progress and makes the decisions that need its input. The code, tests and operating notes stay in your accounts, so the people maintaining the product can take it forward.
What gets built
Work we can take on together.
A feature customers can use
Take a roadmap priority through the user flow, interface, implementation and release checks.
An integration that removes a gap
Connect the systems behind a customer requirement, including authentication, failure handling and the operational handover.
An internal tool that gets used
Replace a repeated workaround with a tool built around the team’s actual process and permissions.
A prototype ready for real users
Review what already works, identify the production gaps and scope the engineering needed to release it.
How I work
From the first decision to handover.
Agree the first useful release
Define the user, the business priority, acceptance criteria and the decisions your team needs to make. Check dependencies before agreeing a fee and timeline.
Build in reviewable pieces
I work in your stack and repository. Agents take bounded implementation and testing tasks; I review the changes and bring you working progress.
Check the actual release
Run the relevant tests, review the user journey and verify the deployed change. A successful build alone is not the acceptance check.
Leave it ready to maintain
Hand over the code, tests, deployment notes and operating instructions. Agree who owns support and any further work.
Recent client projects
See the work in use.
Recent client projects across property software and ecommerce. The build accounts below describe the decisions and implementation behind other releases in more detail.
The work in detail
Read the decisions behind it.
- Project notes and methods
Rebuilding Benson with agents
How I organised the specifications, implementation and launch of a SaaS product.
Read the account → - Project notes and methods
From a prototype to production
The engineering decisions between a working demonstration and a product people can rely on.
Read the account →
Ways to work together
Choose a scope that fits the work.
A working session, a defined release or ongoing delivery. We agree the responsibilities, dependencies and fee before starting.
Common questions
Working together.
Scope, responsibilities and what happens after the release.
Contact meI work in your existing stack, repository and review process. We agree the boundaries of the project, who makes product decisions and how changes reach production. Your team can review working progress throughout.
Agents help with research, implementation and checks against a written brief. I choose and scope the work, review their output, integrate the changes and take responsibility for delivery. Your team keeps the approvals we agree at the start.
We can look for work that can run in parallel and decisions or dependencies that are slowing delivery. The amount we can bring forward depends on your product, team and release process. We scope a first release before committing to a timeline.
The code, tests and documentation stay with you. We agree the handover, operating costs and support arrangements before starting. Further features are scoped separately or included in an ongoing partnership.
Discuss your priorities
What needs to change for your team?
Bring the problem, the existing setup and the decisions you have already made. We can work through the next useful step on a free 30-minute call.
Other areas of work