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 |
|---|---|---|
| MITPO Assistant (chat) | Yes - tab-scoped, resets on reload | Yes - persistent, threaded, with memory |
| Validate Idea | Yes - Quick take or Deep dive | Yes - Quick take or Deep dive, saved to your history |
| Personas | Yes | Yes |
| Competitor preview | Yes - 3 previews a week | Yes - Spy and Scout, with daily limits by plan |
| Brand documents (upload) | No - requires an account | Yes - upload PDF, DOCX, TXT, or MD files in Settings → Brands |
| Campaigns | Yes - Plan and Schedule (Ads locked) | Yes - Plan and Schedule; Ads coming soon |
| Creative Studio | Yes - Generate, Editor, Canvas, and Sketch, with demo limits | Yes - Generate, Editor, Canvas, and Sketch |
| Automation workflows | Yes - Workflow | Yes - visual builder, recipes, and 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 keeping your work needs the workspace that an account provides.
- Rate limits keep costs predictable so the demo can stay free.
- Features that need uploaded context (brand documents) need an account to have anywhere to keep 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.