Skip to main content
Regulaxy

Calculator

What one window costs to coordinate.
With your numbers, and the arithmetic in the open.

This calculator does one thing: it multiplies the coordination hours you actually spend by your own loaded hourly cost, and shows how much of that can be removed. It does not know what you will save — nobody does. What it does is let you change every assumption and see immediately how much the answer depends on it.

Evaluate

The whole calculation runs in your browser. Nothing is sent to our servers and nothing is stored anywhere. The share link encodes the numbers in the URL itself, so even that does not pass through us.

Your numbers

Every field here is your estimate, defaults included. Change all of them.

Estate and windows

Estate and windows

Between 1 and 100,000. Not used in the money arithmetic — it estimates window count and checks the result for plausibility.

Windows you actually coordinate per year, not per host. Between 1 and 5,000.

Using the rule the product enforces — every 3 months for externally exposed systems, every 6 for internal — and roughly 8 hosts per system.

The coordination work

The coordination work

Anyone who spends time on the coordination itself: the coordinator, the system owner, the approver. Between 1 and 20.

Coordination time only — finding, agreeing, inviting, reminding, recording. Not execution time. Between 0.1 and 40.

0 to 100.

A reschedule needs coordinating again, but not from scratch. 0 to 100.

Cost

Cost

Currency

Salary plus overhead. Enter it in the selected currency — nothing is converted.

The assumption that decides the answer

This is the one assumption we cannot supply. We hold no customer measurement for it and will not invent one. 0 to 90.

Optional — from your own quote

Optional — from your own quote

Leave empty if you have no quote. Regulaxy prices are not published, which is why payback cannot be computed without it.

Windows where two dependent systems would have gone down together. 0 to 500.

Optional. Shown separately and kept out of the headline saving — see below.

The result

Coordination hours today

311hrs

Including the reschedule overhead

Coordination hours after

217hrs

At the reduction you entered

Hours saved

93hrs

The difference between the two

Full-time equivalent

0.2

At 1,800 working hours a year

Coordination cost today

$17,078

per year

Annual saving

$5,123

per year

Net saving

Enter a licence cost to compute

per year

Payback

Needs a licence cost

Measured separately, deliberately

Collisions blocked before booking
4per year
This is a count, not a sum. The collision engine is the differentiator with no known price, and we are not giving it an invented one.

How much the answer rests on one assumption

The same arithmetic at three different reduction assumptions plus the one you chose. If the spread is wide, that is what you need to know before putting the number in front of a board.

ReductionHours savedAnnual saving
15%47$2,562
30%Your value93$5,123
45%140$7,685

How this is calculated

The full arithmetic, line by line
  1. base hours = windows × people × hours each
  2. reschedule overhead = windows × reschedule share × people × hours each × reschedule cost
  3. hours today = base hours + reschedule overhead
  4. hours after = hours today × (1 − reduction)
  5. hours saved = hours today − hours after
  6. annual saving = hours saved × hourly cost
  7. FTE = hours today ÷ 1,800
  8. net saving = annual saving − licence cost
  9. payback in months = licence cost ÷ (annual saving ÷ 12)

There is no hidden coefficient and no value supplied by us. Every number in the arithmetic is one of the fields above.

What this model does not know

The whole calculation runs in your browser. Nothing is sent to our servers and nothing is stored anywhere. The share link encodes the numbers in the URL itself, so even that does not pass through us.

  • We hold no customer measurement of the reduction share, which is why it is a field rather than a constant. If it looks optimistic to you, lower it and watch what happens.
  • Loaded hourly cost is your estimate. The default is a starting point, not a market figure.
  • This counts coordination hours only. It makes no attempt to price risk, a regulatory penalty or reputational damage.
  • Hours saved is not automatically money saved. In most organisations those hours move to other work rather than removing a headcount.
  • Onboarding, training and ongoing administration are not included. Ask for them in the quote.
  • Host count does not enter the money arithmetic. It sizes the quote, and the quote is the number we do not publish.

Is the number big enough to talk about?

If it is, we would happily walk it with you and say which of your assumptions look high to us. If it is not, that is a good answer and it did not need a meeting.

Note
  • The numbers you entered never reached us. If you want us to see them, send the link.