Measured service, not promised service.

Most service tools record what happened. Astrolabium One measures it against what was promised, shows the customer the same figures, and says plainly where its own data is weak.

The contract is the clock.

A promise to respond in 15 minutes means nothing if the clock runs on a Friday that the contract excludes, or keeps running while you wait for the customer. Astrolabium One reads the contract first: the service line, the severity, the calendar, the holidays. Then it runs the clock exactly as agreed.

Illustrative screen with sample data.

Coverage before work.

When a request arrives, the first question is whether it is covered: in the contract, in hours, in scope, with entitlement left. Out-of-scope work goes to a quote or an approval before anyone spends an hour on it. Margin is protected at the door, not argued about at renewal.

  1. A request arrivesEmail, portal, Teams, the app or phone
  2. In the contract?The service line and the scope
  3. In hours?The customer's calendar and holidays
  4. Entitlement left?Hours, devices or users in the plan
CoveredWork starts and the SLA clock runs
Not coveredA quote or an approval first, before anyone spends an hour
How coverage is checked before work starts.

A breach pays for itself, automatically.

The contract carries its credit schedule. When a breach happens, the credit line is minted at once, the customer sees it in the portal, and the invoice-ready export carries it. Nobody has to admit it in a meeting; the system already did.

  1. The SLA is breachedRaised exactly once
  2. The schedule appliesThe credit rule in the contract
  3. The credit is mintedA line on the customer's account
  4. The customer sees itIn the portal and the value statement
  5. Finance gets itIn the invoice-ready export
What happens after a breach, with no one in a meeting.

Every figure says how sure it is.

Each pane and report shows when its data was collected, how confident it is, and how each figure is defined. A silent collector raises a page instead of a green dashboard. Customer reports end with an integrity statement that names what was late or missing.

Illustrative screen with sample data.

What we refuse to do

Some shortcuts make a product look better in a demo and worse in production. We leave them out.

No blended scores

Service, estate, security and commercial are graded separately. One average hides the one that matters.

No autonomy percentages

Reason proposes and people approve. We do not market how much it does on its own.

No compliance claims

We build for NCA ECC-2 and PDPL and help you prepare evidence. We never say the product makes you compliant.

No agents on your devices

We read Microsoft's own interfaces. Nothing to deploy, patch or explain to your security team.

No invoices from the product

An invoice-ready export goes to your finance system. Billing stays where your auditors expect it.

No hidden provider actions

Every action in a customer's tenant is in a ledger the customer can read.

Know it's handled.

See Astrolabium One on your own estate. Tell us what you run and we will show you the screens that matter to you.