Blog
What we have learned building systems that have to keep running.
Notes on scoping, budgeting, choosing a partner and the part most projects leave out. No case studies, because we would rather write something you can check.
All posts
Budgeting
What does a custom ERP system actually cost?
There is no price list, and a figure offered in the first ten minutes is a quote for a different project to the one you have. Here is what the number is actually made of.
8 min read
Decisions
Custom software vs off-the-shelf: how to actually decide
The honest answer is usually neither, and the interesting question is not which to buy but which parts of your operation deserve which treatment.
7 min read
Delivery
Why ERP implementations fail, and what going well looks like
The code is almost never the problem. The decisions made in the first month, usually by people who were not in the room, are.
8 min read
Practical
How to write a software scope that two engineers would build the same way
Most documents called a scope are a proposal in a suit. The difference is simple to state and uncomfortable to apply: a scope records decisions somebody has already made.
9 min read
Procurement
Five questions to ask a software vendor before you sign
Price is the easiest thing to compare and the least informative. These five are harder to answer and tell you far more.
7 min read
Operations
Post-launch software support: what it is, and what 99.9% uptime hides
Most software does not fail at launch. It fails eleven months later, quietly, while everyone who built it is somewhere else.
8 min read
Working through one of these decisions?
Tell us how the work runs today and where it stalls. That conversation is usually enough to say whether we are the right partner for it — and it is free either way.