Free resource
The RFP pack
How to write a request for proposal that produces answers you can actually compare. The structure, fourteen questions written so a vague response is obvious, a scoring model agreed before responses arrive, and what to do once they do. Written for contact centre and phone system selection in Australia.
What is inside
Four parts, seven pages
Most technology RFPs are written to be defensible rather than useful. They ask for a feature list, receive a feature list, and produce a shortlist that could have been assembled from the vendors own websites. This is written to produce a different result.
Who it is for
Two situations this is written for
The pack assumes you are replacing something that works well enough to make the decision difficult.
You have to run a formal process
Procurement requires an RFP, and you would rather it produced a genuine comparison than a stack of brochures. Parts one and two are the document, part three is how you defend the outcome.
Start at part one
You are not running a formal process, but you want the answers
The fourteen questions work just as well sent to three vendors by email. Most of the value in an RFP is in asking questions that are hard to answer vaguely, and that does not require a formal process.
Start at part two
Free download
Send me the RFP pack
We use your details to send you this document and to answer you if you get in touch. We do not add you to a mailing list and we do not pass your details to anybody else. See our privacy policy.
Common questions
Questions about the pack
What people ask before giving an email address for something.
What does it cost?
Nothing. We are vendor funded, so the service costs your business nothing.
Will I be added to a sales sequence?
No. You receive the pack, and we contact you only if you ask us to.
Is it specific to contact centres and phone systems?
The questions and the scoring model are written for that selection, because that is the market we work in every day. The structure and the scoring approach transfer to most technology purchases without change.
How long does an RFP process actually take?
About six weeks done properly: writing the document, giving vendors time to answer, scoring, reference calls and negotiation. Anyone who tells you two weeks has removed a step that matters.
Can we send you the responses to look at?
Yes, and it is the fastest way to get value from us. Reading the commercial terms in a set of responses takes us a day rather than a project.
What if we already have a preferred vendor?
That is still worth testing. A renewal or a direct award negotiated against real market pricing usually improves whether or not you end up moving.
We are vendor funded and completely free to your business. Always focused on the right outcome.
Or let us run the process for you
We already know what these vendors charge and where they will move. You get a shortlist with the whole of contract cost attached, and where each option is weak.
Book a Call
Independent guidance at no cost to your business.
Read further on this
The pages and articles that answer the next question a buyer usually asks.
- AI Policy and Governance Pack
- Cyber Incident Response Plan Pack
- IT and Communications Continuity Pack
- cloud phone systems
- cloud contact centre
- whole of market vendor comparison
- all resources
- contact us
- Unified Communications as a Service: Vendor Landscape 2026
- Why AI is reshaping UCaaS and CCaaS pricing for Australian buyers
- AI meeting agents that act inside the call, not after it
- Service desk platforms with native voice: where they fit and where they do not
- Why small retailers miss 40% of calls at their busiest hours
- Voice AI versus phone menus in UCaaS: what Australian teams should weigh

