Back to the main siteFor technical teams

The engineering behind the plain-English pitch.

The main site keeps it simple on purpose. This page is for CTOs, lead developers, and anyone evaluating whether I can actually build: how I architect, where AI earns its place, and the full service detail.

How I build

Principles, not preferences.

The defaults I hold to on every build, whatever the stack.

Clean architecture, documented
Well-defined boundaries, typed end to end, and docs that let another engineer onboard in an afternoon. Clean today means cheap changes tomorrow.
AI where it earns its place
Plain code for deterministic work; models only where they beat it — grounded in your data with retrieval, evaluated, and kept from guessing.
Yours to keep, no lock-in
You own the repo, the infrastructure, and the accounts. No proprietary black boxes — any competent developer can pick it up.
Shipped, not demoed
Accessible, fast, tested, and observable in production. I optimise for the thing still running in a year, not the thing that demos well next week.
01What I do

Software and AI, delivered by the person who builds it.

From a single landing page to the AI infrastructure behind your whole operation. Pick what fits and I'll prefill it on the form — so I know exactly what you need.

GEO optimisation

Get found inside AI answers, not just search results. I structure your content and data so ChatGPT, Gemini, and Perplexity cite you when your customers ask.

Example: Reworked a SaaS site's content and schema so it started turning up in AI answers for its core buying questions.

Landing pages, fully serviced

Design, copywriting, hosting, and maintenance in one pair of hands. A fast, on-brand page that converts — and stays current without you chasing anyone.

Example: Designed, wrote, and now host a product launch page — one point of contact for copy tweaks and uptime.

AI & non-AI automation

Hand the repetitive work to software. I connect your tools and automate the boring steps — with AI where it earns its place, plain code where it doesn't.

Example: Automated invoice intake and follow-ups for a small firm, saving roughly half a day of admin each week.

AI business infrastructure

The foundation that makes AI useful across your business — knowledge bases, retrieval, and the plumbing that keeps models grounded in your own data.

Example: Built a private knowledge base and retrieval layer so a team's assistant answers from their docs instead of guessing.

AI consultancy

A straight second opinion on where AI fits — and where it doesn't. We find the few use cases worth doing and skip the hype that burns budget.

Example: Reviewed a startup's AI roadmap and trimmed it to the two features that actually moved the numbers.

Project management

Someone technical to keep a build on track — scope, timelines, and contractors coordinated, with honest status you can act on.

Example: Ran delivery on a multi-vendor web build, keeping scope and timeline aligned all the way to launch.

Software engineering

Web apps and systems built to last: fast, accessible, documented, and easy to change. Clean architecture today means cheap changes tomorrow.

Example: Shipped a custom client portal on clean, documented architecture the team can extend themselves.

Lead-gen channel development

Build the channels that bring work in — referral systems, outreach, and the tooling behind them — so growth isn't only word of mouth.

Example: Set up a referral and outreach system that gave a consultant a repeatable source of new enquiries.

02What this gets you

Less admin. Systems that hold up.

What working together actually changes — for the business and for the tech behind it.

Your time back
The admin and busywork that eats your week, handled — so your hours go to customers and growth.
Systems that last
Clean, documented, well-defined architecture that scales as you grow — not a demo that breaks in a month.
You stay in the loop
One senior engineer you can reach, honest about trade-offs and cost, with the whole build yours to keep.