Your long-term software partner, from architecture to shipped product.
For founders and teams who need a senior developer embedded in the work rather than a contractor delivering a spec, and for companies with an existing product that needs someone who'll still be around in six months.
Handovers are where projects go wrong. The build finishes, the developer leaves, and three months later nobody knows why a decision was made or how to change it. Working as a partner means the context stays with the project.
Ongoing development across frontend, backend and AI. Architecture decisions made with you and written down. Regular shipping instead of big reveals. Code review and technical direction if you have other developers. Someone who tells you when something is a bad idea before it's built.
We agree a working rhythm, usually a set number of days or hours a week, and a way of prioritising that fits how you already work. You get regular updates without chasing me, and I'm available for the decisions that come up between them.
A clear enough sense of direction that we're not rebuilding every month. One person who can make calls. Honest conversations when priorities change.
Get a build plan