Business & Software · 04 Nov 2026
Custom software can organise a difficult process. It can also make an unclear process harder to change. If a team cannot explain who makes a decision, which information is required or what happens when something goes wrong, the first deliverable should be a shared workflow rather than a screen design.
Follow one real piece of work
Choose an ordinary request and trace it from arrival to completion. Record each handover, spreadsheet, approval and message. Ask the people doing the work to explain the exceptions: incomplete forms, absent approvers, duplicate records and urgent requests. Use anonymised examples where information is sensitive.
The GOV.UK Service Manual’s discovery guidance emphasises understanding the problem, users and constraints before building. This is useful beyond government: it encourages a team to question whether the proposed software addresses the underlying need.
Create a one-page decision brief
- Problem: describe the delay or error in observable terms.
- People: identify who submits, checks, approves and receives the outcome.
- Information: name the records and systems each step needs.
- Exceptions: explain what happens when normal conditions fail.
- Ownership: appoint someone to resolve process questions.
- Measure: decide how you will recognise an improvement.
Compare alternatives honestly
A clearer form, a changed approval rule or configuration of an existing tool may solve part of the problem. Compare those options with a custom build using the same criteria: integration, user effort, ongoing cost, security and flexibility. Custom software is most compelling when the workflow or integration need meaningfully differs from what an existing product supports.
Start with a complete, narrow slice
An illustrative first release might support one request type from submission to approval, including rejection and correction. That provides a usable journey to test. Ten disconnected screens provide less evidence about whether the process works.
Review the prototype with frontline users as well as management. Ask them to complete a task without coaching, and record where they hesitate. Use those findings to revise the brief before expanding scope.
Takeaway: bring a workflow map, a list of exceptions and an accountable decision-maker to the first development discussion. Those inputs help business consulting and software delivery work towards the same outcome.
Topics: Custom software, Business consulting
Sign in to comment or rate this insight.
Back to insights