One project graph across every tool you use.
ProjectiQ unifies Jira, Linear, Asana, GitHub, and Notion into a single project graph. AI rolls up status, finds dependencies, and writes the update before the meeting.
What is ProjectiQ
The view your CEO has been asking for.
Engineering uses Linear. Marketing uses Asana. Ops uses Notion. Leadership wants to know what is shipping next month. Today that answer is a manual deck rebuilt every Friday. ProjectiQ writes it from the source.
Reads, doesn't replace
Engineers stay in Linear, ops stays in Notion. ProjectiQ is the rollup layer on top.
One graph, many sources
Jira epics, Linear cycles, Asana projects, GitHub issues, Notion docs — normalized into a single queryable graph.
AI writes the rollup
Friday status from real ticket activity, not what people remember. Cited tickets, no hallucination.
Ask in plain English
'Which customer commitments are unstaffed?' — answered in seconds, every claim traced to the underlying ticket.
In the editor
The graph your tools never gave you.
Initiatives from every tool, dependencies between them, and the AI rollup written from real ticket activity — in one view.
Layers
What ships in ProjectiQ
Each capability is a queryable layer on top of the tools your team already uses. The chips show what each layer reads from.
Cross-tool project graph
Jira epics, Linear cycles, Asana projects, GitHub issues, Notion docs unified into one queryable graph with consistent status.
AI status rollups
Friday status doc generated from real ticket activity. Per-team, per-initiative, per-customer commitment.
Dependency detection
AI surfaces hidden cross-team dependencies before they block. 'Marketing launch on July 15 needs an API change owned by team X — currently unscheduled.'
Risk + critical path
Velocity-based risk scoring on every commitment. Highlights the 3 things most likely to slip the next milestone.
Natural-language queries
'What did the data team ship in Q1?' 'Which commitments are unstaffed?' Answered in seconds, every claim cited.
Read-only by default
ProjectiQ does not replace your tools. It reads from them. Engineers stay in Linear, ops stays in Notion — only the rollup layer is new.
Integrations
Reads from where work actually happens
Jira / Linear / Asana / ClickUp
Two-way sync for projects, epics, sprints, and statuses. Custom fields preserved.
GitHub / GitLab
Issues, PRs, releases tied to upstream tickets. Code activity informs progress, not just ticket movement.
Notion / Confluence
Project briefs, RFCs, and decision logs linked into the graph. AI cites them in answers.
Slack
ProjectiQ posts daily and weekly rollups into the right channels. Ask a question with /projectiq and get an answer in thread.
Founding-partner program — 5 slots
Built by Destm — engineers who have run multi-tool delivery at retail scale and got tired of rebuilding the Friday status doc by hand. Founding partners lock first-year pricing, ship feedback straight to the build team, and steer the roadmap.