Insights

What I’ve learned building the things on this site.

Decisions, trade-offs and the occasional thing that didn’t work. Written from engagements and from running a business that depends on the software I build for it, rather than from a keyword list.

Fractional CTO or interim CTO: two jobs that share a title

One is a day or two a week for as long as it's useful. The other is a full-time seat with an end date. Which you need depends on whether the chair is empty or the decisions are.

Read it

Running AI locally when the data cannot leave

A refused cloud AI request is a constraint on one stage of the pipeline, not the end of the project. How I run private AI in my own business, and how to work out what yours needs.

Read it

What belongs in a technical due diligence report

The report is for the person signing, and most are written for the engineers. The seven things it has to answer, and how to tell a useful one from a long one.

Read it

Why an AI pilot stalls before production

The pilot worked and nothing shipped. Five reasons that happens, all of them visible before the pilot started, and what to agree on day one so yours is not the next.

Read it

When a database query beats a language model

A good deal of what gets specified as AI is a query nobody wrote. How to tell the difference before you pay for the expensive version.

Read it

Where AI automation pays, and where it does not

Most things sold as AI problems are process problems with a model bolted on. The test I use, the shapes of work where the economics change, and why picking the right technique matters more than picking the model.

Read it

When should a founder hire a CTO?

Later than you think and earlier than you want. Five signals that the technical decisions have outgrown the person currently making them.

Read it

Work with me

Working on something like this?

If one of these is the problem you’re having, that’s a good place to start a conversation.