A business owner rarely needs “an app”. They need fewer lost orders, faster dispatch, or one true number for stock. When a project starts with a feature list, it is easy to build every feature and still not fix the problem.
1. Write the problem in one sentence
“We lose enquiries because follow-ups depend on memory.” “Stock in the system never matches the floor.” If you cannot write it in one sentence, the project is not ready to quote.
2. Decide what “solved” looks like
Pick something you can see: every enquiry has a next step and a date; the stock report matches the physical count at month-end. This becomes the test the software must pass.
3. Walk the process as it really runs
Sit with the people who do the work. The real process always has steps nobody wrote down, such as the WhatsApp group where approvals actually happen. Software that ignores them gets ignored in return.
4. Build the smallest version that solves it
Separate what must work on day one from what can wait. A small version in use beats a large version on a plan.
5. Only now, choose the technology
Custom software, a ready product, WhatsApp automation, AI, or a mix: the right answer follows from the problem, not the other way round.
This is how every ESSENSE engagement starts: a business management expert understands the problem first, and the technology team builds the answer.
Talk to us
Tell us about your business and we will map out a practical path, with a written quotation before any work begins.
Related answers
Have a business problem like this?
Tell us about it and our experts will recommend a practical solution, with a written quotation before any work begins.