SubhX AI· signed in as Priya
Daily capHow much casual leave do I have left, and can you put in a day off for Friday?
You have 6 days of casual leave left this year. I've drafted Friday off for you — have a look and confirm if that's right.
Needs your confirmation
Apply for leave · Casual leave
Friday, 24 July 2026 · 1 day · reason “Personal work”
Every lookup above ran with Priya's own permissions — the same ones she signs in with. The leave request is submitted only when she presses confirm, as the ordinary action her account would have performed anyway.
Illustrative — what the assistant can reach depends entirely on the person asking.
What you get
An assistant you can actually let near your data
Helpful where your team already works, bounded by the permissions they already have, and answerable to an admin who decides who gets it and what it may spend.
Always a click away
A floating assistant sits in the corner of the signed-in screens across your web portals. Ask a question where you are, instead of stopping what you were doing to go and find the answer.
- On your signed-in screens, not one lone page
- Opens in place — you never lose your context
- Replies stream in as they are written
Ask in plain language
No query syntax, no menus to learn. Describe what you want the way you would to a colleague, and the assistant works out which part of the workplace to look in.
- Plain-English questions, plain-English answers
- Follows a conversation across several turns
- Tells you what it is checking as it goes
It works inside your permissions
This is the part that matters. The assistant reaches your workplace through the same permission checks you do — so it can only ever see and do what you could already see and do.
- Your role decides its reach, not the other way round
- Never crosses into a colleague's data
- Never crosses into another organisation
Nothing changes without your say-so
When the assistant drafts something that would write to your workplace, it does not just do it. The draft arrives as a distinct confirmation card and waits.
- Reads happen freely; writes always stop and ask
- A separate card shows exactly what will be submitted
- Nothing happens until you press confirm
Per-person access
An add-on your whole organisation is billed for should not be forced on your whole organisation. An admin decides person by person who actually gets the assistant.
- Switch it on or off for each employee
- People without a seat see no trace of it
- Grant and revoke as your team changes
A cap for every person
Give each person their own daily ceiling, set in millions of tokens, so a single enthusiastic user can never spend the whole month's budget in an afternoon.
- A daily token cap per person, in millions
- A personal cap can only narrow the org's cap
- It can never be set wider than the org allows
Metered from your wallet
Usage draws from an organisation wallet rather than a surprise invoice. The balance, what has been spent and what each person cost are all in one place.
- One org wallet, one running balance
- Usage broken down by person and by day
- Watch the spend as it happens, not a month later
You control the funding
Balance is added by requesting a top-up, optionally quoting a payment reference such as a UTR. SubhX approves it — and nothing is credited until that approval lands.
- Request a top-up with a payment reference
- Approved by SubhX before anything is credited
- Every credit and debit on one ledger
An audit trail for admins
Admins can see what the assistant actually did — which tools ran, what was allowed and what was refused — without being handed a window into their staff's conversations.
- Every tool run recorded, allowed or denied
- Token and cost figures attached to each entry
- What ran is visible; what was asked stays private
How it works
From switched off to answering questions in four steps
Enable it, choose who gets it and what they may spend, and your team starts asking — with a confirmation step standing between a draft and a change.
- 01
Switch it on
Enable SubhX AI for your organisation from the marketplace, and top up the wallet it meters from. Nothing to install and nothing for your team to set up.
- 02
Choose who gets it
Pick the people who should have the assistant and give each of them a daily token cap. Everyone else carries on exactly as before, seeing no trace of it.
- 03
They ask, it looks
Your team opens the assistant from any screen and asks in plain language. It checks the workplace through their own permissions and answers from what it finds.
- 04
They confirm any change
If the answer involves changing something, a confirmation card appears with the exact draft. It is submitted only when the person presses confirm — never before.
Permissions
It can only do what you could already do
The assistant has no privileges of its own. It acts on your behalf through the product's own permissions, so the boundary around it is exactly the boundary around you — not a separate policy someone has to remember to keep in step. A colleague's data stays a colleague's, and another organisation's workplace is simply not reachable.
- Acts as you, through the checks your account already passes
- Never reaches another employee's data
- Never reaches another organisation's data
- Any change waits on a confirmation card before it happens
What it can see
Yours
and nothing beyond
A colleague's data
Closed
no cross-employee reach
Another org
Closed
no cross-organisation reach
Before any change
Asks
on its own confirm card
Admin control
You decide who gets it — and what they can spend
An admin turns the assistant on person by person, so you can start with one team rather than the whole company. Each person can also carry their own daily token cap, set in millions — and because a personal cap can only ever narrow the organisation's, nobody can be handed more headroom than the org itself allows.
- Per-person on and off, changed whenever you like
- A daily token cap per person, expressed in millions
- A personal cap narrows the org cap — it can never widen it
- Usage and cost broken down by person and by day
Members
Priya Nair
HR manager
Arjun Mehta
Support lead
Kabir Shah
Accounts
Meera Iyer
Field sales
A personal cap can only narrow the organisation's 5M — set one higher and it is held at the org ceiling, never above it.
Who it's for
Anyone who loses time hunting for an answer
The same assistant reads very differently depending on who is asking — because what it can reach is decided entirely by the person in front of it.
Employees
The quick questions that eat a morning — where a request got to, what is still open, what the policy says. Ask once, in the corner of whatever screen you are already on.
Managers & HODs
Pull together what your team has in flight without opening five modules. The assistant sees exactly the scope your role does, so the answer respects your remit by construction.
HR & operations
The desk everyone interrupts. Let people self-serve the routine lookups, and keep the drafting-and-confirm step for anything that would actually change a record.
Finance & owners
A per-person cap and a prepaid wallet mean AI spend is a number you set, not one you discover. Fund it on your terms and watch the usage as it accrues.
Pricing
A seat for each person, plus what they actually use
Two parts, both drawn from one organisation wallet — so AI spend is a balance you top up deliberately, never a bill that lands unannounced.
Per seat, monthly
₹50.00/ member / month
Charged for each person you have switched the assistant on for. Turn someone off and the seat stops counting — you are never billed for a colleague who does not use it.
- Billed only for the people you enable
- Add or remove a person whenever you like
- No minimum team size
Usage, per million tokens
₹7.00/ million tokens
On top of the seat, usage is metered per million tokens the assistant consumes. Per-person daily caps keep that number inside the ceiling you set.
- Metered usage, debited from your wallet
- Daily caps per person, set in millions
- Usage visible by person and by day
Topped up on approval, never automatically
Add balance by requesting a top-up for the amount you want, quoting a payment reference such as a UTR if you have one. SubhX approves the request and only then is your wallet credited — an organisation can never credit itself. Every credit and debit lands on one ledger you can read back.
Launch rates, billed only while the add-on is enabled. Billed token usage includes the model's internal reasoning, which is never shown to you. GST applies as per Indian tax law — for rates for a larger team, talk to us.
Questions
The things people ask about SubhX AI
What is SubhX AI?+
It is an assistant built into your workplace, sold as an opt-in add-on. It appears as a floating chat on your signed-in screens across the web portals: ask a question in plain language and it looks the answer up across the modules you already use, then tells you what it found. If what you want would change something, it drafts it and waits for you to confirm.
Can it see things I am not allowed to see?+
No, and this is the core of the design rather than a setting you have to remember to switch on. The assistant reaches your workplace through the same permission checks your own account goes through, so it can only ever see and do what you could already see and do. It cannot cross into another employee's data, and it cannot cross into another organisation's data.
Can it change or delete something on its own?+
No. Reading is free, but anything that would write to your workplace stops and asks first. The draft arrives as a distinct confirmation card showing exactly what is about to be submitted, and it is only carried out when you press confirm — as the ordinary action your own account would have performed anyway, through the same validation.
Does everyone in my organisation get it?+
Only the people you choose. An admin turns the assistant on or off for each employee individually, so you can start with one team and widen it later. Anyone without a seat sees no trace of the feature at all — no button, no panel, nothing to ask about.
How do I stop one person running up the bill?+
Give each person their own daily token cap, set in millions. A personal cap can only ever narrow the organisation's cap, never widen it, so nobody can be granted more headroom than the organisation itself allows — and a single heavy user cannot spend the month's budget in one afternoon.
How is it priced?+
Two parts: ₹50.00 a month for each person you have given a seat to, plus ₹7.00 per million tokens the assistant actually consumes. Both draw from your organisation's SubhX AI wallet, so you can see exactly what the seats and the usage each cost. Billed token usage includes the model's internal reasoning, which is never shown to you. GST applies as per Indian tax law.
How does the wallet get topped up?+
You request a top-up for the amount you want, optionally quoting a payment reference such as a UTR, and SubhX approves it. Nothing is credited to your balance until that approval goes through — an organisation cannot add its own balance — and every credit and debit is recorded on one ledger you can read back.
Can admins read what my team asks it?+
No. Admins get an audit trail of what the assistant did — which tools ran, whether each was allowed or refused, and the tokens and cost attached — so they can account for the spend and the access. The prompts themselves are deliberately left out of that view: an admin sees what ran, not what their colleague asked.
Put an assistant where your team already works
Bounded by the permissions your people already have, stopped by a confirmation card before anything changes, and capped person by person from a wallet you top up on your terms. Switch it on for one team and see how it goes.