Small Business Phone System Costs UK: Compare Quotes Fairly

Small Business Phone System Costs UK: Compare Quotes Fairly

A small business phone system cost in the UK can look simple when a proposal starts with one monthly price per user. Yet two suppliers quoting £13 and £18 per user may not be selling the same thing. One price might exclude calls, support and mobile apps; another might include them but charge separately for number porting, handsets or recording storage. The cheaper licence can produce the larger bill once the contract is running.

A fair comparison therefore starts with a common operating picture and a cost ledger, not a headline rate. This guide shows how to turn cloud, on-premise and hybrid proposals into a consistent three-year view. Every figure in the worked example is illustrative, excludes Value Added Tax (VAT) and should be replaced with a written supplier quote.

Define what suppliers are pricing before comparing prices

A supplier cannot price your needs accurately if “12 users” could mean 12 named employees, eight desktop applications, four shared handsets and three people who only need occasional mobile access. Before requesting quotes, define:

• named users and the permissions each role needs;
• shared locations such as reception, workshop or warehouse phones;
• public telephone numbers to keep, add or retire;
• expected simultaneous inbound and outbound calls;
• desk phones, headsets, desktop apps and mobile apps by role;
• opening hours, queues, overflow and out-of-hours routes;
• recording, reporting and integration requirements;
• office, home and mobile connectivity conditions;
• the support and administration tasks your team expects the supplier to own.

If that work has not been done, use the small business phone system requirements checklist to map users, numbers, call capacity and real customer journeys first. The same specification should go to every shortlisted supplier. Otherwise, each price rests on different assumptions and the totals will never be genuinely comparable.

Build the UK small business phone system cost from eight parts

Put each quote into the same eight cost groups. Require suppliers to mark every line as included, optional, usage-based, third-party or unsupported. A blank cell is not a zero; it is a question that still needs a written answer.

1. Licences, users and shared positions

Ask what triggers a licence. Is it a person, extension, device, simultaneous call or feature bundle? Can one named user have a desktop and mobile app under one licence? Does a shared reception phone require a full user licence? Are voicemail, call queues, an interactive voice response (IVR) menu and reporting included at that tier?

Private Branch Exchange (PBX) software controls extensions, call routing and business calling features. A hosted or cloud system may package PBX functions into per-user plans, but the packaging differs between suppliers. Compare the required behaviour, not just the plan names.

Record the quantity, unit rate, billing period and minimum commitment for every licence. If a feature forces only three supervisors onto a higher tier, price those three separately rather than assuming the entire team needs an upgrade.

2. Calls, numbers and porting

“Unlimited UK calls” needs a definition. Confirm which destinations are included, whether fair-use limits apply, how international and premium numbers are charged, and whether forwarded calls create another charge. Ask how calls to mobiles are treated and whether rates can change during the term.

List monthly rental for the main number, direct-dial numbers and local branch numbers. Include one-off porting fees, failed-port or resubmission charges where applicable, and the cost of keeping a temporary service live during migration. Check which party owns the numbers and how they can be moved when the contract ends.

Voice over Internet Protocol (VoIP) carries calls over an IP network. A Session Initiation Protocol (SIP) trunk connects compatible call-control systems to a telephony provider. Those technical labels do not tell you whether calls, channels, numbers or emergency-calling arrangements are included, so require the commercial boundary in writing.

3. Handsets, headsets and applications

Hardware can be bought, rented or bundled. Separate the cost of IP desk phones, conference devices, headsets, power supplies, delivery and replacement cover. Check whether rented devices must be returned and what happens if one is lost or damaged.

For software endpoints, confirm which desktop and mobile operating systems are supported. Ask whether mobile incoming-call push, contact integration, business caller identity, transfers and updates are included. A free-looking app can still carry rollout, support and device-management costs.

Avoid buying a handset for every employee by default. Reception and shared work areas may need dedicated hardware, while hybrid staff may work better with a managed desktop softphone and mobile fallback. Assign devices by job, then price that role-based mix.

4. Connectivity and resilience

Cloud calling depends on more than the phone licence. Your ledger may need to include business broadband, a backup circuit, mobile data, a managed router, Wi-Fi improvements, Quality of Service configuration, power protection and monitoring.

Ask what happens when the office internet connection fails. A provider-side fallback route to a controlled mobile or answering destination may be included, optional or unavailable. Price both the primary path and the recovery path. Reliability language has little value if keeping the main number reachable requires an unquoted service.

5. Setup, number migration and training

One-off implementation costs can include discovery, call-flow design, number porting administration, handset configuration, remote provisioning, onsite work, testing, project management and staff training. Ask how many call routes and changes are included before extra professional-services fees begin.

Clarify who collects the existing number records, who submits the port, who configures opening hours, and who runs acceptance calls. If your own staff must complete those tasks, estimate their time in the internal-cost section rather than treating it as free.

6. Integrations, recording and data

A customer relationship management (CRM) integration might mean a simple click-to-call browser extension, a caller record pop-up, or full activity write-back. Price setup, licences, third-party connectors, maintenance and support for the exact workflow you require.

For recording, ask about storage allowances, retention, retrieval, export and deletion. Confirm whether transcription, quality review or analytics are separate products. Recording may also create privacy, security and governance work inside the business; involve the people responsible for those obligations before treating it as a tick-box feature.

7. Support and routine changes

A low licence price can assume self-service support. Compare opening hours, target response times, escalation routes and any charge for telephone support. Identify whether moves, adds and changes are included: creating users, replacing devices, changing call flows, updating bank-holiday hours and removing leavers can all consume time.

Price the support level the business actually needs. A company with no telephony specialist may reasonably pay more for managed changes. A business with capable internal IT may prefer administrative control, but it should still estimate that employee time.

8. Contract movement and exit

Calculate over one consistent period, usually the shortest common term that reflects the decision. Record:

• contract length and automatic renewal rules;
• annual price increases and how they are calculated;
• minimum user or spend commitments;
• charges for adding or reducing users;
• hardware ownership at the end of the term;
• number-porting and data-export assistance on exit;
• early termination charges;
• deletion or export of recordings and voicemail;
• professional services needed to move away.

Do not assume today’s team size stays fixed. Ask suppliers to price a plausible high and low point, such as 12 users today, 18 after growth and nine after restructuring. Flexibility can be financially valuable even when it does not reduce the starting invoice.

Understand the different cost shapes

Architecture changes when costs appear, so avoid forcing every proposal into a single per-user number.

Cloud or hosted arrangements

Cloud designs often place more cost into recurring licences and reduce the equipment installed at the office. They may simplify adding remote users, but connectivity, managed endpoints, support tiers, integrations and usage still need separate checks. Confirm whether the supplier, reseller or customer owns each operational task.

On-premise arrangements

An on-premise PBX may involve larger initial expenditure for software, server or appliance hardware, installation and resilience. Ongoing costs can include SIP trunks, calls, support, maintenance, upgrades, power and specialist administration. Existing equipment can change the calculation, but only if its remaining life and support position are understood.

Hybrid arrangements

A hybrid design can preserve a useful existing system while adding cloud services or mobile endpoints. It may avoid an immediate replacement, but it can also create two support boundaries, integration work and overlapping contracts. Price the transition period as well as the intended steady state.

This section is about cost timing, not declaring one architecture universally cheaper. The right answer depends on existing assets, internal skills, growth, mobility, resilience and the customer journeys the system must support.

Worked example: the lower licence loses over three years

Consider a fictional 12-person UK services company. It needs 12 named-user licences, four new handsets, ten number ports and a three-year comparison. Both quotes support its documented call flows. The figures below are invented solely to demonstrate the method and exclude VAT.

Quote A includes UK calls and standard support:

• licences: 12 × £18 × 36 months = £7,776;
• setup: £600;
• four handsets: 4 × £120 = £480;
• ten number ports: 10 × £10 = £100;
• three-year total: £8,956;
• equivalent monthly cost across 36 months: £248.78.

Quote B has a lower licence but separate usage and support:

• licences: 12 × £13 × 36 months = £5,616;
• average calls: £75 × 36 months = £2,700;
• setup: £300;
• four handsets: 4 × £120 = £480;
• ten number ports: 10 × £10 = £100;
• required support tier: £60 × 36 months = £2,160;
• three-year total: £11,356;
• equivalent monthly cost across 36 months: £315.44.

Quote B’s £13 licence is lower than Quote A’s £18 licence, yet its modelled total is £2,400 higher. That does not prove bundled plans are always better. It proves that the headline rate is not the decision metric.

Now stress-test both totals. Replace the estimated call spend with a quiet month and a peak month. Add any annual increase exactly as the contract describes. Model the planned increase in users. Include the cost of a backup connection if only one supplier’s design requires it. The calculation should change when the assumptions change.

Create one quote ledger that finance and operations can both inspect

A spreadsheet is useful, but the discipline matters more than the software. Give every cost line these fields:

1. cost group and item name;
2. required quantity;
3. one-off unit cost;
4. recurring unit cost and billing period;
5. expected usage;
6. number of months in the comparison;
7. VAT status;
8. annual increase method;
9. included, optional or excluded status;
10. supplier assumption or dependency;
11. business owner responsible for validation;
12. evidence source, such as proposal page, contract clause or email confirmation.

Keep one-off cash requirement visible as well as total cost. Two proposals can have similar three-year totals but very different first-month demands. Record deposits and payment timing so cash flow is not hidden inside a long-term equivalent.

Add internal time as a separate, transparent estimate. For example, count the hours needed for data gathering, configuration, user onboarding, routine changes and supplier management. Use an agreed internal rate if finance considers it appropriate, but do not blend that estimate into the supplier invoice. Keeping the two visible prevents confusion.

Make the final quote survive a change-control test

Before approval, send each supplier the completed ledger and ask it to correct any misunderstanding. Require a final order form or proposal that identifies:

• exact products, tiers and quantities;
• call and number assumptions;
• implementation responsibilities and acceptance criteria;
• supported devices and application versions;
• support scope and escalation path;
• dependencies on broadband, third parties or customer labour;
• contract term, increases, renewal and exit conditions;
• every item explicitly excluded.

Then choose three likely changes—a new starter, a bank-holiday routing update and a lost mobile device—and ask how each is completed and charged. This exposes operational costs that a sales demonstration may not show.

Test the endpoint assumptions before signing the wider deal

The cost ledger is stronger when important assumptions have been exercised. Select five representative users: perhaps reception, sales, support, a home worker and a mobile manager. Test the proposed desktop and mobile endpoint pattern with real SIP accounts and realistic networks.

Check provisioning time, incoming calls on a locked mobile, two-way audio, business caller identity, hold and transfer, voicemail, recovery after a network change and complete access removal. Record support time and user feedback. The trial may show that some roles need a headset or managed mobile app while others do not, allowing the quote quantities to be corrected before commitment.

If managed softphones are part of the planned system, run this contained test in a SessionCloud trial. Use the evidence to validate endpoint quantities, rollout effort and support assumptions in the wider proposal. SessionCloud is the endpoint test here; your chosen PBX, carrier and call-routing design still need their own written commercial and technical validation.

Compare the complete commitment, not the teaser price

A fair UK phone-system comparison makes every supplier price the same users, numbers, customer journeys, devices and support boundary. It separates recurring charges from one-off work, usage, connectivity, contract movement and internal effort. It also shows exactly which assumptions drive the total.

That process will not produce one universal small business phone system cost for the UK. It will produce something more useful: a defensible total for your business, a record of what is included and a test plan that can catch an expensive misunderstanding before the contract begins.