One file, fully offline
A single HTML file. No install, no server, no cloud, no macros, no executable for IT to vet. Open it in a browser and work — on a laptop, a network drive, or a USB stick.
PlanX turns what you actually know — phases, people, test demand, equipment, travel, capital, outside services — into a time-phased cost, FTE and duration envelope. Every number traces back to a row you can point at. One self-contained file. Nothing to install.
They fail because nobody can show where the number came from. The annual planning spreadsheet is a black box with a total at the bottom. When finance challenges a line, the PM defends it from memory. When the year goes red, nobody can reconstruct which assumption broke. And next January, the whole exercise starts again from nothing.
Estimate too low and you spend the year in the red. Estimate high without being able to justify it and the work doesn't get funded. The gap between those two outcomes is not accuracy — it's whether you can defend the number line by line, in the room, under pressure.
PlanX is built for that room. It doesn't claim your estimate is right. It makes every figure in it inspectable, reproducible, and arguable.
PlanX isn't a blank spreadsheet with formulas. It's a model with a shape, and the shape is what makes the numbers traceable. Each layer feeds the next, in this order.
A single HTML file. No install, no server, no cloud, no macros, no executable for IT to vet. Open it in a browser and work — on a laptop, a network drive, or a USB stick.
Cost, FTE and duration all decompose back to the inputs that produced them. When someone asks "where does that come from?", you open it rather than explain it.
Capital equipment is a global pool, not a per-plan assumption. Two projects fighting over the same rig show up as contention instead of as two plans that each look fine alone.
When demand exceeds capacity, PlanX shows the work as unscheduled and flags the overflow. It never quietly overlaps jobs to produce a comfortable answer.
Optimistic, expected and pessimistic input sets through the same deterministic engine. You can see exactly which assumption moved the number — which a confidence interval will never tell you.
A person is spread over the phases they work on, with a shape and day-proration at the edges. It's how staffing actually behaves, and it removes a whole class of silent estimating errors.
Snapshot the plan you got approved. As inputs change, see what moved against the number you committed to — and be able to say why.
Model many projects competing for the same people and the same equipment, then roll the cost and FTE up. That competition is the whole point of annual planning.
Everything lives in your file, on your machine. Nothing is transmitted, synced or tracked — by design, for environments that require it.
“This machine buys you nothing. It arrives after the work it was meant to serve has already finished.”
One workspace, walked end to end: the case each project makes for itself, the phases everything hangs off, the equipment every plan competes for, the cost that falls out of it, and the artifact you carry into the funding conversation.
The charter lives in the model, not in a separate document that goes stale. Description, problem, proposed solution, recommendation and a costed benefit table sit alongside the plan they describe — and the derived cost is checked against the target you typed, so you find out you are 18% under before someone else does.
The phase gantt is the spine. Anchor a person, an expense or a test to a phase, then move or stretch that phase — everything on it follows, with nothing to retype. And when a phase can’t contain the testing inside it, PlanX says so and recommends a date; it never quietly moves the end for you.
Projects compete for the same rigs, chambers and benches, so testing is never a per-project question. What each project needs, where the scheduler actually put it, what that does to every machine, and what it costs you when it doesn’t fit.
One pool of equipment, shared across every plan. Set each resource’s capabilities, calendar and downtime once — and weigh a proposed rig against the capacity you already own. Then read the demand as a register of every process type per unit, and drill to the job register: every scheduled occurrence, with its resource, dates, touch hours and FTE.
Every dollar and hour, time-phased against that same spine. People allocate across phases by a shape rather than a flat number, a shared roster carries their rates and locations, and a monthly roll-up combines labor and expense into the Total cost on the project header — nothing re-keyed, every figure still traceable to its row.
What you actually walk into the room with. Every one of these is generated from the same model you have been editing — nothing re-keyed, nothing to drift, and every figure still traceable to the row that produced it. Click any report to read it full size.
Every plan’s cost against what it returns, side by side — modelled cost, the variance to your approved estimate, payback, and how well each case is actually made. Plus the whole portfolio on one timeline, and the cost broken down by where it goes, against baseline as the year unfolds.
Point Copilot, ChatGPT or Claude at a planning spreadsheet and it sees numbers with no structure behind them. It can't tell which figure is an input and which is a result, or what would change if a phase slipped.
PlanX exports the whole model in one readable file — phases, allocations, demand, the resolved schedule, and the outputs those inputs produced. An assistant reading it can trace a cost back to its source, explain what a change would do, or draft the justification narrative for a business case.
The file introduces itself, so the assistant knows what it's looking at without being told. PlanX transmits nothing on its own — what you choose to share stays your call.
PlanX is built for program and engineering managers producing funded plans under time pressure — hardware development, test and validation, capital-intensive engineering, anything where people, rigs and money are all constrained at once and all three have to be justified.
It asks more of you than a spreadsheet does. You have to state your phases, who is on them and in what shape, what your test demand looks like and where it lands. That is exactly why the answer survives its first real challenge — and why next year's plan starts from this year's model instead of from nothing.
One-time purchase with one year of updates included (*). Your version runs forever — renew only if you want newer releases. No subscription, no lock-out, no phone-home. Licensed per organization.
No. PlanX doesn't do critical path, task dependencies or resource levelling, and doesn't pretend to. It answers a different question — what a project will cost and how long it will take, before it's approved. Phases are declared, not solved. If you need a working schedule to run the project, build it in a scheduling tool.
Deliberately not. Probabilistic output is defensible mathematically and indefensible in a planning meeting, because nobody in the room can reconstruct it. PlanX runs optimistic, expected and pessimistic input sets through the same deterministic engine, so the difference between scenarios is visible rather than buried in a distribution.
No. PlanX is a single HTML file. Save it and open it in your browser — no installer, no admin rights, no executable, no macros. In locked-down environments, that's the point.
Yes. PlanX never needs an internet connection to model, compute or export, and it never transmits your data anywhere. It works the same on an air-gapped machine as it does online.
In your browser's local storage and in the JSON files you export. Nothing is uploaded, synced or tracked. You own the file and everything in it, and you can back it up like any other document.
Editing and reports lock until you enter a license key. JSON export never locks — ever. A tool whose entire claim is that your numbers trace to your inputs must not hold those inputs hostage.
Your purchase includes one year of updates, and your version runs forever. After that first year you only renew if you want access to newer releases — there's no recurring charge and nothing stops working.
They're separate tools that share a philosophy. PlanX models the program that hasn't happened yet — cost, FTE and duration before approval. DARIL governs the one that has — decisions, actions, risks, issues, lessons and deliverables. Each stands entirely on its own; you don't need one to use the other.
Any modern desktop browser. Chrome or Edge are recommended. PlanX is designed for desktop use on Windows, macOS and Linux — on tablets and phones the browser restricts how a local file stores its data, and your work may not save reliably.
Yes. PlanX exports the whole model — inputs, resolved schedule and outputs — as one readable file, and the file describes itself so an assistant knows what it's looking at. PlanX itself transmits nothing; because it stays on your machine, you control what you choose to share.
The trial is the complete product — the same single offline file, every feature unlocked. It runs for 30 days, marks exports with a small "trial" watermark, then asks for a license. Thirty days rather than fourteen, because PlanX is judged against a real planning exercise and you may not have real numbers to model for a fortnight. Tell us where to send it.
Unzip it, then open the HTML file in your browser — no install, no admin rights. It works the same offline.
(*) How updates work. PlanX is a single offline file. When a newer release comes out, download the latest copy (the same file linked above) and paste in your license key. Your key unlocks any release dated within your one-year update window; your existing copy keeps working forever either way, and you only renew if you want releases beyond that window.