If this changes, what does it cost us?

Every engineering program asks this. We are building the tool that answers it the same day.

Earned value for the coffee maker program at the reporting date, with cost and schedule performance and the estimate at completion.

Why we built it

The problem

The tools aren't connected

The schedule, the budget and the design each live in a different tool. To see what a change costs, someone copies numbers between them into a spreadsheet, which takes about two weeks.

Our answer

One plan for all of it

Each task is linked to the part it builds, and each risk to both. Cost is measured against the same plan the dates come from.

Our rules

Use the standard

Where an open standard exists, we follow it, and test against the standards body's own example files.

Say what was left out

If we couldn't read part of your data, we tell you above the answer.

No AI in the numbers

Scheduling, costing, modeling and approvals never use an AI model. Switch the assistant off and every number stays the same.

History is never rewritten

Nothing is overwritten. To reverse a decision, you record a new one with a reason.

Your data is yours

Models are saved as standard SysML v2 files, and you can export the rest of the program data too.

No claims we can't back up

Where something isn't built yet, the capabilities page says so.

Who is building it

Cameron Johnstone

Founder

A systems engineer who has spent his career on the kind of programs this tool is for, in nuclear power and aerospace. On those programs, nobody knows what a slip costs until the review, and a requirement that stopped being traced isn't noticed until qualification.

Previously an engineer at a major aerospace and defense prime.

Tell us what you need

We are building the rest with a handful of real programs. It's a twenty-minute call, and if we're not a fit, we'll say so.

Talk to us Read the announcement