What I Do
Four types of engagement. Each one designed around a specific situation where an experienced engineer makes the difference.
Product MVPs
Got an idea to test? Most agencies will quote you six months and a five-figure sum to find out if your idea works. I ship working MVPs in weeks not months — enough to test with real users, attract investment, or prove the concept internally.
Good fit for: Founders, product owners, and innovation teams who need something real in their hands fast.
Discuss Your MVP →What this looks like
- Tightly scoped — only what's needed to test the core assumption
- Fixed price agreed upfront before any work begins
- Direct communication throughout — milestone deliveries
- Delivered with documentation so you can hand it to a team or extend it yourself
- Ecommerce, SaaS, internal tooling, marketplace integrations — all in scope
Modernisations & Rescues
Legacy systems don't fail suddenly — they slow you down gradually until every change is painful and every new feature takes longer than it should. I find what actually matters, cut what doesn't, and ship the change that unblocks you — without rewriting everything.
Good fit for: Businesses running on systems that are 5+ years old, built by people who've moved on, or impossible to change without breaking something.
Discuss Your System →What this looks like
- Assessment of the existing system — what's holding you back and why
- Clear recommendation: modernise, migrate, replace, or leave alone
- Phased delivery — improvements ship while the business keeps running
- No "big bang" rewrites unless they're genuinely the right call
- Handover to your internal team or ongoing support retainer
Founding CTO
You're building a software business. You have the idea, the market knowledge, and the drive — but no technical co-founder. Hiring a CTO too early is expensive and risky. I do the founding-CTO work: architecture decisions, first product, hiring brief, and the early technical team — then transition out cleanly when you're ready to bring someone in-house.
Good fit for: Non-technical founders and companies that need technical leadership without a permanent hire.
Discuss Your Business →What this looks like
- Technical architecture and stack decisions
- First product built to a standard that supports future scale
- Hiring strategy and technical interview support for your first engineers
- Engineering processes and standards established from day one
- Clean transition — documentation, handover, and support through the changeover
Strategic Technical Advisory
A decision your business depends on — build vs. buy, vendor evaluation, technical due diligence on an acquisition, an architecture choice with long-term consequences. Sometimes you just need an experienced engineer to test the thinking, with no stake in the outcome.
Good fit for: CTOs, founders, and boards who need an independent experienced perspective before making a significant technical commitment.
Discuss Your Decision →What this looks like
- Build vs. buy analysis with a clear recommendation and rationale
- Vendor and platform evaluation — cut through sales pitches with technical scrutiny
- Technical due diligence for investment or acquisition decisions
- Architecture and scaling reviews
- Delivered as a written report, a working session, or both — shaped to fit the decision and your timeline