1. Create or join a workspace
If you were invited to an existing workspace, accept the invite and use that workspace. Do not create a duplicate workspace for the same team. If you are starting from scratch, create one workspace for the product, product area, or operating team that will own the journey. If you add a company website during workspace creation, Custory can use it to generate starter context. Treat that as a draft, not validated customer truth. Read Workspace for the full workspace model, or Manage your team for roles and invitations.2. Choose one narrow journey
Pick one journey that matters now. Good first choices:- new user onboarding
- activation
- trial to paid
- support escalation
- renewal risk
3. Choose a starting path
From the dashboard, choose one:| Path | Use it when |
|---|---|
| Import with AI | A focused website, repository, Notion source, or available Figma source already explains the flow. |
| Use a template | You want a proven starting structure and can adapt it quickly. |
| Start blank | The journey is new, hypothetical, or no source is trustworthy yet. |
4. Invite the initial editors
Start with a small editor group. Good early editors are usually:- founder or product lead
- one support or customer-facing teammate
- one engineering lead or product engineer
- one design or research owner if relevant
5. Connect one useful integration
Do not connect every tool during setup. Start with one integration that removes real friction:- Slack or Discord for updates
- GitHub, Jira, or Linear for follow-up work
- Notion or Figma when they already hold useful journey source material
- PostHog or Stripe when metrics or signals should stay connected