The opportunity was an open, competitive procurement for a smart building program and platform. It was our client’s clearest route into public sector real estate technology, and on paper they were built for it.

The proposal was a different matter, for three reasons:

The first was a translation problem. Our client’s strongest platform work sat in commercial and private sector settings, not in government building operations. Every capability they needed to demonstrate was real and delivered. None of it was described in the language a public agency uses when it talks about portfolio performance, integrated systems, and centralised monitoring. Evidence that an evaluator has to translate is evidence that scores below its actual worth.

The second was assurance. Our client’s security attestation was still in progress at the time of bidding. In a procurement where a public agency is asking pointed questions about who touches building systems data and where that data lives, an unqualified claim about certification is the kind of thing that survives the write-up and dies in the debrief. The honest answer needed to be stronger than the vague one.

The third was the operating environment. The agency does not run its real property services in isolation, and any new technology vendor entering that portfolio has to show it can work alongside an established facilities service ecosystem without disrupting it. Very few bidders address this directly. Most write as though they are arriving at an empty site.

Then add the field. Public sector smart building work draws in large building automation vendors, national systems integrators, and incumbent service providers. Our client was the smallest name on that list.

We read every document, annex, and addendum end to end before drafting a single sentence.

From that we built a compliance crosswalk mapping every mandatory requirement, form, certification, deadline, and submission condition to a named owner and a live status. That crosswalk surfaces the quiet disqualifiers early enough to solve them, rather than discovering them during upload week.

We then reverse-engineered the scoring. Each evaluation criterion was mapped to the section that would answer it, sections were weighted against the points available, and the writing effort was concentrated where the marks actually sat rather than spread evenly across a document that looked balanced and scored average.

On assurance, we took the harder line deliberately. Rather than writing a bare certification claim and hoping no one asked, we stated exactly what was in place, gave a clear completion timeline for what was still underway, and set out the controls, hosting region, and data residency arrangements behind them. A precise answer about where a Canadian agency’s building data sits reads as governance maturity. A vague one reads as something to probe.

Accessibility was handled the same way. For a public sector buyer, accessibility conformance is not a closing paragraph, so the applicable standards, the testing method, and the named accessibility lead were written into the technical response where an evaluator would score them.

Last, we set the win themes: a small number of the agency’s priorities, written as agency outcomes rather than vendor capabilities, and threaded through every scored section so an evaluator skimming opening sentences would still meet all of them.

Full RFP Response: complete technical narrative covering solution architecture, integration approach, phased delivery with milestone gates, methodology, staffing and governance structure, risk mitigation, transition and handover, cover letter, executive summary, and conclusion. Every scored section front-loaded so the opening sentence carries the scoring claim on its own.

Compliance and Submission Control: full requirement crosswalk with risk ratings; mandatory forms tracked to completion; addenda monitored and incorporated; certification and insurance thresholds checked against current coverage with remediation lead time; portal submission packaging and deadline control.

Strategy and Win Themes: rubric-weighted section plan; win-theme register traced across every scored section; positioning against incumbent and large-integrator competition developed without naming competitors; technical commitments made specifically rather than deferred to a discovery phase.

Evidence and Reference Architecture: a documented proof-point bank separating verified claims from claims requiring client confirmation, so nothing confident went in unbacked, and a callable reference set built to survive an evaluator actually telephoning the contact.

Document Production: figure production, template compliance, and final assembly to the buyer’s file structure and formatting rules, with a single deliverables matrix controlling what went into which upload file and when.