Veterinary record-exchange infrastructure

Trust should travel with the record.

OneVet is the consent and verification layer between veterinary systems—so a clinic can trust the right history, for the right animal, at the moment care moves.

Working proof, not a concept render. Synthetic data · Browser-based demo · First institutional round

The record route

PatientPepper · Canine
PermissionPurpose-bound · 72h

The broken moment

Pepper is here. Her history is not.

A move, a trip, or an urgent visit turns a routine handoff into phone calls, PDFs, and uncertainty. The record usually exists. The receiving clinic still has to establish whether it is complete, authorized, current, and attached to the right patient.

FIRST WEDGE

Clinic-to-clinic clinical continuity

Start with the information that changes care—medications, sensitivities, vaccines, labs, and the recent clinical story—not another document wallet or vaccine-only compliance tool.

See the handoff protocol

One story, four lenses

Start with the outcome. Go deeper when useful.

Each cut answers a different diligence question. Nothing autoplays, and the technical layer stays available without crowding the opening case.

BUSINESS + CATEGORY

The case for trusted movement

A concise investor narrative: the broken handoff, the trust protocol, the business model, and the round.

  • The user and clinic problem
  • The infrastructure wedge
  • Pricing, economics, and ask

Five bounded acts

A handoff that can explain itself.

OneVet does not become the new record system. It creates a verifiable passage between systems and preserves the source’s authority.

  1. 01

    Verify identities

    Bind the animal, owner, source, and intended receiving organization.

  2. 02

    Scope permission

    Recipient, purpose, record categories, and time window are explicit.

  3. 03

    Preserve provenance

    Facts remain linked to exact source evidence; extraction is reviewable.

  4. 04

    Gate by policy

    Jurisdiction-aware rules stop unsupported disclosure and route ambiguity to humans.

  5. 05

    Deliver atomically

    The package and tamper-evident receipt succeed together—or nothing is disclosed.

The product promise
The right history. The right recipient. A receipt both sides can verify.

Run the handoff yourself

Receiver-free distribution

Charge the workflow owner. Remove friction from the receiver.

The initial model keeps owners and verified receiving clinics free, then monetizes automation, connectors, orchestration, and higher-volume infrastructure.

ACCESS

Owner passport

Free

Consent, history, journey status, and receipts.

NETWORK

Verified receiver

Free

Accept and verify a handoff without a procurement hurdle.

SCALE

Network

$149/location/mo

Plus $0.50 per handoff, with a $3,000 organization minimum.

INFRASTRUCTURE

Platform / OEM

$10k/mo

Plus $0.25 per handoff for embedded exchange infrastructure.

PLANNING CASE

These are modeled targets, not achieved company results. Inputs: 75 handoffs per Pro location per month, 82% gross margin, and $2,000 fully loaded CAC.

Typical Pro MRR$267.75$249 + 25 overage handoffs
CAC payback9.1 moGross-margin adjusted
10% location case$11.02MARR at planning volume
Labor break-even11 minSaved per handoff at $19.39/hr
See the bottom-up math and sources

Location basis

The Census Bureau reports 34,296 U.S. veterinary-services employer establishments in 2023. It includes testing and non-companion-animal services, so we treat it as an upper bound, not an automatically serviceable market.

U.S. Census CBP source opens in a new tab

Base ARR

34,296 × $249 × 12 = $102.48M. At 75 handoffs per month, the modeled total becomes $110.19M. A 10% location case is $11.02M ARR.

Efficiency target

Bessemer’s SMB cloud benchmark recommends sub-12-month CAC payback. OneVet’s 9.1-month figure is a modeled target, not measured performance.

Bessemer benchmark opens in a new tab

The ask

$2.5M to reach repeatable exchange.

Approximately 23.8 months of planned runway at an average $105,000 monthly burn—aimed at design-partner proof, production connectors, and the security and policy work an infrastructure category requires.

Product, security, reliability45%
Connectors + design partners25%
Policy, identity, privacy, legal15%
Founder-led distribution10%
Reserve5%

MILESTONE GATE

25design-partner locations
5production connectors
50kcompleted handoffs
250paying locations
82%target gross margin

For technical diligence

The hard parts are modeled as behavior.

The prototype demonstrates the product logic. It does not claim production integrations, regulatory certification, or a live exchange network.

01

Formal invariants

TLA+ models test that authorization, release, receipt, and revocation cannot reach unsafe states across interleavings.

Modeled: exchange + policy gate
02

Signed policy context

AION artifacts package human-readable rules with provenance and verification evidence to gate AI-assisted reasoning.

Included: California demo policy
03

Rust execution target

The proposed production spine uses typed, memory-safe services for bounded exchange, identity, connectors, and audit evidence.

Target architecture, not deployed network
WORKING NOW

End-to-end synthetic handoff, scoped consent, source-linked fact review, fail-closed wrong-recipient check, signed receipt verification, revocation, policy artifacts, and model-check results.

NEXT TO PROVE

Production identity, durable key custody, practice-system connectors, live policy operations, security review, and design-partner throughput.

Continue the conversation

If trusted movement belongs in the veterinary stack, let’s compare notes.

Tell us which lens matters most—market, distribution, product, policy, or infrastructure. Your note stays in the browser until you choose to open your email app.

No tracking pixel. No silent submission. You stay in control.