If you are considering an operational system for the first time, here is the whole decision in one place, including the parts that usually get discovered late.
Start with the workflow, not the software
Write down how the process actually runs today, including every exception and every “well, except when.” That document is worth more than any vendor demo, because the exceptions are where systems fail.
If you cannot describe the rules, the project is not ready. That is not a criticism, it is the most common finding in scoping, and sorting it out is most of the value.
Decide what stays human
Be explicit about which decisions require judgment and which are just rules being applied. Most organizations want the decision to stay with a person and everything around it handled. Say so up front rather than discovering it in testing.
Know who owns what
Ask any vendor, including us, these questions:
- Who owns the accounts the system runs on?
- Who owns the data, and can I export it in a usable format?
- If I stop paying you, what still works and what stops?
- Who can make changes to the rules, and does that require a support ticket?
The answers should be clear. Anything hedged is a future problem.
Budget the ongoing cost honestly
A system needs maintenance. Platforms update, integrations change, and your business changes what it needs. If there is no budget for that, build something simpler that your team can maintain, because the alternative is an expensive system that drifts out of use.
Plan for partial launch
The projects that stall are waiting on complete information: the full staff list, every rule agreed, all the edge cases resolved. Launch with placeholders where you must. A system running at eighty percent produces value today; a perfect system that launches in nine months does not.
What a good scoping process looks like
It should produce a written map of the workflow, the rules stated explicitly, the integrations named, what is in scope and what is deliberately not, and a real number. It should also tell you honestly if you do not need the thing you asked for.
We charge $2,500 for that and credit it against the build, because scoping done properly takes real work and the worst outcome is building the wrong system efficiently.
Reasonable expectations on timeline
A focused single-workflow build is typically a few weeks once rules are settled. Multi-workflow systems with several integrations take longer. The variable is almost never our speed; it is how fast decisions get made on the client side.
Want to see what this looks like for your business?
Ground Control is our operational systems practice: portals, request and approval workflows, and the integrations that hold them together. Every engagement starts with a paid Blueprint, which is credited against the build if you move forward within 90 days. See how Ground Control works or book a call.