← back to all models ← RevenueBench home
inclusionai

inclusionai/ling-3.1-flash

Mean 0.989 · 22/23 perfect tests · $0.04 total · 23/40 tests completed — remaining tests discarded from study (endpoint timeouts after dedicated retries) · modalities in: text · 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 2 tests
snowflake-sql-trapped-catalogPASS 1.00
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.0026 · 407s · in 1,077 / out 9,757 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
-- REQUEST: per customer company, first calendar month as a customer -> unique givers,
-- recognition count, successful redemption count. Sources limited to the catalog excerpt.
SELECT
    c.COMPANY_ID AS company,                                  -- catalog documents the M1 metrics but not the company key column; assuming COMPANY_ID, adjust to the real key
    DATE_TRUNC('month', c.FIRST_SUB_PAYMENT_DATE) AS first_customer_month,
    c.M1_USERS       AS unique_givers,                        -- grain caveat below
    c.M1_GIVES       AS recognition_count,                    -- historical giving count: deleted-giver exclusion intentionally NOT applied
    c.M1_REDEMPTIONS AS successful_redemption_count
-- Table choice: PRODUCTION.PLG.COMPANY_COHORT_SUMMARY is the canonical one-row-per-
-- self-serve-company cohort table and the only cataloged source carrying per-company
-- month-1 giving/redemption aggregates. Avoided per catalog notes:
-- HUBSPOT_HUB_1973303.V2_LIVE.OBJECTS_DEALS (UNPOPULATED), PRODUCTION.HUBSPOT.DEALS
-- (STALE, last sync 2023-03), GONG_HUBSPOT_MAP_FAST (retired pattern), plus the
-- HubSpot deal/contact/engagement and Gong tables (holds no recognition metrics).
-- REDEMPTION_RECORDS_V2 is not joined: the catalog documents only its STATE column; no
-- company key or event timestamp columns are given, so a first-month per-company count
-- cannot be written without inventing schema. M1_REDEMPTIONS is the documented month-1
-- redemption count, and the catalog rule "only STATE='succeeded' rows count as
-- redemptions" makes it the successful count. (The DEPRECATED-schema caution in the
-- note targets finance-grade use of the raw events table; this is the canonical
-- aggregate and the succeeded-only rule is already baked into the definition.)
FROM PRODUCTION.PLG.COMPANY_COHORT_SUMMARY AS c
WHERE c.FIRST_SUB_PAYMENT_DATE IS NOT NULL      -- "as a customer" begins at first subscription payment (documented column; no CURRENT_STATUS values are documented, so no status filter is invented)
-- Applied business rule: the documented filter excluding deleted givers is NOT applied
-- to these historical giving counts (M1_GIVES); per the catalog it understates history.
-- Documented gap: no distinct-giver metric exists in the catalog; M1_USERS (month-1
-- users) is the only documented M1 user figure and is returned as unique_givers.
-- Documented gap: whether the M1 window anchors to SIGNUP_DATE, ACTIVATED_DATE, or
-- FIRST_SUB_PAYMENT_DATE is not stated; M1_* is taken as the first calendar month of
-- the company's customer lifecycle as defined by this cohort table.
-- Arithmetic: none - each output is the documented pre-aggregated M1 column, one row
-- per company; no joins, sums, or dedupe are performed at query time.
;
```
crm-completeness-enrichmentPASS 1.00
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.0050 · 395s · in 3,257 / out 19,649 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 EXTRACT AUDIT

Missing input: no deals extract was provided (only companies.csv, contacts.csv, zoominfo_enrichment.csv). Owner/stage/amount/close-date/why-buys completeness is unmeasurable (n=0 rows), and the final "pipeline amount at stake" ranking cannot be computed in dollars. I rank the 10 fixes by contact/company blast radius instead and label it as a proxy. Never invent: every value below comes from the three files.

## 1. Completeness per field

Companies (n=34 rows):
- industry: 34/34 = 100.0% populated (11 rows carry non-canonical labels: "tech" x4 C-66D1FC,C-44EA29,C-60C75F,C-0A092932; "Tech " x4 C-425E2A,C-BA969B,C-93C8BF,C-C9BB20; "health care" x2 C-7BBDFA,C-50D386; "SaaS" x1 C-0A092933)
- employee_count: 25/34 = 73.5% populated (missing 9: C-EC3025,C-96039F,C-44EA29,C-D04904,C-B23205,C-60C75F,C-7BBDFA,C-50D386,C-93C8BF) -> 33/34 = 97.1% after enrichment fills (section 4)
- hq_country: 28/34 = 82.4% populated (missing 6: C-2D1F1B,C-D73B89,C-44EA29,C-D04904,C-2C60E5,C-EE9FFB). Spelling variants on populated rows: "US" x9, "USA" x6, "United States" x2 -> 17 US-equivalent rows need one canonical value.

Contacts (n=52 rows, 20 companies; 14 company rows have zero contacts):
- email: populated 52/52 = 100%; valid 48/52 = 92.3% (4 malformed, section 3)
- title: 39/52 = 75.0% (missing 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)
- persona: 37/52 = 71.2% (missing 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)

Deals: NOT PROVIDED - all five fields unmeasurable.

## 2. Duplicate company clusters (shared domain)

Only two shared domains exist; all hex domains are unique. No company_name column exists, so clusters are domain-defined.

Cluster 1: acme-corp.com -> C-0A092931 (Technology,500,US) + C-0A092932 (tech,510,USA). Survivor: C-0A092931 (canonical industry label; fully populated). Unresolved conflict, both values listed: employee_count 500 vs 510 - no enrichment row exists for acme-corp.com, so recommend manual verification; do not average.
Cluster 2: globex.io -> C-0A092933 (SaaS,200,US) + C-0A092934 (Technology,200,US). Survivor: C-0A092934 (canonical industry label; emp/country identical). Unresolved conflict: industry SaaS vs Technology - no enrichment row for globex.io; recommend manual verification before deleting either label.

## 3. Invalid emails and domain mismatches

Invalid (malformed, no domain): CT-0010 user0@ (C-66D1FC), CT-0080 user0@ (C-92D97D), CT-0081 user1@ (C-92D97D), CT-0192 user2@ (C-425E2A).
Domain mismatch: CT-0011 user1@other-domain.com (C-66D1FC) - email domain does not match company/contact domain 66d1fc.com. Verify whether this is a wrong domain capture or a personal address; all other 47 valid emails match their company domain exactly.

## 4. Enrichment fills (only where a matching row exists)

ZoomInfo export matches 25 of 30 hex domains; no rows exist for ba969b.com, 332637.com, 93c8bf.com, ee9ffb.com, c9bb20.com, acme-corp.com, globex.io (7 domains / 8 company rows).

employee_count fills (8, all =400): C-EC3025,C-96039F,C-44EA29,C-D04904,C-B23205,C-60C75F,C-7BBDFA,C-50D386 <- 400. No numeric conflicts anywhere (all 17 dual-populated emp rows agree exactly). C-93C8BF stays missing (no enrichment row).
hq_country fills: NONE possible. The 5 CRM-blank matched countries are also blank in ZoomInfo (2d1f1b.com, d73b89.com, 44ea29.com, d04904.com, 2c60e5.com); C-EE9FFB has no enrichment row at all.

## 5. CRM vs enrichment disagreements (list both, recommend source)

Industry - 10 disagreements, all the same pattern (CRM "tech"/"Technology"/"Tech " vs ZoomInfo "Computer Software"): 66d1fc.com, ec3025.com, 44ea29.com, 92d97d.com, d04904.com, 77a95a.com, aa8dda.com, b25f40.com, 60c75f.com, 425e2a.com. Recommendation: make ZoomInfo the source of record for employee_count and hq_country (dedicated vendor, canonical country strings, fills 8 gaps); for industry keep the CRM taxonomy as the controlling standard with a published mapping (Computer Software -> Technology, health care -> Healthcare, tech/Tech -> Technology), applied to both sides so either value remains auditable. hq_country: no true conflicts, only spelling variants (US/USA/United States vs United States) - formatting fix, not a source conflict. employee_count: zero conflicts.

Also flag: enrichment itself is blank on 5 country values (above) - vendor coverage gap, not a CRM defect.

## 6. Top 10 fixes (proxy rank: contacts then companies affected - dollar ranking impossible, no deals file)

1. Fill 15 missing personas - 15 contacts, 12 companies (C-2D1F1B,C-C6FE92,C-D73B89,C-96039F,C-44EA29,C-92D97D,C-D04904,C-77A95A,C-B23205,C-D0662E,C-B25F40,C-60C75F). Worst coverage field (71.2%).
2. Fill 13 missing titles - 13 contacts, 11 companies; C-AA8DDA is 100% title-blank (CT-0120,CT-0121,CT-0122).
3. Re-source 5 broken contact records - 4 malformed emails + CT-0011 domain mismatch; 3 companies (C-66D1FC,C-92D97D,C-425E2A), 9 contacts at risk.
4. Backfill employee_count=400 from ZoomInfo - 8 companies (C-EC3025,C-96039F,C-44EA29,C-D04904,C-B23205,C-60C75F,C-7BBDFA,C-50D386); 16 contacts across the 6 that have contacts.
5. Research HQ country via a non-ZoomInfo source - 6 companies (C-2D1F1B,C-D73B89,C-44EA29,C-D04904,C-2C60E5,C-EE9FFB); enrichment cannot answer any of them; 11 contacts sit at the 4 contact-bearing ones.
6. Close the enrichment coverage gap - 7 domains missing from ZoomInfo export (ba969b.com,332637.com,93c8bf.com,ee9ffb.com,c9bb20.com,acme-corp.com,globex.io); C-93C8BF emp_count stays missing until resolved.
7. Canonicalize industry labels - 10 CRM-vs-ZI disagreements + 11 non-standard labels via the mapping in section 5 (touch every row, no data loss).
8. Merge acme-corp.com cluster - survivor C-0A092931; manually reconcile emp 500 vs 510 before delete.
9. Merge globex.io cluster - survivor C-0A092934; manually reconcile SaaS vs Technology before delete.
10. Normalize country spellings US/USA/United States to one canonical value - 17 rows; trim whitespace in "Tech " labels (4 rows).

Extra observations (not required fields, so outside the top 10): 14 company rows have zero contacts (C-2C60E5,C-B97B4E,C-2D7423,C-7BBDFA,C-50D386,C-BA969B,C-332637,C-93C8BF,C-EE9FFB,C-C9BB20 plus the 2 merged clusters); C-950043 and C-31ED2A each have a single contact, so no buying-team redundancy.
deal-intelligence 3 tests
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.0017 · 257s · in 2,118 / out 5,461 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
```json
[
  {
    "transcript_id": "TX-001",
    "deal_alias": "Deal-CFE7F4",
    "why_buys": ["Automating anniversary and birthday awards - HR team of three cannot keep up manually (Prospect VP People)"],
    "pain_points": ["HR team of three cannot keep up with awards manually (Prospect VP People)", "Everything tracked in a spreadsheet; people slip through the cracks (Prospect HR Admin)"],
    "stakeholders": ["Prospect (VP People)", "Prospect (HR Admin)"],
    "budget_signal": "About $40k earmarked for engagement tools this fiscal year (Prospect VP People)",
    "timeline_signal": "Live before open enrollment in November (Prospect VP People)",
    "competitor_mentioned": {"name": "Achievers", "raised_by": "Prospect (VP People)", "note": "Looked at last year; too heavy for a team their size"},
    "next_step": "Security review with IT lead on September 12 - explicitly agreed ('Yes - let's do the security review on September 12')",
    "objections": ["Need SSO and audit logs for IT to sign off (Prospect HR Admin)"],
    "confidence": null,
    "missing_data": "No confidence value stated anywhere in the transcript"
  },
  {
    "transcript_id": "TX-002",
    "deal_alias": "Deal-70BB30",
    "why_buys": ["Tie recognition to retention for the hourly workforce (Prospect Head of Total Rewards)"],
    "pain_points": ["Regretted turnover in hourly workforce is over 30% (Prospect Head of Total Rewards)", "Workday integration must be rock solid - CFO's stated one condition (Prospect CFO)"],
    "stakeholders": ["Prospect (Head of Total Rewards)", "Prospect (CFO)"],
    "budget_signal": "Finance approved a $25k pilot budget for this quarter (Prospect CFO)",
    "timeline_signal": "Decision by end of September (Prospect CFO)",
    "competitor_mentioned": null,
    "competitor_note": "None raised - prospect said this is the first vendor with a real demo. Workday is an integration platform, not a competitor, so excluded from competitor field",
    "next_step": "Send pilot agreement; prospect routes it to legal this week - explicitly agreed",
    "objections": ["Workday integration has to be rock solid (Prospect CFO, 'my one condition')"],
    "confidence": null,
    "missing_data": "No confidence value stated"
  },
  {
    "transcript_id": "TX-003",
    "deal_alias": "Deal-530B50",
    "why_buys": ["Make recognition visible across 12 retail locations (Prospect People Ops Manager)"],
    "pain_points": ["Store managers have zero budget autonomy for on-the-spot recognition today (Prospect People Ops Manager)"],
    "stakeholders": ["Prospect (People Ops Manager)"],
    "stakeholder_note": "Prospect referenced CEO as the decider ('she decides anything people-related'), but CEO is not on the speaker list",
    "budget_signal": null,
    "budget_note": "No prospect-stated budget. Rep quoted ~$8/employee/month - rep-stated, excluded per rules",
    "timeline_signal": "No rush until Q1 (Prospect People Ops Manager)",
    "competitor_mentioned": {"name": "Bucketlist", "raised_by": "Prospect (People Ops Manager)", "note": "CEO used it at her last company and liked it"},
    "next_step": "Schedule a call with the CEO; prospect will send two times - explicitly agreed",
    "objections": ["CEO has to be sold first - she decides anything people-related (Prospect People Ops Manager)"],
    "confidence": null,
    "missing_data": "No confidence value stated"
  },
  {
    "transcript_id": "TX-004",
    "deal_alias": "Deal-180D02",
    "why_buys": ["Consolidate three separate recognition tools into one (Prospect VP People)"],
    "pain_points": ["Paying for three tools and none talk to the HRIS (Prospect VP People)"],
    "stakeholders": ["Prospect (VP People)", "Prospect (IT Security Lead)"],
    "budget_signal": "Under $15k annually - VP can approve without board approval (Prospect VP People)",
    "timeline_signal": "Procurement cycle runs six to eight weeks minimum (Prospect IT Security Lead)",
    "competitor_mentioned": null,
    "competitor_note": "No competitor named - 'last vendor' is unnamed",
    "next_step": null,
    "next_step_note": "CFO follow-up next week NOT agreed - prospect said 'Maybe - I need to check her calendar, no promises'",
    "objections": ["Security review took three months for the last vendor - stated hesitation (Prospect IT Security Lead)", "Procurement cycle six to eight weeks minimum (Prospect IT Security Lead)"],
    "confidence": null,
    "missing_data": "No confidence value stated"
  },
  {
    "transcript_id": "TX-005",
    "deal_alias": "Deal-F8767A",
    "why_buys": ["Automate service milestones (Prospect HR Director)", "Analytics on recognition equity across departments (Prospect HR Director)"],
    "pain_points": ["Night-shift teams feel invisible; engagement scores run 20 points lower (Prospect People Ops Coordinator)"],
    "stakeholders": ["Prospect (HR Director)", "Prospect (People Ops Coordinator)"],
    "budget_signal": "$12k approved under the engagement line (Prospect HR Director)",
    "timeline_signal": "Running before the January all-hands (Prospect HR Director)",
    "competitor_mentioned": {"name": "Nectar", "raised_by": "Prospect (HR Director)", "note": "Mid-pilot with Nectar now; prospect says we'd need to beat that experience"},
    "next_step": "Present to the exec team on October 2 - explicitly agreed",
    "objections": ["Exec team skeptical after a failed rollout two years ago (Prospect HR Director)", "Must beat the current Nectar pilot experience (Prospect HR Director)"],
    "confidence": null,
    "missing_data": "No confidence value stated"
  },
  {
    "transcript_id": "TX-006",
    "deal_alias": "Deal-EE195F",
    "why_buys": ["Cut admin time on service awards (Prospect HR Manager)"],
    "pain_points": ["HR Manager personally spends five hours a month ordering and shipping plaques (Prospect HR Manager)"],
    "stakeholders": ["Prospect (HR Manager)"],
    "stakeholder_note": "Prospect referenced COO as preferring in-house builds, but COO is not on the speaker list",
    "budget_signal": "Budget is not the issue - time is (Prospect HR Manager); no amount stated",
    "timeline_signal": "Fiscal year resets in February; Q1 start realistic (Prospect HR Manager)",
    "competitor_mentioned": null,
    "competitor_note": "No competitor vendor named - prospect said they are comparing against just doing it internally",
    "next_step": "Send one-page overview; prospect forwards it to COO this week - explicitly agreed",
    "objections": ["COO usually prefers building things in-house (Prospect HR Manager)"],
    "confidence": null,
    "missing_data": "No confidence value stated"
  }
]
```

Notes: no arithmetic was required - all figures ($40k, 30%, $25k, $8/employee/month, $15k, $12k, 20 points, five hours, 6-8 weeks, three months) are quoted verbatim from prospect lines with no computation. `confidence` is null for all six transcripts because no transcript contains any confidence data.
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.0013 · 166s · in 1,555 / out 3,915 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** — Alex Franklin, $11,200, DS5/COMMIT, close 2026-09-11.
Slack (09:12): redlines clean, signing page out, VP People says they sign tomorrow — explicitly "signature-imminent." Left: the signature itself.

**2. Deal-403845** — $9,000, DS5/COMMIT, close 2026-09-11.
Slack (10:02): order form is with their finance team — normally the last step before signature. Left: finance approval, then sign.
Data flag: CRM owner is Alex Franklin; Dana Mercer claims it in Slack ("on my side"). Ownership conflict, unresolved.

**3. Deal-A2B47C** — Alex Franklin, $6,360, DS5/COMMIT, close 2026-09-11.
Slack (09:44): still warm, normal legal-review pace. Left: legal review to finish. Ranked ahead of Deal-D348E1 ($13,770, also warm/legal pace) because it closes 2026-09-11 vs. 2026-10-15.

Arithmetic: 11,200 + 9,000 + 6,360 = $26,560 total.

Excluded: **Deal-2465CE** ($5,400, DS5/COMMIT, 2026-09-10) looks top-3 on CRM alone, but Slack (09:20) says the champion left and procurement froze new vendors — Dana pulled it from commit; blocked, realistically Q4.

Unconfirmed: **Deal-B7EBD1** ($9,000, DS5/COMMIT, 2026-09-10) has the earliest CRM close date but no Slack signal either way; from the data given I can't verify it's actually near signature, so it misses the list.
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.0009 · 133s · in 815 / out 2,424 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
Deal amounts: not provided in either file — transcripts_gaps.csv has deal_alias only, so I cannot state amounts. I will not invent them.

Candidate review (5 prospect lines, classified against product_docs.md, snapshot 2026-08):

1. Deal-EC3025 — "We need SCIM user provisioning — our security team will not approve any tool that requires manual account management."
Classification: real gap. Docs state "SCIM user provisioning ... NOT currently listed as supported capabilities." It appears on no plan tier (Core/Pro/Enterprise), so this is product absence, not a tier gate.

2. Deal-D0D6B5 — "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. Docs list supported HRIS integrations as "Workday, BambooHR, Gusto, Rippling (Pro and above)" and state "ADP Workforce Now integrations are NOT currently listed as supported capabilities." Absent on every tier.

3. Deal-CFE7F4 — "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. Docs table: custom report builder is "—" on Core and Pro, "yes" on Enterprise. Capability exists in product but is tier-bound; rep offered "upgrade paths." Not a product gap.

4. Deal-84DBA6 — "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. Docs: "Slack and Microsoft Teams integration" is "yes" on all three tiers. Capability present and switched on; the stated cause is missing manager training ("nobody ever trained them"), and rep is scheduling a "manager enablement session."

5. Deal-36C33F — Prospect line: "Good to know. The web version should be fine for our office staff for now."
Classification: no prospect-raised gap. The native mobile app limitation was raised by rep Alex Franklin ("we don't have a native mobile app for hourly workers yet, though it's on the roadmap"), and the prospect accepted the web workaround. Rep language does not count as prospect voice, so this candidate is excluded.

Summary — real gaps only (2 of 5 candidates):
- Deal-EC3025: no SCIM user provisioning on any plan; security approval is blocked on it. Amount: not provided.
- Deal-D0D6B5: no ADP Workforce Now integration on any plan; prospect calls it a dealbreaker. Amount: not provided.

Arithmetic: 5 prospect lines evaluated = 2 real gaps + 1 plan gate + 1 rollout/enablement issue + 1 excluded (rep voice). Real-gap deals: 2 of 5 (40%). Combined deal value cannot be computed — amounts are missing from the provided data.
rep-performance 2 tests
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.0030 · 522s · in 2,390 / out 11,150 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
Data gaps up front (affects every row): the provided files contain no amount, no stage, and no open/closed flag. I treated every deal in deal_contacts.csv as an open deal; amount and stage are reported as "not provided" and cannot be invented.

Arithmetic for the 60-day rule: today 2026-10-19 minus 60 days = 2026-08-20 (Aug 20→Aug 31 = 11d + Sep = 30d + Oct 1→19 = 19d = 60d). So a contact is active only if last_engaged_date is on/after 2026-08-20 AND is_former=false. Boundary cases counted active: 2026-08-20 (exactly 60d). Stale by 1 day: 2026-08-19.

Value-to-add rule (stage is missing, so stage-tuning is impossible; fixed order, first missing persona wins): economic buyer > champion > IT security > finance > HR admin. With stage data this shifts (early stage favors champion, late stage favors EB — flagged where relevant).

FLAGGED DEALS (11 of 14)

1. Deal-36C33F / 63739413805 / C-077A0E — 0 ACTIVE CONTACTS (worst case)
   amount: not provided | stage: not provided | active: 0
   present: none | missing: all five (champion, economic buyer, HR admin, IT security, finance)
   reasons: IT security CT-4FE556 stale 2026-08-15; champion CT-405B45 and EB CT-86B22F both is_former=true
   most valuable to add: economic buyer; on-file fit: CT-1DB73E, Chief People Officer, economic buyer. Champion also absent — none on file.

2. Deal-EC3025 / 61032318100 / C-FDD0C7 — single-threaded
   amount: not provided | stage: not provided | active: 1
   present: champion (CT-047C54, 2026-09-02) | missing: economic buyer, HR admin, IT security, finance
   note: EB CT-F2C1AE is is_former=true and stale 2026-08-15
   most valuable to add: economic buyer; on-file fit: CT-6827DB, Chief People Officer, economic buyer.

3. Deal-92D97D / 59728118877 / C-E23238 — single-threaded
   amount: not provided | stage: not provided | active: 1
   present: HR admin (CT-01F5B4, 2026-08-28) | missing: economic buyer, champion, IT security, finance
   note: champion CT-A902AE stale 2026-06-01 (140 days)
   most valuable to add: economic buyer (champion equally absent; without stage, EB first per rule — if early-stage, champion outranks here); on-file fit: none on file (no C-E23238 rows in unengaged_contacts.csv).

4. Deal-885F45 / 60686135564 / C-5E8EFB — single-threaded
   amount: not provided | stage: not provided | active: 1
   present: economic buyer (CT-51C81E, VP People, 2026-08-26) | missing: champion, HR admin, IT security, finance
   note: champion CT-D9A0E8 stale 2026-08-11
   most valuable to add: champion (EB present, no internal driver); on-file fit for champion: none on file. Secondary: CT-B3F25D, IT Security Lead — fits the next-ranked missing persona (IT security).

5. Deal-D0D6B5 / 60081655042 / C-32918E — single-threaded
   amount: not provided | stage: not provided | active: 1
   present: champion (CT-87CED4, 2026-09-02) | all actives in one persona: yes | missing: economic buyer, HR admin, IT security, finance
   note: two more champions stale — CT-DE6D7C 2026-08-19 (misses cutoff by 1 day), CT-FD70B2 2026-08-07
   most valuable to add: economic buyer; on-file fit: CT-1FA4DB, Chief People Officer, economic buyer.

6. Deal-5BFE3B / 51674270311 / C-535D36 — single-threaded
   amount: not provided | stage: not provided | active: 1
   present: champion (CT-57123B, 2026-08-31) | missing: economic buyer, HR admin, IT security, finance
   note: second champion CT-5CE757 stale 2026-08-12
   most valuable to add: economic buyer; on-file fit: none on file (no C-535D36 rows in unengaged_contacts.csv).

7. Deal-FCBE5B / 62639586615 / C-737030 — single-threaded
   amount: not provided | stage: not provided | active: 1
   present: champion (CT-4A5317, 2026-08-29) | missing: economic buyer, HR admin, IT security, finance
   most valuable to add: economic buyer; on-file fit: none on file.

8. Deal-5408B0 / 60182332309 / C-2AE3AA — single-threaded
   amount: not provided | stage: not provided | active: 1
   present: champion (CT-D33AE4, 2026-09-01) | missing: economic buyer, HR admin, IT security, finance
   note: HR admin CT-8742FD stale 2026-08-18 (2 days short)
   most valuable to add: economic buyer; on-file fit: CT-07FA76, Chief People Officer, economic buyer.

9. Deal-F9A08A / 49757401138 / C-0D15DF — single-threaded
   amount: not provided | stage: not provided | active: 1
   present: champion (CT-931B10, 2026-09-03) | missing: economic buyer, HR admin, IT security, finance
   note: roster EB CT-913581 stale 2026-06-20 (121 days) — a re-engagement candidate, though not in unengaged_contacts.csv
   most valuable to add: economic buyer; on-file fit: CT-697541, Chief People Officer, economic buyer.

10. Deal-50D386 / 61055128146 / C-EB10E4 — under-threaded (fewer than 3)
    amount: not provided | stage: not provided | active: 2
    present: champion (CT-AA41B2, 2026-09-01), HR admin (CT-B9C35B, 2026-08-25) | missing: economic buyer, IT security, finance
    most valuable to add: economic buyer; on-file fit: CT-A1C4B3, Chief People Officer, economic buyer.

11. Deal-C6D97A / 62121783047 / C-5A8FC2 — under-threaded on BOTH tests (active < 3 AND all actives one persona)
    amount: not provided | stage: not provided | active: 2
    present: champion only — CT-223DDC (2026-08-31), CT-B03555 (2026-08-20, exactly 60d, active); third contact CT-4E8A2B stale 2026-08-05 | missing: economic buyer, HR admin, IT security, finance
    most valuable to add: economic buyer; on-file fit: none on file (no C-5A8FC2 rows in unengaged_contacts.csv).

CHECKED, NOT FLAGGED (3): Deal-84DBA6 / 63929535929 (3 active, 3 personas: champion, economic buyer, IT security); Deal-4B0BEB / 61038797752 (3 active, 3 personas: champion, economic buyer, HR admin — finance CT-3E135F stale 2026-08-09 but criteria still met); Deal-D348E1 / 61750885954 (4 active, 4 personas — its HR admin CT-BEDF5E went stale 2026-08-19, one day short, so the HR admin gap is live but count/diversity criteria pass).

Summary: 11 flagged — 9 single-threaded, 2 under-threaded; 1 deal (36C33F) has zero active contacts. Economic buyer is the top gap in 10 of 11, and 7 of 11 have an on-file economic-buyer candidate ready to activate. Amount and stage must come from the deal system before stage-specific prioritization can replace the fixed rule above.
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.0022 · 332s · in 3,197 / out 7,369 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
LEAD, FIRST FIVE MINUTES

8 of 10 calls open with the identical case study (all except TT-004, TT-009):
"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."

TT-004 (Deal-403845) leads with an agenda:
"I put together a short agenda — security review first, then pricing."

TT-009 (Deal-1E2498) leads with pricing:
"You asked for straight pricing last time, so let's start there."

TT-005 (Deal-C61CF7) adds a competitor jab at minute 2:
"And unlike Workhuman, our pricing includes the full rewards catalog with no extra margin."

TOP 3 OBJECTIONS AND HANDLING

1. Budget locked, 4 of 10 calls (TT-001, TT-003, TT-006, TT-010; Deals D348E1, 547B2B, 60C2C2, 84DBA6):
"Honestly, budget is locked until next fiscal year — I can't add a new line item right now."
Handled identically 4 of 4 times: same reply at minute 8, funding from turnover savings, retailer saved about $210k in avoided backfills, finance team sign-off.

2. Next-quarter deferral, 3 of 10 (TT-002, TT-005, TT-008; Deals 5408B0, C61CF7, D9A12F):
"This is good, but can we revisit it next quarter? Open enrollment starts in October and we're underwater."
Handled identically 3 of 3 times: 90-day pilot, one department, internal data before planning.

3. Status quo, 3 of 10 (TT-004, TT-007, TT-009; Deals 403845, EDC141, 1E2498):
"We already do recognition with a spreadsheet and quarterly gift cards — why would we change?"
Handled identically 3 of 3 times: automation and analytics, milestones fire without HR effort, visibility into who is recognized.

Also raised once each: budget-committee gate (TT-004, TT-010) and "no urgency" (TT-007). Counts: 4 + 3 + 3 = 10 objections across 10 calls.

NEXT STEP AGREEMENT RATE

Ask made in 7 of 10 calls:
"Should we lock the next step — a working session with your team this week?"

Agreed in 7 of 10 calls = 70%. When asked, accepted 7 of 7 = 100%. The agreement line is word-for-word identical in all 7:
"Yes, Thursday at 2pm works — send the invite and I'll bring our HRIS manager."

No step in TT-004, TT-007, TT-010; no ask made in any of them (rep closed with "I'll leave it with you", "Fair enough.", "Understood, thanks for the candor.").

COMPETITORS RAISED BY PROSPECTS (2)

Awardco, TT-003 (Deal-547B2B):
"We're also in late talks with Awardco — their rewards catalog looks bigger than yours."

Kudos, TT-007 (Deal-EDC141):
"How are you different from Kudos? Our CEO used them at her last company."

Workhuman appears only in the rep's line (TT-005), never raised by a prospect, so it is excluded.

Missing from the data: deal sizes, what happened after each call, and whether the Thursday sessions occurred. The identical confirmation line across 7 different deals may be a transcript artifact, not seven real calendar commitments.

COACHING NOTES

1. The ask, not the close, is the gap: 7 asks, 7 accepts, and the three dead-end calls are exactly the three with no ask. Coach a fallback ask on every stall, even gated ones: committee decision date, pilot scope, or the invite with a later date.
2. De-script and verify repeats. Identical opener in 8 of 10 calls, identical replies within each objection type, same Thursday-2pm confirmation across 7 deals; TT-009's pricing-first open is the only tailored lead. Coach opens tied to deal context (TT-004's agenda proves the rep can vary it) and confirmation that recurring next steps are real.
reporting-analytics 1 tests
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.0024 · 312s · in 4,284 / out 6,130 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
**KVMs, 2026-08 vs 2026-07** (unweighted mean across 30 companies, 10 per size_band; no user counts provided, so rates are company-averages, not user-weighted)

| KVM | 2026-07 | 2026-08 | Abs change | Rel change | Direction |
|---|---|---|---|---|---|
| Giving rate | 0.6023 | 0.6027 | +0.0004 | +0.07% | up |
| Redemptions per user | 1.7300 | 1.7302 | +0.0002 | +0.01% | up |
| 1:1 meetings engagement | 0.4469 | 0.4472 | +0.0003 | +0.06% | up |
| Pulse check engagement | 0.6006 | 0.5086 | -0.0920 | -15.31% | down |

Largest relative move: **pulse check engagement, -15.31%**. Driver: **size_band = enterprise**, which fell 0.5500 → 0.2743 (-50.13%, arithmetic: -0.2757/0.5500). All ten enterprise companies dropped to a tight 0.2619–0.2864 band while smb (-0.22%) and mid_market (+0.21%) pulse held flat, so the overall move is entirely an enterprise effect. plan_tier cannot drive anything here: every row is tier_three, so the data does not support tier-level attribution.

The data does not say why enterprise halved. A uniform ~50% cut across all ten companies, with no corresponding movement in the other three KVMs, is consistent with a measurement/collection change rather than behavior — worth verifying the pulse methodology before acting.

Giving rate, redemptions, and 1:1 engagement are effectively flat (all under ±0.4% in every band).
customer-success 3 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.0027 · 421s · in 1,756 / out 10,097 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
Qualification test (all three rules must pass): health_score < 60 AND churn_save_eligible_amount > 0 AND renewal within 120 days of snapshot 2026-09-05 (window closes 2027-01-03).

QUALIFYING ACCOUNTS (8) - amount at stake = churn_save_eligible_amount

C-0F6C0F34 | health 51 | $49,707.00 | renew 2026-10-03 (28d) | executive touch
C-0B827671 | health 56 | $25,365.00 | renew 2026-11-14 (70d) | usage revival
C-0B360C78 | health 57 | $35,748.00 | renew 2026-10-28 (53d) | commercial concession
C-0B0F1BAB | health 38 | $5,494.00  | renew 2026-09-23 (18d) | executive touch
C-0CA21961 | health 58 | $16,829.00 | renew 2026-12-28 (114d)| usage revival
C-0E9C27D1 | health 39 | $41,235.00 | renew 2026-09-24 (19d) | commercial concession
C-0CEF69FD | health 53 | $32,621.00 | renew 2026-11-21 (77d) | executive touch
C-0D3278C7 | health 54 | $17,602.00 | renew 2026-11-12 (68d) | usage revival

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

Play subtotals:
- Usage revival (3): $25,365 + $16,829 + $17,602 = $59,796.00
- Executive touch (3): $49,707 + $5,494 + $32,621 = $87,822.00
- Commercial concession (2): $35,748 + $41,235 = $76,983.00
Check: 59,796 + 87,822 + 76,983 = 224,601.00

PLAY MAPPING - caveat: no play definitions were provided in the files, so plays are assigned from the available signals by this heuristic: usage_trend_3m = declining or seat adoption < 50% -> usage revival; otherwise champion_active = false -> executive touch; otherwise (usage flat/growing, adoption >= 50%, champion active) -> commercial concession.

Signals per account:
- C-0F6C0F34 -> exec touch: champion_active=false while usage is healthy (growing, 308/395 seats = 78%). Risk is the relationship, not adoption.
- C-0B827671 -> usage revival: usage_trend_3m=declining, 113/202 seats = 56%. Champion still active.
- C-0B360C78 -> commercial concession: growing usage, 246/327 = 75% adoption, champion active. No usage or champion signal, so the remaining lever is commercial.
- C-0B0F1BAB -> exec touch: champion_active=false, flat usage at 238/363 = 66%. Renewal 18 days out leaves no time for a usage program anyway.
- C-0CA21961 -> usage revival: 84/325 seats = 26% adoption (flat trend masks a collapse). Champion active.
- C-0E9C27D1 -> commercial concession: strong usage (134/157 = 85%, flat) and champion active, yet health 39; renewal 19 days out is too near for remediation, terms are the actionable lever.
- C-0CEF69FD -> exec touch: champion_active=false despite growing usage (97/136 = 71%).
- C-0D3278C7 -> usage revival: declining trend and 126/380 seats = 33% adoption. Champion active.

AT-RISK (health < 60) BUT NOT QUALIFYING (7)

C-0BC71BDD | fails R2: eligible_amount = 0.00 (renewal 2026-10-27 is within window; flat, 59/197 = 30% seats, champion false)
C-0BA71F12 | fails R3: renewal 2027-04-11 is 218 days out (>120). Eligible amount $6,824.00 exists but not in window; declining, 23/98 = 23% seats.
C-0F6694C3 | fails R2 (amount 0.00) and R3 (2027-03-21, 197 days); declining, 39/96 = 41%.
C-0BE96399 | fails R2: amount 0.00 (renewal 2026-10-29 within window; declining, 43/154 = 28%).
C-0F876796 | fails R3: renewal 2027-02-06 is 154 days out (>120) despite $19,958.00 eligible amount; declining, 22/95 = 23%, champion false.
C-0FCCD2DF | fails R2 (0.00) and R3 (2027-04-23, 230 days); flat, 27/63 = 43%, champion false.
C-10A56B0F | fails R2: amount 0.00 (renewal 2026-12-12, 98 days, within window; declining, 85/176 = 48%, champion false).

Remaining 15 accounts all have health_score >= 60 (not at-risk under R1) and eligible_amount = 0.00, so none qualify; no missing fields in the dataset for any account assessed.
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.0014 · 257s · in 489 / out 4,744 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
EXPANSION KIT — C-0DDFC9A7

SEAT COVERAGE (licensed / headcount)
- 150 / 400 = 0.375 → 37.5% of headcount covered; 62.5% uncovered.

USAGE HEALTH
- MAU climbed every month Mar–Aug 2026: 88 → 95 → 102 → 110 → 118 → 126. That is +38 users over 5 months (avg +7.6/mo), +43% since March, no down month.
- August utilization: 126 active / 150 licensed = 84% of seats in use; actives equal 126/400 = 31.5% of headcount.

HEADROOM (seats and ARR at current per-seat rate)
- Per-seat rate: $9,000 / 150 seats = $60/seat/year (assumes ARR is purely seat-based; no other pricing detail provided).
- Seats to full headcount coverage: 400 − 150 = 250 seats.
- Incremental ARR: 250 × $60 = $15,000; ARR at full coverage: 400 × $60 = $24,000 (vs $9,000 today).

REPLYER AND BUYING ABILITY
- Replied: Maria S., People Operations Coordinator, 2026-09-02 (matches her last_engaged date).
- Can buy: no. Her own words: "I'm not the right person for purchasing decisions here. Budget and seat expansion sit with Dana R."

RIGHT BUYER FROM CONTACTS
- Dana R., VP People, last engaged 2026-05-18. Corroborated by Maria's reply naming Dana R. as holding budget and seat expansion. Maria S. offers to make the introduction.

REPLY EMAIL (body ~78 words, under the 150 cap; cites Aug MAU 126 vs March 88)

Subject: RE: Growing your team's recognition program

Hi Maria,

Thanks for the reply — glad the team loves Bonusly, and the numbers back it up: 126 monthly active users in August, up from 88 in March.

You're right that seat expansion belongs with Dana. Would you be open to an introduction, or to copying her on a short note? I'll keep it brief and can include a one-page usage snapshot she can reference beforehand.

No pressure at all — whenever works for your team.

Best,
Cole Ingram

Missing data noted: no pricing tier, discount, or renewal date provided; headroom math assumes seat-only pricing.
onboarding-statusPASS 1.00
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.0010 · 174s · in 558 / out 2,810 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
Company: C-0D284E42. Signup 2026-08-11; data ends 2026-09-04 (day 25).

COMPLETE (field shows it)
- Slack integration: integration_slack = 2026-08-12 (day 1 after signup)
- Allowance set: allowance_set = 2026-08-13 (day 2)
- Admins added: admins_added = 2 (count only; whether 2 is sufficient is not determinable from this data)
- First recognition: first_recognition_at = 2026-08-15 14:22 (day 4)

NOT COMPLETE (field empty — absence of data, not proof of failure)
- HRIS integration: integration_hris is blank
- First redemption: first_redemption_at is blank

EARLY ENGAGEMENT SIGNALS (onboarding_usage.csv, active_givers)
- Start to latest: 3 (2026-08-11) → 15 (2026-09-04). Net +12; 15/3 = 5.0x.
- First week avg (08-11→08-17): 3+3+4+4+5+4+7 = 30, 30/7 = 4.3/day. Last week avg (08-29→09-04): 11+13+11+13+13+15+15 = 91, 91/7 = 13.0/day. 13.0/4.3 ≈ 3.0x week-over-week-equivalent lift.
- Trend is monotone-ish upward with only 4 small dips: 08-16 (−1), 08-18 (−2), 08-27 (−1), 08-31 (−2); each recovered within 1–2 days.
- Every day since 2026-08-26 is ≥10 givers (10 straight days). Peak 15 first hit 09-03 and held 09-04.
- Weekends hold: Sunday 08-30 was 13, a local high; Sunday 08-23 (9) beat Saturday 08-22 (8).
- First recognition (08-15) coincided with givers stepping up 4→5, then 7 on 08-17 — giving kept growing after recognition started.

THREE THINGS TO COVER ON THE CALL
1. HRIS integration is the one open setup item (blank field) — get it connected or confirm the blocker; recognition is live without it.
2. First redemption still blank — givers are giving (first recognition day 4) but no points have been spent; walk the recipient through a first redemption.
3. Giver momentum: 3→15 active givers, 5.0x, sustained ≥10 for 10 days — lock in the pattern (ask about the 2 admins' coverage and whether more admins are needed; data does not say).

Not in data (cannot assess): total user count, company size, target admin count, onboarding program length, redemption volume/points balance.
marketing 3 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.0008 · 96s · in 753 / out 1,824 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
Scoring method (analyst-set weights): industry 40, size band 25, use case 20, region 15. Only rows with has_case_study=true are eligible. All arithmetic shown; no billing or contact fields exist in the supplied data.

Top 3 similar customers with public case studies:

1. C-64171065 — score 100/100
   - Industry: Technology = prospect Technology (+40)
   - Size band: Mid-Market = Mid-Market (+25)
   - Use case: employee_recognition = employee_recognition (+20)
   - Region: NA-West = NA-West (+15)

2. C-A13C193D — score 80/100
   - Industry: Technology = Technology (+40)
   - Size band: Mid-Market = Mid-Market (+25)
   - Region: NA-West = NA-West (+15)
   - Use case: retention vs employee_recognition (+0)

3. C-CD4829A7 — score 65/100
   - Industry: Technology = Technology (+40)
   - Size band: Mid-Market = Mid-Market (+25)
   - Use case: retention vs employee_recognition (+0)
   - Region: NA-East vs NA-West (+0)

Excluded by the case-study rule: two customers match all four prospect fields exactly but have has_case_study=false, so they are not named. Closest eligible non-selected customer: C-11C31562 at 60/100 (Mid-Market +25, employee_recognition +20, NA-West +15; Manufacturing industry +0).
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.0029 · 452s · in 1,618 / out 10,791 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 (updated)

Data cutoffs: snippets through 2026-09-03; deal table through 2026-08. Snippet IDs cited per claim; deal outcomes cited by alias from deals_with_competitor.csv.

## 1. Positioning (one line)
Points-based employee recognition with an engagement feed, sold from mid-market (S02, S04) into enterprise (S10, S12), with fast setup (S04) and a newly strengthened EU story (S11, S15).

## 2. Pricing
Current list: $7 per user/month, Recognition Starter tier, annual billing required — pricing page, 2026-08-12 (S17). Newer source wins; supersedes $5/user/month shown 2026-01-20 (S03) and still posted 2026-04-01 (S08).
Conflict noted: deal quotes diverge from page list — $6.50/user/mo quoted to a 500-seat prospect on an annual term in June (S13, while the page still said $5), and $7/user/mo list with a 15% discount for a 3-year term (S18). Treat page as list, quotes as negotiable. No Bonusly pricing data provided; no price-advantage claim can be sourced.

## 3. Where they win
- Engaging, points-based recognition feed (S02, S16).
- Mid-market rollout: setup under a week, Slack integration out of the box (S04).
- EU/distributed teams: multi-language support praised by EU enterprise reviewer (S12); EU data residency now GA plus Dublin office (S15); ex-Workday VP EMEA hire (S11).
- Support response time under 4 hours (S22).
- New surface area: Pulse survey add-on out of beta (S23), Microsoft Teams app v2 in public preview (S19).

## 4. Where we win
- Head-to-head record: 13 wins vs 7 losses (table below); the one deal with a stated reason: 800-seat prospect picked Bonusly over Rivally citing analytics depth (S25, 2026-09-03, just past the table window).
- Documented Rivally seams to attack (gap inference, not direct comparisons): limited analytics (S02), basic dashboards vs enterprise tools (S07), CSV-only analytics exports making migration off Rivally hard (S20), admin tooling lagging peers (S16), no bulk recognition editing (S24), no SCIM provisioning with painful manual user management (S10), EMEA rewards catalog thinner than their US catalog (S14).
- Only snippet putting both in one evaluation: prospect chose to evaluate both; Rivally pitched EU data residency in Feb 2026 (S05) — before it was GA (S15).

## 5. Objections and responses
- "Rivally is cheaper." -> List rose $5 to $7 on 2026-08-12 (S17); quoted pricing varies ($6.50/500 seats, S13; $7 list less 15% on 3-year, S18). No Bonusly pricing in the provided data — do not claim we are cheaper; anchor on their increase and variable quoting.
- "They have EU data residency / EU strength." -> True now: GA 2026-07-01 with Dublin office (S15), multi-language praised (S12). Counter: EMEA catalog thinner than US (S14), no SCIM (S10), no bulk editing (S24), analytics weak (S02, S07, S20).
- "Setup is fast, Slack works out of the box." -> Conceded, sourced to one mid-market reviewer (S04). Counter: admin tooling still lags peers (S16), lacks bulk recognition editing (S24), lacks SCIM (S10).
- "Their recognition feed is engaging." -> Conceded (S02, S16). Counter: the same reviews note limited analytics (S02); exports are CSV-only and hard to migrate from (S20).
- "They are enterprise-ready." -> Counter: enterprise reviewer reports no SCIM provisioning and painful manual user management (S10).

## 6. Recent changes (dated)
- 2025-11-04: $40M Series C led by Northgate Ventures (S01).
- 2026-03-05: Rivally Pulse engagement survey add-on launched (S06); exited beta 2026-09-01, priced as add-on, not bundled (S23).
- 2026-05-09: hired ex-Workday VP EMEA to lead European expansion (S11).
- 2026-07-01: Dublin office opened; EU data residency generally available (S15).
- 2026-08-12: Recognition Starter $5 -> $7/user/month, annual billing (S17; prior S03, S08).
- 2026-08-20: Microsoft Teams app v2 in public preview (S19).

## 7. 12-month win/loss vs Rivally (2025-09 through 2026-08, 12 months)
| Month | W | L | Deals |
|---|---|---|---|
| 2025-09 | 1 | 1 | W Deal-072E31; L Deal-7767F5 |
| 2025-10 | 2 | 0 | W Deal-A9FD43, Deal-F65C8F |
| 2025-11 | 1 | 1 | W Deal-7AA785; L Deal-D263E0 |
| 2025-12 | 1 | 1 | W Deal-44C524; L Deal-935746 |
| 2026-01 | 2 | 0 | W Deal-0D0CD6, Deal-E46EAB |
| 2026-02 | 2 | 0 | W Deal-D5B790, Deal-1D2392 |
| 2026-03 | 1 | 1 | W Deal-5C636E; L Deal-9066A6 |
| 2026-04 | 0 | 2 | L Deal-5645A5, Deal-72A02F |
| 2026-05 | 0 | 1 | L Deal-C6FFAA |
| 2026-06 | 1 | 0 | W Deal-67BE14 |
| 2026-07 | 1 | 0 | W Deal-1B6969 |
| 2026-08 | 1 | 0 | W Deal-F03E7B |

Arithmetic: W = 1+2+1+1+2+2+1+0+0+1+1+1 = 13; L = 1+0+1+1+0+0+1+2+1+0+0+0 = 7; total = 13+7 = 20; win rate = 13/20 = 0.650 = 65%.
Trend: 3 of 7 losses landed Apr–May 2026 (Deal-5645A5, Deal-72A02F, Deal-C6FFAA); Jun–Aug all wins (3). No loss reasons are sourced in the provided data; the only sourced reason in either direction is S25 (analytics depth, Sep 2026).

## Excluded as rep opinion (not competitor facts)
S09 (Bryce Harmon, UI clunky — self-labeled unverified) and S21 (Elena Sinclair, discounting aggressively — self-labeled not confirmed). Neither used above.

## Old-card audit
- "Points-based recognition for mid-market": verified partially — points-based (S02); mid-market evidenced only by one reviewer's segment (S04), while enterprise reviewers also exist (S10, S12).
- "Pricing $5/user/month (2026-01)": superseded — $7 as of 2026-08-12 (S17).
- "Rivally lacks a Slack integration": contradicted — Slack integration worked out of the box (S04). Removed.
- "Acquired by WorkHuman in 2025": UNVERIFIED — no provided snippet mentions any acquisition; S01 instead shows an independent $40M Series C led by Northgate Ventures (2025-11-04).
- "Strong in EU enterprise with multi-language support": verified with nuance (S12), counterweighted by thinner EMEA rewards catalog (S14); data residency was only a pitch in Feb (S05) until GA in Jul (S15).
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.0015 · 222s · in 335 / out 5,178 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 (2026-07-01 to 2026-09-30). Days elapsed: 66/92 = 71.7%; 26 days remain. So-what: only SQMs are ahead of pace; DS2s and same_quarter_closes are the furthest behind, closed-lost MIA rate is 2x target, and pipeline coverage is 75% of target.

Linear pace expectation = target x (66/92) = target x 0.717.

| Metric | QTD actual | Target | Delta vs target | % of target | Pace verdict |
|---|---|---|---|---|---|
| SQMs | 230 | 300 | -70 | 76.7% | Ahead: 230 vs 215.2 expected (+14.8) |
| SQOs | 84 | 120 | -36 | 70.0% | Behind (marginal): 84 vs 86.1 expected (-2.1) |
| DS2s | 40 | 75 | -35 | 53.3% | Behind: 40 vs 53.8 expected (-13.8, -25.7%) |
| closed_lost_mia_rate | 20.0% (closed_lost_mia 5 / closed_lost_total 25) | 10.0% | +10 pts (adverse) | 2.0x target | Behind; lower_better, no linear pace applies |
| same_quarter_closes | 10 | 20 | -10 | 50.0% | Behind: 10 vs 14.3 expected (-4.3, -30.3%) |
| active_pipeline | $3,000,000 | $4,000,000 | -$1,000,000 | 75.0% | Ahead of elapsed pace: $3.0M vs $2.87M expected (+$130K), but $1.0M short of full-quarter coverage |

What moved this week: the source files are point-in-time QTD snapshots only, with no prior-week figures, so week-over-week movement cannot be computed from the data provided. The day-66 read is that SQMs (230 vs 215.2 linear expectation) are the one metric ahead of the clock, SQOs (84 vs 86.1) are marginally off pace, DS2s (40 vs 53.8) and same_quarter_closes (10 vs 14.3) are the largest gaps at roughly 26% and 30% behind elapsed pace respectively, closed_lost_mia is running at 5 of 25 closed-lost deals (20%, double the 10% ceiling), and active_pipeline at $3.0M covers 75% of the $4.0M target. Which of these improved or slipped versus last week is not determinable without a prior-week snapshot.
communication 5 tests
ceo-slack-compressionPASS 1.00
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.0018 · 263s · in 708 / out 6,316 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
Q3 weighted forecast is 115,976.75: 44,729 COMMIT (7 deals, 100% weight) plus 71,247.75 from 35% of 24 BEST_CASE deals (203,565); 23 PIPELINE deals count zero; 54 of 86 deals close in quarter. 32 deals worth 227,575 land after 2026-09-30, including COMMIT Deal-D348E1 (13,770, dated 2026-10-15). Caveat: owner is blank on 85 of 86 deals and why-buys on all 7 COMMIT deals, so the 44,729 base has no documented reason to buy and no per-rep quota check.
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.0013 · 178s · in 474 / out 4,327 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: Deal-0D2F7A follow-up

Hello,

I'm following up on the July 28 demo with your People team (VP People plus two HR admins). Automated milestone awards and the points catalog got a strong reaction, and you asked for pricing at the end.

Birthdays and anniversaries are still tracked manually today, and the recognition budget sits with the VP People, so the fit for your 150 employees is clear.

My ask: can we book a 15-minute call this week or next to confirm pricing for 150 seats and agree next steps on Deal-0D2F7A ahead of the 2026-11-26 close date?

If timing has moved, reply with a window that suits you.

Best,
Alex Franklin

Word count (body, excluding signature greeting/Subject line): 104. Under 120. Referenced touch: ENG-00002 (2026-07-28 demo); supporting facts from ENG-00003 and the deal row. No invented names, amounts, or dates.
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.0005 · 47s · in 295 / out 837 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.** 46 SQMs landed against a 52 target, a 6-SQM miss (6/52, about 12% under). Webinar carried the week: 18 of 46 SQMs, roughly 39%. Paid search cost per SQM held flat at $150, so the gap is volume, not efficiency.

**Sales.** 14 SQOs converted, 9 DS2 meetings set, and 3 same-quarter closes. New pipeline created totaled $310,000, about $22,100 per converted SQO ($310,000/14). Close count of 3 sets up next week's same-quarter story.

**CS.** 2 renewals saved. Team NPS moved to 61. 3 open red-flag accounts head into next week, the main watch item.

**PLG.** 412 new signups at 31% activation, so roughly 128 activated accounts (412 x 0.31). 38 companies reached the aha moment of 10 recognition gives.

No data gaps in the extracts. No contact names or employee details included.
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.0006 · 65s · in 513 / out 1,273 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

Partner-sourced pipeline: 5 deals, $550,000 total
Arithmetic: $180,000 + $95,000 + $140,000 + $60,000 + $75,000 = $550,000 (5 deals, all utm_source = Partner)

Active partners
- Apex Rewards Co — 2 sourced opps, $275,000 ($180,000 + $95,000). Deals: Deal-DDAAF2, Deal-2CF33E. Both in DS1 per Slack; co-webinar locked for 09-15; both logged with UTM Source = Partner. Deal count and amount match deal data.
- HRCloud Partners — 1 sourced opp, $140,000. Deal: Deal-F1CDA5. Integration referral closed security review; opp moved to DS2. Matches deal data.
- CultureBridge — 2 sourced opps, $135,000 ($60,000 + $75,000). Deals: Deal-096E1D, Deal-067213. Both early stage per lunch-and-learn. Matches deal data.
- WorkWell Group — 0 sourced deals, $0 this period. Wants to restart joint playbook in Q4; planning call booked for 09-09. Matches deal data (no WorkWell rows).

Quiet partners
- Recogniq — no activity in the provided data for this period.
- KudosWave — no activity in the provided data for this period.
- PeopleFirst Advisors — no activity in the provided data for this period.
- TotalPerk — no activity in the provided data for this period.

Missing data note: deal stage beyond the Slack mentions (DS1/DS2/early stage) is not in partner_deals.csv; close dates and currency are not provided. No other fields exist to report.
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.0005 · 40s · in 491 / out 734 tok
✓ answered_count✓ unanswerable_flagged✓ citations✓ no_guess

✓ Correct Answer (ground truth)

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

Model's actual answer

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

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

**Q3** — Yes. We maintain a SOC 2 Type II report, renewed annually. It is available to prospects under NDA. [P2]

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

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

**Q6** — Yes, SAML 2.0 single sign-on is supported, available on the Enterprise plan (SCIM user provisioning is also available on that plan). [P5]

**Q7** — Production databases are backed up daily; backups are encrypted and retained for 35 days. [P6]

**Q8** — Unanswerable from these excerpts. The excerpts state nothing about ISO 27001. The document that would answer it: the compliance/certifications section of the trust portal (or an ISO 27001 certificate/certification scope document).

**Q9** — Unanswerable from these excerpts. The excerpts state no uptime SLA percentage. The document that would answer it: the service-level agreement (SLA)条款 within the MSA/contract terms or the trust portal's SLA page.

**Q10** — Unanswerable from these excerpts. The excerpts say nothing about HIPAA BAAs. The document that would answer it: our BAA policy/legal terms documentation, or a direct answer from the legal/compliance team.

No arithmetic was required for these items; all figures above are verbatim from the cited excerpts. No facts beyond the excerpts were used.
ops-maintenance 4 tests
runbook-from-slack-threadPASS 1.00
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.0018 · 292s · in 747 / out 6,293 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
# Runbook — reward-worker queue incident #incident-2026-08-29-reward-queue

Source: incident_thread.md only. Window: 14:02:10Z → 14:55:00Z on 2026-08-29 (52m50s). Trigger: PagerDuty alert, reward-worker queue depth > 10k [M01]. All times UTC as given.

## Steps

S1 [M01] 14:02:10Z — Acknowledge PagerDuty alert; take incident commander (IC).
- Who: Bryce Harmon. Exact ack action: not stated — needs confirmation.
- Verification: none stated. Rollback: n/a (role/ack only).

S2 [M02] 14:04:33Z — Diagnostic: `bundle exec rake sidekiq:queue_depth`
- Who: Farid Osman. Result: reward queue 48,213 pending (normal under 500).
- Read-only. Verification: the command output itself. Rollback: n/a.

S3 [M03] 14:06:02Z — Inspect dead set: 112 jobs, all Redis::TimeoutError, from around 13:58.
- Who: Farid Osman. Exact command: not stated — needs confirmation.
- Read-only. Verification: none stated. Rollback: n/a.
- Note: thread does not state whether these 112 jobs are part of the 48,213 pending or separate.

S4 [M04] 14:08:45Z — Pause enqueue: `bin/rails runner 'FeatureFlag.disable(:auto_recognition_enqueue)'`
- Who: Farid Osman. State change: yes.
- Rollback (stated in thread): `bin/rails runner 'FeatureFlag.enable(:auto_recognition_enqueue)'`
- Verification immediately after: none stated. Later evidence (S7) cannot be attributed to this step alone (see below).

S5 [M05] 14:15:20Z — Clear out the dead set.
- Who: Elena Sinclair ("While I was in the console"). Exact command, which console, verification, and rollback: all not stated — needs confirmation. Deleted-job restorability not addressed in thread.
- State change: yes (destructive).

S6 [M06] 14:21:07Z — Scale workers up: `kubectl scale deployment/reward-worker --replicas=6` (was 3)
- Who: Bryce Harmon. State change: yes.
- Rollback (stated in thread): `kubectl scale deployment/reward-worker --replicas=3`
- Verification immediately after: none stated.

S7 [M07] 14:33:41Z — Progress check: queue depth 9,400 and falling ~1,200/min.
- Who: Farid Osman. Measurement command not restated in M07 — needs confirmation (S2/S8 used the rake task above; do not assume it here).
- Arithmetic: 48,213 − 9,400 = 38,813 jobs cleared over 14:04:33Z→14:33:41Z (29m08s) ≈ 1,332/min average (enqueue paused at this point). Attribution: follows S4+S5+S6 combined — the thread does not isolate which change produced the drop.

S8 [M08] 14:47:55Z — Verify recovery: `bundle exec rake sidekiq:queue_depth` returns 0; Datadog error rate back to baseline.
- Who: Cole Ingram. Read-only checks. "Baseline" threshold/value for the error rate: not stated.
- Arithmetic: at a sustained ~1,200/min (S7), 9,400 jobs would drain in ~7.8 min (≈14:41:31Z); 0 was observed at 14:47:55Z (~14m14s after S7), so the rate was not sustained — thread gives no explanation. Overall average 14:04:33Z→14:47:55Z (43m22s): 48,213 ÷ 43.37 min ≈ 1,112/min.

S9 [M09] 14:49:10Z — Re-enable enqueue: `bin/rails runner 'FeatureFlag.enable(:auto_recognition_enqueue)'`
- Who: Bryce Harmon. State change: yes.
- Verification (stated): 40 new jobs processed cleanly in the next 3 minutes.
- Rollback: none stated in M09; the inverse command exists in the thread at M04 (`FeatureFlag.disable(:auto_recognition_enqueue)`).

S10 [M10] 14:55:00Z — Scale workers down: `kubectl scale deployment/reward-worker --replicas=3`
- Who: Bryce Harmon. State change: yes.
- Verification (stated): queue stable at 0; incident resolved declared here.
- Rollback: none stated in M10; the inverse command exists in the thread at M06 (`--replicas=6`).

## Needs confirmation (consolidated)

1. S1: exact PagerDuty acknowledgment action.
2. S3: exact dead-set inspection command.
3. S5: exact clear command, which console, verification, rollback/restorability.
4. S7: queue-depth measurement command not restated.
5. S4, S6: no immediate post-change verification stated; recovery is only evidenced in aggregate.
6. Attribution of the recovery among S4/S5/S6 is not established by the thread.
7. Datadog "baseline" error-rate value/threshold.
8. Whether the 112 dead-set jobs overlap the 48,213 pending count.

Nothing else added — every step above traces to its [Mxx] message; all gaps are marked, not filled.
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.0019 · 290s · in 2,128 / out 6,325 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 (origin point)
- 2026-09-03T14:01:12Z, reward-service, ERROR: "Redis::TimeoutError: Connection to Redis at redis-primary:6379 timed out after 5s"
- Last healthy reward-service log before it: 13:59:09Z health check ok. Quiet gap = 2m03s.
- Message says the connection attempt timed out after 5s, so the attempt began ~14:00:57Z (derived from message text, not a logged event).

Cascade in order
1. 14:01:12Z reward-service ERROR — initial Redis timeout to redis-primary:6379
2. 14:01:20Z reward-service ERROR — retry exhausted for RewardGiveJob (+8s)
3. 14:01:30Z reward-service ERROR — retry exhausted for RewardGiveJob (+10s)
4. 14:01:40Z reward-service ERROR — retry exhausted for RewardGiveJob (+10s); same second, sidekiq ERROR "RewardGiveJob failed: Redis::TimeoutError; retrying in 60s" (order within that second not determinable from the data)
5. 14:01:46Z–14:01:57Z — first batch of 6 RewardGiveJob failures in sidekiq_jobs.csv (J-00005, J-00001, J-00003, J-00006, J-00002, J-00004)
6. 14:02:28Z sidekiq ERROR — RewardGiveJob failed; retrying (+48s after 14:01:40)
7. 14:02:30Z sidekiq WARN — "Queue reward depth above 10,000" (78s after first error)
8. 14:02:36Z–14:05:50Z — 4 RecognitionDigestJob failures (J-00013–J-00016), also Redis::TimeoutError
9. 14:02:51Z–14:02:58Z — second batch of 6 RewardGiveJob failures (J-00007, J-00008, J-00009, J-00010, J-00011, J-00012)
10. 14:03:05Z api-gateway ERROR — 502 upstream timeout calling reward-service /gives (first API-layer impact, 1m53s after first error)
11. 14:03:30Z web-app ERROR — Give form submission failed: upstream 502 from api-gateway (first customer-facing error, 2m18s after first error)
12. Retry waves continue: sidekiq retries at 14:03:31, 14:04:22, 14:05:26, 14:06:47 (intervals 63s, 51s, 64s, 81s — consistent with the stated 60s retry cadence); api-gateway 502s at 14:03:48, 14:04:13, 14:05:16, 14:06:52; web-app failures at 14:04:45, 14:05:42, 14:06:49
13. Last error: 14:06:52Z. User-facing 502 window = 3m47s (5 gateway errors, 4 web-app errors).
14. 14:10:56Z–14:14:40+ postgres INFO checkpoints only — no postgres errors in the slice.
15. Recovery: 14:22:10Z reward-service INFO "Redis connection restored; resuming job processing" (20m58s after first error); 14:24:45Z sidekiq INFO queue depth below 500 (+2m35s to drain).

Service and job involved
- Failing dependency: redis-primary:6379. Failing service: reward-service (4 of its log lines are ERROR).
- Job: RewardGiveJob (12 of 16 failures in sidekiq_jobs.csv; the only job named in datadog_logs.csv). Secondary job: RecognitionDigestJob (4 failures, 14:02:36Z–14:05:50Z) — appears only in sidekiq_jobs.csv, never in the log slice.

Datadog query to confirm the first error
```
service:reward-service status:error "Redis::TimeoutError"
```
Time range 2026-09-03T14:00:30Z–14:02:00Z, sort timestamp ascending. Expected result: exactly one record at 14:01:12Z matching "Connection to Redis at redis-primary:6379 timed out after 5s". Confirmation it is the first error: same query over 13:55:00Z–14:01:12Z returns zero rows.

What the logs do not show
- The cause of the Redis outage itself. No redis service logs exist in the slice — crash, GC pause, network partition, failover, or restart are all undetermined.
- No host, region, version, trace ID, request ID, user ID, or give/reward IDs — affected users and specific gives cannot be identified.
- RewardGiveJob retry outcomes after the 14:22:10Z restore — no success lines for the job; only "resuming job processing" and queue depth below 500.
- Sidekiq retry events at 14:03:31Z, 14:04:22Z, 14:05:26Z, 14:06:47Z have no matching rows in sidekiq_jobs.csv (that file ends at 14:05:50Z) — the two sources do not fully reconcile.
- Peak queue depth — only threshold crossings (above 10,000 at 14:02:30Z, below 500 at 14:24:45Z).
- No metrics (error rate, latency percentiles) — log lines only.
- Postgres shows only INFO checkpoints; no postgres errors, but absence of logs is not proof of health.
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.0007 · 77s · in 540 / out 1,331 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 summary (9 flags in export; 6 have code references, 3 do not).

Flags with code references (flag_code.md):

1. recognition_streaks_v2 — ON — segment:beta_companies — 42 companies
   app/models/recognition.rb: gates StreakTracker.record(give)

2. points_budget_guardrails — ON — all_companies — 220 companies
   app/services/budget_service.rb: gates BudgetService.new(company).enforce!(giver, points)

3. slack_dm_nudges — ON — segment:region_na — 87 companies
   app/jobs/nudge_job.rb: return unless enabled, then SlackDm.send_nudge(user)

4. redeem_flow_redesign — OFF — targeted_list — 12 companies
   app/controllers/redeem_controller.rb: enabled renders RedeemV2Component, else RedeemV1Component. Flag is off, so all companies (incl. the 12 on the list) render V1 per the excerpt.

5. analytics_dashboard_v3 — ON — segment:tier_three — 65 companies
   app/controllers/analytics_controller.rb: gates @dashboard = AnalyticsV3.new(company)

6. ms_teams_app_v2 — OFF — targeted_list — 9 companies
   app/services/teams_installer.rb: gates TeamsAppV2.install(company). Off, so no installs via this path.

Flags with NO code reference in the excerpt (state/targets from export only):

7. legacy_give_modal — OFF — segment:legacy_plan — 14 companies. No code reference, so what it controls is not shown.
8. survey_boosters_q3 — ON — segment:legacy_plan — 7 companies. No code reference, so what it controls is not shown.
9. paused_offboard_cleanup — OFF — no targeting rules (empty field) — 0 companies. No code reference and no targets.

Notes:
- The export gives segment labels and counts, not company names, so "which companies" can only be reported as the segment plus count above.
- Counts as given: ON flags total 42+220+87+65+7 = 421; OFF flags total 12+9+14+0 = 35; combined 456. Overlap between segments (e.g., legacy_plan appears in two flags) cannot be ruled out from the data, so 456 is a sum of per-flag counts, not necessarily unique companies.
- No flags were added or inferred beyond the 9 in the export.
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.0007 · 78s · in 551 / out 1,612 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 eval NDA: term 2 yrs + 3-yr survival (max exposure 2 + 3 = 5 yrs from Effective Date, clause 2), full standard carve-outs quoted in clause 3 ("(a) is or becomes publicly available through no breach, (b) was known prior to disclosure, (c) is received from a third party without duty of confidence, (d) is independently developed, or (e) must be disclosed by law or court order"), Delaware law (clause 4), no restrictive covenants (clause 5).

NDA-2 — YELLOW. Clauses 1–3 are standard (mutual, 3-yr term, standard carve-outs, Delaware), but it embeds a mutual 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." (clause 4) — total restrictive window 3 + 1.5 = 4.5 yrs from Effective Date; counsel to confirm the hiring ban's scope and whether Bonusly accepts it.

NDA-3 — RED. Four compounding defects, each quoted: one-way protection only — "One-way confidentiality in favor of [PARTY C]" gives Bonusly no reciprocal safeguard (clause 1); embedded 3-yr non-compete — "For a period of three (3) years following the Effective Date, Recipient shall not, directly or indirectly, engage in or provide services to any business that competes with Discloser's business." (clause 2); absolute obligation, no exceptions — "No confidentiality carve-outs are stated in this Agreement." (clause 4); non-US law and forum — "governed by and construed in accordance with the laws of the Republic of Ireland, and the parties submit to the exclusive jurisdiction of its courts." (clause 3), on top of an unusual 5-yr term (clause 1). Full legal review before any signature.

Tally: 1 GREEN (NDA-1), 1 YELLOW (NDA-2), 1 RED (NDA-3).