Insights from the delivery floor

Written by the people who actually build and support these systems. No vendor spin, and no article that ends by telling you the answer is always more software.

Featured

Build or buy? A decision framework for ERP that survives contact with reality

Most ERP failures are not technical. They happen because the decision to customise a package or build from scratch was made on price alone, before anyone mapped how the business actually works. Here is the framework we use with clients — five questions, in order, and what each answer rules out.

Read the article

The cloud migration checklist nobody sends you before the invoice

Right-sizing, reserved capacity, egress charges and the scheduled job that quietly costs more than the servers. What to check before you migrate, and what to check ninety days after.

Read more

Where AI actually pays for itself in a mid-sized business

Four automation patterns with a genuine payback period — and three popular ones that mostly generate impressive demos and disappointing quarterly reviews.

Read more

Seven security defaults every business application should ship with

Role-based access, audit logging, secret management, dependency scanning and three more — all cheap on day one, all expensive to retrofit in year three.

Read more

Native or cross-platform? Answer these four questions first

Flutter and React Native have closed most of the gap — but not all of it. The specific cases where native still wins, and how to decide without relitigating it every sprint.

Read more

Why the full rewrite is almost never the cheapest option

The strangler pattern explained without jargon, using a fifteen-year-old VB6 inventory system that is still running today — one module at a time.

Read more

The user adoption problem is a design problem

Staff do not resist new systems out of stubbornness. They resist systems that make their day harder. What we changed in our process after one rollout went badly.

Read more

Designing APIs other teams will not curse you for

Versioning, pagination, error shapes, idempotency and rate limits — the five decisions that determine whether your API is a pleasure or a support burden.

Read more

Your dashboard has too many numbers on it

How to cut an MIS screen down to the six metrics management will actually act on — and where to put everything else so nobody feels it was lost.

Read more

What belongs in an MVP, and what is just expensive optimism

A practical scoping method for founders: how to reach something credible in ten weeks without building an architecture you will have to throw away at scale.

Read more

New articles are published roughly twice a month. Subscribe in the footer to get them by email.

Discuss

Facing one of these problems right now?

Articles only go so far. A 30-minute call with an engineer will get you further than a week of research.