Meeting preparation · BB2G’s own position

What BB2G needs
from a security partner.

An ask, and a boundary. Both are BB2G’s own working notes for a partnership conversation — they describe what BB2G intends to request and to withhold, and they characterise no one else.

Confidential working material. These are preparation notes belonging to Born Between 2 Generals LLC. They set out BB2G's own asks and BB2G's own limits. Nothing here represents, commits or describes any other organisation, and no agreement of any kind is claimed or implied.

Ask them to design

  • Identity, credential and access model for humans, organizations, devices and AI agents.
  • PKI and certificate architecture, key lifecycle, crypto-agility and post-quantum transition.
  • Encryption at rest, in transit, in backups and in local/edge data stores.
  • Zero-trust permissions, tenant isolation, privileged access and auditable admin controls.
  • Secure managed mobility for family, school, field and enterprise deployments.
  • Cloud, hybrid and local-first architecture that protects BB2G intellectual property.
  • API gateway, secrets, logging, detection, incident response and compliance evidence.

Protect in the room

  • Show architecture and product requirements — not proprietary source code.
  • Do not expose secret keys, credentials, complete prompt chains or internal agent wiring.
  • Mutual NDA before any deep proprietary technical disclosure.
  • Frame the partner as a security and infrastructure partner, not the owner of the application IP.
  • Ask for an architecture deliverable with boundaries, responsibilities, controls and migration phases.

Bring these numbers, not the ceiling

The three facts that survive scrutiny.

Fact one

10 of 72 are deployed

Measured, and revised downward from a more flattering earlier count. This is the number that makes the others credible.

Fact two

423 addresses answer today

Probed over HTTPS at build time, with each page's served title captured. Re-run the probe yourself.

Fact three

Nothing takes a payment yet

Said first, rather than discovered. Every revenue model here is an intended structure, not a live one.

The highest-value thing a security partner can give before any terms are discussed is independent validation of the pricing and the ceilings — because at present every one of those figures is BB2G's own arithmetic.