Statuses
Define each stage's own statuses and mark which are initial, on hold, blocked, or exit-ready.
DPO Project Management lets holdings build their own product flows — stages, statuses, gates, and tools — as many as they need. Put each product on the right flow and it only advances on evidence.
Flow Maker
Partner onboarding
Stage 2 · Vetting
Statuses
Stage tools
How it works
Every holding runs products differently. DPO gives you the building blocks to model how you work — then enforces it, product by product.
Model every process your holding runs — export, onboarding, launch, anything — as its own flow.
Collect exactly the data each flow needs, then put every product on the flow that fits it.
Teams work inside each stage. Products only advance when the stage's rule is satisfied.
Flows
Start from the built-in export-readiness template or build your own from scratch. Each product runs on the flow that fits it — and every flow is versioned, so changes never break work in progress.
Take supplier products from intake to foreign demo, transfer, and support.
Intake & Worthiness
Decision recorded
Maturity
Target version approved
Preparation
Workstreams + Foreign Demo Ready
Demo
Customer interest
Transfer
Delivery completed
Support
Support closed
Inside a stage
Every stage in every flow is configured from the same parts — no code, no tickets to the vendor.
Define each stage's own statuses and mark which are initial, on hold, blocked, or exit-ready.
Decide who can move a stage between statuses — holding, supplier, leadership, or anyone — and when a reason is required.
Snap built-in engines onto any stage: forms, scoring, checklists, workstreams, demos, deliveries, tickets.
Choose what unlocks the next stage — a simple exit-ready status, or a built-in gate like a recorded decision or completed delivery.
20 built-in stage tools
The platform
DPO doesn't replace your Git, CI, or issue tracker. It sits above them, holding the process, the evidence, and the accountability.
A single command center per product — whatever flow it's on: versions, tasks, commitments, documents, journey timing, meetings, and audit, one tab away.
Harbor CRM
Export readiness
Kite Payments
Partner onboarding
Pulse Analytics
Internal launch
The holding at the center, organizations in orbit, products by stage. Overdue work glows red.
Submit for review, approve or request revision, sync to Jira. Finishing late? A delay reason is required.
Build intake and product forms with sections, required fields, and completion tracking — then share them by public link.
Overdue tasks, pending reviews, and critical risks surface automatically — and escalate by email without spamming.
Minutes, decisions, and action items linked to the products they affect.
Documents attach to products, stages, and tasks — so every gate has proof behind it.
Track commitments, score VCs, and keep a risk register next to the work itself.
∞
flows per holding — one for every process
20
built-in tools you can attach to any stage
14
field types in the Form Maker
7
advance rules, from status-based to delivery gates
Built for the whole chain
Portfolio control, gate approvals, and overrides when the business needs them.
Review, approve, and own the stage-specific decisions and workstreams.
Produce the assets each stage calls for — tracked, reviewed, delivered.
Own their products, submit to the holding, and execute tasks — only on their own data.
Integrations
Link, create, and sync issues from governance tasks.
Pin version baselines to repository references.
SMTP delivery for assignments, due dates, and escalations.
Documents and marketing assets in object storage.
Let AI agents file intakes and work tasks over a hosted MCP endpoint.
Bring your own provider keys for drafting and summaries.
Security & control
Short-lived tokens with rotating refresh cookies, permissions enforced in the API and the database, and a record of who changed what — and why.
Each holding runs in its own tenant with its own members, products, and settings.
PostgreSQL RLS scopes every query to the right VC — even if an API filter is missed.
Permissions are the union of assigned roles. Gate overrides stay with leadership.
Sensitive actions are logged, retention is policy-driven, and backups run on schedule.
Create a holding workspace, start from the built-in template or a blank flow, and put your first product on it.