Microsoft Premier Support
Microsoft-ondersteuning voor ondernemingen

Procurement Evaluation for Support Services: The 2027 Enterprise Guide to Technical Scoring and Vendor Selection.

Score Microsoft support proposals with the five Ps, a weighted scorecard and a real incident before you compare prices.
Rob LaMear, oprichter en voorzitter van US Cloud
Geschreven door:
Rob LaMear
Gepubliceerd op 19, 2026
Beyond the Bid: Procurement Evaluation for Support Services

The easiest number to find in a Microsoft support proposal is the annual fee. Try finding the name of the person responsible for the next update when a critical incident crosses a shift change. If one bidder includes that work and another expects your service desk to handle it, the two prices buy different things.

For a 2027 renewal, give the incumbent and each challenger the same case to work. Decide what good support looks like before anyone sees the prices. That gives procurement a way to explain a decision that otherwise comes down to whose presentation the room remembers best.

Executive summary

  • Agree on mandatory coverage, scoring weights and acceptable evidence before issuing the request for proposal (RFP).
  • Score People, Process, Platform and Performance against a real incident from your environment. Open the commercial bids after the panel records those findings.
  • Price the same year of work for every bidder. Carry the commitments that earned the winning score into the agreement.

Before the first bid

Start with four quarters of tickets, if available. Pull the severity, product, time opened and time service returned. Ask the service desk to flag cases where someone had to repeat the diagnosis or chase another provider. Pick one of those cases for the interviews. A routine case with a difficult handoff can tell you more than a spectacular outage nobody on the panel remembers clearly.

Write down the budget ceiling, renewal date and who can approve an exception. Ask IT operations what it needs at each severity and have security and legal identify any restrictions that apply to particular workloads. If a contract limits where support staff may access diagnostic data, specify the systems, data and activities it covers. Give bidders enough detail to supply evidence against the actual requirement.

Keep a mandatory requirement outside the weighted score. For example, if a plant operates overnight and the agreement must cover those hours, ask for the staffing and contact arrangements that demonstrate coverage. Decide before issuing the RFP how the panel will handle an incomplete answer. A high portal score cannot make an uncovered shift acceptable. For teams still defining their scope, US Cloud’s Microsoft support procurement guide covers the work leading up to the bid.

Use the five Ps

The five Ps give a panel a common order for evaluating support proposals. Use the first four to record what each provider can deliver. Open the price proposal once the technical scores are on file.

The 5 Ps for evaluating support proposals

People. Score the engineers who will hold the tickets, including their seniority and location. Ask who answers on a Saturday and what triggers access to a specialist. A certification roster helps establish expertise. A staffing schedule and a walkthrough tell you when your team can actually reach it.

Process. Follow a critical ticket through a shift change. Who authorizes escalation? Who calls the customer’s incident lead? What happens if the next team has yet to accept the case? Ask to see the handoff record and the time of the next promised update.

Platform. Test the ticketing portal yourself. Have a service desk analyst open a case, attach a diagnostic file, change the severity and export the history. Check which actions the analyst can take without calling the provider.

Performance. Request historical results for incidents comparable to yours. Separate acknowledgment from engineer engagement and service restoration. Ask how the provider counts reopened cases, customer holds and tickets still open at the reporting cutoff.

Price. Score it last. Give each bidder the same workload and hours of coverage to price. Require a line for work billed separately and a written assumption for anything the provider expects your staff to do.

Build the weighted scorecard

A panel can use a 70/30 technical-to-price split for a critical environment. That split is an example. A distributor approaching peak shipping season may put more weight on overnight escalation. Whatever you choose, publish the weights, evidence requirements and treatment of missing information with the RFP. The World Bank’s rated criteria guidance offers a procurement precedent for evaluating technical evidence before opening financial proposals. Its rules apply to its own procurements. Enterprise buyers can adapt the sequence to their approval process.

Agree on rating anchors. In this example, a zero means the bidder supplied no usable evidence, three means it demonstrated the requirement and five means it demonstrated a specific additional capability the panel had identified as valuable. Define one, two and four for each criterion before bidding. A four for Process might mean the bidder both completed the required handoff and demonstrated that a supervisor can see overdue updates. Give panelists a place to record which screen, document or reference supports each rating.

Multiply each technical rating by its available points and divide by five. A Process rating of four earns 16 of 20 points. For price, one possible rule gives the lowest qualifying annual cost 30 points. Divide that cost by each bidder’s qualifying annual cost and multiply by 30. Tell bidders which charges count and ask finance to check for omissions before applying the formula.

Suppose Bid A earns 60 of 70 technical points and costs $120,000. Bid B earns 51 and costs $100,000. A earns 25 price points and finishes at 85. B earns 30 and finishes at 81. The result gives the budget owner a precise question to ask. Which demonstrated capabilities earned A its nine-point technical advantage, and are they worth $20,000 to this business? The scoring notes should identify those capabilities without another sales call.

Run the same incident twice

Give the engineers likely to support your account a redacted version of the incident selected by your service desk. Give each bidder the same facts, time and follow-up questions. For example, six warehouse users lose access to a Microsoft application halfway through a shift. The night supervisor can reach the portal, but the person who usually authorizes diagnostic access has gone home. Tell bidders which permissions are available and ask them to walk the supervisor through the first call.

Have the service desk lead play the caller. Ask the bidder to show where the user impact will be recorded, who can authorize the next step and what update the supervisor should expect. Halfway through the exercise, tell the engineer that the issue now affects a second site. Watch who reclassifies the incident and who tells operations. A panelist should be able to point to a ticket entry or a named role for each action scored.

Then take one question to a reference with similar coverage hours. Ask the customer to describe the last case that crossed a shift boundary. Who called back? Did the incoming engineer have the case notes? How long did the customer spend bringing that engineer up to speed? A customer may be unable to share the ticket itself. Record which details the reference could confirm and which still depend on the bidder’s account.

Score independently before the panel meets. If one reviewer gives Process a five and another gives it a two, have both identify the evidence behind the rating. One might have scored the acknowledgment while the other scored the first substantive update. Resolve that difference against the published definition. If the definition leaves a genuine ambiguity, document it and seek the same clarification from every affected bidder.

US Cloud’s Microsoft support vendor checklist can help the panel spot a missing coverage question. Keep the notes from the exercise alongside the completed checklist. Those notes explain how a stated capability would work for your particular service desk.

Compare the cost of coverage

Model the year you expect to buy. List the prior year’s incidents by severity, the hours spent on planned work and any projects that drew on the same support budget. Ask each bidder to price that mix for the coming term. Record what consumes a credit, whether unused hours expire and which activities require advance approval. For an unlimited-incident bid, record the boundaries of an incident and any separately priced work.

Ask finance to keep provider charges and internal effort on separate lines. Suppose your service desk lead and an application owner each spend half an hour briefing a replacement engineer. That is one staff hour. If the pattern occurred on 24 tickets last year, the annual exposure would be 24 staff hours. Apply your own labor rate. Count the cost as a potential saving only when the proposed workflow gives you a credible reason to expect fewer briefings.

Look at one busy month as well as the annual total. A fixed pool of hours might cover the year on paper while a major incident exhausts the available balance before quarter end. Ask who authorizes extra hours, how quickly they become available and what happens to work already underway. Document the answer so the budget owner can distinguish a predictable overage from a coverage gap.

Before award, ask legal and IT to read the incumbent agreement together. Check renewal notice dates, rights to export ticket histories and any dependencies on licensing or support entitlements. List open cases and identify who can carry each one through transition. Where a product defect may need publisher action, ask the bidder who can open the case, under which entitlement, who pays and who keeps the customer updated. Put any unresolved dependency in the award memo with an owner and a decision date.

Document the award

Capture the bids considered, mandatory requirements met, final scores and cost assumptions. Attach one piece of evidence for each difference that affected the result. A reviewer should be able to trace an award back to the same criteria suppliers saw when they chose to bid.

If the winner earned points for after-hours access to a senior engineer, show where that commitment appears in the proposed agreement. An email from the sales team may describe the promise more clearly than the service schedule. Resolve the wording before signature. Apply the same check to data access, escalation ownership and reporting definitions.

Set a date for the first service review. Bring the award scorecard and an actual ticket from the new term. Look at who took the case, whether the update arrived when promised and what the customer had to do at handoff. If the service desk cannot extract that history, the first review has already identified a specific gap for the account owner to fix.

Request a support proposal 

Procurement FAQs

Procurement FAQs

Start with needs assessment and market analysis. Issue the RFP, evaluate technical proposals, score commercial terms, verify references and make the award with a transition plan. If reference evidence affects a technical rating, collect it before locking the technical scores and opening prices. State that sequence in the RFP so suppliers know when evidence is due.

How should we compare response times?

Ask both bidders to timestamp the same four events in a sample case. When did the customer report the issue, when did a person acknowledge it, when did an engineer begin work and when did service return? A fast acknowledgment answers the first service-level question. Operations still needs to know how long the warehouse waited to resume shipping.

What if the scores are close?

Use the tie-break rule disclosed in the RFP. If a one-point change in a subjective rating would reverse the ranking, review the underlying evidence with both scorers. Record the reason for the final rating and the remaining uncertainty. Changing weights after prices are visible makes the result difficult for the panel to defend.

What should we bring to a support proposal review?

Bring your renewal date, coverage hours, ticket mix and one case where escalation took longer than expected. Ask US Cloud to price those requirements and explain how the case would move through its support team. You can then put its proposal beside the incumbent’s and use the same scorecard for both.

Rob LaMear, oprichter en voorzitter van US Cloud
Rob LaMear
Rob LaMear zorgde voor een revolutie in de tech-industrie door als pionier SharePoint Portal Server 2001 voor het eerst aan te bieden als een cloud-hosted service. Zijn nauwe samenwerking met Microsoft was van groot belang voor het delen van multi-tenant expertise, waardoor de weg werd vrijgemaakt voor de ontwikkeling van SharePoint Online. Vandaag de dag onderscheidt Robs bedrijf, US Cloud, zich als de enige externe ondersteuningsprovider die door Gartner wordt erkend als volledig in staat om Microsoft Unified (voorheen Premier) ondersteuning te vervangen. Zijn niet-aflatende toewijding aan innovatie en uitmuntendheid zorgt ervoor dat US Cloud een betrouwbare partner blijft voor ondernemingen wereldwijd en consistent ondersteuning van wereldklasse levert aan organisaties die afhankelijk zijn van Microsoft-software.
Vraag een offerte aan bij US Cloud om Microsoft te laten besluiten de prijzen voor Unified Support te verlagen.

Onderhandel niet blindelings met Microsoft

In 91% van de gevallen krijgen bedrijven die een schatting van de Amerikaanse cloudkosten aan Microsoft voorleggen, onmiddellijk kortingen en snellere concessies.

Zelfs als u nooit overstapt, biedt een schatting van US Cloud u:

  • Echte marktprijzen om Microsofts 'slikken of stikken'-houding aan te vechten
  • Concrete savings targets – our clients save 30-50% vs Unified
  • Onderhandelen over munitie – bewijs dat je een legitiem alternatief hebt
  • Risicovrije informatie – geen verplichtingen, geen druk

 

"US Cloud was de hefboom die we nodig hadden om onze Microsoft-factuur met $ 1,2 miljoen te verlagen."
— Fortune 500, CIO