I build products with founders, from first scope to launch.
Most software goes wrong in the first few decisions. I work with founders to get those right, then stay with the build until it holds up.
- COR Health
- Avea
- SiPhox Health
It starts with your business, not the build.
Whether you come with an idea, a spec or a build that has stalled, we start in the same place: what you are trying to achieve.
- Before anything
Understand the business
What you are trying to achieve, who it is for and what success looks like. The goals come before the feature list.
- Before the build
Decide what to build, and in what order
Then we agree the scope, the phases and an honest estimate. The hard questions get asked here, while there are still options.
- During the build
Build it with the right people
My team builds it, and you always know where things stand. No one should have to chase for an update.
- After launch
Stay with it after launch
Products change once real people use them. We stay involved, so what we built keeps holding up.
How I work with founders and their teams.
You work with me throughout. Behind me is Code Pros, the engineering company I founded in 2017, whose senior engineers bring the technical depth: web platforms, connected devices, data and AI.
Understand the problem beneath the request
The feature someone asks for is not always what they need. Some of the most valuable work happens before any code is written.
Raise hard questions while there are still options
I would rather surface an uncomfortable constraint early than let it become an expensive surprise.
Use technology for a reason
The newest architecture is not automatically the right one. Cost, team capability, maintenance, product lifetime and operational load all count.
Communicate before anyone has to chase
Clients should never have to ask where something stands. When circumstances change, the communication should change with them.
Give people clarity and credit
I bring the context and the technical view. My team brings its own judgement and expertise, and the credit is shared.
Decide with you, not for you
You hear the options, the trade-offs and my recommendation. Every major call is one you understand and agree with.
What you can count on.
How working with me worksYou’ll hear from me every week.
What’s done, what’s next, and anything that needs your decision.
You’ll get a reply within a working day.
Usually much sooner, whatever time zone you’re in.
You deal with me.
One point of contact, from the first call to long after launch.
If something breaks, we respond straight away, whatever the hour.
Then we decide together how fast it needs fixing, based on how serious it is.
Founders I’ve built with.
How each project started, the decisions we made, and what happened.
What founders say about working with me.
All recommendationsRequests get handled quickly, problems get solved without fuss, and I have never had to chase him on anything.
High quality, on-time, on-budget. They have the highest quality project management. Low friction
Notes for founders.
All writing- EstimatesWhat to prepare before asking for a software estimateA good estimate starts with a good brief. Here is what to have ready, what you do not need, and how to tell a real estimate from a guess.
- Stalled buildsWhat to check before replacing your development teamSwitching teams can rescue a product or set it back months. Before you move, find out what you actually have, what went wrong and what the new team will inherit.
- Choosing a partnerHow to choose a development partner for your first productMost guides compare portfolios, tech stacks and prices. The things that decide how it goes show up before you sign, if you know where to look.
Building something?
A 20-minute call, no preparation needed. Tell me what you are trying to achieve and where things stand.
Book a 20-minute call