Separate AI seats from client boundaries. A boutique firm can share one Kiweely Team Credits pool at $149/seat/month while every conversation still pins a single Client, a selected tenant set, and that Client’s Documents. Mixing fails when partners dump every Sandbox screenshot, SOW clause, and Integration System User note into one ChatGPT or Claude workspace and hope folder names count as isolation.
Five-to-twenty person Workday practices feel this first. One senior consultant works three tenants before lunch. Juniors inherit Studio CLARs and Extend apps. Owners want one invoice for AI usage without a Friday incident where Client A’s compensation domain paste lands in Client B’s thread.
The Failure Mode: One Shared Chat, Many Tenants
| Shared chat habit | What leaks | What breaks next |
|---|---|---|
| Shared chat habitOne ChatGPT Team space for the whole firm | What leaksWorker samples, security group names, vendor file layouts | What breaks nextWrong client advice reused as “the usual pattern” |
| Shared chat habitOne Claude project with every SOW PDF | What leaksPricing, scope, and confidential org charts | What breaks nextProposal language from Client A reused for Client B |
| Shared chat habitOne browser profile signed into three Sandboxes | What leaksSession cookies and downloaded reports | What breaks nextAccidental deploy or report run in the wrong tenant |
| Shared chat habitOne Flex Credit pool with no delivery tagging | What leaksUnexplained Workday AI spend | What breaks nextPartner argues about which engagement burned credits |
Workday’s own Developer Agent guidance tells builders not to put PII into prompts. Firm tooling has to enforce the same discipline across people, not only across model calls.
Seat Math Without Inventing Caps Clients Never Asked For
Vine Free is free for your Workday personal developer account and its tenant. Any other tenant needs Vine Personal at $99 a month for one person, or a Vine Team seat at $149 a month. For a practice that shares work:
- Personal: $99/month or $990/year per person when they connect company or client tenants alone.
- Team & Enterprise: $149/seat/month. Owners and Admins manage members, buy a shared Kiweely Credits balance, set each member’s monthly limit, and can make Kiweely Credits the only AI path in the firm space.
- Nest: $999/seat/month for company HRIS teams running Nest, not for external consulting delivery.
Kiweely does not invent row or timeout ceilings inside the Workday apps and integrations it helps you build. Token budgets are firm-side spend controls on Credits, not product limits imposed on the customer’s tenant.
Client Pins: Tenants, Projects, Conversations, Documents
Kiweely Vine models the practice the way partners already staff work:
- Client holds tenants, Documents (Proposals, Contracts, Communication), and projects.
- Project belongs to exactly one Client (Extend app, Studio integration, or other Workday project kinds).
- Conversation pins that Client and only the tenants you select for the thread. Consent grants clear when connections change.
- Credentials for another Client never enter that turn, even though the consultant can see other Clients in the sidebar.
That pin is the difference between “we told people not to mix clients” and “the host refused the wrong tenant.” Pair it with multi-client zero data leakage practices and the five intake questions in firm AI agent for Workday.
Token Budgets Beside Workday Flex Credits
Firms usually track two meters:
- Workday Flex Credits for native agents, Sana, and Developer Agent usage inside the customer’s UMSA.
- Kiweely Credits for desktop agent work on Bedrock (or the consultant’s own ChatGPT, Claude, or API plan when chosen per conversation).
Keep them separate in delivery reporting. A Sandbox week that burns Deployment Agent Ask credits on the customer’s Production Flex balance is a customer cost. A partner rebuilding calculated fields in Vine is a firm Credits cost. Owners set per-member Kiweely caps so one overloaded engagement cannot empty the shared pool overnight.
Production consent is stricter on purpose
When a conversation includes Production, Kiweely locks Full access off, bars bulk loads and EIB writes, and verifies each configuration change before the next. Boutique firms should treat Production pins as partner-supervised, not junior self-serve.
Contractor and Junior Onboarding Without a Second Leak Path
Boutiques often add contractors for a single Workday release. Seat sharing without Client pins creates a predictable incident: the contractor’s personal ChatGPT history retains client extracts after the SOW ends. Prefer a Team seat that places their desktop in the firm space, with a tight Credits cap and access only to the Clients they staff.
Juniors need the opposite of a shared pastebin. Give them:
- Read-heavy Sandbox conversations under the correct Client.
- Explicit consent coaching before any security policy edit.
- A rule that Production pins require a named partner on the thread.
- Deliverable templates in Client Documents instead of copying SOW text into prompts.
Workday Developer Agent guidance already warns builders not to include PII in prompts. Firm policy should extend that to screenshots of worker compensation, ISU naming spreadsheets, and SFTP host lists. If a prompt needs an example worker, use synthetic Development-tenant personas such as the Open Developer Program sample users, not a production employee row.
Operating Cadence That Survives Partner Review
- Open work under the Client first; never start from a nameless chat and attach tenants later as an afterthought.
- File SOWs and change orders in Client Documents before building.
- Give each member a Credits cap tied to utilization, not a shared unlimited tab.
- Prove security and workflow fixes with multi-persona proxy testing inside the pinned tenant, then store evidence under the project.
- Separate internal Nest evaluations ($999/seat/month) from external consulting Team seats so company HRIS experiments never share a Client tree with billable tenants.
- Review seat and Credits posture on /pricing and /security before onboarding contractors.
A weekly partner check that takes fifteen minutes: list Live conversations, confirm each Client pin, skim Credits burn by member, and close any thread that still holds Production without an active change ticket. That ritual catches mix-ups faster than an annual security training slide.
Shared seats are a billing and collaboration choice. Client boundaries are a host rule. A boutique that keeps both explicit can scale AI without turning every engagement into a data-handling incident.
Frequently asked questions
Can one Kiweely conversation use tenants from two different clients?
No. Each conversation pins one Client and only the tenants selected for that thread. Credentials for any other Client, or any tenant not ticked on that conversation, are never served to that turn.
How do Team seats differ from Personal licences for a five-person boutique?
Personal is ninety-nine dollars a month or nine hundred ninety a year for one person. Team is one hundred forty-nine dollars per seat per month: one firm space, a shared Kiweely Credits pool on zero-retention US Amazon Bedrock, and monthly caps Owners or Admins set per member.
Where should SOWs and client contracts live relative to tenant work?
Under that Client's Documents, in Proposals, Contracts, and Communication folders with a version timeline. Project deliverables sit under the Client's projects. Do not paste SOW text into a shared ChatGPT workspace that also holds another client's Sandbox screenshots.
Does joining a firm cancel someone's existing Personal licence automatically?
No. A separately paid Personal licence keeps billing until the person cancels it. Warn consultants before they join a Team space so they do not double-pay.