Talking notes — WidePoint meeting

What this covers: what to say, in what order, and what to say back. Logistics and timings are in the binder runsheet.

---

The opening, in four sentences

One inventor built a single body of evidence, identity and provenance infrastructure that spans seven regulated domains. They are not seven product ideas — they are seven applications of the same small set of cryptographic and tokenization primitives, all resting on one core.

That core is the Blindfold Engine. Once you understand it, the rest of this list stops reading like seventy-two unrelated ideas and starts reading like one identity and provenance platform expressed across many regulated verticals.

This is a partner search, not a product pitch.

The frame to hold all morning

Everything in front of you is ordered, and the ordering is not my opinion of my own work. Each item carries five scores — revenue ceiling, build readiness, IP protection, fit with your business, mission impact — and the weights are on screen. Tell me which of those matters most to WidePoint and the list re-ranks in front of you.

Say this out loud once: whichever order you choose, that is the order I hand over.

Why the pairing works — the version to lead with

You already sell PKI-based identity credentialing, telecom lifecycle management and cybersecurity managed services into federal agencies and regulated enterprise. This is not a departure from that business, it is an extension of it.

• Compartmented Delivery, One-Way Derivation, Zero-Knowledge Observer are primitives that OEM straight into your own PKI stack. Three items, $110M–$330M of combined ceiling, and the purest technical overlap in the portfolio.
• The Standing Business Token closes the STIR/SHAKEN gap — it verifies the business calling, not just the number. That is the telecom-fraud space you already operate in.
• Defense Parts Hidden Marking is DoD supply-chain integrity, sold through federal relationships you already hold.

The point: this gives you new patent-pending IP to sell into markets you already have distribution for. It does not ask you to enter markets you do not understand.

The numbers, said carefully

The full list carries an illustrative ceiling of $2.0B to $4.5B a year. That is the size of the opportunity space and not a plan, and I will say so before anyone else does.

The real conversation is the twenty-five Tier-1 Build Now items: $1.58B to $4.51B of ceiling between them, and the subset most directly sellable through the distribution you already own.

Then bring it down to earth: no per-item financial history exists yet. Every ceiling is TAM math — institution or population count times a defensible price point — published that way so it can be argued with rather than guessed at. Half of one percent of the Build Now base is still an eight-figure business in year one.

The IP position, stated plainly and first

Four engines are already copyrighted: Strong Room, Blindfold, Vote Verification, and Strong Chain / Lock Chain. Safe Elections files tonight, along with one further engine still to be named.

Then the sentence that matters most: copyright protects the written work and the source code. It does not protect the mechanisms. Those need the provisional patent filing, and the twelve-month public-disclosure clock is already running.

Twenty-seven Tier-A mechanisms sit behind that clock. It is why sequencing is a real constraint and not a preference, and it is the reason nothing goes into a technical review before the filing that protects it.

Hold the line on depth: enough mechanism detail for them to evaluate fit, no more. Deep technical specifics go to follow-up sessions under the NDA.

The sequence to propose

Blindfold Engine first, because nearly everything else sits on it. Then the Comms family, because it is the closest thing in this portfolio to what WidePoint already ships. Then the money and telecom fraud mechanisms that intersect the telecom management business.

Offered as a starting shape. Ask them to correct it.

What to ask them

• Which of your people owns the technical review, by name, and what does that review need to see?
• What pricing validation can you offer? Real numbers replace my ceilings the day they exist.
• Which existing federal or enterprise contracts could carry Vote Verification, the Veteran Two-Vault Record, or the Custody family as an add-on line?
• Licence, co-development, or transfer — which shape does your side prefer to work in?
• What can you retain after today, and under what terms?

Four answers to have ready

"How much of this actually exists?" — Four engines are copyrighted and written. Twenty-seven mechanisms are documented to patent-counsel standard in the Invention Disclosure Workbook. The rest is specified. Every row says which.

"Why is one person holding seventy-two things?" — Because they are seven applications of the same primitives. The second application of a mechanism costs a fraction of the first.

"These ceilings look enormous." — They are ceilings, not forecasts, and they are TAM arithmetic you can check. Tell me which price point you would defend and I will change it in front of you.

"What do you actually want from us?" — Distribution, engineering depth, and a security review. The order of the build is negotiable; the crypto core going first is not.

Close

Agree the weighting. Export the ranked list and the Build Now pack in the room. Name a point of contact on each side and a date for the technical review.