Consult
A conversation worth having deserves a page you can link to.
Not a popup you dismiss on the way to something else. This is what the session is, who is on it, what we will ask you, and what you walk away with — written down before you commit an hour to it.
What it is
A working session, not a pitch.
Roughly an hour. Your cryptography, our method, and a shared screen. Nobody is going to walk you through a slide deck you could have read here.
Who is on it from our side: [PLACEHOLDER: named roles who attend a consult — founders to confirm before this page goes live]. We are a small company and we are not going to imply a bench we do not have.
What we will not do on the call: quote you a price, assert a date for cryptographically relevant quantum computing, or tell you your exposure score. The first is a scoping decision, the second is a claim we refuse to make, and the third requires a scan.
The five things we will ask
What is in scope, and who owns it?
Discovery is bounded by what someone is willing to point us at. Naming the estate and its owner up front is the difference between a scan and an argument about a scan.
How long does your data need to stay confidential?
This is the Confidentiality Horizon dimension, and it is the one input we cannot observe. A statutory retention period, a contract term, a records schedule — whatever governs it, you know it and we do not.
What is already known to be exposed?
Most teams have a list. Starting from it stops us presenting findings you have been escalating internally for a year as though they were news.
What genuinely cannot change this year?
An external counterparty, a certified appliance, a frozen release train. Constraints are what make a migration sequence real rather than a wish list in dependency order.
Who has to be convinced, and of what?
A board paper, a regulator response and an engineering plan are three different documents. Knowing which one you need changes what we produce.
What you have afterwards
- A written scope: what we would look at, what we would not, and where our detectors stop seeing. This is the same limits language published in the Knowledge Base, applied to your estate.
- Our read on where you sit against the published method — which dimensions we would expect to dominate your scores, and why. Framed as a hypothesis to test, never as a finding, because we will not have looked yet.
- The honest answer on whether AutoPQC is the right thing for you at all. Some estates need an inventory. Some need a regulator response. Some need neither of those yet.
What happens to what you tell us
We take notes and we keep them. We do not need credentials, network access, a certificate export or a key inventory to have this conversation, and you should not send any of those to arrange it. Nothing you say on a consult is published, quoted or used as a reference — including your company name. The retention rules are the ordinary ones: what we hold and how long we hold it.
Ask for a consult
Four fields. No calendar to negotiate with, because we would rather read what you need before proposing a time.
Before you submit
Being straight with you about the mechanics: this goes to a person, not a queue. There is no scoring, no routing rules and no automated sequence waiting for your address — someone reads what you wrote and answers it. If delivery fails you will see an error rather than a success message, so a submission you saw accepted is one we hold. We publish no response window until we can honour one: [PLACEHOLDER: response-time commitment].