What to do first

These are the changes that move the grade. The check each one cites is named at the end of the report.

1. Assign an owner to $28.9M of ARR. 1,085 active accounts have no rep. The top rep holds 25.2% of ARR, and parent is the least-covered tag field. Owner coverage drives two checks: whether the tags actually cover the book, and whether one owner holds the book. This moves Multi-Dimensional Insights toward B.
2. Add a definitions tab. Write one line each for the terms not yet written down: MRR, GRR, new and reactivation. Keep the existing lines for ARR, NRR, churn, expansion and cohort. Written definitions make the KPI table reproducible by someone outside the team. They also lift the check on whether the words in the definitions were written down, and they support the diligence-ready lens.
3. Normalize 2 tag fields. 2 fields carry case or whitespace variants of the same value. One pass of normalization removes them. This moves Multi-Dimensional Insights up one band.
4. Send the inputs we could not check. Export tags as of each month rather than one per account, so tag stability can be read. Add a units-or-price table or a payments table, which the diligence-ready lens lists as missing. This raises the share of the cube that is graded rather than assumed.
5. Re-grade after each month-end close. A monthly re-grade catches broken ties, duplicates and status drift before they reach the board pack. This keeps Audit-Grade Accuracy where it is.

Where the grade comes from

Inputs: 2 file(s), 8 sheet(s), 393,691 rows. Hazards handled: none. Checks run: 39 of 41. 2 could not be checked (listed below).

• Unified, Finance-Approved Foundation: 87.3 (B+)
• Audit-Grade Accuracy: 100 (A+)
• Cohort-Centric Design: 100 (A+)
• Multi-Dimensional Insights: 77.5 (B-)
• Anomalies: 100 (A+)

The two pillars below A+ share one cause: ownership. Unassigned owners appear in Unified, Finance-Approved Foundation as bookings with no owner. They appear again in Multi-Dimensional Insights, where they limit how far one owner’s share can be judged and how fully the tags cover the book.

Each check

Each item below is one piece of the rubric. The words are the check. The short code is the citation.

Unified, Finance-Approved Foundation

Bookings with no product or no owner

Unified, Finance-Approved Foundation. Cited as CP-05, owner.

This check measures how much of the latest book has no product, and how much has no owner.

In this file, 1,085 accounts have no owner, which is 25.5% of the book. The share with no product is 0%. Check score 30.

A buyer would ask: who is accountable for renewing the unowned quarter of the book?

Next step. Assign a product and an owner to the unassigned book before the next export.

The words in the definitions were written down

Unified, Finance-Approved Foundation. Cited as CP-07.

This check looks for the standard terms in the definitions text. It does not test whether those words match the numbers.

In this file, 5 of 9 terms were found. MRR, GRR, new and reactivation have no written definition. Check score 56.

A buyer would ask: how is gross retention defined, and how is a returning customer counted?

Next step. Write a short definition for each headline term the summary uses, in the same words the rubric expects.

Came through clean:

• Enough history to follow a customer (CP-01)
• Months where the whole book went quiet (CP-02)
• A customer goes quiet without a churn mark (CP-03)
• Revenue with no customer behind it (CP-04)
• Bookings with no product (CP-05, product)
• The product file covers the same months as billing (CP-06)
• Billed customers appear on the customer list (CP-08)

Audit-Grade Accuracy

Came through clean:

• The bridge foots on its own (CR-01)
• Customer detail matches the bridge ending (CR-02)
• Movements rebuild from the customer rows (CR-03)
• Product lines tie to billing (CR-04)
• The amount matches the status word (CR-05)
• Statuses tell a legal story over time (CR-06)
• Headline KPIs can be reproduced (CR-07)
• The bridge and the KPI table agree (CR-08)
• Product and segment totals add up (CR-09)
• Duplicate dollars that break the tie (CR-10)

Cohort-Centric Design

Came through clean:

• Customers have a start date (CO-01)
• The start date matches the first revenue month (CO-02)
• Too many customers share one start month (CO-03)
• A returning customer kept the same key (CO-04)
• Contract end dates exist and fall after the start (CO-05)
• Retention looks earned, not just unexpired (CO-06)
• A trailing year has a year of history behind it (CO-07)

Multi-Dimensional Insights

One owner does not hold the book

Multi-Dimensional Insights. Cited as SG-06.

This check measures the top owner’s share of the latest book and the share with no owner.

In this file, the book is spread across 3 reps. The top rep carries $28.5M, a 25.2% share. Another 25.5% has no owner at all. Check score 30.

A buyer would ask: how much of the book depends on a single relationship, and how much depends on none?

Next step. Reassign concentrated accounts and fill the unassigned ones so the book is not one rep’s.

Those tags actually cover the book

Multi-Dimensional Insights. Cited as SG-02.

For each tag, this check measures how much of the latest book sits on accounts with a real value.

In this file, the 6 tags cover 79.1% of the book on average. Parent is the least covered. Check score 55.

A buyer would ask: can concentration be read on the real customer, or only on the billing entity?

Next step. Fill the blank tags on the accounts that carry the book, starting with product and owner.

The same idea is spelled one way

Multi-Dimensional Insights. Cited as SG-04.

This check groups tag values that match once case and spacing are removed, and scores how many spellings each idea has.

In this file, 2 tag fields, segment and status, carry more than one spelling of the same value. Check score 80.

A buyer would ask: does a cut by segment split one group into several?

Next step. Pick one spelling for each category and apply it across the file.

Came through clean:

• The cuts a buyer expects are present (SG-01)
• A tag is a category, not free text (SG-03)
• Parent accounts are used (SG-05)

Anomalies

Came through clean:

• One customer spikes for a month and reverts (AN-01)
• A customer drops to zero and comes back unmarked (AN-02)
• One month moves the whole book (AN-03)
• Amounts do not match the file’s own format (AN-05)
• Duplicate rows (AN-06)
• The book sits in a few customers (AN-07)
• Prices did not move where an escalator was promised (AN-08)
• A sentence in the talking points does not match the file (AN-09)

What we could not check

• A new product line copies a price the account already had (AN-04). No month moved the whole book, so there was no mass-attach month to test.
• Tags stay stable over the year (SG-07). The file stores one tag per account rather than one per month, so drift cannot be read.

How this was graded

Weights:

• Unified, Finance-Approved Foundation: 25%
• Audit-Grade Accuracy: 30%
• Cohort-Centric Design: 15%
• Multi-Dimensional Insights: 15%
• Anomalies: 15%

Bands: A ≥ 90, B ≥ 75, C ≥ 60, D ≥ 45.

Bridge convention detected: monthly_sum. Rules version caeb8e512330.

Lenses: decision-ready not yet, diligence-ready no, AI-ready yes. Decision-ready waits on the two ownership findings. Diligence-ready also waits on a units-or-price table or a payments table.

Next step

The Strategic Revenue Intelligence Assessment walks through these findings with a FinQore analyst. It shows what a decision-ready and diligence-ready cube looks like for your business.

Your files are retained in FinQore infrastructure for the stated retention period and deleted on request.