OpenBook® — the transparency ledger.

Your CFO shouldn’t have to take our word for compression. They can read it.

OpenBook® is the auditable ledger behind every Allari engagement. Every ticket, every billable hour, every retired root cause, every dollar of spend — live, timestamped, and accessible to your team, your CFO, and your board at any time. The deflationary contract enforces compression. OpenBook® is how you verify it.

What OpenBook® tracks

Six dimensions. All live. All auditable.

1. Tickets. Every ticket logged in your environment — open, in-progress, resolved. Categorized by root-cause taxonomy. Aging tracked against the contract’s chronic-backlog definition. Every state change timestamped.
2. Billable hours. Every senior-engineer hour spent on your environment. Logged by named engineer, by ticket or work item, by category. Year-over-year hour count is the basis for the annual recalibration of the contract fee.
3. Root causes retired. Recurring ticket categories that have been permanently fixed and removed from the queue. Each retired root cause documented with the runbook that replaced it. Compression is measured by what gets retired, not what gets closed.
4. Spend-to-date. Cumulative billed-to-date against the contract baseline and against the not-to-exceed guardrail. Surfaced live in the ledger so the customer’s approver sees current spend, projected work, and any decision required before an overrun is approached.
5. Compression metrics. Chronic-backlog percentage, median time-to-resolve, recurrence rate per category, year-over-year hour-count delta. The four metrics the monthly compression review is conducted against. All historical values retained.
6. Engineer activity. Named delivery team activity log — who handled what, when, and what the resolution involved. Senior-engineer continuity is contractually guaranteed; the activity log is how it’s verified.

What it looks like — a page from the ledger

Below: a representative row-level view of the ticket log. Names and ticket IDs are illustrative; the data shape and fidelity match production.

Illustrative ledger view. Real engagements show 60–200 ticket rows per week, with full filtering by category, engineer, root-cause taxonomy, and date range. Customers can export to CSV at any time.

Tickets this week:

47

Hours this week:

62.5

Root causes retired YTD:

31

Chronic backlog:

7.2%

Who can audit it

Your team. Your CFO. Your board. At any time.

• Your IT team. Named access for the customer’s IT leadership and any designated team members. Live view of every ticket, every hour, every root cause. No separate request. No reporting cadence to wait for.
• Your CFO and finance team. Read-only access to spend-to-date, year-over-year hour count, projected work against the contract guardrail. The annual recalibration of the contract fee is computed from the same data the CFO can audit independently.
• Your board and audit committee. On-demand access for any board member or audit committee chair. The compression metrics that justify the contract are visible without requiring a sales conversation or a custom report. Defensible to anyone who asks for the math.
• Allari’s delivery team. The same ledger Allari uses for the monthly compression review. There is no separate “internal view” the customer doesn’t see. One source of truth.

How OpenBook® enforces the deflationary contract

The contract is only as good as the ledger behind it.

The deflationary contract has four structural features: three-year term, annual recalibration against actual workload, ninety-day exit clause, and renewals tied to compression performance. Each one depends on auditable data.

Recalibration depends on the ledger. The annual fee is set by the prior year’s actual ticket volume, hours billed, and root-cause closure rate. OpenBook® is where those numbers live. The customer doesn’t take Allari’s word for the math — the customer reads the same numbers Allari uses.

The monthly compression review depends on the ledger. Each month, senior engineers from both sides review the prior-month compression curve against the contract baseline. Without a live ledger, the review is a sales meeting. With a live ledger, the review is an audit.

Renewal performance depends on the ledger. At the end of the three-year term, renewal terms are computed from the documented compression trajectory. If run-rate didn’t bend, the contract doesn’t renew at the prior rate. The ledger is the evidence either way.

This is why every Allari engagement begins with OpenBook® instrumentation before any compression work begins. The ledger isn’t a reporting product layered on top of the engagement — it is the foundation the engagement is built on.

Why this matters

Most ERP support contracts give you a report. Allari gives you the ledger.

The standard ERP support engagement has a quarterly business review — a slide deck prepared by the vendor showing whatever metrics support the renewal. The customer sees what the vendor chooses to show. The underlying data sits in the vendor’s ticketing system, behind their firewall, on their schedule.

OpenBook® inverts that. The customer has the ledger. The vendor builds the slide deck from the same data. The slide deck becomes optional, because the customer has the source data and can audit any claim in it independently.

That distinction is the difference between a contract that depends on trust and a contract that depends on math. The deflationary thesis only works because OpenBook® makes the math accessible to the side of the table that’s paying for it.

See OpenBook® for your environment

A 45-minute working session walks you through an anonymized live ledger from an active engagement, then mocks up what the same view would look like for your platform, your ticket categories, your team. You leave with a sample report you can hand directly to your CFO. Book the working session, or read the contract structure.