AI on the same surface as the work.
Generate a full project tree from a prompt. Refine descriptions in place. Run analysis against the live plan — not a copy of it, pasted into another window that forgets the context the second you close the tab.
ODINPMP
PROJECT COMMAND,
WITH TEETH.
An AI-first planning deck for teams who would rather ship than perform. Strategy in. Tasks out. No busywork.
- STATUS
- PRIVATE BETA
- AI
- BUILT-IN
- TENANCY
- MULTI
- WAITLIST
- OPEN
Most planning tools are filing cabinets.
This one is a drafting table.
The cabinet version expects the plan to arrive finished — your job is to type it in, keep it tidy, and produce a status update on Friday. OdinPMP starts a step earlier: the first draft of the plan happens here, against your constraints, and the record of what was decided stays attached to the decision instead of the meeting.
Four moves, in order.
A project goes from charter to receipt without stopping in anyone's inbox. The trail it leaves behind is the artifact.
- 01
CHARTER
Drop the mission, constraints, and outcomes. OdinPMP drafts the first project tree from intent instead of asking the team to start in a blank grid.
- 02
GENERATE
Epics break into stories. Stories break into tasks. Owners, statuses, and types land in the tree where the work will actually be run.
- 03
RANK
Run the hard tradeoff head to head. The next priority earns its slot because the team chose it, not because someone shouted last.
- 04
DELIVER
Status, assignee, and history are first-class events. What changed, who changed it, and why — inspectable long after the sprint ends.
The load-bearing parts.
The capabilities we couldn't cut without changing what the product is. Everything else is implementation detail.
A02
PAIRWISE RANKING
Decide what ships next by ranking it head to head against everything else. No averages. No silent priorities.
A03
CONTRIBUTOR SIGNAL
Movement, reviews, comments, mentions — the visible record of who did the work, kept legible without ceremony.
A04
EVENT-NATIVE STATE
Status and assignment live on an event log. The label on a card is a view of the truth, not the truth itself.
A05
PER-TENANT AI
Your OpenAI keys. Your prompt policy. Your isolation boundary. The product respects that boundary by default.
A06
VAULT, COMMENTS, MENTIONS
Files, threads, and @-mentions stay attached to the task that needed them — not to a parallel channel that forgets the context by Monday.
A07
MULTI-TENANT
Separate organizations, separate rules, separate AI configuration. Designed in from the first schema, not retrofitted.
Three inversions.
Each is a question every PM tool answers — quietly, in its defaults. These are the three where OdinPMP answers differently, and why.
- 01 / WHERE THE PLAN STARTS
A prompt and a constraint, drafted inside the project tree.
INSTEAD OF Elsewhere — a decision someone already made, copied into a grid you maintain.
- 02 / WHERE PRIORITY LANDS
On the slot the team ranked head-to-head against everything else.
INSTEAD OF On the slide whoever spoke last refused to back down from.
- 03 / WHERE HISTORY LIVES
On an event log that explains what moved, who moved it, and when.
INSTEAD OF On the current label, and the comment thread someone half-remembers.
A short list. Four things we believe hard enough to start over for. Everything in the product is downstream of these.
- PRINCIPLE 01 — ARTIFACT
The plan is the artifact.
What ships is the project, not the deck about the project. We keep the plan close enough to the work that nobody has to translate it back at the end of the quarter.
- PRINCIPLE 02 — PROXIMITY
AI belongs in the tree, not in a tab.
A model that has to be invited into a meeting is a search bar with better marketing. Generation, refinement, and analysis live inside the project — where the work and the history already are.
- PRINCIPLE 03 — PROOF
Priority is something a team earns by choosing.
A roadmap survives because the people building it ranked it against the alternatives. Pairwise, on the record, every cycle. The result is not negotiated in the hallway.
- PRINCIPLE 04 — BOUNDARY
Tenancy is a boundary, not a setting.
Your keys, your prompts, your statuses, your data. The architecture starts there. We did not retrofit it after the screenshots got popular.
SIGNED ODINPMP COMMAND BUILD · v0 · 2026
The first cohort is hand-seated.
We're still picking it.
Tell us what your current planning tool refuses to do. We are reading every entry and using them to decide which of the rough edges in v0 get smoothed before launch and which stay as a feature.
END / ODINPMP · v0 · PRIVATE BETA