
Costs and pricing
How to build a community budget that finance will trust
Build an England community budget from people, technology, implementation, risk, change and exit, using traceable inputs instead of invented rates.
A community budget pays for a service delivered by people through technology. The visible subscription may be small beside research, facilitation, moderation, expert answers, assurance, integration and change. Conversely, an expensive product does not prove that members receive a useful outcome.
This guide provides a reproducible budgeting method for an English organisation. It does not publish market rates or future prices. Supplier pages were reviewed on 5 September 2026 and must be checked again when the buyer requests a quote.
What to take away
The method has six steps: boundary, people model, setup versus steady operation, charging units, assurance with contingency and exit, then three connected views and reforecasting.
- Set the service boundary before any request for prices; Define what the budget includes explains why different boundaries cannot share a meaningful cost comparison.
- Build the people model from tasks and ranges, not job titles, and keep rare high-consequence work visible.
- Separate setup from steady operation and keep a change budget after launch for permissions, moderation and integrations.
- Ask suppliers to define each charging unit, then turn that unit into a driver you can forecast.
- Budget exit at the start, including notice payments, data export, archive decisions and deletion verification.
Define what the budget includes
Write the service boundary before requesting prices. Record:
- the eligible member group and its English or UK scope;
- the activity the organisation will support;
- public, member-only and private functions;
- normal and exceptional operating hours;
- forecast member, contribution, event and report ranges;
- internal, supplier and volunteer responsibilities;
- the period of the decision.
Different boundaries cannot share a meaningful cost comparison. A public customer-support forum with weekend cover requires different work from a small professional cohort meeting once a month.
State the alternative too. The decision may compare community delivery with direct support, events, documentation or no intervention. Continuing an existing service should include the cost of current technical debt and unpaid work borrowed from other teams.
Build the people model first
List tasks rather than starting with job titles. Discovery, welcoming, facilitation, unanswered questions, moderation, appeals, events, reporting, product feedback, data requests, technical administration and specialist escalation need different time and authority.
People cost formula inputs
- activity volumerecurring work
- handling timeper task
- loaded people costfrom finance
- rangelow to high
For recurring work, calculate:
activity volume x handling time x loaded people cost
Use a range for both volume and time. A routine welcome and a complex harmful-content report should not share an average that obscures their different distributions. Keep rare, high-consequence work visible as a scenario even when the expected monthly count is low.
The Office for National Statistics publishes earnings and working-hours datasets. Those statistics can provide labour-market context, but they do not determine an employer's salary, pension, National Insurance, recruitment, equipment or overhead. Finance should supply the loaded cost for each role.
4 to gross salary to cover employer National Insurance, pension and other employment costs. That range is typical rather than a rule, so ask finance for the multiplier it uses. The ONS Annual Survey of Hours and Earnings gives median gross pay by occupation for the UK, which makes the closest standard occupational code the useful comparison for England.
Account for absence and continuity. If members can post at any time, the plan needs a credible route when the ordinary manager is unavailable. This may involve limited service hours, a rota, an external provider or urgent-only cover. Price the promise the organisation actually makes.
Include contributions from product, customer support, legal, privacy, security, accessibility and safeguarding specialists. If their time is not charged to the community budget, record it as a resource dependency so decision makers see the full organisational cost.
Separate setup from steady operation
Setup can include audience research, service design, procurement, contract review, configuration, customisation, integrations, data work, content preparation, user testing, training and launch communication.
Setup to steady operation
- Audience research and service design
- Procurement and contract review
- Configuration, integrations and data work
- Content preparation and user testing
- Training and launch communication
- Keep a post-launch change budget
Estimate each line with a quantity, rate, source and range. Avoid a single implementation percentage applied to every product. Migration effort follows the quality and complexity of source data, while integration effort follows the systems and decisions involved.
Keep a change budget after launch. Permissions, notification rules, moderation processes, content structure and integrations will need adjustment when real members use the service. Without that allowance, necessary improvement appears as an overrun rather than an expected part of implementation.
Understand software charging units
Community products can charge by plan, registered members, active members, administrators, storage, messages, streaming, automation, support or negotiated enterprise terms.
Treat each unit as a driver to forecast. Write the supplier's definition beside your own input, so the line reads as active members multiplied by the price per active member per month. Before you accept the definition, ask for the measurement period, exclusions, reset, overage and the evidence available to the buyer.
Software charging units
Circle
- Plan structure
- public plans
- Unit basis
- varies
- Quote status
- not a quote
- Taxes
- may exclude
Mighty Networks
- Plan structure
- public plans
- Unit basis
- varies
- Quote status
- not a quote
- Taxes
- may exclude
Discourse
- Plan structure
- public plans
- Unit basis
- varies
- Quote status
- not a quote
- Taxes
- may exclude
Circle's pricing page, Mighty Networks' pricing page and Discourse's pricing page are first-party records for those providers. They illustrate different public plan structures on the review date. They are not quotes, do not establish like-for-like features and may not include taxes or the buyer's full service.
Create low, expected and high scenarios using the supplier's precise definitions. Do not inflate or suppress member activity to fit a tier. If an economically sustainable plan requires removing legitimate historical accounts, assess the retention and member consequences rather than making cost the only rule.
Cost the delivery model
Internal operation
An internal team may connect closely with product, policy and support. Budget recruitment, management, training, absence, specialist time and tooling. Do not treat work dispersed across existing employees as free.
Delivery model cost drivers
Internal operation
- Main cost
- staff time
- Key risk
- hidden effort
- Must define
- recruitment and cover
- Often missed
- dispersed work
Managed service
- Main cost
- retained capacity
- Key risk
- scope creep
- Must define
- volumes and boundaries
- Often missed
- investigation time
Self-managed technology
- Main cost
- engineering
- Key risk
- upgrades and recovery
- Must define
- availability
- Often missed
- monitoring and backups
Managed service
An external provider may price retained capacity, hours, activity units, named deliverables or a bespoke service. Define volumes, judgement boundaries, additional work and change. A quoted moderation hour may not include investigation, expert escalation, reporting or client approval.
Self-managed technology
Self-hosting can alter licence and infrastructure cost while increasing responsibility for upgrades, monitoring, backups, spam controls, recovery and technical support. Price engineering availability, not just server resources.
Combined suppliers
A platform, implementation partner and operator can create separate fees and handoff work. Allocate incident leadership, member communication, data requests and termination. Unowned gaps often become unexpected internal cost.
Include assurance and compliance
Budget the work required by the actual audience and risk: privacy review, data mapping, security assessment, accessibility testing, legal advice, online-safety assessment, advertising review, safeguarding and sector expertise.
The amount should follow scope, not a generic percentage. A public service likely to be accessed by children and a closed adult professional network present different questions. Both still need evidence for their conclusion.
Security costs span supplier due diligence, identity, administrative controls, monitoring, response and recovery. The National Cyber Security Centre's cloud security principles provide assessment questions without pricing or approving a product.
Privacy work continues after launch through rights requests, retention, access review, incident handling and new uses. The Information Commissioner's Office's accountability framework can help identify governance activities, but the organisation must estimate them using its own design and responsibilities.
Expose hidden and contingent work
Create a separate register for costs that depend on events. Examples include:
Contingent cost register
- Serious moderation or safeguarding case
- Rapid growth after product launch
- Inaccessible custom component remediation
- Supplier plan or feature changes
- Integration failure needing manual repair
- Legal or regulatory review after scope change
- Administrator loss or security incident
For each, estimate likelihood only where evidence supports it, then show consequence and response. Some high-impact risks belong in organisational contingency or insurance rather than the community's ordinary operating line.
Do not hide uncertainty in a rounded contingency percentage. Name the uncertain assumption and show how the total changes. This gives the owner a decision, such as narrowing the first cohort or removing a complex integration.
Budget exit at the start
Termination may require notice payments, member communication, data export, archive decisions, content review, reconstruction, parallel running, supplier assistance and deletion verification.
Exit cost checklist
- Notice payments and member communication
- Data export and archive decisions
- Content review and reconstruction
- Parallel running and supplier assistance
- Deletion verification
- Test a representative export first
Test a representative export. Count posts, attachments and accounts only after checking relationships, visibility and permissions. A file that contains every record may still be expensive to use if it loses threading or group context.
Decide which material moves, remains read-only or is deleted under an established rule. Budget human review for content that cannot be classified automatically. Include the service required while the new route is prepared.
A worked example budget
A worked example shows the arithmetic behind the method. Every figure is illustrative, not a market rate. It describes an English membership body with 8,000 registered members, one public forum and no self-hosting.
Assume a loaded people cost of £40,000 per full-time equivalent, taken from payroll rather than from a salary survey. Use your own figure, because the people line moves with volume, handling time and loaded cost.
| Line | Low | Expected | High | Main driver |
|---|---|---|---|---|
| People | 0.4 FTE, about £16,000 | 0.6 FTE, about £24,000 | 0.9 FTE, about £36,000 | volume x handling time x loaded cost |
| Software | £4,000 | £7,000 | £14,000 | charging unit, tier and overage |
| Setup | £6,000 | £12,000 | £25,000 | data quality, integrations, training |
| Change budget | £1,000 | £2,000 | £6,000 | adjustments after launch |
| Contingency register | £3,000 | £6,000 | £12,000 | event-dependent costs |
| Exit | £3,000 | £8,000 | £20,000 | export testing, review and notice terms |
| First-year indicative total | £33,000 | £59,000 | £113,000 | sum of the lines above |
All amounts are illustrative and exclude VAT. Do not treat them as a market rate, because the drivers in the last column set the real numbers. The contingency line comes from the risk register, not from a flat percentage of the total.
Supplier pages commonly show prices excluding VAT. VAT on community software and management services is normally charged at the standard rate of 20% across the UK. An organisation that cannot recover VAT should budget the inclusive amount, and partial recovery needs finance's own calculation.
Build three connected views
Three connected budget views
Finance view
- Groups by
- setup and recurring
- Includes
- contingency and exit
- Shared input
- same inputs
- Rule
- one total
Service view
- Groups by
- member activity
- Includes
- outcomes
- Shared input
- same inputs
- Rule
- one total
Responsibility view
- Groups by
- owners
- Includes
- internal and supplier
- Shared input
- same inputs
- Rule
- one total
Build three tables from one set of inputs, so the views agree. Separate tables must not produce three different totals.
Question it answers
- Finance
- What will we pay, and when?
- Service
- What activity drives each line?
- Responsibility
- Who owns and approves the figure?
What it holds
- Finance
- cash by period and cost category
- Service
- volumes, handling times, charging units
- Responsibility
- owner, approver and evidence for each line
Assign a source, accessed date, confidence and reviewer to every material amount.
Run sensitivity on the factors most likely to move the decision. Member registrations may affect one software model, while contribution volume and report complexity affect staffing. Implementation uncertainty can dominate the first year even when steady operation is predictable.
Evaluate value without forcing a number
Connect financial benefits through a measured route. A peer-support answer may reduce direct support only if the member receives an appropriate response and does not require the same contact later. Page views are not ticket deflection.
For each attributable financial benefit, calculate:
eligible volume x measured change x attributable share x unit value
Test low, central and high assumptions. Community members may already be more committed than non-members, so a retention difference is not automatically caused by participation.
The government's Magenta Book concerns evaluation of public interventions, while HM Treasury's Green Book concerns public-sector appraisal. A commercial organisation should not copy their parameters. Their attention to counterfactuals, options, uncertainty and evaluation is still a useful methodological check.
Keep valuable outcomes without credible monetary conversion as separate evidence. Member access, learning, safety and trust should not acquire invented pound values merely to enter a formula.
Control and update the budget
Obtain approval from the service owner and finance, plus specialist sign-off for material assurance lines. Record which assumptions would trigger reforecasting. Do not wait for annual planning when activity or supplier terms have moved substantially.
Compare actual invoices and staff effort with the original drivers. If product colleagues repeatedly answer questions or moderators spend longer on appeals, bring that work into the next forecast. Investigate whether the process, scope or measure should change.
Retain versions and source dates. Prices, employment costs, taxes, volumes and regulatory expectations can move. The reliable output is not one permanent total; it is a transparent model in which another reviewer can replace an input, follow the calculation and understand which decision changes.
Before you act
- Write the service boundary first.
- List tasks rather than starting with job titles.
- Use a range for both volume and handling time.
- Record specialist time as a resource dependency if uncharged.
- Keep a change budget after launch.
- Test a representative export before committing to exit terms.
Common questions
Why should the service boundary be written before prices are requested?
Different boundaries cannot share a meaningful cost comparison. See Define what the budget includes for the record to keep before asking suppliers for quotes.
How should recurring people costs be calculated?
For recurring work, calculate activity volume multiplied by handling time multiplied by loaded people cost. Use a range for both volume and time, because a routine welcome and a complex harmful-content report should not share an average. Finance should supply the loaded cost for each role, including pension, National Insurance, recruitment, equipment and overhead.
What should be budgeted for exit?
Budget exit before launch and test a representative export. Count posts, attachments and accounts only after checking relationships, visibility and permissions. Decide which material moves, remains read-only or is deleted under an established rule. Budget exit at the start sets out the work, from notice payments to deletion verification.
In this guide
- Costing an English community from people to termination without invented ratesEstimate community costs in England from people, software, implementation, moderation, governance, support, change and exit without invented rates.
- How flat, per-member, per-seat and usage pricing behave as a community growsCompare flat-tier, member, activity, administrator, usage and bespoke community pricing through official records and workload-based scenarios.
- Sizing contingency in a community budget from confidence ratingsSize contingency for an English community budget by rating uncertain lines low, medium or high confidence, then adding the expected-to-high gap.
- Community return on investment only counts once the counterfactual is written downCalculate community ROI from an evidenced counterfactual, attributable benefits, complete costs, uncertainty ranges and non-financial member outcomes.
- After a community pilot: finding the hidden costs other teams absorbedReview a community pilot for hidden costs that other teams absorbed, from leave cover to departure, and move that work into the next English budget.



