Build · Hands-on engineering

Software and systems, built by the person who scoped them.

Bespoke products, SaaS platforms and internal systems, designed, built and kept running in production.


What a build engagement covers

A build starts with the commercial problem, and the feature list comes out of that. We agree what the system has to do, and what “working” looks like once it’s live.

Then it’s engineering: architecture, data model, interfaces, integrations, infrastructure and the pipeline that gets it in front of real users and keeps it there.

  • Product design & architecture
  • Full-stack development
  • Desktop, browser-extension and chat clients
  • APIs & integrations
  • Cloud & DevOps
  • AI-enabled features where useful

Typical work

What this looks like in practice

Custom software and SaaS platforms

New products, from first architecture to a running service.

Internal tools and operational systems

Workflow, reporting, back office. The systems a business runs on.

APIs and integrations

Getting your systems to agree.

Clients beyond the browser

Desktop apps, browser extensions and chat tools, all writing to one record.

Cloud infrastructure and DevOps

Environments, pipelines, observability and a sane path to release. I set that up in the first weeks of a build, so the last weeks aren’t about how to deploy it.

AI-enabled features

Language models and automation, where they’re worth it.

Where it starts

The Leverage Diagnostic.
Two weeks, fixed, £7,500.

All prices exclude VAT.

If the brief is still forming, that’s what the fortnight is for, and the risky part gets proved before anyone builds on it. Got one I can build from already? Ask for a quote.

Questions


The things people ask first

How long does a build take?

Six to twelve weeks is the usual shape, and the diagnostic turns it into a number before you commit.

What does a build cost?

It comes from a specification, and either you bring one or the diagnostic produces one: £7,500, and two weeks later you hold a spec and a costing you can bring back to me or take elsewhere.

If the number is bigger than the problem is worth, you found out for £7,500 in a fortnight. Bring a brief I can build from and the quote is free. All prices exclude VAT.

What do you build on?

C# and .NET with MongoDB is where I’m deepest, and it’s what the platforms in the case studies run on. Python where it suits the problem, Avalonia for cross-platform desktop, Azure and local inference for AI.

I’ve shipped relational work too, but document stores are where my depth is. If your data is strongly relational and reporting-heavy, say so early. The right answer might be Postgres and an engineer who lives in it, and I’d sooner tell you that in week one.

Will you work on an existing codebase?

Yes, and I’d say it’s the more valuable job. The first stretch is reading, because I don’t change a system I haven’t understood.

Who owns the code?

You own what you pay me to build, once it’s paid for. Anything I bring that existed before (my own tools, mostly) stays mine and comes with a licence to use and change it as part of your system. The handover includes the system, its infrastructure and enough documentation for another engineer to take it on.

Am I buying a team or a person?

A person: if you need a team of five starting next month, I’m the wrong call.

Other ways to work together

Not quite the right shape?

Work with me

Losing time or money to something you can’t fix?

I reply within one working day to arrange a free 30-minute call.