Abraxas North Star

Become inevitable — not bigger

One page. Every feature, screen, and outreach email should satisfy these.

One sentence

Abraxas removes redundant verification so trusted people and trusted assets can move faster — with only the minimum information needed, shared only when it's needed.

CUDA (platform)
Every credential issued today works everywhere tomorrow.
Product
Trust as an API. Passport is the UX.
Becker pitch
Every company keeps asking for the same information. We make that happen once.

Principles

  1. 01
    Remove the imagination gap

    Show. Don't explain. Replace abstract labels with outcomes people can picture.

  2. 02
    Verify once. Never ask twice.

    Every repeated upload is a tax on liquidity. Reuse is the product.

  3. 03
    Ask for the minimum proof

    Partners get yes, no, or review — never a document folder by default.

  4. 04
    One action. One outcome.

    Every screen has one primary CTA. If there are two equals, simplify.

  5. 05
    Every feature reduces friction

    If it adds steps without removing repeated work, it probably shouldn't ship.

  6. 06
    Verification before tokenization

    Trust creates assets. Assets don't create trust.

  7. 07
    Build systems, not demos

    If it can't survive without you in the room, it isn't finished.

  8. 08
    Every credential should become reusable

    Value compounds when proof travels across partners without re-collection.

  9. 09
    Partners integrate once

    Everything else should come from policy — not another bespoke integration.

  10. 10
    Five-year-old test

    If someone can't explain Abraxas after using it once, keep simplifying.

Phases — remove friction before adding surface area

Phase A
Remove friction

Finish the loop. Nothing breaks. A five-year-old can get through it.

  • Session + wallet bind reliable on mobile
  • No duplicate profile or wallet flows
  • One home for verification, wallets, and access

Exit: The loop is boring — it works every time without explanation.

Phase B
Create undeniable proof

One operator. One issuer. One relying party. One completed flow. Measure everything.

  • Onboarding time · documents avoided · approval time
  • Drop-off · support tickets · repeat users
  • One reference quote with numbers

Exit: One operator says: this saved us time and guests completed onboarding.

Phase C
Productize the story

Package technology as outcomes — never as infrastructure jargon.

  • Never upload your driver's license again
  • Share only what they're asking for
  • Verify once · use everywhere

Exit: A non-technical operator explains Abraxas in one minute without help.

Phase D
Scale systems

Operator onboarding before operator volume — not more features.

  • Implementation guide · pilot metrics · API examples
  • Partner success playbooks · support docs
  • Issuers and relying parties expand from proof, not pitches

Exit: 100 operators signing tomorrow breaks operations — not trust in the demo.

Before every significant build

Write a one-page memo:

  • Objective — what problem?
  • Why now — highest leverage?
  • Success metric — how do we know it's done?
  • What we're not doing
  • Decision — merge, iterate, or discard

Alex Becker test: if you deleted half the homepage, would conversions go up? Ask before every PR.

Design partner outreach →Homepage workflowHome →