31 August 2026 · 4 min read
Most businesses don't have a software problem
Most software projects go wrong before the first line of code, because nobody has written down how the work actually happens.
Most businesses that ask us to build software don't have a software problem. They have a process that nobody has ever written down.
It lives in three people's heads. One of them is on leave. Another one has a spreadsheet with a tab called “final_v3_use_this” and won't explain it.
So when a software company arrives and asks “what do you want the system to do,” the honest answer is: nobody actually knows. Not fully. Not end to end.
And that's the moment most projects quietly go wrong.
The vendor still has to quote something
So they build what they were told, in the order they were told it, and eight months later the business has a system that automates a process that was never the real process.
The fix is unglamorous
Before anyone writes a line of code, someone should sit with the three people who actually do the work and write down every step, including the ugly ones. The WhatsApp approval. The manual correction on Friday afternoon. The register that gets updated by hand because the software doesn't handle that one supplier.
Half the time, that exercise alone finds the problem. And the problem is rarely “we need an app.”
We have walked away at this stage
Not out of virtue. Because building the wrong thing quickly is worse for everyone than building nothing.
If someone is quoting you a price before they have seen how your work actually happens, they are quoting you a guess.
Email [email protected] with the process you want to fix rather than the software you think you need. We will map the real steps with you first and tell you honestly whether code is the answer.