A planning operating system that keeps the operational thread intact.
OpenPlan is being shaped for transportation and public-sector delivery work where analysis, decisions, risks, datasets, meetings, and reporting need to stay connected. The goal is not more dashboard clutter. The goal is cleaner execution.
Operational thread
What stays connected
The product direction is intentionally operational: fewer broken handoffs, clearer state, and more honest evidence-to-action continuity.
Projects stay legible
Scope, owners, blockers, and deliverables stay visible instead of dissolving into email and meeting notes.
Map context stays attached
Analysis, linked datasets, and reporting context remain connected to the actual work instead of becoming isolated screenshots.
Risks and decisions stay alive
The product is being shaped around operational memory, not just dashboard snapshots.
Built for lean teams that need continuity, not software sprawl.
The product is being designed around real planning delivery rhythm: a team needs to see what the project is, what changed, what is blocked, what evidence supports the next move, and what still needs review.
Messaging guardrail
Honest product language only
- • Do not present prelaunch access as a guaranteed pilot admission.
- • Do not imply production readiness where hardening is still in progress.
- • Do not use AI-replaces-planners rhetoric.
- • Do not overstate mapping or data-readiness posture.
The useful promise is practical: less rework, better continuity, clearer handoffs, and more trustworthy evidence-to-action flow.
Good fit now
Best for teams already doing real delivery work.
Probably wait or talk first
Not ideal for teams expecting a finished enterprise platform today.
Choose the access path that matches your operating need.
OpenPlan is still in active buildout. Prelaunch pricing reflects early access and shaping feedback, with a 15% discount applied before launch. If the right tier is not obvious yet, use the scoped discussion path first.
Starter
$212 /mo
$249/mo standard price before launch
Best for a single agency team validating monthly workflow improvements.
- • 1 workspace
- • Up to 100 corridor runs/month
- • Grant-ready reporting templates
- • Email support (2 business days)
Secure Stripe-hosted checkout. AI may accelerate drafting and data prep, but final analysis is human-reviewed. No guarantee of funding awards or regulatory approvals.
Professional
Recommended$679 /mo
$799/mo standard price before launch
Best for active planning teams running production analysis every week.
- • Up to 5 workspaces
- • Up to 500 corridor runs/month
- • Priority support + onboarding office hours
- • Advanced KPI and methods exports
Secure Stripe-hosted checkout. AI may accelerate drafting and data prep, but final analysis is human-reviewed. No guarantee of funding awards or regulatory approvals.
Agency
$1699 /mo
$1999/mo standard price before launch
Best for consultants and multi-agency programs needing scale and governance.
- • Up to 20 workspaces
- • Up to 2,000 corridor runs/month
- • Team training + implementation review
- • Dedicated success cadence
Secure Stripe-hosted checkout. AI may accelerate drafting and data prep, but final analysis is human-reviewed. No guarantee of funding awards or regulatory approvals.
Not ready to subscribe?
Use the softer path and stay in the loop.
If your team is interested but not ready for prelaunch checkout, the right move is to ask for pilot updates or a fit conversation first. That keeps the process honest and prevents a forced purchase decision too early.
Best use of this page
- • Read the fit guidance before treating pricing as the next automatic step.
- • Use prelaunch checkout only if your team is ready for active usage and grounded feedback.
- • Use the contact path if you want updates, scoping, or a cleaner fit decision first.
Straight answers before anyone buys in.
This page is designed to keep the OpenPlan offer clear: what it is, who it fits, what stage it is in, and how we talk about AI and mapping without bluffing.
What is OpenPlan?+
OpenPlan is an emerging modular planning operating system designed to keep projects, decisions, risks, datasets, and map-based analysis in one operational thread.
Who is it for?+
The strongest fit today is lean public-sector and transportation planning teams, plus consultants supporting rural, county, regional, or tribal planning work.
What problem is it meant to solve?+
A lot of planning work breaks down after the meeting or analysis. Decisions, source files, risk notes, and next actions get scattered across different tools. OpenPlan is being shaped to reduce that handoff failure.
How is this different from a normal dashboard?+
A dashboard reports status. OpenPlan is being built to preserve context across projects, decisions, meetings, datasets, and outputs so teams can move from evidence to action without losing the thread.
Is OpenPlan fully launched?+
Not as a broad general-release product. The current phase is active buildout, prelaunch packaging, and early customer access. Direction is strong, but product hardening is still ongoing.
What does prelaunch access mean?+
It means you are joining during an early customer-access phase while the product is still being hardened. Pricing reflects that stage, and the best-fit customers are teams willing to use the product seriously and share grounded feedback.
What kinds of workflows is OpenPlan being shaped around?+
Current direction includes project and deliverable tracking, decisions/issues/risks, meeting continuity, linked datasets and map context, analysis-to-report continuity, and grant/proposal readiness support.
How should we think about AI here?+
Carefully and practically. The useful standard is whether AI reduces rework, preserves context, and makes the next decision clearer. Final analysis still requires human judgment and review.
How should we think about data readiness and mapping?+
With explicit honesty. If geometry is ready, say so. If coverage exists but thematic support is partial, say that too. Trust matters more than flashy maps.
Want to pressure-test fit before subscribing?
That is the preferred move if your workflow is unusual, high-stakes, or still being defined. We can scope the right access path before asking you to commit.