Skip to content

Home / Industries

Where this work earns its keep.

Not a client list. A description of the conditions under which custom software, and the decisions around it, tend to be worth the money.

01 Conditions

Five situations where the arithmetic works.

Custom software is not always the right answer. These are the circumstances in which it usually is, and the reason why in each case.

01

Operations heavy businesses

Distribution, service, field work

The way work moves is specific enough that packaged software forces awkward compromises, and a small gain per job compounds across thousands of them. The case here is arithmetic rather than ambition.

02

Companies outgrowing spreadsheets

Concentration risk

The point where the workbook that ran the business becomes the thing holding it back. Too many hands in it, no history of changes, no controls, and a growing amount of judgement living in one person's head. The risk is concentration as much as inefficiency.

03

Businesses carrying older systems

Rising cost to hold

Software that still works but costs more each year to sustain, or that no remaining member of staff can safely amend. Replacement is never urgent until it is, which is the worst moment to begin. Planning early is most of the saving.

04

Teams taking a product to market

Scope discipline

An idea with real demand behind it and no agreed line between what version one is and what version four might be. Most of the value created here comes from deciding what to leave out and holding that decision under pressure.

05

Companies where systems do not talk

Quiet duplication

Two or three tools that each do their job while somebody enters the same information twice. The integration is usually smaller work than expected and pays back faster than anything else on this list. It is also the easiest thing to keep postponing.

02 The other side of it

When we will tell you not to build.

Worth saying plainly, because it comes up often enough to matter.

Process, not software

The problem is upstream

A fair number of problems arrive framed as software problems and turn out to be agreement problems: two teams with different definitions of the same number, or an approval nobody owns. Software built on top of that makes it more expensive to fix, not less.

Buy, do not build

Something adequate already exists

If the workload is genuinely standard and the vendor market is mature, buying is usually the better answer and we will say so. Custom work earns its cost when the way you operate is the advantage, and not otherwise.

Not sure which of these describes you?

Describe the situation in a paragraph. We will tell you which it is, and whether it is worth doing anything about yet.