Solutions
The four problems we are called about most
It is a short list on purpose. These four recur in company after company, each carries money, and each gets measurably better when it is modelled instead of run on judgement. For each we have a method we have used before, research we have published, and in three cases a calculator you can run on your own numbers before you talk to anyone. Each engagement starts with an audit. A platform, if there is ever one, comes last.
Which of your projects is losing money, and since when
For consultancies, agencies, engineering and construction firms running many projects at once. A forecast of the loss per project while a manager can still do something about it. Explore Capacity, scheduling & acceptance 02Which orders to take, and in what order to run them
For manufacturers, logistics operators and field-service businesses. Acceptance, batching and scheduling modelled together, so the plan holds when the forecast does not. Explore Warranty, remediation & intervention 03Which cases to fix first, when the queue is longer than the crew
For warranty, remediation and maintenance backlogs. The queue ordered by what each case will cost if it waits, with the reason beside each line. Explore Verification of critical software 04Proving a rule holds for every input, when testing is not enough
For decision logic that must not fail quietly. A machine-checked proof of the rule, and a clear line around what has been proved and what has not. ExploreNot sure which of these your problem is, or whether it is one at all? The decision patterns are the longer answer, and a first conversation is the shorter one.
Which one is yours
How each one shows up, and what stands behind our answer
Each of these starts as something you notice long before you can name it. Under each one we list the evidence behind our method, including where that evidence is still only an idea, because you should know that before you pay for an audit and not after.
Projects land under margin and nobody saw it until the period closed.
Run it yourself
What stands behind it
More demand than capacity, and what you take is decided first-come or by whoever asks loudest.
Run it yourself
What stands behind it
A queue of defects or claims, fixed worst-first, with no view of what waiting costs.
Run it yourself
What stands behind it
Logic where a silent wrong answer is the failure, and tests can only cover the cases you thought of.
Run it yourself
No browser tool: a proof is not something you can approximate in a form.
What stands behind it
Start with the decision
Bring us the one that keeps going wrong
If it recurs, carries money, and no existing system handles it well, it is the kind of problem we start from. Describe it in your own words and a partner will reply.