What you get in the demo
The demo surface is a focused subset — the features most useful to decide whether the product fits your team.
| Capability | In the demo | In the full app |
|---|---|---|
| Marketing Assistant (chat) | Yes — tab-scoped, resets on reload | Yes — persistent, threaded, with memory |
| Idea validation (council) | Yes — one-off preview | Yes — full history, follow-up questions |
| Competitor preview | Yes — one preview per day | Yes — unlimited Spy runs on paid plans |
| Brand voice (upload docs) | No — requires an account | Yes — upload PDFs or Word docs, searchable by meaning |
| Campaigns + calendar | No — requires an account | Yes — planner, brief, scheduler |
| Creative Studio | No — requires an account + credits | Yes — image, video, speech modes |
| Automation workflows | No | Yes — visual builder, 27+ integrations |
Demo parity is about trust — every demo answer uses the same engine as the logged-in app.
Why the limits exist
Two reasons the demo is constrained: abuse control and pipeline fairness. Anonymous users can burn a lot of compute quickly if nothing gates the flow, and the expensive modes (video, campaigns) need the workspace context that an account provides.
- Rate limits keep costs predictable so the demo can stay free.
- Modes that require uploaded context (brand voice, campaigns) need an account to have anywhere to persist that context.
- The in-tab conversation you have in the demo is not saved — refresh and you start over, by design.
Upgrading from demo to full
When the demo runs out — quota hit, or a locked feature needed — signing up continues your current session in spirit, not in state. The demo does not transfer transcripts into your new account, but the brand context you set up after signup is immediately deeper than anything the demo had.