Your people leave, and the relationship knowledge usually leaves with them. When the record belongs to the client instead of the seat, practitioner turnover stops destroying continuity, and nobody re-explains themselves to the next partner on the account.
Nothing here is a promise you have to take on faith. Read the public revocation list or check a signed checkpoint yourself.
We're new, so there's no logo wall here and no client count. What there is instead: a live demo you can run yourself, a revocation list published in the open, and signed checkpoints you can verify with our servers out of the loop.
A seat-based CRM cannot offer this because the record is the thing it sells. Here, the record was never the firm's to hold.
A client shares their record with the firm, scoped to what they agree to. Any practitioner on the account the client authorizes can read it, and each gets their own revocable grant.
Entries stay attributed to whoever wrote them, not to the firm. A client can see exactly who said what, even years and several consultants later.
A consultant leaves, a seat is reassigned, or a client is handed to a new partner. The record stays intact, and the client decides whether to extend a grant to the new practitioner.
A seat-based CRM stores the client relationship inside the firm's account, tied to whoever holds the seat. That's the one thing changed here.
| A typical seat-based agency CRM | Pupul | |
|---|---|---|
| Who owns the client relationship | The firm's account, tied to the seat | The client |
| What happens when a consultant leaves | Relationship history often leaves with them, informally | Stays in the client's file, attributed and intact |
| What a new partner on the account sees | Whatever notes made it into the CRM, if any | The client's own record, if the client shares it |
| Can an entry be backdated | Usually, notes stay editable by whoever holds the seat | No, append-only and checkpointed the moment it's signed |
| Client's right to revoke a seat's access | Rarely a client-facing option | Always, and the revocation is published |
A comparison of designs, not a claim about any one vendor. Keep your billing and project tooling: nothing here replaces them.
Plain numbers, no hidden per-client fee. Enterprise and white-label terms are quoted with an SLA, never self-serve.
Most firms start with one practitioner seat, then move to the firm license once more than one person is reading the same clients.
See firm licensingElapsed, attributed time is the one credential that can't be minted on demand, staffing change or not. Everything below exists to make that claim checkable by someone who doesn't trust us, which on this page includes you.
Entries are added, never edited or reordered. No write path into the past, for a consultant, the firm, or us.
The ledger publishes signed checkpoints. Anyone can prove an entry existed at a point in time without our permission.
Every entry carries the name of whoever wrote it. The firm licenses the rail; it never becomes the author of a client's file.
Each practitioner on an account gets their own scoped, revocable grant. A firm license widens who can be granted access, not what's automatically shared.
Every revoked grant publishes to a list anyone can read, including the count.
Published keys, a public revocation list, and signed checkpoints let a receiver verify a grant with our servers out of the loop.
Start with one practitioner seat free, or talk to us about licensing the whole firm.