Spectrum Flare
Two founders, six client projects, one shared brain
A two-person product studio juggling client work in parallel. Each project has years of decisions, custom patterns, and "we tried this once" moments. CompanyAura made them all queryable — so picking up a project after three months feels like never having left.
Project overview
The kind of team this fits:
- Small studios, agencies, and consultancies running multiple client projects in parallel
- Founder-led teams where most operational knowledge lives in chat threads, emails, and people's heads
- Teams already using Claude, ChatGPT, or Cursor and wanting those agents to actually know how the company runs
The problem
"We were the wiki. Six clients, six stacks, six sets of weird preferences — all in our heads. Every time we came back to a project we'd re-derive half the decisions."
Years of decisions, client-specific patterns, integration choices, and "we tried this once" learnings were spread across chat threads, email, Linear, and the two founders' memories. Documentation existed but nobody had time to keep it current.
Key outcomes for Spectrum Flare
Three measurable shifts in how the team uses what they already know.
Six projects, one shared brain
Every client's stack, integrations, and quirky preferences are queryable in seconds. Coming back to a project after three months feels like never having left.
Docs drafted in a day, not months
CompanyAura read every doc, task, and message — then drafted the operational map in a day. Two founders reviewed in an evening. No "documentation project" that drags on forever.
Every answer cites its source
Every claim links back to the chat thread, email, or task it came from. No hallucinations. Trust isn't optional when you're billing clients on the result.
What was breaking
Context lived across too many places
Client preferences in email. Technical decisions in chat. Bug history in Linear. Recurring patterns in nobody-wrote-it-down. Two founders had to remember which thread held which answer.
Documentation was always "next month"
Writing proper SOPs for six client projects would take months. Two founders running the business have no months. So the runbooks didn't exist — and the same questions came up again every quarter.
Agents knew nothing about the actual work
Cursor and Claude could write generic code, but couldn't say "this client uses X library because we hit Y issue in 2024." The operational context was in chats and email — out of reach for agents.
Re-deriving decisions on every project return
Coming back to a project after three months meant re-reading old threads to remember "why did we choose this." Wasted hours every time, on every project.
Our approach
One idea framed the whole project:
"The brain should compile from how the team already works."
Two founders don't have time to write docs. They keep talking in chat, sending emails, and shipping tasks the way they always have. CompanyAura does the filing, the cross-referencing, and the lint pass — across every client project.
The solution, from the inside
Four mechanisms that turned scattered project context into an operational map two founders actually trust.
One-pass ingest across every project
CompanyAura read every chat thread, email, task, doc, and design note across all six client projects in one pass. For each project it extracted entities (services, integrations, client preferences), decisions ("we picked X library because…"), and recurring patterns. Result: a cross-project operational map in a day, all cross-linked, with citations back to the source.
First useful brain in 24 hours — not "the documentation project we'll get to next year."
Continuous capture, not periodic cleanup
Every new chat message, email, or task flows through CompanyAura. If a thread changes how a client wants something handled, the matching page updates. If a decision contradicts an older claim, both get flagged for the founders to reconcile. The brain gets denser every week, not staler.
Stale-claim alerts arrive the same week the practice changes — not next quarter.
Claude and Cursor query the brain via MCP
The founders plugged CompanyAura's MCP endpoint into Claude Code and Cursor. New work gets pre-loaded with relevant client context: "this customer uses X auth provider because we hit Y issue in 2024." Agents stop guessing and start citing.
Every agent answer comes with a link back to the thread or task that proves it.
Lint passes catch the contradictions
Once a week, CompanyAura surfaces conflicting claims across projects, orphan pages, and topics mentioned repeatedly in chat but missing from the map. The founders triage in a 15-minute review.
15 minutes a week instead of "documentation is the perpetual side-quest nobody finishes."
"We used to be the wiki. Now there's an actual one — and it stays current across every client project without us writing anything."
Spectrum Flare
Product studio
Build your company brain. Make your team agent-ready.
We're picking a small number of design partners. If most of your team's "how we actually handle X" lives in chat, email, or someone's head — and you want an agent to act on it — we'd love to talk.
hello@companyaura.com