By Steadnet Cyber · 15 September 2026
Start with the boundaries
Define where information enters the process, which systems change and who owns the result. A workflow that prepares a draft has a different scope from one that updates customer records or takes an external action.
Separate the cost categories
- Discovery: requirements, sample data and feasibility.
- Build: application logic, integrations and the review interface.
- Operation: hosting, model/API usage and other subscriptions.
- Support: monitoring, incident handling and agreed maintenance.
- Change: new workflows, source systems or requirements.
Budget for exceptions
Documents may be unreadable, external services unavailable or inputs incomplete. Agree a manual route and make failed items visible. Review effort should be counted in the business case rather than assumed to disappear.
Use your own volumes
Estimate monthly workload and the number of processing steps per item. Test the estimate with actual pilot usage. Set appropriate usage limits and alerts before allowing a workflow to run unattended.
Agree ownership
Your quote should say who owns cloud accounts, pays subscriptions, receives alerts and approves changes. Include handover and a route to export your information. Model changes and third-party API changes can require retesting.
A useful first brief
Bring a sample input, desired output, estimated volume, systems involved and the cost of the existing process. We can then distinguish an achievable first version from later improvements.