Switch to ProductOS
Moving a team to a new tool is a project. Here is what carries over, a two-week pilot you can run before you commit, and a short pitch you can send your team.
Updated
What carries over?
Integrations pull your existing records into ProductOS. Engineering doesn't have to move: Linear and Jira issues sync in as Work, and ProductOS pushes the status back when the Work ships.
| From | Comes in as | Notes |
|---|---|---|
| Productboard | Feedback | Notes and feature requests |
| Canny | Feedback | Posts |
| Intercom, Zendesk, Freshdesk, HubSpot | Feedback | Conversations and tickets |
| Notion | Feedback | The rows of one database |
| Linear, Jira | Work | Status is pushed back when the Work ships |
| GitHub, GitLab | Work | Issues; the GitHub App also links pull requests and commits |
| Asana, ClickUp, monday.com, Shortcut | Work | Tasks, items and stories |
| Pipedrive | Accounts | Deal value as ARR |
| Figma, Confluence | Links on Work | Files and pages stay where they are |
| Anything else | Any record | The Excel import template, Settings, Import/Export |
What does a two-week pilot look like?
1.Day 1: set up
Create a workspace and describe your product in a paragraph. The onboarding wizard drafts a vision, OKRs, personas, themes and a first thread for you to edit.
2.Days 2 and 3: connect
Connect one feedback source (your support tool or Productboard) and your tracker. Invite the rest of the product team.
3.Week 1: triage
Group a week of feedback into themes, link the top themes to Work, and set one initiative with an outcome to measure.
4.Week 2: ship one thread
Take one Work item through to a release, with its pull request or coding-agent session attached, and publish the changelog entry. Invite sales and leadership as viewers.
5.Day 14: decide
Ask the two questions: can we see why each shipped item was built, and what it was meant to move? If yes, move the rest over.
How do I make the case to my team?
I'd like us to trial ProductOS for two weeks. It keeps customer feedback, our OKRs, the work, the code that shipped it and the results in one place, so we can answer why we built something and whether it worked without writing a retro doc. Engineering stays in our tracker: issues sync in, and ProductOS marks them done when they ship. Viewers and commenters are free, so sales and leadership can follow along at no cost. The plan: connect one feedback source and our tracker, run one initiative end to end, then decide.
What changes for each team?
| Team | Day to day |
|---|---|
| Product | Triage, prioritise and plan in ProductOS; specs carry their evidence. |
| Engineering | Stays in Linear or Jira; the why is on the Work item, and coding agents report back to it. |
| Design | Figma files link to the Work they serve, and the design system lives in the same workspace. |
| Leadership | Reads OKRs, initiatives and outcomes without asking for a status deck. |
| Marketing and sales | Launch plans, messaging, battle cards and deal blockers sit next to the roadmap. |
Common questions
1.Can we leave again?
Yes. Export the whole workspace to Excel at any time, from Settings or through the MCP connector.
2.Does the pilot cost anything?
No. The free plan covers up to 3 members, and viewers and commenters are free on every plan.
3.What about AI costs?
Bring your own Anthropic key on any plan and pay Anthropic directly, or use the hosted allowance on Pro and Team.