QR Codes for Agencies
One balance, one bill, and a ceiling per client that the edge enforces.
no subscription · pay per scan · nothing to cancel
Client work breaks the one-account-one-plan shape
An agency is not one customer. It is thirty, with thirty budgets, thirty reporting lines and thirty different opinions about what a scan is worth. Platforms priced per seat and per plan make you choose between one account nobody can be billed for and thirty accounts nobody can administer.
- A campaign that goes viral on Friday and spends the retainer of every other client on the account.
- Thirty logins, thirty renewal dates and thirty cards, so that each client can be invoiced separately.
- A client workspace that reads as "Free" because the plan sits on the parent, so nobody trusts the numbers.
- Finding out a client went over at the end of the month, from a report rather than from a stop.
How a client budget behaves
A ceiling, not a forecast.
One balance pays for the tree
Credits sit on the agency and every client workspace draws from them. There is one purchase, one expiry to track and one place to top up.
Each client carries its own ceiling
Set a credit budget per client. The counter lives beside the redirect at the edge and is checked on the scan, so a client that reaches its ceiling pauses on the next scan rather than in next month reconciliation.
scan 1 credit · budget checked at the edge, per clientYou hear about it before it stops
An alert fires when a client crosses four fifths of its budget and again when it reaches the whole of it, so raising the ceiling is a decision rather than an incident.
One client pausing changes nothing for the rest
The ceiling is per client, so the codes belonging to everyone else keep resolving normally. That containment is the whole point of the ceiling.
What the tree gives you
- One bill, many workspaces
one payerThroughput and entitlements are billed to the payer rather than to the workspace that acted, so client work does not need its own subscription.
- A client sees the real plan
A client workspace reads its payer plan rather than showing as free, so the limits on screen are the limits that will actually apply.
- Domains resolve tree-wide
A domain entitlement anywhere in the tree unlocks custom hostnames for the client workspaces under it, so client codes can sit on the client brand.
- Budgeted keys for automation
An API key can carry its own daily credit ceiling, so a script or an agent working on one client cannot spend another client credits.
- Codes outlive the retainer
A code that is still being scanned keeps the account alive. When a client leaves, what they printed does not stop working the day the contract does.
- No per-seat pricing
Adding a person is not a line item. What costs money is scans, which is the thing your client is actually buying.
Against the usual agency workaround, including where we fall short
| Capability | taproute | One subscription per client |
|---|---|---|
| Spend ceiling per client A per-client stop is the difference between containing an overspend and reporting it. | Yes, enforced at the edge on the scan | The plan limit is the only ceiling |
| Renewals to manage | None. Credits are prepaid and nothing recurs. | One per client, each with its own date |
| Cost of adding a client | Nothing until they have codes and scans | A new plan, from day one |
| Client codes on the client own domain | Yes, one CNAME, entitlement reads tree-wide | Usually a per-domain annual fee |
| Read-only viewer role for a client We do not ship a viewer role yet. If a client needs to see the dashboard without editing it, that is a real gap today. | No | Yes |
| Scheduled emailed reports Analytics are on screen and in the API. Nothing mails a client a monthly PDF for you. | No | Yes |
Questions
How do I stop one client spending another client credits?
Give each client workspace a credit budget. The counter sits beside the redirect at the edge and is checked on the scan, so a client that reaches its ceiling stops there and everyone else is unaffected. You are alerted when a client crosses four fifths of its budget and again at the whole of it.
Do I need a separate plan for each client?
No. Credits sit on the agency and the client workspaces draw from them. Throughput and entitlements bill to the payer rather than to the workspace that acted, which is why one purchase covers the whole tree.
Can a client keep their codes if they leave?
The printed codes keep resolving while the account behind them has credit. Moving a client onto their own account is a conversation to have deliberately rather than something that happens by accident at the end of a billing period.
Can client codes sit on the client own domain?
Yes. A domain entitlement anywhere in the tree unlocks custom hostnames for the workspaces under it, and a domain slot is bought once rather than rented by the year.
Is there a per-seat charge for my team?
No. Adding people is not billed. What is billed is code creation at 1 credit and scans at 1 credit, so the cost tracks what your clients actually get.
Can I give a client read-only access to their own dashboard?
Not yet. There is no viewer role today, and nothing mails a client a scheduled report. Both are real gaps for agency work and worth knowing before you move a book of clients across.