Launch guide
Getting Started
Start with the demo. The public Product Hunt flow should be dashboard, feed, patterns, then epics. Real OAuth setup belongs after a workspace is configured and verified.
Demo vs. Google sign-in
Live Demo enters a seeded demo workspace. Google sign-in enters a real authenticated workspace. These are separate flows so visitors do not land in the founder account or any private workspace while trying the demo.
Open the live demo
Use the Live Demo button on the homepage or login page. It creates a separate demo session with seeded Slack and GitHub feedback, so Product Hunt visitors can explore without signing in.
- -The demo is intentionally separate from Google sign-in.
- -Starting the demo clears existing Supabase auth cookies before entering the demo workspace.
- -Use Google sign-in only when you want to work in a real workspace.
Read the dashboard first
The dashboard is the fastest way to understand the sample workspace. It shows signal volume, sentiment mix, active channels, and recent feedback movement.
- -Use this page as the opening Product Hunt walkthrough screen.
- -The sample data refreshes dates when the demo starts so the charts look current.
Triage the feed
The feed shows individual feedback signals from the seeded Slack and GitHub sources. Use search, sentiment, source, date, severity, and ranking controls to scan the backlog.
- -Rank by impact or recency when explaining how teams find the strongest signal.
- -Demo data is read-only, so visitors cannot damage the source setup.
Open the patterns page
Patterns group related signals into product themes. The demo includes authentication friction, API reliability, dashboard UX, and onboarding patterns.
- -Use the signal volume chart to show when a pattern is gaining momentum.
- -Open a pattern detail view to show the source signals behind the summary.
Review generated epics
Epics turn patterns into product work with acceptance criteria, user stories, priority, and effort estimates. This is the strongest end state for the demo.
- -Treat Linear and Jira export as a configured-workspace feature, not a public demo promise.
- -For Product Hunt, show the generated epic content rather than connecting a real external account.
What to avoid in the launch demo
Do not ask visitors to connect their own Slack, GitHub, Jira, Linear, Zendesk, or Discord account during the public demo. The current launch path is strongest when it uses the seeded demo workspace.
View integration status