← back to all models ← RevenueBench home
openai

openai/gpt-5.6-sol

Mean 0.940 · 29/40 perfect tests · $3.67 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.1115 · 58s · in 6 / out 3,873 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
- DS2+: current stage DS2, DS3, DS4, or DS5.
- Why-buys non-compliant: blank, under 15 characters, or a placeholder. `LONG(n)` is compliant.
- Missing DS1: `t_ds1` is blank.
- Regressed: an earlier-stage timestamp is later than a populated later-stage timestamp.

Results
- Overall why-buys non-compliance: 101 / 124 = 81.5%
- By owner:
  - 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%
  - Elena Sinclair: 0 DS2+ deals; percentage not applicable
- Deals with no DS1 timestamp: 0
- Deals that regressed: 0

Process fixes
1. Block advancement into DS2+ unless why-buys contains at least 15 non-placeholder characters.
2. Automatically stamp immutable stage-entry dates on every stage transition.
3. Add a weekly owner-level exception report for missing/invalid why-buys and out-of-order timestamps.
owner-resolutionPASS 1.00
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.1019 · 34s · in 6 / out 2,653 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

Deals with unmatched owner IDs: None

Deal owner IDs mapped to archived/deactivated owners: None
- Gavin Porter (1520255671) and Hugo Lindqvist (77260721) are archived but own no listed open deals.

Total pipeline by resolved owner:

- Bryce Harmon (119337721), 35 deals:
  $24,000 + $19,656 + $13,500 + $7,000 + $2,520 + $240,000 + $99,000 + $72,000 + $70,000 + $63,600 + $45,000 + $1 + $21,000 + $23,400 + $13,680 + $5,502 + $8,160 + $1 + $11,400 + $1 + $36,000 + $31,500 + $6,000 + $10,800 + $30,275 + $17,400 + $12,600 + $18,000 + $37,440 + $18,828 + $2,880 + $36,000 + $20,880 + $10,920 + $25,200 = $1,054,144

- Alex Franklin (84342457), 67 deals:
  $14,850 + $13,770 + $11,200 + $9,000 + $6,360 + $5,400 + $3,240 + $2,484 + $1,920 + $1,080 + $7,200 + $19,000 + $2,880 + $1,400 + $4,800 + $1,632 + $10,000 + $9,300 + $2,700 + $2,160 + $1,800 + $3,600 + $3,840 + $15,000 + $1,968 + $4,000 + $3,600 + $4,800 + $3,120 + $2,520 + $9,000 + $2,400 + $62,000 + $5,400 + $5,100 + $16,700 + $4,400 + $1,620 + $2,600 + $7,200 + $18,000 + $17,000 + $8,316 + $8,100 + $18,000 + $12,600 + $24,000 + $15,000 + $9,000 + $7,200 + $3,780 + $16,200 + $7,200 + $4,680 + $1,800 + $18,000 + $2,730 + $2,400 + $3,060 + $18,000 + $12,000 + $1,800 + $4,400 + $31,200 + $7,200 + $1,600 + $60,000 = $624,310

- Dana Mercer (83155923), 24 deals:
  $11,250 + $10,500 + $9,000 + $9,000 + $5,400 + $4,800 + $4,600 + $1,920 + $15,000 + $4,200 + $18,900 + $27,000 + $43,875 + $20,000 + $60,000 + $8,100 + $16,250 + $3,150 + $5,000 + $2,100 + $23,400 + $5,400 + $7,350 + $25,000 = $341,195

- Cole Ingram (83155924), 22 deals:
  $2,760 + $1,330 + $7,225.40 + $3,360 + $5,616 + $2,700 + $7,781.20 + $6,947.50 + $40,000 + $12,168 + $2,480.40 + $11,116 + $11,193 + $1,875 + $31,750 + $32,175 + $4,779.88 + $3,334.80 + $58,529.25 + $4,140 + $18,000 + $18,900 = $288,161.43

- Farid Osman (716654662), 7 deals:
  $1,249 + $1 + $1 + $1 + $2,880 + $1 + $1 = $4,134

- Elena Sinclair (701163055), 1 deal:
  $2,100 = $2,100
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.1162 · 44s · in 6 / out 3,325 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 of 67 Gong rows.

Arithmetic: 67 total Gong rows − 37 rows matched to `deals_open` = 30 orphan rows.

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

(b) Duplicate conversation keys: 0 rows.

Every row has `calls_90d = distinct_conversation_keys`; therefore, no duplicate conversation keys are indicated.

(c) DS3-or-later call coverage: 25 of 85 open deals.

Arithmetic: 25 ÷ 85 = 0.2941 = 29.4%.
snowflake-sql-trapped-catalog0.83
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.0421 · 8s · in 3 / out 415 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
SELECT
    'Cannot produce the requested per-company query from this catalog: no recognition/giving event table or giver identifier is provided, and PRODUCTION.PLG.COMPANY_COHORT_SUMMARY does not document a company identifier. M1_USERS is not documented as unique givers, and M1_GIVES cannot support a distinct-giver calculation. The redemption source documents only STATE, but no company key or event date needed to assign successful redemptions to the first calendar month as a customer.' AS MISSING_DATA;
```
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.1147 · 55s · in 6 / out 5,939 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 COMPLETENESS

Deals
- No deals extract was provided.
- Owner, stage, amount, close date, and why-buys completeness cannot be calculated.
- Pipeline amount at stake cannot be calculated or attributed to fixes.

Companies — 34 records
- Industry: 34 / 34 = 100.00%
- Employee count: 25 / 34 = 73.53%
- HQ country: 28 / 34 = 82.35%

Contacts — 52 records
- Email populated: 52 / 52 = 100.00%
- Email syntactically valid: 48 / 52 = 92.31%
- Title: 39 / 52 = 75.00%
- Persona: 37 / 52 = 71.15%

MISSING COMPANY FIELDS AND ENRICHMENT FIXES

Safe fills supported by matching enrichment rows:
- C-EC3025: employee_count blank → 400
- C-96039F: employee_count blank → 400
- C-44EA29: employee_count blank → 400
- C-D04904: employee_count blank → 400
- C-B23205: employee_count blank → 400
- C-60C75F: employee_count blank → 400
- C-7BBDFA: employee_count blank → 400
- C-50D386: employee_count blank → 400

After these fills:
- Employee count: (25 + 8) / 34 = 33 / 34 = 97.06%

Missing fields that cannot be filled from the enrichment export:
- C-93C8BF: employee_count missing; no matching enrichment row
- C-2D1F1B: hq_country missing; matching enrichment value also blank
- C-D73B89: hq_country missing; matching enrichment value also blank
- C-44EA29: hq_country missing; matching enrichment value also blank
- C-D04904: hq_country missing; matching enrichment value also blank
- C-2C60E5: hq_country missing; matching enrichment value also blank
- C-EE9FFB: hq_country missing; no matching enrichment row

No industry values are missing.

CRM–ENRICHMENT DISAGREEMENTS

Recommendation: use enrichment for industry taxonomy and country standardization because its values are more consistently formatted. Preserve the previous CRM value in audit history. The data does not establish which source is factually authoritative.

- C-66D1FC
  - industry: CRM “tech”; enrichment “Computer Software” → recommend enrichment
  - hq_country: CRM “US”; enrichment “United States” → recommend enrichment as standardized form
- C-950043
  - hq_country: CRM “US”; enrichment “United States” → recommend enrichment as standardized form
- C-EC3025
  - industry: CRM “Technology”; enrichment “Computer Software” → recommend enrichment
  - hq_country: CRM “USA”; enrichment “United States” → recommend enrichment as standardized form
- C-96039F
  - hq_country: CRM “USA”; enrichment “United States” → recommend enrichment as standardized form
- C-44EA29
  - industry: CRM “tech”; enrichment “Computer Software” → recommend enrichment
- C-92D97D
  - industry: CRM “Technology”; enrichment “Computer Software” → recommend enrichment
- C-D04904
  - industry: CRM “Technology”; enrichment “Computer Software” → recommend enrichment
- C-77A95A
  - industry: CRM “Technology”; enrichment “Computer Software” → recommend enrichment
  - hq_country: CRM “US”; enrichment “United States” → recommend enrichment as standardized form
- C-AA8DDA
  - industry: CRM “Technology”; enrichment “Computer Software” → recommend enrichment
- C-B23205
  - hq_country: CRM “US”; enrichment “United States” → recommend enrichment as standardized form
- C-E51FB7
  - hq_country: CRM “USA”; enrichment “United States” → recommend enrichment as standardized form
- C-D0662E
  - hq_country: CRM “US”; enrichment “United States” → recommend enrichment as standardized form
- C-B25F40
  - industry: CRM “Technology”; enrichment “Computer Software” → recommend enrichment
- C-60C75F
  - industry: CRM “tech”; enrichment “Computer Software” → recommend enrichment
- C-425E2A
  - industry: CRM “Tech ”; enrichment “Computer Software” → recommend enrichment
  - hq_country: CRM “USA”; enrichment “United States” → recommend enrichment as standardized form
- C-2D7423
  - hq_country: CRM “USA”; enrichment “United States” → recommend enrichment as standardized form

DUPLICATE COMPANY CLUSTERS

Company names were not provided, so name-variant matching cannot be performed. Shared-domain matching identifies two clusters.

1. acme-corp.com
   - Records: C-0A092931, C-0A092932
   - Survivor: C-0A092931, using the lowest alias as a deterministic tie-break
   - Conflict requiring review:
     - industry: C-0A092931 = “Technology”; C-0A092932 = “tech”
     - employee_count: C-0A092931 = 500; C-0A092932 = 510
     - hq_country: C-0A092931 = “US”; C-0A092932 = “USA”
   - Fix: merge records, preserve both source values in audit history, and do not choose between 500 and 510 without another source.

2. globex.io
   - Records: C-0A092933, C-0A092934
   - Survivor: C-0A092933, using the lowest alias as a deterministic tie-break
   - Conflict requiring review:
     - industry: C-0A092933 = “SaaS”; C-0A092934 = “Technology”
   - Matching values:
     - employee_count = 200
     - hq_country = “US”
   - Fix: merge records and retain the conflicting industry values for review.

INVALID EMAILS

- CT-0010: “user0@”
- CT-0080: “user0@”
- CT-0081: “user1@”
- CT-0192: “user2@”

Fix: replace only from a verified source or clear the invalid value and queue it for enrichment. No replacement email was provided.

DOMAIN MISMATCHES

- CT-0011: email domain “other-domain.com” does not match contact/company domain “66d1fc.com”

Fix: verify company affiliation or correct the email from a trusted source. The provided data does not establish which value is correct.

MISSING CONTACT FIELDS

Missing title — 13:
- CT-0000
- CT-0022
- CT-0072
- CT-0080
- CT-0081
- CT-0092
- CT-0120
- CT-0121
- CT-0122
- CT-0132
- CT-0141
- CT-0162
- CT-0170

Missing persona — 15:
- CT-0000
- CT-0022
- CT-0041
- CT-0060
- CT-0070
- CT-0081
- CT-0082
- CT-0092
- CT-0110
- CT-0132
- CT-0162
- CT-0171
- CT-0172
- CT-0180
- CT-0181

Fix: enrich or manually research these fields; no source values were provided, so none can be safely filled.

TOP 10 FIXES BY PIPELINE AMOUNT AT STAKE

Cannot be produced: the deals extract—including deal aliases, company associations, amounts, owners, stages, close dates, and why-buys—was not provided. Therefore, no fix can be ranked by pipeline amount without inventing data.
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.1450 · 83s · in 21 / out 6,563 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

Pricing — 5
- Deal-7ED004 — buyer
- Deal-7B2236 — buyer
- Deal-C33D91 — buyer
- Deal-DAFB82 — buyer
- Deal-8A119B — buyer

Competitor — 22
- Deal-F7F635 — unknown
- Deal-381C8C — unknown
- Deal-F1E8A6 — unknown
- Deal-DDAB52 — Bonusly
- Deal-ACE061 — unknown
- Deal-2D2F8D — unknown
- Deal-0F96AA — unknown
- Deal-1BCA50 — unknown
- Deal-7CC678 — unknown
- Deal-A2C349 — buyer
- Deal-C7156E — unknown
- Deal-8A0992 — buyer
- Deal-D0C698 — buyer
- Deal-EECC02 — unknown
- Deal-5AD03E — unknown
- Deal-47F1A1 — buyer
- Deal-BF2A98 — buyer
- Deal-1E7DA9 — unknown
- Deal-286F9C — Bonusly
- Deal-369281 — buyer
- Deal-9FCD0D — buyer
- Deal-64B19A — buyer

No decision — 32
- Deal-AC944F — unknown
- Deal-214060 — unknown
- Deal-13E9CF — buyer
- Deal-21B045 — unknown
- Deal-ED9AE7 — buyer
- Deal-988493 — unknown
- Deal-F308CA — unknown
- Deal-70F704 — unknown
- Deal-4664E1 — unknown
- Deal-E74A73 — buyer
- Deal-D48E0B — unknown
- Deal-583ADB — unknown
- Deal-8E27DA — buyer
- Deal-E0441F — unknown
- Deal-7CB44D — unknown
- Deal-FAC17C — buyer
- Deal-50E5D8 — buyer
- Deal-AFA56C — unknown
- Deal-413C56 — buyer
- Deal-2A292B — buyer
- Deal-D1AABF — unknown
- Deal-2BBA21 — unknown
- Deal-7FBAC6 — buyer
- Deal-386F6E — unknown
- Deal-3F86A0 — unknown
- Deal-096750 — unknown
- Deal-F325A5 — buyer
- Deal-79E61A — unknown
- Deal-AE7C4E — unknown
- Deal-DAB4F1 — unknown
- Deal-B4B50F — unknown
- Deal-5885B9 — unknown

Timing — 22
- Deal-DB0AAC — buyer
- Deal-91A056 — buyer
- Deal-29326C — unknown
- Deal-831B7B — buyer
- Deal-39E25C — buyer
- Deal-B3ABED — buyer
- Deal-B6AC09 — buyer
- Deal-E6E80A — buyer
- Deal-B038F0 — buyer
- Deal-175756 — buyer
- Deal-BB78F3 — buyer
- Deal-15DA99 — buyer
- Deal-F4AF5D — buyer
- Deal-79B7A1 — unknown
- Deal-9F176A — buyer
- Deal-5E64CE — buyer
- Deal-69CF3D — unknown
- Deal-ECBF89 — unknown
- Deal-D1A623 — unknown
- Deal-FEDBCB — buyer
- Deal-55867E — unknown
- Deal-2FEDDB — buyer

Product gap — 7
- Deal-F97C37 — Bonusly
- Deal-422BA6 — Bonusly
- Deal-242273 — Bonusly
- Deal-9048EB — Bonusly
- Deal-3618CC — Bonusly
- Deal-981AD4 — Bonusly
- Deal-DC77FE — Bonusly

Champion left — 0

Other — 2
- Deal-5DB9B0 — buyer
- Deal-ABD14C — buyer

Category-count arithmetic

5 pricing + 22 competitor + 32 no decision + 22 timing + 7 product gap + 0 champion left + 2 other = 90 deals

Side split

- Buyer: 41
- Bonusly: 9
- Unknown: 40

41 + 9 + 40 = 90 deals

Clear tag/free-text disagreements — 3

- Deal-8E27DA: tag says “Feature Request”; text says the buyer chose only a swag provider and did not want R&R currently → no decision.
- Deal-9048EB: tag says “MIA”; text explicitly reports a bad fit and multiple feature gaps → product gap.
- Deal-3618CC: tag says “Lost DM”; text says “Wanted Surveys” → product gap.

Two patterns most worth acting on

1. No decision and timing dominate: 32 + 22 = 54 of 90 deals. The recurring evidence is inactivity, deprioritization, pauses, and future reconnect dates. The actionable focus is stronger priority/timeline qualification and a structured re-engagement motion for explicitly deferred deals.

2. Competitive and product-related losses total 22 + 7 = 29 deals. All 7 explicit product-gap losses are assigned to Bonusly, involving broader offerings, integrations, points functionality, surveys, UI/UK fit, or customization. The actionable focus is product-gap prioritization plus competitive enablement tied to those documented differentiators.
pipeline-tiering0.80
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.3567 · 359s · in 69 / out 7,026 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":37,"REVIVE":18,"WATCH":50,"RISKY":36},"tier_examples":{"LOCK":["Deal-D348E1","Deal-C26D20","Deal-403845"],"ACTION":["Deal-25F752","Deal-944310","Deal-3974EB"],"BUILD":["Deal-D73B89","Deal-523604","Deal-CA7DC0"],"REVIVE":["Deal-2D1F1B","Deal-66D1FC","Deal-950043"],"WATCH":["Deal-6787C2","Deal-C9C286","Deal-332637"],"RISKY":["Deal-E53952","Deal-5408B0","Deal-9AAE5F"]},"risky_deals":["Deal-E53952","Deal-5408B0","Deal-9AAE5F","Deal-C61CF7","Deal-62D607","Deal-C6D97A","Deal-7B3B0F","Deal-F9A08A","Deal-0660B4","Deal-BA571A","Deal-FC22A3","Deal-7BBDFA","Deal-60C2C2","Deal-4A13AD","Deal-8AD4A5","Deal-15D24F","Deal-9D0060","Deal-690476","Deal-635B8E","Deal-ED725A","Deal-55164C","Deal-3BA5EA","Deal-5FDCE4","Deal-F336B6","Deal-5EED42","Deal-BA3DDC","Deal-7599B8","Deal-F9A3C1","Deal-FA32A0","Deal-547B2B","Deal-B7EBD1","Deal-A2B47C","Deal-2465CE","Deal-A5E80A","Deal-FD9F4E","Deal-499BF6"],"lock_violations":0,"pipeline_shape":"The pipeline is forecast-fragile: 3 LOCK + 11 ACTION + 37 BUILD = 51 actively supported deals, while 18 REVIVE + 50 WATCH = 68 need reactivation or monitoring; 36 RISKY deals have forecast categories unsupported by stage and/or meeting evidence. Arithmetic: 3 + 11 + 37 + 18 + 50 + 36 = 155 total deals."}
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.0537 · 15s · in 3 / out 1,355 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
[
  {
    "transcript_id": "TX-001",
    "deal_alias": "Deal-CFE7F4",
    "why_buys": [
      "Automating anniversary and birthday awards",
      "The HR team of three cannot keep up with the process manually"
    ],
    "pain_points": [
      "Awards are tracked in a spreadsheet",
      "People slip through the cracks"
    ],
    "stakeholders": [
      "Prospect (VP People)",
      "Prospect (HR Admin)"
    ],
    "budget_signal": "About $40k earmarked for engagement tools this fiscal year",
    "timeline_signal": "Ideally live before open enrollment in November",
    "competitor_mentioned": "Achievers",
    "next_step": "Security review on September 12",
    "objections": [
      "Achievers was too heavy for a team of their size",
      "SSO and audit logs are required for IT sign-off"
    ],
    "confidence": "high"
  },
  {
    "transcript_id": "TX-002",
    "deal_alias": "Deal-70BB30",
    "why_buys": [
      "Tie recognition to retention for the hourly workforce"
    ],
    "pain_points": [
      "Regretted turnover among the hourly workforce is over 30%"
    ],
    "stakeholders": [
      "Prospect (Head of Total Rewards)",
      "Prospect (CFO)"
    ],
    "budget_signal": "$25k pilot budget approved for this quarter",
    "timeline_signal": "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": "high"
  },
  {
    "transcript_id": "TX-003",
    "deal_alias": "Deal-530B50",
    "why_buys": [
      "Make recognition visible across 12 retail locations"
    ],
    "pain_points": [
      "Store managers have zero budget autonomy for on-the-spot recognition"
    ],
    "stakeholders": [
      "Prospect (People Ops Manager)"
    ],
    "budget_signal": null,
    "timeline_signal": "No rush 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 and decides anything people-related"
    ],
    "confidence": "high"
  },
  {
    "transcript_id": "TX-004",
    "deal_alias": "Deal-180D02",
    "why_buys": [
      "Consolidate three separate recognition tools into one"
    ],
    "pain_points": [
      "The company is paying for three tools",
      "None of the three tools communicate with the HRIS"
    ],
    "stakeholders": [
      "Prospect (VP People)",
      "Prospect (IT Security Lead)"
    ],
    "budget_signal": "The VP People can approve an annual price under $15k without going to the board",
    "timeline_signal": "Procurement takes a minimum of six to eight weeks",
    "competitor_mentioned": null,
    "next_step": null,
    "objections": [
      "The security review took three months for the last vendor",
      "A CFO follow-up was not confirmed"
    ],
    "confidence": "high"
  },
  {
    "transcript_id": "TX-005",
    "deal_alias": "Deal-F8767A",
    "why_buys": [
      "Automate service milestones",
      "Provide analytics on recognition equity across departments"
    ],
    "pain_points": [
      "Night-shift teams feel invisible",
      "Night-shift engagement scores are 20 points lower"
    ],
    "stakeholders": [
      "Prospect (HR Director)",
      "Prospect (People Ops Coordinator)"
    ],
    "budget_signal": "$12k approved under the engagement line",
    "timeline_signal": "Running before the January all-hands",
    "competitor_mentioned": "Nectar",
    "next_step": "Present to the exec team on October 2",
    "objections": [
      "The company is mid-pilot with Nectar, and the proposed experience would need to beat it",
      "The exec team is skeptical after a failed rollout two years ago"
    ],
    "confidence": "high"
  },
  {
    "transcript_id": "TX-006",
    "deal_alias": "Deal-EE195F",
    "why_buys": [
      "Cut the administrative time spent on service awards"
    ],
    "pain_points": [
      "The HR Manager spends five hours per month ordering and shipping plaques"
    ],
    "stakeholders": [
      "Prospect (HR Manager)"
    ],
    "budget_signal": "Budget is not the issue; time is",
    "timeline_signal": "The fiscal year resets in February, making a Q1 start 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",
      "The prospect is comparing the product against continuing to handle the process internally"
    ],
    "confidence": "high"
  }
]
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.0426 · 7s · in 3 / out 410 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: DS5/COMMIT; redlines are clean, signing page is out, and VP People said they are signing tomorrow.  
What is left: Signature.

2. Deal-403845 — $9,000  
Why close: DS5/COMMIT; Slack says the order form is already with the finance team.  
What is left: Finance approval and signature. No more specific steps are provided.

3. Deal-A2B47C — $6,360  
Why close: DS5/COMMIT; Slack confirms it is still warm and moving at a normal legal-review pace.  
What is left: Complete legal review, then signature. No timing is provided.

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.0424 · 7s · in 3 / out 497 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
Candidate assessment

1. Deal-EC3025 — Amount: not provided
   Prospect: “We need SCIM user provisioning — our security team will not approve any tool that requires manual account management.”
   Classification: Real gap
   Basis: Product docs state that SCIM user provisioning is not currently listed as supported.

2. 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.”
   Classification: Real gap
   Basis: Product docs state that ADP Workforce Now integrations are not currently listed as supported.

3. 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?”
   Classification: Plan gate
   Basis: The custom report builder exists, but only on the Enterprise tier.

4. 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.”
   Classification: Rollout/enablement issue
   Basis: Slack integration is supported on all plans; the stated problem is lack of manager training.

Excluded: Deal-36C33F. The mobile-app limitation was raised by Alex Franklin, not the prospect, so it does not count as prospect voice.

Summary: true product gaps

- Deal-EC3025 — SCIM user provisioning — Amount: not provided
- Deal-D0D6B5 — ADP Workforce Now integration — Amount: not provided

Arithmetic: 2 real gaps = 4 prospect-raised candidates − 1 plan gate − 1 rollout/enablement issue. Total associated amount cannot be calculated because no deal amounts were provided.
rep-performance 5 tests
stale-pipeline-by-rep0.67
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.1791 · 87s · in 6 / out 8,279 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
Bryce Harmon
- Deal-2D1F1B | Bryce Harmon | DS1 | $240,000 | 81 days (2026-09-05 − 2026-06-16)
- Deal-66D1FC | Bryce Harmon | DS1 | $99,000 | 16 days (2026-09-05 − 2026-08-20)
- Deal-950043 | Bryce Harmon | DS1 | $70,000 | 19 days (2026-09-05 − 2026-08-17)
- Deal-B23205 | Bryce Harmon | DS1 | $45,000 | 16 days (2026-09-05 − 2026-08-20)
- Deal-7BBDFA | Bryce Harmon | DS3 | $37,440 | 46 days (2026-09-05 − 2026-07-21)
- Deal-332637 | Bryce Harmon | DS2 | $36,000 | 9 days (2026-09-05 − 2026-08-27)
- Deal-1BEEBF | Bryce Harmon | DS1 | $31,500 | 19 days (2026-09-05 − 2026-08-17)
- Deal-A414F6 | Bryce Harmon | DS1 | $25,200 | 19 days (2026-09-05 − 2026-08-17)
- Deal-C5658B | Bryce Harmon | DS1 | $23,400 | 16 days (2026-09-05 − 2026-08-20)
- Deal-40522D | Bryce Harmon | DS3 | $21,000 | 19 days (2026-09-05 − 2026-08-17)
- Deal-C1FA6D | Bryce Harmon | DS1 | $18,000 | 16 days (2026-09-05 − 2026-08-20)
- Deal-01E193 | Bryce Harmon | DS1 | $12,600 | 8 days (2026-09-05 − 2026-08-28)
- Deal-F0EBBB | Bryce Harmon | DS3 | $11,400 | 24 days (2026-09-05 − 2026-08-12)
- Deal-927338 | Bryce Harmon | DS1 | $10,920 | 18 days (2026-09-05 − 2026-08-18)
- Deal-E25A09 | Bryce Harmon | DS1 | $6,000 | 9 days (2026-09-05 − 2026-08-27)
- Deal-C9C286 | Bryce Harmon | DS2 | $5,502 | 9 days (2026-09-05 − 2026-08-27)
- Deal-3795AD | Bryce Harmon | DS2 | $1 | 8 days (2026-09-05 − 2026-08-28)
- Deal-012CB1 | Bryce Harmon | DS1 | $1 | 23 days (2026-09-05 − 2026-08-13)

Subtotal: 18 stale deals; Σ amounts = $692,964.

Dana Mercer
- Deal-44EA29 | Dana Mercer | DS2 | $60,000 | 10 days (2026-09-05 − 2026-08-26)
- Deal-E51FB7 | Dana Mercer | DS2 | $43,875 | 12 days (2026-09-05 − 2026-08-24)
- Deal-B42F46 | Dana Mercer | DS1 | $27,000 | 19 days (2026-09-05 − 2026-08-17)
- Deal-BA3DDC | Dana Mercer | DS3 | $23,400 | 15 days (2026-09-05 − 2026-08-21)
- Deal-9DDE86 | Dana Mercer | DS2 | $20,000 | 15 days (2026-09-05 − 2026-08-21)
- Deal-215CCA | Dana Mercer | DS3 | $18,900 | 17 days (2026-09-05 − 2026-08-19)
- Deal-57887A | Dana Mercer | DS2 | $15,000 | 8 days (2026-09-05 − 2026-08-28)
- Deal-944310 | Dana Mercer | DS4 | $10,500 | 33 days (2026-09-05 − 2026-08-03)
- Deal-B7EBD1 | Dana Mercer | DS5 | $9,000 | 16 days (2026-09-05 − 2026-08-20)
- Deal-3974EB | Dana Mercer | DS4 | $9,000 | 8 days (2026-09-05 − 2026-08-28)
- Deal-F40F04 | Dana Mercer | DS2 | $8,100 | 15 days (2026-09-05 − 2026-08-21)
- Deal-7599B8 | Dana Mercer | DS3 | $7,350 | 18 days (2026-09-05 − 2026-08-18)
- Deal-87DDD1 | Dana Mercer | DS1 | $5,000 | 19 days (2026-09-05 − 2026-08-17)
- Deal-F336B6 | Dana Mercer | DS3 | $4,200 | 15 days (2026-09-05 − 2026-08-21)
- Deal-0660B4 | Dana Mercer | DS4 | $1,920 | 16 days (2026-09-05 − 2026-08-20)

Subtotal: 15 stale deals; Σ amounts = $263,245.

Alex Franklin
- Deal-CC08D1 | Alex Franklin | DS1 | $24,000 | 16 days (2026-09-05 − 2026-08-20)
- Deal-E73427 | Alex Franklin | DS3 | $18,000 | 10 days (2026-09-05 − 2026-08-26)
- Deal-885F45 | Alex Franklin | DS2 | $9,300 | 12 days (2026-09-05 − 2026-08-24)
- Deal-C2FF3C | Alex Franklin | DS1 | $8,316 | 10 days (2026-09-05 − 2026-08-26)
- Deal-3EED2C | Alex Franklin | DS2 | $7,200 | days unavailable—no engagements-table row
- Deal-0D2F7A | Alex Franklin | DS3 | $5,100 | 12 days (2026-09-05 − 2026-08-24)
- Deal-6C60D4 | Alex Franklin | DS3 | $4,800 | 12 days (2026-09-05 − 2026-08-24)
- Deal-13FEBD | Alex Franklin | DS2 | $4,680 | 12 days (2026-09-05 − 2026-08-24)
- Deal-819506 | Alex Franklin | DS1 | $4,400 | 8 days (2026-09-05 − 2026-08-28)
- Deal-9D0060 | Alex Franklin | DS3 | $3,840 | 12 days (2026-09-05 − 2026-08-24)
- Deal-690476 | Alex Franklin | DS2 | $3,600 | 18 days (2026-09-05 − 2026-08-18)
- Deal-C6D97A | Alex Franklin | DS4 | $3,240 | 8 days (2026-09-05 − 2026-08-28)
- Deal-EE195F | Alex Franklin | DS3 | $3,120 | 8 days (2026-09-05 − 2026-08-28)
- Deal-635B8E | Alex Franklin | DS3 | $2,600 | 18 days (2026-09-05 − 2026-08-18)
- Deal-6883F3 | Alex Franklin | DS1 | $2,400 | 16 days (2026-09-05 − 2026-08-20)
- Deal-4A13AD | Alex Franklin | DS3 | $2,160 | 26 days (2026-09-05 − 2026-08-10)
- Deal-F67D31 | Alex Franklin | DS2 | $1,800 | 8 days (2026-09-05 − 2026-08-28)
- Deal-5FDCE4 | Alex Franklin | DS3 | $1,600 | 12 days (2026-09-05 − 2026-08-24)
- Deal-BA571A | Alex Franklin | DS4 | $1,080 | 18 days (2026-09-05 − 2026-08-18)

Subtotal: 19 stale deals; Σ amounts = $111,236.

Cole Ingram
- Deal-D04904 | Cole Ingram | DS2 | $58,529.25 | 11 days (2026-09-05 − 2026-08-25)
- Deal-B25F40 | Cole Ingram | DS3 | $40,000 | 8 days (2026-09-05 − 2026-08-28)
- Deal-813836 | Cole Ingram | DS2 | $32,175 | 11 days (2026-09-05 − 2026-08-25)
- Deal-1BA595 | Cole Ingram | DS2 | $31,750 | 11 days (2026-09-05 − 2026-08-25)
- Deal-CFE1E8 | Cole Ingram | DS3 | $18,000 | 11 days (2026-09-05 − 2026-08-25)
- Deal-627646 | Cole Ingram | DS3 | $11,193 | 11 days (2026-09-05 − 2026-08-25)
- Deal-FF809F | Cole Ingram | DS2 | $7,781.20 | 11 days (2026-09-05 − 2026-08-25)
- Deal-AF932D | Cole Ingram | DS2 | $7,225.40 | 11 days (2026-09-05 − 2026-08-25)
- Deal-A71728 | Cole Ingram | DS2 | $6,947.50 | 11 days (2026-09-05 − 2026-08-25)
- Deal-8BC9F5 | Cole Ingram | DS2 | $5,616 | 10 days (2026-09-05 − 2026-08-26)
- Deal-175395 | Cole Ingram | DS3 | $4,779.88 | 11 days (2026-09-05 − 2026-08-25)
- Deal-481E24 | Cole Ingram | DS3 | $4,140 | 10 days (2026-09-05 − 2026-08-26)
- Deal-C7F9BF | Cole Ingram | DS2 | $3,360 | 11 days (2026-09-05 − 2026-08-25)
- Deal-342E96 | Cole Ingram | DS2 | $2,700 | 24 days (2026-09-05 − 2026-08-12)
- Deal-E568D5 | Cole Ingram | DS3 | $1,875 | 11 days (2026-09-05 − 2026-08-25)
- Deal-FD9F4E | Cole Ingram | DS5 | $1,330 | 10 days (2026-09-05 − 2026-08-26)

Subtotal: 16 stale deals; Σ amounts = $237,402.23.

Farid Osman
- Deal-8BA24E | Farid Osman | DS1 | $2,880 | 8 days (2026-09-05 − 2026-08-28)
- Deal-8FDCD2 | Farid Osman | DS1 | $1 | 15 days (2026-09-05 − 2026-08-21)

Subtotal: 2 stale deals; $2,880 + $1 = $2,881.

Elena Sinclair
- Deal-57FF13 | Elena Sinclair | DS1 | $2,100 | days unavailable—no engagements-table row

Subtotal: 1 stale deal; Σ amounts = $2,100.
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.1692 · 96s · in 6 / out 7,978 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
30-day window: 2026-08-06 through 2026-09-05, inclusive.

| Efficiency rank | Rep | Emails | Calls | Meetings | Total activities | Activity mix (email/call/meeting) | DS2 entries | Activities per DS2 |
|---:|---|---:|---:|---:|---:|---|---:|---:|
| 1 | Alex Franklin | 307 | 36 | 41 | 307 + 36 + 41 = 384 | 79.9% / 9.4% / 10.7% | 17 | 384 ÷ 17 = 22.59 |
| 2 | Bryce Harmon | 162 | 0 | 43 | 162 + 0 + 43 = 205 | 79.0% / 0.0% / 21.0% | 4 | 205 ÷ 4 = 51.25 |
| 3 | Cole Ingram | 96 | 14 | 1 | 96 + 14 + 1 = 111 | 86.5% / 12.6% / 0.9% | 2 | 111 ÷ 2 = 55.50 |
| 4 | Farid Osman | 38 | 0 | 34 | 38 + 0 + 34 = 72 | 52.8% / 0.0% / 47.2% | 1 | 72 ÷ 1 = 72.00 |
| 5 | Dana Mercer | 84 | 18 | 11 | 84 + 18 + 11 = 113 | 74.3% / 15.9% / 9.7% | 1 | 113 ÷ 1 = 113.00 |
| Unranked | Elena Sinclair | 0 | 0 | 0 | 0 + 0 + 0 = 0 | Undefined: no activities | 0 | Undefined: no DS2 entries |

Qualifying DS2 entries:

- Alex Franklin: Deal-403845, Deal-1FC049, Deal-3EED2C, Deal-7FA0C3, Deal-E531A6, Deal-5296C9, Deal-EE195F, Deal-F436DA, Deal-317E6F, Deal-D1E6C2, Deal-D9A72E, Deal-CA5E44, Deal-4F775F, Deal-898FC5, Deal-46988D, Deal-E73427, Deal-92D97D
- Bryce Harmon: Deal-25F752, Deal-D73B89, Deal-CA7DC0, Deal-1CCE5C
- Cole Ingram: Deal-42326B, Deal-1BA595
- Farid Osman: Deal-499BF6
- Dana Mercer: Deal-57887A
- Elena Sinclair: none

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

Highest-volume rep: Alex Franklin, with 384 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.1290 · 56s · in 21 / out 3,765 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
Alex Franklin — QTD Scorecard as of 2026-09-05

Bookings vs. quota
- Q3 bookings: $150,000
- Q3 quota: $200,000
- Attainment: $150,000 ÷ $200,000 = 75.0%
- Remaining to quota: $200,000 − $150,000 = $50,000
- Wins: 8

Q3 closed-won deals:
Deal-A1C3E5, Deal-F2C7D8, Deal-B7D2F4, Deal-C9E1A6, Deal-A8B4D6, Deal-D4B8C2, Deal-E6F3A9, Deal-C5D9E2.

Deal-B3E6F1 ($24,000; closed 2026-06-20) is excluded because it closed before Q3.

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

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

Rolling 90-day DS2-to-won rate
- Window: 2026-06-08 through 2026-09-05
- Deals entering DS2: 111
- Won: 8
- Rate: 8 ÷ 111 = 7.2%

QTD outcomes
- Wins: 8
- Losses: 27
- Top loss reason: Lost- Timing (1 year or more) — 13 losses
- Share of losses: 13 ÷ 27 = 48.1%

Last-30-day activity
- Emails: 807
- Calls: 112
- Meetings: 128
- Notes: 50

Coaching observations
1. Alex is $50,000 short of quota with $1,260,390 in active pipeline, but only $69,304 is in DS4–DS5 ($23,574 + $45,730). Coaching should focus on advancing qualified DS2–DS3 opportunities rather than relying on total pipeline volume.
2. The rolling DS2-to-won rate is 7.2% (8 ÷ 111), indicating substantial leakage or long cycle time after DS2. Review qualification and next-step discipline at DS2.
3. “Lost- Timing (1 year or more)” represents 48.1% of QTD losses. Tightening urgency and timing qualification earlier could reduce time spent on opportunities unlikely to close this year.
multithreading-gapPASS 1.00
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.0728 · 29s · in 6 / out 2,702 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 cutoff: 2026-09-05 − 60 days = 2026-07-07. Former contacts are excluded.

Open/closed status, deal amount, and stage are not provided. Therefore, I cannot verify which deals are open or determine the most valuable persona based on stage. Assuming every listed deal is open, these 11 deals are flagged:

| Deal | Flag / active-contact arithmetic | Amount | Stage | Personas present | Personas missing | Most valuable persona to add | On-file unengaged contact who fits a missing persona |
|---|---|---|---|---|---|---|---|
| Deal-EC3025 | Single-threaded: 1 active = CT-047C54; CT-F2C1AE excluded as former | Missing | Missing | champion | economic buyer, HR admin, IT security, finance | Cannot determine—stage missing | CT-6827DB, Chief People Officer, economic buyer |
| Deal-92D97D | Single-threaded: 1 active = CT-01F5B4; CT-A902AE excluded because 2026-06-01 < 2026-07-07 | Missing | Missing | HR admin | economic buyer, champion, IT security, finance | Cannot determine—stage missing | None on file |
| Deal-50D386 | Under-threaded: 2 active = CT-AA41B2 + CT-B9C35B | Missing | Missing | champion, HR admin | economic buyer, IT security, finance | Cannot determine—stage missing | CT-A1C4B3, Chief People Officer, economic buyer |
| Deal-D0D6B5 | Under-threaded: 3 active, but all 3 are champion | Missing | Missing | champion | economic buyer, HR admin, IT security, finance | Cannot determine—stage missing | CT-1FA4DB, Chief People Officer, economic buyer |
| Deal-5BFE3B | Under-threaded: 2 active = CT-57123B + CT-5CE757; both are champion | Missing | Missing | champion | economic buyer, HR admin, IT security, finance | Cannot determine—stage missing | None on file |
| Deal-36C33F | Single-threaded: 1 active = CT-4FE556; CT-405B45 and CT-86B22F excluded as former | Missing | Missing | IT security | economic buyer, champion, HR admin, finance | Cannot determine—stage missing | CT-1DB73E, Chief People Officer, economic buyer |
| Deal-885F45 | Under-threaded: 2 active = CT-51C81E + CT-D9A0E8 | Missing | Missing | economic buyer, champion | HR admin, IT security, finance | Cannot determine—stage missing | CT-B3F25D, IT Security Lead, IT security |
| Deal-FCBE5B | Single-threaded: 1 active = CT-4A5317 | Missing | Missing | champion | economic buyer, HR admin, IT security, finance | Cannot determine—stage missing | None on file |
| Deal-5408B0 | Under-threaded: 2 active = CT-D33AE4 + CT-8742FD | Missing | Missing | champion, HR admin | economic buyer, IT security, finance | Cannot determine—stage missing | CT-07FA76, Chief People Officer, economic buyer |
| Deal-C6D97A | Under-threaded: 3 active, but all 3 are champion | Missing | Missing | champion | economic buyer, HR admin, IT security, finance | Cannot determine—stage missing | None on file |
| Deal-F9A08A | Single-threaded: 1 active = CT-931B10; CT-913581 excluded because 2026-06-20 < 2026-07-07 | Missing | Missing | champion | economic buyer, HR admin, IT security, finance | Cannot determine—stage missing | 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.0611 · 17s · in 6 / out 1,464 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
1. First-five-minute lead

- Customer outcome story: 8/10 calls (80%) — Deal-D348E1, Deal-5408B0, Deal-547B2B, Deal-C61CF7, Deal-60C2C2, Deal-EDC141, Deal-D9A12F, Deal-84DBA6.
  > “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.”
- Agenda: 1/10 (10%) — Deal-403845.
  > “I put together a short agenda — security review first, then pricing.”
- Pricing: 1/10 (10%) — Deal-1E2498.
  > “You asked for straight pricing last time, so let's start there.”
- In Deal-C61CF7, the rep also proactively positioned against Workhuman at minute 2.

2. Three most common objections and handling

- Budget locked: 4/10 calls (40%) — Deal-D348E1, Deal-547B2B, Deal-60C2C2, Deal-84DBA6. He reframes the purchase around turnover savings and finance approval.
  > “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.”
- Timing/open-enrollment workload: 3/10 calls (30%) — Deal-5408B0, Deal-C61CF7, Deal-D9A12F. He proposes a limited 90-day pilot to create data before planning.
  > “Makes sense. What if we scope a 90-day pilot with one department so you have internal data before next quarter's planning?”
- Existing spreadsheet and gift-card process: 3/10 calls (30%) — Deal-403845, Deal-EDC141, Deal-1E2498. He differentiates through 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.”

3. Concrete next-step rate

7 calls with an agreed date, time, and attendee ÷ 10 total calls = 70%.

Agreed: Deal-D348E1, Deal-5408B0, Deal-547B2B, Deal-C61CF7, Deal-60C2C2, Deal-D9A12F, Deal-1E2498.  
Not agreed: Deal-403845, Deal-EDC141, Deal-84DBA6.

> “Yes, Thursday at 2pm works — send the invite and I'll bring our HRIS manager.”

4. 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.”

Workhuman was raised by the rep, not a prospect.

Coaching notes

1. Preserve the outcome-led opening, but replace the repeated retailer story with discovery tied to each prospect’s situation; 8/10 calls use exactly the same opener.
2. When prospects defer to a committee or express no urgency, do not end with acknowledgment alone. Diagnose decision criteria and secure a concrete follow-up, since all three calls without an agreed next step ended this way.
reporting-analytics 5 tests
q3-weighted-forecastPASS 1.00
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.0953 · 33s · in 6 / out 4,116 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

Only deals closing from 2026-07-01 through 2026-09-30 are included.

| Forecast category | Deal count | Total amount | Forecast weight | Weighted amount |
|---|---:|---:|---:|---:|
| COMMIT | 7 | $44,729.00 | 100% | $44,729.00 |
| BEST_CASE | 24 | $203,565.00 | 35% | $71,247.75 |
| PIPELINE | 23 | $201,637.40 | 0% | $0.00 |

COMMIT arithmetic:

$11,200 + $9,000 + $9,000 + $6,360 + $5,400 + $2,520 + $1,249 = $44,729

BEST_CASE arithmetic:

$38,935 + $24,000 + $19,656 + $16,250 + $11,116 + $10,800 + $10,500 + $9,890 + $9,720 + $9,000 + $7,200 + $3,840 + $3,780 + $3,600 + $3,240 + $3,150 + $3,120 + $3,060 + $2,916 + $2,760 + $2,484 + $2,100 + $1,920 + $528 = $203,565

Weighted forecast:

($44,729 × 100%) + ($203,565 × 35%) + ($201,637.40 × 0%)  
= $44,729 + $71,247.75 + $0  
= **$115,976.75**

## Top 5 BEST_CASE deals inside Q3

| Rank | Deal | Amount | Close date |
|---:|---|---:|---|
| 1 | Deal-2D7423 | $38,935 | 2026-09-30 |
| 2 | Deal-25F752 | $24,000 | 2026-09-25 |
| 3 | Deal-E53952 | $19,656 | 2026-09-30 |
| 4 | Deal-5EED42 | $16,250 | 2026-09-30 |
| 5 | Deal-FA32A0 | $11,116 | 2026-09-25 |

## Excluded for being outside Q3

**32 deals totaling $227,575.00**, all with close dates after 2026-09-30:

| Deal | Category | Amount | Close date |
|---|---|---:|---|
| Deal-E51FB7 | PIPELINE | $43,875 | 2026-10-01 |
| Deal-B936FE | PIPELINE | $18,000 | 2026-10-09 |
| Deal-D9A12F | PIPELINE | $17,000 | 2026-10-15 |
| Deal-D348E1 | COMMIT | $13,770 | 2026-10-15 |
| Deal-4062CF | PIPELINE | $10,800 | 2026-10-15 |
| Deal-293AF3 | PIPELINE | $9,000 | 2026-10-09 |
| Deal-034D49 | PIPELINE | $9,000 | 2026-10-15 |
| Deal-E0ADD8 | PIPELINE | $7,920 | 2026-10-15 |
| Deal-9F2E43 | PIPELINE | $7,690 | 2026-10-08 |
| Deal-FCBE5B | PIPELINE | $7,500 | 2026-10-07 |
| Deal-712010 | PIPELINE | $7,200 | 2026-10-15 |
| Deal-6691E0 | PIPELINE | $5,700 | 2026-10-15 |
| Deal-C61CF7 | BEST_CASE | $5,400 | 2026-10-09 |
| Deal-600CD9 | PIPELINE | $5,400 | 2026-10-02 |
| Deal-A92065 | PIPELINE | $5,400 | 2026-10-15 |
| Deal-1D532E | PIPELINE | $5,400 | 2026-10-15 |
| Deal-48B656 | BEST_CASE | $5,160 | 2026-10-15 |
| Deal-E531A6 | PIPELINE | $4,800 | 2026-10-15 |
| Deal-D1E6C2 | PIPELINE | $4,400 | 2026-10-09 |
| Deal-D9E112 | PIPELINE | $4,300 | 2026-10-09 |
| Deal-5AD94B | PIPELINE | $4,000 | 2026-10-15 |
| Deal-901332 | BEST_CASE | $3,600 | 2026-10-15 |
| Deal-47AE31 | BEST_CASE | $3,600 | 2026-10-09 |
| Deal-15D24F | BEST_CASE | $3,600 | 2026-10-09 |
| Deal-766C74 | PIPELINE | $3,300 | 2026-10-14 |
| Deal-ED725A | BEST_CASE | $2,400 | 2026-10-08 |
| Deal-8AD4A5 | BEST_CASE | $1,800 | 2026-10-07 |
| Deal-D7E999 | PIPELINE | $1,800 | 2026-10-15 |
| Deal-ED13B0 | PIPELINE | $1,680 | 2026-10-09 |
| Deal-5FDCE4 | BEST_CASE | $1,600 | 2026-10-01 |
| Deal-7FA0C3 | PIPELINE | $1,400 | 2026-10-01 |
| Deal-F5A622 | BEST_CASE | $1,080 | 2026-10-08 |

Excluded-total arithmetic:

$185,565 PIPELINE + $28,240 BEST_CASE + $13,770 COMMIT = **$227,575**

## Data quality

Owner is blank on 85 of 86 deals, preventing reliable ownership and accountability analysis. The `why_buys_chars` value is zero on 72 of 86 deals, indicating largely missing qualification evidence. Four deals remained open despite close dates before the 2026-09-05 extraction date, suggesting stale close dates. Stage/category combinations such as DS1 COMMIT and DS5 BEST_CASE indicate possible forecast-category or stage-governance problems.
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.1018 · 38s · in 6 / out 3,540 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
24-month retention by first-month activation signals:

| Cohort | Cohort size | Retained (`active`) | Retention rate |
|---|---:|---:|---:|
| Both signals: `m1_users >= 5` and `m1_redemptions >= 1` | 47 | 31 | 31 ÷ 47 = **66.0%** |
| Givers-only: `m1_users >= 5` and `m1_redemptions = 0` | 49 | 23 | 23 ÷ 49 = **46.9%** |
| Redemption-only: `m1_users < 5` and `m1_redemptions >= 1` | 29 | 9 | 9 ÷ 29 = **31.0%** |
| Neither: `m1_users < 5` and `m1_redemptions = 0` | 95 | 38 | 38 ÷ 95 = **40.0%** |

Total denominator: 47 + 49 + 29 + 95 = **220 companies**.

Excluded: **0 companies**. Every company has the required first-month signal fields and `current_status`, and the extract states all companies are at least 25 months old. `active` was counted as retained; all other statuses were counted as not retained.

Hypothesis result: **Supported descriptively.** The both-signals cohort retained at **66.0%**, versus **46.9%** for givers-only, **31.0%** for redemption-only, and **40.0%** for neither.

Single signal with the largest retention lift:
- Givers-only versus neither: 46.9% − 40.0% = **+6.9 percentage points**
- Redemption-only versus neither: 31.0% − 40.0% = **−9.0 percentage points**

Therefore, **5+ unique givers is the single signal with the largest positive retention lift**.

This proves a descriptive association within this 2023 extract: companies showing both signals had the highest observed 24-month retention. It does **not** prove causality, statistical significance, or that the result generalizes beyond this cohort; other company characteristics or selection effects could explain the differences.
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.0788 · 31s · in 6 / out 3,080 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

Sign convention: Variance = CRM ARR − active billing ARR.

Totals
- CRM ARR: $603,581.76
- Billing ARR: $50,394.94 MRR × 12 = $604,739.28
- Variance: $603,581.76 − $604,739.28 = -$1,157.52

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

Mismatched accounts

| Company alias | CRM ARR | Billing ARR | Variance | Bucket | Suggested owner |
|---|---:|---:|---:|---|---|
| C-0C8323BF | $4,905.24 | $0.00 | +$4,905.24 | Status mismatch: billing cancelled | CRM/RevOps |
| C-0DC4FB8C | $8,253.24 | $0.00 | +$8,253.24 | Status mismatch: billing cancelled | CRM/RevOps |
| C-0D66DF9E | $23,200.00 | $1,932.00 × 12 = $23,184.00 | +$16.00 | Rounding | CRM/RevOps |
| C-14D70CE0 | $18,200.00 | $1,515.00 × 12 = $18,180.00 | +$20.00 | Rounding | CRM/RevOps |
| C-0D5BBE3A | $16,497.24 | $0.00 | +$16,497.24 | Missing billing record | Billing Operations |
| C-21629AA4 | $0.00 | $2,370.77 × 12 = $28,449.24 | -$28,449.24 | Missing CRM record | CRM/RevOps |
| C-0F7269D7 | $24,396.00 | $2,233.00 × 12 = $26,796.00 | -$2,400.00 | Other; cause not provided | CRM/RevOps and Billing Operations |

Non-12-month term violations

| Subscription | Company alias | Term | Violation | Suggested owner |
|---|---|---:|---|---|
| SUB-0002 | C-1794A52C | 24 months | `cf_agreement_end_date` is blank | Billing Operations |
| SUB-0019 | C-22170CA1 | 36 months | `cf_agreement_end_date` is blank | Billing Operations |
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.0674 · 19s · in 6 / out 1,835 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 prior | Absolute change | Relative change | Direction |
|---|---:|---:|---:|---:|---|
| Giving rate | 0.602713 | 0.602297 | +0.000417 | +0.069% | Up |
| Redemptions per user | 1.730163 | 1.729983 | +0.000180 | +0.010% | Up |
| 1:1 meetings engagement | 0.447177 | 0.446887 | +0.000290 | +0.065% | Up |
| Pulse check engagement | 0.508610 | 0.600587 | −0.091977 | −15.314% | Down |

Arithmetic: each monthly value is the unweighted mean across 30 companies. Absolute change = August − July. Relative change = (August − July) ÷ July × 100.

Pulse check engagement had the largest relative move. The `enterprise` size_band drove it: 0.549980 → 0.274280; absolute change = −0.275700; relative change = −0.275700 ÷ 0.549980 × 100 = −50.129%. For comparison, `smb` moved −0.225% and `mid_market` +0.211%. The `plan_tier` data does not identify a driver because every company is `tier_three`.
rewards-ytd-sectionPASS 1.00
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.1497 · 13s · in 6 / out 591 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
Redemption section — through 2026-08

Last completed month: 2026-08

- Redemption count: 378
- Spend: $27,846.00
- Unique redeemers: 235
- Redemptions per redeemer: 378 ÷ 235 = 1.6085, or 1.61

Provider mix by spend:
- custom: $10,873.00 ÷ $27,846.00 = 39.05%
- Tremendous: $8,505.00 ÷ $27,846.00 = 30.54%
- Snappy: $5,238.00 ÷ $27,846.00 = 18.81%
- TangoCard: $3,230.00 ÷ $27,846.00 = 11.60%
- Total: 39.05% + 30.54% + 18.81% + 11.60% = 100.00%

Top 5 countries by redemption count:
1. US: 244
2. CA: 24
3. AU: 21
4. GB: 17
5. NL: 17
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.0666 · 25s · in 6 / out 2,170 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
Eligibility requires all three rules: health score <60, churn-save eligible amount >$0, and renewal within 120 days of 2026-09-05 (through 2027-01-03).

Qualified accounts

| Account | Amount at stake | Best-fit play | Justifying signal |
|---|---:|---|---|
| C-0F6C0F34 | $49,707.00 | Executive touch | `champion_active=false`; usage is growing, so lack of an active champion is the clearest risk signal. |
| C-0B827671 | $25,365.00 | Usage revival | `usage_trend_3m=declining`; only 113 of 202 seats are used (113 ÷ 202 = 55.9%). |
| C-0B360C78 | $35,748.00 | Commercial concession | Health is 57 with renewal in 53 days, despite growing usage and an active champion; no usage- or champion-led intervention is indicated. |
| C-0B0F1BAB | $5,494.00 | Executive touch | `champion_active=false`; renewal is in 18 days. |
| C-0CA21961 | $16,829.00 | Usage revival | Only 84 of 325 seats are used (84 ÷ 325 = 25.8%); usage is flat. |
| C-0E9C27D1 | $41,235.00 | Commercial concession | Health is 39 with renewal in 19 days, while 134 of 157 seats are used (85.4%) and the champion is active; adoption and champion signals do not support the other plays. |
| C-0CEF69FD | $32,621.00 | Executive touch | `champion_active=false`; usage is growing, making executive relationship coverage the clearer need. |
| C-0D3278C7 | $17,602.00 | Usage revival | `usage_trend_3m=declining`; only 126 of 380 seats are used (126 ÷ 380 = 33.2%). |

Total amount at stake:

$49,707 + $25,365 + $35,748 + $5,494 + $16,829 + $41,235 + $32,621 + $17,602 = $224,601.00

The files document eligibility rules but do not document play-assignment rules. The play selections above are therefore best fits based strictly on the supplied usage, seat-utilization, champion, health, and renewal signals.

At risk but not qualified

| Account | Why it does not qualify |
|---|---|
| C-0BC71BDD | Health 55 and renewal in 52 days, but `churn_save_eligible_amount=$0.00`, failing R2. |
| C-0BA71F12 | Health 52 and eligible amount $6,824.00, but renewal is 218 days after the snapshot, failing R3. |
| C-0F6694C3 | Health 43, but eligible amount is $0.00 and renewal is 197 days away, failing R2 and R3. |
| C-0BE96399 | Health 54 and renewal in 54 days, but eligible amount is $0.00, failing R2. |
| C-0F876796 | Health 47 and eligible amount $19,958.00, but renewal is 154 days away, failing R3. |
| C-0FCCD2DF | Health 43, but eligible amount is $0.00 and renewal is 230 days away, failing R2 and R3. |
| C-10A56B0F | Health 54 and renewal in 98 days, but 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.0477 · 15s · in 6 / out 735 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
- 150 licensed seats / 400 employees = 37.5% coverage.

Usage health
- Monthly active users increased every month, from 88 in March to 126 in August.
- Growth: 126 − 88 = 38 users, or 38 / 88 = 43.2%; August utilization was 126 / 150 = 84.0% of licensed seats.

Expansion headroom
- Current rate: $9,000 ARR / 150 seats = $60 per seat annually.
- Seat headroom: 400 − 150 = 250 seats.
- ARR headroom: 250 × $60 = $15,000 ARR.
- Full coverage ARR: 400 × $60 = $24,000.

Reply and buying authority
- Maria S., People Operations Coordinator, replied.
- She explicitly said she is not the purchasing decision-maker.

Right buyer
- Dana R., VP People. Maria S. identified Dana R. as responsible for budget and seat expansion.

Reply email

Hi Maria,

Thanks for the context—and great to hear the team loves Bonusly. Monthly active users increased from 88 in March to 126 in August, so it makes sense that Dana has been asking about usage.

An introduction to Dana R. would be very helpful. I can share the usage trend and discuss whether your current 150-seat allocation still fits the team’s needs. No pressure to make changes; the goal would simply be to give her the numbers and understand what she’s considering.

Thanks again for offering to connect us.

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.0486 · 10s · in 6 / out 774 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 — Mid-onboarding call prep

Complete
- Slack integration connected: 2026-08-12
- Allowance set: 2026-08-13
- Admins added: 2
- First recognition given: 2026-08-15 at 14:22

Not complete
- HRIS integration: no completion date provided
- First redemption: no redemption date provided

Early engagement signals
- Active givers increased from 3 on 2026-08-11 to 15 on 2026-09-04.
- Increase: 15 − 3 = 12 active givers
- Percentage increase: (12 ÷ 3) × 100 = 400%
- First 7-day average: (3 + 3 + 4 + 4 + 5 + 4 + 7) ÷ 7 = 30 ÷ 7 = 4.3 active givers
- Last 7-day average: (11 + 13 + 13 + 15 + 15 + 15 + 15) ÷ 7 = 97 ÷ 7 = 13.9 active givers

Three things to cover on the call
1. Identify what is blocking the HRIS integration and agree on next steps.
2. Review the redemption process and address why no first redemption is recorded.
3. Review the growth in active givers and discuss how to sustain or broaden early 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.0969 · 40s · in 6 / out 4,169 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
Window: 2026-09-05–2026-12-04

Date policy: Use Chargebee for multi-year contracts because ChurnZero multi-year dates are known to be wrong. Where dates agree, both systems support the date.

| Company | CSM | ARR | Date used | Seat utilization | 3-month usage trend (Jun→Jul→Aug) | Risk | Evidence |
|---|---|---:|---|---:|---|---|---|
| C-0B7D2C30 | Dana Mercer | $65,901 | 2026-09-15 (Chargebee) ⚠ | 274 ÷ 476 = 57.6% | 97→94→84; -13 (-13.4%) | High | Moderate utilization and a 13.4% three-month usage decline indicate material adoption risk. |
| C-0BCDB8C2 | Cole Ingram | $54,427 | 2026-09-18 (Chargebee) ⚠ | 232 ÷ 424 = 54.7% | 127→118→110; -17 (-13.4%) | High | Utilization is 54.7% and usage declined 13.4% over three months. |
| C-0D2AB865 | Elena Sinclair | $38,022 | 2026-09-22 (Chargebee) ⚠ | 250 ÷ 407 = 61.4% | 125→117→109; -16 (-12.8%) | High | Usage declined every month and fell 12.8% overall despite 61.4% seat utilization. |
| C-0BBE3E60 | Dana Mercer | $30,993 | 2026-09-26 (Chargebee) ⚠ | 74 ÷ 114 = 64.9% | 39→35→33; -6 (-15.4%) | High | The 15.4% usage decline is the steepest in the renewal group. |
| C-0F5D2323 | Cole Ingram | $90,647 | 2026-09-29 (Chargebee) ⚠ | 111 ÷ 390 = 28.5% | 20→21→18; -2 (-10.0%) | High | Only 28.5% of seats are utilized and usage declined 10.0%. |
| C-0EC6999D | Elena Sinclair | $79,419 | 2026-10-03 (both) | 31 ÷ 112 = 27.7% | 17→16→15; -2 (-11.8%) | High | The combination of 27.7% utilization and an 11.8% usage decline creates severe adoption risk. |
| C-0B20DB64 | Dana Mercer | $21,770 | 2026-10-07 (both) | 214 ÷ 378 = 56.6% | 294→298→294; 0 (0.0%) | Medium | Usage is stable, but only 56.6% of contracted seats are utilized. |
| C-0BBC4E7A | Cole Ingram | $56,374 | 2026-10-10 (both) | 228 ÷ 337 = 67.7% | 142→141→139; -3 (-2.1%) | Medium | Utilization is 67.7% and usage has declined slightly for two consecutive months. |
| C-0FD551AB | Elena Sinclair | $48,815 | 2026-10-14 (both) | 210 ÷ 376 = 55.9% | 123→122→126; +3 (+2.4%) | Medium | Usage increased overall, but 55.9% seat utilization leaves meaningful unused capacity. |
| C-0F9F8F13 | Dana Mercer | $46,230 | 2026-10-18 (both) | 199 ÷ 352 = 56.5% | 185→185→182; -3 (-1.6%) | Medium | Utilization is only 56.5%, while usage was flat and then declined modestly. |
| C-0BC34584 | Cole Ingram | $16,740 | 2026-10-22 (both) | 327 ÷ 494 = 66.2% | 104→104→106; +2 (+1.9%) | Medium | Usage is slightly positive, but one-third of seats remain unutilized. |
| C-0B7A7546 | Elena Sinclair | $35,062 | 2026-10-25 (both) | 182 ÷ 205 = 88.8% | 64→65→63; -1 (-1.6%) | Low | High 88.8% seat utilization offsets the small 1.6% usage decline. |
| C-0B369871 | Dana Mercer | $85,128 | 2026-10-29 (both) | 317 ÷ 422 = 75.1% | 326→330→333; +7 (+2.1%) | Low | Utilization is 75.1% and usage increased in each of the last three months. |
| C-0B144C78 | Cole Ingram | $30,899 | 2026-11-02 (both) | 169 ÷ 224 = 75.4% | 101→101→106; +5 (+5.0%) | Low | Utilization is 75.4% and usage increased 5.0%. |
| C-0FC4DBB8 | Elena Sinclair | $94,732 | 2026-11-05 (both) | 356 ÷ 464 = 76.7% | 189→191→193; +4 (+2.1%) | Low | Utilization is 76.7% and usage increased consistently. |
| C-0D5BBE3A | Dana Mercer | $39,740 | 2026-11-09 (both) | 85 ÷ 102 = 83.3% | 88→90→91; +3 (+3.4%) | Low | Strong 83.3% utilization is supported by consistent usage growth. |
| C-0FB9D5AF | Cole Ingram | $63,158 | 2026-11-13 (both) | 144 ÷ 199 = 72.4% | 173→173→176; +3 (+1.7%) | Low | Utilization exceeds 70% and usage is stable to increasing. |
| C-0B344485 | Elena Sinclair | $64,384 | 2026-11-16 (both) | 224 ÷ 287 = 78.0% | 238→240→244; +6 (+2.5%) | Low | Utilization is 78.0% and usage increased in both monthly intervals. |
| C-0CB2C1B4 | Dana Mercer | $40,628 | 2026-11-20 (both) | 386 ÷ 473 = 81.6% | 47→48→49; +2 (+4.3%) | Low | Strong 81.6% seat utilization and 4.3% usage growth support renewal. |
| C-22170CA1 | Cole Ingram | $45,646 | 2026-11-24 (both) | 251 ÷ 294 = 85.4% | 143→148→146; +3 (+2.1%) | Low | Utilization is 85.4% and usage remains 2.1% above June despite an August dip. |

Date disagreements

- C-0B7D2C30: ChurnZero 2026-09-10 vs. Chargebee 2026-09-15; use Chargebee because the contract is multi-year.
- C-0BCDB8C2: ChurnZero 2027-09-18 vs. Chargebee 2026-09-18; use Chargebee because the contract is multi-year.
- C-0D2AB865: ChurnZero 2026-09-10 vs. Chargebee 2026-09-22; use Chargebee because the contract is multi-year.
- C-0BBE3E60: ChurnZero 2027-09-26 vs. Chargebee 2026-09-26; use Chargebee because the contract is multi-year.
- C-0F5D2323: ChurnZero 2026-09-10 vs. Chargebee 2026-09-29; use Chargebee because the contract is multi-year.

Totals

- Total ARR renewing: $65,901 + $54,427 + $38,022 + $30,993 + $90,647 + $79,419 + $21,770 + $56,374 + $48,815 + $46,230 + $16,740 + $35,062 + $85,128 + $30,899 + $94,732 + $39,740 + $63,158 + $64,384 + $40,628 + $45,646 = $1,048,715.
- ARR at risk (High + Medium): $359,409 High + $189,929 Medium = $549,338.
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.0704 · 23s · in 6 / out 1,995 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
Broad patterns — ranked by ARR exposure

1. HRIS provisioning/sync failures
- Count: 12
- Share: 12 ÷ 80 = 15.0%
- Distinct accounts: 3
- ARR affected: $30,000 + $36,000 + $48,000 = $114,000
- Example tickets: IC-460059, IC-460062
- Recommendation: Prioritize HRIS sync reliability and add alerts for skipped provisioning events and silent log failures.

2. Redemption and gift-card failures
- Count: 18
- Share: 18 ÷ 80 = 22.5%
- Distinct accounts: 7
- ARR affected: $8,900 + $10,700 + $9,600 + $8,700 + $11,000 + $9,600 + $10,300 = $68,800
- Example tickets: IC-460025, IC-460024
- Recommendation: Investigate checkout failures end-to-end and prevent point deductions until gift-card fulfillment succeeds.

3. Recognition points not posting
- Count: 20
- Share: 20 ÷ 80 = 25.0%
- Distinct accounts: 9
- ARR affected: $3,500 + $4,500 + $2,700 + $3,400 + $4,200 + $2,900 + $2,500 + $2,900 + $4,500 = $31,100
- Example tickets: IC-460004, IC-460016
- Recommendation: Audit recognition-to-balance processing and add reconciliation for delivered recognitions with missing points.

4. Slack integration/command failures
- Count: 14
- Share: 14 ÷ 80 = 17.5%
- Distinct accounts: 4
- ARR affected: $4,400 + $5,400 + $3,900 + $5,200 = $18,900
- Example tickets: IC-460041, IC-460049
- Recommendation: Stabilize Slack authentication, sync-toggle persistence, and slash-command execution.

Single-account noise — ranked by ARR exposure

5. Billing seat-count/tier errors
- Count: 16
- Share: 16 ÷ 80 = 20.0%
- Distinct accounts: 1
- ARR affected: $52,000
- Account: C-0E9C27D1
- Example tickets: IC-460071, IC-460078
- Recommendation: Escalate an account-specific billing correction and audit C-0E9C27D1’s seat-count and renewal-tier configuration.
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.0550 · 18s · in 6 / out 1,081 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
Using one point per exact field match:

1 (tie). C-11C31562 — 3/4 = 75%
   - Size band: Mid-Market
   - Use case: employee_recognition
   - Region: NA-West
   - Industry differs: Manufacturing vs. Technology

1 (tie). C-64171065 — 3/4 = 75%
   - Industry: Technology
   - Size band: Mid-Market
   - Use case: employee_recognition
   - Region differs: NA-East vs. NA-West

1 (tie). C-A13C193D — 3/4 = 75%
   - Industry: Technology
   - Size band: Mid-Market
   - Region: NA-West
   - Use case differs: retention vs. employee_recognition

Arithmetic: 3 exact matches ÷ 4 comparison fields × 100 = 75% each. All three have public case studies.
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.0865 · 45s · in 9 / out 3,503 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: March–August 2026

Paid channels

| Channel | Spend | SQMs | SQOs | Cost/SQM | Cost/SQO | SQM→SQO | 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 |
| Total | $87,000 | 77 | 31 | $1,129.87 | $2,806.45 | 40.3% | $876,000 | $10.07 |

Arithmetic:

- paid_search spend = 6 × $6,000 = $36,000
  - Cost/SQM = $36,000 ÷ 40 = $900
  - Cost/SQO = $36,000 ÷ 18 = $2,000
  - SQM→SQO = 18 ÷ 40 = 45.0%
  - Pipeline = 18 × $40,000 = $720,000
  - Pipeline/$ = $720,000 ÷ $36,000 = $20.00

- linkedin_ads spend = 6 × $4,000 = $24,000
  - Cost/SQM = $24,000 ÷ 25 = $960
  - Cost/SQO = $24,000 ÷ 8 = $3,000
  - SQM→SQO = 8 ÷ 25 = 32.0%
  - Pipeline = 8 × $12,000 = $96,000
  - Pipeline/$ = $96,000 ÷ $24,000 = $4.00

- paid_social spend = 6 × $3,000 = $18,000
  - Zero SQMs; cost/SQM, cost/SQO, and conversion rate are undefined
  - Pipeline/$ = $0 ÷ $18,000 = $0.00

- webinars spend = 6 × $1,500 = $9,000
  - Cost/SQM = $9,000 ÷ 12 = $750
  - Cost/SQO = $9,000 ÷ 5 = $1,800
  - SQM→SQO = 5 ÷ 12 = 41.7%
  - Pipeline = 5 × $12,000 = $60,000
  - Pipeline/$ = $60,000 ÷ $9,000 = $6.67

Organic channels

| Channel | Volume | SQOs | SQO rate | Pipeline |
|---|---:|---:|---:|---:|
| organic_search | 30 | 10 | 33.3% | $90,000 |
| referral | 15 | 6 | 40.0% | $48,000 |
| Total organic | 45 | 16 | 35.6% | $138,000 |

Arithmetic:

- organic_search: 10 ÷ 30 = 33.3%; 10 × $9,000 = $90,000
- referral: 6 ÷ 15 = 40.0%; 6 × $8,000 = $48,000
- Total organic: 16 ÷ 45 = 35.6%; $90,000 + $48,000 = $138,000

Data-quality flags — SQO date precedes SQM date:

- CT-000044: SQM 2026-07-23; SQO 2026-07-18
- CT-000041: SQM 2026-06-14; SQO 2026-06-09

These rows are included in the reported metrics because no exclusion rule was provided.

Recommendation: Reallocate paid_social’s $18,000 because it produced zero SQMs. Prioritize paid_search, which has the highest pipeline per dollar ($20.00) and the largest paid sample (40 SQMs, 18 SQOs). A smaller test allocation to webinars is also supportable because it has the lowest cost/SQO ($1,800), but its sample is only 12 SQMs and 5 SQOs. Consider reducing linkedin_ads before webinars because linkedin_ads produced only $4.00 of pipeline per dollar.

Confidence: Moderate. paid_search has the strongest supporting sample, but webinars and linkedin_ads have small SQO samples, and two linkedin_ads records contain invalid date sequencing. paid_social’s zero-SQM result is clear for this period, but the data provides no campaign-level detail explaining why.
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.0665 · 24s · in 6 / out 2,261 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
# Battlecard: Rivally

## One-line positioning
Points-based employee recognition with an engagement-survey add-on, emphasizing distributed European teams and multi-language support. [S02, S06, S12]

## Pricing
- Current list price: Recognition Starter is $7/user/month with annual billing, dated 2026-08-12. [S17]
- Deal evidence: an 800-seat prospect reported a $7/user/month list price and a 15% discount for a three-year term, dated 2026-08-14. [S18]
- Conflict: the public price was previously $5/user/month on 2026-04-01, while a 500-seat prospect reported a $6.50/user/month annual quote on 2026-06-02. [S08, S13]
- Newer source wins: use $7/user/month annually as the current public starting price. [S17]
- Rivally Pulse is separately priced rather than bundled; its price is not provided. [S23]

## Where they win
- Engaging points-based recognition feed. [S02, S16]
- Fast implementation: one mid-market reviewer reported setup in under a week. [S04]
- Slack integration reportedly works out of the box. [S04]
- Strong fit for distributed EU teams, including praised multi-language support. [S12]
- EU data residency became generally available. [S15]
- Support response time was praised as under four hours. [S22]

## Where we win
- Analytics depth: reviewers describe Rivally’s analytics and reporting as limited or basic, and an 800-seat prospect selected Bonusly over Rivally specifically because of analytics depth. [S02, S07, S25]
- Enterprise user administration: Rivally reportedly lacks SCIM provisioning, making user management manual. [S10]
- Admin tooling: reviewers say it lags peers and lacks bulk recognition editing. [S16, S24]
- Data portability: analytics exports are reportedly CSV-only, and one reviewer described migration away from Rivally as difficult. [S20]
- EMEA rewards breadth: a reviewer reported that Rivally’s EMEA rewards catalog is thinner than its US catalog. [S14]

## Objections and responses
- Objection: “Rivally is cheaper.”
  Response: Current public pricing is $7/user/month annually; request a term-matched, seat-matched comparison that includes add-ons and discounts. [S17, S18, S23]

- Objection: “Rivally is easy to deploy.”
  Response: A reviewer did report setup in under a week and an out-of-the-box Slack integration; evaluate post-launch administration separately because reviewers report missing SCIM, lagging admin tooling, and no bulk recognition editing. [S04, S10, S16, S24]

- Objection: “Rivally is stronger for Europe.”
  Response: Its multi-language support and EU data residency are credible strengths, but validate rewards coverage because one review reports a thinner EMEA catalog. [S12, S14, S15]

- Objection: “Rivally covers engagement surveys too.”
  Response: Rivally Pulse is a lightweight survey add-on and is separately priced rather than bundled; detailed feature depth and price are not provided. [S06, S23]

- Objection: “Rivally has sufficient reporting.”
  Response: Multiple reviewers characterize its analytics as limited or basic, and one competitive decision favored Bonusly because of analytics depth. [S02, S07, S25]

## Recent changes
- 2026-09-01: Rivally Pulse exited beta as a separately priced add-on. [S23]
- 2026-08-20: Microsoft Teams app v2 entered public preview. [S19]
- 2026-08-12: Recognition Starter increased to $7/user/month annually. [S17]
- 2026-07-01: Rivally opened a Dublin office and made EU data residency generally available. [S15]
- 2026-05-09: Rivally hired a former Workday VP EMEA to lead European expansion. [S11]
- 2026-03-06: Rivally launched the lightweight Rivally Pulse engagement-survey add-on. [S06]
- 2025-11-04: Rivally announced a $40M Series C led by Northgate Ventures. [S01]

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

- Wins: 13
- Losses: 7
- Total: 13 + 7 = 20
- Win rate: 13 ÷ 20 × 100 = 65%
- Loss rate: 7 ÷ 20 × 100 = 35%

Wins: 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: Deal-7767F5, Deal-5645A5, Deal-C6FFAA, Deal-D263E0, Deal-935746, Deal-9066A6, Deal-72A02F.

The deal records do not contain snippet IDs, so snippet citations cannot be supplied for this section.

## Unverified or corrected claims from the old card
- “Points-based recognition for mid-market”: points-based recognition is supported, but the supplied evidence does not establish “mid-market” as Rivally’s positioning. Mark “mid-market” unverified. [S02]
- “Starts at $5/user/month”: outdated; the newer public price is $7/user/month annually. [S08, S17]
- “Rivally lacks a Slack integration”: contradicted by a reviewer reporting that its Slack integration worked out of the box. [S04]
- “Rivally was acquired by WorkHuman in 2025”: unverified; no supplied snippet supports this claim.
- “Strong in EU enterprise with multi-language support”: supported by an EU enterprise review. [S12]
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.1529 · 62s · in 27 / out 3,531 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
Rates use totals across all steps: metric ÷ sent.

- New Logo Nurture: sent 1,386; open 490/1,386 = 35.35%; reply 90/1,386 = 6.49%; meeting 27/1,386 = 1.95%. Weakest: step 3—18/428 = 4.21% reply; 6/428 = 1.40% meeting.
- Expansion Nurture: sent 875; reported open 565/875 = 64.57%; reply 59/875 = 6.74%; meeting 12/875 = 1.37%. Weakest: step 3—12/275 = 4.36% reply; 3/275 = 1.09% meeting. Open rate is unreliable due to the tracking error below.
- Cold Outbound - HR Leaders: sent 1,785; open 545/1,785 = 30.53%; reply 8/1,785 = 0.45%; meeting 0/1,785 = 0.00%. Weakest: step 3—1/590 = 0.17% reply and 0/590 = 0% meeting.
- Cold Outbound - People Ops: sent 1,163; open 340/1,163 = 29.23%; reply 29/1,163 = 2.49%; meeting 6/1,163 = 0.52%. Weakest: step 3—6/377 = 1.59% reply; 1/377 = 0.27% meeting.

Tracking error: Expansion Nurture step 2 reports 340 opens on 300 sent: 340/300 = 113.33%, or 40 excess opens.

Audience overlap:
- Cold Outbound - HR Leaders / Cold Outbound - People Ops: 21 contacts: CT-000849, CT-000884, CT-000890, CT-000908, 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.
- New Logo Nurture / Expansion Nurture: CT-000301, CT-000624.

Under-2% reply failure modes: HR Leaders fails at every step despite measurable opens, indicating post-open message/offer mismatch; exact cause is unavailable. People Ops step 3 indicates follow-up fatigue or weak step-3 relevance; exact cause is unavailable.

Changes:
- HR Leaders: replace the sequence copy with an HR-specific value proposition and CTA.
- People Ops: replace step 3 with a materially different angle.

Fix HR Leaders first: 0.45% replies and 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.0498 · 16s · in 6 / out 937 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 weekly marketing goals update — 66 of 92 days elapsed (66 ÷ 92 = 71.74%)

| Metric | QTD actual | Target | Delta (actual − target) | Pace |
|---|---:|---:|---:|---|
| SQMs | 230 | 300 | 230 − 300 = **−70** | **Ahead**: 230 ÷ 300 = 76.67%, versus 71.74% elapsed |
| SQOs | 84 | 120 | 84 − 120 = **−36** | **Behind**: 84 ÷ 120 = 70.00%, versus 71.74% elapsed |
| DS2s | 40 | 75 | 40 − 75 = **−35** | **Behind**: 40 ÷ 75 = 53.33%, versus 71.74% elapsed |
| Closed-lost MIA rate | 5 ÷ 25 = **20.00%** | ≤10.00% | 20.00% − 10.00% = **+10.00 pp unfavorable** | **Behind**: current rate exceeds the maximum target |
| Same-quarter close count | 10 | 20 | 10 − 20 = **−10** | **Behind**: 10 ÷ 20 = 50.00%, versus 71.74% elapsed |
| Active pipeline coverage | $3,000,000 ÷ $4,000,000 = **75.00% (0.75×)** | $4,000,000 | $3,000,000 − $4,000,000 = **−$1,000,000** | **Ahead**: 75.00% of target, versus 71.74% elapsed |

What moved this week cannot be determined: the provided data contains only current QTD values and no prior-week figures or weekly changes.
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.0404 · 6s · in 3 / out 340 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
Plan Q3 at $115,976.75: $44,729 COMMIT + 35% × $203,565 BEST_CASE ($71,247.75), across 54 of 86 in-quarter deals; PIPELINE contributes $0. Another 32 deals worth $227,575 are excluded, including COMMIT Deal-D348E1 at $13,770 dated 2026-10-15. Caveat: all 7 in-quarter COMMIT deals lack documented why-buys, so the $44,729 committed base is unsupported.
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.0371 · 4s · in 3 / out 56 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: Follow-up on 150-seat pricing

Hi,

Following up on my August 5 recap of the July 28 demo and pricing for 150 seats. Would you be open to a brief call to discuss next steps?

Best,  
Alex Franklin
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.0400 · 9s · in 3 / out 373 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:** Marketing delivered 46 SQMs against a weekly target of 52, reaching 88.5% of goal (46 ÷ 52 × 100). The webinar channel contributed 18 SQMs, or 39.1% of the total (18 ÷ 46 × 100). Paid search cost per SQM held at $150.

**Sales:** Sales converted 14 SQOs, set 9 DS2 meetings, and created $310,000 in new pipeline. The team also recorded 3 same-quarter closes this week—solid momentum to recognize as the quarter moves forward.

**CS:** CS saved 2 renewals this week, while Team NPS moved to 61. Looking ahead, the team enters next week with 3 open red-flag accounts requiring attention.

**PLG:** PLG welcomed 412 new signups, with activation at 31% (412 × 31% = 127.72 calculated activations; an exact activated-user count was not provided). Additionally, 38 companies reached the aha moment of 10 recognition gives.
partner-digest-sectionPASS 1.00
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.0409 · 9s · in 3 / out 415 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
Partner Digest: 2026-08-24 to 2026-09-04

- Apex Rewards Co — 2 partner-sourced opportunities totaling $275,000 ($180,000 + $95,000): Deal-DDAAF2 and Deal-2CF33E. Both are in DS1. Co-webinar scheduled for 09-15.
- HRCloud Partners — 1 partner-sourced opportunity totaling $140,000: Deal-F1CDA5. Security review closed; opportunity moved to DS2.
- CultureBridge — 2 partner-sourced opportunities totaling $135,000 ($60,000 + $75,000): Deal-096E1D and Deal-067213. Both are early stage.
- WorkWell Group — 0 partner-sourced opportunities totaling $0. Joint-playbook planning call scheduled for 09-09, with a potential Q4 restart.
- Recogniq — Quiet; 0 partner-sourced opportunities totaling $0.
- KudosWave — Quiet; 0 partner-sourced opportunities totaling $0.
- PeopleFirst Advisors — Quiet; 0 partner-sourced opportunities totaling $0.
- TotalPerk — Quiet; 0 partner-sourced opportunities totaling $0.

Partner-sourced pipeline: 5 opportunities totaling $550,000.

Arithmetic: 2 + 1 + 2 + 0 = 5 opportunities; $275,000 + $140,000 + $135,000 + $0 = $550,000.
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.0394 · 5s · in 3 / out 270 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 using TLS 1.2 or higher. [P1]

Q3. Yes. Bonusly maintains a SOC 2 Type II report, renewed annually. Prospects can obtain the report under NDA. [P2]

Q4. Customer data is retained for 90 days after contract termination, 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 certification statement would answer this question.

Q9. Unanswerable from the provided excerpts. The contractual Service Level Agreement or uptime policy would answer this question.

Q10. Unanswerable from the provided excerpts. Bonusly’s HIPAA/BAA policy or standard Business Associate Agreement terms would answer this question.
ops-maintenance 5 tests
skill-file-reconciliation0.86
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.3121 · 107s · in 9 / out 6,983 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
1. CRITICAL · MERGE — `comms-drafter` and `email-drafter`

Finding: Their ALWAYS-trigger phrases substantially duplicate each other, including `"write me an email"`, `"draft a follow-up"`, `"help me reply"`, `"what should I say"`, `"bump email"`, `"contract nudge"`, and requests to review or rewrite customer-facing email copy.

Proposal: Merge `email-drafter` into `comms-drafter`; retain `comms-drafter` because it covers email plus support, partner, rewards, broker, and channel communications.


2. CRITICAL · REVIEW — Circular delegation chain

Chain:

`deal-strategy-coach` → `email-drafter` → `deal-strategy-coach`

Evidence:
- `deal-strategy-coach`: “use the `email-drafter` skill” for manager-to-prospect emails.
- `email-drafter`: points strategy, diagnosis, and coaching back to `deal-strategy-coach`.

Proposal: Establish one-way ownership: `deal-strategy-coach` may delegate drafting to the surviving communications skill, but that drafting skill must return the draft without delegating the same request back.


3. CRITICAL · UPDATE_BODY — Dangling target `bonusly-brand`

Referenced by:
- `comms-drafter`
- `email-drafter`
- `sales-forecast`
- `signalforge-claim-compressor`

No manifest row or supplied skill file exists.

Proposal: Add the missing skill to both manifest and file set, or remove these delegations and place the required brand rules in an existing skill.


4. CRITICAL · UPDATE_BODY — Dangling target `prospect-research-multithreading`

Referenced by:
- `comms-drafter`
- `email-drafter`
- `deal-strategy-coach`

No manifest row or supplied skill file exists.

Proposal: Add the target to both manifest and file set, or replace the handoffs with a target that exists.


5. CRITICAL · UPDATE_BODY — Dangling target `bonusly-data-questions`

Delegated to by `analysis-validator`; no manifest row or supplied file exists.

Proposal: Add the target or remove its specialist delegation entry.


6. CRITICAL · UPDATE_BODY — Dangling target `bonusly-product-questions`

Delegated to by `analysis-validator`; no manifest row or supplied file exists.

Proposal: Add the target or remove its specialist delegation entry.


7. CRITICAL · UPDATE_BODY — Dangling target `bonusly-business-reporting-questions`

Delegated to by `analysis-validator`; no manifest row or supplied file exists.

Proposal: Add the target or remove its specialist delegation entry.


8. CRITICAL · UPDATE_BODY — Dangling target `bonusly-rewards-questions`

Delegated to by `analysis-validator`; no manifest row or supplied file exists.

Proposal: Add the target or remove its specialist delegation entry.


9. CRITICAL · UPDATE_BODY — Dangling target `bonusly-ppp-questions`

Delegated to by `analysis-validator`; no manifest row or supplied file exists.

Proposal: Add the target or remove its specialist delegation entry.


10. CRITICAL · UPDATE_BODY — Dangling target `bonusly-feature-flag-questions`

Delegated to by `analysis-validator`; no manifest row or supplied file exists.

Proposal: Add the target or remove its specialist delegation entry.


11. CRITICAL · UPDATE_BODY — Dangling target `bonusly-deal-desk-questions`

Delegated to by `analysis-validator`; no manifest row or supplied file exists.

Proposal: Add the target or remove its specialist delegation entry.


12. CRITICAL · UPDATE_BODY — Dangling target `bonusly-datadog-questions`

Delegated to by `analysis-validator`; no manifest row or supplied file exists.

Proposal: Add the target or remove its specialist delegation entry.


13. WARNING · UPDATE_BODY — `analysis-validator` version conflict

Finding:
- Declared current version: `3.6`
- Header and changelog latest version: `3.6`
- Validation Trail template still says `analysis-validator v3.2`

Proposal: Keep `analysis-validator` v3.6 and update the stale v3.2 trail reference. No competing skill should survive; the surviving version is v3.6.


14. INFO · REVIEW — Manifest descriptions over 1,024 characters

Arithmetic:

- Manifest rows: 14
- Descriptions over 1,024 characters: 0
- Largest value: `pipeline-intelligence-report` = 1,006
- `1,006 ≤ 1,024`

Proposal: No trimming is required under the stated 1,024-character limit.


15. WARNING · UPDATE_BODY — Hardcoded values in `analysis-validator`

Hardcoded dates include `April 26, 2026`, `May 4, 2026`, and `May 9, 2026`.

Hardcoded person names include `Manish`, `Amani`, `Bryce Harmon`, `Hugo Lindqvist`, `Dana Mercer`, `Alex Franklin`, `Cole Ingram`, `Gavin Porter`, `Alaina Loori`, `Shealagh Coughlin`, `Colleen Perry`, `Ellie Barton`, `Ashley Reyer`, `Ashley Le`, `Megan Franz`, `Elena Sinclair`, `Tracy`, `Youssef Elkhateeb`, `Amanda Czenkus`, `Ben Castelli`, `Amani Phipps`, `John Thomas`, and `Yasmin Wahid`.

Proposal: Move dated rosters, escalation contacts, and effective-date metadata to a live reference source; leave only lookup instructions in the body.


16. WARNING · UPDATE_BODY — Hardcoded dates in `closed-lost-analysis`

Examples include `May 2026`, `May 4–12`, and dated scenario references such as `"demo on 4/13"`.

Proposal: Move historical examples into a dated reference file and keep the operating taxonomy date-independent.


17. WARNING · UPDATE_BODY — Hardcoded values in `deal-strategy-coach`

Hardcoded Confluence page ID: `2257879045`.

Hardcoded dates include `April 2026`, `2026`, and multiple six-month lookback references tied to that pricing year.

Hardcoded person aliases include `Perseus` and `Farid`.

Proposal: Replace the page ID and named routing owners with configurable references and move year-specific pricing into a versioned pricing reference.


18. WARNING · UPDATE_BODY — Hardcoded dates in `model-selection`

Hardcoded dates include `2026-05-19`, `2026-05-05`, model retirement/deprecation dates, and fixed knowledge-cutoff dates.

Proposal: Keep model registry data in a separately refreshed reference and have the body describe only the update procedure.


19. WARNING · UPDATE_BODY — Hardcoded values in `partner-digest`

Hardcoded page/folder IDs include:
- `2286616609`
- `2286321666`
- `2265382925`
- `2236940297`
- `2237825028`
- `2239365136`
- `2238283777`

Hardcoded dates include `May 16, 2026`, `May 19, 2026`, `June 2, 2026`, `Q2/Q3 2026`, and `2026-05-17`.

Hardcoded person names include `Amani Phipps`, `Kelli`, `Jen Lee`, `Hani`, `Bryce`, and `Sara`.

Proposal: Move destination IDs, canonical-page IDs, partner contacts, and dated examples into a configurable partnerships reference.


20. WARNING · UPDATE_BODY — Hardcoded values in `pipeline-intelligence-report`

Hardcoded dates include `May 2026` and `March 2023`.

Hardcoded person names include `Bryce Harmon`, `Dana Mercer`, `Cole Ingram`, `Alex Franklin`, and `Gavin Porter`.

Proposal: Resolve the AE roster dynamically and move system-state dates into a live data-source reference.


21. WARNING · UPDATE_BODY — Hardcoded values in `sales-forecast`

Hardcoded Confluence page IDs:
- `2232811524`
- `2232582148`

Hardcoded dates include `Q2`, `Q3 2026`, `July 9, 2026`, `April 27, 2026`, and the fixed 13-week cadence examples.

Hardcoded person name: `Alaina`.

Proposal: Parameterize the Confluence destination, derive quarter/date examples at runtime, and resolve forecast ownership dynamically.


22. INFO · UPDATE_BODY — Hardcoded dates in `signalforge-claim-compressor`

Hardcoded date: `2026-05-09`.

Proposal: Move changelog metadata outside the operational body or retain it in a versioned metadata field.


23. WARNING · UPDATE_BODY — Hardcoded values in `signalforge-feedback`

Hardcoded Confluence page IDs:
- `2295136266`
- `2232811524`
- `2234417154`
- `2247295002`

Proposal: Move all feedback-log destinations into configuration and reference them by logical name.


24. WARNING · UPDATE_BODY — Hardcoded values in `stale-pipeline-report`

Hardcoded dates include `2026-06-10` and examples such as `5/7`, `5/15`, and `5/19`.

Hardcoded person name: `Alaina`.

Proposal: Replace dated examples with relative placeholders and resolve leadership names dynamically.


25. WARNING · UPDATE_BODY — Hardcoded values in `weekly-pipeline-report`

Hardcoded dates include `April 1 – June 30, 2026`, `Q1 2026`, and fixed Q1/Q2 figures.

Hardcoded person name: `Ben Lavin`.

Proposal: Derive quarter windows and reviewer identity at runtime; move historical Q1 figures to a dated reference.


26. INFO · REVIEW — Files with no manifest row

Arithmetic:

- Supplied skill files: 14
- Files matched to manifest rows: 14
- Files with no manifest row: `14 − 14 = 0`

Proposal: No action required; continue enforcing file-to-manifest reconciliation.


27. INFO · REVIEW — Manifest rows with no file

Arithmetic:

- Manifest rows: 14
- Rows matched to supplied files: 14
- Manifest rows with no file: `14 − 14 = 0`

Proposal: No action required; continue enforcing manifest-to-file reconciliation.
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.0467 · 14s · in 3 / out 958 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 | Command or action taken | Who ran it | Success verification | Rollback | Trace |
|---|---|---|---|---|---|
| 1 | Acknowledge the PagerDuty alert for reward-worker queue depth >10k and take incident command. Exact command/action sequence needs confirmation. | Bryce Harmon | No separate verification stated. | Not stated. | [M01] |
| 2 | Run `bundle exec rake sidekiq:queue_depth`. | Farid Osman | Reward queue reported 48,213 pending jobs; normal is under 500. | Not applicable; read-only check. | [M02] |
| 3 | Inspect the dead set. Exact command needs confirmation. | Farid Osman | Found 112 jobs, all showing `Redis::TimeoutError` from around 13:58. | Not applicable; inspection only. | [M03] |
| 4 | Pause enqueue with `bin/rails runner 'FeatureFlag.disable(:auto_recognition_enqueue)'`. | Farid Osman | No immediate verification stated. | `bin/rails runner 'FeatureFlag.enable(:auto_recognition_enqueue)'` | [M04] |
| 5 | Clear the dead set from the console. Exact console command/action needs confirmation. | Elena Sinclair | No verification stated. | No rollback stated; needs confirmation. | [M05] |
| 6 | Scale reward workers from 3 to 6 with `kubectl scale deployment/reward-worker --replicas=6`. | Bryce Harmon | Queue depth later fell to 9,400 at approximately 1,200 jobs per minute. | `kubectl scale deployment/reward-worker --replicas=3` | [M06], [M07] |
| 7 | Run `bundle exec rake sidekiq:queue_depth` and check the Datadog error rate. | Cole Ingram | Command returned 0; Datadog error rate was back to baseline. | Not applicable; verification only. | [M08] |
| 8 | Re-enable enqueue with `bin/rails runner 'FeatureFlag.enable(:auto_recognition_enqueue)'`. | Bryce Harmon | 40 new jobs processed cleanly during the next 3 minutes. | The thread contains the pause command `bin/rails runner 'FeatureFlag.disable(:auto_recognition_enqueue)'`, but does not explicitly identify it as this step’s rollback; needs confirmation. | [M09], [M04] |
| 9 | Scale reward workers back to 3 with `kubectl scale deployment/reward-worker --replicas=3`. | Bryce Harmon | Queue remained stable at 0; incident declared resolved. | No rollback explicitly stated for this step. The thread’s prior scale-up command was `kubectl scale deployment/reward-worker --replicas=6`; using it as rollback needs confirmation. | [M10], [M06] |
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.0493 · 13s · in 3 / out 958 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 error: `2026-09-03T14:01:12Z` — `reward-service` logged `Redis::TimeoutError: Connection to Redis at redis-primary:6379 timed out after 5s`.

- Cascade, in order:
  1. `14:01:20Z–14:01:40Z` — `reward-service` exhausted retries for `RewardGiveJob`.
  2. `14:01:40Z` onward — `sidekiq` reported repeated `RewardGiveJob` failures and retries.
  3. `14:01:46Z` onward — individual `RewardGiveJob` failures appear in `sidekiq_jobs.csv`; the earliest is `J-00005`.
  4. `14:02:30Z` — Sidekiq queue `reward` depth exceeded 10,000.
  5. `14:03:05Z` onward — `api-gateway` returned 502 upstream timeouts calling `reward-service`.
  6. `14:03:30Z` onward — `web-app` give-form submissions failed because of upstream 502s.
  7. `14:22:10Z` — `reward-service` reported that the Redis connection was restored and job processing resumed.
  8. `14:24:45Z` — queue `reward` depth fell below 500.

- Service and job involved: `reward-service`; `RewardGiveJob`. `RecognitionDigestJob` also recorded Redis timeout failures in `sidekiq_jobs.csv`, but it is not named in the application-log cascade.

- Datadog query to confirm the first error:
  `service:reward-service status:error "Redis::TimeoutError" "redis-primary:6379"`
  
  Time window: around `2026-09-03T14:01:12Z`.

- The logs do not show why `redis-primary:6379` became unreachable or slow, any Redis host/service logs or infrastructure metrics, the triggering request or job ID for the first timeout, or whether data was lost or duplicated.
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.0572 · 24s · in 9 / out 1,355 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 per code excerpt | Targeting rule / enabled population | Company count |
|---|---|---|---|---:|
| `recognition_streaks_v2` | On | Records recognition activity through `StreakTracker.record(give)`. | `segment:beta_companies`; company identities are not provided. | 42 |
| `points_budget_guardrails` | On | Enforces giver point budgets through `BudgetService.new(company).enforce!(giver, points)`. | `all_companies`. | 220 |
| `slack_dm_nudges` | On | Allows `SlackDm.send_nudge(user)`; the job exits when the flag is not enabled. | `segment:region_na`; company identities are not provided. | 87 |
| `redeem_flow_redesign` | Off | Selects `RedeemV2Component` when enabled and `RedeemV1Component` otherwise. It currently uses V1 because the flag is off. | `targeted_list`; the 12 company identities are not provided. No companies are shown as enabled. | 12 |
| `analytics_dashboard_v3` | On | Assigns the company’s dashboard to `AnalyticsV3`. | `segment:tier_three`; company identities are not provided. | 65 |
| `ms_teams_app_v2` | Off | Enables installation through `TeamsAppV2.install(company)`. Installation is disabled while the flag is off. | `targeted_list`; the 9 company identities are not provided. No companies are shown as enabled. | 9 |
| `legacy_give_modal` | Off | No code reference is provided, so what it controls is unknown. | `segment:legacy_plan`; 14 companies are associated with the rule, but none are shown as enabled. | 14 |
| `survey_boosters_q3` | On | No code reference is provided, so what it controls is unknown. | `segment:legacy_plan`; company identities are not provided. | 7 |
| `paused_offboard_cleanup` | Off | No code reference is provided, so what it controls is unknown. | No targeting rule and no targets. | 0 |

Count check:

- On flags: 42 + 220 + 87 + 65 + 7 = **421**
- Off flags: 12 + 9 + 14 + 0 = **35**
- Exported company-count total: 421 + 35 = **456**

The export does not establish whether companies overlap across flags, so **456 is not necessarily a unique-company count**.
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.0388 · 5s · in 3 / out 190 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 mutual NDA: two-year term, three-year survival, Delaware law, and complete carve-outs, including information that “is independently developed” and “must be disclosed by law or court order.”

NDA-2 — YELLOW — Counsel review due to the embedded 18-month non-solicit: “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 due to the broad three-year non-compete (“Recipient shall not, directly or indirectly, engage in or provide services to any business that competes with Discloser's business”), unusual Republic of Ireland law and exclusive jurisdiction (“the parties submit to the exclusive jurisdiction of its courts”), five-year one-way term, and absence of confidentiality carve-outs.