Skip to content

Bijection for B2B SaaS

Who is this customer? One answer, not four.

Product database, billing, CRM and support joined into one account, with every admin change reviewed.

Get started

Ask who a customer is and you get four answers: the plan in Stripe, the seats in your product database, the owner in Salesforce and the open tickets in Zendesk. The admin panel that fixes any of them writes straight to production, and nobody reviews what it did.

Bijection joins those records into one account and turns each admin write into a named action with a preview, an approver when it matters, and a record of who ran it.

  • Trial extension

    Starts: A customer asks for more trial time

    1. Check usage, seats and open tickets on the account.
    2. Extensions past your threshold wait for an approver.
    3. The new end date is written to billing and the product database.

  • Usage billing check

    Starts: Every month, before invoices go out

    1. Compare metered usage with the invoice lines in Stripe.
    2. Mismatches become a list, each with the rows that disagree.
    3. An owner corrects each one or marks it explained.

  • Incident credits

    Starts: An incident is closed

    1. Find the accounts that were active during the incident.
    2. Preview the credit for each one.
    3. Apply every credit in one reviewed change, recorded against the incident.

  • Seat overages

    Starts: An account uses more seats than its plan

    1. Show the seat count, usage and plan together.
    2. The account owner decides to upsell or allow it.
    3. Plan changes are written to Stripe and the product database.

  • Workspace deletion

    Starts: A customer asks to delete their workspace

    1. Preview every record the deletion touches.
    2. An engineer approves.
    3. Each system is re-read to confirm the data is gone.

  • Failed payments

    Starts: Stripe reports a failed payment

    1. Tell the account owner, with the account’s usage and history.
    2. Wait for the retry or a new card.
    3. Downgrades after the grace period need an approver.