Understand the work before choosing technology
First, understand who receives an enquiry, where it lives, which decisions people make and what happens when something unusual occurs. A real example reveals unnecessary work more clearly than a diagram filled with fashionable terminology. We then separate useful automation from decisions that need people. This avoids wrapping an old, confusing process in a new interface and identifies a first improvement that genuinely helps the team.
A first release should complete a real task
A release can be small, but a user should be able to complete the selected journey: provide information, get a result and know the next step. A milestone includes rules, notifications, error handling and outcome checks, not just screens. An enquiry workflow might assign an owner and track the response deadline, for example. That is an illustrative scenario, not an invented client story or a claim that every business needs identical automation.
Deliver something your business can build on
Agree on a working release, source code, operating instructions, deployment steps and a list of connected services. Decide who manages access, updates and support after launch. The estimate follows a discussion of the workflow and project boundaries; further improvements can become separate milestones. A system should not depend on one developer’s memory. Your team needs to know how to use it, where to seek help and what needs regular attention.
- A clear workflow
- A working milestone
- Documentation and handover
Two useful questions
Do we need to replace everything that already works?
No. We assess the existing system first. An integration or small module may be more useful than a full replacement, depending on the project’s condition and your needs.
Can we start without a formal specification?
Yes. Explain the problem and show a few real workflows. If the task needs more definition, we can agree on a discovery and planning stage first.