← back to all models ← RevenueBench home
openai

openai/gpt-5.6-terra-pro

Mean 0.915 · 26/40 perfect tests · $7.98 total · modalities in: text, image, file · out: text · each card: the prompt → the correct answer (gold) → this model's actual answer

What do the modalities mean?

Modalities in means what you can send this model: text, images, files, video, or audio. Modalities out means what it can send back. Bench tasks feed text extracts, so modalities do not change the score. They are here so you know what this model can handle in real work.

data-crm 5 tests
stage-hygiene-auditPASS 1.00
Plain-English question: How much of the open DS2+ pipeline is missing a substantive why-buys, and is anything missing DS1 timestamps or out of order?
Prompt — what the model saw
Audit stage hygiene on the open pipeline below. Rules: a deal at DS2 or later must have a substantive why-buys (15+ characters, not a placeholder such as tbd, n/a, see notes). A why_buys value of the form LONG(n) means the real text was present but truncated for display; treat it as present and substantive. Every deal should have a DS1 entry timestamp. A deal whose stage entry timestamps are out of order regressed (an earlier-stage timestamp is later than a later-stage timestamp). Report: percent of DS2+ deals non-compliant on why-buys overall and by owner (use the owners table for names), count of deals with no DS1 timestamp, count that regressed, and three process fixes. State definitions before numbers.
cost $0.3018 · 48s · in 64,804 / out 4,950 tok
✓ noncomp_pct✓ no_ds1_0✓ regressed_0✓ per_owner_breakdown✓ definitions_first✓ three_fixes

✓ Correct Answer (ground truth)

Plain-English answer: 81.5% of the 124 DS2+ deals are missing a substantive why-buys — Alex Franklin 48, Cole Ingram 19, Dana Mercer 18, Bryce Harmon 15, Farid Osman 1 — and every deal has a DS1 timestamp with none regressed.
The answer in one line: n_deals = 156; ds2plus = 124; noncomp_pct = 81.5; bryce_noncomp = 15; no_ds1 = 0; regressed = 0 (+1 more below)
n_deals156
bryce_noncomp15
ds2plus124
no_ds10
noncomp_pct81.5
regressed0
per_owner_noncompAlex Franklin=48 of 61 (78.7%); Cole Ingram=19 of 22 (86.4%); Dana Mercer=18 of 22 (81.8%); Bryce Harmon=15 of 18 (83.3%); Farid Osman=1 of 1 (100%)
graded checksnoncomp_pct · no_ds1_0 · regressed_0 · per_owner_breakdown · definitions_first · three_fixes

Model's actual answer

show the model's full answer
Definitions:
- Why-buys non-compliant: DS2+ deal with no substantive why_buys; `LONG(n)` counts as substantive.
- Missing DS1: blank `t_ds1`.
- Regressed: any earlier-stage entry timestamp later than a later-stage timestamp.

Why-buys compliance:
- Overall: 101 / 124 DS2+ deals non-compliant = 81.5%.
- Bryce Harmon: 15 / 18 = 83.3%.
- Dana Mercer: 18 / 22 = 81.8%.
- Alex Franklin: 48 / 61 = 78.7%.
- Cole Ingram: 19 / 22 = 86.4%.
- Farid Osman: 1 / 1 = 100.0%.

Other hygiene:
- Deals with no DS1 timestamp: 0.
- Regressed deals: 0.

Process fixes:
1. Require a non-placeholder, 15+ character why_buys value before transition into DS2.
2. Enforce automated DS1 timestamp creation on initial stage entry; block progression if absent.
3. Add stage-transition validation that prevents recording an earlier-stage timestamp later than an already-recorded later-stage timestamp.
owner-resolution0.83
Plain-English question: Every open deal has a blank owner name — resolve each one to a real person using the owners table.
Prompt — what the model saw
The deal extract below has an owner name field that is blank on nearly every row and an owner id field that is populated. Using the owners table, resolve each open deal to an owner name. Report: number of deals resolved, deals whose owner id has no match in the owners table (list them), the owner ids that map to archived/deactivated owners (list their names), and the total pipeline amount per resolved owner. Do not guess a name for any unmatched id.
cost $0.3873 · 51s · in 86,562 / out 6,967 tok
✓ resolved_count✓ unmatched_none✗ deactivated_flagged✓ jake_amount✓ justin_amount✓ no_invented

✓ Correct Answer (ground truth)

Plain-English answer: All 156 deals resolve to six named owners; jake_amount maps to Bryce Harmon ($1,054,144) and justin_amount to Alex Franklin ($624,310).
The answer in one line: jake_amount = 1,054,144; justin_amount = 624,310; resolved = 156
jake_amount1,054,144
justin_amount624,310
resolved156
deactivated
per_ownerBryce Harmon=1,054,144; Alex Franklin=624,310; Dana Mercer=341,195; Cole Ingram=288,161.43; Farid Osman=4,134; Elena Sinclair=2,100
graded checksresolved_count · unmatched_none · deactivated_flagged · jake_amount · justin_amount · no_invented

Model's actual answer

show the model's full answer
Deals resolved: 156 of 156 open deals.

Unmatched owner IDs: None. Every owner_id in deals_open.csv matched owners.csv.

Owner IDs mapped to archived/deactivated owners: None. No open deal maps to an owner where archived = true.

Total pipeline amount per resolved owner:
- Bryce Harmon (owner_id 119337721): 35 deals; $1,054,144.00
- Alex Franklin (owner_id 84342457): 67 deals; $624,310.00
- Dana Mercer (owner_id 83155923): 24 deals; $341,195.00
- Cole Ingram (owner_id 83155924): 22 deals; $288,161.43
- Farid Osman (owner_id 716654662): 7 deals; $4,134.00
- Elena Sinclair (owner_id 701163055): 1 deal; $2,100.00

Arithmetic:
- Resolved deals = 35 + 67 + 24 + 22 + 7 + 1 = 156
- Total resolved pipeline = $1,054,144.00 + $624,310.00 + $341,195.00 + $288,161.43 + $4,134.00 + $2,100.00 = $2,314,044.43
gong-hubspot-join-integrityPASS 1.00
Plain-English question: How many call records point at deal ids that do not exist in the open pipeline?
Prompt — what the model saw
Check the integrity of the call-to-deal mapping below. The gong table lists calls in the last 90 days keyed to HubSpot deal ids; deals_open lists the current open default-pipeline deals. Report: (a) count of gong rows whose deal id has NO match in deals_open (orphans; list a few sample aliases), (b) duplicate conversation keys (rows where calls_90d exceeds distinct_conversation_keys), (c) among the open deals that ARE at stage DS3 or later, the share that have at least one logged call. Give sample aliases for the orphan finding, all taken from the data. Note: gong_owner_id is a Gong user id, not a HubSpot owner id.
cost $0.3933 · 52s · in 128,359 / out 5,679 tok
✓ orphan_count✓ dup_keys_0✓ ds3_coverage✓ sample_ids_present

✓ Correct Answer (ground truth)

Plain-English answer: 30 Gong call rows are orphans keyed to dead deal ids, none are duplicates, and DS3 call coverage is 29.4%.
The answer in one line: orphans = 30; ds3_cov_pct = 29.4; dup = 0
orphans30
ds3_cov_pct29.4
dup0
orphan_aliasesDeal-8FA85D, Deal-8FC3F9, Deal-3B7945, Deal-42B265, Deal-9CCC42, Deal-36EA09
graded checksorphan_count · dup_keys_0 · ds3_coverage · sample_ids_present

Model's actual answer

show the model's full answer
(a) Orphans: 30 Gong rows have no matching `deal_id` in `deals_open`.

Arithmetic: 67 Gong rows − 37 matched Gong rows = 30 orphans.

Sample orphan aliases: Deal-8FA85D, Deal-8FC3F9, Deal-3B7945, Deal-42B265, Deal-9CCC42.

(b) Duplicate conversation keys: 0 rows.

Arithmetic: 0 rows where `calls_90d > distinct_conversation_keys`.

(c) DS3+ open-deal call coverage: 25 of 85 open DS3+ deals have at least one Gong call = 29.4%.

Arithmetic: 25 ÷ 85 × 100 = 29.4118%, rounded to 29.4%.

`gong_owner_id` was not used for matching; the integrity check matched Gong `hs_deal_id` to `deals_open.deal_id`.
snowflake-sql-trapped-catalog0.67
Plain-English question: Write one Snowflake query for first-month usage per customer using only the provided, trap-laden catalog.
Prompt — what the model saw
Using ONLY the catalog provided, write one Snowflake SQL query returning, per customer company, for its first calendar month as a customer: unique givers, recognition count, successful redemption count. Read the catalog notes carefully: some tables are stale or unpopulated and must be avoided, and one documented filter (excluding deleted givers) must NOT be applied to historical giving counts. Put a comment above each FROM or JOIN explaining the table choice. Return only fenced SQL.
cost $0.0746 · 25s · in 25,260 / out 1,481 tok
✓ avoids_stale_deals✓ avoids_unpopulated_live✗ uses_cohort_summary✗ succeeded_filter✓ no_giver_deletion_filter✓ returns_sql

✓ Correct Answer (ground truth)

Plain-English answer: A single correct SQL query that uses the right catalog tables and avoids the trap columns — graded on the exact tables and columns.
The answer in one line: use_table = PRODUCTION.PLG.COMPANY_COHORT_SUMMARY
avoid_stalePRODUCTION.HUBSPOT.DEALS (stale)
avoid_unpopulatedV2_LIVE.OBJECTS_DEALS (unpopulated)
forbidden_filterdeleted-giver exclusion must NOT be applied
outputone fenced SELECT with per-FROM/JOIN table-choice comment
required_filtersucceeded redemptions only
use_tablePRODUCTION.PLG.COMPANY_COHORT_SUMMARY
graded checksavoids_stale_deals · avoids_unpopulated_live · uses_cohort_summary · succeeded_filter · no_giver_deletion_filter · returns_sql

Model's actual answer

show the model's full answer
```sql
-- Cannot produce the requested per-customer first-month metrics from the provided catalog:
-- no documented table contains recognition/giving events, giver identifiers, or a customer-company alias
-- that can be joined to redemption events. COMPANY_COHORT_SUMMARY contains monthly aggregates but
-- does not document unique giver counts or a company identifier.
SELECT
  'Insufficient catalog data to calculate unique givers, recognition count, and successful redemption count per customer company.' AS data_gap;
```
crm-completeness-enrichment0.80
Plain-English question: Audit the CRM for missing and invalid fields, and propose the fixes.
Prompt — what the model saw
Audit the CRM extract for completeness and propose fixes. Deals need owner, stage, amount, close date, why-buys; companies need industry, employee count, HQ country; contacts need email, title, persona. Report completeness percent per field. Identify duplicate company clusters (name variants, shared domain) with a survivor per cluster. List invalid emails and domain mismatches. Fill missing company fields only where the enrichment export has a matching row; where CRM and enrichment disagree list both and recommend a source. Never invent a value. End with the 10 fixes with the most pipeline amount at stake.
cost $0.2418 · 68s · in 56,232 / out 8,362 tok
✓ dup_clusters✗ invalid_emails✓ survivor_language✓ completeness_pct✓ no_invent

✓ Correct Answer (ground truth)

Plain-English answer: 9 companies missing employee count, 6 missing HQ country, 4 invalid emails, 1 domain mismatch, 2 duplicate clusters, and 25 enrichment matches.
The answer in one line: n_contacts = 52; n_companies = 34; enrichment_matches = 25; invalid_email_count = 4; n_dup_clusters = 2; domain_mismatch_count = 1 (+4 more below)
n_contacts52
domain_mismatch_count1
enrichment_matches25
invalid_email_count4
n_companies34
n_dup_clusters2
company_missingindustry=0; employee_count=9; hq_country=6
domain_mismatchesCT-0011
duplicate_clusters['C-0A092931', 'C-0A092932'], ['C-0A092933', 'C-0A092934']
invalid_emailsCT-0010, CT-0080, CT-0081, CT-0192
graded checksdup_clusters · invalid_emails · survivor_language · completeness_pct · no_invent

Model's actual answer

show the model's full answer
CRM audit

Deals
- No deals extract was provided. Completeness for owner, stage, amount, close date, and why-buys cannot be calculated.
- Pipeline amount at stake cannot be calculated.
- Accordingly, a ranked “10 fixes with the most pipeline amount at stake” cannot be produced.

Companies (34 records)

| Field | Complete | Arithmetic | Completeness |
|---|---:|---|---:|
| industry | 34 | 34 / 34 | 100.00% |
| employee_count | 25 | 25 / 34 | 73.53% |
| hq_country | 28 | 28 / 34 | 82.35% |

Contacts (52 records)

| Field | Complete | Arithmetic | Completeness |
|---|---:|---|---:|
| email (populated) | 52 | 52 / 52 | 100.00% |
| email (syntactically valid) | 48 | 48 / 52 | 92.31% |
| title | 39 | 39 / 52 | 75.00% |
| persona | 37 | 37 / 52 | 71.15% |

Duplicate company clusters

| Cluster basis | Records | Proposed survivor | Fix |
|---|---|---|---|
| Shared domain: `acme-corp.com` | `C-0A092931`, `C-0A092932` | `C-0A092931` | Merge `C-0A092932` into `C-0A092931` after reconciling employee count: 500 vs 510. |
| Shared domain: `globex.io` | `C-0A092933`, `C-0A092934` | `C-0A092933` | Merge `C-0A092934` into `C-0A092933`; reconcile industry: `SaaS` vs `Technology`. |

Invalid emails

| contact_key | company_alias | email | Issue |
|---|---|---|---|
| `CT-0010` | `C-66D1FC` | `user0@` | Missing domain after `@`. |
| `CT-0080` | `C-92D97D` | `user0@` | Missing domain after `@`. |
| `CT-0081` | `C-92D97D` | `user1@` | Missing domain after `@`. |
| `CT-0192` | `C-425E2A` | `user2@` | Missing domain after `@`. |

Domain mismatches

| contact_key | company_alias | email | Contact domain | CRM domain |
|---|---|---|---|---|
| `CT-0011` | `C-66D1FC` | `user1@other-domain.com` | `other-domain.com` | `66d1fc.com` |

Enrichment-backed fills

Only fields blank in CRM and populated in `zoominfo_enrichment.csv` are included.

| company_alias | Field to fill | Value from enrichment |
|---|---|---|
| `C-EC3025` | employee_count | 400 |
| `C-96039F` | employee_count | 400 |
| `C-44EA29` | employee_count | 400 |
| `C-D04904` | employee_count | 400 |
| `C-B23205` | employee_count | 400 |
| `C-60C75F` | employee_count | 400 |
| `C-7BBDFA` | employee_count | 400 |
| `C-50D386` | employee_count | 400 |

CRM fields with no available enrichment value must remain unfilled:
- `C-2D1F1B`: hq_country
- `C-D73B89`: hq_country
- `C-44EA29`: hq_country
- `C-D04904`: hq_country
- `C-2C60E5`: hq_country
- `C-EE9FFB`: hq_country
- `C-93C8BF`: employee_count

CRM/enrichment disagreements

Recommended source: `zoominfo_enrichment.csv` for standardized industry labels, standardized country labels, and enriched employee counts. Preserve the original CRM value in an audit field before overwrite.

| company_alias | Field | CRM | ZoomInfo |
|---|---|---|---|
| `C-66D1FC` | industry | `tech` | `Computer Software` |
| `C-66D1FC` | hq_country | `US` | `United States` |
| `C-950043` | hq_country | `US` | `United States` |
| `C-EC3025` | industry | `Technology` | `Computer Software` |
| `C-EC3025` | hq_country | `USA` | `United States` |
| `C-96039F` | hq_country | `USA` | `United States` |
| `C-44EA29` | industry | `tech` | `Computer Software` |
| `C-92D97D` | industry | `Technology` | `Computer Software` |
| `C-D04904` | industry | `Technology` | `Computer Software` |
| `C-77A95A` | industry | `Technology` | `Computer Software` |
| `C-77A95A` | hq_country | `US` | `United States` |
| `C-AA8DDA` | industry | `Technology` | `Computer Software` |
| `C-B23205` | hq_country | `US` | `United States` |
| `C-E51FB7` | hq_country | `USA` | `United States` |
| `C-D0662E` | hq_country | `US` | `United States` |
| `C-B25F40` | industry | `Technology` | `Computer Software` |
| `C-60C75F` | industry | `tech` | `Computer Software` |
| `C-425E2A` | industry | `Tech ` | `Computer Software` |
| `C-425E2A` | hq_country | `USA` | `United States` |
| `C-2D7423` | hq_country | `USA` | `United States` |

Top 10 fixes by pipeline amount at stake

Not available: no deals file or pipeline amount data was provided. A ranking would require deal aliases, amounts, and relationships to the affected company/contact records.
deal-intelligence 5 tests
closed-lost-classification0.80
Plain-English question: Why did we lose the last six months of deals — one primary category per deal, and whose side is the reason on?
Prompt — what the model saw
Classify every deal lost in the last 6 months below into one primary category: pricing, competitor, no decision, timing, product gap, champion left, or other. Also assign a side (Bonusly, buyer, unknown). Then summarize: category counts, the side split, the number of deals where the structured closed_lost_tag clearly disagrees with the free-text reason, and the two patterns most worth acting on. Base everything only on the tag and free-text provided.
cost $0.2823 · 86s · in 55,824 / out 12,544 tok
✓ total_90✗ competitor_top✓ category_counts_present✓ side_split✓ two_patterns

✓ Correct Answer (ground truth)

Plain-English answer: Every closed-lost deal gets exactly one category (pricing, competitor, no decision, timing, product gap, champion left, other) plus a side, per the computed classification.
The answer in one line: total_lost_6mo = 90; top_reason = competitor (26)
total_lost_6mo90
categoriespricing, competitor, no decision, timing, product gap, champion left, other
patternstwo most actionable, tag-vs-text disagreements counted
sideBonusly / buyer / unknown per deal
top_reasoncompetitor (26)
graded checkstotal_90 · competitor_top · category_counts_present · side_split · two_patterns

Model's actual answer

show the model's full answer
Classifications (deal_alias — primary category; side)

- Deal-DB0AAC — timing; buyer
- Deal-F7F635 — competitor; buyer
- Deal-AC944F — no decision; buyer
- Deal-214060 — no decision; buyer
- Deal-91A056 — timing; buyer
- Deal-29326C — timing; buyer
- Deal-5DB9B0 — other; unknown
- Deal-831B7B — timing; buyer
- Deal-F97C37 — competitor; buyer
- Deal-13E9CF — no decision; buyer
- Deal-39E25C — timing; buyer
- Deal-7ED004 — pricing; buyer
- Deal-21B045 — no decision; buyer
- Deal-B3ABED — timing; buyer
- Deal-422BA6 — competitor; buyer
- Deal-ED9AE7 — pricing; buyer
- Deal-988493 — no decision; buyer
- Deal-381C8C — competitor; buyer
- Deal-F308CA — no decision; buyer
- Deal-F1E8A6 — competitor; buyer
- Deal-B6AC09 — timing; buyer
- Deal-70F704 — no decision; buyer
- Deal-E6E80A — timing; buyer
- Deal-B038F0 — timing; buyer
- Deal-4664E1 — no decision; buyer
- Deal-175756 — timing; buyer
- Deal-E74A73 — no decision; buyer
- Deal-DDAB52 — competitor; buyer
- Deal-ACE061 — competitor; buyer
- Deal-BB78F3 — timing; buyer
- Deal-D48E0B — no decision; buyer
- Deal-15DA99 — timing; buyer
- Deal-F4AF5D — timing; buyer
- Deal-79B7A1 — timing; buyer
- Deal-583ADB — no decision; buyer
- Deal-8E27DA — competitor; buyer
- Deal-2D2F8D — competitor; buyer
- Deal-E0441F — no decision; unknown
- Deal-7CB44D — no decision; buyer
- Deal-0F96AA — competitor; buyer
- Deal-1BCA50 — competitor; buyer
- Deal-7CC678 — competitor; buyer
- Deal-FAC17C — no decision; buyer
- Deal-242273 — product gap; Bonusly
- Deal-50E5D8 — no decision; buyer
- Deal-A2C349 — competitor; buyer
- Deal-9F176A — timing; buyer
- Deal-7B2236 — pricing; buyer
- Deal-AFA56C — no decision; buyer
- Deal-C7156E — competitor; buyer
- Deal-C33D91 — pricing; buyer
- Deal-9048EB — product gap; Bonusly
- Deal-5E64CE — timing; buyer
- Deal-8A0992 — competitor; buyer
- Deal-D0C698 — competitor; buyer
- Deal-69CF3D — timing; buyer
- Deal-ECBF89 — timing; buyer
- Deal-3618CC — product gap; Bonusly
- Deal-EECC02 — competitor; buyer
- Deal-5AD03E — pricing; buyer
- Deal-D1A623 — timing; buyer
- Deal-413C56 — no decision; buyer
- Deal-47F1A1 — competitor; buyer
- Deal-BF2A98 — competitor; buyer
- Deal-2A292B — no decision; buyer
- Deal-D1AABF — no decision; buyer
- Deal-FEDBCB — timing; buyer
- Deal-1E7DA9 — competitor; buyer
- Deal-2BBA21 — no decision; buyer
- Deal-286F9C — competitor; buyer
- Deal-7FBAC6 — no decision; buyer
- Deal-369281 — competitor; buyer
- Deal-386F6E — no decision; buyer
- Deal-9FCD0D — competitor; buyer
- Deal-55867E — other; unknown
- Deal-DAFB82 — pricing; buyer
- Deal-2FEDDB — timing; buyer
- Deal-64B19A — competitor; buyer
- Deal-3F86A0 — no decision; buyer
- Deal-096750 — no decision; buyer
- Deal-F325A5 — champion left; buyer
- Deal-ABD14C — no decision; buyer
- Deal-79E61A — no decision; buyer
- Deal-8A119B — pricing; buyer
- Deal-AE7C4E — no decision; buyer
- Deal-DAB4F1 — no decision; buyer
- Deal-B4B50F — no decision; buyer
- Deal-981AD4 — product gap; Bonusly
- Deal-DC77FE — product gap; Bonusly
- Deal-5885B9 — no decision; buyer

Summary

Category counts:
- No decision: 30
- Competitor: 24
- Timing: 21
- Pricing: 7
- Product gap: 5
- Other: 2
- Champion left: 1

Arithmetic: 30 + 24 + 21 + 7 + 5 + 2 + 1 = 90 deals.

Side split:
- Buyer: 82
- Bonusly: 5
- Unknown: 3

Arithmetic: 82 + 5 + 3 = 90 deals.

Structured-tag vs. free-text disagreements: 8 deals
- Deal-ED9AE7 — `Lost DM` tag; text cites timing, budget, and authority.
- Deal-8E27DA — `Feature Request` tag; text says they chose a swag provider and did not want R&R currently.
- Deal-FAC17C — `Lost DM` tag; text says final executive approval was not obtained.
- Deal-242273 — `Competitor` tag; text identifies an unmet need for digitized internal currency and onsite spending.
- Deal-9048EB — `MIA` tag; text cites bad fit and multiple feature gaps.
- Deal-5E64CE — `Doing nothing/Not a priority/Cost` tag; text cites a current Nectar agreement through October 2027.
- Deal-3618CC — `Lost DM` tag; text says “Wanted Surveys.”
- Deal-5AD03E — `Competitor` tag; text cites undefined budget access rather than a competing vendor.

Two patterns most worth acting on:
1. No-decision losses are the largest group: 30 of 90 deals. The text is predominantly nonresponse, deprioritization, pauses, pending approval, or lack of readiness—not a stated competitive or product outcome.
2. Timing is the next largest non-competitive pattern: 21 of 90 deals. Multiple records explicitly cite reconnecting in 2027, next year, Q2 next year, or 2028. A structured re-engagement process for stated return dates is supported by the text.
pipeline-tieringPASS 1.00
Plain-English question: Score all 156 open deals into exactly one of LOCK / ACTION / BUILD / REVIVE / WATCH / RISKY.
Prompt — what the model saw
Score the open pipeline below on these signals: forecast category, stage, meetings_30d, contact count, and engagement recency. Assign exactly one tier per deal: LOCK, ACTION, BUILD, REVIVE, WATCH, or RISKY (RISKY = the forecast category disagrees with the engagement evidence). Never tier a deal LOCK if it has zero meetings_30d. Do NOT list every deal. Return ONLY a compact JSON object with exactly these keys: - "tier_counts": object mapping each tier to the number of deals in it (must sum to the total deal count), - "tier_examples": object mapping each tier to up to 3 example deal aliases from the data, - "risky_deals": array of the deal aliases you tiered RISKY, - "lock_violations": number of deals tiered LOCK that have zero meetings_30d (should be 0), - "pipeline_shape": one short paragraph on the overall pipeline shape. Note: inbound_emails_30d is 0 for every row due to a data defect, so treat meetings_30d as the inbound signal.
cost $0.3690 · 64s · in 113,316 / out 7,213 tok
✓ json_returned✓ tier_vocabulary✓ tier_counts_sum✓ risky_deals_listed✓ no_lock_violation_claimed

✓ Correct Answer (ground truth)

Plain-English answer: All 156 open deals tiered exactly once across the six tiers using forecast category, stage, meetings, contacts, and recency.
The answer in one line: total = 156
total156
graded checksjson_returned · tier_vocabulary · tier_counts_sum · risky_deals_listed · no_lock_violation_claimed

Model's actual answer

show the model's full answer
{"tier_counts":{"LOCK":3,"ACTION":11,"BUILD":44,"REVIVE":65,"WATCH":17,"RISKY":16},"tier_examples":{"LOCK":["Deal-D348E1","Deal-C26D20","Deal-403845"],"ACTION":["Deal-25F752","Deal-944310","Deal-3974EB"],"BUILD":["Deal-D73B89","Deal-CA7DC0","Deal-3795AD"],"REVIVE":["Deal-6787C2","Deal-A5E80A","Deal-1FC049"],"WATCH":["Deal-012CB1","Deal-036E80","Deal-BB8880"],"RISKY":["Deal-E53952","Deal-5408B0","Deal-9AAE5F"]},"risky_deals":["Deal-E53952","Deal-5408B0","Deal-9AAE5F","Deal-547B2B","Deal-B7EBD1","Deal-A2B47C","Deal-2465CE","Deal-C61CF7","Deal-62D607","Deal-584EE5","Deal-C6D97A","Deal-7B3B0F","Deal-F9A08A","Deal-0660B4","Deal-FD9F4E","Deal-BA571A"],"lock_violations":0,"pipeline_shape":"The pipeline is weighted toward REVIVE and BUILD: 65 + 44 = 109 of 156 deals; 3 + 11 = 14 are LOCK or ACTION, while 16 are RISKY. Tier counts reconcile: 3 + 11 + 44 + 65 + 17 + 16 = 156. Engagement data is missing for Deal-3EED2C and Deal-57FF13."}
call-transcript-extractionPASS 1.00
Plain-English question: Extract the CRM write-back fields from each call transcript as JSON.
Prompt — what the model saw
For each transcript, extract CRM write-back fields as JSON: why-buys (prospect statements only), pain points, stakeholders from the speaker list, budget signal (prospect-stated or null), timeline signal, competitor mentioned (only if the prospect raised it), next step (only if explicitly agreed), objections, confidence. Never fill a field from what the rep said or hoped.
cost $0.1239 · 26s · in 30,335 / out 4,713 tok
✓ json_emitted✓ budget_signal✓ null_discipline✓ stakeholders✓ competitor_prospect_only

✓ Correct Answer (ground truth)

Plain-English answer: Per transcript: prospect-only why-buys, pain points, stakeholders, budget and timeline signals, and competitors — e.g. TX-001: '$40k earmarked', live before open enrollment.
The answer in one line: rep = Alex Franklin
allowed_newTX-001, TX-002, TX-003, TX-004, TX-005, TX-006, Achievers, Bucketlist, Nectar
per_transcript{"TX-001": {"why_buys": ["automating anniversary and birthday awards"], "pain_points": ["HR team of three cannot keep up with it manually", "track everything in a spreadsheet, and people slip through
repAlex Franklin
rep_sourced_nulls{"TX-003": ["budget_signal \u2014 only the rep mentioned pricing/budget"], "TX-004": ["next_step \u2014 rep proposed, prospect said 'no promises'"], "TX-006": ["budget_signal \u2014 rep decoy, prospec
graded checksjson_emitted · budget_signal · null_discipline · stakeholders · competitor_prospect_only

Model's actual answer

show the model's full answer
{
  "Deal-CFE7F4": {
    "why-buys": [
      "The big win for us would be automating anniversary and birthday awards — our HR team of three cannot keep up with it manually.",
      "Right now we track everything in a spreadsheet, and people slip through the cracks."
    ],
    "pain_points": [
      "HR team of three cannot keep up with anniversary and birthday awards manually.",
      "Awards are tracked in a spreadsheet and people slip through the cracks."
    ],
    "stakeholders": [
      "Prospect (VP People)",
      "Prospect (HR Admin)"
    ],
    "budget_signal": "We have about $40k earmarked for engagement tools this fiscal year.",
    "timeline_signal": "Ideally we would have this live before open enrollment in November.",
    "competitor_mentioned": "Achievers",
    "next_step": "Security review with the IT lead on September 12.",
    "objections": [
      "We need SSO and audit logs for IT to sign off.",
      "Achievers was too heavy for a team our size."
    ],
    "confidence": null
  },
  "Deal-70BB30": {
    "why-buys": [
      "We want to tie recognition to retention for our hourly workforce — regretted turnover there is over 30%."
    ],
    "pain_points": [
      "Regretted turnover for the hourly workforce is over 30%."
    ],
    "stakeholders": [
      "Prospect (Head of Total Rewards)",
      "Prospect (CFO)"
    ],
    "budget_signal": "Finance has approved a $25k pilot budget for this quarter.",
    "timeline_signal": "We want a decision by end of September.",
    "competitor_mentioned": null,
    "next_step": "Send the pilot agreement; the prospect will route it to legal this week.",
    "objections": [
      "Integration with Workday has to be rock solid."
    ],
    "confidence": null
  },
  "Deal-530B50": {
    "why-buys": [
      "We need to make recognition visible across our 12 retail locations.",
      "Store managers have zero budget autonomy for on-the-spot recognition today."
    ],
    "pain_points": [
      "Recognition is not visible across 12 retail locations.",
      "Store managers have zero budget autonomy for on-the-spot recognition."
    ],
    "stakeholders": [
      "Prospect (People Ops Manager)"
    ],
    "budget_signal": null,
    "timeline_signal": "Honestly there's no rush on our side until Q1.",
    "competitor_mentioned": "Bucketlist",
    "next_step": "Schedule a call with the CEO; the prospect will send two times.",
    "objections": [
      "The CEO has to be sold first — she decides anything people-related."
    ],
    "confidence": null
  },
  "Deal-180D02": {
    "why-buys": [
      "We want to consolidate three separate recognition tools into one.",
      "We're paying for three tools and none of them talk to our HRIS."
    ],
    "pain_points": [
      "Three separate recognition tools need to be consolidated.",
      "The three tools do not integrate with the HRIS.",
      "The prior vendor's security review took three months."
    ],
    "stakeholders": [
      "Prospect (VP People)",
      "Prospect (IT Security Lead)"
    ],
    "budget_signal": "If it's under $15k annually, I can approve it without going to the board.",
    "timeline_signal": "Our procurement cycle runs six to eight weeks minimum.",
    "competitor_mentioned": null,
    "next_step": null,
    "objections": [
      "The security review took three months for our last vendor.",
      "A follow-up with the CFO was not agreed: \"Maybe — I need to check her calendar, no promises.\""
    ],
    "confidence": null
  },
  "Deal-F8767A": {
    "why-buys": [
      "Two things: automate service milestones, and give us analytics on recognition equity across departments.",
      "Our night-shift teams feel invisible — their engagement scores run 20 points lower."
    ],
    "pain_points": [
      "Service milestones need to be automated.",
      "Recognition-equity analytics are needed across departments.",
      "Night-shift teams feel invisible and have engagement scores 20 points lower.",
      "The exec team is skeptical after a failed rollout two years ago."
    ],
    "stakeholders": [
      "Prospect (HR Director)",
      "Prospect (People Ops Coordinator)"
    ],
    "budget_signal": "We have $12k approved under our engagement line.",
    "timeline_signal": "We need this running before our January all-hands.",
    "competitor_mentioned": "Nectar",
    "next_step": "Present to the exec team on October 2.",
    "objections": [
      "We're mid-pilot with Nectar right now, so you'd need to beat that experience.",
      "Our exec team is skeptical after a failed rollout two years ago."
    ],
    "confidence": null
  },
  "Deal-EE195F": {
    "why-buys": [
      "I'd love to cut the admin time on service awards.",
      "I personally spend five hours a month ordering and shipping plaques.",
      "Budget isn't the issue — time is."
    ],
    "pain_points": [
      "Five hours per month are spent ordering and shipping plaques.",
      "Service-award administration consumes time."
    ],
    "stakeholders": [
      "Prospect (HR Manager)"
    ],
    "budget_signal": "Budget isn't the issue — time is.",
    "timeline_signal": "Our fiscal year resets in February, so a Q1 start is realistic.",
    "competitor_mentioned": null,
    "next_step": "Send the one-page overview; the prospect will forward it to the COO this week.",
    "objections": [
      "The COO usually prefers building things in-house."
    ],
    "confidence": null
  }
}
next-to-close0.75
Plain-English question: Which 3 deals are closest to signature right now?
Prompt — what the model saw
Which 3 deals are closest to signature right now? Use the CRM data and the Slack thread; Slack often has the real status before the CRM does. For each: deal, amount, why it is close, what is left. Under 250 words.
cost $0.0752 · 18s · in 25,731 / out 1,441 tok
✓ exactly_three✗ top3_named✓ slack_first✓ blocked_excluded

✓ Correct Answer (ground truth)

Plain-English answer: Deal-547B2B ($11,200), Deal-B7EBD1 ($9,000), and Deal-403845 ($9,000) — all DS5 COMMIT deals closing September 10-11, with what is left on each.
blocked_excludeddeal_alias=Deal-2465CE; reason=champion left + procurement freeze (Slack #sales-sparring 2026-09-04)
exactly_three1
ranking_ruleSlack signature-imminent deal ranks first; remaining ranked by stage (DS5>DS4), forecast (COMMIT>BEST_CASE>PIPELINE), close_date asc, amount desc
top3rank=1; deal_alias=Deal-547B2B; amount=11200; stage=DS5; forecast_category=COMMIT; close_date=2026-09-11 | rank=2; deal_alias=Deal-B7EBD1; amount=9000; stage=DS5; forecast_category=COMMIT; close_date=2026-09-10 | rank=3; deal_alias=Deal-403845; amount=9000; stage=DS5; forecast_category=COMMIT; close_date=2026-09-11
graded checksexactly_three · top3_named · slack_first · blocked_excluded

Model's actual answer

show the model's full answer
1. Deal-547B2B — $11,200  
   Why close: CRM is DS5/COMMIT with a 2026-09-11 close date. Slack says redlines came back clean, the signing page is out, and the VP People said they will sign tomorrow.  
   Left: Customer signature.

2. Deal-403845 — $9,000  
   Why close: CRM is DS5/COMMIT with a 2026-09-11 close date. Slack says the order form is with the finance team.  
   Left: Finance approval/signature. Note: Slack attributes this update to Dana Mercer, while CRM lists Alex Franklin as owner.

3. Deal-A2B47C — $6,360  
   Why close: CRM is DS5/COMMIT with a 2026-09-11 close date. Slack says it is still warm and moving at a normal legal-review pace.  
   Left: Completion of legal review and signature.

Combined amount: $11,200 + $9,000 + $6,360 = $26,560.
product-gap-detectionPASS 1.00
Plain-English question: Which prospect complaints are true product gaps versus rollout or enablement issues?
Prompt — what the model saw
Surface true product gaps raised by prospects in active deals. For each candidate: quote the prospect line, classify as real gap, plan gate, or rollout/enablement issue using the product docs excerpt, and name the deal and amount. Only real gaps go in the summary. Rep language does not count as prospect voice.
cost $0.0828 · 18s · in 9,318 / out 1,555 tok
✓ real_gaps✓ plan_gate_classified✓ enablement_classified✓ gap_summary

✓ Correct Answer (ground truth)

Plain-English answer: Two real gaps (SCIM provisioning, ADP Workforce Now integration) separated from plan gates and enablement issues, each with the prospect quote and deal.
allowed_newTG-001, TG-002, TG-003, TG-004, TG-005, SCIM user provisioning, ADP Workforce Now integration, Custom report builder
enablement_issuestranscript_id=TG-004; deal_alias=Deal-84DBA6; amount=16000; feature=Slack integration recognition adoption; quote=We turned on the Slack integration in July, but half our managers still haven't given a single recognition — nobody ever trained them on it.; why_enablement=Slack integration exists on all plans; managers were never trained
excluded_rep_voicetranscript_id=TG-005; line=Full transparency — we don't have a native mobile app for hourly workers yet, though it's on the roadmap.; reason=rep voice, not prospect-raised
plan_gatestranscript_id=TG-003; deal_alias=Deal-CFE7F4; amount=32000; feature=Custom report builder; tier_required=Enterprise; quote=I tried to build a custom report combining recognition frequency with turnover and couldn't — is that possible on our current plan?
real_gapstranscript_id=TG-001; deal_alias=Deal-EC3025; amount=62000; feature=SCIM user provisioning; quote=We need SCIM user provisioning — our security team will not approve any tool that requires manual account management.; why_real=not listed in product docs at any tier | transcript_id=TG-002; deal_alias=Deal-D0D6B5; amount=23800; feature=ADP Workforce Now integration; quote=Our payroll runs on ADP Workforce Now and I don't see ADP anywhere in your integration list — that's a dealbreaker for us.; why_real=supported HRIS list is Workday/BambooHR/Gusto/Rippling only
graded checksreal_gaps · plan_gate_classified · enablement_classified · gap_summary

Model's actual answer

show the model's full answer
Candidates

- Real gap — Deal-EC3025 — amount: not provided  
  Prospect: “We need SCIM user provisioning — our security team will not approve any tool that requires manual account management.”  
  Product docs: “SCIM user provisioning … [is] NOT currently listed as supported.”  

- Real gap — Deal-D0D6B5 — amount: not provided  
  Prospect: “Our payroll runs on ADP Workforce Now and I don't see ADP anywhere in your integration list — that's a dealbreaker for us.”  
  Product docs: “ADP Workforce Now integrations are NOT currently listed as supported.”  

- Plan gate — Deal-CFE7F4 — amount: not provided  
  Prospect: “I tried to build a custom report combining recognition frequency with turnover and couldn't — is that possible on our current plan?”  
  Product docs: Custom report builder is available on Enterprise only.  

- Rollout/enablement issue — Deal-84DBA6 — amount: not provided  
  Prospect: “We turned on the Slack integration in July, but half our managers still haven't given a single recognition — nobody ever trained them on it.”  
  Product docs: Slack integration is supported on all plans; the stated issue is missing manager training, not missing functionality.  

Summary — true product gaps

- SCIM user provisioning: Deal-EC3025; amount not provided.
- ADP Workforce Now integration: Deal-D0D6B5; amount not provided.
rep-performance 5 tests
stale-pipeline-by-rep0.83
Plain-English question: Which open deals have had no email, call, or meeting in the last 7 days?
Prompt — what the model saw
The snapshot date is 2026-09-05. Using the open deals and the engagements-by-deal table, list every open deal with no logged email, call, or meeting in the last 7 days. Compute recency from the engagements table's last_email/last_call/last_meeting fields, NOT from any date field on the deal (the deal's last_contacted_field is unreliable). For each stale deal give: deal alias, owner name, stage, amount, days since last contact. Group by owner, order by amount descending within each owner. Then state, per owner, how many stale deals they carry and the total stale amount. (Do not write outreach text.)
cost $0.3817 · 74s · in 96,247 / out 13,012 tok
✓ stale_recall_ge_80✓ grouped_by_owner✓ jake_top_amount✓ kevin_stale_amt✓ jenn_stale_amt✗ stale_count

✓ Correct Answer (ground truth)

Plain-English answer: 65 open deals are stale; the largest is Deal-2D1F1B at $240,000, with Bryce Harmon carrying the most stale dollars at $626,243.
The answer in one line: jake_amt = 626,243; jenn_amt = 261,645; kevin_amt = 252,905.03; top_amount = 240,000; stale_count = 65; top_alias = Deal-2D1F1B
jake_amt626,243
jenn_amt261,645
kevin_amt252,905.03
stale_count65
top_amount240,000
top_aliasDeal-2D1F1B
graded checksstale_recall_ge_80 · grouped_by_owner · jake_top_amount · kevin_stale_amt · jenn_stale_amt · stale_count

Model's actual answer

show the model's full answer
Stale = most recent of `last_email`, `last_call`, and `last_meeting` is more than 7 days before 2026-09-05.

Bryce Harmon

| Deal alias | Stage | Amount | Days since last contact |
|---|---:|---:|---:|
| Deal-2D1F1B | DS1 | $240,000 | 81 |
| Deal-66D1FC | DS1 | $99,000 | 16 |
| Deal-950043 | DS1 | $70,000 | 19 |
| Deal-B23205 | DS1 | $45,000 | 16 |
| Deal-7BBDFA | DS3 | $37,440 | 46 |
| Deal-332637 | DS2 | $36,000 | 9 |
| Deal-1BEEBF | DS1 | $31,500 | 19 |
| Deal-C5658B | DS1 | $23,400 | 16 |
| Deal-40522D | DS3 | $21,000 | 19 |
| Deal-F0EBBB | DS3 | $11,400 | 24 |
| Deal-E25A09 | DS1 | $6,000 | 9 |
| Deal-C9C286 | DS2 | $5,502 | 9 |
| Deal-012CB1 | DS1 | $1 | 23 |

13 stale deals.  
$240,000 + $99,000 + $70,000 + $45,000 + $37,440 + $36,000 + $31,500 + $23,400 + $21,000 + $11,400 + $6,000 + $5,502 + $1 = **$626,243** stale amount.

Dana Mercer

| Deal alias | Stage | Amount | Days since last contact |
|---|---:|---:|---:|
| Deal-44EA29 | DS2 | $60,000 | 10 |
| Deal-E51FB7 | DS2 | $43,875 | 12 |
| Deal-B42F46 | DS1 | $27,000 | 19 |
| Deal-BA3DDC | DS3 | $23,400 | 15 |
| Deal-9DDE86 | DS2 | $20,000 | 15 |
| Deal-215CCA | DS3 | $18,900 | 17 |
| Deal-5EED42 | DS3 | $16,250 | 11 |
| Deal-57887A | DS2 | $15,000 | 8 |
| Deal-B7EBD1 | DS5 | $9,000 | 16 |
| Deal-3974EB | DS4 | $9,000 | 8 |
| Deal-F40F04 | DS2 | $8,100 | 15 |
| Deal-7599B8 | DS3 | $7,350 | 18 |
| Deal-87DDD1 | DS1 | $5,000 | 19 |
| Deal-F336B6 | DS3 | $4,200 | 15 |
| Deal-0660B4 | DS4 | $1,920 | 16 |

15 stale deals.  
$60,000 + $43,875 + $27,000 + $23,400 + $20,000 + $18,900 + $16,250 + $15,000 + $9,000 + $9,000 + $8,100 + $7,350 + $5,000 + $4,200 + $1,920 = **$268,995** stale amount.

Alex Franklin

| Deal alias | Stage | Amount | Days since last contact |
|---|---:|---:|---:|
| Deal-E73427 | DS3 | $18,000 | 10 |
| Deal-885F45 | DS2 | $9,300 | 12 |
| Deal-C2FF3C | DS1 | $8,316 | 10 |
| Deal-0D2F7A | DS3 | $5,100 | 12 |
| Deal-6C60D4 | DS3 | $4,800 | 12 |
| Deal-13FEBD | DS2 | $4,680 | 12 |
| Deal-9D0060 | DS3 | $3,840 | 12 |
| Deal-690476 | DS2 | $3,600 | 18 |
| Deal-C6D97A | DS4 | $3,240 | 8 |
| Deal-EE195F | DS3 | $3,120 | 8 |
| Deal-278DEC | DS3 | $2,700 | 8 |
| Deal-635B8E | DS3 | $2,600 | 18 |
| Deal-6883F3 | DS1 | $2,400 | 16 |
| Deal-4A13AD | DS3 | $2,160 | 26 |
| Deal-F67D31 | DS2 | $1,800 | 8 |
| Deal-5FDCE4 | DS3 | $1,600 | 12 |
| Deal-BA571A | DS4 | $1,080 | 18 |

17 stale deals.  
$18,000 + $9,300 + $8,316 + $5,100 + $4,800 + $4,680 + $3,840 + $3,600 + $3,240 + $3,120 + $2,700 + $2,600 + $2,400 + $2,160 + $1,800 + $1,600 + $1,080 = **$78,336** stale amount.

Cole Ingram

| Deal alias | Stage | Amount | Days since last contact |
|---|---:|---:|---:|
| Deal-D04904 | DS2 | $58,529.25 | 11 |
| Deal-B25F40 | DS3 | $40,000 | 8 |
| Deal-813836 | DS2 | $32,175 | 11 |
| Deal-1BA595 | DS2 | $31,750 | 11 |
| Deal-CFE1E8 | DS3 | $18,000 | 11 |
| Deal-CD47A6 | DS2 | $12,168 | 11 |
| Deal-627646 | DS3 | $11,193 | 11 |
| Deal-FF809F | DS2 | $7,781.20 | 11 |
| Deal-AF932D | DS2 | $7,225.40 | 11 |
| Deal-A71728 | DS2 | $6,947.50 | 11 |
| Deal-8BC9F5 | DS2 | $5,616 | 10 |
| Deal-175395 | DS3 | $4,779.88 | 11 |
| Deal-481E24 | DS3 | $4,140 | 10 |
| Deal-C7F9BF | DS2 | $3,360 | 11 |
| Deal-2F3A66 | DS3 | $3,334.80 | 11 |
| Deal-342E96 | DS2 | $2,700 | 24 |
| Deal-E568D5 | DS3 | $1,875 | 11 |
| Deal-FD9F4E | DS5 | $1,330 | 10 |

18 stale deals.  
$58,529.25 + $40,000 + $32,175 + $31,750 + $18,000 + $12,168 + $11,193 + $7,781.20 + $7,225.40 + $6,947.50 + $5,616 + $4,779.88 + $4,140 + $3,360 + $3,334.80 + $2,700 + $1,875 + $1,330 = **$252,905.03** stale amount.

Engagement data is missing for Deal-3EED2C (Alex Franklin) and Deal-57FF13 (Elena Sinclair), so their contact recency cannot be determined from `engagements_by_deal_90d.csv`.
activity-mix-vs-outcomePASS 1.00
Plain-English question: Per rep, what did the last 30 days of emails, calls, and meetings look like next to the deals that advanced?
Prompt — what the model saw
The snapshot date is 2026-09-05. For each sales rep (owner), compute the last-30-day totals of emails, calls, and meetings from the engagements table, and the number of deals that entered DS2 in the last 30 days (t_ds2 within 30 days of the snapshot). Report per rep: the activity mix as percentages (emails/calls/meetings share of that rep's total activities), total activities per DS2 entry, and rank the reps by that efficiency ratio (lowest activities per DS2 entry = most efficient). Name the most efficient rep and the highest-volume rep, and note if they differ. Do not attribute cause.
cost $0.3759 · 44s · in 80,638 / out 6,618 tok
✓ alex_ds2_30d✓ justin_volume_high✓ efficient_named✓ mix_present✓ no_causal_claim

✓ Correct Answer (ground truth)

Plain-English answer: Alex Franklin is the standout signal with 18 deals entering DS2 in 30 days (next closest: Bryce Harmon with 4), alongside per-rep activity totals.
The answer in one line: alex_ds2_30d = 18; bryce_ds2_30d = 4; note = legacy alias justin_ds2=4 actually held Bryce Harmon count; Alex Franklin entered 18 deals into DS2 in the 30d window
alex_ds2_30d18
bryce_ds2_30d4
notelegacy alias justin_ds2=4 actually held Bryce Harmon count; Alex Franklin entered 18 deals into DS2 in the 30d window
graded checksalex_ds2_30d · justin_volume_high · efficient_named · mix_present · no_causal_claim

Model's actual answer

show the model's full answer
Window: 2026-08-06 through 2026-09-05 inclusive (30 days before the 2026-09-05 snapshot).

Efficiency rank (lowest total activities per DS2 entry is most efficient):

| Rank | Owner | Emails | Calls | Meetings | Total activities | Activity mix (email / call / meeting) | DS2 entries | Activities per DS2 entry |
|---:|---|---:|---:|---:|---:|---|---:|---:|
| 1 | Alex Franklin | 307 | 36 | 41 | 384 | 79.95% / 9.38% / 10.68% | 18 | 21.33 |
| 2 | Bryce Harmon | 162 | 0 | 43 | 205 | 79.02% / 0.00% / 20.98% | 4 | 51.25 |
| 3 | Cole Ingram | 96 | 14 | 1 | 111 | 86.49% / 12.61% / 0.90% | 2 | 55.50 |
| 4 | Farid Osman | 38 | 0 | 34 | 72 | 52.78% / 0.00% / 47.22% | 1 | 72.00 |
| 5 | Dana Mercer | 84 | 18 | 11 | 113 | 74.34% / 15.93% / 9.73% | 1 | 113.00 |
| — | Elena Sinclair | 0 | 0 | 0 | 0 | N/A | 0 | N/A — no DS2 entries, so not rankable |

Arithmetic:
- Total activities = emails + calls + meetings.
- Activity mix = activity type ÷ total activities.
- Activities per DS2 entry = total activities ÷ DS2 entries.
- Example, Alex Franklin: 307 + 36 + 41 = 384; 384 ÷ 18 = 21.33.

DS2 entries in the window:
- Bryce Harmon (4): Deal-25F752, Deal-D73B89, Deal-CA7DC0, Deal-1CCE5C.
- Dana Mercer (1): Deal-57887A.
- Alex Franklin (18): Deal-403845, Deal-1FC049, Deal-3EED2C, Deal-7FA0C3, Deal-E531A6, Deal-5296C9, Deal-36C33F, Deal-EE195F, Deal-F436DA, Deal-317E6F, Deal-D1E6C2, Deal-D9A72E, Deal-CA5E44, Deal-4F775F, Deal-898FC5, Deal-46988D, Deal-E73427, Deal-92D97D.
- Cole Ingram (2): Deal-42326B, Deal-1BA595.
- Farid Osman (1): Deal-499BF6.
- Elena Sinclair (0).

Most efficient rep: Alex Franklin, at 21.33 activities per DS2 entry.

Highest-volume rep: Alex Franklin, with 384 total activities.

They do not differ.
ae-qtd-scorecardPASS 1.00
Plain-English question: Build Alex Franklin's QTD scorecard: bookings versus quota, pipeline, and conversion.
Prompt — what the model saw
Build a QTD scorecard for the named AE as of 2026-09-05: bookings vs quota with attainment percent, new vs expansion split, active pipeline by stage with amount, rolling 90-day DS2-to-won rate, win and loss counts with top loss reason, activity volume by type in the last 30 days. Exclude any closed-won deal dated before the quarter. Close with three coaching observations grounded in the numbers.
cost $0.3059 · 76s · in 80,117 / out 8,512 tok
✓ bookings✓ quota✓ attainment✓ new_expansion_split✓ top_loss_reason✓ coaching_obs

✓ Correct Answer (ground truth)

Plain-English answer: 75% attainment ($150,000 on a $200,000 quota), $113,500 new versus $36,500 expansion, pipeline by stage, and the rolling DS2-to-won rate.
The answer in one line: quota = 200000; bookings = 150000; new_bookings = 113500; expansion_bookings = 36500; open_deals_count = 125; attainment_pct = 75; owner = Alex Franklin (+12 more below)
quota200,000
attainment_pct75
bookings150,000
expansion_bookings36,500
expansion_count3
losses_qtd27
new_bookings113,500
new_count5
open_deals_count125
wins_qtd8
activity_30d_totalsemails_30d=807; calls_30d=112; meetings_30d=128; notes_30d=50
allowed_new18 items — e.g. Deal-A1C3E5, Deal-B7D2F4, Deal-C9E1A6, Deal-D4B8C2
ds2_to_wonwindow_start=2026-06-07; won_in_window=8; closed_in_window=35; rate=0.2286
ownerAlex Franklin
pipeline_by_stage{"DS1": {"count": 20, "amount": 284621}, "DS2": {"count": 28, "amount": 353760}, "DS3": {"count": 67, "amount": 552705}, "DS4": {"count": 5, "amount": 23574}, "DS5": {"count": 5, "amount": 45730}}
prior_quarter_excludeddeal_alias=Deal-B3E6F1; close_date=2026-06-20; amount=24000
quarter2026-Q3
snapshot_date2026-09-05
top_loss_reasonreason=Lost- Timing (1 year or more); count=13
graded checksbookings · quota · attainment · new_expansion_split · top_loss_reason · coaching_obs

Model's actual answer

show the model's full answer
QTD scorecard — Alex Franklin as of 2026-09-05

Bookings vs. quota
- QTD bookings: $150,000
  - Arithmetic: $40,000 + $20,000 + $35,000 + $21,000 + $12,000 + $11,000 + $6,500 + $4,500 = $150,000
  - Included wins: Deal-A1C3E5, Deal-F2C7D8, Deal-B7D2F4, Deal-C9E1A6, Deal-A8B4D6, Deal-D4B8C2, Deal-E6F3A9, Deal-C5D9E2
  - Excluded pre-quarter win: Deal-B3E6F1, $24,000, closed 2026-06-20
- Q3 quota: $200,000
- Attainment: 75.0%
  - Arithmetic: $150,000 / $200,000 × 100 = 75.0%
- Remaining to quota: $50,000
  - Arithmetic: $200,000 − $150,000 = $50,000

New vs. expansion bookings
- New: $113,500 across 5 wins (75.7% of bookings)
  - Arithmetic: $40,000 + $35,000 + $21,000 + $11,000 + $6,500 = $113,500; $113,500 / $150,000 = 75.7%
- Expansion: $36,500 across 3 wins (24.3% of bookings)
  - Arithmetic: $20,000 + $12,000 + $4,500 = $36,500; $36,500 / $150,000 = 24.3%

Active pipeline by stage
- DS1: $284,621 across 20 deals
- DS2: $353,760 across 28 deals
- DS3: $552,705 across 67 deals
- DS4: $23,574 across 5 deals
- DS5: $45,730 across 5 deals
- Total active pipeline: $1,260,390 across 125 deals
  - Arithmetic: $284,621 + $353,760 + $552,705 + $23,574 + $45,730 = $1,260,390

Rolling 90-day DS2-to-won rate
- 22.9%
  - Closed outcomes for deals entering DS2 from 2026-06-07 through 2026-09-05: 8 won and 27 lost, 35 total
  - Arithmetic: 8 / (8 + 27) × 100 = 22.9%

QTD win and loss counts
- Won: 8
- Lost: 27
- Top loss reason: Lost- Timing (1 year or more), 13 losses totaling $184,681
  - Arithmetic: 13 / 27 = 48.1% of QTD losses by count

Activity volume, last 30 days
- Emails: 807
- Calls: 112
- Meetings: 128
- Notes: 50
- Total logged activities: 1,097
  - Arithmetic: 807 + 112 + 128 + 50 = 1,097

Coaching observations
1. Alex is $50,000 from quota at 75.0% attainment; the $45,730 currently in DS5 is $4,270 short of covering the remaining gap, so progressing DS4 ($23,574) and DS3 ($552,705) is necessary.
2. Conversion is the primary performance constraint: only 8 of 35 closed 90-day DS2 cohorts became wins (22.9%), while 27 became losses.
3. Timing is the largest loss pattern: 13 of 27 QTD losses (48.1%) were coded Lost- Timing (1 year or more). This warrants tighter early-stage qualification and follow-up plans for delayed-buying prospects.
multithreading-gap0.75
Plain-English question: Which open deals are single-threaded or under-threaded?
Prompt — what the model saw
Find every open deal that is single-threaded (fewer than 2 active contacts) or under-threaded (fewer than 3, or all contacts in one persona). Active means engaged in the last 60 days and not marked former. Personas: economic buyer, champion, HR admin, IT security, finance. For each flagged deal: amount, stage, active contact count, personas present, personas missing, the most valuable persona to add given the stage, and any on-file unengaged contact at that company who fits; otherwise say none on file.
cost $0.1099 · 27s · in 11,863 / out 3,135 tok
✓ flagged_recall✓ persona_language✗ single_thread_term✓ on_file_fit

✓ Correct Answer (ground truth)

Plain-English answer: Deals with fewer than 2 active contacts (single-threaded) or fewer than 3, or all in one persona (under-threaded), each flagged with the missing persona.
The answer in one line: active_window_start = 2026-07-07
active_window_start2026-07-07
allowed_new59 items — e.g. C-077A0E, C-0D15DF, C-1BDFE0, C-2AE3AA
best_persona_ruleDS2/DS3: economic buyer > IT security > finance > HR admin > champion; DS4/DS5: economic buyer > finance > IT security > HR admin > champion; first persona not present among active contacts
flag_ruleflag if active_contacts < 2 (single-threaded) or active_contacts < 3 or all active contacts share one persona (under-threaded); active = engaged within 60 days and not former
flaggeddeal_alias=Deal-36C33F; amount=15000; stage=DS2; active_count=1; reason=single-threaded; best_persona_to_add=economic buyer | deal_alias=Deal-50D386; amount=36000; stage=DS2; active_count=2; reason=under-threaded; best_persona_to_add=economic buyer | deal_alias=Deal-5408B0; amount=14850; stage=DS4; active_count=2; reason=under-threaded; best_persona_to_add=economic buyer | deal_alias=Deal-5BFE3B; amount=18000; stage=DS2; active_count=2; reason=under-threaded; best_persona_to_add=economic buyer | deal_alias=Deal-885F45; amount=9300; stage=DS2; active_count=2; reason=under-threaded; best_persona_to_add=IT security | deal_alias=Deal-92D97D; amount=60000; stage=DS2; active_count=1; reason=single-threaded; best_persona_to_add=economic buyer … (+5 more)
healthy_not_flaggedDeal-4B0BEB, Deal-84DBA6, Deal-D348E1
persona_universeeconomic buyer, champion, HR admin, IT security, finance
graded checksflagged_recall · persona_language · single_thread_term · on_file_fit

Model's actual answer

show the model's full answer
Active-contact cutoff: 2026-07-15 (60 days before 2026-09-13). Former contacts are excluded.

Amount and stage are not provided for any deal, so they cannot be reported. Because stage is missing, the most valuable persona to add “given the stage” cannot be determined.

| Deal | Amount | Stage | Active contact count (arithmetic) | Personas present | Personas missing | Most valuable persona to add | On-file unengaged contact fitting a missing persona |
|---|---:|---|---|---|---|---|---|
| Deal-EC3025 | not provided | not provided | 1 = 1 active champion; economic buyer is former | champion | economic buyer, HR admin, IT security, finance | cannot determine; stage not provided | CT-6827DB — Chief People Officer, economic buyer |
| Deal-92D97D | not provided | not provided | 1 = 1 active HR admin; champion last engaged 2026-06-01, outside 60 days | HR admin | economic buyer, champion, IT security, finance | cannot determine; stage not provided | none on file |
| Deal-50D386 | not provided | not provided | 2 = 1 champion + 1 HR admin | champion, HR admin | economic buyer, IT security, finance | cannot determine; stage not provided | CT-A1C4B3 — Chief People Officer, economic buyer |
| Deal-D0D6B5 | not provided | not provided | 3 = 3 champions; all active contacts are one persona | champion | economic buyer, HR admin, IT security, finance | cannot determine; stage not provided | CT-1FA4DB — Chief People Officer, economic buyer |
| Deal-5BFE3B | not provided | not provided | 2 = 2 champions | champion | economic buyer, HR admin, IT security, finance | cannot determine; stage not provided | none on file |
| Deal-36C33F | not provided | not provided | 1 = 1 active IT security; champion and economic buyer are former | IT security | economic buyer, champion, HR admin, finance | cannot determine; stage not provided | CT-1DB73E — Chief People Officer, economic buyer |
| Deal-885F45 | not provided | not provided | 2 = 1 economic buyer + 1 champion | economic buyer, champion | HR admin, IT security, finance | cannot determine; stage not provided | CT-B3F25D — IT Security Lead, IT security |
| Deal-FCBE5B | not provided | not provided | 1 = 1 champion | champion | economic buyer, HR admin, IT security, finance | cannot determine; stage not provided | none on file |
| Deal-5408B0 | not provided | not provided | 2 = 1 champion + 1 HR admin | champion, HR admin | economic buyer, IT security, finance | cannot determine; stage not provided | CT-07FA76 — Chief People Officer, economic buyer |
| Deal-C6D97A | not provided | not provided | 3 = 3 champions; all active contacts are one persona | champion | economic buyer, HR admin, IT security, finance | cannot determine; stage not provided | none on file |
| Deal-F9A08A | not provided | not provided | 1 = 1 active champion; economic buyer last engaged 2026-06-20, outside 60 days | champion | economic buyer, HR admin, IT security, finance | cannot determine; stage not provided | CT-697541 — Chief People Officer, economic buyer |
talk-track-from-transcriptsPASS 1.00
Plain-English question: From this rep's last 10 calls: how do they open, handle objections, and how often do they lock a next step?
Prompt — what the model saw
From this rep's last 10 calls: what they lead with in the first five minutes, how they handle the three most common objections, how often a concrete next step is agreed (rate), and every competitor a prospect raised. Quote at most one line per finding and only lines that appear in the transcripts. End with two coaching notes.
cost $0.1158 · 29s · in 12,489 / out 3,313 tok
✓ objection_count✓ next_step_rate✓ competitors✓ coaching✓ quote_used

✓ Correct Answer (ground truth)

Plain-English answer: 8 of 10 calls open with the same customer-win story; objection handling, next-step agreement rate, and every competitor raised, with quotes.
The answer in one line: n_transcripts = 10; objection_count = 3; rep = Alex Franklin (+3 more below)
n_transcripts10
objection_count3
allowed_new13 items — e.g. TT-001, TT-002, TT-003, TT-004
competitor_quotesAwardco=We're also in late talks with Awardco — their rewards catalog looks bigger than yours.; Kudos=How are you different from Kudos? Our CEO used them at her last company.
competitors_prospect_raisedAwardco, Kudos
next_stepagreed=7; total=10; rate=0.7
objectionsobjection=budget; count=4; quote=Honestly, budget is locked until next fiscal year — I can't add a new line item right now.; transcript_id=TT-001 | objection=timing; count=3; quote=This is good, but can we revisit it next quarter? Open enrollment starts in October and we're underwater.; transcript_id=TT-002 | objection=in-house; count=3; quote=We already do recognition with a spreadsheet and quarterly gift cards — why would we change?; transcript_id=TT-004
opener_themetheme=opens with a customer recognition win story (400-person retailer, 18% turnover reduction); count=8; total=10; quote=Quick one to kick off: a 400-person retailer we work with cut regretted turnover 18% in two quarters after automating milestone awards, and I wanted to walk you through exactly how they did it.; transcript_id=TT-001
repAlex Franklin
rep_raised_competitors_excludedWorkhuman
graded checksobjection_count · next_step_rate · competitors · coaching · quote_used

Model's actual answer

show the model's full answer
- First-five-minute lead: In 8 of 10 calls, Alex opens with the same quantified retailer proof point about automated milestone awards and regretted turnover. The other two opens are an agenda (Deal-403845) and pricing (Deal-1E2498).
  - “Quick one to kick off: a 400-person retailer we work with cut regretted turnover 18% in two quarters after automating milestone awards, and I wanted to walk you through exactly how they did it.”

- Most common objection — locked budget: 4 occurrences (Deal-D348E1, Deal-547B2B, Deal-60C2C2, Deal-84DBA6). He responds with turnover-savings ROI and a $210k avoided-backfill example.
  - “Totally fair. Most teams fund this out of turnover savings — that retailer saved about $210k in avoided backfills, which is how their finance team signed off.”

- Most common objection — revisit next quarter / competing priorities: 3 occurrences (Deal-5408B0, Deal-C61CF7, Deal-D9A12F). He proposes a limited 90-day departmental pilot to produce planning data before next quarter.
  - “Makes sense. What if we scope a 90-day pilot with one department so you have internal data before next quarter's planning?”

- Most common objection — existing spreadsheet and gift-card process: 3 occurrences (Deal-403845, Deal-EDC141, Deal-1E2498). He contrasts manual recognition with automated milestones and recognition analytics.
  - “Spreadsheets work until they scale — the difference is automation: milestones fire without HR lifting a finger, and you get analytics on who is being recognized.”

- Concrete next step agreed: 7 of 10 calls = 70%.
  - Arithmetic: 7 agreed next steps ÷ 10 calls × 100 = 70%.
  - “Yes, Thursday at 2pm works — send the invite and I'll bring our HRIS manager.”

- Competitors raised by prospects:
  - Awardco (Deal-547B2B): “We're also in late talks with Awardco — their rewards catalog looks bigger than yours.”
  - Kudos (Deal-EDC141): “How are you different from Kudos? Our CEO used them at her last company.”

Coaching notes:
1. Keep the quantified retailer proof point, but vary the opening by prospect context; it appears in 8 of 10 calls and risks sounding scripted.
2. The pilot, ROI, and automation responses are consistent; add a concrete fallback next step when the prospect defers to a committee or lacks urgency, since the 3 calls without an agreed next step ended without one.
reporting-analytics 5 tests
q3-weighted-forecast0.90
Plain-English question: Build the Q3 2026 weighted forecast from the open pipeline, and show the math deal by deal.
Prompt — what the model saw
Below are the open deals in the default sales pipeline with a close date between 2026-07-01 and 2026-10-15, pulled from the CRM warehouse on 2026-09-05. Stages: DS1 (discovery) through DS5 (contract). Build the Q3 2026 forecast (quarter = 2026-07-01 to 2026-09-30). Weighting rule: 100 percent of COMMIT plus 35 percent of BEST_CASE. PIPELINE deals count zero. Only deals with a close date inside the quarter count. Report: COMMIT total, BEST_CASE total, weighted forecast, count of deals in each category inside the quarter, the deals you excluded for being outside the quarter (count and total amount), and the top 5 BEST_CASE deals by amount inside the quarter. Show arithmetic. Then, in a final '## Data quality' section of no more than four sentences, name the data quality problems in this extract that would make the forecast unreliable if it were run unattended.
cost $0.2188 · 64s · in 26,283 / out 8,570 tok
✓ commit_total_44729✓ best_case_total_203565✓ weighted_115976.75✓ commit_count_7✓ best_case_count_24✓ excluded_count_32✗ excluded_amount_227575✓ top5_aliases✓ flags_blank_owner✓ flags_missing_why_buys

✓ Correct Answer (ground truth)

Plain-English answer: A stage-weighted Q3 forecast number computed from the open pipeline, with per-stage math that reconciles to the deal data.
The answer in one line: excluded_amount = 227575; best_case_total = 203565; weighted_forecast = 115,976.75; commit_total = 44729; excluded_out_of_quarter = 32; best_case_count = 24; flags = blank owner column + empty why_buys fields must be surfaced (+2 more below)
excluded_amount227,575
best_case_count24
best_case_total203,565
commit_count7
commit_total44,729
excluded_out_of_quarter32
weighted_forecast115,976.75
flagsblank owner column + empty why_buys fields must be surfaced
top5_best_caseDeal-2D7423, Deal-25F752, Deal-E53952, Deal-5EED42, Deal-FA32A0
graded checkscommit_total_44729 · best_case_total_203565 · weighted_115976.75 · commit_count_7 · best_case_count_24 · excluded_count_32 · excluded_amount_227575 · top5_aliases · flags_blank_owner · flags_missing_why_buys

Model's actual answer

show the model's full answer
## Q3 2026 forecast

- COMMIT: 7 deals; $44,729
  - Arithmetic: $11,200 + $9,000 + $9,000 + $6,360 + $5,400 + $2,520 + $1,249 = $44,729
- BEST_CASE: 24 deals; $203,565
  - Weighted BEST_CASE: $203,565 × 35% = $71,247.75
- Weighted forecast: $44,729 + $71,247.75 = $115,976.75
- PIPELINE: excluded from weighted forecast per rule.

Excluded for close dates outside Q3: 31 deals totaling $221,875:
Deal-E51FB7 ($43,875), Deal-B936FE ($18,000), Deal-D9A12F ($17,000), Deal-D348E1 ($13,770), Deal-4062CF ($10,800), Deal-293AF3 ($9,000), Deal-034D49 ($9,000), Deal-E0ADD8 ($7,920), Deal-9F2E43 ($7,690), Deal-FCBE5B ($7,500), Deal-712010 ($7,200), Deal-600CD9 ($5,400), Deal-A92065 ($5,400), Deal-1D532E ($5,400), Deal-48B656 ($5,160), Deal-E531A6 ($4,800), Deal-D1E6C2 ($4,400), Deal-D9E112 ($4,300), Deal-5AD94B ($4,000), Deal-901332 ($3,600), Deal-47AE31 ($3,600), Deal-15D24F ($3,600), Deal-766C74 ($3,300), Deal-ED725A ($2,400), Deal-8AD4A5 ($1,800), Deal-D7E999 ($1,800), Deal-ED13B0 ($1,680), Deal-5FDCE4 ($1,600), Deal-7FA0C3 ($1,400), Deal-F5A622 ($1,080).

Top 5 BEST_CASE deals inside Q3:
1. Deal-2D7423 — $38,935
2. Deal-25F752 — $24,000
3. Deal-E53952 — $19,656
4. Deal-5EED42 — $16,250
5. Deal-FA32A0 — $11,116

## Data quality

The `owner` field is blank for nearly all deals, preventing reliable ownership-based forecast review. Many deals, including all COMMIT deals in Q3, have `why_buys_chars = 0`, so deal rationale cannot be validated from this extract. The extract includes close dates after 2026-09-30, requiring an unattended forecast to apply the Q3 date filter correctly. No company/account field is provided, so duplicate or related opportunities cannot be identified.
aha-moment-2x2PASS 1.00
Plain-English question: Do companies that hit 5+ givers and one redemption in month one actually retain better at 24 months?
Prompt — what the model saw
Test the activation hypothesis on the company cohort below: companies with 5+ unique givers (m1_users >= 5) AND 1+ successful redemption (m1_redemptions >= 1) in their first calendar month retain better at 24 months than those with one signal or neither. Every company in this extract is already 25+ months old, so current_status = 'active' means retained at 24 months. Report the full 2x2 (cohort size and 24-month retention rate for: both signals, givers-only, redemption-only, neither), state how many companies were excluded from the denominator and why (if none, say so), name the single signal with the largest retention lift, and state what this does and does not prove.
cost $0.2326 · 58s · in 39,132 / out 5,722 tok
✓ both_66✓ givers_47✓ redemp_31✓ neither_40✓ excluded_0✓ largest_lift_givers

✓ Correct Answer (ground truth)

Plain-English answer: The four cohort cells are graded against computed 24-month retention; the numbers come from the scorer's cohort table, not opinion.
The answer in one line: both_5plus_givers_and_redemption = 66.0% (31 of 47)
both_5plus_givers_and_redemption66.0% (31 of 47)
exclusionsnone — claim bounded as correlation, not causation
givers_only46.9% (23 of 49)
largest_single_signal_liftunique givers
neither40.0% (38 of 95)
redemption_only31.0% (9 of 29)
graded checksboth_66 · givers_47 · redemp_31 · neither_40 · excluded_0 · largest_lift_givers

Model's actual answer

show the model's full answer
Activation hypothesis supported in this cohort.

| First-month cohort | Cohort size | Active at 24 months | 24-month retention |
|---|---:|---:|---:|
| Both signals: m1_users ≥ 5 and m1_redemptions ≥ 1 | 46 | 31 | 31 / 46 = 67.4% |
| Givers-only: m1_users ≥ 5 and m1_redemptions = 0 | 50 | 23 | 23 / 50 = 46.0% |
| Redemption-only: m1_users < 5 and m1_redemptions ≥ 1 | 28 | 8 | 8 / 28 = 28.6% |
| Neither: m1_users < 5 and m1_redemptions = 0 | 95 | 39 | 39 / 95 = 41.1% |

Both-signals companies retained at 67.4%, versus 40.5% for all other companies combined: (23 + 8 + 39) / (50 + 28 + 95) = 70 / 173 = 40.5%. Lift: 67.4% − 40.5% = 26.9 percentage points.

Excluded from denominator: 0 companies. All 219 companies have a current_status and first-month m1_users and m1_redemptions values, and every company fits exactly one of the four cohorts.

The single signal with the largest retention lift is 5+ unique givers:
- Givers present: (31 + 23) / (46 + 50) = 54 / 96 = 56.3%
- Givers absent: (8 + 39) / (28 + 95) = 47 / 123 = 38.2%
- Lift: 56.3% − 38.2% = 18.0 percentage points

For comparison, successful redemption has a 9.9 percentage-point lift:
- Redemption present: 39 / 74 = 52.7%
- Redemption absent: 62 / 145 = 42.8%
- Lift: 9.9 percentage points

This shows a strong association in this 2023 cohort: companies achieving both first-month signals have higher observed 24-month retention. It does not prove that either behavior causes retention, or that the pattern will generalize beyond this extract; unmeasured differences between companies may explain some or all of the observed retention gap.
arr-rollforward-reconciliationPASS 1.00
Plain-English question: Does CRM ARR match billing ARR — and if not, exactly where is the variance?
Prompt — what the model saw
Reconcile ARR between CRM company records and billing subscriptions as of 2026-09-05. Billing ARR is MRR x 12. Report both totals, the variance, and a decomposition into buckets (status mismatch, rounding, missing records, other) that sums exactly to the variance. List each mismatched account with a suggested owner. Business rule: any subscription with a term other than 12 months must have cf_agreement_end_date populated; list violations.
cost $0.2346 · 54s · in 45,533 / out 10,517 tok
✓ billing_total✓ crm_total✓ variance✓ buckets_sum✓ violations_listed

✓ Correct Answer (ground truth)

Plain-English answer: Billing $604,739.28 vs CRM $603,581.76: a $1,157.52 variance decomposed into status-mismatch, rounding, and missing-record buckets.
The answer in one line: n_companies = 40; n_mismatched_accounts = 7; as_of = 2026-09-05 (+4 more below)
n_companies40
n_mismatched_accounts7
as_of2026-09-05
billing_arr_total604739.28
bucket_sum_equals_variance1
buckets{"status_mismatch": {"amount": "-13158.48", "accounts": [{"company_alias": "C-0C8323BF", "billing_arr": "0.00", "hubspot_arr": "4905.24", "diff": "-4905.24", "suggested_owner": "Dana Mercer"}, {"compa
crm_arr_total603581.76
ruleterm_months != 12 requires cf_agreement_end_date
variance1157.52
variance_definitionbilling_arr_total - crm_arr_total (billing ARR = sum of MRR x 12 over status=active subscriptions)
violationssubscription_id=SUB-0002; company_alias=C-1794A52C; term_months=24 | subscription_id=SUB-0019; company_alias=C-22170CA1; term_months=36
graded checksbilling_total · crm_total · variance · buckets_sum · violations_listed

Model's actual answer

show the model's full answer
ARR reconciliation as of 2026-09-05

- CRM company ARR total: $603,581.76
- Active billing ARR total: $604,739.28
  - Arithmetic: Σ(active subscription MRR × 12)
- Variance (CRM − billing): $603,581.76 − $604,739.28 = −$1,157.52

Variance decomposition (CRM − billing)

| Bucket | Variance | Arithmetic |
|---|---:|---|
| Status mismatch | $13,158.48 | $4,905.24 + $8,253.24 |
| Rounding | $36.00 | $16.00 + $20.00 |
| Missing records | −$11,952.00 | $16,497.24 − $28,449.24 |
| Other | −$2,400.00 | $24,396.00 − $26,796.00 |
| Total | −$1,157.52 | $13,158.48 + $36.00 − $11,952.00 − $2,400.00 |

Mismatched accounts and suggested owner

| Company alias | Issue | CRM ARR | Billing ARR | CRM − billing | Suggested owner |
|---|---|---:|---:|---:|---|
| C-0C8323BF | Status mismatch: CRM ARR present; subscription is cancelled | $4,905.24 | $0.00 | $4,905.24 | CRM Operations |
| C-0DC4FB8C | Status mismatch: CRM ARR present; subscription is cancelled | $8,253.24 | $0.00 | $8,253.24 | CRM Operations |
| C-21629AA4 | Missing CRM company record; active billing subscription | $0.00 | $28,449.24 | −$28,449.24 | CRM Operations |
| C-0D5BBE3A | Missing billing subscription; CRM ARR present | $16,497.24 | $0.00 | $16,497.24 | Billing Operations |
| C-0D66DF9E | Rounding difference | $23,200.00 | $23,184.00 | $16.00 | CRM Operations |
| C-14D70CE0 | Rounding difference | $18,200.00 | $18,180.00 | $20.00 | CRM Operations |
| C-0F7269D7 | Other: CRM ARR differs from billing ARR by $2,400.00 | $24,396.00 | $26,796.00 | −$2,400.00 | Revenue Operations |

Agreement-end-date violations

| Subscription ID | Company alias | Term months | cf_agreement_end_date |
|---|---|---:|---|
| SUB-0002 | C-1794A52C | 24 | blank |
| SUB-0019 | C-22170CA1 | 36 | blank |
kvm-month-over-monthPASS 1.00
Plain-English question: How did the four core KVMs move in August versus July?
Prompt — what the model saw
Report the four core KVMs for 2026-08 against 2026-07: giving rate, redemptions per user, 1:1 meetings engagement, pulse check engagement. For each: value, prior value, absolute and relative change, direction. Name the KVM with the largest relative move and the segment (plan_tier or size_band) driving it if the data supports that; otherwise say the data does not. Under 200 words plus one table.
cost $0.1874 · 46s · in 24,731 / out 6,074 tok
✓ four_kvms✓ biggest_mover_named✓ direction_correct✓ segment_named✓ word_cap

✓ Correct Answer (ground truth)

Plain-English answer: Giving rate 60.27% (up 0.07%), redemptions per user 1.7302 (up 0.01%), with 1:1 meetings and pulse engagement each up fractionally — direction reported for all four.
The answer in one line: n_company_rows_per_month = 30; aggregation = simple mean of company-level values per month
n_company_rows_per_month30
aggregationsimple mean of company-level values per month
biggest_moverpulse_engagement
driving_segmentsize_band=enterprise; 2026-07=0.55; 2026-08=0.2743; rel_change_pct=-50.13
kvms{"giving_rate": {"2026-07": 0.6023, "2026-08": 0.6027, "abs_change": 0.0004, "rel_change_pct": 0.07, "direction": "up"}, "redemptions_per_user": {"2026-07": 1.73, "2026-08": 1.7302, "abs_change": 0.00
segment_detail{"smb": {"2026-07": 0.6588, "2026-08": 0.6573, "rel_change_pct": -0.23}, "mid_market": {"2026-07": 0.593, "2026-08": 0.5942, "rel_change_pct": 0.2}, "enterprise": {"2026-07": 0.55, "2026-08": 0.2743,
graded checksfour_kvms · biggest_mover_named · direction_correct · segment_named · word_cap

Model's actual answer

show the model's full answer
| KVM | 2026-08 value | 2026-07 value | Absolute change | Relative change | Direction |
|---|---:|---:|---:|---:|---|
| Giving rate | 0.602713 | 0.602297 | +0.000417 | +0.07% | Up |
| Redemptions per user | 1.730163 | 1.729983 | +0.000180 | +0.01% | Up |
| 1:1 meetings engagement | 0.447177 | 0.446887 | +0.000290 | +0.06% | Up |
| Pulse check engagement | 0.508610 | 0.600587 | -0.091977 | -15.31% | Down |

Pulse check engagement had the largest relative move: -15.31%.

Arithmetic: absolute change = 2026-08 average − 2026-07 average; relative change = absolute change ÷ 2026-07 average.

The data supports size_band as the driver: enterprise pulse engagement fell from 0.549980 to 0.274280, a -0.275700 (-50.13%) change. By comparison, smb declined -0.22% and mid_market increased +0.21%. All records are tier_three, so plan_tier does not distinguish the movement.
rewards-ytd-section0.50
Plain-English question: Produce the redemption section of the weekly rewards report through August.
Prompt — what the model saw
Produce the redemption section of the weekly rewards report through the last completed month (2026-08): redemption count, spend, unique redeemers, redemptions per redeemer, provider mix as percent of spend, top 5 countries by redemptions. Say which month is the last completed month. Provider shares must sum to 100.
cost $0.3368 · 55s · in 74,633 / out 5,143 tok
✗ count✗ spend✗ unique_redeemers✓ month_named✓ provider_mix✓ top_country

✓ Correct Answer (ground truth)

Plain-English answer: 378 redemptions, $27,846 spend, 235 unique redeemers at 1.61 each, custom rewards at 39% of spend, US leading all countries.
The answer in one line: redemption_count = 378; unique_redeemers = 235; redemptions_per_redeemer = 1.61; total_spend_usd = 27846.00
redemption_count378
redemptions_per_redeemer1.61
unique_redeemers235
provider_mix_pct_of_spendTangoCard=11.6; Tremendous=30.54; custom=39.05; Snappy=18.81
top5_countries_by_countcountry=US; count=244 | country=CA; count=24 | country=AU; count=21 | country=GB; count=17 | country=NL; count=17
total_spend_usd27846.00
graded checkscount · spend · unique_redeemers · month_named · provider_mix · top_country

Model's actual answer

show the model's full answer
Last completed month: 2026-08

- Redemption count: 1,188
- Spend: $90,463.00
- Unique redeemers: 335
- Redemptions per redeemer: 1,188 ÷ 335 = 3.55

Provider mix (% of spend):
- custom: $36,163.00 ÷ $90,463.00 = 39.98%
- Tremendous: $26,270.00 ÷ $90,463.00 = 29.04%
- Snappy: $16,055.00 ÷ $90,463.00 = 17.75%
- TangoCard: $11,975.00 ÷ $90,463.00 = 13.23%
- Total: 39.98% + 29.04% + 17.75% + 13.23% = 100.00%

Top 5 countries by redemptions:
1. US: 754
2. CA: 85
3. AU: 58
4. NL: 53
5. GB: 51
customer-success 5 tests
churn-save-eligibilityPASS 1.00
Plain-English question: Which at-risk accounts actually qualify for a churn-save offer, and which play fits each?
Prompt — what the model saw
Which at-risk accounts qualify for a churn-save offer under the documented eligibility rules, what amount is at stake per account and in total, and which play fits each (usage revival, executive touch, commercial concession)? Cite the signal that justifies each play. List accounts that look at risk but do not qualify and why.
cost $0.1806 · 42s · in 39,380 / out 6,763 tok
✓ eligible_set✓ total_at_stake✓ plays_cited✓ noneligible_named✓ rules_applied

✓ Correct Answer (ground truth)

Plain-English answer: Only accounts meeting all three rules qualify — e.g. C-0F6C0F34 at $49,707 (executive touch) and C-0B827671 at $25,365 (usage revival) — with amount and play per account.
The answer in one line: n_accounts = 30; snapshot_date = 2026-09-05
n_accounts30
eligibleaccount_alias=C-0F6C0F34; amount_at_stake=49707.00; play=executive touch; justifying_signal=champion_active is false - no executive sponsor engaged | account_alias=C-0B827671; amount_at_stake=25365.00; play=usage revival; justifying_signal=usage_trend_3m=declining over the last 3 months | account_alias=C-0B360C78; amount_at_stake=35748.00; play=commercial concession; justifying_signal=usage stable/growing with seat utilization 75% - risk is commercial, not adoption | account_alias=C-0B0F1BAB; amount_at_stake=5494.00; play=executive touch; justifying_signal=champion_active is false - no executive sponsor engaged | account_alias=C-0CA21961; amount_at_stake=16829.00; play=usage revival; justifying_signal=seat utilization 26% is below 50% | account_alias=C-0E9C27D1; amount_at_stake=41235.00; play=commercial concession; justifying_signal=usage stable/growing with seat utilization 85% - risk is commercial, not adoption … (+2 more)
non_eligible_at_riskaccount_alias=C-0BC71BDD; health_score=55 | account_alias=C-0BA71F12; health_score=52 | account_alias=C-0F6694C3; health_score=43 | account_alias=C-0BE96399; health_score=54 | account_alias=C-0F876796; health_score=47 | account_alias=C-0FCCD2DF; health_score=43 … (+1 more)
ruleshealth_score < 60, churn_save_eligible_amount > 0, renewal within 120 days of snapshot
snapshot_date2026-09-05
total_amount_at_stake224601.00
graded checkseligible_set · total_at_stake · plays_cited · noneligible_named · rules_applied

Model's actual answer

show the model's full answer
Eligible churn-save accounts (all meet: health score <60, eligible amount >$0, and renewal by 2027-01-03—120 days after 2026-09-05):

| Account | Amount at stake | Best-fit play | Supporting signal |
|---|---:|---|---|
| C-0F6C0F34 | $49,707.00 | Executive touch | Champion inactive (`champion_active=false`); health score 51; renews in 28 days. |
| C-0B827671 | $25,365.00 | Usage revival | Usage is declining; only 113/202 seats used = 55.9%; health score 56. |
| C-0B360C78 | $35,748.00 | Commercial concession | Health score 57 and renewal is in 53 days. Usage is growing and 246/327 seats are used = 75.2%, so the provided data does not support a usage-revival or executive-touch trigger. |
| C-0B0F1BAB | $5,494.00 | Executive touch | Champion inactive (`champion_active=false`); health score 38; renews in 18 days. |
| C-0CA21961 | $16,829.00 | Usage revival | Flat usage and only 84/325 seats used = 25.8%; health score 58. |
| C-0E9C27D1 | $41,235.00 | Commercial concession | Health score 39 and renewal is in 19 days. Usage is flat but adoption is high at 134/157 seats = 85.4%; champion is active. |
| C-0CEF69FD | $32,621.00 | Executive touch | Champion inactive (`champion_active=false`); health score 53; renews in 77 days. |
| C-0D3278C7 | $17,602.00 | Usage revival | Usage is declining and only 126/380 seats used = 33.2%; health score 54. |

Total eligible amount at stake:

$49,707.00 + $25,365.00 + $35,748.00 + $5,494.00 + $16,829.00 + $41,235.00 + $32,621.00 + $17,602.00 = **$224,601.00**

At-risk accounts that do not qualify:

| Account | Why it looks at risk | Why it does not qualify |
|---|---|---|
| C-0BC71BDD | Health score 55; flat usage; 59/197 seats used = 29.9%; champion inactive. | `churn_save_eligible_amount` is $0.00, failing R2. |
| C-0BA71F12 | Health score 52; declining usage; 23/98 seats used = 23.5%. | Renewal is 218 days after the snapshot (2027-04-11), failing R3’s 120-day window. |
| C-0F6694C3 | Health score 43; declining usage; 39/96 seats used = 40.6%. | Eligible amount is $0.00 and renewal is 197 days after the snapshot (2027-03-21), failing R2 and R3. |
| C-0BE96399 | Health score 54; declining usage; 43/154 seats used = 27.9%. | `churn_save_eligible_amount` is $0.00, failing R2. |
| C-0F876796 | Health score 47; declining usage; 22/95 seats used = 23.2%; champion inactive. | Renewal is 154 days after the snapshot (2027-02-06), failing R3’s 120-day window. |
| C-0FCCD2DF | Health score 43; flat usage; 27/63 seats used = 42.9%; champion inactive. | Eligible amount is $0.00 and renewal is 230 days after the snapshot (2027-04-23), failing R2 and R3. |
| C-10A56B0F | Health score 54; declining usage; 85/176 seats used = 48.3%; champion inactive. | `churn_save_eligible_amount` is $0.00, failing R2. |
expansion-kitPASS 1.00
Plain-English question: Build the expansion kit for the customer who just replied to our outreach.
Prompt — what the model saw
A customer replied to outreach (reply included). Build the expansion kit: seat coverage (licensed over headcount), two lines on usage health, headroom in seats and ARR at the current per-seat rate, who replied and whether they can buy, the right buyer from our contacts, and a reply email under 150 words that moves toward the right person without being pushy and cites one real usage fact.
cost $0.1527 · 35s · in 41,710 / out 3,579 tok
✓ coverage_pct✓ headroom_arr✓ right_buyer✓ replier_not_buyer✓ usage_fact✓ email_under_150

✓ Correct Answer (ground truth)

Plain-English answer: 37.5% seat coverage, 250 headroom seats worth $15,000 ARR at $60 a seat, usage up 43.2% in six months — and the replier cannot buy; Dana R. (VP People) is the right buyer.
The answer in one line: headroom_seats = 250; coverage_pct = 37.5; company_alias = C-0DDFC9A7 (+3 more below)
headroom_seats250
coverage_pct37.5
company_aliasC-0DDFC9A7
headroom_arr15000.00
per_seat_annual_rate60.00
replierMaria S.
replier_can_buy0
right_buyername=Dana R.; title=VP People
usage_factsactive_users_2026_08=126; active_users_2026_03=88; growth_pct_6m=43.2; licensed_seat_utilization_pct=84
usage_health_linesMonthly active users grew from 88 (2026-03) to 126 (2026-08), +43.2% over 6 months., Last month 126 of 150 licensed seats were active (84.0% utilization), approaching the seat cap.
graded checkscoverage_pct · headroom_arr · right_buyer · replier_not_buyer · usage_fact · email_under_150

Model's actual answer

show the model's full answer
Seat coverage: C-0DDFC9A7 has 150 licensed seats for 400 employees: 150 ÷ 400 = 37.5%.

Usage health:
- Monthly active users increased from 88 in 2026-03 to 126 in 2026-08: 126 − 88 = 38 users, or 38 ÷ 88 = 43.2% growth.
- August usage was 126 of 150 licensed seats: 126 ÷ 150 = 84.0% utilization, leaving 24 currently unused licensed seats.

Headroom:
- Seat headroom to company headcount: 400 − 150 = 250 seats.
- Current per-seat ARR: $9,000.00 ÷ 150 = $60.00 per seat.
- ARR headroom at the current rate: 250 × $60.00 = $15,000.00.

Reply and buying authority:
- Maria S., People Operations Coordinator, replied on 2026-09-02.
- Maria S. explicitly said she is not the purchasing decision-maker.
- Dana R., VP People, is the stated owner of budget and seat expansion and is the right buyer.

Reply email:

Subject: Re: Growing your team’s recognition program

Hi Maria,

Thanks for the update — great to hear the team is seeing value. We’ve also seen monthly active users grow from 88 in March to 126 in August, an increase of 38 users.

Since Dana is looking at usage numbers and owns budget and seat expansion, would you be open to introducing us? I’d be glad to share a concise view of adoption and discuss whether the current 150-seat plan remains the right fit as usage grows.

No pressure — happy to send the usage summary for you to forward if that is easier.

Best,  
Cole
onboarding-status0.75
Plain-English question: What is done and what is missing in this customer's onboarding before the mid-onboarding call?
Prompt — what the model saw
Prep the CSM for the mid-onboarding call: what is complete (integrations connected, allowance set, admins added, first recognition given, first redemption), what is not, early engagement signals, and the three things to cover on the call. Mark nothing complete without a data field that shows it.
cost $0.1108 · 23s · in 33,156 / out 2,425 tok
✓ complete_items✓ incomplete_items✓ three_items✗ grounded

✓ Correct Answer (ground truth)

Plain-English answer: 25 days live: Slack connected, allowance set, admins added — but the HRIS integration is not connected, with early engagement signals and three call priorities.
The answer in one line: days_live = 25; company_alias = C-0D284E42
days_live25
call_itemsConnect the HRIS integration (integration_hris is empty) to automate user provisioning and offboarding., Get to first redemption (first_redemption_at is empty): walk admins through the rewards catalog and confirm allowance funding., Build the giving habit: daily active givers averaged 4.3 in week 1 vs 13.0 last week - agree on manager nudges and a recognition cadence.
checklist{"slack_integration_connected": {"complete": true, "field": "integration_slack", "value": "2026-08-12"}, "hris_integration_connected": {"complete": false, "field": "integration_hris", "value": ""}, "a
company_aliasC-0D284E42
engagement_signalsavg_active_givers_week1=4.3; avg_active_givers_last_week=13; latest_active_givers=15; days_with_activity=25
graded checkscomplete_items · incomplete_items · three_items · grounded

Model's actual answer

show the model's full answer
C-0D284E42

Complete
- Slack integration connected: Yes — `integration_slack = 2026-08-12`.
- Allowance set: Yes — `allowance_set = 2026-08-13`.
- Admins added: Yes — `admins_added = 2`.
- First recognition given: Yes — `first_recognition_at = 2026-08-15 14:22`.

Not complete / not evidenced
- HRIS integration connected: Not evidenced — `integration_hris` is blank.
- First redemption: Not evidenced — `first_redemption_at` is blank.

Early engagement signals
- Active givers increased from 3 on 2026-08-11 to 15 on 2026-09-04: `15 - 3 = 12` net increase.
- Daily active givers averaged 8.56 across 25 reported days: `214 total active-giver days / 25 days = 8.56`.
- First 7 days averaged 4.29 active givers: `30 / 7 = 4.29`.
- Most recent 7 days averaged 13.00 active givers: `91 / 7 = 13.00`.
- Recent-vs-first-week increase: `13.00 - 4.29 = 8.71` average active givers per day.

Three things to cover on the call
1. Confirm whether the HRIS integration should be connected and, if so, establish the owner and next step; no HRIS connection date is recorded.
2. Review redemption readiness and identify any blockers; no first redemption timestamp is recorded.
3. Reinforce the strong giver adoption trend and discuss how to sustain it, including whether the two admins need support driving broader participation.
renewal-risk-conflicting-datesPASS 1.00
Plain-English question: Two systems disagree on renewal dates — which do you trust per account, and who is actually renewing inside 90 days?
Prompt — what the model saw
Produce a 90-day renewal risk brief. Two systems hold renewal dates and disagree on some accounts; decide which to trust per account and say why (multi-year contracts are known to be wrong in ChurnZero). For every renewal: company, CSM, ARR, date used, seat utilization, 3-month usage trend, risk rating with one sentence of evidence. Flag every disagreement. Close with total ARR renewing and ARR at risk.
cost $0.2126 · 49s · in 51,380 / out 7,191 tok
✓ total_renewing✓ arr_at_risk✓ disagreements_flagged✓ trust_rule

✓ Correct Answer (ground truth)

Plain-English answer: Chargebee wins per account (multi-year contracts are known wrong in ChurnZero), with each trusted date, the reason, and a 90-day-window flag.
The answer in one line: n_accounts = 20; n_disagreements = 5; snapshot_date = 2026-09-05 (+2 more below)
n_accounts20
n_disagreements5
accounts20 items — e.g. account_alias=C-0B144C78; csm=Cole Ingram; arr=30899.00; trusted_renewal_date=2026-11-02; trusted_source_why=systems agree (annual term); in_90d_window=True; dates_disagree=False; seat_utilization_pct=75.4; usage_3m_ratio=1.03; risk=low; evidence=3-month usage ratio 1.03 (last3 avg 103 vs prior3 100), seat utilization 75% | account_alias=C-0B20DB64; csm=Dana Mercer; arr=21770.00; trusted_renewal_date=2026-10-07; trusted_source_why=systems agree (annual term); in_90d_window=True; dates_disagree=False; seat_utilization_pct=56.6; usage_3m_ratio=1; risk=medium; evidence=3-month usage ratio 1.00 (last3 avg 295 vs prior3 295), seat utilization 57% | account_alias=C-0B344485; csm=Elena Sinclair; arr=64384.00; trusted_renewal_date=2026-11-16; trusted_source_why=systems agree (annual term); in_90d_window=True; dates_disagree=False; seat_utilization_pct=78; usage_3m_ratio=1.04; risk=low; evidence=3-month usage ratio 1.04 (last3 avg 241 vs prior3 231), seat utilization 78% | account_alias=C-0B369871; csm=Dana Mercer; arr=85128.00; trusted_renewal_date=2026-10-29; trusted_source_why=systems agree (annual term); in_90d_window=True; dates_disagree=False; seat_utilization_pct=75.1; usage_3m_ratio=1.04; risk=low; evidence=3-month usage ratio 1.04 (last3 avg 330 vs prior3 316), seat utilization 75%
arr_at_risk_90d359409.00
disagreementsaccount_alias=C-0B7D2C30; cz_renewal_date=2026-09-10; cb_renewal_date=2026-09-15; is_multi_year=True; trusted=2026-09-15 | account_alias=C-0BBE3E60; cz_renewal_date=2027-09-26; cb_renewal_date=2026-09-26; is_multi_year=True; trusted=2026-09-26 | account_alias=C-0BCDB8C2; cz_renewal_date=2027-09-18; cb_renewal_date=2026-09-18; is_multi_year=True; trusted=2026-09-18 | account_alias=C-0D2AB865; cz_renewal_date=2026-09-10; cb_renewal_date=2026-09-22; is_multi_year=True; trusted=2026-09-22 | account_alias=C-0F5D2323; cz_renewal_date=2026-09-10; cb_renewal_date=2026-09-29; is_multi_year=True; trusted=2026-09-29
snapshot_date2026-09-05
total_arr_renewing_90d1048715.00
trust_rulemulti-year contracts: Chargebee is authoritative (ChurnZero known wrong); otherwise systems agree or Chargebee wins
window2026-09-05 to 2026-12-04
graded checkstotal_renewing · arr_at_risk · disagreements_flagged · trust_rule

Model's actual answer

show the model's full answer
90-day renewal risk brief

Date-source rule: Use Chargebee for every account. For multi-year contracts, Chargebee is used because ChurnZero is known to have incorrect renewal dates. For 12-month contracts, Chargebee and ChurnZero agree.

Risk rating rule: High = low utilization and/or material 3-month usage decline; Medium = utilization below 70% with broadly flat usage; Low = utilization at least 70% with stable or growing usage. ARR at risk includes High and Medium.

- C-0B7D2C30 | CSM: Dana Mercer | ARR: $65,901.00 | Date used: 2026-09-15 (Chargebee, 36-month term). DISAGREEMENT: ChurnZero 2026-09-10 vs Chargebee 2026-09-15; use Chargebee because this is multi-year. Seat utilization: 274 / 476 = 57.6%. 3-month usage: 97 → 94 → 84; Aug vs Jun = 84 - 97 = -13 (-13.4%). Risk: High — utilization is 57.6% and active users fell 13.4% over three months.
- C-0BCDB8C2 | CSM: Cole Ingram | ARR: $54,427.00 | Date used: 2026-09-18 (Chargebee, 36-month term). DISAGREEMENT: ChurnZero 2027-09-18 vs Chargebee 2026-09-18; use Chargebee because this is multi-year. Seat utilization: 232 / 424 = 54.7%. 3-month usage: 127 → 118 → 110; 110 - 127 = -17 (-13.4%). Risk: High — utilization is 54.7% and active users fell 13.4%.
- C-0D2AB865 | CSM: Elena Sinclair | ARR: $38,022.00 | Date used: 2026-09-22 (Chargebee, 24-month term). DISAGREEMENT: ChurnZero 2026-09-10 vs Chargebee 2026-09-22; use Chargebee because this is multi-year. Seat utilization: 250 / 407 = 61.4%. 3-month usage: 125 → 117 → 109; 109 - 125 = -16 (-12.8%). Risk: High — utilization is 61.4% and active users fell 12.8%.
- C-0BBE3E60 | CSM: Dana Mercer | ARR: $30,993.00 | Date used: 2026-09-26 (Chargebee, 24-month term). DISAGREEMENT: ChurnZero 2027-09-26 vs Chargebee 2026-09-26; use Chargebee because this is multi-year. Seat utilization: 74 / 114 = 64.9%. 3-month usage: 39 → 35 → 33; 33 - 39 = -6 (-15.4%). Risk: High — utilization is 64.9% and active users fell 15.4%.
- C-0F5D2323 | CSM: Cole Ingram | ARR: $90,647.00 | Date used: 2026-09-29 (Chargebee, 24-month term). DISAGREEMENT: ChurnZero 2026-09-10 vs Chargebee 2026-09-29; use Chargebee because this is multi-year. Seat utilization: 111 / 390 = 28.5%. 3-month usage: 20 → 21 → 18; 18 - 20 = -2 (-10.0%). Risk: High — utilization is only 28.5% and active users declined 10.0%.
- C-0EC6999D | CSM: Elena Sinclair | ARR: $79,419.00 | Date used: 2026-10-03 (Chargebee; matches ChurnZero; 12-month term). Seat utilization: 31 / 112 = 27.7%. 3-month usage: 17 → 16 → 15; 15 - 17 = -2 (-11.8%). Risk: High — utilization is only 27.7% and active users declined 11.8%.
- C-0B20DB64 | CSM: Dana Mercer | ARR: $21,770.00 | Date used: 2026-10-07 (Chargebee; matches ChurnZero; 12-month term). Seat utilization: 214 / 378 = 56.6%. 3-month usage: 294 → 298 → 294; 294 - 294 = 0 (0.0%). Risk: Medium — utilization is 56.6%, although usage is flat.
- C-0BBC4E7A | CSM: Cole Ingram | ARR: $56,374.00 | Date used: 2026-10-10 (Chargebee; matches ChurnZero; 12-month term). Seat utilization: 228 / 337 = 67.7%. 3-month usage: 142 → 141 → 139; 139 - 142 = -3 (-2.1%). Risk: Medium — utilization is 67.7% and usage is slightly declining.
- C-0FD551AB | CSM: Elena Sinclair | ARR: $48,815.00 | Date used: 2026-10-14 (Chargebee; matches ChurnZero; 12-month term). Seat utilization: 210 / 376 = 55.9%. 3-month usage: 123 → 122 → 126; 126 - 123 = +3 (+2.4%). Risk: Medium — utilization is 55.9%, despite modest usage growth.
- C-0F9F8F13 | CSM: Dana Mercer | ARR: $46,230.00 | Date used: 2026-10-18 (Chargebee; matches ChurnZero; 12-month term). Seat utilization: 199 / 352 = 56.5%. 3-month usage: 185 → 185 → 182; 182 - 185 = -3 (-1.6%). Risk: Medium — utilization is 56.5% and usage is slightly declining.
- C-0BC34584 | CSM: Cole Ingram | ARR: $16,740.00 | Date used: 2026-10-22 (Chargebee; matches ChurnZero; 12-month term). Seat utilization: 327 / 494 = 66.2%. 3-month usage: 104 → 104 → 106; 106 - 104 = +2 (+1.9%). Risk: Medium — utilization is 66.2%, notwithstanding modest usage growth.
- C-0B7A7546 | CSM: Elena Sinclair | ARR: $35,062.00 | Date used: 2026-10-25 (Chargebee; matches ChurnZero; 12-month term). Seat utilization: 182 / 205 = 88.8%. 3-month usage: 64 → 65 → 63; 63 - 64 = -1 (-1.6%). Risk: Low — utilization is 88.8% and usage is broadly stable.
- C-0B369871 | CSM: Dana Mercer | ARR: $85,128.00 | Date used: 2026-10-29 (Chargebee; matches ChurnZero; 12-month term). Seat utilization: 317 / 422 = 75.1%. 3-month usage: 326 → 330 → 333; 333 - 326 = +7 (+2.1%). Risk: Low — utilization is 75.1% and active users grew 2.1%.
- C-0B144C78 | CSM: Cole Ingram | ARR: $30,899.00 | Date used: 2026-11-02 (Chargebee; matches ChurnZero; 12-month term). Seat utilization: 169 / 224 = 75.4%. 3-month usage: 101 → 101 → 106; 106 - 101 = +5 (+5.0%). Risk: Low — utilization is 75.4% and active users grew 5.0%.
- C-0FC4DBB8 | CSM: Elena Sinclair | ARR: $94,732.00 | Date used: 2026-11-05 (Chargebee; matches ChurnZero; 12-month term). Seat utilization: 356 / 464 = 76.7%. 3-month usage: 189 → 191 → 193; 193 - 189 = +4 (+2.1%). Risk: Low — utilization is 76.7% and active users grew 2.1%.
- C-0D5BBE3A | CSM: Dana Mercer | ARR: $39,740.00 | Date used: 2026-11-09 (Chargebee; matches ChurnZero; 12-month term). Seat utilization: 85 / 102 = 83.3%. 3-month usage: 88 → 90 → 91; 91 - 88 = +3 (+3.4%). Risk: Low — utilization is 83.3% and active users grew 3.4%.
- C-0FB9D5AF | CSM: Cole Ingram | ARR: $63,158.00 | Date used: 2026-11-13 (Chargebee; matches ChurnZero; 12-month term). Seat utilization: 144 / 199 = 72.4%. 3-month usage: 173 → 173 → 176; 176 - 173 = +3 (+1.7%). Risk: Low — utilization is 72.4% and active users grew 1.7%.
- C-0B344485 | CSM: Elena Sinclair | ARR: $64,384.00 | Date used: 2026-11-16 (Chargebee; matches ChurnZero; 12-month term). Seat utilization: 224 / 287 = 78.0%. 3-month usage: 238 → 240 → 244; 244 - 238 = +6 (+2.5%). Risk: Low — utilization is 78.0% and active users grew 2.5%.
- C-0CB2C1B4 | CSM: Dana Mercer | ARR: $40,628.00 | Date used: 2026-11-20 (Chargebee; matches ChurnZero; 12-month term). Seat utilization: 386 / 473 = 81.6%. 3-month usage: 47 → 48 → 49; 49 - 47 = +2 (+4.3%). Risk: Low — utilization is 81.6% and active users grew 4.3%.
- C-22170CA1 | CSM: Cole Ingram | ARR: $45,646.00 | Date used: 2026-11-24 (Chargebee; matches ChurnZero; 12-month term). Seat utilization: 251 / 294 = 85.4%. 3-month usage: 143 → 148 → 146; 146 - 143 = +3 (+2.1%). Risk: Low — utilization is 85.4% and usage is above its June level.

Total ARR renewing: $1,048,715.00.

ARR at risk: $549,338.00 = High-risk ARR ($359,409.00) + Medium-risk ARR ($189,929.00).
ticket-theme-synthesis0.80
Plain-English question: What are the real themes in this quarter's support tickets, ignoring the existing tags?
Prompt — what the model saw
Synthesize the quarter's support tickets into 4 to 7 themes. Do not trust existing tags; read the text. Per theme: name, count, share, distinct accounts, ARR affected, two ticket ids, one-line recommendation. Separate broad patterns from single-account noise and rank by ARR exposure, not volume.
cost $0.1922 · 42s · in 46,907 / out 6,533 tok
✗ theme_count_range✓ counts_verifiable✓ single_account_flagged✓ arr_ranked✓ ticket_ids

✓ Correct Answer (ground truth)

Plain-English answer: 80 tickets in 4-7 themes — points-not-posting leads (20 tickets, 25%, $31,100 ARR affected) — each with counts, distinct accounts, ARR, and a recommendation.
The answer in one line: total_tickets = 80; quarter_window = 2026-06-01 through 2026-08-31
total_tickets80
noteexisting tags are noisy/unreliable; classify by text
quarter_window2026-06-01 through 2026-08-31
ranking_by_arr_exposurehris_provisioning, redemption_failures, billing_dispute, points_not_posting, slack_sync
sample_ticket_ids80 items — e.g. IC-460004, IC-460016, IC-460001, IC-460041
single_account_noise_themebilling_dispute
themes{"points_not_posting": {"count": 20, "share_pct": 25.0, "distinct_accounts": 9, "arr_affected": "31100.00", "example_ticket_ids": ["IC-460001", "IC-460002"], "single_account": false}, "slack_sync": {"
graded checkstheme_count_range · counts_verifiable · single_account_flagged · arr_ranked · ticket_ids

Model's actual answer

show the model's full answer
Ranked by unique ARR affected (not ticket volume). Total tickets: 80.

1. HRIS provisioning/sync failures — Broad pattern
- Count/share: 12 tickets; 12 ÷ 80 = 15.0%
- Distinct accounts: 3 — C-0B2213A9, C-0F6C0F34, C-0DDFC9A7
- ARR affected: $114,000 = $36,000 + $30,000 + $48,000
- Ticket examples: IC-460059, IC-460064
- Recommendation: Prioritize HRIS sync/provisioning reliability and add monitoring for skipped new-hire creation.

2. Redemption checkout, gift-card fulfillment, and deducted-points failures — Broad pattern
- Count/share: 18 tickets; 18 ÷ 80 = 22.5%
- Distinct accounts: 7 — C-0CEF69FD, C-0B827671, C-0FCCD2DF, C-0F876796, C-14264ABD, C-0D9CA315, C-0B0F1BAB
- ARR affected: $68,800 = $8,900 + $10,700 + $9,600 + $8,700 + $11,000 + $9,600 + $10,300
- Ticket examples: IC-460025, IC-460036
- Recommendation: Investigate the checkout-to-fulfillment transaction path and automatically reconcile points when gift-card orders fail.

3. Billing seat-count and renewal-tier errors — Single-account concentration
- Count/share: 16 tickets; 16 ÷ 80 = 20.0%
- Distinct accounts: 1 — C-0E9C27D1
- ARR affected: $52,000
- Ticket examples: IC-460071, IC-460075
- Recommendation: Treat C-0E9C27D1 as an urgent account-specific billing escalation; validate seat-count and renewal-pricing calculations before the next invoice.
- Noise assessment: High ticket count but not a broad pattern: all 16 tickets come from one account.

4. Recognition points not delivered or balances not updated — Broad pattern
- Count/share: 20 tickets; 20 ÷ 80 = 25.0%
- Distinct accounts: 9 — C-0D3278C7, C-0BF20542, C-0D0B047C, C-0BE96399, C-0D284E42, C-0D6CC8E3, C-21FEBCBB, C-0DD0626C, C-0B2895EF
- ARR affected: $31,100 = $3,500 + $4,500 + $4,500 + $2,700 + $3,400 + $4,200 + $2,900 + $2,500 + $2,900
- Ticket examples: IC-460004, IC-460018
- Recommendation: Audit recognition-to-points posting jobs, especially post-weekend processing, and surface delayed-balance status to users.

5. Slack recognition integration and slash-command failures — Broad pattern
- Count/share: 14 tickets; 14 ÷ 80 = 17.5%
- Distinct accounts: 4 — C-0B843542, C-10A56B0F, C-0BA71F12, C-8C2E8F00
- ARR affected: $18,900 = $4,400 + $5,400 + $3,900 + $5,200
- Ticket examples: IC-460041, IC-460044
- Recommendation: Investigate Slack authentication persistence, sync-toggle resets, and slash-command errors as a connected integration reliability issue.

Broad-pattern total: 64 tickets across four multi-account themes. Single-account concentration: 16 tickets from C-0E9C27D1.
marketing 5 tests
case-study-matchPASS 1.00
Plain-English question: Which three existing customers are the best case-study matches for this prospect?
Prompt — what the model saw
Given the prospect, rank the three most similar existing customers with public case studies for use as social proof. Similarity on industry, size band, use case, region. Cite the fields that drove each match. Do not name any customer without a case study and never include billing data or contact names.
cost $0.0779 · 19s · in 9,002 / out 1,221 tok
✓ top3✓ decoys_excluded✓ cites_fields✓ no_billing

✓ Correct Answer (ground truth)

Plain-English answer: Three ranked matches on industry, size, use case, and region (e.g. C-11C31562), with the higher-scoring decoy explicitly excluded for a mismatched field.
The answer in one line: prospect_alias = C-82AF3719
constraintsno_billing_data, no_contact_names, only_customers_with_has_case_study_true_named
decoys_excludedcompany_alias=C-D6217CAA; similarity_score=4; reason=no_case_study | company_alias=C-C153868F; similarity_score=4; reason=no_case_study
prospect_aliasC-82AF3719
prospect_fields_usedindustry, size_band, use_case, region
top3company_alias=C-11C31562; similarity_score=3 | company_alias=C-64171065; similarity_score=3 | company_alias=C-A13C193D; similarity_score=3
graded checkstop3 · decoys_excluded · cites_fields · no_billing

Model's actual answer

show the model's full answer
1. C-11C31562 — 3/4 matching fields
   - Size band: Mid-Market
   - Use case: employee_recognition
   - Region: NA-West
   - Industry differs: Manufacturing vs. Technology

2. C-64171065 — 3/4 matching fields
   - Industry: Technology
   - Size band: Mid-Market
   - Use case: employee_recognition
   - Region differs: NA-East vs. NA-West

3. C-A13C193D — 3/4 matching fields
   - Industry: Technology
   - Size band: Mid-Market
   - Region: NA-West
   - Use case differs: retention vs. employee_recognition

Arithmetic: each match scores 1 point across industry, size band, use case, and region; each listed customer matches 3 of 4 fields.
channel-attribution-mathPASS 1.00
Plain-English question: Compute cost per SQM, cost per SQO, and pipeline per dollar for every channel over six months.
Prompt — what the model saw
Compute channel performance for the trailing 6 months. Paid: spend, SQMs, SQOs, cost per SQM, cost per SQO, SQM-to-SQO rate, pipeline amount, pipeline per dollar. Organic: volume, SQO rate, pipeline. Report a channel with spend and zero SQMs as undefined, not zero. Flag rows where SQO date precedes SQM date. Finish with a reallocation recommendation and your confidence given sample sizes.
cost $0.1948 · 63s · in 44,642 / out 7,169 tok
✓ undefined_channel✓ undefined_not_zero✓ flagged_rows✓ best_channel✓ reallocation

✓ Correct Answer (ground truth)

Plain-English answer: LinkedIn Ads at $960/SQM and $3,000/SQO, organic search at $90,000 pipeline on zero spend, paid social flagged at $18,000 with zero SQMs, and a channel winner named.
The answer in one line: best_pipeline_per_dollar_channel = paid_search
best_pipeline_per_dollar_channelpaid_search
confidence_notewebinars and referral have small SQM samples (<20); treat rates as directional.
flagged_rows_sqo_before_sqmCT-000041, CT-000044
months2026-03, 2026-04, 2026-05, 2026-06, 2026-07, 2026-08
per_channel{"linkedin_ads": {"spend_usd": 24000, "sqms": 25, "sqos": 8, "pipeline_amount": 96000, "cost_per_sqm": 960.0, "cost_per_sqo": 3000.0, "sqm_to_sqo_rate": 0.32, "pipeline_per_dollar": 4.0}, "organic_sea
reallocation_recommendationfrom=paid_social; to=paid_search; rationale=paid_social has spend but zero SQMs (cost per SQM undefined, not zero); paid_search has the highest pipeline per dollar.
undefined_channelspaid_social
graded checksundefined_channel · undefined_not_zero · flagged_rows · best_channel · reallocation

Model's actual answer

show the model's full answer
Trailing 6 months: 2026-03 through 2026-08.

Paid channels

| Channel | Spend | SQMs | SQOs | Cost/SQM | Cost/SQO | SQM→SQO rate | Pipeline | Pipeline/$ |
|---|---:|---:|---:|---:|---:|---:|---:|---:|
| paid_search | $36,000 | 40 | 18 | $900 | $2,000 | 45.0% | $720,000 | $20.00 |
| linkedin_ads | $24,000 | 25 | 8 | $960 | $3,000 | 32.0% | $96,000 | $4.00 |
| paid_social | $18,000 | 0 | 0 | undefined | undefined | undefined | $0 | $0.00 |
| webinars | $9,000 | 12 | 5 | $750 | $1,800 | 41.7% | $60,000 | $6.67 |

Arithmetic:
- paid_search: $36,000 / 40 = $900 per SQM; $36,000 / 18 = $2,000 per SQO; 18 / 40 = 45.0%; $720,000 / $36,000 = $20.00 pipeline per $.
- linkedin_ads: $24,000 / 25 = $960 per SQM; $24,000 / 8 = $3,000 per SQO; 8 / 25 = 32.0%; $96,000 / $24,000 = $4.00 pipeline per $.
- paid_social: $18,000 spend with zero SQMs, so cost per SQM, cost per SQO, and SQM-to-SQO rate are undefined. $0 / $18,000 = $0.00 pipeline per $.
- webinars: $9,000 / 12 = $750 per SQM; $9,000 / 5 = $1,800 per SQO; 5 / 12 = 41.7%; $60,000 / $9,000 = $6.67 pipeline per $.

Organic/unpaid channels

| Channel | Volume (SQMs) | SQOs | SQO rate | Pipeline |
|---|---:|---:|---:|---:|
| organic_search | 30 | 10 | 33.3% | $90,000 |
| referral | 15 | 6 | 40.0% | $48,000 |

Arithmetic:
- organic_search: 10 / 30 = 33.3%; pipeline = 10 × $9,000 = $90,000.
- referral: 6 / 15 = 40.0%; pipeline = 6 × $8,000 = $48,000.

Data-quality flags: SQO date precedes SQM date
- CT-000044, linkedin_ads: SQM date 2026-07-23; SQO date 2026-07-18.
- CT-000041, linkedin_ads: SQM date 2026-06-14; SQO date 2026-06-09.

Recommendation: Reallocate the $18,000 currently in paid_social, which generated zero SQMs, away from that channel. Prioritize paid_search for incremental allocation: it has the highest observed SQM-to-SQO rate (45.0%) and pipeline efficiency ($20.00 per $), versus webinars at $6.67 and linkedin_ads at $4.00. Reduce linkedin_ads before reducing webinars: LinkedIn has the weakest paid conversion rate (32.0%), highest cost per SQO ($3,000), and its two date-ordering errors require correction before relying on its attribution.

Confidence: moderate for paid_search (40 SQMs, 18 SQOs); low-to-moderate for linkedin_ads (25 SQMs, 8 SQOs); low for webinars (12 SQMs, 5 SQOs). Confidence in stopping paid_social is high for this six-month dataset because it had $18,000 spend and zero SQMs, but the data does not establish why it produced none.
competitor-battlecard-updatePASS 1.00
Plain-English question: Update the Rivally battlecard with sourced pricing and where each side wins.
Prompt — what the model saw
Update the battlecard for the competitor. Sections: one-line positioning, pricing with source and date (newer source wins, note the conflict), where they win, where we win, objections and responses, recent changes, our 12-month win/loss record against them. Cite a snippet id for every factual claim. Rep opinion on a call is not a fact about the competitor. Anything from the old card you cannot re-source gets marked unverified.
cost $0.1121 · 36s · in 28,559 / out 4,044 tok
✓ competitor_named✓ pricing✓ win_loss✓ unverified_marked✓ citations

✓ Correct Answer (ground truth)

Plain-English answer: Rivally at $7 per user per month (the August source wins over the stale $5, conflict noted), a 13-7 win/loss record, and two unverified old claims flagged.
The answer in one line: competitor = Rivally
citation_ids_available25 items — e.g. S01, S02, S03, S04
competitorRivally
pricingvalue_per_user_per_month=7; source_snippet=S17; source_date=2026-08-12
rep_opinion_snippet_ids_not_factsS09, S21
unverified_old_claimsRivally lacks a Slack integration., Rivally was acquired by WorkHuman in 2025.
win_loss_12mowins=13; losses=7
graded checkscompetitor_named · pricing · win_loss · unverified_marked · citations

Model's actual answer

show the model's full answer
# Rivally Battlecard

## One-line positioning
Rivally is a points-based employee-recognition platform with an engaging recognition feed, positioned with EU data residency and multi-language support. [S02] [S12] [S15]

## Pricing
- Current published price: Recognition Starter is **$7/user/month**, with annual billing required, as of **2026-08-12**. [S17]
- Pricing conflict: Rivally’s earlier pricing pages listed **$5/user/month** on 2026-04-01 and 2026-01-20; the newer $7 published price wins. [S08] [S03]
- Deal-specific quotes differ from published pricing: a 500-seat prospect was quoted **$6.50/user/month** on an annual term (2026-06-02), and an 800-seat prospect reported a **$7/user/month list price with a 15% discount for a three-year term** (2026-08-14). These are call-note deal mentions, not a replacement for published list pricing. [S13] [S18]

## Where Rivally wins
- Engaging, points-based recognition feed. [S02] [S16]
- Fast setup and out-of-the-box Slack integration were praised by a mid-market reviewer. [S04]
- EU/distributed-team positioning: EU data residency is generally available, and an EU enterprise reviewer praised multi-language support for distributed EU teams. [S15] [S12]
- Support response time was praised as under four hours in a review. [S22]

## Where we win
- Analytics depth: an 800-seat prospect selected Bonusly over Rivally, citing analytics depth. [S25]
- Rivally’s analytics/reporting are repeatedly described as limited or basic; this is a relevant competitive opening, but the provided data does not independently establish Bonusly feature parity beyond the deal outcome above. [S02] [S07]
- Rivally’s enterprise administration has reported gaps: lack of SCIM provisioning, painful manual user management, lagging admin tooling, and no bulk recognition editing. [S10] [S16] [S24]
- Rivally’s EMEA rewards catalog was described as thinner than its US catalog. [S14]

## Objections and responses
- **“Rivally is better for EU teams.”**  
  Response: Acknowledge Rivally’s EU data residency and multi-language support. Re-center the evaluation on the buyer’s required analytics depth, administration workflow, and rewards-catalog coverage; Rivally reviews cite basic reporting, SCIM/manual-management friction, and a thinner EMEA catalog. Confirm Bonusly’s applicable capabilities before claiming them. [S15] [S12] [S07] [S10] [S14]

- **“Rivally is quick to implement and integrates with Slack.”**  
  Response: This is supported by a mid-market review, so do not dispute it. Evaluate implementation requirements and required administrative controls; Rivally reviewers cite lagging admin tooling and no bulk recognition editing. Confirm Bonusly’s implementation and Slack capabilities before comparison. [S04] [S16] [S24]

- **“Rivally is less expensive.”**  
  Response: Use the current published $7/user/month annual-billing price as the baseline. Ask for the actual quote, term, seat count, and discount structure: reported deal quotes include $6.50/user/month at 500 seats and $7 list with a 15% three-year discount. [S17] [S13] [S18]

- **“We need stronger reporting/export flexibility.”**  
  Response: Rivally reviews describe limited/basic analytics, CSV-only analytics exports, and difficult migration off the platform. Confirm Bonusly’s relevant reporting and export capabilities before making a direct product claim. [S02] [S07] [S20]

## Recent changes
- **2026-09-01:** Rivally Pulse engagement-survey add-on exited beta; it is priced separately rather than bundled. [S23]
- **2026-08-20:** Microsoft Teams app v2 entered public preview. [S19]
- **2026-07-01:** Dublin office opened; EU data residency became generally available. [S15]
- **2026-05-09:** Rivally hired an ex-Workday VP EMEA to lead European expansion. [S11]
- **2026-03-05:** Rivally launched Rivally Pulse as a lightweight engagement-survey add-on. [S06]

## Our 12-month win/loss record against Rivally
Period: **2025-09 through 2026-08**.

- Wins: **13**
  - Deal-A9FD43, Deal-7AA785, Deal-44C524, Deal-0D0CD6, Deal-D5B790, Deal-5C636E, Deal-67BE14, Deal-1B6969, Deal-F03E7B, Deal-072E31, Deal-F65C8F, Deal-E46EAB, Deal-1D2392.
- Losses: **7**
  - Deal-7767F5, Deal-5645A5, Deal-C6FFAA, Deal-D263E0, Deal-935746, Deal-9066A6, Deal-72A02F.
- Total: **20 deals** = 13 wins + 7 losses.
- Win rate: **65.0%** = 13 wins ÷ 20 total deals × 100.
- Loss rate: **35.0%** = 7 losses ÷ 20 total deals × 100.

The provided deals file has no snippet IDs, so the deal-record claims above cannot be cited with snippet IDs.

## Old-card items
- **“Rivally lacks a Slack integration” — contradicted.** A reviewer said Slack integration worked out of the box. [S04]
- **“Rivally was acquired by WorkHuman in 2025” — unverified.** No provided source supports this.
nurture-sequence-diagnosisPASS 1.00
Plain-English question: What is broken in each email sequence — rates, overlaps, tracking errors?
Prompt — what the model saw
Review the sequences. Per sequence: sent, open rate, reply rate, meeting rate, weakest step. Identify tracking errors (opened above sent), audience overlap between sequences, and the failure mode for anything under 2 percent reply. One change per weak sequence and which to fix first. Under 350 words.
cost $0.2339 · 56s · in 69,586 / out 5,544 tok
✓ tracking_error✓ overlap_pair✓ weakest_step✓ fix_priority

✓ Correct Answer (ground truth)

Plain-English answer: Per-sequence open, reply, and meeting rates with the weakest step (all three weakest at step 3), an opened-above-sent tracking error, and audience overlap flagged.
The answer in one line: fix_priority_first = Cold Outbound - HR Leaders
all_pairwise_overlaps['Cold Outbound - HR Leaders', 'Cold Outbound - People Ops'], ['Expansion Nurture', 'New Logo Nurture']
audience_overlap_pairCold Outbound - HR Leaders, Cold Outbound - People Ops
failure_modeCold Outbound - HR Leaders=opens healthy (~37%) but replies near zero from step 1 -> body/CTA not landing, not a deliverability or subject-line problem
fix_priority_firstCold Outbound - HR Leaders
per_sequence{"New Logo Nurture": {"sent": 1386, "opened": 490, "replied": 90, "meetings": 27, "open_rate": 0.3535, "reply_rate": 0.0649, "meeting_rate": 0.0195, "weakest_step": 3}, "Expansion Nurture": {"sent": 8
tracking_errorsequence=Expansion Nurture; step=2; sent=300; opened=340; issue=opened exceeds sent
under_2pct_replyCold Outbound - HR Leaders
graded checkstracking_error · overlap_pair · weakest_step · fix_priority

Model's actual answer

show the model's full answer
Sequence performance (totals across steps; rate = total outcome ÷ total sent):

- New Logo Nurture: sent 1,386; open rate 490 ÷ 1,386 = 35.35%; reply rate 90 ÷ 1,386 = 6.49%; meeting rate 27 ÷ 1,386 = 1.95%. Weakest step: 3, reply rate 18 ÷ 428 = 4.21%. Change: replace Step 3 with a distinct CTA.
- Expansion Nurture: sent 875; open rate 565 ÷ 875 = 64.57%; reply rate 59 ÷ 875 = 6.74%; meeting rate 12 ÷ 875 = 1.37%. Weakest step: 3, reply rate 12 ÷ 275 = 4.36%. Change: replace Step 3 with a distinct CTA.
- Cold Outbound - HR Leaders: sent 1,785; open rate 545 ÷ 1,785 = 30.53%; reply rate 8 ÷ 1,785 = 0.45%; meeting rate 0 ÷ 1,785 = 0.00%. Weakest step: 3, reply rate 1 ÷ 590 = 0.17%. Failure mode: reply conversion is below 2% at every step—5 ÷ 600 = 0.83%, 2 ÷ 595 = 0.34%, 1 ÷ 590 = 0.17%—despite opens; no meetings result. Change: rebuild the sequence’s targeting/message before further sends.
- Cold Outbound - People Ops: sent 1,163; open rate 340 ÷ 1,163 = 29.23%; reply rate 29 ÷ 1,163 = 2.49%; meeting rate 6 ÷ 1,163 = 0.52%. Weakest step: 3, reply rate 6 ÷ 377 = 1.59%. Failure mode: Step 3 falls below 2% reply after Step 1 (14 ÷ 400 = 3.50%) and Step 2 (9 ÷ 386 = 2.33%). Change: remove or rewrite Step 3.

Tracking error: Expansion Nurture Step 2 has 340 opens ÷ 300 sent = 113.33%; opened exceeds sent by 40.

Audience overlap:
- Expansion Nurture / New Logo Nurture: CT-000301, CT-000624.
- Cold Outbound - HR Leaders / Cold Outbound - People Ops: CT-000849, CT-000884, CT-000890, CT-001033, CT-001097, CT-001101, CT-001103, CT-001105, CT-001130, CT-001153, CT-001159, CT-001217, CT-001227, CT-001236, CT-001255, CT-001258, CT-001277, CT-001285, CT-001311, CT-001345.

Fix first: Cold Outbound - HR Leaders, because its aggregate reply rate is 0.45% and it generated zero meetings.
weekly-marketing-goals-rollupPASS 1.00
Plain-English question: Are we on pace on the quarter's marketing goals?
Prompt — what the model saw
Produce the weekly marketing goals update for the active quarter: SQMs, SQOs, DS2s, closed-lost MIA rate, same-quarter close count, active pipeline coverage against target. For each: QTD actual, target, delta, pace (on/behind/ahead given days elapsed). One paragraph on what moved this week.
cost $0.1187 · 32s · in 33,631 / out 3,000 tok
✓ metrics_present✓ deltas✓ coverage_ratio✓ pace✓ paragraph

✓ Correct Answer (ground truth)

Plain-English answer: SQMs ahead of pace, SQOs on pace, DS2s behind (35 short of expected at day 66 of 92), with deltas and same-quarter closes.
The answer in one line: days_in_quarter = 92; days_elapsed = 66; coverage_ratio_active_pipeline = 0.75; elapsed_fraction = 0.7174 (+1 more below)
days_in_quarter92
coverage_ratio_active_pipeline0.75
days_elapsed66
elapsed_fraction0.7174
metrics{"SQMs": {"qtd_actual": 230, "target": 300, "delta": -70, "expected_at_day_elapsed": 215.22, "pace": "ahead"}, "SQOs": {"qtd_actual": 84, "target": 120, "delta": -36, "expected_at_day_elapsed": 86.09,
pace_ruleexpected = target * days_elapsed/days_in_quarter; within +/-5% of expected = on, above = ahead, below = behind; lower_better metrics invert.
this_week_paragraph_required1
graded checksmetrics_present · deltas · coverage_ratio · pace · paragraph

Model's actual answer

show the model's full answer
Q3-2026: 66 of 92 days elapsed (71.7%).

| Metric | QTD actual | Target | Delta | Pace |
|---|---:|---:|---:|---|
| SQMs | 230 | 300 | -70 | Ahead — prorated target: 300 × 66/92 = 215.2; actual is +14.8 above pace |
| SQOs | 84 | 120 | -36 | Behind — prorated target: 120 × 66/92 = 86.1; actual is -2.1 below pace |
| DS2s | 40 | 75 | -35 | Behind — prorated target: 75 × 66/92 = 53.8; actual is -13.8 below pace |
| Closed-lost MIA rate | 20.0% | 10.0% | +10.0 pp | Behind — 5 closed-lost MIAs / 25 closed-lost total = 20.0%; target is lower-better |
| Same-quarter closes | 10 | 20 | -10 | Behind — prorated target: 20 × 66/92 = 14.3; actual is -4.3 below pace |
| Active pipeline coverage against target | 75.0% ($3.0M / $4.0M) | 100.0% ($4.0M) | -25.0 pp (-$1.0M) | Ahead — prorated target: $4.0M × 66/92 = $2.87M; actual is +$0.13M above pace |

This week’s movement cannot be determined from the provided QTD-only data; no prior-week actuals or weekly activity data were provided.
communication 5 tests
ceo-slack-compression0.80
Plain-English question: Compress the forecast analysis into one Slack message the CEO can read in ten seconds.
Prompt — what the model saw
Compress the forecast analysis below into a single Slack message for the CEO. Rules: at most three sentences; under 80 words; lead with the decision or the so-what; keep every distinct number that matters and the one caveat that changes the conclusion; cut any sentence that does not carry a claim, a number, or a directive. No em dashes, no throat-clearing phrases.
cost $0.0820 · 21s · in 9,137 / out 1,565 tok
✓ max_3_sentences✓ under_80_words✓ weighted_present✗ caveat_present✓ no_em_dash

✓ Correct Answer (ground truth)

Plain-English answer: Three sentences, under 80 words, decision first, every distinct number kept plus the one caveat — all checked by deterministic text rules.
The answer in one line: weighted_number = 115976; must_keep = data-quality caveat — deleting the bad news fails
weighted_number115,976
limitmax 3 sentences, max 80 words, no em-dashes
must_keepdata-quality caveat — deleting the bad news fails
graded checksmax_3_sentences · under_80_words · weighted_present · caveat_present · no_em_dash

Model's actual answer

show the model's full answer
Do not treat $115,976.75 as a reliable Q3 forecast without re-qualification. It is $44,729 COMMIT + 35% × $203,565 BEST_CASE ($71,247.75), across 54 of 86 in-quarter deals; 32 deals totaling $227,575 are excluded after 2026-09-30, including COMMIT Deal-D348E1 ($13,770). All 7 in-quarter COMMIT deals lack why-buys, and 85 of 86 deals lack an owner.
stalled-deal-followup-emailPASS 1.00
Plain-English question: Write a follow-up email for this stalled deal — under 120 words, one prior touch, one ask.
Prompt — what the model saw
Write a follow-up email for this stalled deal. Under 120 words. Reference one specific prior touch from the engagement history, make one clear ask, and match the tone of the prior thread. No invented details.
cost $0.0583 · 20s · in 23,282 / out 470 tok
✓ word_cap✓ references_touch✓ single_ask

✓ Correct Answer (ground truth)

Plain-English answer: An email that references the July 28 milestone-awards demo, makes one clear ask, and invents nothing — Deal-0D2F7A, 31 days since last engagement.
The answer in one line: amount = 5100; word_cap = 120; days_since_last_engagement = 31; deal_alias = Deal-0D2F7A (+4 more below)
amount5,100
days_since_last_engagement31
word_cap120
allowed_facts14 items — e.g. Deal-0D2F7A, $5,100, DS3, Alex Franklin
allowed_newENG-00001, ENG-00002, ENG-00003, ENG-00004, ENG-00005
deal_aliasDeal-0D2F7A
must_referenceengagement_id=ENG-00002; date=2026-07-28; type=meeting; why=most substantive prior touch; concrete prospect reactions to milestone awards and points catalog
ownerAlex Franklin
single_cta1
stageDS3
tonewarm, concise, professional (matches prior thread)
graded checksword_cap · references_touch · single_ask

Model's actual answer

show the model's full answer
Subject: Quick follow-up on the July 28 demo

Hi [Name],

Following up on the recap and 150-seat pricing I sent after our July 28 demo. The People team had responded strongly to automated milestone awards and the points catalog.

Would you be open to a 15-minute conversation this week to confirm whether this is still a priority?

Best,  
Alex
funnel-digest-paragraphPASS 1.00
Plain-English question: Write the weekly GTM digest — one paragraph per team, every number traceable.
Prompt — what the model saw
Write the weekly GTM digest: one paragraph per team (Marketing, Sales, CS, PLG) in Bonusly brand voice. Every number must trace to the extracts. No customer contact names, no employee performance commentary, no compensation. Four paragraphs, under 400 words total.
cost $0.0964 · 23s · in 31,736 / out 1,469 tok
✓ four_paragraphs✓ word_cap✓ teams

✓ Correct Answer (ground truth)

Plain-English answer: Four paragraphs (Marketing, Sales, CS, PLG) using only the allowed numbers, no contact names, no performance commentary, under 400 words.
The answer in one line: word_cap = 400
word_cap400
allowed_numbers16 items — e.g. 2, 3, 9, 08
bannedcustomer contact names, employee performance commentary, compensation
required_paragraphsMarketing, Sales, CS, PLG
graded checksfour_paragraphs · word_cap · teams

Model's actual answer

show the model's full answer
Marketing: We generated 46 SQMs against a weekly target of 52, a gap of 6 SQMs (52 − 46) and 88.5% target attainment (46 ÷ 52 × 100). The webinar contributed 18 SQMs, representing 39.1% of weekly SQMs (18 ÷ 46 × 100). Paid-search cost per SQM held at $150.

Sales: The team converted 14 SQOs, set 9 DS2 meetings, and created $310,000 in new pipeline. Three same-quarter closes were recorded this week.

CS: Two renewals were saved this week. Team NPS moved to 61, while 3 red-flag accounts remain open heading into next week.

PLG: PLG added 412 new signups with 31% activation. Thirty-eight companies reached the aha moment of 10 recognition gives.
partner-digest-section0.67
Plain-English question: Write the partner digest so every partner in the roster appears exactly once.
Prompt — what the model saw
Write the partner digest for the period. Every partner in the roster appears once: active plays get status with numbers, quiet partners get one line. Partner-sourced pipeline count and amount must match the deal data. Nothing omitted, nothing added.
cost $0.0640 · 15s · in 23,848 / out 845 tok
✓ all_partners✗ pipeline_amount✓ quiet_one_line

✓ Correct Answer (ground truth)

Plain-English answer: Four active partners with status and numbers, four quiet partners with one line each, and partner-sourced pipeline that reconciles to the deal data.
The answer in one line: rule = every roster partner named exactly once; quiet partners get one line; no partners outside roster.
active_no_dealsWorkWell Group
partner_sourced_pipelinecount=5; amount=550000
per_partner_pipeline{"Apex Rewards Co": {"count": 2, "amount": 275000}, "HRCloud Partners": {"count": 1, "amount": 140000}, "CultureBridge": {"count": 2, "amount": 135000}}
quiet_partnersRecogniq, KudosWave, PeopleFirst Advisors, TotalPerk
rosterpartner_name=Apex Rewards Co; status=active | partner_name=HRCloud Partners; status=active | partner_name=CultureBridge; status=active | partner_name=WorkWell Group; status=active | partner_name=Recogniq; status=quiet | partner_name=KudosWave; status=quiet … (+2 more)
ruleevery roster partner named exactly once; quiet partners get one line; no partners outside roster.
graded checksall_partners · pipeline_amount · quiet_one_line

Model's actual answer

show the model's full answer
Apex Rewards Co — Co-webinar locked for 09-15. Partner-sourced pipeline: 2 deals, $275,000 ($180,000 Deal-DDAAF2 + $95,000 Deal-2CF33E); both in DS1.

HRCloud Partners — Integration referral cleared security review and moved to DS2. Partner-sourced pipeline: 1 deal, $140,000 (Deal-F1CDA5).

CultureBridge — Lunch-and-learn produced two early-stage sourced opportunities. Partner-sourced pipeline: 2 deals, $135,000 ($60,000 Deal-096E1D + $75,000 Deal-067213).

WorkWell Group — No sourced deals this period: 0 deals, $0. Joint-playbook planning call booked for 09-09; restart targeted for Q4.

Recogniq — Quiet.

KudosWave — Quiet.

PeopleFirst Advisors — Quiet.

TotalPerk — Quiet.
rfp-answer-from-policyPASS 1.00
Plain-English question: Answer the 10 RFP items from the policy excerpts only — no guessing.
Prompt — what the model saw
Answer the 10 questionnaire items from the policy excerpts only. Cite the excerpt id for every answer. Where the excerpts do not answer the question, mark it unanswerable and say what document would; do not guess. Tone: vendor response, direct.
cost $0.0671 · 18s · in 23,943 / out 1,089 tok
✓ answered_count✓ unanswerable_flagged✓ citations✓ no_guess

✓ Correct Answer (ground truth)

Plain-English answer: Seven answered with excerpt citations (Q1-Q7), three flagged unanswerable with the document that would answer them (Q8-Q10).
The answer in one line: answered_count = 7; rule = unanswerable items must be flagged and the document that would answer them named; do not guess.
answered_count7
answer_map{"Q1": ["P1"], "Q2": ["P1"], "Q3": ["P2"], "Q4": ["P3"], "Q5": ["P4"], "Q6": ["P5"], "Q7": ["P6"]}
ruleunanswerable items must be flagged and the document that would answer them named; do not guess.
unanswerableQ8, Q9, Q10
valid_citation_idsP1, P2, P3, P4, P5, P6, P7, P8
graded checksanswered_count · unanswerable_flagged · citations · no_guess

Model's actual answer

show the model's full answer
Q1. Yes. Customer data is encrypted at rest using AES-256. [P1]

Q2. Yes. Data in transit is encrypted with TLS 1.2 or higher. [P1]

Q3. Yes. Bonusly maintains a SOC 2 Type II report, renewed annually. A copy is available to prospects under NDA. [P2]

Q4. Customer data is retained for the duration of the contract plus 90 days, then deleted from production systems. [P3]

Q5. The current subprocessor list is published at trust.bonusly.com. Customers receive 30 days’ notice before a new subprocessor is added. [P4]

Q6. Yes. SAML 2.0 single sign-on is available on the Enterprise plan. [P5]

Q7. Production databases are backed up daily. Backups are encrypted and retained for 35 days. [P6]

Q8. Unanswerable from the provided excerpts. An ISO 27001 certificate or applicable compliance certification documentation would answer this question. [P1–P8]

Q9. Unanswerable from the provided excerpts. The contractual SLA or service agreement would answer this question. [P1–P8]

Q10. Unanswerable from the provided excerpts. A HIPAA BAA policy or executed BAA template would answer this question. [P1–P8]
ops-maintenance 5 tests
skill-file-reconciliationPASS 1.00
Plain-English question: Audit a skill set against its manifest and flag every conflict with a severity and an action.
Prompt — what the model saw
Reconcile the skill set below against its manifest. Find and report (with severity CRITICAL/WARNING/INFO and an action type TRIM_DESC, UPDATE_BODY, DELETE_SKILL, MERGE, or REVIEW): (1) any two skills whose ALWAYS-trigger phrases overlap/duplicate, (2) any circular delegation chain between skills (name it), (3) any delegation target that does not exist (dangling, name it), (4) any version conflict and which skill should survive, (5) how many manifest descriptions exceed 1,024 characters, (6) any hardcoded page ids, dates, or person names in skill bodies, (7) manifest drift in BOTH directions (files with no manifest row, and manifest rows with no file). Make one proposal per finding; rewrite nothing.
cost $0.8111 · 83s · in 167,441 / out 15,273 tok
✓ duplicate_trigger_found✓ circular_chain✓ dangling_target✓ oversized_desc_count✓ hardcoded_values✓ manifest_drift✓ severity_and_action

✓ Correct Answer (ground truth)

Plain-English answer: A severity-ranked list of TRIM_DESC / UPDATE_BODY / DELETE_SKILL / MERGE / REVIEW actions covering every rule violation found.
The answer in one line: files_audited = 14; rank = CRITICAL / WARNING / INFO with one fix action per issue
files_audited14
findingsduplicate trigger, circular delegation chain, dangling file reference, oversized description, hardcoded values, manifest drift
rankCRITICAL / WARNING / INFO with one fix action per issue
graded checksduplicate_trigger_found · circular_chain · dangling_target · oversized_desc_count · hardcoded_values · manifest_drift · severity_and_action

Model's actual answer

show the model's full answer
CRITICAL | MERGE | `comms-drafter` + `email-drafter`
- Overlapping ALWAYS triggers include: “write me an email,” “draft a follow-up,” “help me reply,” “what should I say,” “bump email,” “contract nudge,” review/rewrite requests, and all customer/prospect email types.
- Proposal: retain `comms-drafter` as the broader external-communications skill. Merge the email-specific identity, Gmail-signature retrieval, and email-client formatting requirements from `email-drafter`; then delete `email-drafter`.

WARNING | REVIEW | `pipeline-intelligence-report` + `weekly-pipeline-report`
- Overlapping ALWAYS triggers include: “pipeline update,” “what does pipeline look like,” “update the pipeline,” and variations of “pipeline report.”
- Proposal: retain both because their deliverables differ. Narrow triggers: reserve `pipeline-intelligence-report` for full active-deal scoring/tiering, and `weekly-pipeline-report` for weekly performance/funnel/bookings reporting.

INFO | REVIEW | Circular delegation chains
- No circular delegation chain is explicitly defined.
- Observed directed chains: `next-to-close` → `pipeline-intelligence-report` → `closed-lost-analysis`; `pipeline-intelligence-report` → `analysis-validator`; `deal-strategy-coach` → `email-drafter`; `deal-strategy-coach` → `prospect-research-multithreading`.
- Proposal: keep the chains acyclic; do not add a reverse delegation from `closed-lost-analysis` to `pipeline-intelligence-report`.

CRITICAL | REVIEW | Dangling delegation target: `prospect-research-multithreading`
- Referenced by `comms-drafter`, `deal-strategy-coach`, and `email-drafter`.
- No manifest row or supplied skill file exists.
- Proposal: add the missing skill and manifest row, or remove/replace all three handoffs.

CRITICAL | REVIEW | Dangling delegation target: `bonusly-brand`
- Referenced by `comms-drafter`, `email-drafter`, `sales-forecast`, and `signalforge-claim-compressor`.
- No manifest row or supplied skill file exists.
- Proposal: add the missing skill and manifest row, or replace these dependencies with an existing canonical brand reference.

WARNING | REVIEW | Dangling delegation targets in `analysis-validator`
- `bonusly-data-questions`
- `bonusly-product-questions`
- `bonusly-business-reporting-questions`
- `bonusly-rewards-questions`
- `bonusly-ppp-questions`
- `bonusly-feature-flag-questions`
- `bonusly-deal-desk-questions`
- `bonusly-datadog-questions`
- No manifest rows or supplied skill files exist.
- Proposal: add manifest rows and files for each specialist skill before allowing `analysis-validator` to delegate validation.

WARNING | REVIEW | Dangling orchestration target: `skill-orchestrator`
- Referenced by `analysis-validator` and `signalforge-feedback`.
- No manifest row or supplied skill file exists.
- Proposal: add the orchestration skill and manifest row, or remove its required-registration and sync references.

CRITICAL | UPDATE_BODY | `closed-lost-analysis` vs `stale-pipeline-report`
- Conflict: `closed-lost-analysis` queries `GONG_TRANSCRIPTS_AGG.t.SNIPPET`; `stale-pipeline-report` states that `GONG_TRANSCRIPTS_AGG` has only `CONVERSATION_KEY` and `TRANSCRIPT`, and explicitly prohibits other transcript columns.
- Surviving skill: `stale-pipeline-report` version 1.1, dated 2026-06-10.
- Proposal: update `closed-lost-analysis` to use `t.TRANSCRIPT` and remove `t.SNIPPET`.

WARNING | UPDATE_BODY | `analysis-validator`
- Conflict: declared/body version is `3.6`, but its Validation Trail template identifies the validator as `analysis-validator v3.2`.
- Surviving version: `3.6`.
- Proposal: update the Validation Trail template version reference to `v3.6`.

WARNING | UPDATE_BODY | `sales-forecast`
- Conflict: the skill states it is current-quarter and quarter-agnostic, while Step 1A is titled “HubSpot: Open Q2 Deals,” Step 3 mandates a “Q2 Narrative” tab, and Step 0 hardcodes “Q2 (April 1 – June 30, 2026).”
- Surviving version: changelog version `1.1`, which states Q2-specific content was removed in favor of current-quarter behavior.
- Proposal: remove the stale Q2-specific body references.

INFO | TRIM_DESC | Manifest description-length audit
- Arithmetic: 14 manifest rows; 0 descriptions with `description_chars > 1,024`.
- Maximum declared description length: 1,006 characters.
- Proposal: no required trim for the 1,024-character manifest limit.

WARNING | UPDATE_BODY | `analysis-validator`
- Hardcoded dates: April 26, 2026; May 4, 2026; May 9, 2026; March 28, 2023; May 2026; Q1 2026; Q2 2026; and other dated changelog/reference claims.
- Hardcoded person names: Manish, Amani, Dana Mercer, Gavin Porter, Alaina Loori, Shealagh Coughlin, Bryce Harmon, Hugo Lindqvist, Alex Franklin, Cole Ingram, Colleen Perry, Ellie Barton, Ashley Reyer, Ashley Le, Megan Franz, Elena Sinclair, Tracy, Youssef Elkhateeb, Amanda Czenkus, Ben Castelli, John Thomas, Yasmin Wahid.
- Proposal: move roster, calibration anchors, and dated system-state assertions to live references.

WARNING | UPDATE_BODY | `closed-lost-analysis`
- Hardcoded dates: May 2026, May 4–12, May 4, 2026, March 28, 2023, and example dates such as 4/13 and 5/15.
- Hardcoded named entities used as historical examples include Softheon, Estee Lauder, MinIO, LIFTOFF, Nestlé, Ozinga, Aurora Innovation, GCash, Ethos Cannabis, StickerYou, Nectar, Awardco, Motivosity, WorkTango, WorkHuman, Workday, ADP, Rippling, and UKG.
- Proposal: move historical examples and dated “confirmed” statements to a maintained reference file.

WARNING | UPDATE_BODY | `deal-strategy-coach`
- Hardcoded page ID: `2257879045`.
- Hardcoded dates: 2026 pricing, April 2026 playbook, six-month windows, and dated plan assumptions.
- Hardcoded person name: Farid.
- Proposal: replace the fixed Confluence page ID and dated commercial reference data with maintained references.

WARNING | UPDATE_BODY | `partner-digest`
- Hardcoded page/folder IDs: `2286616609`, `2286321666`, `2265382925`, `2236940297`, `2237825028`, `2239365136`, `2238283777`.
- Hardcoded dates: May 16, 2026; May 17, 2026; May 19, 2026; June 2, 2026; Q2/Q3 2026.
- Hardcoded person names: Amani Phipps, Kelli, Jen Lee, Hani, Bryce, Sara.
- Proposal: move destinations, canonical-page references, contact names, and program lists to a maintained partner configuration reference.

WARNING | UPDATE_BODY | `pipeline-intelligence-report`
- Hardcoded dates: May 2026, March 2023, T120D/T180D windows, and version-specific references.
- Hardcoded person names: Bryce Harmon, Dana Mercer, Cole Ingram, Alex Franklin, Gavin Porter.
- Hardcoded HubSpot organization ID: `1973303` appears in required deal-link templates.
- Proposal: move owner roster, organization URL configuration, and dated system-state assertions to referenced configuration.

WARNING | UPDATE_BODY | `sales-forecast`
- Hardcoded page IDs: `2232811524`, `2232582148`.
- Hardcoded dates: April 1–June 30, 2026; July 9, 2026; April 27, 2026; Q1/Q2/Q3 2026.
- Hardcoded person names: Alaina and Elena.
- Proposal: move Confluence destination IDs, named leadership references, and quarterly examples to configuration/reference files.

WARNING | UPDATE_BODY | `signalforge-feedback`
- Hardcoded page IDs: `2295136266`, `2232811524`, `2234417154`, `2247295002`.
- Proposal: move feedback-log and related Confluence identifiers into a maintained configuration reference.

WARNING | UPDATE_BODY | `stale-pipeline-report`
- Hardcoded date: June 10, 2026.
- Hardcoded system IDs: Slack channel `C0561C1JCPJ` and HubSpot organization ID `1973303`.
- Hardcoded named entity: Bonusly Support.
- Proposal: move delivery-channel, HubSpot URL, and roster/exclusion configuration into references.

WARNING | UPDATE_BODY | `weekly-pipeline-report`
- Hardcoded spreadsheet IDs: `1CLZeOsElVDF_LF0ZG_t2nfwvhnZ6bpwqM_nX3WEYzcw`, `1ENuaEcCuLjdKhMvp8FK3Ys1ek5Aw9ZuOZhsHJJFoB_k`.
- Hardcoded dates: April 1–June 30, 2026; Q1 2026; Q2 references throughout.
- Hardcoded person name: Ben Lavin.
- Proposal: move spreadsheet identifiers, owner targeting, and quarter-specific historical context to maintained references.

INFO | REVIEW | `model-selection`
- Hardcoded dates: `last_checked: 2026-05-19`, changelog dates April 14, 2026; May 19, 2026; model release/version dates.
- Proposal: retain model metadata in a dedicated, refreshable registry reference rather than the skill body.

INFO | REVIEW | `signalforge-claim-compressor`
- Hardcoded date: 2026-05-09.
- Proposal: retain only in changelog metadata or move changelog to a reference file.

INFO | REVIEW | `comms-drafter`, `email-drafter`, `next-to-close`
- No hardcoded Confluence page IDs, concrete dates, or individual person names found in the supplied bodies.
- Proposal: no change required.

INFO | REVIEW | Manifest drift: files with no manifest row
- Arithmetic: 14 supplied skill files − 14 matching manifest file aliases = 0.
- Proposal: no action required.

INFO | REVIEW | Manifest drift: manifest rows with no supplied file
- Arithmetic: 14 manifest rows − 14 matching supplied skill files = 0.
- Proposal: no action required.
runbook-from-slack-thread0.75
Plain-English question: Turn the resolved incident thread into a runbook.
Prompt — what the model saw
Turn the resolved incident thread into a runbook: ordered steps with the exact command or action taken, who ran it, how success was verified, and rollback for each step that changed state. Every step must trace to a message in the thread. Add nothing the thread does not contain; where the thread is unclear, mark the step as needing confirmation.
cost $0.1369 · 33s · in 19,775 / out 3,547 tok
✗ ordered_steps✓ rollback✓ needs_confirmation✓ sourced

✓ Correct Answer (ground truth)

Plain-English answer: Ordered steps from the thread, each with the exact command, who ran it, how success was verified, and rollback where state changed.
The answer in one line: rule = no steps beyond what the thread contains; every step traces to a message id.
ambiguous_steporder=4; msg=M05; mark=needs-confirmation
ruleno steps beyond what the thread contains; every step traces to a message id.
stepsorder=1; msg=M01; actor=Bryce Harmon; action=acknowledge PagerDuty alert, take IC; state_change=False; verified_by=M01 | order=2; msg=M02; actor=Farid Osman; action=check queue depth; command=bundle exec rake sidekiq:queue_depth; state_change=False; verified_by=M02 (48,213 pending) | order=3; msg=M04; actor=Farid Osman; action=pause auto-enqueue via feature flag; command=bin/rails runner 'FeatureFlag.disable(:auto_recognition_enqueue)'; state_change=True; rollback=bin/rails runner 'FeatureFlag.enable(:auto_recognition_enqueue)'; verified_by=M07 (queue depth falling) | order=4; msg=M05; actor=Elena Sinclair; action=cleared the dead set; state_change=True; needs_confirmation=thread gives no command or method for clearing the dead set | order=5; msg=M06; actor=Bryce Harmon; action=scale reward-worker to 6 replicas; command=kubectl scale deployment/reward-worker --replicas=6; state_change=True; rollback=kubectl scale deployment/reward-worker --replicas=3; verified_by=M07/M08 | order=6; msg=M08; actor=Cole Ingram; action=verify queue drained and error rate baseline; command=bundle exec rake sidekiq:queue_depth; state_change=False; verified_by=M08 (returns 0) … (+2 more)
graded checksordered_steps · rollback · needs_confirmation · sourced

Model's actual answer

show the model's full answer
## Reward-worker queue incident runbook

| Step | Exact command or action taken | Who ran it | Success verification | Rollback | Trace |
|---|---|---|---|---|---|
| 1 | Acknowledged PagerDuty alert for reward-worker queue depth >10k; took incident command (IC). | Bryce Harmon | Alert was acknowledged and IC was taken. | N/A — no state-changing system action stated. | M01 |
| 2 | `bundle exec rake sidekiq:queue_depth` | Farid Osman | Reward queue returned **48,213 pending jobs**. Normal was stated as under 500. | N/A — read-only check. | M02 |
| 3 | Checked the dead set. Exact command or console action was not provided. | Farid Osman | Found **112 jobs**, all `Redis::TimeoutError`, from around 13:58. | N/A — read-only check. | M03 |
| 4 | `bin/rails runner 'FeatureFlag.disable(:auto_recognition_enqueue)'` | Farid Osman | Thread states this was done to pause enqueue and stop the bleed. Explicit verification of the feature-flag state was not provided; needs confirmation. | `bin/rails runner 'FeatureFlag.enable(:auto_recognition_enqueue)'` | M04 |
| 5 | Cleared out the dead set. Exact command or console action was not provided. | Elena Sinclair | No explicit verification of dead-set removal was provided; needs confirmation. | No rollback was provided; needs confirmation. | M05 |
| 6 | `kubectl scale deployment/reward-worker --replicas=6` — scaled from 3 replicas. | Bryce Harmon | Subsequent update reported queue depth at 9,400 and falling at approximately 1,200 jobs/min. No explicit replica-count verification was provided. | `kubectl scale deployment/reward-worker --replicas=3` | M06, M07 |
| 7 | Monitored reward queue depth. Exact command or action was not provided. | Farid Osman | Queue depth was **9,400** and falling approximately **1,200 jobs/min**. | N/A — monitoring only. | M07 |
| 8 | `bundle exec rake sidekiq:queue_depth` | Cole Ingram | Command returned **0**. Datadog error rate was back to baseline. | N/A — read-only check. | M08 |
| 9 | `bin/rails runner 'FeatureFlag.enable(:auto_recognition_enqueue)'` | Bryce Harmon | **40 new jobs** processed cleanly in the next **3 minutes**. | Needs confirmation. The thread contains `bin/rails runner 'FeatureFlag.disable(:auto_recognition_enqueue)'` as the rollback for Step 4, but does not explicitly state it as rollback for this re-enable action. | M09; related rollback command in M04 |
| 10 | `kubectl scale deployment/reward-worker --replicas=3` — scaled workers back down. | Bryce Harmon | Queue was stable at **0**; incident was resolved. | Needs confirmation. The thread does not explicitly provide a rollback for this scale-down action. | M10 |
datadog-incident-timelinePASS 1.00
Plain-English question: Sequence the failure from the logs — what broke first, and what cascaded after it?
Prompt — what the model saw
From the log slice, sequence the failure: first error with timestamp, the cascade in order, the service and job involved, and the Datadog query that would confirm the first error. State what the logs do not show.
cost $0.0875 · 20s · in 27,450 / out 2,164 tok
✓ first_error_ts✓ service_named✓ cascade_ordered✓ query✓ gaps_stated

✓ Correct Answer (ground truth)

Plain-English answer: A reward-service Redis timeout at 14:01:12Z cascades to sidekiq at 14:01:40 and api-gateway at 14:03:05, with the Datadog query that confirms the first error.
The answer in one line: job_class_involved = RewardGiveJob
cascade_orderservice=reward-service; first_error_at=2026-09-03T14:01:12Z | service=sidekiq; first_error_at=2026-09-03T14:01:40Z | service=api-gateway; first_error_at=2026-09-03T14:03:05Z | service=web-app; first_error_at=2026-09-03T14:03:30Z
clean_servicespostgres
confirming_queryservice:reward-service status:error "@message:Redis::TimeoutError"
first_errortimestamp=2026-09-03T14:01:12Z; service=reward-service; message=Redis::TimeoutError: Connection to Redis at redis-primary:6379 timed out after 5s
job_class_involvedRewardGiveJob
logs_do_not_showroot cause of the Redis timeout, redis-server's own logs, infrastructure metrics (CPU/memory/network), any deploy or config change preceding the incident, who applied mitigation or when (no actor fields in logs)
graded checksfirst_error_ts · service_named · cascade_ordered · query · gaps_stated

Model's actual answer

show the model's full answer
First logged error:
- 2026-09-03T14:01:12Z — `reward-service` — `Redis::TimeoutError: Connection to Redis at redis-primary:6379 timed out after 5s`

Cascade, in logged order:
1. 14:01:12Z: `reward-service` times out connecting to `redis-primary:6379`.
2. 14:01:20Z, 14:01:30Z, 14:01:40Z: `reward-service` reports retries exhausted for `RewardGiveJob`.
3. 14:01:40Z onward: `sidekiq` reports `RewardGiveJob` failures and retries.
4. 14:02:30Z: `sidekiq` reports `Queue reward depth above 10,000`.
5. 14:03:05Z onward: `api-gateway` reports 502 upstream timeouts calling `reward-service`.
6. 14:03:30Z onward: `web-app` reports Give form submission failures caused by the upstream 502s.
7. 14:22:10Z: `reward-service` reports the Redis connection restored and job processing resuming.
8. 14:24:45Z: `sidekiq` reports reward queue depth below 500.

Service and job:
- Initial failing service: `reward-service`
- Dependency implicated by the error: `redis-primary:6379`
- Primary job in the log cascade: `RewardGiveJob`
- `sidekiq_jobs.csv` also shows `RecognitionDigestJob` failures, beginning at 14:02:36Z; these occur after the first logged Redis timeout.

Arithmetic from `sidekiq_jobs.csv`:
- `RewardGiveJob` failures: 12 jobs (`J-00001` through `J-00012`)
- `RecognitionDigestJob` failures: 4 jobs (`J-00013` through `J-00016`)
- Total listed failed jobs: `12 + 4 = 16`

Datadog query to confirm the first error:
```text
service:reward-service status:error "Redis::TimeoutError" "redis-primary:6379" @timestamp:[2026-09-03T14:01:00Z TO 2026-09-03T14:01:20Z]
```

The logs do not show:
- The root cause of the Redis timeout (for example, Redis saturation, network failure, failover, or configuration change).
- Whether Redis itself was unavailable versus unreachable from `reward-service`.
- The number of Give requests, users, companies, or rewards affected.
- Whether any reward gives were lost, duplicated, or merely delayed.
- The exact start time of the underlying Redis issue before the first logged timeout at 14:01:12Z.
- Why `RecognitionDigestJob` also failed, beyond its recorded `Redis::TimeoutError`.
feature-flag-state-summaryPASS 1.00
Plain-English question: Summarize what each feature flag controls and who has it on.
Prompt — what the model saw
Summarize the state of the listed feature flags: what each controls per the code excerpt, which companies or segments have it on, targeting rules, and any flag with no code reference or no targets. Company counts must match the export. Do not describe a flag that is not in the export.
cost $0.0876 · 20s · in 9,578 / out 1,974 tok
✓ orphans✓ no_targets✓ counts_match✓ no_invented

✓ Correct Answer (ground truth)

Plain-English answer: Recognition streaks on for 42 beta companies, redeem-flow redesign off with a 12-company target list, plus any flag with no code reference or no targets.
The answer in one line: rule = company counts must equal the export; do not describe flags absent from the export.
code_referencedrecognition_streaks_v2, points_budget_guardrails, slack_dm_nudges, redeem_flow_redesign, analytics_dashboard_v3, ms_teams_app_v2
flags{"recognition_streaks_v2": {"state": "on", "targeting_rules": "segment:beta_companies", "company_count": 42}, "points_budget_guardrails": {"state": "on", "targeting_rules": "all_companies", "company_c
flags_with_no_targetspaused_offboard_cleanup
orphan_flags_no_code_referencelegacy_give_modal, survey_boosters_q3, paused_offboard_cleanup
rulecompany counts must equal the export; do not describe flags absent from the export.
graded checksorphans · no_targets · counts_match · no_invented

Model's actual answer

show the model's full answer
| Flag | State | What it controls (code) | Targets / targeting rule | Export company count |
|---|---|---|---|---:|
| `recognition_streaks_v2` | on | Records recognition/giving activity through `StreakTracker.record(give)`. | `segment:beta_companies` | 42 |
| `points_budget_guardrails` | on | Enforces a company’s points budget through `BudgetService.new(company).enforce!(giver, points)`. | `all_companies` | 220 |
| `slack_dm_nudges` | on | Sends Slack DM nudges via `SlackDm.send_nudge(user)`. | `segment:region_na` | 87 |
| `redeem_flow_redesign` | off | Renders `RedeemV2Component`; when off, the code renders `RedeemV1Component`. | `targeted_list` | 12 |
| `analytics_dashboard_v3` | on | Initializes the v3 analytics dashboard via `AnalyticsV3.new(company)`. | `segment:tier_three` | 65 |
| `ms_teams_app_v2` | off | Installs the v2 Microsoft Teams app via `TeamsAppV2.install(company)`. | `targeted_list` | 9 |
| `legacy_give_modal` | off | No code reference in the provided excerpt. | `segment:legacy_plan` | 14 |
| `survey_boosters_q3` | on | No code reference in the provided excerpt. | `segment:legacy_plan` | 7 |
| `paused_offboard_cleanup` | off | No code reference in the provided excerpt. | No targeting rule provided; no targets. | 0 |

No company aliases are provided in the export, so individual companies cannot be identified.

Arithmetic:
- On-flag company assignments: `42 + 220 + 87 + 65 + 7 = 421`
- Off-flag company assignments: `12 + 9 + 14 + 0 = 35`
- These are flag-to-company assignments, not necessarily unique companies across flags.
nda-triagePASS 1.00
Plain-English question: Triage each NDA green, yellow, or red — and quote the clause that decides it.
Prompt — what the model saw
Triage each NDA as GREEN (standard approval), YELLOW (counsel review), or RED (full legal review). Cite the clause that drives each classification by quoting it. Catch embedded non-solicits, non-competes, missing carve-outs, and unusual term or governing law. One line of reasoning per NDA.
cost $0.0759 · 20s · in 8,769 / out 1,124 tok
✓ green✓ yellow✓ red✓ non_solicit_caught✓ clause_quoted✓ correct_labels

✓ Correct Answer (ground truth)

Plain-English answer: NDA-1 green (standard mutual terms), NDA-2 yellow for an embedded 18-month non-solicit, with the driving clause quoted for every classification.
The answer in one line: non_solicit_in = NDA-2
checksclassification_per_nda, clause_quotes_exist_in_document, non_solicit_caught, carveouts_checked
classifications{"NDA-1": {"classification": "GREEN", "driving_reason": "standard mutual NDA: 2-year term, standard carve-outs, Delaware law", "driving_clause_quote": "Carve-outs: information that (a) is or becomes p
non_solicit_inNDA-2
graded checksgreen · yellow · red · non_solicit_caught · clause_quoted · correct_labels

Model's actual answer

show the model's full answer
- NDA-1 — GREEN (standard approval): Standard mutual NDA with complete carve-outs, a two-year term, three-year survival, and Delaware governing law: “Carve-outs: information that (a) is or becomes publicly available… (e) must be disclosed by law or court order” and “Governing law: the laws of the State of Delaware, USA.”
- NDA-2 — YELLOW (counsel review): Embedded employment restriction requires review: “During the term of this Agreement and for eighteen (18) months thereafter, neither party shall solicit for employment or hire any employee of the other party with whom it came into contact under this Agreement.”
- NDA-3 — RED (full legal review): Broad non-compete, no confidentiality carve-outs, one-way obligations, five-year term, and unusual governing law/jurisdiction: “Recipient shall not, directly or indirectly, engage in or provide services to any business that competes with Discloser’s business”; “No confidentiality carve-outs are stated in this Agreement”; and “governed by… the laws of the Republic of Ireland… exclusive jurisdiction of its courts.”