I'm an independent principal engineer and technical partner based outside London. Fifteen years of shipping production systems for fintech, SaaS, and agencies — hired when teams need someone senior enough to make the architectural calls, hands-on enough to ship the code, and around long enough to live with the consequences.
Most engagements fall into one of these. The boundaries are loose, and one often turns into another over a few years.
Greenfield Rails & React with the architecture, API, and admin surface set up to last beyond the first year. The boring foundations that decide whether the next two years are easy or expensive.
Triage the structural problems holding the team back, fix the things that matter, and hand back a codebase the next developer wants to inherit. Often inherited from another team, often the reason the roadmap stalled.
Get the API, OAuth, SDKs and integration surface to a level where partners, scale, and agents can actually rely on it. The work most platforms skip until it's expensive to fix.
A handful of the clients and products I've spent meaningful time on. Happy to walk you through what shipped, what we learned, and what I'd do differently.
Cloud access control for offices and shared spaces — Rails platform, native mobile, hardware integrations.
Cross-border payments and FX API powering fintechs and businesses worldwide.
Engineering across the agency's roster of client products and platforms.
SaaS I'm building for freelancers — to understand and plan their businesses. Live and in active development.
Long-form essays on the architectural decisions that compound — for better or worse — over the lifetime of a software business.
Why the next era of software integration isn't about agents, aggregators, or APIs — it's about systems that can prove they agree.
Read the essayI've spent fifteen years on the boring foundations most platforms skip — proper REST, proper OAuth, sandboxes that actually work, SDKs that developers can use without reading source code. I'm hired when those foundations matter, when the cost of getting them wrong compounds, or when a team has hit a structural ceiling that more developers won't fix.
I work the way I'd want a partner of mine to work: opinionated about the foundations, direct about what's wrong, and disciplined enough to run my own work through specs and sign-offs rather than wing it. The relationship is the product as much as the code is — most of my clients have worked with me for years, not weeks.
If you want a sense of how I think, read the essay. If you want to know whether I'm the right fit for what you're working on, drop me an email.
Tell me what you're working on. I'll respond honestly about whether I'm the right fit, how I'd approach it, and what the next step would look like — usually within a day.
[email protected]