How to compare business service quotes

Define the requirement once, in writing

A comparison is only meaningful if every supplier was asked the same question, and the common failure is that they were not. Write the requirement down before approaching anyone: what is being bought, for how many sites, users, seats or circuits, over what period, with what service hours, and with what has to be included. Then send the same document to every supplier and ask each to respond against it clause by clause, declaring any deviation rather than quietly shaping the offer around what they prefer to sell. Proposals that answer a different question are not cheaper or better; they are answers to something else, and the difference belongs in the comparison. State the obligations that follow the service in the same document, because a supplier who is told about them prices them, and one who is not will either assume they are excluded or raise them after the decision.

• One written requirement, sent to everyone unchanged.
• Counts stated explicitly: sites, users, seats, circuits, volumes.
• Service hours and inclusions named rather than implied.
• Deviations declared by the supplier, not discovered later by you.

Where the binding terms sit, and which duties follow the service

A quote is an offer, not the agreement, and the terms you can enforce are usually written somewhere else. Some services are sold under a filed tariff, and interstate telecommunications is the clearest example: a carrier that is required to file may not provide the service until its tariff publication is on file and in effect, and that filing — not the sales proposal — states the rates, terms and conditions, with 47 CFR Part 61 governing how the publications are made and revised. Services sold on contract work the other way round, with the enforceable terms living in a master agreement and its schedules. That is why two quotes for an identical requirement can differ in where they bind, and not only in what they say. Some duties also follow the service rather than the supplier. A voice deployment has to let a caller reach emergency services directly and pass location information specific enough to find the caller, and that duty sits with the organisation even where the platform supplies the capability. Number porting carries its own clock: a simple wireline-to-wireline or simple intermodal port has to be completed within one business day unless the new provider or the customer asks for longer, and a non-simple port within four business days. Two voice proposals that disagree on those points are not the same product at different prices.

• A quote is an offer; the enforceable terms live in a tariff or an agreement.
• Tariffed services are governed by a filing the regulator can read.
• Contract-based services put everything in the master agreement and its schedules.
• Some duties follow the service: emergency calling, and the porting interval.

The four clauses that decide a proposal's real value

Behind every total sit four things that change what the arrangement actually costs to own. Scope says what is included and, more usefully, what is not. Term says how long you are committed and what leaving early involves. Exclusions and assumptions say which risks the supplier has left with you, often in a section near the end that is easy to skim. The end-of-term position says what happens when it finishes: whether it renews automatically, what notice is required, and what you are entitled to take with you. Two proposals with identical scope and different end-of-term positions are different products, and the second one usually decides the outcome. Read the notice window and the renewal term together rather than separately, because the effective deadline in any renewal is the notice date, not the end of the term, and an evergreen clause simply extends the commitment when that date passes unremarked. Early-termination terms are worth reading for the same reason: they are usually a formula rather than a fixed sum, and if the formula is calculated on the remaining commitment then the cost of leaving falls as the term runs down while the cost of staying does not.

• Scope, including everything explicitly excluded.
• Term, and the cost of leaving before it ends.
• Assumptions the supplier has made on your behalf.
• What happens at the end: renewal, notice and what you keep.

Put everything over the same period

Comparisons go wrong when the periods differ: an offer that looks lower may simply cover a shorter commitment, exclude installation, or include an uplift partway through. Restate every proposal over the same period with the same inclusions, and where an offer has a one-off component, keep it visible rather than averaging it into a monthly figure that hides it. For services with a usage element — energy, circuits, cloud consumption — normalise against your own historical volumes rather than an assumed profile, because the supplier's assumption about your usage is frequently the largest single difference between two proposals. Ask what happens when you deviate from it: whether the basis steps up in tiers, whether a minimum commitment applies regardless of what you consume, and whether an unused allowance can be carried forward. Unit consistency is part of the same discipline: a service quoted per seat per month and another quoted per site per year cannot be compared until both are restated over one base, and the restatement is usually where the apparent difference disappears or doubles. Write the common base into the request so the supplier does the conversion rather than you.

• Same period for every option, stated on every line.
• One-off charges shown separately, not smoothed into a monthly number.
• Usage-based components recalculated against your own history.
• The supplier's assumed usage profile identified and challenged.

Separate what is promised from what is measured

Service commitments are where proposals are least comparable, because language that sounds identical can mean very different things. Response is not resolution. Business hours are not round-the-clock. A credit is not compensation for what the outage cost you. For each proposal, extract the commitment, the measurement, the reporting and the remedy as four separate entries, and note where any of them is missing — an absent remedy is a commitment that costs the supplier nothing. Then check whether the supplier reports performance as a matter of course, since a commitment nobody measures cannot be enforced by either side. A remedy is usually capped as well, commonly as a proportion of the monthly charge, so the size of the credit tells you what the supplier has agreed to risk rather than what the outage cost. Where availability is expressed as a percentage, remember that the percentage is a time budget rather than a quality statement: a tenth of one per cent of a thirty-day month is a little over forty minutes, and a hundredth of one per cent is a little over four. Two offers both promising the same figure are not the same promise if one measures it across all hours and the other only across business hours, or if one excludes scheduled maintenance windows and the other does not.

• Commitment, measurement, reporting and remedy as separate entries.
• Whether the clock counts business hours or all hours.
• Whether performance is reported, and how often.
• Whether planned maintenance sits outside the availability figure.

Send this when you ask for quotes

The request that produces comparable answers contains the requirement, the counts, the period, the service hours, the volumes from your own history where usage matters, the obligations that apply, the date by which a decision has to be made, and the format you want the answer in. If you have a preferred structure — a table, a template, a list of clauses to address — say so, because it costs nothing and removes most of the work of normalising later. The shape of the response is itself evidence. A document that restates your requirement, names what is excluded, states its assumptions and identifies the people accountable will be manageable when something goes wrong; one that quotes a single headline figure and leaves the end-of-term position vague is not more confident, only less specific, and the specificity you do not obtain before signature is the specificity you negotiate later, at a worse moment. Vendor oversight is a continuing function rather than a one-off review — NIST's Cybersecurity Framework, revised in 2024, added a Govern function for precisely this reason — which is the argument for treating the end-of-term position as seriously as the total.

• Requirement, counts, period and service hours.
• Your own usage history where the service is usage-based.
• The decision date, so responses arrive in time to be used.
• The response format you want, stated up front.

PUT THE OPTIONS SIDE BY SIDE

Your comparison checklist

Common questions