Most post-quantum budget requests fail for the same reason. They ask for money against a threat nobody can date, in a year when every other line item has a deadline attached.
There is a better argument available, and it does not depend on predicting when a quantum computer arrives. Public TLS certificate lifetimes are already falling on a published schedule: 200 days today, 100 days from March 2027, 47 days from March 2029. Whatever your renewal process looks like now, it runs roughly four times as often inside three years.
That is the same capability post-quantum migration needs. A complete inventory, known ownership for every entry, and the ability to reissue without a person in the loop. Budget them separately and you build the same thing twice. This kit is the argument for building it once, with the framing, the procurement language and the worksheets to make the case internally.
46%
of organizations have no single named individual responsible for leading their post-quantum migration
66%
in government and public sector, the segment facing the hardest external deadlines
50%
of post-quantum readiness delivered by a certificate automation program, and the hardest half to start
4x
renewal events per certificate at a 47-day ceiling compared with today's 200 days
The myth is you have time. You don't. You're already late.
Ian Farquhar, former Security CTO, Gigamon
What is inside
01
Why this lands in the 2027 budget
The published certificate schedule, and why a deadline set by a vendor compliance roadmap survives a budget committee better than a risk that depends on a forecast.
02
The build-it-once case
Why certificate agility and post-quantum agility are one capability with two triggers, how much of post-quantum readiness a certificate program actually delivers, and what it does not cover.
03
Framing it so it gets funded
Why leading with quantum computing loses the room, and what to lead with instead. Includes a worked example: the certificate expiry that took an entire bank's e-banking infrastructure offline.
04
Putting a number on it
Why certificate failures are a hard stop rather than a degradation, why resolution is slow for structural reasons, and the four inputs to a defensible cost figure.
05
Five procurement clauses you can paste
Requirements language for automated issuance, algorithm agility, post-quantum readiness, certificate authority independence and written evidence. Plus how to read the three answers vendors give.
06
Naming an owner, and a worksheet
The accountability gap, why shared ownership is the most common failure mode, and a seven-role table to fill in before the budget meeting.
Who should use this
- Security and IT leaders building a 2027 budget request for post-quantum or certificate work
- CISOs who need the business framing rather than the technical one
- PKI and security architects being asked to size a migration before anyone has funded it
- Procurement and vendor management teams writing requirements for 2027 acquisitions
- Federal, SLED and regulated-industry teams working to external migration deadlines
Get the kit
Ten pages covering the funding argument, the cost model, paste-ready procurement language and an ownership worksheet. No form.
Download the kit
