The why
Quarterly bets and strategic pushes. The container that gives every task its purpose.
PLANNING SYSTEMPlan what your team
Plan what your team
intends to do.
Initiatives, intents, tasks, workspaces — all in one place. No more scattered Asana, Linear, and Notion silos.
v1.4 · macOS · Windows · Linux
synap.app/acme/planning
BACKLOG
INTENTCut onboarding from 3 days to 1
TASKSketch the import wizard
IN PROGRESS
INITIATIVEQ2 — Multi-LLM rollout
TASKWire the provider selector
DONE
TASKShip sync engine v2
INTENTMove drafts to workspace zone
4SURFACESinitiatives · intents · tasks · workspaces
1SOURCE-OF-TRUTHplanning lives next to docs and chat
0SETUPno boards to configure, no schemas to design
100%SHAREABLEevery plan is a real, addressable file
01 · INITIATIVES, INTENTS, TASKSThree layers.
Three layers.
One plan.
Initiatives are the why. Intents are the what. Tasks are the how.
The what
Outcomes, not chores. Intents declare the result the team is going after — tasks come later.
The how
Concrete, shippable work. Drag onto a kanban, assign, close — without losing the intent above it.
02 · WORKSPACESA temporary lens
A temporary lens
for one shared goal.
Workspaces bundle the initiatives, intents, tasks and people working a single goal — without the permanence of a project tool. Spin one up for a launch, a sprint, or a quarterly bet, then dissolve it when the work lands. Every artifact lives on in your mind.
VS SCATTERED PM TOOLS
One mind. Not five tabs.
Why a planning surface that lives next to your docs beats a separate PM tool.
TODAY · ASANA + LINEAR + NOTION
Plans in 5 different tools
Tasks in one tool, docs in another, decisions in a third
Strategy lives in slides nobody opens twice
Half your week is copying status between tabs
AI can't see the plan because it's in a database it can't read
WITH SYNAP · PLANNING
Plans next to knowledge
Initiatives, intents, tasks — all in your Mind
Strategy, status and source-docs share one canvas
Status updates write back to memory automatically
Claude reads your plan and your docs in one shot
03 · INTENTS BEFORE TASKSDecide what.
Decide what.
Then decide how.
The intent layer keeps the why visible while the team breaks work into shippable pieces.
Outcomes,
not chores.
An intent declares what the team is trying to achieve, in plain language. Tasks come later — and every task carries its parent intent so the why never gets lost in the how.
Planning lives next to docs
Open the same Mind to find the plan, the spec, and the decisions behind both.
Drag intents into kanban
When an intent is concrete enough, drop it on the board as a task. The link upward is preserved.
Plans that
compound knowledge.
Free for personal mode, Pro for teams.
Free · No credit card · No telemetry