Docs
Gwen runs Gwen
How Gwen uses the same mission, memory, planning, approval, and artifact system to improve Gwen itself.
Gwen is customer-zero
The strongest claim a product can make is that its makers run on it. Gwen does: the company building Gwen uses Gwen to run and improve Gwen.
That is not a slogan but an operating decision. The same growth, content, research, support, and engineering work that customers need is work the company also has — so it is done with the same system, in the open against real stakes.
Why dogfooding matters
Running on your own product is the fastest way to find out whether it actually works. The patterns customers rely on — research, docs, marketing, onboarding, support, analytics, engineering, and operations — are exactly the patterns Gwen needs internally.
So every rough edge a customer might hit is one the team is likely to hit first, with every incentive to fix it. Dogfooding turns the product roadmap into the team's own daily experience.
The internal Gwens
Internally, Gwen shows up as a set of focused operators, each pointed at part of the business:
- A planner that prioritizes work.
- Knowledge and web operators that improve docs and public pages.
- Research that curates daily learning.
- Onboarding and success that inspect activation.
- Product that turns feedback into capability ideas.
- A developer operator that drafts code changes for human review.
Each is the same Gwen — same memory, missions, and approvals — scoped to a different job.
Draft-first, approval-gated
The safe way to let Gwen help run a company is to start read-only and draft-first: summarize metrics, find gaps, draft documentation, propose content, plan missions, and prepare pull requests.
The consequential actions — publishing, sending, deploying, refunds, account changes — stay behind approval, exactly as they do for customers. Internal use does not get a pass on the guardrails; if anything, it proves them.
Your benefit
Every internal Gwen mission is product evidence. If Gwen can improve its own knowledgebase, onboarding, docs, and operations under approval, the same workflow is one that can be offered to customer workspaces.
In other words, what the team builds for itself becomes a proven playbook for you — and the bar for quality is set by people who have to live with the result.