A good starting point when
Staff copy information between tools, send the same reminders, or manually route routine approvals.
What an agreed scope can include
The proposal confirms the exact deliverables before work starts.
- A map of the current process and its exceptions
- One clearly defined automation or an agreed set of workflows
- Connections to the systems and APIs listed in the scope
- Failure alerts, retry rules and a manual fallback
- Test cases, operating instructions and a named handover contact
What is quoted or checked separately
- API limits, platform subscriptions and usage charges are quoted separately.
- Unavailable APIs or unreliable source data may require a different approach.
- An automated step still needs an agreed owner and exception process.
What we need from your team
- Explain the business rules and who can approve changes.
- Provide sample cases, including failed or unusual transactions.
- Nominate someone to receive alerts and own exceptions.
How you review the result
Run normal, duplicate and failed transactions; check that alerts reach the right person and the manual fallback works.