Define what the price must deliver.
“Automate our requests” is too broad for a comparable price. State which requests enter, who receives them, what constitutes accepted ownership, what staff can change and what residents can see. Include exception handling and the finish event. A form and notification are a different scope from a connected case-management system.
Clarify whether the work configures an existing product, connects approved systems or builds a focused application. These choices distribute costs differently. Existing licenses may reduce new purchasing while still requiring configuration, training, support and internal review.
This guide supplies a budgeting method, not a market-price survey or a Civicfield quote. Actual prices require an agreed scope and current supplier information. Website pricing has a different owner in the website cost guide.
Separate the cost drivers.
| Cost area | Scope assumptions to record | Evidence to request |
|---|---|---|
| Process discovery | Services, roles, exceptions and approval decisions | Reviewed process map and unresolved questions. |
| Configuration or development | Forms, queues, roles, rules and notifications | Demonstrated acceptance scenarios. |
| Integrations | Systems, supported operations, authentication and error recovery | Access confirmation, field map and recovery test. |
| Data preparation | Records, attachments, cleaning and historical events | Sample export, reconciliation and rejected-row handling. |
| Evaluation | Functional, accessibility, security and service checks in scope | Test plan, findings and retest evidence. |
| Training and handover | Staff roles, practice tasks, documentation and access | Successful handoff exercises and named owners. |
| Ongoing operation | Licenses, usage, hosting, monitoring, support and changes | Limits, coverage, unit pricing and escalation. |
| Exit and transition | Usable exports, attachments, accounts and support | Export demonstration and priced transition responsibility. |
On a small screen, scroll the table sideways to see every column.
Separate vendor fees from agency labor. A proposal can be inexpensive in cash and still require significant staff capacity. Show required agency decisions and dependencies in the schedule, especially when access or procurement is outside the implementer’s control.

Compare three scope shapes without assuming a standard price.
A configuration-only pilot may use one form, one owner queue and existing licensed tools, with no historical import. A connected workflow may add a supported API, synchronized fields, retries and reconciliation. A broader operational system may include multiple departments, detailed permissions, historical records and a higher support commitment.
For each option, write what is included and excluded. Ask how a new department, notification channel or required approval changes the scope. Document usage assumptions such as staff seats, records, attachments, message volume and API availability. “Unlimited” should not stand in for a reviewed service definition.
Use the integration checklist before assuming an account’s API can support the proposed work. A published API does not prove your account has the required access or that every action is supported.
Use a transparent comparison calculation.
Hypothetical budget arithmetic only. Suppose one option has $8,000 in implementation fees, $250 per month in recurring fees, $2,000 in agency setup labor and $1,200 per year in agency operating labor. These are invented inputs to demonstrate the calculation, not market estimates or an offer.
For a three-year comparison with no escalation, migration extras, tax or exit fee: $8,000 + (36 × $250) + $2,000 + (3 × $1,200) = $22,600. Show excluded amounts as unresolved rather than silently treating them as included. If an exit cost is expected, add it explicitly.
Calculate another option over the same period and scope. Test a higher usage assumption, a changed support need and a delayed integration. Report the changed totals separately. A comparison that grants one option free staff labor or omits its exit work can reverse the apparent choice.
Keep savings assumptions separate from the budget.
Observe current handling time and rework before estimating a benefit. If a task takes less time, that creates potential capacity; it does not automatically reduce payroll or prove a cash saving. Staff may use the time for other service work, and the new workflow also needs support.
The GOV.UK cost-per-transaction guidance (opens in a new tab) is a methodological reference for defining service cost and transactions. It is UK guidance. Do not import its reporting obligations into a municipal scope.
Use consistent event definitions from the measurement guide. Completed submissions, accepted cases and completed operational work are different denominators. A lower cost per closed record can conceal unresolved work if closure criteria change.
Ask for a reviewable proposal and a bounded first step.
Request one-time costs, recurring charges, usage limits, optional work, agency responsibilities, support coverage, acceptance evidence and transition costs in separate fields. Require assumptions and open dependencies alongside the total. Ask what happens when an integration fails after launch and who investigates.
If uncertainty is high, scope a bounded discovery or pilot with a clear output and decision point. Use the priority matrix to select it and the build-or-buy pilot record to define the evaluation. The result should make the next spending decision better informed.


