Turning a blank AI chat window into a configured workspace, thirteen plugins deep
Strategy Stack
The challenge
Knowledge workers open an AI assistant to a blank screen. It knows nothing about them, their clients, their voice or their files — so they try it, get generic output, and conclude AI doesn't work for their job. The gap isn't model capability. It's that nobody configured it.
What we built
We built a commercial product line of 13 plugins: one foundation plugin that configures the workspace, and 12 profession-specific packs covering accountants, real-estate agents, insurance brokers, financial advisers, management consultants, marketing agencies, nonprofits, ecommerce operators, product managers, sales directors, business coaches and creative freelancers.
The foundation plugin runs a 13-question guided interview built as a conversational state machine — one question at a time, with a documented response framework, a protocol for thin answers, another for answers given out of order, and a resume path for sessions interrupted mid-way. From that it classifies the user into one of four working archetypes and generates their entire workspace: a personalised instruction file, a folder architecture, a persistent memory system, a connectors manifest, and a first task designed to produce a visible win immediately.
Each persona pack then layers domain expertise on top — 20 to 24 named capabilities across five categories, so a configured workspace knows what work that profession actually does.
The engineering discipline is what makes it a product rather than a prototype: strict version synchronisation across three files per plugin, a licence shipped in every pack, and per-user package baking with a recurrence guard that prevents intellectual property leaking between customers.
What was delivered
13
plugins shipped
12 / 12
packs verified on the delivery gate
20–24
capabilities per persona pack
142
documentation files
- 13 plugins and 12 persona packs shipped, each pack carrying 20–24 capabilities
- 12 of 12 packs verified live on the delivery gate, confirmed through the public download path
- Version synchronisation maintained across every release, bumped in lockstep
- 142 documentation files supporting the product line
- A body of empirically-discovered platform limitations documented as primary research — the kind of finding only available to someone shipping on a new platform in production
Every figure above is taken from the delivered system itself. Where we don't have a client-verified business outcome, we report what was built and measured rather than estimating an improvement.
Tech stack
- Claude Code plugin architecture
- Markdown-as-specification
- Supabase
- n8n
- Per-user package baking
Related service
Generative AI & LLM Application DevelopmentLLM-powered features your users actually rely on.
Have a similar project?
Tell us your goal and we'll map the fastest path to results.