Corporate back office
≈ $350M revenue (approx.) · PE-owned · six operating companies · a 12-person corporate team
Shared skills and brand assets portal
Invoice coding, on-brand presentations and monthly reports from one shared portal where the logic and the assets live in one place, instead of in each person's chat window.
- Organization
- Corporate back office of a private-equity-owned group
- Reality
- Small team, many recurring tasks, everyone using a different chat tool
- Runs on
- The group's cloud tenancy
- Scope
- Shared skills and brand assets in one portal
Where they started.
People were already using chat assistants for invoice coding, presentations and reports, and getting different answers, in different formats, from the same prompt. Skills could not be shared between individual accounts, brand guidelines were reapplied by hand every time, and the private inference bill would have grown with every seat.
What was built.
- An administrator publishes shared skills once: invoice coding rules, the monthly report, the presentation template.
- The brand kit and data connections live in one place and every user's agent calls the same tools, so the output is the same for everyone.
- Role-based access keeps finance tools with finance and marketing assets with marketing.
- Flat-rate private inference: adding a user adds no per-seat model cost.
What changed.
- One report, one format, produced the same way by everyone.
- Invoice coding that follows the rules every month instead of most months.
- Presentations that come out on brand without a second pass.
- The 'everyone has their own assistant' bill replaced by one tenancy.
Invoices, board materials and internal reports are exactly the documents a company does not want in a vendor's training set. Shared skills only work well when everyone can use them on the real data.
The group's cloud tenancy
Components involved.
More like this.
Regulated outbound contact center
≈ $40M revenue (approx.) · ~250 agents · three sites
- Use Case:
- Compliant voicemail lane beside the existing dialer
- Results:
- A voicemail lane leaves a message specific to each account, in a consented agent voice, at a volume no floor can match, and shares one attempt ledger with the dialer so contact limits stay enforced in one place.
Global law firm
≈ $3B+ revenue · Thousands of lawyers · dozens of offices
- Use Case:
- Walled-matter research assistant
- Results:
- Document search and drafting inside the firm's own tenancy: every answer cited to its source, every matter isolated by role, and nothing ever sent to a third-party model.
Technology consultancy
≈ $8M revenue (approx.) · Boutique consultancy · ~25 consultants
- Use Case:
- Content production agent
- Results:
- Sales decks, one-pagers and campaign copy from a private agent with the brand system loaded, running on the company's own inference, with skills shared across the team rather than pasted between chats.
Have one like it?
Every spotlight started as a conversation about a process nobody liked doing, under a data-locality constraint.