Costs and pricing
Part of How to build a community budget that finance will trust
After a community pilot: finding the hidden costs other teams absorbed
Review a community pilot for hidden costs that other teams absorbed, from leave cover to departure, and move that work into the next English budget.
A pilot shows which work happened without a budget line. The ten prompts below are not benchmark prices. They are places to look for effort that someone else absorbed. Estimate each from the chosen audience, risk and delivery model using current internal rates or written supplier evidence, and size what stays uncertain with the contingency method.
What to take away
- Review actual effort after a pilot and move absorbed work into the next forecast.
- Hidden costs appear when work falls outside a platform quote or a named job description.
- Continuous platform availability is not the same as continuous human support.
- Training, measurement and volunteer coordination all consume staff time and money.
- A yearly total can still fail if cash and people are missing in the required month.
Ask what the pilot absorbed
Review actual effort after a pilot. If another team quietly absorbed expert answers or incident work, transfer that work into the next forecast. A budget is complete only when all necessary work has an accountable home.
Costs become hidden when work falls outside a platform quote or a named job description. A pilot exposes them because real members create real handoffs. Ask each team that touched the pilot what it did that appears on no list, and record the answer against one of the ten items.
Ten places absorbed work hides
| Item | What absorbed work looks like | What to ask the pilot team |
|---|---|---|
| Unanswered-question follow-up | Finding a product, policy or subject expert, returning to the member and recording the answer | How long the full handoff took, not only the time spent posting |
| Leave and out-of-hours cover | Member access continued while the operator was absent | Whether relief, on-call arrangements or a reduced service were agreed |
| Appeals and quality review | Evidence, review and communication on complex removals, plus sampling of routine decisions | Which cases a trained colleague handled outside initial moderation |
| Privacy and rights handling | Mapping, notices, retention, access controls and request handling | Which of these activities actually ran |
| Security and recovery | Patching, monitoring, backup and restore, or identity, permission, supplier and incident oversight | Who did this work and under whose job description |
| Accessibility remediation | Specialist review, participant testing, fixes and regression checks | Barriers found in custom themes, embedded forms or event tools |
| Content and data migration | Ownership, retention and permission decisions, broken links, duplicate accounts, private groups and attachments | Manual work hidden by the headline record count |
| Integration maintenance | Monitoring, failed-record repair, credential rotation and vendor updates | Which connections changed after the original build |
| Usage and feature expansion | Members, storage, email, streaming, administrators or automation beyond allowances | How far the pilot sat from each allowance |
| Exit and parallel operation | Export, archive review, member communication, reconstruction, supplier assistance and two services running | Whether the export format was tested early |
Read the table against the quotes
Continuous platform availability is not continuous human support. Member access can continue while the operator is absent, so a leave line needs relief, an on-call arrangement or a clear reduction in service. Never describe the first as the second.
Hosted platforms still need supplier oversight. The NCSC suggests gaining confidence in a managed service provider's cloud offering by measuring it against its 14 cloud security principles. Those principles help structure questions. They are not a substitute for a service-specific cost estimate.
For privacy work, the ICO suggests starting with its accountability toolkit to assess an organisation's accountability measures. It can reveal governance activities but does not price them, and data protection duties still need specialist input.
Allowances need checking on the purchasing date. Circle's pricing page shows first-party plan information, while Mighty Networks publishes its own plans. These examples do not establish the cost of another product, and how pricing models behave as a community grows explains why.
Count the work that cuts across items
Training cuts across several lines. New moderators need practice, experts need a safe answer route and administrators need succession. Include preparation, attendance, exercises, documentation and refresher time. A vendor webinar may explain controls without teaching the organisation's rules or incident boundaries.
Measurement also consumes work. Definitions, baseline collection, data cleaning, quality sampling, analysis and reporting need ownership. A platform dashboard may reduce extraction effort but cannot decide whether an answer was appropriate or an outcome was attributable.
Volunteer programmes bring coordination rather than free capacity. Recruitment, screening where appropriate, support, recognition, conflict management and replacement belong in the forecast. Do not put an urgent safety function on a rota that participants can leave without a staffed alternative.
Show cash timing and update the forecast
Several small annual lines may arrive together during launch or renewal. A total that fits the yearly envelope can still fail if the organisation lacks people and funds in the required month, so the corrected forecast shows timing as well as totals.
Assign each item a driver, source, range and owner. Appeals follow disputed decisions, while migration effort follows content complexity, not simply membership size. Keep contingency tied to identified uncertainty. The surrounding method is in building a community budget.
Before you act
- Ask every team that touched the pilot what work it absorbed.
- Assign each hidden item a driver, source, range and owner.
- Estimate costs from internal rates or written supplier evidence.
- Check first-party pricing on the purchasing date.
- Test export formats early before planning an exit.
- Include training, measurement and volunteer coordination in the forecast.
Common questions
Why do these community costs go missing from budgets?
Costs become hidden when work falls outside a platform quote or a named job description. A pilot makes the gap visible, because another team's absorbed effort shows up as work nobody had planned or priced.
Does a hosted platform remove the need for security and recovery work?
No. Self-managed systems need patching, monitoring, backup and restore work, but hosted platforms still require identity, permission, supplier and incident oversight.
What should be done after a pilot?
Review the actual effort, then move any work another team quietly absorbed into the next forecast.
