You don't lose bids because of capability. You lose because your proposal doesn't score the way you think it does.

25 years in the evaluation processes. I identify where a proposal may be losing points from the first few pages. A technically strong solution doesn't guarantee a high score. It depends on how proposals are likely to be read, perceived, and scored. Send me your draft. I'll show you where you may be leaving points on the table.

  • 25+ Years in Evaluations
  • Public & Private Sector
  • EN / FR
  • Fast Turnaround

It isn't capability.
It's interpretation.

You know what you can deliver. The problem: evaluators don't see it the way you do. And what they see determines the score.

1
The proposal checks every box, and still scores low.

Evaluators bring risk filters shaped by past failures. What scores high resolves that anxiety. Checking boxes doesn't.

2
Your best people write the worst-scoring sections.

Dense content that requires interpretation scores lower in consensus. Four evaluators reading it independently each read it differently, and consensus defaults to the lowest defensible score.

3
You rarely find out why you actually lost.

Post-evaluation feedback is constrained. You hear “didn't meet the threshold.” You never hear “your governance section made us nervous about everything after it.” The real reasons often stay in the evaluation room.

Here's what's actually happening inside the evaluation room.

What evaluators see

4
The governance narrative collapses under scrutiny

Most teams describe governance as org charts. Evaluators look for evidence it has been tested under pressure. If it reads as aspirational, the doubt carries into every section that follows.

5
Demonstrations prove capability, not evaluator confidence

Evaluators ask: “Can I defend this selection?” A technically impressive demo that introduces uncertainty loses to a solid one that feels defensible.

6
Subjective criteria get treated as the softer part

They're not. Evaluators look for quantifiable anchors: numbers, timelines, named roles. Without anchors, each evaluator interprets differently, and consensus defaults to the lowest defensible score.

7
The proposal creates risk signals the team doesn't see

Overly optimistic timelines, vague resource commitments, generic contingency language. These read as “hasn't done this at this scale.” A committee that senses risk doesn't score it as ambitious. It scores it as unproven.

8
Transition plans are the most scrutinized and least prepared section

Evaluators look for realistic planning: named dependencies, knowledge of current-state, contingencies, acknowledgment of unknowns. Overconfidence scores as inexperience.

9
Socio-economic commitments read as performative

Evaluators distinguish structural commitment from compliance decoration. Listing a subcontractor is not a strategy. A superficial section doesn't just score poorly. It casts doubt on the entire proposal.


Send me your proposal. I'll show you how it is likely to be interpreted and where it may be losing points.

Proposal Scoring Assessment & Alignment

Send me your draft. I assess how proposals are likely to be read and interpreted against evaluation criteria. You get back exactly where points are being left, what to change, and why. Criterion-by-criterion. No fluff.

Deliverables

  1. 1Interpretation-based scoring assessment with specific changes
  2. 2Evidence gaps flagged
  3. 3Subjective criteria anchors
  4. 4Risk perception signals identified
  5. 5Compliance issues caught

Complementary engagements

Solicitation Intelligence

Before you write, understand how the evaluation is structured. I decode the solicitation architecture: what the scoring logic is designed to measure, where evaluator interpretation has the most latitude, and where the highest-value points sit. Available standalone or as a precursor to a scoring assessment.

Demonstration & Presentation Preparation

For procurements with presentations, demos, or interviews. I prepare teams for how evaluators observe, not just what they ask. Goal: defensible selection confidence, not technical admiration.

Post-Evaluation Intelligence

After results are in, I extract patterns from debriefs, scoring, and outcomes. Institutional knowledge that improves your next bid, not just this one.


The difference shows up in the score.

What most teams do
What changes after a scoring assessment
Write to stated requirements
Write to how criteria are actually interpreted and scored
Demonstrate capability
Communicate capability in language that resolves evaluator concerns
Treat subjective criteria as softer requirements
Inject measurable anchors that drive higher consensus scores
Present governance as structure
Present governance as evidence of operational resilience
Respond broadly to every opportunity
Focus resources on winnable bids with scoring alignment
Learn from limited debriefs
Build institutional scoring intelligence that compounds across bids

Where the score is determined.

I don't need to be involved in every step. I intervene where the score is determined.

1
Before the RFPSolicitation Intelligence
Understand the evaluation architecture before you start writing. Decode scoring intent, identify where the highest-value points sit.
2
QualificationEvidence Alignment
Ensure clarity and defensibility at the qualification gate. Misalignment here eliminates you before the competition begins.
3
Proposal Scoring AssessmentCore Engagement
I assess how your proposal is likely to be interpreted and where scoring risks exist. Criterion-by-criterion. Evidence mapping. Risk signal detection. This is where the score is determined.
4
DemonstrationEvaluation Performance
Prepare the team for how evaluators observe. Scored on selection confidence, not technical depth.
5
After the DecisionPattern Extraction
Analyze outcomes and scoring patterns to build institutional intelligence for the next pursuit.

25 years at the heart of evaluations

I'm Suzy Bouchard. For more than 25 years, I've worked at the heart of evaluation processes for complex competitive procurements, public and private sector. I've contributed to solicitation design, evaluation criteria, and participated in complex evaluation processes. I understand how criteria are interpreted through direct experience in evaluation processes.

I assess how your solution is likely to be interpreted and where it may impact scoring outcomes. I work with organizations competing for high-value contracts where the margin between winning and losing comes down to how capability is communicated to a risk-conscious evaluation committee.

I work fluently in English and French, supporting bilingual procurement environments where nuance in both languages directly impacts how proposals are interpreted and scored.


Ready to see where you're leaving points?

Send your draft. You get back a written assessment, criterion by criterion, in 5 to 10 business days.

Best engaged before your submission deadline.

Response within one business day. Conversations are confidential.

info@agilipro.ca
(819) 230 6856

Not ready to send yet? Let's talk first.

Response within one business day. Conversations are confidential.