Oct 8, 2026 · 4 min read
Define the problem before you define the software
The most expensive software is the kind that solves the wrong problem well. A few questions that save months of rework.
Draft article. Replace with NUMO's own published piece before launch.
Most software projects begin with a feature list. The list feels concrete, so it gets priced, scheduled and built. Months later the team discovers the list described a solution to a problem nobody had fully named.
Start with the business outcome
Before any screen is drawn, we ask what should be different in the business once the software exists. Fewer manual steps? Faster orders? A new revenue line? The answer becomes the measure every later decision is checked against.
Questions worth answering first
- Who will use this every day, and what do they do today instead?
- What does a bad outcome cost, and how often does it happen now?
- Which existing systems does this depend on, and who owns them?
- What is the smallest version that would prove the idea is worth more investment?
Why this matters more with AI
AI makes it cheaper to build software, which makes it easier to build the wrong thing quickly. Clear thinking at the start is the part that technology cannot do for you, and it is where most wasted budget is saved.