How government evaluators actually score RFPs

Government procurement uses weighted scoring matrices. Every criterion has a defined point value, and evaluators score each section independently. The weights are typically published in the RFP document itself — which means you know exactly what matters before you start writing.

For SaaS procurement, the typical scoring breakdown looks like this:

30–50%
Technical requirements
Product capabilities, feature completeness, integration support, scalability, user experience. Does your product do what the RFP asks for?
20–30%
Security and compliance
Data residency, encryption, CLOUD Act status, security certifications, breach notification. This section is growing — modern SaaS RFPs allocate 20–30% here.
20–30%
Pricing
Total cost of ownership, licensing model, implementation costs. Canadian suppliers get a 10% price reduction for evaluation purposes under Buy Canadian.
25%
Canadian content (Buy Canadian)
New since December 2025. Up to 25% of total score allocated to Canadian value-added content. Development, R&D, hosting, and support in Canada all count.

The key insight: security/compliance and Canadian content together can account for 45–55% of the total evaluation. This is where Canadian SaaS vendors have a structural advantage that no US competitor can match.

Read the Basis of Selection. Every government RFP includes a “Basis of Selection” or “Evaluation Procedures” section that tells you exactly how bids will be scored. Read it before you write a single word. Structure your entire response around it. Vendors who mirror the RFP’s evaluation structure in their response make it easy for evaluators to award points.

The sovereignty scoring advantage

Sovereignty is no longer a secondary consideration in government procurement — it’s baked into the scoring structure. Here’s where Canadian vendors pick up points that US competitors structurally cannot:

Security and compliance section (20–30%)

When the RFP asks about data residency, jurisdiction, and CLOUD Act exposure, your answer as a Canadian vendor is short and clean. US vendors must explain their mitigation measures, document their limitations, and hope the evaluator gives them partial credit. You get full marks.

Include in your response:

Canadian content section (up to 25%)

Under the Buy Canadian policy, procuring departments must allocate up to 25% of the evaluation score to Canadian value-added content. For a SaaS company, Canadian content includes development team location, R&D activities, hosting infrastructure, support operations, and IP ownership.

If your entire operation is Canadian, you can claim close to 100% Canadian content — capturing the full 25% advantage. A US vendor with a Canadian sales office and Canadian data centre gets partial credit at best.

Price evaluation (20–30%)

Canadian suppliers receive a 10% reduction to their financial proposal for evaluation purposes. Your $100,000 bid is evaluated as $90,000. This doesn’t change the actual contract price — it’s a scoring mechanism that advantages Canadian vendors in the evaluation.

Free Index listing, $249 Sovereign Badge, $499 Competitor Report. Build your RFP toolkit.
See Vendor Services →

How to beat Microsoft (and Salesforce, and AWS)

Small Canadian SaaS companies can and do beat the global incumbents in government procurement. Here’s how:

Don’t compete on feature count

Microsoft has more features than you. That’s not the game. Government evaluators score against the specific requirements listed in the RFP, not against a feature catalogue. If the RFP asks for 15 capabilities and you deliver all 15, you score the same as Microsoft on technical requirements — regardless of the 500 features you don’t have.

Compete on sovereignty and compliance

Microsoft is US-incorporated and CLOUD Act exposed. Their Canadian data residency is a geographic configuration, not jurisdictional protection. In the security/compliance section, your sovereignty story is cleaner, simpler, and scores higher. This is 20–30% of the evaluation that you win structurally.

Compete on Canadian content

Microsoft’s Canadian content percentage is limited to their Canadian office operations — a fraction of their global development, hosting, and R&D footprint. Your Canadian content is likely 80–100%. That’s up to 25% of the evaluation where you have a mathematical advantage.

Compete on support and proximity

Government buyers value responsive support in their time zone, in their language, with their regulatory context. When a federal department in Ottawa has a problem at 3pm on a Tuesday, they want to call someone in Canada — not a global support queue routing to Bangalore. Make your support model a selling point, not an afterthought.

Compete on price

Your 10% price evaluation advantage under Buy Canadian means you can price higher than a US competitor and still score better. If your total cost of ownership is within 10% of the US vendor, you win on price evaluation. Combined with your sovereignty and Canadian content advantages, the math is overwhelmingly in your favour.

The combined advantage: A Canadian SaaS vendor competing against a US incumbent captures scoring advantages across security/compliance (20–30%), Canadian content (25%), and price (10% reduction). Even if the US vendor has a technically superior product, the Canadian vendor can win on total evaluation score. This is the structural shift the Buy Canadian policy created.

Structuring your RFP response

Government RFP responses follow a specific format. Here’s how to structure yours for maximum score:

Mirror the RFP structure

Use the same section numbers and headings as the RFP. If the RFP has 12 evaluation criteria, your response should have 12 clearly labelled sections addressing each one. Make it effortless for evaluators to find your answers and award points.

Answer the question first

Start every section with a direct answer to the evaluation criterion. “Yes, we comply. Here’s how.” Then provide the supporting detail. Evaluators review dozens of proposals — the ones that make their job easy score better.

Use their language

If the RFP says “data residency,” use “data residency” in your response — not “data hosting” or “cloud deployment.” Evaluators are looking for keyword matches against their scoring rubric. Use their exact terms.

Provide evidence, not claims

Generic claims get low scores. Specific evidence gets full marks. Instead of “we prioritize security,” write “SOC 2 Type II audited annually, most recent audit completed [date], letter of attestation attached as Appendix C.” Instead of “Canadian-owned,” write “Incorporated in [province], Canada. Federal corporation number [number]. No US subsidiaries or operations. Sovereign Badge verification attached as Appendix D.”

Include appendices

Attach your trust documentation as appendices that evaluators can reference: SOC 2 letter of attestation, Sovereign Badge, Competitor Sovereignty Report, subprocessor list, DPA template, insurance certificates. Each appendix supports a specific evaluation criterion.

After submission

Government procurement doesn’t end at submission. Here’s what to expect:

Build your RFP toolkit. Get listed in the Sovereignty Index (free), earn a Sovereign Badge ($249), or get a Competitor Report ($499) to attach as evidence in every government RFP response.
See All Vendor Services →