Reseller guide | Fact-checked 29 June 2026
How to price phone system projects without underselling support
Phone system projects should price discovery, design, build, porting, testing, training, documentation, and hypercare separately from recurring licences. Resellers lose margin when they hide project work inside monthly seats or underestimate post-go-live support.
The short version
Phone system projects should price discovery, design, build, porting, testing, training, documentation, and hypercare separately from recurring licences. Resellers lose margin when they hide project work inside monthly seats or underestimate post-go-live support.
What to decide first
Start with the operating model: who owns the platform, who supports users, who owns numbers, and how changes are handled after go-live.
What usually gets missed
Phone-system projects fail around undocumented call flows, number porting, devices, emergency calling, support ownership, and user training.
How to use this guide
Use the table, checklist, and FAQs as a starting point for discovery before asking for quotes or recommending a platform.
Commercial model: practical decision points
| Area | What it means | Why it matters |
|---|---|---|
| Discovery fee | Audit current system and requirements. | Filters poor-fit opportunities and funds proper scoping. |
| Implementation fee | Build users, call flows, devices, numbers, integrations, and testing. | Reflects real labour. |
| Porting fee | Coordinate documents, carrier process, and cutover. | Porting is project management, not admin fluff. |
| Managed support | Adds/moves/changes, troubleshooting, vendor escalation, and reviews. | Recurring price must match support expectations. |
Reseller support
Pressure-test the client opportunity
If How to price phone system projects without underselling support is part of a client conversation, we can help test the scope, platform fit, migration path, and support model before you quote it.
Get a practical second opinion
Tell us what you are reviewing, replacing, selling, or migrating. We will help you work out the sensible next step.
Checklist
- Track time by project phase.
- Create standard packages.
- Charge for complex call-flow design.
- Separate hardware from labour.
- Review support tickets after 60 days.
Frequently asked questions
Should discovery be free?
Sometimes for simple opportunities, but complex environments deserve paid discovery.
What support is commonly forgotten?
Reception changes, call-flow edits, reporting requests, handset swaps, and carrier escalations.
How do you defend project fees?
Show the customer the migration plan, risks, and work involved.
Sources checked
This article was fact-checked on 29 June 2026 against official sources where applicable. Product features, technical requirements, regulations, and service availability can change, so confirm the current state before purchasing, quoting, or migrating, or reach out for a free, personalised comparison.