Admin

Governance ships with it.
Not bolted on after.

Teams, permissions, record ownership and agent spend are all settings, not a services engagement.

The admin surface is small because the defaults are safe

There is no governance module to buy and no services engagement to book. It is 4 settings screens, and 3 of them you will read once.

What a reviewer checks first

Nothing is deleted

Removing a user deactivates them. What they produced stays on the records they touched.

Nothing is ungated

Every feature has its own View and Edit box, and the route behind a gated control refuses the request too.

Nothing is a surprise

Each run is priced before it starts, and the spend report says where the credits went.

Users and teams

Onboarding a rep is picking a team

Access comes from the team, so you review teams rather than people. Invites are bulk, and 1 team applies to the whole batch. Nobody can end up without a team: moving someone out and deleting a team both make you name where they land.

Permissions

The matrix is enforced, not decorative

Permissions belong to a team, and 4 System teams ship before you make any. Every feature then gets its own View box and Edit box. The route behind a gated control refuses the request too, so the matrix is enforcement rather than decoration.

Ownership

Every record gets an owner without anyone assigning it

An ordered stack, read top to bottom, first match wins. There is no run button because the rules fire on their own once a record finishes qualification, and the owner they set syncs to the CRM seat.

Credits

Credits, not seat licenses

The wallet sits in the header: the balance, what is left of the grant, and when the next one lands. You pay for work done, not for people who might log in.

Spend

Where the credits went, by agent

A 12-week curve beside the balance, then all-time spend per agent grouped the way the agent library groups it. The outlook runs 6 months back and 12 forward: the solid line is the real balance at each close, the dashed one adds the grants already scheduled.

What your security team will ask
  • Never used to train models

    Your CRM data, research outputs and agent activity are never used to train or fine-tune models. Not by us, not by our providers.

  • Your workspace is isolated

    Each workspace is logically isolated, so your data is never accessible to another customer.

  • You control retention

    If you cancel, your data is returned or deleted, your choice. If you make no request, all personal data is permanently deleted within 30 calendar days.

The detail, the sub-processors and the DPA are on Security and trust.

Your material stays yours

Under the MSA, everything you upload and everything the agents produce from it is yours.

SOC 2Audited
ISO 27001Certified
GDPRCompliant

Hand this page to your security team

We will walk your admin and your reviewer through the matrix, the ownership rules and the spend report, on a real workspace.

Request a demo