Technical decisions you can defend, without a full-time CTO.

Architecture calls, technical hiring, vendor oversight and roadmap sequencing, from people who have shipped and then maintained the kind of product you are building.

Start a project See the work

This is for you if

You are making architecture decisions nobody in the room has made before.
You need to hire engineers and have no one who can judge the candidates.
A board or an investor is asking technical questions you would rather answer properly.
You have an agency or a vendor to manage and nobody who can check their work.

And it is not, if

If you already have a strong engineering lead, you do not need this. What you probably need is capacity, and ongoing engineering covers that. We will tell you which one you are rather than selling you the more expensive answer.

What you actually receive

A standing seat in your technical decisions

Regular sessions with you or your product lead, plus availability between them for the calls that cannot wait a fortnight.

Architecture decisions, written down

What we chose, what we rejected and why. The reasoning has to survive the engagement, or you are buying it again next year.

Technical hiring you can trust

Role definitions, interview and take-home design, and a second opinion in your loop so you are not judging engineers on instinct.

Vendor and agency oversight

Someone who can read the contract, the estimate and the code, and tell you whether the three of them agree.

How the engagement runs

A rolling engagement sized in days per month rather than a retainer for being reachable, so you can see what you are paying for. Reviewed openly at the end of each cycle. It is meant to end: when you hire the person it was standing in for, we help you pick them and then we step back.

Before you ask

The ones that come up on most first calls.

All the questions

What does a project cost?

We do not publish a number, because a quote written before anyone has looked at your problem is a guess dressed up as a price. We scope first, as a small paid piece of work, and that produces a fixed shape and a real figure. If the scope shows the project is not worth doing, you have spent a fraction of a build to find that out.

How long will it take?

Ask us after the scope, not before. Anyone quoting a duration off a first call is quoting a hope. What we can tell you up front is the shape: releases land continuously against a preview environment you can open, so you are never waiting months to see whether it is going the right way.

Do you work fixed price or time and materials?

Both, depending on what the work actually is. A defined release with an agreed scope can be fixed. Ongoing engineering against a moving roadmap cannot honestly be, and anyone who fixes it is pricing in the risk and charging you for it. We will tell you which one your project is.

We are early and pre-funding. Are we too small?

Possibly, and we will say so. If you are still testing whether anyone wants this, a full build is an expensive way to find out. Tell us where you are and we will tell you what would answer the question faster, even when the answer is not us.

Can you work with our existing team and codebase?

Yes, and most of our work is exactly that. We have joined codebases whose original authors had left and worked alongside in-house teams who needed a discipline they did not have, usually mobile or front end. We read before we rewrite.

Start the conversation

Tell us what you need to ship. You will get a straight answer on whether this is the right engagement for it.

Start a project