Getting started
Get started by creating a workspace, connecting the apps behind the first useful workflow, and starting with one real initiative.
Start with the apps that make that first workflow useful: Slack for invites and updates, a version control app for code activity, an issue tracker if active work already lives there, and Google Calendar when meetings affect the day.
Start with the essentials
Do not migrate everything first. Connect the apps with current work, create one initiative, then invite the team.
Replacing an issue tracker or roadmap tool?
Create initiatives for planned work and bugs for defects or incidents. If you are replacing Aha!, Productboard, or another roadmap tool, start with active roadmap items and current product bets.
Keeping Linear, Jira, or another issue tracker?
Keep active issue execution in Linear, Jira, or the issue tracker your team already trusts. Use the workspace for roadmap context, daily planning, recaps, standups, AI handoff, and reporting.
If your current planning app is not connected, recreate only the active work that matters now. Leave old closed history behind unless you still need it for reporting.
Create the workspace
Create an account and name the workspace. Onboarding gets the workspace ready for the first integration, initiative, team invite, and standup.
Each workspace has its own members, teams, integrations, taxonomy, work, and settings. You can belong to multiple workspaces without mixing data.
Once the workspace exists, set up integrations, create your first initiative, and invite your team. Admins can manage workspace integrations in Settings -> Integrations and keep access clean through Members, Roles, and Teams.