Each client gets its own Clembot install with its own data vault. No client data is shared between installs.
1. Run the setup wizard
The first time the dashboard opens, it runs a six-step wizard:
| Step | What you fill in |
|---|---|
| Product | Name, tagline, product type, one-line description, website |
| Brand voice | How formal or casual, words that describe the voice, phrases to avoid, patterns to use |
| Audience | Who the customer is, how technical they are, what problems they have |
| Positioning | The value proposition, themes to lead with, themes to avoid, competitors |
| Features | Which parts to switch on: content calendar, SEO radar, founder persona, evidence log, Notion sync |
| Review | A summary of everything, then initialize |
The wizard writes the first brand files from your answers. The specificity of the answers sets the quality of everything after. Vague positioning produces vague content, so budget 20 to 30 minutes for it.
2. Fill in the product facts
The wizard cannot know your technical facts. It writes the product-facts file as a template, and someone has to fill it in: how the product works, real performance numbers, pricing, and an accurate feature list.
This is the most important step. Agents quote the file directly. A placeholder left in it gets quoted in a blog post.
3. Finish the remaining brand files
Review the competitors file, add your SEO keywords, and fill in the content playbook and style guide. Every agent reads these before producing anything.
4. Run the first commands
/seo-pulsescans for trending keywords and content gaps./competitor-scanbuilds a competitive report from your competitors file./campaign <name>turns a campaign into a calendar with a brief for each piece.
Read the output closely. The first runs show where the brand files are thin, and fixing the files fixes every run after.
Optional
- Notion. If the client wants the calendar and reports in Notion, a setup script creates the databases. Without it, everything is stored locally and the dashboard reads it from there.
- Slack. A per-client channel for the personas.
- Scheduled routines. Recurring jobs such as a weekly digest. They create drafts only.