Per-seat spending limits
Your organization buys AI credits into one shared pool. Per-seat spending limits let you cap how much of that pool each loan officer can draw in a month, without ever moving credits around. Raising a limit is free and instant.
What it is
Your organization buys AI credits into one shared pool. Per-seat spending limits let you put a monthly ceiling on how much each loan officer may draw from that pool. A loan officer with a 300-credit limit can generate up to 300 credits’ worth of content a month. After that, they’re paused until the next month, or until you raise the number.
Each loan officer sees their own number: how much they’ve used, how much they have left. They do not see the organization’s total pool or anyone else’s usage.
The whole design rests on one idea: a limit, not a wallet.
- A wallet would give each loan officer their own separate bucket of credits. The problem: an underused person’s credits sit stranded. If one loan officer barely generates and another is slammed, the organization has to buy more credits for the busy one while the first person’s go to waste.
- A limit leaves all the credits in one shared pool and just governs how much each person may pull. Unused capacity from a quiet seat is always available to the rest of the organization. The moment you raise someone’s limit, they can use it, for free, instantly, with nothing purchased, because the credits were already there.
A limit is a steering wheel, not a fuel tank. Adjusting it costs nothing.
The problem it solves
Without limits, one loan officer can burn the whole organization’s credits in a week and everyone else is stuck. With naive per-person wallets, the organization overspends to cover uneven usage. Limits give you control over pace without stranding anyone’s capacity or forcing a purchase.
Who it’s for
You, the org admin, set and adjust each seat’s limit. Every loan officer in your organization lives within theirs.
How it works
A loan officer approaches their limit
As they generate content, their own usage view shows what they’ve used and what they have left, so they can see it coming (for example, 280 of 300 credits used) instead of hitting a wall mid-generation.
They hit their limit
The product tells them the truth: they’ve used their monthly allowance, the organization still has credits, and they should ask their admin to raise their limit. It points at the person who can fix it in one click.
It does not tell them “your company is out of credits” and send them to a checkout page. Those are two different situations, and the product keeps them apart on purpose:
| What happened | What it means | The fix |
|---|---|---|
| A loan officer hits their limit | The org has credits; they’ve used their share | You raise a number, free |
| The org is out | Nobody can generate | The org buys more credits |
Telling a loan officer “your company is out of credits” when a colleague still has room would push the organization to buy credits it already owns.
You raise (or lower) their limit
Adjust the seat’s monthly ceiling at any time. Because the credit pool is shared, raising a limit doesn’t purchase anything and doesn’t move credits between people. It simply lets that seat draw more from the pool that already exists.
Good to know
- Defaults: new seats provision with a sensible limit, 300 credits for a loan officer and 900 for an org admin (an admin produces seeds and governs the account, so they get more). Both numbers are adjustable per organization, and any individual’s limit can be raised or lowered at will.
- No limit is a valid setting: leaving a limit blank means no limit for that seat.
- Only you can raise a limit. A loan officer cannot raise their own ceiling.
Reward mechanics, such as granting a bonus pack to a top performer, are a natural extension of this same machinery but are not built yet.