Mean 0.885 · 23/34 perfect tests · $0.38 total · 34/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
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.
**Definitions** - DS2+ deal: a deal whose stage is DS2, DS3, DS4, or DS5. - Substantive why-buys: non-empty text of 15+ characters; LONG(n) format counts as substantive (per the LONG(n) rule). - DS1 timestamp: the t_ds1 column value for a deal. - Stage regression: an earlier-stage timestamp (e.g., t_ds1) is later than a later-stage timestamp (e.g., t_ds2), i.e., stage entry order is out of sequence. - Owner: resolved from owner_id via the owners table (Gavin Porter, Hugo Lindqvist, Bryce Harmon, Dana Mercer, Alex Franklin, Cole Ingram, Farid Osman, Elena Sinclair). **Hygiene results (156 total deals; 124 DS2+)** - DS2+ deals with non-substantive why-buys: **101 / 124 = 81.5%** - By owner (DS2+ non-compliance): - Alex Franklin: 48 - Cole Ingram: 19 - Dana Mercer: 18 - Bryce Harmon: 15 - Farid Osman: 1 - Deals missing a DS1 timestamp: **0** - Deals with regressed stage timestamps: **0** **Process fixes** 1. **Mandatory why-buys at pipeline intake** — every DS2+ deal must carry a substantive why-buys value (15+ characters or LONG(n)); reject or flag empty/placeholder entries at creation. 2. **Stage-transition ordering guardrail** — validate that stage entry timestamps are chronologically ordered (t_ds1 ≤ t_ds2 ≤ t_ds3 ≤ t_ds4 ≤ t_ds5) before allowing a deal to advance past DS2; flag or auto-reject regressions. 3. **DS1 timestamp gate** — require a non-empty t_ds1 on pipeline entry; deals without a DS1 timestamp cannot be marked as DS2+.
**Deal resolution results (280 open deals)** | Metric | Value | |---|---| | Deals resolved | **280** (all owner_ids matched) | | Deals with no owner_id match in owners table | **0** | **Unmatched deal IDs:** none — every owner_id in the deal extract (119337721, 83155923, 84342457, 83155924, 716654662, 701163055) maps to a row in the owners table. **Owner IDs mapping to archived/deactivated owners:** none of the resolved deals point to an archived owner. For reference, the archived/deactivated owners in the owners table are: - 1520255671 → Gavin Porter (archived) - 77260721 → Hugo Lindqvist (archived) **Total pipeline amount per resolved owner:** | Owner | Amount | |---|---| | Alex Franklin | $1,260,390.00 | | Bryce Harmon | $1,494,776.00 | | Cole Ingram | $577,138.18 | | Dana Mercer | $545,094.00 | | Elena Sinclair | $2,100.00 | | Farid Osman | $17,703.00 | | **Total** | **$3,897,195.18** | All amounts are sums of `amount` across the resolved deals per owner name. No name was invented for any unmatched ID (there were none).
Here is the integrity report based on the provided data. **(a) Orphan rows — gong deal ids with no match in deals_open** - **Count: 30** out of 67 gong rows (45% of the gong table). - Sample aliases (exact as given): `Deal-B038F0`, `Deal-9A43B4`, `Deal-D84A2D`, `Deal-51EA1A`, `Deal-36EA09`, `Deal-76821A`, `Deal-344163`, `Deal-3B6668`, `Deal-5592CC`, `Deal-8FA85D`. **(b) Duplicate conversation keys — rows where calls_90d exceeds distinct_conversation_keys** - **Count: 0.** Every row in the gong table has calls_90d equal to distinct_conversation_keys (67/67). No row has calls_90d > distinct_conversation_keys. **(c) Open deals at DS3 or later — share with at least one logged call** - Open deals at DS3 or later: **85** (out of 156 total open deals). - Of those 85, **all 85 have at least one logged call** (each has a non-empty value in at least one of the t_ds1–t_ds5 stage columns). - **Share: 100%.** Stage breakdown of the DS3+ set: DS3 = 61 deals (all 61 logged), DS4 = 14 deals (all 14 logged), DS5 = 10 deals (all 10 logged). Notes on the data as given: gong_owner_id values (e.g., 4729257026550273695, 5886696740382085504) are Gong user IDs, not HubSpot owner IDs — they are used here only for the orphan/duplicate checks, not for owner mapping. ⚠️ File-mutation verifier: 1 file edit(s) FAILED this turn despite any wording above that may suggest otherwise. Run `git status` or `read_file` to confirm what actually landed. • `/Users/amaniphipps/gong_calls_by_deal_90d.csv` — [write_file] Refusing to overwrite `/Users/amaniphipps/gong_calls_by_deal_90d.csv`: `/Users/amaniphipps/gong_calls_by_deal_90d.csv` exists but this task has not seen its full current content (neve…
```sql
-- Per customer company: first calendar month as a customer, unique givers, recognition count, successful redemption count
-- Table choices:
-- PRODUCTION.PLG.COMPANY_COHORT_SUMMARY: company list and first customer month (ACTIVATED_DATE or SIGNUP_DATE)
-- PRODUCTION.HUBSPOT.HS_ENGAGEMENTS_ENRICHED: recognition events (engagements) per company
-- PRODUCTION.DEPRECATED_RECOGNITION.REDEMPTION_RECORDS_V2: redemption events (only STATE='succeeded' counts)
WITH company_first_month AS (
SELECT
company_id,
TO_CHAR(TO_DATE
```sql
-- Per customer company: first calendar month as a customer, unique givers, recognition count, successful redemption count
-- Table choices:
-- PRODUCTION.PLG.COMPANY_COHORT_SUMMARY: company list with first customer month (ACTIVATED_DATE)
-- PRODUCTION.HUBSPOT.HS_ENGAGEMENTS_ENRICHED: recognition events per company (OWNER_ID = giver)
-- PRODUCTION.DEPRECATED_RECOGNITION.REDEMPTION_RECORDS_V2: redemption events (STATE='succeeded' only)
-- Note: a documented filter excluding deleted givers exists in some giving queries; per business rules, it must NOT be applied to historical giving counts (recognition/redemption counts), so all givers are included.
WITH company_first_month AS (
-- Company's first calendar month as a customer, derived from the activation date
SELECT
company_id,
TO_CHAR(TO_DATE(ACTIVATED_DATE)) AS first_customer_month
FROM PRODUCTION.PLG.COMPANY_COHORT_SUMMARY
)
SELECT
cfm.company_id,
cfm.first_customer_month,
COUNT(DISTINCT eng.OWNER_ID) AS unique_givers,
COUNT(eng.ENGAGEMENT_ID) AS recognition_count,
COUNT(CASE WHEN rr.STATE = 'succeeded' THEN 1 END) AS successful_redemption_count
FROM company_first_month cfm
-- Recognition events: each engagement record represents a recognition (giver action)
LEFT JOIN PRODUCTION.HUBSPOT.HS_ENGAGEMENTS_ENRICHED eng
ON cfm.company_id = eng.COMPANY_ID
-- Redemption events: only STATE='succeeded' rows count as redemptions
LEFT JOIN PRODUCTION.DEPRECATED_RECOGNITION.REDEMPTION_RECORDS_V2 rr
ON cfm.company_id = rr.COMPANY_ID
GROUP BY cfm.company_id, cfm.first_customer_month;
```
## Classification of all 90 lost deals (last 6 months)
| Deal Alias | Tag | Primary Category | Side |
|---|---|---|---|
| Deal-DB0AAC | Lost- Timing (1 year or more) | timing | unknown |
| Deal-F7F635 | Competitor | competitor | bonusly |
| Deal-AC944F | MIA | no_decision | buyer |
| Deal-214060 | MIA | no_decision | buyer |
| Deal-91A056 | Lost- Timing (1 year or more) | timing | unknown |
| Deal-29326C | Lost- Timing (1 year or more) | timing | unknown |
| Deal-5DB9B0 | Lost- Does not fit ICP (write in notes) | product_gap | unknown |
| Deal-831B7B | Lost- Timing (1 year or more) | timing | unknown |
| Deal-F97C37 | Competitor | competitor | unknown |
| Deal-13E9CF | Doing nothing/Not a priority/Cost | no_decision | unknown |
| Deal-39E25C | Lost- Timing (1 year or more) | timing | unknown |
| Deal-7ED004 | Lost- Budget/Price | pricing | unknown |
| Deal-21B045 | MIA | no_decision | buyer |
| Deal-B3ABED | Lost- Timing (1 year or more) | timing | buyer |
| Deal-422BA6 | Competitor | competitor | bonusly |
| Deal-ED9AE7 | Lost DM | no_decision | unknown |
| Deal-988493 | MIA | no_decision | buyer |
| Deal-381C8C | Competitor | competitor | bonusly |
| Deal-F308CA | MIA | no_decision | buyer |
| Deal-F1E8A6 | Competitor | competitor | bonusly |
| Deal-B6AC09 | Lost- Timing (1 year or more) | timing | unknown |
| Deal-70F704 | Lost DM | no_decision | buyer |
| Deal-E6E80A | Lost- Timing (1 year or more) | timing | unknown |
| Deal-B038F0 | Lost- Timing (1 year or more) | timing | unknown |
| Deal-4664E1 | MIA | no_decision | buyer |
| Deal-175756 | Lost- Timing (1 year or more) | timing | unknown |
| Deal-E74A73 | Doing nothing/Not a priority/Cost | no_decision | unknown |
| Deal-DDAB52 | Competitor | competitor | unknown |
| Deal-ACE061 | Competitor | competitor | unknown |
| Deal-BB78F3 | Lost- Timing (1 year or more) | timing | bonusly |
| Deal-D48E0B | MIA | no_decision | buyer |
| Deal-15DA99 | Lost- Timing (1 year or more) | timing | unknown |
| Deal-F4AF5D | Lost- Timing (1 year or more) | timing | unknown |
| Deal-79B7A1 | Lost- Timing (1 year or more) | timing | unknown |
| Deal-583ADB | MIA | no_decision | buyer |
| Deal-8E27DA | Feature Request | product_gap | unknown |
| Deal-2D2F8D | Competitor | competitor | unknown |
| Deal-E0441F | MIA | no_decision | unknown |
| Deal-7CB44D | MIA | no_decision | buyer |
| Deal-0F96AA | Competitor | competitor | bonusly |
| Deal-1BCA50 | Competitor | competitor | unknown |
| Deal-7CC678 | Competitor | competitor | unknown |
| Deal-FAC17C | Lost DM | no_decision | unknown |
| Deal-242273 | Competitor | competitor | unknown |
| Deal-50E5D8 | Doing nothing/Not a priority/Cost | no_decision | unknown |
| Deal-A2C349 | Competitor | competitor | unknown |
| Deal-9F176A | Lost- Timing (1 year or more) | timing | unknown |
| Deal-7B2236 | Doing nothing/Not a priority/Cost | no_decision | unknown |
| Deal-AFA56C | MIA | no_decision | buyer |
| Deal-C7156E | Competitor | competitor | unknown |
| Deal-C33D91 | Lost- Budget/Price | pricing | buyer |
| Deal-9048EB | MIA | no_decision | buyer |
| Deal-5E64CE | Doing nothing/Not a priority/Cost | no_decision | bonusly |
| Deal-8A0992 | Competitor | competitor | unknown |
| Deal-D0C698 | Competitor | competitor | unknown |
| Deal-69CF3D | Lost- Timing (1 year or more) | timing | unknown |
| Deal-ECBF89 | Lost- Timing (1 year or more) | timing | unknown |
| Deal-3618CC | Lost DM | no_decision | unknown |
| Deal-EECC02 | Competitor | competitor | unknown |
| Deal-5AD03E | Competitor | competitor | unknown |
| Deal-D1A623 | Lost- Timing (1 year or more) | timing | unknown |
| Deal-413C56 | Doing nothing/Not a priority/Cost | no_decision | unknown |
| Deal-47F1A1 | Competitor | competitor | unknown |
| Deal-BF2A98 | Competitor | competitor | unknown |
| Deal-2A292B | Doing nothing/Not a priority/Cost | no_decision | unknown |
| Deal-D1AABF | MIA | no_decision | buyer |
| Deal-FEDBCB | Doing nothing/Not a priority/Cost | no_decision | unknown |
| Deal-1E7DA9 | Competitor | competitor | unknown |
| Deal-2BBA21 | MIA | no_decision | buyer |
| Deal-286F9C | Competitor | competitor | bonusly |
| Deal-7FBAC6 | Doing nothing/Not a priority/Cost | no_decision | bonusly |
| Deal-369281 | Competitor | competitor | unknown |
| Deal-386F6E | MIA | no_decision | buyer |
| Deal-9FCD0D | Competitor | competitor | unknown |
| Deal-55867E | Lost- Timing (1 year or more) | timing | bonusly |
| Deal-DAFB82 | Lost- Budget/Price | pricing | bonusly |
| Deal-2FEDDB | Doing nothing/Not a priority/Cost | no_decision | unknown |
| Deal-64B19A | Competitor | competitor | buyer |
| Deal-3F86A0 | MIA | no_decision | buyer |
| Deal-096750 | MIA | no_decision | buyer |
| Deal-F325A5 | Lost DM | no_decision | buyer |
| Deal-ABD14C | Doing nothing/Not a priority/Cost | no_decision | buyer |
| Deal-79E61A | MIA | no_decision | buyer |
| Deal-8A119B | Lost- Budget/Price | pricing | unknown |
| Deal-AE7C4E | MIA | no_decision | buyer |
| Deal-DAB4F1 | MIA | no_decision | buyer |
| Deal-B4B50F | MIA | no_decision | buyer |
| Deal-981AD4 | Feature Request | product_gap | unknown |
| Deal-DC77FE | Competitor | competitor | bonusly |
| Deal-5885B9 | MIA | no_decision | buyer |
## Summary
**Category counts (90 deals):**
- no_decision: 38
- competitor: 26
- timing: 19
- pricing: 4
- product_gap: 3
**Side split:**
- bonusly: 12
- buyer: 27
- unknown: 51
**Tag vs. free-text disagreement:** 2 deals
1. **Deal-F7F635** (Competitor) — reason: "the group decided to go in another direction... will definitely keep Bonusly in mind if an opportunity arises." Tag says competitor, but text explicitly states they're keeping Bonusly in mind.
2. **Deal-70F704** (Lost DM) — reason: "have been MIA - will reopen if they reach back out." Tag says lost, but text says they'll revisit.
**Two patterns most worth acting on:**
1. **Buyer-side non-engagement (MIA/unresponsive)** — 22 deals. These are tagged MIA or Lost DM, and the free text consistently shows the prospect is unresponsive, MIA, or has ignored outreach ("unresponsive," "no meaningful contact," "ignored multiple pieces of outreach"). The pattern is clear: prospects who have gone silent without a clear decision. Action: proactive re-engagement cadence for MIA contacts before they become permanently cold; improve lead follow-up processes and set outreach reminders at the point of silence.
2. **Timing-driven losses** — 19 deals tagged as "Lost- Timing (1 year or more)." The free text consistently cites timing blockers: "will reconnect in 2027," "pushed into early 2027," "put on hold until 2027," "waiting for budget in 2028," "timing, budget, authority." These prospects want the product but can't commit due to timing/budget constraints. Action: build a nurture sequence that triggers when budget cycles align (early 2027, Q2 2027); pre-qualify leads for timing-based re-engagement; set expectations upfront about timeline so the deal doesn't fall through the cracks.
```json
{
"tier_counts": {
"LOCK": 9,
"ACTION": 13,
"BUILD": 31,
"REVIVE": 0,
"WATCH": 53,
"RISKY": 50
},
"tier_examples": {
"LOCK": ["Deal-25F752", "Deal-C26D20", "Deal-944310"],
"ACTION": ["Deal-D73B89", "Deal-012CB1", "Deal-CA7DC0"],
"BUILD": ["Deal-66D1FC", "Deal-C5658B", "Deal-C9C286"],
"REVIVE": [],
"WATCH": ["Deal-D348E1", "Deal-3974EB", "Deal-6787C2"],
"RISKY": [
"Deal-E53952", "Deal-5408B0", "Deal-9AAE5F", "Deal-547B2B", "Deal-B7EBD1",
"Deal-A2B47C", "Deal-2465CE", "Deal-C61CF7", "Deal-62D607", "Deal-584EE5",
"Deal-C6D97A", "Deal-7B3B0F", "Deal-F9A08A", "Deal-0660B4", "Deal-1FC049",
"Deal-FD9F4E", "Deal-BA571A", "Deal-523604", "Deal-FC22A3", "Deal-01E193",
"Deal-C1FA6D", "Deal-93C8BF", "Deal-1CCE5C", "Deal-927338", "Deal-60C2C2",
"Deal-4A13AD", "Deal-8AD4A5", "Deal-15D24F", "Deal-9D0060", "Deal-690476",
"Deal-635B8E", "Deal-DCA846", "Deal-ED725A", "Deal-55164C", "Deal-819506",
"Deal-3BA5EA", "Deal-5FDCE4", "Deal-F336B6", "Deal-5EED42", "Deal-BA3DDC",
"Deal-7599B8", "Deal-F9A3C1", "Deal-FA32A0", "Deal-03BA69", "Deal-117863",
"Deal-F17780", "Deal-8BA24E", "Deal-2B39B0", "Deal-8FDCD2"
]
},
"risky_deals": [
"Deal-E53952", "Deal-5408B0", "Deal-9AAE5F", "Deal-547B2B", "Deal-B7EBD1",
"Deal-A2B47C", "Deal-2465CE", "Deal-C61CF7", "Deal-62D607", "Deal-584EE5",
"Deal-C6D97A", "Deal-7B3B0F", "Deal-F9A08A", "Deal-0660B4", "Deal-1FC049",
"Deal-FD9F4E", "Deal-BA571A", "Deal-523604", "Deal-FC22A3", "Deal-01E193",
"Deal-C1FA6D", "Deal-93C8BF", "Deal-1CCE5C", "Deal-927338", "Deal-60C2C2",
"Deal-4A13AD", "Deal-8AD4A5", "Deal-15D24F", "Deal-9D0060", "Deal-690476",
"Deal-635B8E", "Deal-DCA846", "Deal-ED725A", "Deal-55164C", "Deal-819506",
"Deal-3BA5EA", "Deal-5FDCE4", "Deal-F336B6", "Deal-5EED42", "Deal-BA3DDC",
"Deal-7599B8", "Deal-F9A3C1", "Deal-FA32A0", "Deal-03BA69", "Deal-117863",
"Deal-F17780", "Deal-8BA24E", "Deal-2B39B0", "Deal-8FDCD2"
],
"lock_violations": 0,
"pipeline_shape": "The open pipeline is dominated by PIPELINE-stage deals (105 of 156), with a smaller BEST_CASE (40) and COMMIT (11) cohort. Engagement signals are weak: 101 of 156 deals recorded zero meetings in the last 30 days, and 38 deals have missing contact counts. Risk is concentrated in 50 deals where the forecast category contradicts the engagement evidence (mostly BEST_CASE/COMMIT with no activity), while 9 LOCK deals have confirmed activity. The remaining 31 BUILD deals are early-stage with low contact counts, and 53 WATCH deals are PIPELINE with minimal activity; no REVIVE candidates exist because no DS4/DS5 deals show prior activity with zero meetings."
}
```
Score summary: 156 deals scored across 6 tiers — LOCK (9), ACTION (13), BUILD (31), REVIVE (0), WATCH (53), RISKY (50). No lock violations.
```json
[
{
"transcript_id": "TX-001",
"deal_alias": "Deal-CFE7F4",
"why_buys": ["Automating anniversary and birthday awards — our HR team of three cannot keep up with it manually."],
"pain_points": ["Tracking everything in a spreadsheet", "People slip through the cracks"],
"stakeholders": ["Prospect (VP People)", "Prospect (HR Admin)"],
"budget_signal": "$40k earmarked for engagement tools this fiscal year",
"timeline_signal": "Live before open enrollment in November",
"competitor_mentioned": "Achievers",
"next_step": "Security review on September 12",
"objections": ["Need SSO and audit logs for IT sign-off"],
"confidence": null
},
{
"transcript_id": "TX-002",
"deal_alias": "Deal-70BB30",
"why_buys": ["Tie recognition to retention for the hourly workforce — regretted turnover over 30%."],
"pain_points": ["Regretted turnover over 30% among hourly workforce"],
"stakeholders": ["Prospect (Head of Total Rewards)", "Prospect (CFO)"],
"budget_signal": "$25k pilot budget for this quarter",
"timeline_signal": "Decision by end of September",
"competitor_mentioned": null,
"next_step": "Send pilot agreement, route to legal this week",
"objections": ["Workday integration must be rock solid"],
"confidence": null
},
{
"transcript_id": "TX-003",
"deal_alias": "Deal-530B50",
"why_buys": ["Make recognition visible across 12 retail locations.", "Store managers have zero budget autonomy for on-the-spot recognition today"],
"pain_points": ["Store managers have zero budget autonomy for on-the-spot recognition today"],
"stakeholders": ["Prospect (People Ops Manager)"],
"budget_signal": "$8 per employee per month",
"timeline_signal": "No rush until Q1",
"competitor_mentioned": "Bucketlist",
"next_step": "Schedule a call with CEO — will send two times",
"objections": ["CEO has to be sold first — she decides anything people-related"],
"confidence": null
},
{
"transcript_id": "TX-004",
"deal_alias": "Deal-180D02",
"why_buys": ["Consolidate three separate recognition tools into one.", "None of them talk to our HRIS"],
"pain_points": ["Paying for three tools that do not talk to HRIS", "Security review took three months for last vendor — hesitation"],
"stakeholders": ["Prospect (VP People)", "Prospect (IT Security Lead)"],
"budget_signal": "Under $15k annually",
"timeline_signal": "Procurement cycle 6–8 weeks minimum; follow-up with CFO next week (tentative — VP said 'maybe, no promises')",
"competitor_mentioned": null,
"next_step": null,
"objections": ["Security review took 3 months for previous vendor"],
"confidence": null
},
{
"transcript_id": "TX-005",
"deal_alias": "Deal-F8767A",
"why_buys": ["Automate service milestones", "Provide analytics on recognition equity across departments", "Night-shift teams feel invisible — engagement scores run 20 points lower"],
"pain_points": ["Night-shift teams feel invisible — engagement scores run 20 points lower", "Exec team is skeptical after a failed rollout two years ago"],
"stakeholders": ["Prospect (HR Director)", "Prospect (People Ops Coordinator)"],
"budget_signal": "$12k approved under engagement line",
"timeline_signal": "Running before January all-hands; present to exec team on October 2",
"competitor_mentioned": "Nectar",
"next_step": "Present to exec team on October 2",
"objections": ["Exec team is skeptical after a failed rollout two years ago"],
"confidence": null
},
{
"transcript_id": "TX-006",
"deal_alias": "Deal-EE195F",
"why_buys": ["Cut the admin time on service awards.", "Spends 5 hours/month ordering and shipping plaques"],
"pain_points": ["Spends 5 hours/month ordering and shipping plaques", "Time is the constraint, not budget"],
"stakeholders": ["Prospect (HR Manager)"],
"budget_signal": "Flexible on pricing; time is the issue",
"timeline_signal": "Q1 start is realistic (fiscal year resets in February)",
"competitor_mentioned": null,
"next_step": "Send one-page overview, forward to COO this week",
"objections": ["COO prefers building things in-house"],
"confidence": null
}
]
```
All fields extracted from the transcripts as-is. No deals, companies, or numbers were invented. Key notes:
- **Confidence**: not stated in any transcript — set to `null` across all records.
- **Next step (TX-004)**: left `null` — the VP responded "maybe" and "no promises," so no explicit agreement was reached; the tentative follow-up with the CFO was not confirmed.
- **Competitors**: only raised when the prospect named them (Achievers, Bucketlist, Nectar). Workday in TX-002 is an integration requirement, not a competitor.
- **Pain points** were taken from prospect statements only (e.g., TX-003's "zero budget autonomy," TX-006's 5-hour/month admin time); rep statements were excluded from pain points.
Based on the CRM close dates and the Slack thread (2026-09-04), the three deals closest to signature are: 1. **Deal-547B2B** — $11,200 — Signature-imminent: redlines came back clean, the signing page is out, and Alex Franklin reported that VP People confirmed signing tomorrow. What's left: execute the signature. 2. **Deal-D348E1** — $13,770 — Warm, progressing at normal legal-review pace (per Alex Franklin). What's left: complete legal review and finalize. 3. **Deal-A2B47C** — $6,360 — Warm, progressing at normal legal-review pace (per Alex Franklin). What's left: complete legal review and finalize. Deal-2465CE was pulled from commit due to a procurement freeze (champion left, vendor freeze) and is no longer close. Deal-403845 is also moving fine with the order form in finance's hands, but the Slack thread groups D348E1 and A2B47C together as actively warming in legal review, making them the next closest after the imminent 547B2B.
## Per-candidate analysis **Deal-EC3025** - Prospect line: "We need SCIM user provisioning — our security team will not approve any tool that requires manual account management." - Classification: **Real gap** — SCIM user provisioning is not a supported capability (product docs: "SCIM user provisioning and ADP Workforce Now integrations are NOT currently listed as supported capabilities"). - Deal: Deal-EC3025 | Amount: not provided in data **Deal-D0D6B5** - Prospect line: "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** — ADP Workforce Now integration is not a supported capability (product docs: "ADP Workforce Now integrations are NOT currently listed as supported capabilities"). - Deal: Deal-D0D6B5 | Amount: not provided in data **Deal-CFE7F4** - Prospect line: "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** — custom report builder is only available on Enterprise tier (product docs: "Custom report builder" row shows "—" for Core and Pro, "yes" for Enterprise). - Deal: Deal-CFE7F4 | Amount: not provided in data **Deal-84DBA6** - Prospect line: "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** — Slack integration is supported on all tiers, but adoption/training is required (prospect: "nobody ever trained them on it"; Alex Franklin: "I'll set up a manager enablement session"). - Deal: Deal-84DBA6 | Amount: not provided in data **Deal-36C33F** - Prospect line: "Full transparency — we don't have a native mobile app for hourly workers yet, though it's on the roadmap." - Classification: **Rollout/enablement issue** — native mobile app is not yet delivered (product docs do not list a mobile app feature; prospect notes it is on the roadmap). - Deal: Deal-36C33F | Amount: not provided in data ## Summary of real gaps All five candidates raised genuine product gaps. Classified: 1. **Deal-EC3025** — Real gap: SCIM user provisioning not supported 2. **Deal-D0D6B5** — Real gap: ADP Workforce Now integration not supported 3. **Deal-CFE7F4** — Plan gate: custom report builder gated behind Enterprise 4. **Deal-84DBA6** — Rollout/enablement issue: Slack integration adopted/trained 5. **Deal-36C33F** — Rollout/enablement issue: native mobile app not yet delivered **Note on amounts:** No monetary figures appear in either file (transcripts_gaps.csv has no amount column; product_docs.md contains no pricing). Amounts are unavailable from the provided data.
Based on the data provided, here is the complete analysis. **Data sources used:** - `deals_open.csv` — 156 open deals (each with deal_id, alias, owner_id, stage, amount, last_contacted_field, last_email, last_call, last_meeting) - `engagements_by_deal_90d.csv` — 154 engagement records keyed by deal_id - `owners.csv` — owner name mapping (owner_id → owner_name) **Methodology:** A deal is stale if it has no logged email, call, or meeting in the last 7 days (cutoff = 2026-08-29, since snapshot date is 2026-09-05). Recency is computed from the engagement table's `last_email`/`last_call`/`last_meeting` fields only — the deal's own `last_contacted_field` is unreliable and not used. **Results:** | Owner | Alias | Owner ID | Stale Deals | Total Stale Amount | |---|---|---|---|---| | Jake Mason | Deal-2D1F1B | 119337721 | 13 | $626,243.00 | | Tracie Wilson | Deal-57FF13 | 701163055 | 1 | $2,100.00 | | Jenn Tully | Deal-44EA29 | 83155923 | 14 | $261,645.00 | | Kevin Schermerhorn | Deal-D04904 | 83155924 | 18 | $252,905.03 | | Justin Durfee | Deal-CC08D1 | 84342457 | 19 | $109,536.00 | **Grand total stale amount: $1,252,429.03** Per-owner breakdown (sorted by amount descending within each owner): **Jake Mason (119337721) — 13 stale deals, $626,243.00** - Deal-2D1F1B | DS1 | $240,000.00 | 81 days since last contact - Deal-66D1FC | DS1 | $99,000.00 | 16 days - Deal-950043 | DS1 | $70,000.00 | 19 days - Deal-B23205 | DS1 | $45,000.00 | 16 days - Deal-7BBDFA | DS3 | $37,440.00 | 46 days - Deal-332637 | DS2 | $36,000.00 | 9 days - Deal-1BEEBF | DS1 | $31,500.00 | 19 days - Deal-C5658B | DS1 | $23,400.00 | 16 days - Deal-40522D | DS3 | $21,000.00 | 19 days - Deal-F0EBBB | DS3 | $11,400.00 | 24 days - Deal-E25A09 | DS1 | $6,000.00 | 9 days - Deal-C9C286 | DS2 | $5,502.00 | 9 days - Deal-012CB1 | DS1 | $1.00 | 23 days **Tracie Wilson (701163055) — 1 stale deal, $2,100.00** - Deal-57FF13 | DS1 | $2,100.00 | No contact recorded (no engagement record) **Jenn Tully (83155923) — 14 stale deals, $261,645.00** - Deal-44EA29 | DS2 | $60,000.00 | 10 days - Deal-E51FB7 | DS2 | $43,875.00 | 12 days - Deal-B42F46 | DS1 | $27,000.00 | 19 days - Deal-BA3DDC | DS3 | $23,400.00 | 15 days - Deal-9DDE86 | DS2 | $20,000.00 | 15 days - Deal-215CCA | DS3 | $18,900.00 | 17 days - Deal-5EED42 | DS3 | $16,250.00 | 11 days - Deal-57887A | DS2 | $15,000.00 | 8 days - Deal-B7EBD1 | DS5 | $9,000.00 | 16 days - Deal-3974EB | DS4 | $9,000.00 | 8 days - Deal-F40F04 | DS2 | $8,100.00 | 15 days - Deal-87DDD1 | DS1 | $5,000.00 | 19 days - Deal-F336B6 | DS3 | $4,200.00 | 15 days - Deal-0660B4 | DS4 | $1,920.00 | 16 days **Kevin Schermerhorn (83155924) — 18 stale deals, $252,905.03** - Deal-D04904 | DS2 | $58,529.25 | 11 days - Deal-B25F40 | DS3 | $40,000.00 | 8 days - Deal-813836 | DS2 | $32,175.00 | 11 days - Deal-1BA595 | DS2 | $31,750.00 | 11 days - Deal-CFE1E8 | DS3 | $18,000.00 | 11 days - Deal-CD47A6 | DS2 | $12,168.00 | 11 days - Deal-627646 | DS3 | $11,193.00 | 11 days - Deal-FF809F | DS2 | $7,781.20 | 11 days - Deal-AF932D | DS2 | $7,225.40 | 11 days - Deal-A71728 | DS2 | $6,947.50 | 11 days - Deal-8BC9F5 | DS2 | $5,616.00 | 10 days - Deal-175395 | DS3 | $4,779.88 | 11 days - Deal-481E24 | DS3 | $4,140.00 | 10 days - Deal-C7F9BF | DS2 | $3,360.00 | 11 days - Deal-2F3A66 | DS3 | $3,334.80 | 11 days - Deal-342E96 | DS2 | $2,700.00 | 24 days - Deal-E568D5 | DS3 | $1,875.00 | 11 days - Deal-FD9F4E | DS5 | $1,330.00 | 10 days **Justin Durfee (84342457) — 19 stale deals, $109,536.00** - Deal-CC08D1 | DS1 | $24,000.00 | 16 days - Deal-E73427 | DS3 | $18,000.00 | 10 days - Deal-885F45 | DS2 | $9,300.00 | 12 days - Deal-C2FF3C | DS1 | $8,316.00 | 10 days - Deal-3EED2C | DS2 | $7,200.00 | No contact recorded - Deal-0D2F7A | DS3 | $5,100.00 | 12 days - Deal-6C60D4 | DS3 | $4,800.00 | 12 days - Deal-13FEBD | DS2 | $4,680.00 | 12 days - Deal-9D0060 | DS3 | $3,840.00 | 12 days - Deal-690476 | DS2 | $3,600.00 | 18 days - Deal-C6D97A | DS4 | $3,240.00 | 8 days - Deal-EE195F | DS3 | $3,120.00 | 8 days - Deal-278DEC | DS3 | $2,700.00 | 8 days - Deal-635B8E | DS3 | $2,600.00 | 18 days - Deal-6883F3 | DS1 | $2,400.00 | 16 days - Deal-4A13AD | DS3 | $2,160.00 | 26 days - Deal-F67D31 | DS2 | $1,800.00 | 8 days - Deal-5FDCE4 | DS3 | $1,600.00 | 12 days - Deal-BA571A | DS4 | $1,080.00 | 18 days **Two additional deals with no engagement record at all (no logged email/call/meeting in the entire 90-day window):** - 64524667574 | Deal-57FF13 | 701163055 | DS1 | $2,100.00 | No contact recorded - 64623982954 | Deal-3EED2C | 84342457 | DS2 | $7,200.00 | No contact recorded **Note:** The engagement table's deal_id format (numeric) does not match the deal file's deal_id format (e.g., "Deal-25F752"), but the numeric portion of each alias matches the corresponding engagement deal_id exactly. All 65 deals with engagement records were evaluated using their `last_email`/`last_call`/`last_meeting` dates; the 2 deals without engagement records have no contact data at all, so days since last contact is N/A.
**Analysis date:** 2026-09-05 (last-30-day window: 2026-08-06 through 2026-09-05) **Per-rep last-30-day activity totals** (from `engagements_by_deal_90d.csv`): | Rep | Emails | Calls | Meetings | Total activities | |---|---|---|---|---| | Alex Franklin (84342457) | 307 | 36 | 38 | 381 | | Bryce Harmon (119337721) | 162 | 0 | 43 | 205 | | Cole Ingram (83155924) | 96 | 14 | 1 | 111 | | Dana Mercer (83155923) | 84 | 18 | 11 | 113 | | Farid Osman (716654662) | 38 | 0 | 34 | 72 | **DS2 entries (t_ds2 within last 30 days):** | Rep | DS2 entries | |---|---| | Alex Franklin (84342457) | 17 | | Bryce Harmon (119337721) | 4 | | Cole Ingram (83155924) | 2 | | Farid Osman (716654662) | 1 | | Dana Mercer (83155923) | 1 | **Activity mix (per rep, share of total activities):** - Alex Franklin: emails 80.58%, calls 9.45%, meetings 9.97% - Bryce Harmon: emails 79.02%, calls 0.00%, meetings 20.98% - Cole Ingram: emails 86.49%, calls 12.61%, meetings 0.90% - Farid Osman: emails 52.78%, calls 0.00%, meetings 47.22% - Dana Mercer: emails 74.34%, calls 15.93%, meetings 9.73% **Efficiency ratio (total activities ÷ DS2 entries, lower = more efficient):** 1. Alex Franklin — 22.41 2. Bryce Harmon — 51.25 3. Cole Ingram — 55.50 4. Farid Osman — 72.00 5. Dana Mercer — 113.00 **Most efficient rep:** Alex Franklin (84342457) — 22.41 activities per DS2 entry. **Highest-volume rep:** Alex Franklin (84342457) — 381 total activities. **They are the same rep.**
I'll analyze the data. First, I'll establish the reference date and 60-day window, then evaluate each deal. **Reference date:** 2026-09-03 (latest engagement date in the dataset). **60-day window:** 2026-07-05 through 2026-09-03. A contact is "active" if `last_engaged_date` falls within this window and `is_former` is false. **Flagged deals (5):** **1. Deal-EC3025 (C-FDD0C7)** - Amount: not available in the provided data - Stage: not available in the provided data - Active contact count: 1 — CT-047C54 (Head of Employee Experience, champion, engaged 2026-09-02) - Personas present: champion, economic buyer - Personas missing: IT security, finance - Most valuable persona to add given the stage: cannot be determined — stage is not recorded in the data - On-file unengaged contact at C-FDD0C7: CT-6827DB, Chief People Officer, economic buyer (fits the economic buyer persona) **2. Deal-92D97D (C-E23238)** - Amount: not available in the provided data - Stage: not available in the provided data - Active contact count: 1 — CT-01F5B4 (HRIS Manager, HR admin, engaged 2026-08-28) - Personas present: HR admin, champion - Personas missing: economic buyer, IT security, finance - Most valuable persona to add given the stage: cannot be determined — stage is not recorded in the data - On-file unengaged contact at C-E23238: CT-1FA4DB, Chief People Officer, economic buyer (fits the economic buyer persona) **3. Deal-5BFE3B (C-535D36)** - Amount: not available in the provided data - Stage: not available in the provided data - Active contact count: 2 — CT-57123B (People Ops Manager, champion, engaged 2026-08-31); CT-5CE757 (Head of Employee Experience, champion, engaged 2026-08-12) - Personas present: champion - Personas missing: economic buyer, IT security, finance - Most valuable persona to add given the stage: cannot be determined — stage is not recorded in the data - On-file unengaged contact at C-535D36: none on file **4. Deal-36C33F (C-077A0E)** - Amount: not available in the provided data - Stage: not available in the provided data - Active contact count: 1 — CT-4FE556 (IT Security Lead, IT security, engaged 2026-08-15) - Personas present: IT security, champion - Personas missing: economic buyer, finance - Most valuable persona to add given the stage: cannot be determined — stage is not recorded in the data - On-file unengaged contact at C-077A0E: CT-1DB73E, Chief People Officer, economic buyer (fits the economic buyer persona) **5. Deal-FCBE5B (C-737030)** - Amount: not available in the provided data - Stage: not available in the provided data - Active contact count: 1 — CT-4A5317 (People Ops Manager, champion, engaged 2026-08-29) - Personas present: champion - Personas missing: economic buyer, IT security, finance - Most valuable persona to add given the stage: cannot be determined — stage is not recorded in the data - On-file unengaged contact Continuing from the point of truncation: **5. Deal-5BFE3B (C-535D36)** - Amount: not available in the provided data - Stage: not available in the provided data - Active contact count: 2 — CT-57123B (People Ops Manager, champion, engaged 2026-08-31); CT-5CE757 (Head of Employee Experience, champion, engaged 2026-08-12) - Personas present: champion - Personas missing: economic buyer, IT security, finance - Most valuable persona to add given the stage: cannot be determined — stage is not recorded in the provided data - On-file unengaged contact at C-535D36: none on file --- **Summary of all 5 flagged deals:** | Deal | Alias | Active contacts | Personas present | Missing personas | On-file unengaged contact | |---|---|---|---|---|---| | 61032318100 | Deal-EC3025 | 1 | champion, economic buyer | IT security, finance | CT-6827DB (Chief People Officer, economic buyer) | | 59728118877 | Deal-92D97D | 1 | HR admin, champion | economic buyer, IT security, finance | CT-1FA4DB (Chief People Officer, economic buyer) | | 61055128146 | Deal-50D386 | 2 | champion | economic buyer, IT security, finance | None | | 63739413805 | Deal-36C33F | 1 | IT security, champion | economic buyer, finance | CT-1DB73E (Chief People Officer, economic buyer) | | 51674270311 | Deal-5BFE3B | 2 | champion | economic buyer, IT security, finance | None | **Key findings:** - **No deal exceeds 2 active contacts**, so none qualify as multi-threaded; all 5 are flagged as either single-threaded (1 contact) or under-threaded (2 contacts, all in one persona). - **Amount and stage are not recorded** in either CSV — these fields do not exist in the provided data, so they cannot be reported. - **Most valuable persona to add cannot be determined for any deal** — stage information is absent from the dataset, which is required to match a persona to the appropriate stage. - **On-file unengaged contacts:** 3 of the 5 flagged deals have at least one unengaged contact on file (all economic buyer persona). The remaining 2 deals have no unengaged contacts on file.
**1. Lead-in (first 5 minutes)**
In all 10 calls the rep opens with the same line (Alex Franklin, minute 0):
"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."
**2. Three most common objections and how they're handled**
1. **Budget locked until next fiscal year** — 4 of 10 calls (TT-001, TT-003, TT-006, TT-010). Handling: acknowledges ("Totally fair"), reframes the spend as funded by turnover savings, and counters with a 90-day pilot to produce data before the next fiscal cycle.
2. **Open enrollment / underwater / can't commit** — 3 of 10 calls (TT-002, TT-005, TT-008). Handling: acknowledges ("Makes sense"), counters with a 90-day pilot scoped to one department so the prospect gets internal data before next quarter's planning.
3. **Already using spreadsheet/quarterly gift cards / no urgency** — 3 of 10 calls (TT-004, TT-007, TT-009). Handling: acknowledges ("Understood — I'll leave it with you" / "I need to think about it"), counters with the automation + analytics pitch.
**3. Concrete next-step agreement rate**
7 of 10 calls ended with a concrete next step agreed (a working session with the team this week). Rate: 7/10 = 70%. Arithmetic: 7 agreements ÷ 10 calls.
**4. Competitors raised**
- Awardco (TT-003)
- Workhuman (TT-005)
- Kudos (TT-007)
**Coaching notes**
1. The opener is 100% identical across all 10 calls — efficient, but it never changes to reflect the prospect's context. A one-line customization (e.g., leading with the prospect's industry or the specific pain point noted at booking) would raise relevance without adding time.
2. 30% of calls (3 of 10) produced no concrete next step. For the "no urgency" prospect (TT-007) and the "wait for the committee" prospect (TT-010), the rep accepted silence. A standard fallback — a value-focused email summarizing the pilot data or a 30-day check-in — would convert more of those into scheduled sessions.
The file on disk contains 26 deals with only four columns: `deal_id`, `deal_alias`, `owner_id`, and `amount`. The prompt describes an 86-row dataset with stage, forecast_category, close_date, and why_buys_chars columns — the two files do not match, and the actual file is missing the three fields required for the forecast (stage, forecast_category, close_date). **Forecast** - COMMIT total: cannot be computed — no `forecast_category` field exists in the data. - BEST_CASE total: cannot be computed — no `forecast_category` field exists in the data. - Weighted forecast: cannot be computed — depends on the above. - Count of deals in each category inside the quarter: cannot be computed — no stage or close_date fields. - Deals excluded for being outside the quarter: cannot be computed — no close_date field. - Top 5 BEST_CASE deals by amount inside the quarter: cannot be computed — no `forecast_category` or close_date fields. Arithmetic attempted: filter by close_date ∈ [2026-07-01, 2026-09-30] × (COMMIT + 0.35×BEST_CASE). The file has no close_date, no forecast_category, and no stage, so none of the filters or weights can be applied. ## Data quality The file on disk (26 rows) does not match the 86-row dataset shown in the prompt; the prompt's stage, forecast_category, and close_date columns are absent from the actual file. The required fields for the forecast — stage (DS1 through DS5), forecast_category (COMMIT/BEST_CASE), and close_date — are not present, so no deal can be classified or filtered by quarter. Without close dates, no deal can be verified against the Q3 2026 window (2026-07-01 to 2026-09-30). Without forecast categories, the 100%/35% weighting rule cannot be applied.
## Activation hypothesis test — plg_company_cohort_2023.csv **2x2 retention at 24 months (current_status = active, cohort = companies with m1_users ≥ 5 AND m1_redemptions ≥ 1):** | Signal | Cohort size | Retained | Retention rate | |---|---|---|---| | Both signals (m1_users ≥ 5 AND m1_redemptions ≥ 1) | 47 | 31 | 65.96% | | Givers only (m1_users ≥ 5, no redemption) | 49 | 23 | 46.94% | | Redemption only (m1_redemptions ≥ 1, no givers) | 29 | 9 | 31.03% | | Neither | 95 | 38 | 40.00% | **Excluded from the denominator:** 0. All 220 rows in the file contain valid m1_users and m1_redemptions values; no company lacks first-calendar-month signal data. **Single signal with the largest retention lift:** **givers** (m1_users ≥ 5), with a +6.94 pp lift over the neither baseline (46.94% vs 40.00%). The combined "both signals" group has the largest overall lift (+25.96 pp), but that is a joint effect of both signals together. **What this proves and does not prove:** - **Proves:** The cohort with both signals retains at 24 months at a substantially higher rate than the givers-only or redemption-only groups, and that having ≥5 givers alone is associated with better 24-month retention than having no givers. - **Does not prove:** Causation — the givers/redemption signals may be correlated with other drivers (ARR, product tier, industry, country) that are responsible for retention. The "both" group's lift may be synergistic rather than simply additive. It does not establish that these signals predict retention beyond the 24-month window, nor that they are the primary cause of retention (confounding by ARR tier, for example, is possible given the data available).
Per-company KVMs for 2026-08 vs 2026-07: | KVM | Value (Aug) | Prior (Jul) | Δ abs | Δ % | Direction | |---|---|---|---|---|---| | Giving Rate | 0.5937 | 0.5975 | -0.0038 | -0.64% | down | | Redemptions per User | 1.4839 | 1.4838 | +0.0001 | +0.01% | up | | 1:1 Meetings Engagement | 0.4098 | 0.4090 | +0.0008 | +0.20% | up | | Pulse Check Engagement | 0.2619 | 0.5398 | -0.2779 | -51.48% | down | Largest relative move: Pulse Check Engagement on C-0D0B047C (0.5398→0.2619, Δ=-51.48%). Driven by size_band=enterprise (plan_tier is uniform tier_three across all 30 companies, so no plan_tier signal exists).
**Last completed month:** 2026-08 (August 2026) **Redemption count:** 48 **Total spend:** $3,536.00 **Unique redeemers:** 46 **Redemptions per redeemer:** 48 ÷ 46 = 1.04 **Provider mix (percent of spend):** - TangoCard: $500.00 → 14.14% - Tremendous: $1,145.00 → 32.38% - custom: $1,057.00 → 29.89% - Snappy: $834.00 → 23.59% - **Total: $3,536.00 → 100.00%** ✓ **Top 5 countries by redemption count:** 1. US: 31 2. CA: 7 3. GB: 2 4. SG: 2 5. AU: 2 (GB, SG, and AU are tied at 2 redemptions each; the next tier is NL at 2 as well — all four are shown in the top 5 by count.)
## Eligible accounts (7 of 28) — all three rules met | Account | Health | ARR | Churn-save amount | Renewal | Usage | Play | |---|---|---|---|---|---|---| | C-0F6C0F34 | 51 | 86,741 | 49,707 | 2026-10-03 | growing | Commercial concession | | C-0B827671 | 56 | 72,088 | 25,365 | 2026-11-14 | declining | Usage revival | | C-0B360C78 | 57 | 60,427 | 35,748 | 2026-10-28 | growing | Executive touch | | C-0B0F1BAB | 38 | 15,391 | 5,494 | 2026-09-23 | flat | Commercial concession | | C-0E9C27D1 | 39 | 75,093 | 41,235 | 2026-09-24 | flat | Executive touch | | C-0CEF69FD | 53 | 79,324 | 32,621 | 2026-11-21 | growing | Commercial concession | | C-0D3278C7 | 54 | 33,815 | 17,602 | 2026-11-12 | declining | Usage revival | **Arithmetic:** 49,707 + 25,365 + 35,748 + 5,494 + 41,235 + 32,621 + 17,602 = **207,772** ## Play justification (per account) - **Usage revival** — C-0B827671, C-0D3278C7: both show a declining 3-month usage trend. C-0B827671 (declining, champion active) and C-0D3278C7 (declining, champion active) need re-engagement to reverse the usage drop. - **Executive touch** — C-0B360C78, C-0E9C27D1: both have champion_active = true. C-0B360C78 (champion, growing usage) and C-0E9C27D1 (champion, flat usage) benefit from an executive-level conversation driven by their internal champion. - **Commercial concession** — C-0F6C0F34, C-0B0F1BAB, C-0CEF69FD: high churn-save-eligible amounts with no usage problem to fix. C-0F6C0F34 ($49,707), C-0CEF69FD ($32,621), and C-0B0F1BAB ($5,494) are the dollar-at-stake targets for concession offers. ## At-risk accounts that do not qualify **Fail R1 (health score ≥ 60):** C-8C2E8F00 (73), C-0B843542 (63), C-14264ABD (87), C-0B2895EF (73), C-0EE1203E (88), C-0FC7A215 (62), C-0D035262 (85), C-0D6CC8E3 (77), C-0B2213A9 (69), C-0D0B047C (70), C-21FEBCBB (65), C-172EEFBC (75), C-0C3848D2 (73), C-0D890324 (81), C-0AAA9434 (75) — none meet the "health score below 60" threshold. **Fail R2 (churn-save amount = 0):** C-0BC71BDD, C-0F6694C3, C-0BE96399, C-0FCCD2DF, C-10A56B0F — eligible amount is zero, so no churn-save offer applies. **Fail R3 (renewal outside 120 days from snapshot 2026-09-05, i.e., after 2026-12-24):** C-0CA21961 (renewal 2026-12-28, 4 days past the window), C-0F876796 (renewal 2027-02-06).
## Expansion Kit — C-0DDFC9A7 **1. Seat coverage** Licensed seats ÷ headcount = 150 ÷ 400 = **37.5%**. The account is under-covered: 250 more people than licensed seats. **2. Usage health (two lines)** - Monthly active users climbed from 88 (Mar) → 126 (Aug), a **43% increase**, with steady month-over-month gains of 7–8 users. - The recognition feed is busy every week, confirming strong ongoing engagement. **3. Headroom at the current per-seat rate** - Per-seat rate: $9,000 ÷ 150 = **$60/seat/yr**. - Seats: 150 − 400 = **−250 seats** (shortfall). - ARR headroom: $60 × (−250) = **−$15,000** — a $15,000 gap to cover the full headcount at the current rate. **4. Who replied and can they buy?** Maria S. (People Operations Coordinator) replied on 2026-09-02. She explicitly stated she is "not the right person for purchasing decisions here. Budget and seat expansion sit with Dana R." — so **she cannot buy**. **5. Right buyer from contacts** **Dana R.** — VP People (last engaged 2026-05-18). She owns budget and seat expansion. **6. Reply email (under 150 words)** ``` Hi Dana, Thanks for Maria's intro — I'm glad the recognition program is working well for your team. Quick context: your team's monthly active users have climbed from 88 in March to 126 in August, a 43% increase, and the recognition feed is busy every week. At our current rate of $60/seat, we'd need 400 seats to cover your headcount of 400, so there's room to expand your license set. I'd love to walk you through the next steps when you're ready — no rush. Happy to set up a quick call. Best, Cole ``` Word count: 94. One real usage fact cited: the 88→126 MAU climb (43% growth). The email names Dana, references the usage fact, and is non-pushy.
Mid-onboarding call prep — Company C-0D284E42 (signup 2026-08-11) **Complete (data-backed)** - Integrations connected: Slack — connected 2026-08-12 (integration_slack field). HRIS integration — no date recorded (integration_hris field is empty). Not fully complete. - Allowance set: 2026-08-13 (allowance_set field). Complete. - Admins added: 2 (admins_added field). Complete. - First recognition given: 2026-08-15 14:22 (first_recognition_at field). Complete. - First redemption: no date recorded (first_redemption_at field is empty). Not complete. **Not complete** - HRIS integration — no connection date on file. - First redemption — no date recorded. **Early engagement signals (onboarding_usage.csv, 2026-08-11 through 2026-08-31)** - First week (8/11–8/17): active givers 3, 3, 4, 4, 5, 4, 7 — rose from 3 to 7, a 133% increase, with 8/17 the strongest day of the week. - Sustained growth: 9 by 8/21, 13 by 8/30, 15 by 9/3–9/4. Trend is upward, not flat. - Volume: 214 total active-giver-days across 24 days, average ~8.9/day. The 8/26 spike to 11 and the 9/3–9/4 plateau at 15 show the onboarding loop is gaining traction. **Three things to cover on the call** 1. Integration status — confirm Slack is live (2026-08-12) and push HRIS as the outstanding item; the missing HRIS date means its status cannot be verified yet. 2. Adoption trajectory — walk the usage curve (3→7 in week one, sustained to 15 by day 24) and flag that the first redemption date is still missing — set a redemption target before the next check-in. 3. Action items — allowance confirmed (2026-08-13), 2 admins onboarded, first recognition delivered (2026-08-15 14:22), and close out the first redemption (date TBD).
**Theme 1: Billing & invoicing errors (invoice discrepancies + tier pricing)** — 16 tickets, 20.0% share, $832,000 ARR, 2 distinct accounts (C-0E9C27D1, C-0B2213A9) - Ticket IDs: IC-460071, IC-460069 - Recommendation: Reconcile invoices and fix tier-pricing configuration; the seat-count mismatch and wrong-tier renewal both originate from the same account and need a single pricing/seat-validation rule change. **Theme 2: Slack integration & sync failures** — 22 tickets, 27.5% share, $369,400 ARR, 7 distinct accounts - Ticket IDs: IC-460041, IC-460047 - Recommendation: Audit the Slack app reconnection flow and sync toggle; restore channel posting and prevent the toggle from resetting mid-week. **Theme 3: Recognition points / balance not posting** — 38 tickets, 47.5% share, $247,500 ARR, 16 distinct accounts - Ticket IDs: IC-460004, IC-460016 - Recommendation: Fix the recognition delivery-to-balance pipeline so posted recognitions update the user's balance within the same business day. **Theme 4: HRIS provisioning / new-hire account creation** — 4 tickets, 5.0% share, $150,000 ARR, 4 distinct accounts - Ticket IDs: IC-460059, IC-460055 - Recommendation: Repair the HRIS sync to provision new-hire accounts on first use and add a provisioning status check before invoicing. **Separation note:** The invoice discrepancy and billing tier price issues were both single-account noise (both from C-0E9C27D1); they are grouped here as one broad billing/invoicing pattern. The remaining three themes are broad patterns affecting multiple accounts. Ranked by ARR exposure: billing & invoicing ($832k) > Slack sync ($369.4k) > recognition points ($247.5k) > HRIS provisioning ($150k).
Top 3 most similar existing customers with public case studies (scored on industry, size band, use case, region): 1. **C-11C31562** — 3/4 fields matched - Matched: size_band (Mid-Market), use_case (employee_recognition), region (NA-West) - Missed: industry (Manufacturing ≠ Technology) 2. **C-64171065** — 3/4 fields matched - Matched: industry (Technology), size_band (Mid-Market), use_case (employee_recognition) - Missed: region (NA-East ≠ NA-West) 3. **C-A13C193D** — 2/4 fields matched - Matched: industry (Technology), size_band (Mid-Market), region (NA-West) - Missed: use_case (retention ≠ employee_recognition) - Tied with C-CD4829A7 and C-9D69D147 on 2/4; selected on industry + region alignment No billing data or contact names included. Customer aliases cited exactly as in the source files.
**Trailing 6-month window: March 2026 – August 2026** --- ### Paid channels | Channel | Spend | SQMs | SQOs | Cost/SQM | Cost/SQO | SQM→SQO rate | Pipeline | Pipeline/$ | |---|---|---|---|---|---|---|---|---| | paid_search | $36,000 | 26 | 12 | $1,384.62 | $3,000.00 | 2.17 (26/12) | $480,000 | 13.33 | | linkedin_ads | $24,000 | 17 | 6 | $1,411.76 | $4,000.00 | 2.83 (17/6) | $72,000 | 3.00 | | paid_social | $18,000 | 0 | 0 | undefined | undefined | undefined | $0 | N/A | | webinars | $9,000 | 4 | 1 | $2,250.00 | $9,000.00 | 4.00 (4/1) | $12,000 | 1.33 | ### Organic channels (organic_search) | Metric | Value | |---|---| | Volume (contacts) | 17 | | SQO rate | 5/17 = 29.4% | | Pipeline | $45,000 | ### Flagged rows (SQO date precedes SQM date) - **CT-000044** (linkedin_ads): sqm 2026-07-23, sqo 2026-07-18 — SQO recorded before the SQM. ### Reallocation recommendation 1. **Scale paid_search.** It delivers the best unit economics: lowest cost per SQM ($1,384.62 vs. $1,411.76 / $2,250), the highest pipeline-per-dollar (13.33), and the most SQOs per SQM (2.17). With 26 SQMs and 12 SQOs across the period, it is the clear primary acquisition engine. 2. **Pause or audit paid_social.** Spends $18,000 with zero SQMs and zero SQOs — no qualified lead generation at all. Either cut the budget or diagnose why no first-touch events are being logged. 3. **Investigate linkedin_ads.** The 2.83 SQM→SQO rate is acceptable, but CT-000044's inverted dates suggest a process or recording error (SQO entered before SQM). Fix the date capture workflow; if the underlying conversion holds, keep the channel but monitor the data integrity. 4. **Trim webinars.** Highest cost per SQM ($2,250) and lowest pipeline efficiency (1.33 per dollar) on only 4 SQMs. Reduce spend until the channel proves a better conversion rate. ### Confidence Moderate to low. Sample sizes are small: paid_search has 26 SQMs (adequate), linkedin_ads 17 (good), webinars 4 (weak), paid_social 0 SQMs (no conversion data), organic_search 17 contacts with 5 SQOs (moderate). The paid_search and linkedin_ads figures are the most reliable; webinars and paid_social conclusions rest on thin evidence and should be re-evaluated once more data accumulates.
**Per-sequence metrics (sent / open rate / reply rate / meeting rate):** *New Logo Nurture:* Step 1 42.00% / 8.40% / 2.40%; Step 2 34.93% / 6.55% / 1.97%; Step 3 28.04% / 4.21% / 1.40%. **Weakest: Step 3 (4.21%).** *Expansion Nurture:* Step 1 43.33% / 7.33% / 1.67%; Step 2 113.33% / 8.33% / 1.33%; Step 3 34.55% / 4.36% / 1.09%. **Weakest: Step 3 (4.36%).** *Cold Outbound - HR Leaders:* Step 1 40.00% / 0.83% / 0.00%; Step 2 29.41% / 0.34% / 0.00%; Step 3 22.03% / 0.17% / 0.00%. **Weakest: Step 3 (0.17%).** *Cold Outbound - People Ops:* Step 1 37.50% / 3.50% / 0.75%; Step 2 28.50% / 2.33% / 0.52%; Step 3 21.22% / 1.59% / 0.27%. **Weakest: Step 3 (1.59%).** **Tracking errors:** One — *Expansion Nurture* Step 2: opened 340 > sent 300. Opened cannot exceed sent; this inflates the open rate and distorts the sequence's reporting. **Audience overlap:** *Cold Outbound - HR Leaders* ↔ *Cold Outbound - People Ops* share 21 contacts; *New Logo Nurture* ↔ *Expansion Nurture* share 2 contacts. The remaining contacts are exclusive to their sequences. **Failure mode (reply rate < 2%):** *Cold Outbound - HR Leaders* fails on all three steps (0.83%, 0.34%, 0.17%) — the message has no meaningful engagement with this audience at any stage. *Cold Outbound - People Ops* Step 3 falls short at 1.59% — engagement drops off by the final step. **Changes (one per weak sequence):** 1. *Cold Outbound - HR Leaders:* Correct the Step 2 opened count (340 → ≤300). It is the only tracking error and invalidates the sequence's reported rates. 2. *Cold Outbound - People Ops:* Revise Step 3 content/targeting to lift the 1.59% reply rate. **Fix first:** *Cold Outbound - HR Leaders.* The tracking error is a data-integrity issue that must be corrected before any reply-rate improvement can be meaningfully measured.
**Weekly Marketing Goals Update — Q3-2026** Quarter: Q3-2026 (Jul 1 – Sep 30, 2026); 66 of 92 days elapsed (~72%). | Metric | QTD Actual | Target | Delta | Pace (66/92 days) | |---|---|---|---|---| | SQMs | 230 | 300 | −70 | Ahead | | SQOs | 84 | 120 | −36 | Behind | | DS2s | 40 | 75 | −35 | Behind | | Closed-Lost MIA Rate | 5.0% | 0.1% | +4.9pp | Behind | | Same-Quarter Closes | 10 | 20 | −10 | Behind | | Active Pipeline | $3.0M | $4.0M | −$1.0M | Ahead | **What moved this week:** SQMs and active pipeline are tracking ahead of the quarter's pace — SQMs are 230 vs an expected 215 (66% through the quarter, +15 above pace) and the pipeline is $3.0M vs an expected $2.87M (+$130k, 75% of target). The other four metrics are trailing: SQOs (84 vs 87), DS2s (40 vs 53), same-quarter closes (10 vs 14), and the closed-lost MIA rate (5.0% vs 0.07% pace) — the MIA rate is the standout miss at roughly 70× the quarterly target rate. At 72% through the quarter, closing the gap on SQOs, DS2s, and the close rate is the priority.
Q3 2026 weighted forecast is $115,976.75, made from $44,729 committed plus 35% of $203,565 best-case across 54 of 86 deals. Top 5 best-case deals are Deal-2D7423 $38,935, Deal-25F752 $24,000, Deal-E53952 $19,656, Deal-5EED42 $16,250, Deal-FA32A0 $11,116, totaling $109,957. Caveat: 85 of 86 deals lack owners, 71 of 86 lack why-buys, and 32 deals totaling $227,575 have October close dates suggesting pushed closes, so the forecast is precise but unreliable.
**Subject:** Pricing for your recognition program Hi, Following up on our July 28 demo — I've put together the pricing details for the 150-seat recognition package we discussed. You were interested in the automated milestone awards and points catalog, so the quote reflects those features. Which tier works best for your team, or would you like a quick walkthrough? Best, Alex Franklin
This week's marketing delivered 46 SQMs against a target of 52. The webinar channel drove 18 of those SQMs, about 39 percent of the total. Paid search cost per SQM held at 150 dollars. We fell 6 SQMs short of the target, roughly 12 percent. Sales converted 14 SQOs and set 9 DS2 meetings, a conversion rate of about 64 percent. New pipeline created was 310,000 dollars. Three deals closed in the same quarter, so the close rate on new pipeline is about 1 in 100. Renewals saved this week were 2. Team NPS moved to 61. There are 3 open red-flag accounts heading into next week. PLG added 412 new signups with a 31 percent activation rate. 38 companies reached the aha moment of 10 recognition gives.
# Partner Digest: 2026-08-24 to 2026-09-04 ## Active plays - Apex Rewards Co: 2 sourced deals, $275,000 - HRCloud Partners: 1 sourced deal, $140,000 - CultureBridge: 2 sourced deals, $135,000 - WorkWell Group: 0 sourced deals, $0 ## Quiet partners - Recogniiq - KudosWave - PeopleFirst Advisors - TotalPerk **Verification against deal data:** Apex Rewards Co — Deal-DDAAF2 ($180,000) + Deal-2CF33E ($95,000) = $275,000 across 2 deals. HRCloud Partners — Deal-F1CDA5 ($140,000) = 1 deal. CultureBridge — Deal-096E1D ($60,000) + Deal-067213 ($75,000) = $135,000 across 2 deals. WorkWell Group — no deals in the file. Total partner-sourced pipeline: 5 deals, $550,000. Quiet partners have no entries in partner_deals.csv, consistent with the "no sourced deals this period" note for WorkWell.
Q1: Yes. Customer data is encrypted at rest using AES-256. [P1] Q2: Yes. Data in transit is encrypted with TLS 1.2 or higher. [P1] Q3: Yes. Bonusly maintains a SOC 2 Type II report, renewed annually, and it is available to prospects under NDA. [P2] Q4: Retained for the duration of the contract plus 90 days, after which it is deleted from production systems. [P3] Q5: Subprocessor list is published at trust.bonusly.com; customers receive 30 days notice before a new subprocessor is added. [P4] Q6: Yes. SAML 2.0 single sign-on is available on the Enterprise plan. [P5] Q7: Production databases are backed up daily; backups are encrypted and retained for 35 days. [P6] Q8: Unanswerable from the provided documents. No excerpt covers ISO 27001 certification; the relevant document would be the ISO 27001 certification record or compliance report. Q9: Unanswerable from the provided documents. No excerpt covers uptime SLA; the relevant document would be the contractual SLA or service agreement. Q10: Unanswerable from the provided documents. No excerpt covers a HIPAA Business Associate Agreement; the relevant document would be the BAA itself.
Runbook written to `runbook_incident_2026-08-29_reward_queue.md`. It covers 10 ordered steps traced to each message in the thread: 1. **Acknowledge alert** — Bryce Harmon (M01) 2. **Measure queue depth** — Farid Osman, `bundle exec rake sidekiq:queue_depth` → 48,213 (M02) 3. **Identify dead set** — Farid Osman, 112 jobs, all Redis::TimeoutError (M03) 4. **Pause enqueue** — Farid Osman, `FeatureFlag.disable(:auto_recognition_enqueue)` (M04); rollback: re-enable 5. **Clear dead set** — Elena Sinclair (M05) — **needs confirmation**: no rollback specified 6. **Scale workers up** — Bryce Harmon, `kubectl scale deployment/reward-worker --replicas=6` (was 3) (M06); rollback: scale back to 3 7. **Confirm queue dropping** — Farid Osman, 9,400 and falling ~1,200/min (M07) 8. **Verify error rate baseline** — Cole Ingram, Datadog back to baseline (M08) 9. **Re-enable enqueue** — Bryce Harmon, `FeatureFlag.enable(:auto_recognition_enqueue)` (M09); 40 new jobs processed cleanly in 3 min; **needs confirmation**: no rollback specified 10. **Scale workers back down** — Bryce Harmon, `kubectl scale deployment/reward-worker --replicas=3` (M10); queue stable at 0, incident resolved Arithmetic shown: 48,213 − 9,400 = 38,813 jobs cleared by the pause; 40 new jobs in 3 minutes after re-enable; final depth 0. All commands and flags are cited exactly as they appear in the thread.
**First error (timestamp):** 2026-09-03T14:01:12Z — `reward-service` ERROR: `Redis::TimeoutError: Connection to Redis at redis-primary:6379 timed out after 5s` **Cascade (chronological):** 1. 14:01:12 reward-service — Redis connection timeout (redis-primary:6379) 2. 14:01:20, 14:01:30, 14:01:40 reward-service — retry exhausted for **RewardGiveJob** (3 consecutive retries) 3. 14:01:40 sidekiq — `RewardGiveJob failed: Redis::TimeoutError; retrying in 60s` 4. 14:02:28 sidekiq — retrying 5. 14:02:30 sidekiq WARN — "Queue reward depth above 10,000" 6. 14:03:05 api-gateway — 502 upstream timeout calling reward-service /gives 7. 14:03:30 web-app — Give form submission failed: upstream 502 from api-gateway 8. 14:03:31 sidekiq — retrying 9. 14:04:13 api-gateway — 502 upstream timeout calling reward-service 10. 14:04:45 web-app — Give form submission failed: upstream 502 11. 14:04:22 sidekiq — retrying 12. 14:05:16 api-gateway — 502 upstream timeout calling reward-service 13. 14:05:26 sidekiq — retrying 14. 14:06:47 sidekiq — retrying 15. 14:06:49 web-app — Give form submission failed: upstream 502 16. 14:06:52 api-gateway — 502 upstream timeout calling reward-service 17. 14:20:59 reward-service — Redis connection restored; resuming job processing 18. 14:24:45 sidekiq — Queue reward depth below 500 **Services and jobs involved:** - `reward-service` — primary failure point (Redis timeout) - `sidekiq` — job processor; repeatedly failed on **RewardGiveJob** - `api-gateway` — returned 502 upstream to reward-service - `web-app` — surfaced user-facing "Give form submission failed: upstream 502" - `RecognitionDigestJob` — also hit Redis::TimeoutError (J-00013 through J-00016); parallel job, not in the RewardGiveJob retry loop - `postgres` — no errors (checkpoint complete); no role in the cascade **Datadog query confirming the first error:** ``` service:reward-service AND level:ERROR AND message:Redis::TimeoutError ``` **What the logs do not show:** - Root cause of the Redis outage (no Redis node restart/restart event, no infra change recorded) - Error-rate or latency metrics, queue-depth trend, or throughput figures - User impact (number of failed submissions, revenue exposure) - Alerting/notification trail (no pager or alert logs) - Pre-outage queue depth context (the "above 10,000" WARN has no earlier baseline) - Per-retry latency or backoff timing beyond the observed retries - Any postgres-side incident during the window (postgres checkpoints are clean, but no explicit health check around the outage)
Feature flag state (from flags_export.csv, with control descriptions taken from flag_code.md): - **recognition_streaks_v2** — on. StreakTracker.record(give) records gives; targets segment:beta_companies. Company count: 42. - **points_budget_guardrails** — on. BudgetService.new(company).enforce!(giver, points) enforces the points budget; targets all_companies. Company count: 220. - **slack_dm_nudges** — on. SlackDm.send_nudge(user) sends a Slack DM nudge; targets segment:region_na. Company count: 87. - **redeem_flow_redesign** — off. Renders RedeemV2Component when enabled, otherwise falls back to RedeemV1Component; targets targeted_list. Company count: 12. - **analytics_dashboard_v3** — on. Loads AnalyticsV3 dashboard; targets segment:tier_three. Company count: 65. - **ms_teams_app_v2** — off. TeamsAppV2.install(company) installs the Teams app; targets targeted_list. Company count: 9. - **legacy_give_modal** — off. Targets segment:legacy_plan. Company count: 14. - **survey_boosters_q3** — on. Targets segment:legacy_plan. Company count: 7. - **paused_offboard_cleanup** — off. No targeting rules defined. Company count: 0. Flags with no code reference (flag_code.md): legacy_give_modal, survey_boosters_q3, paused_offboard_cleanup — none of these appear in the code excerpt. Flag with no targeting rules: paused_offboard_cleanup (targeting_rules column is empty in the export). Arithmetic: - On: 4 flags (recognition_streaks_v2, points_budget_guardrails, slack_dm_nudges, analytics_dashboard_v3) - Off: 5 flags (redeem_flow_redesign, ms_teams_app_v2, legacy_give_modal, survey_boosters_q3, paused_offboard_cleanup) - Sum of company counts across all flags: 42 + 220 + 87 + 12 + 65 + 9 + 14 + 7 + 0 = 456
Triage results: **NDA-1 — GREEN.** Standard mutual confidentiality with standard carve-outs (public availability, prior knowledge, third-party receipt, independent development, legally required disclosure), 2-year term with 3-year post-termination survival, Delaware governing law. No embedded non-solicit or non-compete; carve-outs present; governing law consistent with the other inbound NDAs. **NDA-2 — YELLOW.** Driven by the embedded non-solicit clause: "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." Non-solicit provisions require legal review before approval; otherwise the rest of the agreement is standard (3-year term, Delaware law, standard carve-outs). **NDA-3 — RED.** Three compounding issues: (1) 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." (2) Missing confidentiality carve-outs — "No confidentiality carve-outs are stated in this Agreement," leaving the obligation overbroad and potentially unenforceable. (3) Unusual governing law — Republic of Ireland with exclusive jurisdiction, diverging from the Delaware standard in the other two inbound NDAs. Full legal review required before approval.