Skip to content

Topic · 14 articles

Decide & scope

Most software projects that fail were not badly built. They were badly chosen. A custom system for a process two people run, a rewrite of a platform nobody wants to own, a vendor selected on a polished demo, a fixed-price contract signed before anyone understood the requirements — each of those is a cost that no amount of engineering skill recovers.

This is where the expensive, hard-to-reverse decisions live. What should exist at all. Whether to buy, build, hire or borrow. Which architecture you can still operate in three years. What the work is worth paying for, and what a credible proposal looks like. These articles are written for the person who signs the decision, not for someone collecting frameworks.

Each piece names the trade-off, says when the advice is wrong, and gives you a way to test your own answer before you commit budget. Where a number is involved — cost, timeline, team size — we explain what it depends on rather than quoting a figure that would not survive contact with your context.

Start with build vs buy if the question is still open, how to choose a partner if you have decided to buy, and signs you need custom software if you are not sure software is the answer at all. If you want a second read on a live decision, that is the work we do.

All articles in this topic

Need help with a decision in this area?

Tell us what you are weighing up. We will share how we frame the trade-offs and what evidence we would need.

Email is the best way to reach us.