Mean 0.948 · 34/40 perfect tests · $0.00 total · modalities in: text, image, file, video, audio · 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** - Open pipeline: 156 deals (DS1 32, DS2 39, DS3 61, DS4 14, DS5 10). - DS2+ : stage DS2, DS3, DS4 or DS5. Count = 124. - Non-compliant on why-buys: DS2+ deal where why_buys is blank, a placeholder (tbd, n/a, see notes), or under 15 characters. LONG(n) counts as compliant. - No DS1: t_ds1 is blank. - Regressed: any non-blank stage timestamp is later than a non-blank timestamp for a later stage (pairwise across t_ds1 to t_ds5). **Why-buys compliance (DS2+)** - Overall: 101 of 124 non-compliant = 81.5%. All 101 are blank; none were placeholder or short text. - Bryce Harmon: 15 / 18 = 83.3% - Dana Mercer: 18 / 22 = 81.8% - Alex Franklin: 48 / 61 = 78.7% - Cole Ingram: 19 / 22 = 86.4% - Farid Osman: 1 / 1 = 100% - Elena Sinclair: 0 DS2+ deals (no data) - Check: 15+18+48+19+1 = 101; 18+22+61+22+1 = 124. **Stage hygiene** - No DS1 timestamp: 0 deals. - Regressed timestamps: 0 deals. **Three process fixes** 1. Make why-buys a required field at the DS2 gate, with a minimum length and a blocked placeholder list. Alex Franklin's 48 blank records are the largest backlog. 2. Add a validation rule that requires a non-blank t_ds1 when a deal is created. (No gaps today, so this is preventive.) 3. Add a weekly report of DS2+ deals with blank why-buys, by owner, for managers to clear before the next pipeline review.
Owner resolution results (156 open deals, all resolved): Deals resolved: 156 of 156. Every owner_id in deals_open.csv matched an entry in owners.csv. Deals with no owner match: none. Owner ids mapping to archived/deactivated owners: none. The two archived owners in the table — Gavin Porter (1520255671) and Hugo Lindqvist (77260721) — own zero open deals. Total pipeline amount per resolved owner: - Alex Franklin (84342457): 67 deals, $624,310.00 - Bryce Harmon (119337721): 35 deals, $1,054,144.00 - Dana Mercer (83155923): 24 deals, $341,195.00 - Cole Ingram (83155924): 22 deals, $288,161.43 - Farid Osman (716654662): 7 deals, $4,134.00 - Elena Sinclair (701163055): 1 deal (Deal-57FF13), $2,100.00 Total: $2,314,044.43. Notes on arithmetic: owner totals are straight sums of the amount column per owner_id. Farid Osman's total includes four deals at amount 1 each ($4) plus $2,880 (Deal-8BA24E) and $1,249 (Deal-499BF6) = $4,134. Cole Ingram's total carries cents from four deals (7225.40, 7781.20, 6947.50, 2480.40, 4779.88, 3334.80, 58529.25), so his total is not a round figure. One caveat: the source file has no explicit currency marker; I report amounts as given. ⚠️ 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/.hermes/cache/scratch/deals_open.csv` — [write_file] Refusing to overwrite `/Users/amaniphipps/.hermes/cache/scratch/deals_open.csv`: `/Users/amaniphipps/.hermes/cache/scratch/deals_open.csv` exists but this task has not seen its full c…
(a) 30 Gong rows are orphans: their HubSpot deal IDs have no match in `deals_open`. Examples: Deal-8FA85D, Deal-8FC3F9, Deal-3B7945, Deal-42B265, Deal-9CCC42. (b) 0 duplicate conversation keys (0 rows where `calls_90d` exceeds `distinct_conversation_keys`). (c) 25 of 85 open deals at DS3 or later have at least one logged call: 25 ÷ 85 = 29.4%.
```sql -- A correct query cannot be written using only this catalog. -- Missing: customer-company identifiers and the date each company became a customer. -- Missing: a recognition-event source with company ID, giver ID, event timestamp, -- and recognition ID or documented row grain. -- PRODUCTION.DEPRECATED_RECOGNITION.REDEMPTION_RECORDS_V2 is the documented -- redemption source, but its company key, event timestamp, and row grain are missing. -- PRODUCTION.PLG.COMPANY_COHORT_SUMMARY covers only self-serve companies; -- its M1_* fields are not documented as first-calendar-month metrics. -- Historical giving must retain deleted givers. -- Successful redemptions must use STATE = 'succeeded'. ```
# CRM Extract Audit
**Important data limitation first: no deals file was provided.** The extract contains only companies.csv, contacts.csv, and zoominfo_enrichment.csv. Therefore deal-level fields (owner, stage, amount, close date, why-buys) cannot be audited, and **the "Top 10 fixes by pipeline amount at stake" cannot be ranked by dollar value** — I list the 10 highest-impact fixes below without invented amounts. Provide the deals extract to complete that section.
## 1. Field completeness
Companies (34 rows):
| Field | Complete | % |
|---|---|---|
| domain | 34/34 | 100.0% |
| industry | 34/34 | 100.0%* |
| employee_count | 25/34 | 73.5% |
| hq_country | 28/34 | 82.4% |
*industry is 100% filled but not clean: values include "tech" (3), "Tech " with trailing space (2), "health care" (2), "SaaS" (1) — normalization needed.
Contacts (52 rows):
| Field | Complete | % |
|---|---|---|
| email | 52/52 | 100.0%* |
| title | 39/52 | 75.0% |
| persona | 37/52 | 71.2% |
| domain | 52/52 | 100.0% |
*100% filled but 4 are structurally invalid (see §3).
Deals: not auditable — no data.
## 2. Duplicate company clusters (2, both shared-domain)
Cluster A — domain acme-corp.com: C-0A092931 (Technology, 500, US) vs C-0A092932 (tech, 510, USA).
Survivor: C-0A092931 — identical domain, near-identical attributes (500 vs 510 employees is consistent with headcount drift); C-0A092932 should merge into it.
Cluster B — domain globex.io: C-0A092933 (SaaS, 200, US) vs C-0A092934 (Technology, 200, US).
Survivor: C-0A092933 — employee count and country identical, industry differs only in normalization; C-0A092934 should merge into it.
No name-variant clusters beyond these two were detectable: the extract uses opaque aliases, so name-based matching is not possible with the data given.
## 3. Invalid emails and domain mismatches
Invalid emails (4) — no domain after the @:
- CT-0010 (C-66D1FC): "user0@"
- CT-0080 (C-92D97D): "user0@"
- CT-0081 (C-92D97D): "user1@"
- CT-0192 (C-425E2A): "user2@"
All four can be reconstructed from the company domain column (e.g. user0@66d1fc.com) — but that is a normalization rule, not an invented value, since the contacts' own `domain` field supplies the missing part.
Domain mismatch (1):
- CT-0011 (C-66D1FC): email "user1@other-domain.com" vs contact/company domain 66d1fc.com. Conflict — needs manual verification; do not auto-overwrite.
## 4. Fill missing company fields from enrichment
Employee count — fillable (9 of 9 blanks have an enrichment row):
| Company | CRM blank | Fill from ZI |
|---|---|---|
| C-EC3025, C-96039F, C-44EA29, C-D04904, C-B23205, C-60C75F, C-7BBDFA, C-50D386 | — | 400 each |
| C-93C8BF | — | No enrichment row — remains missing; no value invented |
HQ country — NOT fillable in 5 of 6 cases; enrichment is also blank:
- C-2D1F1B, C-D73B89, C-44EA29, C-D04904, C-2C60E5: enrichment blank → leave blank.
- C-EE9FFB: no enrichment row → leave blank.
Disagreements (both sources filled, values differ). Most "disagreements" are cosmetic (US/USA/United States); recommend normalizing country to ISO long form ("United States") on the CRM side. The substantive ones:
| Company | Field | CRM | ZoomInfo | Recommended source |
|---|---|---|---|---|
| C-EC3025 | employee_count | (blank) | 400 | ZoomInfo (only value) |
| C-EC3025 | industry | Technology | Computer Software | ZoomInfo — vendor-standard taxonomy; map Technology→Computer Software |
| C-66D1FC, C-44EA29, C-92D97D, C-D04904, C-77A95A, C-AA8DDA, C-B25F40, C-60C75F, C-425E2A | industry | tech/Technology | Computer Software | ZoomInfo taxonomy, same mapping |
| C-EC3025, C-96039F, C-E51FB7, C-425E2A, C-2D7423, C-77A95A, C-950043, C-66D1FC, C-B23205, C-D0662E | hq_country | US/USA | United States | Cosmetic only — normalize CRM values, no source conflict |
7bbdfa.com and 50d386.com carry "health care" in both sources — normalize to Healthcare.
## 5. Top 10 fixes by pipeline amount at stake
Pipeline amounts are not available (no deals extract), so this list is ordered by estimated data-completeness blast radius (rows touched × fields × downstream blocking effect), not by dollars:
1. Merge cluster A (C-0A092932 → C-0A092931, domain acme-corp.com) — duplicate company splits pipeline rollups.
2. Merge cluster B (C-0A092934 → C-0A092933, domain globex.io) — same.
3. Fill 9 missing employee_counts from ZoomInfo (8 fillable: 400 each; C-93C8BF stays blank) — employee count drives segmentation and pricing tiers.
4. Fix 4 invalid emails (CT-0010, CT-0080, CT-0081, CT-0192) using each contact's own domain field — broken emails break outreach on 3 companies.
5. Resolve CT-0011 domain mismatch (user1@other-domain.com vs 66d1fc.com) — manual verification required.
6. Normalize industry values (tech/Tech /Technology/health care/SaaS → ZoomInfo taxonomy) across ~15 companies.
7. Normalize country values (US/USA/United States) across ~12 companies.
8. Backfill 13 blank contact titles (75% complete) — persona routing for outreach.
9. Backfill 15 blank contact personas (71.2% complete) — blocking lead-routing rules.
10. Blank hq_country on 6 companies (C-2D1F1B, C-D73B89, C-44EA29, C-D04904, C-2C60E5, C-EE9FFB) — cannot be filled from enrichment (blank or absent); requires re-enrichment or manual research.
Once the deals extract is supplied, this list should be re-ranked strictly by open pipeline amount per affected company/contact.
**Classification: 90 deals lost (all rows in closed_lost_6mo.csv)**
Rules applied: "Lost DM" and "Lost- Does not fit ICP" tags are mapped by free text. Competitor = a rival is named or the text says the buyer chose another vendor. Side = Bonusly when the text cites Bonusly's product, breadth, or fit; buyer when it cites budget, priority, timing, authority, or unresponsiveness; unknown when the text gives no cause.
Category codes: T=timing, C=competitor, N=no decision, P=product gap, PR=pricing, O=other. Side codes: B=Bonusly, Y=buyer, U=unknown.
1 Deal-DB0AAC T/Y
2 Deal-F7F635 C/U
3 Deal-AC944F N/Y
4 Deal-214060 N/Y
5 Deal-91A056 T/Y
6 Deal-29326C T/Y
7 Deal-5DB9B0 O/U
8 Deal-831B7B T/Y
9 Deal-F97C37 C/B
10 Deal-13E9CF N/Y
11 Deal-39E25C T/Y
12 Deal-7ED004 PR/Y
13 Deal-21B045 N/Y
14 Deal-B3ABED T/Y
15 Deal-422BA6 C/Y
16 Deal-ED9AE7 O/Y
17 Deal-988493 N/Y
18 Deal-381C8C N/U
19 Deal-F308CA N/Y
20 Deal-F1E8A6 N/U
21 Deal-B6AC09 T/Y
22 Deal-70F704 P/B
23 Deal-E6E80A T/Y
24 Deal-B038F0 T/Y
25 Deal-4664E1 N/Y
26 Deal-175756 T/Y
27 Deal-E74A73 N/Y
28 Deal-DDAB52 C/B
29 Deal-ACE061 C/U
30 Deal-BB78F3 T/Y
31 Deal-D48E0B N/Y
32 Deal-15DA99 T/Y
33 Deal-F4AF5D T/Y
34 Deal-79B7A1 T/Y
35 Deal-583ADB N/Y
36 Deal-8E27DA C/Y
37 Deal-2D2F8D C/U
38 Deal-E0441F N/U
39 Deal-7CB44D N/Y
40 Deal-0F96AA C/U
41 Deal-1BCA50 C/Y
42 Deal-7CC678 O/U
43 Deal-FAC17C N/Y
44 Deal-242273 C/U
45 Deal-50E5D8 N/Y
46 Deal-A2C349 C/B
47 Deal-9F176A T/Y
48 Deal-7B2236 PR/Y
49 Deal-AFA56C N/Y
50 Deal-C7156E C/U
51 Deal-C33D91 PR/Y
52 Deal-9048EB P/B
53 Deal-5E64CE T/Y
54 Deal-8A0992 C/Y
55 Deal-D0C698 C/Y
56 Deal-69CF3D T/Y
57 Deal-ECBF89 T/Y
58 Deal-3618CC P/B
59 Deal-EECC02 C/U
60 Deal-5AD03E PR/Y
61 Deal-D1A623 T/Y
62 Deal-413C56 N/Y
63 Deal-47F1A1 C/Y
64 Deal-BF2A98 C/Y
65 Deal-2A292B O/Y
66 Deal-D1AABF N/Y
67 Deal-FEDBCB T/Y
68 Deal-1E7DA9 C/U
69 Deal-2BBA21 N/Y
70 Deal-286F9C C/B
71 Deal-7FBAC6 N/Y
72 Deal-369281 C/Y
73 Deal-386F6E N/Y
74 Deal-9FCD0D C/Y
75 Deal-55867E N/U
76 Deal-DAFB82 PR/Y
77 Deal-2FEDDB T/Y
78 Deal-64B19A C/Y
79 Deal-3F86A0 N/Y
80 Deal-096750 N/Y
81 Deal-F325A5 N/Y
82 Deal-ABD14C N/Y
83 Deal-79E61A N/Y
84 Deal-8A119B PR/Y
85 Deal-AE7C4E N/Y
86 Deal-DAB4F1 N/Y
87 Deal-B4B50F N/Y
88 Deal-981AD4 P/B
89 Deal-DC77FE C/B
90 Deal-5885B9 N/Y
**Category counts (sum check: 21 + 23 + 32 + 4 + 6 + 4 = 90)**
- Timing: 21 (23.3%)
- Competitor: 23 (25.6%)
- No decision: 32 (35.6%)
- Product gap: 4 (4.4%)
- Pricing: 6 (6.7%)
- Other: 4 (4.4%)
- Champion left: 0
**Side split (sum check: 9 + 14 + 67 = 90)**
- Bonusly: 9 (10.0%)
- Buyer: 67 (74.4%)
- Unknown: 14 (15.6%)
**Tag vs. free-text disagreements: 12 flagged, 10 clear and 2 borderline**
Clear (10): Deal-13E9CF (tag Cost; text says "Not a budget issue"), Deal-9048EB (tag MIA; text cites bad fit and feature gaps), Deal-381C8C and Deal-F1E8A6 (tag Competitor; text says "not going to be moving forward," with no rival named), Deal-8E27DA (tag Feature Request; text says they didn't want R&R), Deal-5E64CE (tag Doing nothing; text cites contract lock-in through Oct 2027), Deal-3618CC (tag Lost DM; text says "Wanted Surveys"), Deal-5AD03E (tag Competitor; text says "Wanted more defined budget access"), Deal-2A292B (tag Doing nothing; text says "going to build something simple internally"), Deal-55867E (tag Timing; text says "don't think we'll be moving forward").
Borderline (2): Deal-70F704 (tag Lost DM; text is narrow use case plus MIA) and Deal-5DB9B0 (tag Does not fit ICP; text says "Spam.").
**Pattern 1: Most losses are parked, not lost to a rival (53 of 90, 58.9%)**
Timing (21) plus no decision (32). Of the no-decision deals, 22 carry the MIA tag. Five explicitly say the rep's outreach was ignored: Deal-F308CA, Deal-4664E1, Deal-7CB44D, Deal-2BBA21, Deal-096750. Action: require a dated re-engagement step on any timing or MIA close, and track reopen rates for the 2027 pushes.
**Pattern 2: Bonusly-side losses cluster on breadth and feature gaps (7 of 9 Bonusly-side losses)**
Deal-F97C37 (more diversified offerings), Deal-DDAB52 (more at the same cost), Deal-A2C349 (buyer adds surveying elsewhere), Deal-DC77FE (more customization), Deal-3618CC (wanted surveys), Deal-981AD4 (UI and UK focus), Deal-9048EB (feature gaps). Action: check surveys and customization against the roadmap. Product-side losses are small in count (9 Bonusly-side of 90, 10%), so validate before prioritizing.
**Data gaps**
- 14 deals have unknown side, including 7 competitor losses with no vendor named (Deal-F7F635, Deal-2D2F8D, Deal-0F96AA, Deal-242273, Deal-C7156E, Deal-EECC02, Deal-1E7DA9).
- Deal-ACE061 (HeyTaco) and Deal-64B19A (Motivosity) are inferred from text ("I feel," "likely"), not confirmed.
I can't return a verified JSON yet. Tiering 217 deals by hand would produce counts I can't check, so I haven't guessed them. Proposed rules, to confirm before I run them: - **LOCK:** COMMIT, stage DS4 or DS5, meetings_30d ≥ 2, last activity within 14 days. - **ACTION:** BEST_CASE or COMMIT, stage DS3 or DS4, meetings_30d ≥ 1, no open next step. - **BUILD:** PIPELINE, stage DS2 or DS3, n_contacts ≥ 3, emails_30d ≥ 3. - **REVIVE:** any open deal with last engagement older than 30 days and emails_30d ≤ 2. - **WATCH:** PIPELINE, stage DS1, and anything not covered above. - **RISKY:** COMMIT or BEST_CASE with zero meetings_30d and no calls_30d, or PIPELINE with meetings_30d ≥ 3 and emails_30d ≥ 5 in the last 14 days (forecast disagrees with engagement). Some deal rows are missing last_contacted or engagement fields, and inbound_emails_30d is 0 everywhere, as you noted. I would flag those deals as unscored rather than assign them a tier. Should I run these rules over the data and return the JSON? If you want a different threshold for any tier, say so first.
```json
[
{
"transcript_id": "TX-001",
"deal_alias": "Deal-CFE7F4",
"why_buys": ["The big win for us would be automating anniversary and birthday awards (Prospect (VP People))"],
"pain_points": [
"HR team of three cannot keep up with anniversary and birthday 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)); security review set for September 12 (Prospect (VP People))",
"competitor_mentioned": "Achievers. Prospect said they looked at it last year and it was too heavy for a team their size (Prospect (VP People))",
"next_step": "Security review on September 12 with IT lead. Prospect agreed: \"Yes — let's do the security review on September 12.\" IT lead is referenced but not on the speaker list.",
"objections": [
"Needs SSO and audit logs for IT sign-off (Prospect (HR Admin))",
"Achievers judged too heavy for team size (Prospect (VP People))"
],
"confidence": "High"
},
{
"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 the hourly workforce is over 30% (Prospect (Head of Total Rewards))"],
"stakeholders": ["Prospect (Head of Total Rewards)", "Prospect (CFO)"],
"budget_signal": "$25k pilot budget approved for this quarter (Prospect (CFO))",
"timeline_signal": "Decision by end of September (Prospect (CFO)); pilot agreement to legal this week (Prospect (CFO))",
"competitor_mentioned": null,
"next_step": "Send the pilot agreement; prospect will route it to legal this week. Prospect agreed: \"Yes — send the pilot agreement and we'll route it to legal this week.\" (Prospect (CFO))",
"objections": ["Workday integration must be rock solid; stated as the CFO's one condition (Prospect (CFO))"],
"confidence": "High"
},
{
"transcript_id": "TX-003",
"deal_alias": "Deal-530B50",
"why_buys": ["Make recognition visible across 12 retail locations (Prospect (People Ops Manager))"],
"pain_points": [
"Recognition is not visible across 12 retail locations (Prospect (People Ops Manager))",
"Store managers have zero budget autonomy for on-the-spot recognition today (Prospect (People Ops Manager))"
],
"stakeholders": ["Prospect (People Ops Manager)"],
"budget_signal": null,
"timeline_signal": "\"No rush on our side until Q1\" (Prospect (People Ops Manager))",
"competitor_mentioned": "Bucketlist. Prospect said the CEO used it at her last company and liked it (Prospect (People Ops Manager))",
"next_step": "Schedule a call with the CEO. Prospect agreed: \"Yes, let's schedule a call with our CEO — I'll send two times.\" No time has been set; prospect will send two options.",
"objections": ["No urgency until Q1 (Prospect (People Ops Manager))", "CEO must be sold first; she decides anything people-related (Prospect (People Ops Manager))"],
"confidence": "Medium. Decision maker (CEO) is not on the speaker list and the call is not yet scheduled. The ~$8/employee/month figure was stated by the rep, so it is excluded from budget_signal."
},
{
"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 recognition tools, none of which integrate with the HRIS (Prospect (VP People))"
],
"stakeholders": ["Prospect (VP People)", "Prospect (IT Security Lead)"],
"budget_signal": "Prospect can approve without the board if under $15k annually (Prospect (VP People))",
"timeline_signal": "Procurement cycle is six to eight weeks minimum (Prospect (IT Security Lead)); last vendor's security review took three months (Prospect (IT Security Lead))",
"competitor_mentioned": null,
"next_step": null,
"objections": [
"Procurement takes six to eight weeks minimum (Prospect (IT Security Lead))",
"Security review concern based on three months for the last vendor (Prospect (IT Security Lead))"
],
"confidence": "Medium. The CFO follow-up was not agreed: prospect said \"Maybe — I need to check her calendar, no promises.\" The CFO is not on the speaker list."
},
{
"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; their 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": "Must be running before the January all-hands (Prospect (HR Director))",
"competitor_mentioned": "Nectar. Prospect said they are mid-pilot with Nectar and the offering would need to beat that experience (Prospect (HR Director))",
"next_step": "Present to the exec team on October 2. Prospect agreed: \"Yes — come present to our exec team on October 2.\"",
"objections": [
"Exec team is skeptical after a failed rollout two years ago (Prospect (HR Director))",
"Must beat the Nectar pilot experience (Prospect (HR Director))"
],
"confidence": "High. The October 2 date is before today (October 19, 2026); verify whether it refers to a past meeting."
},
{
"transcript_id": "TX-006",
"deal_alias": "Deal-EE195F",
"why_buys": ["Cut the admin time on service awards (Prospect (HR Manager))"],
"pain_points": ["Spends five hours a month ordering and shipping plaques (Prospect (HR Manager))"],
"stakeholders": ["Prospect (HR Manager)"],
"budget_signal": null,
"timeline_signal": "Fiscal year resets in February; a Q1 start is realistic (Prospect (HR Manager))",
"competitor_mentioned": null,
"next_step": "Rep sends the one-page overview; prospect will forward it to the COO this week. Prospect agreed: \"Yes — send the one-page overview and I'll forward it to our COO this week.\"",
"objections": [
"Comparing against building it internally; prospect said \"Nobody else\" is being considered (Prospect (HR Manager))",
"COO usually prefers building things in-house (Prospect (HR Manager))"
],
"confidence": "Medium. No budget figure was stated; the prospect said \"Budget isn't the issue — time is,\" which is not a dollar amount. The COO is not on the speaker list."
}
]
```
Data gaps and flags:
- TX-001: the security review date (September 12) and TX-005: the exec presentation date (October 2) are both before today (October 19, 2026). Confirm they are not stale.
- TX-003 and TX-004: the decision makers (CEO, CFO) are referenced but not on the speaker list, so they are not listed as stakeholders.
- TX-006: no budget amount was given.
Data caveats first: the only Slack evidence is dated 2026-09-04, ~6 weeks before today (2026-10-19), and several COMMIT deals (Deal-B7EBD1, Deal-3974EB, Deal-C26D20, etc.) have no Slack signal at all — status unknown. 1. Deal-547B2B — $11,200 — Alex Franklin — DS5/COMMIT Why close: redlines back clean, signing page out, VP People said they sign tomorrow. Explicitly "signature-imminent." Left: counter-signed signature only. 2. Deal-403845 — $9,000 — CRM owner Alex Franklin / Dana Mercer claims it in Slack Why close: order form is with their finance team — post-legal, execution-stage. No freeze reported. Left: finance sign-off and return of the order form. Owner attribution conflict between CRM and Slack should be resolved. 3. Deal-A2B47C — $6,360 — Alex Franklin — DS5/COMMIT Why close: Alex confirmed still warm, "normal legal-review pace," no procurement freeze. Left: legal review completion, then signature. Earlier CRM close date (2026-09-11) than the other legal-stage deals. Excluded: Deal-2465CE ($5,400) — champion left, procurement froze vendors; Dana pulled it from commit, now Q4. Runner-up: Deal-D348E1 ($13,770, COMMIT) — same "normal legal-review" status as Deal-A2B47C, but later close date (2026-10-15), so it ranks fourth on available evidence.
Real gaps (summary) 1. Deal-EC3025: SCIM user provisioning Prospect (IT Security Lead): "We need SCIM user provisioning — our security team will not approve any tool that requires manual account management." Docs: SCIM is listed under "NOT currently listed as supported capabilities." It also does not appear in the plans table. Amount: not in the provided data. 2. Deal-D0D6B5: ADP Workforce Now integration Prospect (HRIS Manager): "Our payroll runs on ADP Workforce Now and I don't see ADP anywhere in your integration list — that's a dealbreaker for us." Docs: ADP is listed under "NOT currently listed as supported capabilities." HRIS integrations are limited to Workday, BambooHR, Gusto, and Rippling. Amount: not in the provided data. Excluded from summary - TG-003, Deal-CFE7F4 (custom report builder): Plan gate. Docs place the custom report builder on Enterprise only. Prospect (VP People): "I tried to build a custom report combining recognition frequency with turnover and couldn't — is that possible on our current plan?" - TG-004, Deal-84DBA6 (manager adoption): Rollout/enablement issue. The Slack integration is available on all plans, and the prospect says managers were never trained. Prospect (People Ops Manager): "...half our managers still haven't given a single recognition — nobody ever trained them on it." - TG-005, Deal-36C33F (mobile app): Not a prospect-raised gap. The mobile statement is from the rep (Alex Franklin), which does not count as prospect voice. The prospect (HR Manager) said: "The web version should be fine for our office staff for now." The docs do not mention a mobile app either way. Data gaps - No deal amounts were provided for any deal alias, so I cannot state dollar exposure or totals. Amounts for Deal-EC3025 and Deal-D0D6B5 need to come from the CRM. - The docs excerpt is a 2026-08 snapshot, and the transcripts are the only source for prospect statements.
Stale = no email, call, or meeting in the last 7 days. Recency = max(last_email, last_call, last_meeting) from the engagements table; days = 2026-09-05 minus that date. A deal is stale when days > 7 (last contact on or before 2026-08-29). Sorted by owner, amount descending. Data gaps, stated up front: - Deal-3EED2C (Alex Franklin, DS2, $7,200) has NO row in the engagements table — recency cannot be computed from the required fields, so it is excluded from the stale list. - Deal-57FF13 (Elena Sinclair, DS1, $2,100) also has no engagements row — excluded for the same reason. - Some engagements rows contain future-dated meetings (e.g., Deal-93C8BF meeting 2026-09-14); I treated any future date as "recent," so those deals are not stale. Alex Franklin (owner 84342457) - Deal-CC08D1 | DS1 | $24,000 | 16 days since 2026-08-20 - Deal-E73427 | DS3 | $18,000 | 10 days since 2026-08-26 - Deal-885F45 | DS2 | $9,300 | 12 days since 2026-08-24 - Deal-C2FF3C | DS1 | $8,316 | 10 days since 2026-08-26 - Deal-0D2F7A | DS3 | $5,100 | 12 days since 2026-08-24 - Deal-6C60D4 | DS3 | $4,800 | 12 days since 2026-08-24 - Deal-13FEBD | DS2 | $4,680 | 12 days since 2026-08-24 - Deal-9D0060 | DS3 | $3,840 | 12 days since 2026-08-24 - Deal-690476 | DS2 | $3,600 | 18 days since 2026-08-18 - Deal-C6D97A | DS4 | $3,240 | 8 days since 2026-08-28 - Deal-EE195F | DS3 | $3,120 | 8 days since 2026-08-28 - Deal-278DEC | DS3 | $2,700 | 8 days since 2026-08-28 - Deal-635B8E | DS3 | $2,600 | 18 days since 2026-08-18 - Deal-6883F3 | DS1 | $2,400 | 16 days since 2026-08-20 - Deal-4A13AD | DS3 | $2,160 | 26 days since 2026-08-10 - Deal-F67D31 | DS2 | $1,800 | 8 days since 2026-08-28 - Deal-5FDCE4 | DS3 | $1,600 | 12 days since 2026-08-24 - Deal-BA571A | DS4 | $1,080 | 18 days since 2026-08-18 Total: 18 stale deals, $102,336. Bryce Harmon (owner 119337721) - Deal-2D1F1B | DS1 | $240,000 | 81 days since 2026-06-16 - Deal-66D1FC | DS1 | $99,000 | 16 days since 2026-08-20 - Deal-950043 | DS1 | $70,000 | 19 days since 2026-08-17 - Deal-B23205 | DS1 | $45,000 | 16 days since 2026-08-20 - Deal-7BBDFA | DS3 | $37,440 | 46 days since 2026-07-21 - Deal-332637 | DS2 | $36,000 | 9 days since 2026-08-27 - Deal-1BEEBF | DS1 | $31,500 | 19 days since 2026-08-17 - Deal-C5658B | DS1 | $23,400 | 16 days since 2026-08-20 - Deal-40522D | DS3 | $21,000 | 19 days since 2026-08-17 - Deal-F0EBBB | DS3 | $11,400 | 24 days since 2026-08-12 - Deal-E25A09 | DS1 | $6,000 | 9 days since 2026-08-27 - Deal-C9C286 | DS2 | $5,502 | 9 days since 2026-08-27 - Deal-012CB1 | DS1 | $1 | 23 days since 2026-08-13 Total: 13 stale deals, $626,243. Cole Ingram (owner 83155924) - Deal-D04904 | DS2 | $58,529.25 | 11 days since 2026-08-25 - Deal-B25F40 | DS3 | $40,000 | 8 days since 2026-08-28 - Deal-813836 | DS2 | $32,175 | 11 days since 2026-08-25 - Deal-1BA595 | DS2 | $31,750 | 11 days since 2026-08-25 - Deal-CFE1E8 | DS3 | $18,000 | 11 days since 2026-08-25 - Deal-CD47A6 | DS2 | $12,168 | 11 days since 2026-08-25 - Deal-627646 | DS3 | $11,193 | 11 days since 2026-08-25 - Deal-FF809F | DS2 | $7,781.20 | 11 days since 2026-08-25 - Deal-AF932D | DS2 | $7,225.40 | 11 days since 2026-08-25 - Deal-A71728 | DS2 | $6,947.50 | 11 days since 2026-08-25 - Deal-8BC9F5 | DS2 | $5,616 | 10 days since 2026-08-26 - Deal-175395 | DS3 | $4,779.88 | 11 days since 2026-08-25 - Deal-481E24 | DS3 | $4,140 | 10 days since 2026-08-26 - Deal-C7F9BF | DS2 | $3,360 | 11 days since 2026-08-25 - Deal-2F3A66 | DS3 | $3,334.80 | 11 days since 2026-08-25 - Deal-342E96 | DS2 | $2,700 | 24 days since 2026-08-12 - Deal-E568D5 | DS3 | $1,875 | 11 days since 2026-08-25 - Deal-FD9F4E | DS5 | $1,330 | 10 days since 2026-08-26 Total: 18 stale deals, $252,905.03. Dana Mercer (owner 83155923) - Deal-44EA29 | DS2 | $60,000 | 10 days since 2026-08-26 - Deal-E51FB7 | DS2 | $43,875 | 12 days since 2026-08-24 - Deal-B42F46 | DS1 | $27,000 | 19 days since 2026-08-17 - Deal-BA3DDC | DS3 | $23,400 | 15 days since 2026-08-21 - Deal-9DDE86 | DS2 | $20,000 | 15 days since 2026-08-21 - Deal-215CCA | DS3 | $18,900 | 17 days since 2026-08-19 - Deal-5EED42 | DS3 | $16,250 | 11 days since 2026-08-25 - Deal-57887A | DS2 | $15,000 | 8 days since 2026-08-28 - Deal-B7EBD1 | DS5 | $9,000 | 16 days since 2026-08-20 - Deal-3974EB | DS4 | $9,000 | 8 days since 2026-08-28 - Deal-F40F04 | DS2 | $8,100 | 15 days since 2026-08-21 - Deal-87DDD1 | DS1 | $5,000 | 19 days since 2026-08-17 - Deal-F336B6 | DS3 | $4,200 | 15 days since 2026-08-21 - Deal-0660B4 | DS4 | $1,920 | 16 days since 2026-08-20 Total: 14 stale deals, $261,645. Farid Osman (owner 716654662): 0 stale deals (all his engagements rows show contact within 7 days, counting future-dated meetings as recent). Elena Sinclair (owner 701163055): cannot assess — her only deal (Deal-57FF13) has no engagements row. Overall: 63 stale deals across 4 assessable owners, $1,243,129.03 total stale amount. ⚠️ 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/.hermes/cache/scratch/deals_open.csv` — [write_file] Refusing to overwrite `/Users/amaniphipps/.hermes/cache/scratch/deals_open.csv`: `/Users/amaniphipps/.hermes/cache/scratch/deals_open.csv` exists but this task has not seen its full c…
Snapshot 2026-09-05. Window: 2026-08-06 to 2026-09-05 (30 days). Activity = sum of emails_30d + calls_30d + meetings_30d across each owner's deals. DS2 entries = deals with t_ds2 in the window. Per rep (E = emails, C = calls, M = meetings, T = total; mix = E/C/M share of T) 1. Alex Franklin: E 307, C 36, M 41, T 384. Mix 79.9% / 9.4% / 10.7%. DS2 entries 18. Activities per DS2 = 384 / 18 = 21.3 2. Bryce Harmon: E 162, C 0, M 43, T 205. Mix 79.0% / 0.0% / 21.0%. DS2 entries 4. Activities per DS2 = 205 / 4 = 51.3 3. Cole Ingram: E 96, C 14, M 1, T 111. Mix 86.5% / 12.6% / 0.9%. DS2 entries 2. Activities per DS2 = 111 / 2 = 55.5 4. Farid Osman: E 38, C 0, M 34, T 72. Mix 52.8% / 0.0% / 47.2%. DS2 entries 1. Activities per DS2 = 72 / 1 = 72.0 5. Dana Mercer: E 84, C 18, M 11, T 113. Mix 74.3% / 15.9% / 9.7%. DS2 entries 1. Activities per DS2 = 113 / 1 = 113.0 6. Elena Sinclair: no ratio. T 0, DS2 entries 0. Her only deal (Deal-57FF13) has no row in the engagements file, so its activity is unknown, not zero. Ranking by activities per DS2 entry (lowest = most efficient): Alex Franklin (21.3), Bryce Harmon (51.3), Cole Ingram (55.5), Farid Osman (72.0), Dana Mercer (113.0). Elena Sinclair is unranked. Most efficient: Alex Franklin (21.3). Highest volume: Alex Franklin (384 total activities). Same rep for both. Data notes: - Deal-3EED2C (Alex Franklin) entered DS2 on 2026-09-03 and is counted, but it has no engagements row, so it contributes 0 activity. If it had any activity, Alex's ratio would be lower than 21.3, not higher. - Deal-57FF13 (Elena Sinclair) has no engagements row. - The engagements file has last_meeting dates after the snapshot (e.g., 2026-09-14, 2026-10-02). They do not affect these 30-day counts, which come from the emails_30d, calls_30d, and meetings_30d columns; I did not verify those columns against source systems. - Gavin Porter and Hugo Lindqvist are archived and own no deals in the file.
Alex Franklin QTD scorecard, as of 2026-09-05. Quarter is 2026-Q3 (2026-07-01 through 2026-09-30). Quota from quota.csv is $200,000. Deal-B3E6F1 ($24,000, closed won 2026-06-20, new) is excluded from bookings because it closed before the quarter. Bookings vs quota QTD closed-won on or before 2026-09-05: 8 deals, $150,000. Attainment: 150,000 / 200,000 = 75.0%. Gap: $50,000. New: Deal-A1C3E5 $40,000 + Deal-B7D2F4 $35,000 + Deal-C9E1A6 $21,000 + Deal-D4B8C2 $11,000 + Deal-E6F3A9 $6,500 = $113,500 (75.7% of bookings). Expansion: Deal-F2C7D8 $20,000 + Deal-A8B4D6 $12,000 + Deal-C5D9E2 $4,500 = $36,500 (24.3%). Active pipeline (status=open, 125 deals, $1,260,390) DS1: 20 deals, $284,621 DS2: 28 deals, $353,760 DS3: 67 deals, $552,705 DS4: 5 deals, $23,574 DS5: 5 deals, $45,730 Check: 284,621 + 353,760 + 552,705 + 23,574 + 45,730 = 1,260,390. Rolling 90-day DS2-to-won Window: entered_ds2 from 2026-06-07 through 2026-09-05 (90 days back from the snapshot). 111 deals entered DS2. Of those, 8 won, 27 lost, 76 still open. Closed rate: 8 / (8+27) = 8/35 = 22.9%. Including still-open: 8/111 = 7.2%. Won dollars in that cohort equal QTD bookings ($150,000); lost dollars $329,272. Win and loss counts QTD wins: 8. QTD losses (close date 2026-07-01 through 2026-09-05): 27, $329,272. No losses in the file closed before the quarter. Top loss reason: Lost- Timing (1 year or more), 13 of 27 losses (48.1%) and $184,681 of $329,272 (56.1%). Next: Competitor 5 deals / $49,020; MIA 5 / $45,831; Lost DM 2 / $17,940; Feature Request 1 / $21,000; Lost- Does not fit ICP (write in notes) 1 / $10,800. Activity, last 30 days (columns already windowed; all 161 deal rows) Emails 807, meetings 128, calls 112, notes 50. Total 1,097. Open book only: emails 599, meetings 90, calls 54, notes 1. 103 of 125 open deals had zero calls. One open deal had zero activity of any type (Deal-3EED2C). Coaching 1. Timing is the loss pattern, not competitive losses. 13 of 27 QTD losses, and more than half the lost dollars, are "Lost- Timing (1 year or more)." Those deals had already entered DS2. The 22.9% closed DS2-to-won rate (8 won vs 27 lost) is mostly a qualification problem, not a late-stage close problem. 2. The $50,000 gap is not covered by DS5 alone. DS5 is $45,730, $4,270 short of the gap. DS4+DS5 is $69,304 across 10 deals. The other $1,191,086 sits in DS1-DS3, so the open-pipeline total is not this-quarter coverage. 3. Open-pipeline activity is email, not conversation. 599 emails against 54 calls and 1 note on 125 open deals, and 103 of those deals had no call in 30 days. The 9 won rows in the activity file show a different mix (33 calls and 24 notes). The open book is not being worked the way the won deals were.
Data gaps first: the file has no amount or stage fields for any deal (and no open/closed flag) — so amount = not provided, stage = not provided for every deal below, and "most valuable persona to add" is picked without stage information (I note the assumption). Today = 2026-10-19, so active = last_engaged_date ≥ 2026-08-20 and is_former = false.
Flagged deals (7 of 12; Deal-84DBA6, Deal-4B0BEB, Deal-D348E1 are healthy and excluded):
1. Deal-EC3025 (C-FDD0C7) — amount: not provided; stage: not provided.
Active contacts: 1 (CT-047C54, champion). CPO is former. Single-threaded.
Personas present: champion. Missing: economic buyer, HR admin, IT security, finance.
Most valuable add: economic buyer (assumed — no stage on file). Fits on file: CT-6827DB (Chief People Officer, economic buyer).
2. Deal-92D97D (C-E23238) — amount/stage: not provided.
Active: 1 (CT-01F5B4, HR admin; champion last engaged 2026-06-01 = ~140 days, inactive). Single-threaded.
Present: HR admin. Missing: champion, economic buyer, IT security, finance.
Most valuable add: champion (no deal champion currently active). None on file at C-E23238.
3. Deal-50D386 (C-EB10E4) — amount/stage: not provided.
Active: 2 (champion 09-01, HR admin 08-25). Under-threaded (<3).
Present: champion, HR admin. Missing: economic buyer, IT security, finance.
Most valuable add: economic buyer. Fits on file: CT-A1C4B3 (Chief People Officer, economic buyer).
4. Deal-D0D6B5 (C-32918E) — amount/stage: not provided.
Active: 1 (CT-87CED4, champion; other two champions engaged 08-19 and 08-07 = 61 and 73 days ago — outside 60). Also single-persona even at full roster (all three are champions). Single-threaded and under-threaded.
Present: champion. Missing: economic buyer, HR admin, IT security, finance.
Most valuable add: economic buyer. Fits on file: CT-1FA4DB (Chief People Officer, economic buyer).
5. Deal-5BFE3B (C-535D36) — amount/stage: not provided.
Active: 1 (CT-57123B, champion; second champion 08-12 = 68 days, inactive). Single-threaded, single-persona.
Present: champion. Missing: economic buyer, HR admin, IT security, finance.
Most valuable add: economic buyer. None on file at C-535D36.
6. Deal-36C33F (C-077A0E) — amount/stage: not provided.
Active: 0. Champion and economic buyer are both former; IT security last engaged 08-15 = 65 days ago, inactive. Most severe deal on the list.
Present (active): none. Missing: all five personas.
Most valuable add: economic buyer (re-establish executive sponsorship). Fits on file: CT-1DB73E (Chief People Officer, economic buyer).
7. Deal-885F45 (C-5E8EFB) — amount/stage: not provided.
Active: 1 (CT-51C81E, economic buyer; champion 08-11 = 69 days, inactive). Single-threaded.
Present: economic buyer. Missing: champion, HR admin, IT security, finance.
Most valuable add: champion (EB engaged, no one to carry it). No unengaged champion on file; only CT-B3F25D (IT Security Lead) fits a missing persona.
8. Deal-FCBE5B (C-737030) — amount/stage: not provided.
Active: 1 (champion, 08-29). Single-threaded.
Present: champion. Missing: economic buyer, HR admin, IT security, finance.
Most valuable add: economic buyer. None on file at C-737030.
9. Deal-5408B0 (C-2AE3AA) — amount/stage: not provided.
Active: 1 (champion 09-01; HR admin 08-18 = 62 days, inactive). Single-threaded.
Present: champion. Missing: economic buyer, HR admin, IT security, finance.
Most valuable add: economic buyer. Fits on file: CT-07FA76 (Chief People Officer, economic buyer).
10. Deal-C6D97A (C-5A8FC2) — amount/stage: not provided.
Active: 2 (champions 08-31 and 08-20 — the latter exactly at the 60-day boundary; if you read "last 60 days" as strict, count drops to 1). Either way, all contacts are champions → under-threaded (single persona).
Present: champion. Missing: economic buyer, HR admin, IT security, finance.
Most valuable add: economic buyer. None on file at C-5A8FC2.
11. Deal-F9A08A (C-0D15DF) — amount/stage: not provided.
Active: 1 (champion 09-03; economic buyer last engaged 2026-06-20 = 121 days, inactive — a re-engagement candidate, CT-913581). Single-threaded.
Present: champion. Missing: economic buyer, HR admin, IT security, finance.
Most valuable add: economic buyer. Fits on file: CT-697541 (Chief People Officer, economic buyer).
Not flagged: Deal-84DBA6 (3 active: champion, economic buyer, IT security — the 08-20 IT contact sits exactly on the 60-day boundary; if strict, it drops to 2 active across 2 personas and becomes under-threaded), Deal-4B0BEB (3 active: champion, economic buyer, HR admin), Deal-D348E1 (4 active: champion, economic buyer, IT security, finance).
Priority view: Deal-36C33F has zero active threads and two former senior contacts — the clear top risk. Deal-885F45 is the only deal whose single active thread is the economic buyer with no champion.
First five minutes Alex Franklin leads with the same retailer turnover-results story in 8/10 calls = 80%: Deal-D348E1, Deal-5408B0, Deal-547B2B, Deal-C61CF7, Deal-60C2C2, Deal-EDC141, Deal-D9A12F, and Deal-84DBA6. The story claims an 18% reduction in regretted turnover after automating milestone awards; the supplied data does not independently verify that result. The other openings are security review followed by pricing in Deal-403845 and prospect-requested pricing in Deal-1E2498: 1/10 = 10% each. Three most common objections Counts below are calls containing each objection; categories can overlap. 1. Budget/funding approval: 5/10 = 50%. Deal-D348E1, Deal-547B2B, Deal-60C2C2, and Deal-84DBA6 raise locked budgets; Deal-403845 raises budget-committee approval. Alex counters locked budgets with the retailer’s claimed $210k in avoided backfills. When committee approval blocks Deal-403845 and Deal-84DBA6, he accepts the delay without securing an action. Evidence, Deal-403845, minute 12: “Understood — I'll leave it with you.” 2. Timing/workload: 3/10 = 30%. Deal-5408B0, Deal-C61CF7, and Deal-D9A12F ask to revisit next quarter because of open enrollment. Alex proposes a one-department, 90-day pilot to produce internal evidence before planning. Evidence, Deal-5408B0, minute 8: “Makes sense. What if we scope a 90-day pilot with one department so you have internal data before next quarter's planning?” 3. Existing spreadsheet/gift-card process: 3/10 = 30%. Deal-403845, Deal-EDC141, and Deal-1E2498 question why they should change. Alex responds with automated milestones and recognition analytics rather than eliciting the prospect’s specific shortcomings. Evidence, Deal-1E2498, minute 8: “Spreadsheets work until they scale — the difference is automation: milestones fire without HR lifting a finger, and you get analytics on who is being recognized.” Concrete next-step agreement rate 7 agreed calls ÷ 10 total calls × 100 = 70%. Agreed: Deal-D348E1, Deal-5408B0, Deal-547B2B, Deal-C61CF7, Deal-60C2C2, Deal-D9A12F, and Deal-1E2498. Each prospect accepts Thursday at 2pm and commits to bringing an HRIS manager to the working session. Evidence, Deal-D348E1, minute 15: “Yes, Thursday at 2pm works — send the invite and I'll bring our HRIS manager.” No concrete next step is agreed in Deal-403845, Deal-EDC141, or Deal-84DBA6. Meeting completion is not provided. Every competitor raised by a prospect - Awardco — Deal-547B2B, minute 4: “We're also in late talks with Awardco — their rewards catalog looks bigger than yours.” - Kudos — Deal-EDC141, minute 4: “How are you different from Kudos? Our CEO used them at her last company.” Workhuman is mentioned only by Alex in Deal-C61CF7, not by a prospect, so it is excluded. Two coaching notes 1. Tailor discovery before repeating the retailer story. Ask about the prospect’s turnover costs and current recognition workload before applying the savings or automation argument. 2. Convert committee and urgency stalls into a mutually agreed action: identify the decision owner, required evidence, and a dated follow-up instead of accepting an open-ended delay.
**Q3 2026 forecast (close date 2026-07-01 to 2026-09-30)** **Category totals (in-quarter, 54 deals)** - COMMIT: 7 deals, $44,729 11,200 + 9,000 + 9,000 + 6,360 + 5,400 + 2,520 + 1,249 = 44,729 - BEST_CASE: 24 deals, $203,565 - PIPELINE: 23 deals, $201,637.40 (weight 0; excluded from forecast) **Weighted forecast** - COMMIT at 100%: $44,729 - BEST_CASE at 35%: 203,565 × 0.35 = $71,247.75 - Forecast: 44,729 + 71,247.75 = **$115,976.75** **Excluded (close date outside quarter)** - 32 deals, $227,575 total (9 BEST_CASE, 1 COMMIT, 22 PIPELINE) - Includes Deal-D348E1 (COMMIT, $13,770, closes 2026-10-15) and Deal-E51FB7 (PIPELINE, $43,875, closes 2026-10-01) **Top 5 BEST_CASE in quarter** 1. Deal-2D7423: $38,935 (DS3, 2026-09-30) 2. Deal-25F752: $24,000 (DS4, 2026-09-25) 3. Deal-E53952: $19,656 (DS4, 2026-09-30) 4. Deal-5EED42: $16,250 (DS3, 2026-09-30) 5. Deal-FA32A0: $11,116 (DS3, 2026-09-25) ## Data quality Owner is blank on 85 of 86 rows, so no deal can be routed or validated against a rep. Deal-A5E80A (DS1) and Deal-499BF6 (DS2) are marked COMMIT at early stages that do not support it, and Deal-42326B has a fractional amount ($2,480.40). The extract is dated 2026-09-05 but today is 2026-10-19, so every in-quarter deal with a close date before 2026-10-19 is past due with no refreshed stage or category, and the data gives no way to tell which are still live.
Analysis run on the full extract: 220 companies, all retained-relevant (per the prompt, every company is 25+ months old, so active = retained at 24 months). Excluded from denominator: none — every company in the file has valid m1_users and m1_redemptions values, and none needed to be dropped. 2x2 (signal = m1_users >= 5 givers; m1_redemptions >= 1): - Both signals: 47 companies, 31 active, 66.0% retention (31/47) - Givers-only: 49 companies, 23 active, 46.9% retention (23/49) - Redemption-only: 29 companies, 9 active, 31.0% retention (9/29) - Neither: 95 companies, 38 active, 40.0% retention (38/95) Check: 47+49+29+95 = 220 = full file. Overall retention 101/220 = 45.9%. Hypothesis verdict: supported directionally. The "both" cell (66.0%) beats every other cell, and the ordering is both > givers-only > neither > redemption-only. Largest single-signal lift: givers-only, +6.9 points over the neither baseline (46.9% vs 40.0%). Redemption-only is not a lift at all — it's 9 points BELOW neither (31.0% vs 40.0%), so it's the weakest single signal in this extract. What this proves and doesn't prove: Proves (within this extract): among these 220 companies, early giver breadth combined with a successful redemption is associated with higher 24-month retention, and the combination outperforms either signal alone. Does not prove: 1. Causation. This is observational; healthy companies may adopt broadly and redeem early because they were going to retain anyway (selection effect), not because activation drove retention. 2. Generalizability. One extract, 2023 signups only, 220 companies; no confidence intervals or significance testing were requested or performed, and cell sizes (29-95) are small enough that a few companies could move these rates meaningfully. 3. Mechanism. Nothing here shows WHY redemption-only companies underperform the neither cell — that counterintuitive result (31.0% < 40.0%) suggests redemption without giver breadth may mark single-person/low-adoption accounts, but the data provided cannot distinguish that from noise. 4. Completeness of covariates. Tier is heavily confounded with status (cancelled rows are nearly all tier_two with $0 ARR); the extract does not include contract terms, so retention differences may partly reflect product tier or contract mechanics rather than activation behavior. Data caveats stated: the file has no excluded rows; missing industry/country values exist but are irrelevant to the hypothesis; current_status has three values (active / cancelled / non_renewing) and I counted only active as retained, treating cancelled and non_renewing both as not retained.
**ARR reconciliation as of 2026-09-05** Scope: 39 Chargebee subscriptions, 39 CRM company rows. Billing ARR counts active subscriptions only (MRR x 12). Cancelled subscriptions contribute $0. The files contain no snapshot date, so I took the data as-is for 2026-09-05. **Totals** - Billing ARR: 37 active subs, sum of MRR x 12 = $604,739.28 - CRM ARR (hubspot_arr, all 39 rows) = $603,581.76 - Variance (CRM minus billing) = 603,581.76 - 604,739.28 = **-$1,157.52** **Variance decomposition (sums exactly to -1,157.52)** - Status mismatch: +$13,158.48 - C-0C8323BF (SUB-000E, cancelled): CRM 4,905.24 vs billing 0 - C-0DC4FB8C (SUB-000F, cancelled): CRM 8,253.24 vs billing 0 - Missing records: -$11,952.00 - CRM-only, no subscription: C-0D5BBE3A, +16,497.24 - Billing-only, no CRM record: C-21629AA4 (SUB-0004), -28,449.24 (2370.77 x 12) - Rounding: +$36.00 - C-0D66DF9E (SUB-0005): CRM 23,200.00 vs billing 1932 x 12 = 23,184.00, diff +16 - C-14D70CE0 (SUB-0008): CRM 18,200.00 vs billing 1515 x 12 = 18,180.00, diff +20 - Both CRM values look like the billing figure rounded to the nearest $100. That is my inference, not something the data states. - Other: -$2,400.00 - C-0F7269D7 (SUB-0006): CRM 24,396.00 vs billing 2233 x 12 = 26,796.00, diff -2,400. A 2,400 gap equals 200 MRR x 12, and 2033 x 12 = 24,396, so this may be a keying error in the CRM. Unconfirmed. Check: 13,158.48 - 11,952.00 + 36.00 - 2,400.00 = -1,157.52 ✓ All other 33 matched accounts tie exactly to the cent. **Mismatched accounts and suggested owners** No owner field exists in the data, so these are suggested by function. 1. C-21629AA4 (SUB-0004): billing only, $28,449.24. Owner: RevOps / CRM admin, to create or link the company record. 2. C-0D5BBE3A: CRM only, $16,497.24. Owner: Billing ops, to confirm whether it is a live customer and, if so, create the subscription. 3. C-0C8323BF (SUB-000E): cancelled in billing, CRM $4,905.24. Owner: Account owner / CRM admin, to zero out ARR. 4. C-0DC4FB8C (SUB-000F): cancelled in billing, CRM $8,253.24. Owner: Account owner / CRM admin, to zero out ARR. 5. C-0F7269D7 (SUB-0006): CRM is $2,400 below billing. Owner: Billing ops, to confirm MRR 2233 vs CRM value. 6. C-0D66DF9E (SUB-0005): $16 rounding. Owner: RevOps, to sync CRM to billing. 7. C-14D70CE0 (SUB-0008): $20 rounding. Owner: RevOps, to sync CRM to billing. **Term rule violations (term other than 12 months, cf_agreement_end_date blank)** - SUB-0002 (C-1794A52C): 24-month term, no end date - SUB-0019 (C-22170CA1): 36-month term, no end date Compliant non-12-month subscriptions: SUB-000C (C-0DB48281, 24 months, end 2027-11-30) and SUB-001A (C-0FC4DBB8, 36 months, end 2027-11-30). **Gaps** - No owner or account-owner data was provided. - No CRM status field was provided, so the status mismatches are inferred from the cancelled billing status and the non-zero CRM ARR.
| KVM | 2026-08 | 2026-07 | Abs. change | Rel. change | Direction | |---|---|---|---|---|---| | Giving rate | 0.6027 | 0.6023 | +0.0004 | +0.07% | Flat (up) | | Redemptions per user | 1.7302 | 1.7300 | +0.0002 | +0.01% | Flat (up) | | 1:1 meetings engagement | 0.4472 | 0.4469 | +0.0003 | +0.06% | Flat (up) | | Pulse check engagement | 0.5086 | 0.6006 | -0.0920 | -15.31% | Down | Method: unweighted mean of the 30 company rows per month (10 smb, 10 mid_market, 10 enterprise). No account weights or denominators were provided. Largest relative move: pulse check engagement, -15.31% (-0.0920 / 0.6006). Driver: size_band = enterprise. Enterprise pulse fell from 0.5500 to 0.2743 (-0.2757, -50.1%). All 10 enterprise accounts dropped, each to between 0.2619 and 0.2864. Non-enterprise pulse was flat, 0.6259 to 0.6258. plan_tier cannot be tested as a driver: all 30 rows are tier_three. The enterprise drop is uniform across all 10 accounts and roughly halves in one month. That pattern could point to an instrumentation or survey change rather than a behavior change. The data cannot confirm which.
**Redemption section, Jan–Aug 2026 (through 2026-08)** **Last completed month:** 2026-09 is the last completed month as of Oct 19, 2026. The file has no September rows (latest date is 2026-08-31), so September is missing from the data. This section covers 2026-01-01 to 2026-08-31 as requested. - **Redemption count:** 378 - **Spend:** $27,846.00 - **Unique redeemers:** 234 (distinct user_key) - **Redemptions per redeemer:** 378 / 234 = 1.62 **Provider mix (share of spend, $27,846.00 total)** | Provider | Redemptions | Spend | Share of spend | |---|---|---|---| | custom | 37 | $10,873 | 39.05% | | Tremendous | 192 | $8,505 | 30.54% | | Snappy | 59 | $5,238 | 18.81% | | TangoCard | 90 | $3,230 | 11.60% | | **Total** | **378** | **$27,846** | **100.00%** | Check: 10,873 / 27,846 = 39.05%; 8,505 / 27,846 = 30.54%; 5,238 / 27,846 = 18.81%; 3,230 / 27,846 = 11.60%. Sum = 100.00%. **Top 5 countries by redemptions** 1. US: 244 2. CA: 24 3. AU: 21 4. GB: 17 5. NL: 17 (tied with GB; both shown) Next is SG at 12. Caveat: I transcribed the CSV into a script by hand, so the 378-row count and the totals depend on that transcription. Confirm the row count against the source file before publishing.
Eligibility is gated only by R1–R3 (health < 60, eligible amount > 0, renewal ≤ 2026-09-05 + 120 days = 2027-01-03). Play assignment is not defined in eligibility_rules.csv, so the play below is analyst judgment from the cited signals. QUALIFIERS — 8 accounts, $224,601 total churn-save eligible amount Account Health ARR Eligible Renewal Days Usage Champion Play Justifying signal C-0F6C0F34 51 86,741 49,707 2026-10-03 28 growing false executive touch champion_active=false with only 28 days to renewal; usage is growing, so no usage-revival case C-0B827671 56 72,088 25,365 2026-11-14 70 declining true usage revival usage_trend_3m=declining, champion still active C-0B360C78 57 60,427 35,748 2026-10-28 53 growing true commercial concession usage growing and champion active with 246/327 seats used (75.2%); no product-side signal, eligible amount is 59.2% of ARR (35,748/60,427) — highest leverage ratio among qualifiers C-0B0F1BAB 38 15,391 5,494 2026-09-23 18 flat false executive touch lowest health among qualifiers (38), champion_active=false, 18 days to renewal C-0CA21961 58 31,501 16,829 2026-12-28 114 flat true usage revival only 84/325 seats used (25.8%) with flat usage — adoption gap despite active champion C-0E9C27D1 39 75,093 41,235 2026-09-24 19 flat true executive touch health 39 with renewal in 19 days; usage flat and 134/157 seats used (85.4%) — problem is not adoption C-0CEF69FD 53 79,324 32,621 2026-11-21 77 growing false executive touch champion_active=false; usage growing, so relationship coverage is the gap C-0D3278C7 54 33,815 17,602 2026-11-12 68 declining true usage revival usage_trend_3m=declining plus 126/380 seats used (33.2%) Total eligible: 49,707 + 25,365 + 35,748 + 5,494 + 16,829 + 41,235 + 32,621 + 17,602 = $224,601 Total ARR of these accounts: $454,380. Eligible amount equals 49.4% of that ARR. AT-RISK BUT NOT QUALIFYING — 7 accounts Account Health Eligible Renewal Days Reason for exclusion C-0BC71BDD 55 0 2026-10-27 52 R2 fail: churn_save_eligible_amount=0 C-0BA71F12 52 6,824 2027-04-11 218 R3 fail: renewal 218 days out, beyond 120 C-0F6694C3 43 0 2027-03-21 197 R2 fail (0) and R3 fail (197 days) C-0BE96399 54 0 2026-10-29 54 R2 fail: churn_save_eligible_amount=0 C-0F876796 47 19,958 2027-02-06 154 R3 fail: renewal 154 days out; meets R1 and R2 C-0FCCD2DF 43 0 2027-04-23 230 R2 fail (0) and R3 fail (230 days) C-10A56B0F 54 0 2026-12-12 98 R2 fail: churn_save_eligible_amount=0 The remaining 15 accounts have health scores 62–88, so they fail R1 and were not assessed as at risk, regardless of renewal timing or eligible amount. Data caveat: C-0B360C78 is the only qualifier assigned “commercial concession,” and no field in the dataset records pricing, discount, or contract friction. That play is the residual option given healthy usage and an active champion; it is the least directly evidenced assignment in the table.
Expansion kit — C-0DDFC9A7 Seat coverage - Licensed seats 150 over headcount 400 = 37.5% coverage (150/400). - Unused seats: 400 − 150 = 250. Usage health (two lines) - Active users grew from 88 (Mar 2026) to 126 (Aug 2026): +38 users, +43% over five months, climbing every single month. - At 126 of 150 seats (84% of licensed seats now active), utilization is high — the license will likely feel tight before year-end. Headroom at current per-seat rate - Per-seat rate: $9,000 ARR / 150 seats = $60/seat. - Seat headroom: 250 seats. - ARR headroom: 250 × $60 = $15,000. Who replied / can they buy - Maria S., People Operations Coordinator, replied (2026-09-02). She explicitly stated she is not the purchasing decision-maker — she cannot buy. Right buyer from our contacts - Dana R., VP People (last engaged 2026-05-18). Maria has offered an introduction and says Dana has been asking about usage numbers — warm path in. Reply email (under 150 words) Subject: RE: Growing your team's recognition program Hi Maria, Thank you — glad to hear the recognition feed is busy and the team's loving it. The numbers back you up: monthly active users have climbed from 88 in March to 126 in August, a 43% rise, and you're now using 126 of your 150 licensed seats. An introduction to Dana would be great. Since she's already asking about usage, the simplest next step is a short call where I can share the usage trend and what adding seats would look like — you'd be welcome to join. Would sometime in the next week or two work for her? Happy to send a couple of times that fit your calendars. Thanks again, Cole
## Onboarding Prep — C-0D284E42 (signed up 2026-08-11; call covers day ~24) ### Complete (each backed by a data field) - Slack connected: integration_slack = 2026-08-12 (day 1 after signup). - Allowance set: allowance_set = 2026-08-13. - Admins added: admins_added = 2. - First recognition given: first_recognition_at = 2026-08-15 14:22 (day 4). ### Not complete - HRIS integration: integration_hris is blank. No data field shows it connected. - First redemption: first_redemption_at is blank. No data field shows one. - Admin count context: 2 admins_added is a count only; whether that's the intended full admin team can't be verified from this data. - No field exists for channel/workspace config, kickoff completion, or training — completeness on those is unknown, not confirmed. ### Early engagement signals (from onboarding_usage, active_givers) - Trend is up: day 1 = 3 givers; last 4 days = 15, 15 with a ramp through 7 → 9 → 11 → 13 → 15. Peak = 15 (2026-09-03 and 09-04). - Arithmetic: total giver-days across 25 days = 3+3+4+4+5+4+7+5+7+6+9+8+9+9+9+11+10+10+11+13+11+13+13+15+15 = 213. Average = 213 / 25 = 8.52 givers/day. - Weekly averages: week 1 (08-11 to 08-17) = 30/7 = 4.29; week 2 (08-18 to 08-24) = 53/7 = 7.57; week 3 (08-25 to 08-31) = 75/7 = 10.71; week 4 (09-01 to 09-04, 4 days) = 56/4 = 14.0. Clean week-over-week climb: ~4.3 → ~7.6 → ~10.7 → ~14.0. - Dips are minor and recover next day (08-16: 4→7; 08-18: 7→5→7), so the ramp looks organic, not spiky. - Interpretation: givers are growing steadily, but recognition is happening without a confirmed redemption loop yet — points are being earned but nobody has cashed them in (per the blank first_redemption_at). ### Three things to cover on the call 1. HRIS connection — the only integration still blank. Get it scheduled or an explicit reason it's not planned; it's also the risk of manual user-list drift as the giver base grows. 2. First redemption — walk an employee through redeeming live on the call. Recognition is clearly happening (recognition on day 4, givers up 5x since launch); redemption is the missing half of the loop, and zero redemptions by day ~24 is the main adoption gap in the data. 3. Admin coverage — confirm 2 admins is the intended setup and who owns ongoing config (allowance tuning, user onboarding) once HRIS is connected, since admins_added = 2 with no field showing a broader admin plan. Data limitations: no headcount/seat count, so giver counts can't be converted to adoption percentages; no recognition volume (only first-occurrence timestamps); no redemption-catalog or points-balance data.
90-day renewal risk brief Scope: No reporting start date was supplied. Using September 1–November 29, 2026, inclusive, as the 90-day window immediately after the latest usage month, August 2026. All 20 corrected renewal dates fall within it. Renewal completion status is missing. Date authority: Use Chargebee for all accounts. For the five multi-year accounts, ChurnZero is known to be unreliable; for the remaining 15 annual accounts, both systems agree. Calculations and risk rules: Seat utilization = seats_used ÷ seats × 100. Three-month trend = June → July → August active users; change = (August − June) ÷ June × 100. High risk: usage declines at least 10%, or seat utilization is below 40%. Moderate risk: not High, but seat utilization is below 70%. Low risk: neither condition applies. These are analytical screening rules, not confirmed churn predictions. ARR at risk includes High and Moderate accounts at full ARR, not probability-weighted loss. Renewals C-0B7D2C30 | Dana Mercer | ARR $65,901 | Date used: 2026-09-15, Chargebee DISAGREEMENT: ChurnZero says 2026-09-10; trust Chargebee because this is a 36-month multi-year contract. Seats: 274/476 = 57.6%. Usage: 97 → 94 → 84; (84−97)/97 = −13.4%. HIGH: Usage declined each month and fell 13.4%, alongside 57.6% seat utilization. C-0BCDB8C2 | Cole Ingram | ARR $54,427 | Date used: 2026-09-18, Chargebee DISAGREEMENT: ChurnZero says 2027-09-18; trust Chargebee because this is a 36-month multi-year contract. Seats: 232/424 = 54.7%. Usage: 127 → 118 → 110; (110−127)/127 = −13.4%. HIGH: Usage fell 13.4% with only 54.7% of seats used. C-0D2AB865 | Elena Sinclair | ARR $38,022 | Date used: 2026-09-22, Chargebee DISAGREEMENT: ChurnZero says 2026-09-10; trust Chargebee because this is a 24-month multi-year contract. Seats: 250/407 = 61.4%. Usage: 125 → 117 → 109; (109−125)/125 = −12.8%. HIGH: Usage declined each month, falling 12.8% despite 61.4% seat utilization. C-0BBE3E60 | Dana Mercer | ARR $30,993 | Date used: 2026-09-26, Chargebee DISAGREEMENT: ChurnZero says 2027-09-26; trust Chargebee because this is a 24-month multi-year contract. Seats: 74/114 = 64.9%. Usage: 39 → 35 → 33; (33−39)/39 = −15.4%. HIGH: Usage fell 15.4%, the largest three-month percentage decline in this cohort. C-0F5D2323 | Cole Ingram | ARR $90,647 | Date used: 2026-09-29, Chargebee DISAGREEMENT: ChurnZero says 2026-09-10; trust Chargebee because this is a 24-month multi-year contract. Seats: 111/390 = 28.5%. Usage: 20 → 21 → 18; (18−20)/20 = −10.0%. HIGH: Only 28.5% of seats are used and usage fell 10.0%. C-0EC6999D | Elena Sinclair | ARR $79,419 | Date used: 2026-10-03, Chargebee; both systems agree. Seats: 31/112 = 27.7%. Usage: 17 → 16 → 15; (15−17)/17 = −11.8%. HIGH: Seat utilization is just 27.7% and usage declined every month. C-0B20DB64 | Dana Mercer | ARR $21,770 | Date used: 2026-10-07, Chargebee; both systems agree. Seats: 214/378 = 56.6%. Usage: 294 → 298 → 294; (294−294)/294 = 0.0%. MODERATE: Usage is flat, but 56.6% seat utilization signals unused capacity. C-0BBC4E7A | Cole Ingram | ARR $56,374 | Date used: 2026-10-10, Chargebee; both systems agree. Seats: 228/337 = 67.7%. Usage: 142 → 141 → 139; (139−142)/142 = −2.1%. MODERATE: Seat utilization is below 70% and usage declined slightly each month. C-0FD551AB | Elena Sinclair | ARR $48,815 | Date used: 2026-10-14, Chargebee; both systems agree. Seats: 210/376 = 55.9%. Usage: 123 → 122 → 126; (126−123)/123 = +2.4%. MODERATE: Usage increased 2.4%, but only 55.9% of seats are used. C-0F9F8F13 | Dana Mercer | ARR $46,230 | Date used: 2026-10-18, Chargebee; both systems agree. Seats: 199/352 = 56.5%. Usage: 185 → 185 → 182; (182−185)/185 = −1.6%. MODERATE: Seat utilization is 56.5% with a slight usage decline. C-0BC34584 | Cole Ingram | ARR $16,740 | Date used: 2026-10-22, Chargebee; both systems agree. Seats: 327/494 = 66.2%. Usage: 104 → 104 → 106; (106−104)/104 = +1.9%. MODERATE: Modest usage growth does not eliminate the unused capacity indicated by 66.2% seat utilization. C-0B7A7546 | Elena Sinclair | ARR $35,062 | Date used: 2026-10-25, Chargebee; both systems agree. Seats: 182/205 = 88.8%. Usage: 64 → 65 → 63; (63−64)/64 = −1.6%. LOW: Seat utilization is 88.8% and the three-month usage decline is limited to 1.6%. C-0B369871 | Dana Mercer | ARR $85,128 | Date used: 2026-10-29, Chargebee; both systems agree. Seats: 317/422 = 75.1%. Usage: 326 → 330 → 333; (333−326)/326 = +2.1%. LOW: Seat utilization exceeds 70% and usage increased every month. C-0B144C78 | Cole Ingram | ARR $30,899 | Date used: 2026-11-02, Chargebee; both systems agree. Seats: 169/224 = 75.4%. Usage: 101 → 101 → 106; (106−101)/101 = +5.0%. LOW: Seat utilization is 75.4% and usage increased 5.0%. C-0FC4DBB8 | Elena Sinclair | ARR $94,732 | Date used: 2026-11-05, Chargebee; both systems agree. Seats: 356/464 = 76.7%. Usage: 189 → 191 → 193; (193−189)/189 = +2.1%. LOW: Seat utilization is 76.7% and usage increased each month. C-0D5BBE3A | Dana Mercer | ARR $39,740 | Date used: 2026-11-09, Chargebee; both systems agree. Seats: 85/102 = 83.3%. Usage: 88 → 90 → 91; (91−88)/88 = +3.4%. LOW: Seat utilization is 83.3% and usage increased steadily. C-0FB9D5AF | Cole Ingram | ARR $63,158 | Date used: 2026-11-13, Chargebee; both systems agree. Seats: 144/199 = 72.4%. Usage: 173 → 173 → 176; (176−173)/173 = +1.7%. LOW: Seat utilization exceeds 70% and usage ended above June. C-0B344485 | Elena Sinclair | ARR $64,384 | Date used: 2026-11-16, Chargebee; both systems agree. Seats: 224/287 = 78.0%. Usage: 238 → 240 → 244; (244−238)/238 = +2.5%. LOW: Seat utilization is 78.0% and usage increased each month. C-0CB2C1B4 | Dana Mercer | ARR $40,628 | Date used: 2026-11-20, Chargebee; both systems agree. Seats: 386/473 = 81.6%. Usage: 47 → 48 → 49; (49−47)/47 = +4.3%. LOW under the stated rules: Seat utilization is 81.6% and usage increased, although August’s 49 active users is far below 386 seats_used and needs reconciliation. C-22170CA1 | Cole Ingram | ARR $45,646 | Date used: 2026-11-24, Chargebee; both systems agree. Seats: 251/294 = 85.4%. Usage: 143 → 148 → 146; (146−143)/143 = +2.1%. LOW: Seat utilization is 85.4% and August usage remained above June despite a July-to-August dip. Data limitation: The seats_used snapshot date and metric definition are missing; active_users and seats_used differ substantially, and some active-user counts exceed seats_used. They cannot be treated as equivalent measures. Commercial intent, customer sentiment, and renewal outcomes are also missing. ARR totals High risk, 6 accounts: $65,901 + $54,427 + $38,022 + $30,993 + $90,647 + $79,419 = $359,409. Moderate risk, 5 accounts: $21,770 + $56,374 + $48,815 + $46,230 + $16,740 = $189,929. Low risk, 9 accounts: $35,062 + $85,128 + $30,899 + $94,732 + $39,740 + $63,158 + $64,384 + $40,628 + $45,646 = $499,377. Total ARR renewing: $359,409 + $189,929 + $499,377 = $1,048,715. ARR at risk: $359,409 + $189,929 = $549,338, or $549,338 ÷ $1,048,715 × 100 = 52.4%.
Q3 2026 (Jun 1 – Aug 29) support synthesis: 80 tickets, 24 distinct accounts, 284,800 total ARR in file. Themes ranked by ARR exposure.
1. HRIS provisioning failing for new hires
- Count: 12 tickets (15.0% = 12/80)
- Accounts: 3 — C-0B2213A9 (36,000), C-0DDFC9A7 (48,000), C-0F6C0F34 (30,000)
- ARR affected: 114,000
- Examples: IC-460059, IC-460060
- Pattern, not noise. Recommendation: escalate to engineering as a provisioning-sync defect — three independent accounts report identical symptoms ("skipped new hires," "provisioning log shows no errors") across the full quarter.
2. Redemption / gift-card checkout failures (points deducted, reward never delivered)
- Count: 18 tickets (22.5%)
- Accounts: 7 — C-0B827671, C-14264ABD, C-0B0F1BAB, C-0FCCD2DF, C-0D9CA315, C-0CEF69FD, C-0F876796
- ARR affected: 68,800
- Examples: IC-460025, IC-460024
- Pattern. Recommendation: treat as a fulfillment-pipeline defect with a points-refund SLA; the "errored but points deducted" variant directly erodes trust in the core product loop.
3. Invoice / billing errors — SINGLE-ACCOUNT
- Count: 16 tickets (20.0%)
- Accounts: 1 — C-0E9C27D1 (52,000)
- ARR affected: 52,000
- Examples: IC-460071, IC-460069
- Single-account noise, but the highest-ARR account in the file with an unresolved billing dispute spanning the entire quarter (seat count 150 vs 200 charged, wrong renewal tier). Recommendation: route to billing/CS leadership for a named-account save play this week, not a support queue.
4. Points not credited to balances
- Count: 20 tickets (25.0%)
- Accounts: 9 — C-0BF20542, C-0D0B047C, C-0D284E42, C-0D6CC8E3, C-0BE96399, C-21FEBCBB, C-0DD0626C, C-0D3278C7, C-0B2895EF
- ARR affected: 31,100
- Examples: IC-460001, IC-460004
- Broad pattern, highest volume, lowest per-account ARR (all ≤ 4,500). Includes team-wide weekend posting failures and individual missing-credit cases. Recommendation: audit the points ledger posting job, especially the weekend batch; publish a status page entry when posting lags.
5. Slack integration broken (sync drops, re-auth not sticking, slash-command errors)
- Count: 14 tickets (17.5%)
- Accounts: 4 — C-0BA71F12, C-10A56B0F, C-0B843542, C-8C2E8F00
- ARR affected: 18,900
- Examples: IC-460047, IC-460046
- Pattern. Recommendation: investigate OAuth token persistence — "re-auth does not stick" and "toggle resets itself" point to a token/credential refresh bug, not user error.
Notes: existing tags were ignored (they carry no signal — every theme spans bug/billing/feedback/question/etc.). Arithmetic shown as counts and sums of the arr column per theme; account-level ARR is deduplicated so a multi-ticket account counts once. C-0E9C27D1's 16 tickets are ~inseparable from theme 3 only because every one of its tickets is a billing complaint; no other account reports billing issues, so it does not indicate a systemic billing defect.
Prospect C-82AF3719: Technology / Mid-Market / employee_recognition / NA-West. Ranking of case-study customers (has_case_study=true only), scored by fields matched (industry, size_band, use_case, region — 4 possible): 1. C-64171065 — Technology, Mid-Market, employee_recognition, NA-East — 3/4 matched (industry, size_band, use_case). Miss: region. 2. C-A13C193D — Technology, Mid-Market, retention, NA-West — 3/4 matched (industry, size_band, region). Miss: use_case. 3. C-11C31562 — Manufacturing, Mid-Market, employee_recognition, NA-West — 3/4 matched (size_band, use_case, region). Miss: industry. Ranking logic: all three match 3 of 4 fields. C-64171065 leads because use_case is typically the strongest social-proof driver, and it also matches the prospect's industry. C-A13C193D over C-11C31562 because matching industry + size keeps the story relevant even with a different use case. Next-best alternative, C-CD4829A7 (Technology, Mid-Market, retention, NA-East, case study), matches only 2/4 and was excluded from the top three. Caveat: no existing case-study customer matches all 4 fields exactly — the closest Technology/Mid-Market/employee_recognition/NA-West customer (C-C153868F) has no case study and is therefore excluded per your rule.
Channel performance, Mar–Aug 2026 (the six months covered by both files; September is not in the data) Paid channels (spend from channel_spend.csv; SQMs, SQOs, and pipeline counted from contacts_first_touch.csv) paid_search: spend $36,000 (6 × $6,000). SQMs 40. SQOs 18. Cost per SQM = 36,000 / 40 = $900. Cost per SQO = 36,000 / 18 = $2,000. SQM-to-SQO = 18 / 40 = 45.0%. Pipeline = 18 × $40,000 = $720,000. Pipeline per $ = 720,000 / 36,000 = 20.0. linkedin_ads: spend $24,000 (6 × $4,000). SQMs 25. SQOs 8. Cost per SQM = 24,000 / 25 = $960. Cost per SQO = 24,000 / 8 = $3,000. SQM-to-SQO = 8 / 25 = 32.0%. Pipeline = 8 × $12,000 = $96,000. Pipeline per $ = 96,000 / 24,000 = 4.0. webinars: spend $9,000 (6 × $1,500). SQMs 12. SQOs 5. Cost per SQM = 9,000 / 12 = $750. Cost per SQO = 9,000 / 5 = $1,800. SQM-to-SQO = 5 / 12 = 41.7%. Pipeline = 5 × $12,000 = $60,000. Pipeline per $ = 60,000 / 9,000 = 6.67. paid_social: spend $18,000 (6 × $3,000). SQMs 0. Cost per SQM, cost per SQO, and SQM-to-SQO are undefined. No pipeline. The file contains no paid_social contacts. Total paid spend: $87,000. Paid_search 41.4%, linkedin_ads 27.6%, paid_social 20.7%, webinars 10.3%. Organic (no spend in the file) organic_search: 30 SQMs, 10 SQOs, SQO rate = 10 / 30 = 33.3%. Pipeline = 10 × $9,000 = $90,000. Cost metrics are not computable because no organic spend is provided. Reference only: referral has 15 SQMs, 6 SQOs (40.0%), and $48,000 pipeline, with no spend in the file. Flagged rows (SQO date before SQM date) CT-000044 (linkedin_ads): SQM 2026-07-23, SQO 2026-07-18. Pipeline $12,000 is included in the linkedin totals. CT-000041 (linkedin_ads): SQM 2026-06-14, SQO 2026-06-09. Pipeline $12,000 is included in the linkedin totals. Excluding both would move linkedin to 6 SQOs, $3,999 per SQO... specifically $24,000 / 6 = $4,000 per SQO, and pipeline to $72,000 (pipeline per $ = 3.0). Both are kept as recorded because the data does not say which date is wrong. Other data notes - Every contact carries one fixed pipeline value per channel ($40,000 paid_search, $12,000 linkedin/webinars, $9,000 organic, $8,000 referral). This looks like a default, not a deal-level amount. Pipeline figures are only as good as that assumption. - The file has 122 unique contact keys and no duplicates. - No deal IDs are provided, so pipeline cannot be tied to CRM deals. Reallocation recommendation Shift budget away from linkedin_ads and toward paid_search, and verify paid_social before funding it further. - linkedin_ads has the highest cost per SQO ($3,000) and the lowest pipeline per $ (4.0) among paid channels with data. - paid_search has the lowest cost per SQO among the large-volume channels ($2,000) and the highest pipeline per $ (20.0). - A reasonable test is moving $1,000–2,000 per month from linkedin to paid_search and tracking SQO rate and cost per SQO monthly. The file has no data on paid_search saturation, so diminishing returns are unknown. - Keep webinars as is. It has the lowest cost per SQO ($1,800), but five SQOs is too few to scale on. - Do not fund paid_social further until its contacts show up in the data. $18,000 in spend with zero SQMs is either a tracking gap or a channel that is not producing. Confidence: low to moderate. - paid_search (40 SQMs, 18 SQOs) is the most reliable channel here, but it is still one six-month sample. - linkedin_ads (25 SQMs, 8 SQOs) and webinars (12 SQMs, 5 SQOs) are small samples. A difference of one or two SQOs changes their cost per SQO substantially. - Organic and referral have no spend, so they cannot be compared on cost. - Two linkedin rows have impossible date ordering, which affects that channel's numbers.
RIVALLY BATTLECARD (updated 2026-10-19) Source data: snippets S01–S25 (2025-11-04 to 2026-09-03), deals_with_competitor.csv (2025-09 to 2026-08). No snippets after 2026-09-03 were provided, so Sept–Oct 2026 is a gap. 1. POSITIONING Points-based recognition with an engaging feed (S02, S16), aimed at mid-market and growing into EU enterprise with multi-language support and EU data residency (S04, S12, S15). 2. PRICING Current list: $7/user/month, annual billing required, Recognition Starter tier (S17, 2026-08-12). Conflicts, newest wins: - S03 (2026-01-20) and S08 (2026-04-01) showed $5/user/month. Superseded by S17. - S13 (2026-06-02): a 500-seat prospect was quoted $6.50/user/month, annual term. This is a deal quote, not list, and predates S17. Treat as a discounted quote. - S18 (2026-08-14), prospect-reported: $7 list with 15% off for a 3-year term. Derived effective rate: $7 × 0.85 = $5.95/user/month. Prospect-reported, not verified on Rivally's pricing page. - Pulse add-on is priced separately, not bundled (S23, 2026-09-01). No Pulse price is in the data. - Missing: Bonusly's own price for comparison. 3. WHERE RIVALLY WINS - Engaging recognition feed (S02, S16). - Fast setup, under a week, with Slack working out of the box (S04). - EU data residency, generally available 2026-07-01 (S05, S15). - EU enterprise strength with multi-language support for distributed teams (S12). Note: EMEA rewards catalog is thinner than US (S14). - Support response under 4 hours (S22). - Switching cost: migrating off Rivally is hard because analytics exports are CSV-only (S20). - Teams app v2 in public preview (S19). Bonusly's Teams status is not in the data. - Engagement survey add-on Pulse, out of beta (S06, S23). 4. WHERE WE WIN - Analytics depth: an 800-seat prospect picked Bonusly over Rivally citing analytics depth (S25). Rivally's analytics are described as limited (S02), basic (S07), and CSV-only on export (S20). - Admin gaps at Rivally: no SCIM provisioning, so manual user management (S10); no bulk recognition editing (S24); admin tooling lags peers (S16). - Missing: whether Bonusly has SCIM, bulk editing, EU residency, Teams app, or EMEA catalog. These are needed to confirm the parity side of each point. 5. OBJECTIONS AND RESPONSES - "Rivally is cheaper." Rivally's list is $7 (S17), and its 3-year discount brings effective price to about $5.95 (S18 arithmetic). Respond with a 3-year total-cost comparison against Bonusly's pricing. Bonusly pricing: missing. - "Rivally has EU data residency." True as of 2026-07-01 (S15). Respond with Bonusly's residency position. Missing. - "Rivally's feed is engaging." Concede (S16). Respond with analytics depth (S25) and export limits (S20). - "Rivally has a Teams app." Preview only as of S19. Respond with Bonusly's Teams status. Missing. - "Rivally's Pulse survey is included." Not bundled; priced as add-on (S23). - "Rivally support is fast." Concede the sourced claim (S22). Bonusly support SLA: missing. - "Rivally has Slack and quick setup." Concede (S04). 6. RECENT CHANGES (dated) - 2025-11-04: $40M Series C led by Northgate Ventures (S01). - 2026-03-05: Pulse engagement add-on launched (S06). - 2026-05-09: Ex-Workday VP EMEA hired for European expansion (S11). - 2026-07-01: Dublin office opened; EU data residency GA (S15). - 2026-08-12: List price raised from $5 to $7 (S17). - 2026-08-20: Teams app v2 in public preview (S19). - 2026-09-01: Pulse exited beta, priced as add-on (S23). - Rep opinions (S09 on UI, S21 on "aggressive discounting") are excluded as facts. 7. OUR 12-MONTH WIN/LOSS VS RIVALLY (2025-09 to 2026-08) - Total: 13 wins, 7 losses, 20 deals. Win rate: 13 ÷ 20 = 65%. - Sep 2025–Feb 2026: 9 wins, 3 losses, 12 deals. Win rate 9 ÷ 12 = 75%. - Mar–Aug 2026: 4 wins, 4 losses, 8 deals. Win rate 4 ÷ 8 = 50%. - Wins: Deal-A9FD43, Deal-7AA785, Deal-44C524, Deal-0D0CD6, Deal-D5B790, Deal-5C636E, Deal-67BE14, Deal-1B6969, Deal-F03E7B, Deal-072E31, Deal-F65C8F, Deal-E46EAB, Deal-1D2392. - Losses: Deal-7767F5, Deal-5645A5, Deal-C6FFAA, Deal-D263E0, Deal-935746, Deal-9066A6, Deal-72A02F. - Caveat: the data has no loss reasons per deal, and the S25 deal is not linked to any alias. The H2 decline is a small-sample trend; the data does not explain it. 8. OLD CARD: RE-SOURCING - "Points-based recognition for mid-market": supported (S02, S04). Kept. - "Starts at $5/user/month (2026-01)": superseded by S17. Replaced. - "Lacks a Slack integration": contradicted by S04. Removed. - "Acquired by WorkHuman in 2025": UNVERIFIED. No snippet supports it. Remove unless sourced. - "Strong in EU enterprise with multi-language support": supported (S12), with EMEA catalog caveat (S14). Kept. 9. DATA GAPS TO CLOSE - Bonusly pricing and packaging. - Bonusly SCIM, bulk editing, EU residency, Teams app, EMEA catalog, support SLA. - Snippets from 2026-09-04 onward. - Loss reasons for the 7 losses.
Per-sequence (sums across steps: sent 1386/875/1785/1163): | Sequence | Sent | Open | Reply | Meeting | Weakest step | |---|---|---|---|---|---| | New Logo Nurture | 1,386 | 35.4% (490/1386) | 6.5% (90/1386) | 1.9% (27) | Step 3: 4.2% reply (18/428) | | Expansion Nurture | 875 | 64.6% (565/875) | 6.7% (59/875) | 1.4% (12) | Step 3: 4.4% (12/275) — but Step 2 numbers are corrupt (see below) | | Cold Outbound - HR Leaders | 1,785 | 30.5% (545/1785) | 0.45% (8/1785) | 0% (0) | Every step fails; Step 3 worst (1/590 = 0.17%) | | Cold Outbound - People Ops | 1,163 | 29.2% (340/1163) | 2.5% (29/1163) | 0.5% (6) | Step 3: 1.6% (6/377) | Tracking errors - Expansion Nurture Step 2: opened 340 > sent 300 — 40 impossible opens (113% open rate). Reply/meeting numbers for that step are unreliable until fixed. No other row has opened > sent. Audience overlap - 23 contacts are in two sequences. HR Leaders ↔ People Ops: 21 contacts (CT-001217, CT-001159, CT-001153, CT-001227, CT-000884, CT-000849, CT-001285, CT-001101, CT-001255, CT-001105, CT-001097, CT-001258, CT-000908, CT-001130, CT-001103, CT-001033, CT-001345, CT-001311, CT-000890, CT-001277, CT-001236) — these two "cold" sequences are heavily the same audience. - Expansion Nurture ↔ New Logo Nurture: 2 contacts (CT-000301, CT-000624). Failure modes (reply < 2%) - HR Leaders (0.45%): structural, not copy — 30.5% opens with 0.8%→0.2% declining replies and zero meetings across 1,785 sends means the offer/ICP mismatch is total. Also inflated by the 21 shared contacts being hit twice by two cold sequences. - People Ops Step 3 (1.6%): standard late-sequence fatigue — replies decay each step; needs a fresh angle, not another nudge. One change per weak sequence - HR Leaders: pause and rebuild — dedupe against People Ops and requalify the list before resending (zero meetings proves nothing to optimize here). - People Ops: rewrite Step 3 as a new value angle (case study or question) instead of a follow-up. - Expansion Nurture: fix the Step 2 tracking error first, then judge. - New Logo Nurture: only weak-ish; rewrite Step 3 like People Ops. Fix first: Cold Outbound - HR Leaders — largest send volume (1,785), lowest yield (8 replies, 0 meetings), and the worst data-quality tailwind (shared audience with People Ops).
# Weekly Marketing Goals Update — Q3-2026 (day 66 of 92, 71.7% elapsed) | Metric | QTD Actual | Target | Delta to Target | Pace | |---|---|---|---|---| | SQMs | 230 | 300 | -70 (76.7% attained) | Ahead | | SQOs | 84 | 120 | -36 (70.0% attained) | Behind (slight) | | DS2s | 40 | 75 | -35 (53.3% attained) | Behind | | Closed-lost MIA rate | 5/25 = 20.0% | ≤10% | +10 pts worse | Behind | | Same-quarter closes | 10 | 20 | -10 (50.0% attained) | Behind | | Active pipeline coverage | $3.0M | $4.0M | -$1.0M (75.0% attained) | Slightly ahead | Arithmetic and pace basis (proportional expected QTD = target × 66/92 = target × 0.7174): - SQMs: expected 300 × 0.7174 = 215.2; actual 230 → +14.8 vs pace. Ahead. - SQOs: expected 120 × 0.7174 = 86.1; actual 84 → -2.1 vs pace. Marginally behind. - DS2s: expected 75 × 0.7174 = 53.8; actual 40 → -13.8 vs pace. Clearly behind; largest funnel gap. - MIA rate: 5 MIA ÷ 25 total closed-lost = 20.0% vs 10% target → 2× the allowed rate. Behind (lower is better). - Same-quarter closes: expected 20 × 0.7174 = 14.3; actual 10 → -4.3 vs pace. Behind. - Pipeline: $3.0M ÷ $4.0M = 75.0% attained vs 71.7% pace → slightly ahead; remaining $1.0M over 26 days needs ~$38.5K/day, vs the QTD run rate of $3.0M ÷ 66 = $45.5K/day. Coverage target is reachable at current accrual rate, but with no cushion if accrual slows. **What moved this week:** The data is QTD-cumulative only, so week-over-week movement cannot be isolated — that's a data gap, not a reading. Within the quarter, the shape is clear: top-of-funnel conversion is holding (SQMs slightly ahead of pace, SQOs essentially at pace), but downstream is thin — DS2s are the biggest shortfall (-13.8 vs pace), which likely feeds the same-quarter close shortfall (10 vs 14.3 expected). Deal-quality signal is also weak: 1 in 5 closed-lost deals went MIA (20% vs the 10% ceiling), consistent with mid-funnel deals engaging less before dying. Pipeline coverage is the one bright spot at 75% of target with 26 days left, but closing both the DS2 gap and the close-rate gap in the remaining third of the quarter would require acceleration, not just maintenance. Note: "active_pipeline" units are assumed USD as given; targets file does not state currency.
Q3 forecast is 115,977 (44,729 COMMIT + 35% × 203,565 BEST_CASE = 71,248), but don't sign off on it yet. None of the 7 COMMIT deals (44,729) has a documented why-buy, and 32 of 86 deals carry October close dates, which suggests dates are being pushed. Have reps re-qualify COMMIT and fill owners (blank on 85 of 86) first.
Subject: Pricing from our July 28 demo Hi [First name], Following up on the pricing recap I sent August 5 after our July 28 demo. Your team responded strongly to the automated milestone awards and the points catalog, so I want to make sure the 150-seat pricing answers your questions. Would you be open to a 20-minute call this week to walk through it? Best, Alex Franklin Word count: 58. Data gaps: the file has no recipient name, so [First name] is a placeholder. There are no inbound replies in the engagement history, so the tone is matched to our outbound emails rather than a customer reply.
Marketing delivered 46 SQMs this week against a goal of 52 (a gap of 6 SQMs, or 88.5% to target: 46 / 52 = 88.46%). The webinar channel served as the primary contributor, supplying 18 of the 46 total SQMs (39.1%: 18 / 46 = 39.13%). Meanwhile, paid search efficiency remained stable, holding at a cost per SQM of $150. Sales generated $310,000 in new pipeline, converting 14 SQOs and scheduling 9 DS2 meetings. Execution at the bottom of the funnel remained active, with 3 same-quarter closes completed during the week. Additional pipeline conversion details by stage or territory are not provided in the source extract. Customer Success defended 2 saved renewals and saw team NPS shift to 61. Account health monitoring remains focused heading into next week, with 3 open red-flag accounts currently requiring active attention and intervention. Retention dollar amounts and account breakdowns were not reported in this week's data. PLG brought in 412 new signups, achieving an activation rate of 31% (representing approximately 128 activated users: 412 * 0.31 = 127.72). In addition, 38 companies crossed the product aha moment by reaching 10 recognition gives. Self-serve conversion data to paid plans is missing from the provided extract.
Partner Digest — 2026-08-24 to 2026-09-04 Active partners - Apex Rewards Co — Two sourced opps this period, both in stage DS1 and logged with UTM Source = Partner; co-webinar locked for 09-15. Deal data: Deal-DDAAF2 ($180,000) and Deal-2CF33E ($95,000). Partner-sourced total $275,000 (180,000 + 95,000). - HRCloud Partners — One sourced opp this period; integration referral passed security review and moved to DS2. Deal data: Deal-F1CDA5 ($140,000). - CultureBridge — Lunch-and-learn produced two sourced opps, both early stage. Deal data: Deal-096E1D ($60,000) and Deal-067213 ($75,000). Partner-sourced total $135,000 (60,000 + 75,000). - WorkWell Group — No sourced deals this period. Wants to restart the joint playbook in Q4; planning call booked for 09-09. Quiet partners - Recogniq — No activity or sourced deals reported this period. - KudosWave — No activity or sourced deals reported this period. - PeopleFirst Advisors — No activity or sourced deals reported this period. - TotalPerk — No activity or sourced deals reported this period. Partner-sourced pipeline - Count: 5 deals (Deal-DDAAF2, Deal-2CF33E, Deal-F1CDA5, Deal-096E1D, Deal-067213), all with utm_source = Partner, matching the Slack-reported opp counts (2 Apex + 1 HRCloud + 2 CultureBridge). - Amount: $550,000 (180,000 + 95,000 + 140,000 + 60,000 + 75,000). Reconciliation notes: Slack and deal data agree on all counts. Slack says both Apex opps are in DS1 and the HRCloud opp is in DS2; the deal file records stages nowhere, so stage labels come from Slack only and are stated as such.
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. The report is available to prospects under NDA, so we can provide a copy once the NDA is in place. [P2] Q4: Customer data is retained for the duration of the contract plus 90 days. After that period it is deleted from production systems. [P3] Q5: The current subprocessor list is published at trust.bonusly.com. Customers receive 30 days notice before a new subprocessor is added. [P4] Q6: Yes. SAML 2.0 single sign-on is available on the Enterprise plan. [P5] Q7: Production databases are backed up daily. Backups are encrypted and retained for 35 days. [P6] Q8: Unanswerable from the provided excerpts. No excerpt mentions ISO 27001. To answer, we need the current ISO 27001 certificate, or a written statement from Bonusly's compliance function confirming certification status and scope. Q9: Unanswerable from the provided excerpts. No excerpt states an uptime SLA. To answer, we need the executed customer agreement or SLA addendum that sets the contractual uptime percentage. Q10: Unanswerable from the provided excerpts. No excerpt mentions HIPAA or a Business Associate Agreement. To answer, we need a legal/compliance determination on BAA availability, which would be confirmed by the company's standard BAA template or a written position from Bonusly legal.
Scope: 14 manifest rows and 14 files provided. Descriptions and body_lines are taken from the manifest; I did not re-measure them. (1) OVERLAPPING ALWAYS-TRIGGER PHRASES - email-drafter vs comms-drafter. CRITICAL. MERGE. Identical trigger phrases in both descriptions: "write me an email", "draft a follow-up", "help me reply", "what should I say", "bump email", "contract nudge". Both draft external copy. Survivor: comms-drafter, which has the wider scope. Fold email-drafter's Gmail signature retrieval step into it. - pipeline-intelligence-report vs weekly-pipeline-report. WARNING. REVIEW. "pipeline update" (PIR) is a substring of "run the pipeline update" (WPR). "what's the pipeline look like" (PIR) and "what does pipeline look like" (WPR) are near-duplicates. Add a routing rule that assigns each phrase to one skill. (2) CIRCULAR DELEGATION CHAINS - deal-strategy-coach ↔ email-drafter. WARNING. UPDATE_BODY (deal-strategy-coach). deal-strategy-coach routes manager emails to email-drafter. email-drafter routes deal strategy back to deal-strategy-coach. Resolving finding (1) removes the email-drafter leg. Keep deal-strategy-coach's draft handoff pointed at comms-drafter only. - pipeline-intelligence-report ↔ closed-lost-analysis. WARNING. UPDATE_BODY (closed-lost-analysis). PIR Phase 2b delegates to closed-lost-analysis Mode 4. Mode 4's trigger text says it is "called from pipeline-intelligence-report," which is a callback. Keep PIR → CLA and remove the callback wording. (3) DANGLING DELEGATION TARGETS (not in the provided set) Caveat: these names appear in the runtime skill list, so they may resolve outside this set. Verify before acting. - bonusly-brand. CRITICAL. REVIEW. Referenced as a mandatory "apply first" step in comms-drafter and email-drafter, and in signalforge-claim-compressor. - prospect-research-multithreading. WARNING. REVIEW. Referenced by comms-drafter, email-drafter, and deal-strategy-coach. - skill-orchestrator. WARNING. REVIEW. Referenced by analysis-validator §11 and signalforge-feedback. - Eight specialists in analysis-validator §12.4. WARNING. REVIEW. bonusly-data-questions, bonusly-product-questions, bonusly-business-reporting-questions, bonusly-rewards-questions, bonusly-ppp-questions, bonusly-feature-flag-questions, bonusly-deal-desk-questions, bonusly-datadog-questions. - signalforge-reports (/mnt/skills/organization/signalforge-reports). INFO. REVIEW. Referenced by pipeline-intelligence-report and weekly-pipeline-report. - analysis-validator §11 also names CUSTOMER_DATA_REFERENCE, HUBSPOT_CONNECTOR_REFERENCE, and SIGNALFORGE_PRODUCT_INSIGHT_SKILL. None are files in this set. INFO. REVIEW. (4) VERSION CONFLICTS - analysis-validator, internal. WARNING. UPDATE_BODY (§7 trail template). The header, the changelog, and PIR's footer all say v3.6. The §7 template says "analysis-validator v3.2". Survivor: v3.6. - model-selection registry is stale. WARNING. UPDATE_BODY. last_checked is 2026-05-19. Days to 2026-10-19: 12 (May 19–31) + 30 + 31 + 31 + 30 + 19 = 153. The skill's own rule requires a self-update after 14 days. I did not check Anthropic's docs here. - Not a version conflict, but related: transcript source policy differs. INFO. REVIEW. analysis-validator G1-D allows only GONG_TRANSCRIPTS_AGG with no fallback. deal-strategy-coach uses HubSpot → Granola → Gong. (5) MANIFEST DESCRIPTIONS OVER 1,024 CHARACTERS: 0 of 14. Largest: pipeline-intelligence-report and signalforge-claim-compressor at 1,006 (18 under the limit), then partner-digest at 1,004. (6) HARDCODED PAGE IDs, DATES, OR PERSON NAMES - analysis-validator. WARNING. UPDATE_BODY. Dates: Apr 26 2026, May 4 2026, May 9 2026, Mar 28 2023, "May 2026". Names: Manish, Amani, and the §12.3 roster (Alaina Loori, Shealagh Coughlin, Ben Castelli, Amani Phipps, John Thomas, Yasmin Wahid, plus the AEs and CSMs listed there). Owner IDs and stage IDs are hardcoded. - closed-lost-analysis. INFO. UPDATE_BODY. Dates: "May 2026" in several places. No person names or page IDs. Customer names appear as examples only (Softheon, MinIO, Estee Lauder, and others). - deal-strategy-coach. WARNING. UPDATE_BODY. Page ID 2257879045 in the AE Excellence Playbook URL. Name: Farid (.edu routing). Dates: "April 2026", "2026". - partner-digest. WARNING. UPDATE_BODY. Confluence IDs: 2286616609 (folder), 2286321666, 2265382925, 2236940297, 2237825028, 2239365136, 2238283777, space 1958248479, cloud ID. Slack user U03QLMBL7AR. Names: Amani Phipps, Kelli, Jen Lee, Hani, Bryce, Sara. Dates: May 16, May 17, and May 19 2026. - pipeline-intelligence-report. WARNING. UPDATE_BODY. Names: Bryce Harmon, Dana Mercer, Cole Ingram, Alex Franklin, Gavin Porter, and Alaina. Owner IDs, stage IDs, org ID 1973303. Dates: "March 2023", "May 2026". - sales-forecast. WARNING. UPDATE_BODY. Confluence IDs: space 2232811524, parent 2232582148, cloud ID. Names: Alaina, Elena (changelog). Dates: April 27 2026, and the July 9 2026 example title. - stale-pipeline-report. WARNING. UPDATE_BODY. Slack channel C0561C1JCPJ. Owner ID 55483190 (Bonusly Support). Org ID 1973303. Name: Alaina. Dates: 2026-06-10, and the 5/7, 5/15, 5/19 examples. - weekly-pipeline-report. WARNING. UPDATE_BODY. Name: Ben Lavin (also "Ben" throughout). Spreadsheet IDs 1CLZeOsElVDF_LF0ZG_t2nfwvhnZ6bpwqM_nX3WEYzcw and 1ENuaEcCuLjdKhMvp8FK3Ys1ek5Aw9ZuOZhsHJJFoB_k. Hardcoded Q1 figures: $365,152, $475,000, $2,490,532, $3,288,000. Dates: April 1 – June 30 2026, Q1 2026. - signalforge-feedback. INFO. UPDATE_BODY. Confluence IDs: 2295136266 (Feedback Log), 2234417154 (parent), 2247295002 (Build Log), space 2232811524. Name: Gavin Porter (example title). No dates. - signalforge-claim-compressor. INFO. UPDATE_BODY. Customer names as examples only (Felix Construction, Panopto, Schneider Downs). Changelog date 2026-05-09. - model-selection. INFO. UPDATE_BODY. Dates: 2026-05-19, April 14 2026 (Opus 4.6 deprecation), knowledge-cutoff dates. No names or page IDs. - comms-drafter and email-drafter: none found. - next-to-close: none of the three types. Stage IDs and org ID 1973303 are hardcoded but are outside this check. (7) MANIFEST DRIFT - Files with no manifest row: 0 of 14. - Manifest rows with no file: 0 of 14. - declared_name matches the filename for all 14. - Not verified: description_chars and body_lines against the actual files. If you want those checked, I can count them.
INCIDENT RUNBOOK: #incident-2026-08-29-reward-queue (resolved) Source: incident_thread.md, messages M01 to M10. Times are UTC. Step 1. Detect and take IC (M01, 14:02:10Z) Who: Bryce Harmon Action: Acknowledged PagerDuty alert for reward-worker queue depth > 10k. Took IC. State change: None. Verification: None recorded. Step 2. Measure queue depth (M02, 14:04:33Z) Who: Farid Osman Command: bundle exec rake sidekiq:queue_depth Result: 48,213 pending jobs. Normal is under 500 (per thread). State change: None (read-only). Step 3. Inspect dead set (M03, 14:06:02Z) Who: Farid Osman Command: NOT STATED IN THREAD. Needs confirmation. Result: 112 dead jobs, all Redis::TimeoutError from around 13:58. State change: None reported. Step 4. Pause enqueue (M04, 14:08:45Z) Who: Farid Osman Command: bin/rails runner 'FeatureFlag.disable(:auto_recognition_enqueue)' Verification: NOT RECORDED in M04. Queue trend is first reported in M07. Needs confirmation of an explicit check. Rollback: bin/rails runner 'FeatureFlag.enable(:auto_recognition_enqueue)' (stated in M04) Step 5. Clear dead set (M05, 14:15:20Z) Who: Elena Sinclair Action: "cleared out the dead set." The thread gives no command, no count before or after, and no verification. NEEDS CONFIRMATION: exact command or console action, the number of jobs removed (112 per M03 is the only count in the thread), and whether the step was coordinated with Farid. The thread does not say when this was done relative to Step 4. State change: Yes (deletion of dead jobs). Rollback: NOT STATED IN THREAD. Needs confirmation of whether deleted jobs can be recovered. Step 6. Scale workers up (M06, 14:21:07Z) Who: Bryce Harmon Command: kubectl scale deployment/reward-worker --replicas=6 (was 3, per M06) Verification: Queue depth down to 9,400 and falling about 1,200/min at 14:33:41Z (M07, Farid Osman). Rollback: kubectl scale deployment/reward-worker --replicas=3 (stated in M06) Step 7. Confirm queue drain (M07, 14:33:41Z) Who: Farid Osman Action: Observed queue depth. Read-only. Result: 9,400 and falling at about 1,200 per minute. Note: The thread does not say which command produced this number. Step 8. Confirm queue at zero and error rate at baseline (M08, 14:47:55Z) Who: Cole Ingram Command: bundle exec rake sidekiq:queue_depth (returns 0). Datadog error rate checked. Result: Queue depth 0. Error rate back to baseline. State change: None (read-only). Note: Datadog check method and dashboard are not specified in the thread. Step 9. Re-enable enqueue (M09, 14:49:10Z) Who: Bryce Harmon Command: bin/rails runner 'FeatureFlag.enable(:auto_recognition_enqueue)' Verification: 40 new jobs processed cleanly in the next 3 minutes (stated in M09). State change: Yes (feature flag). Rollback: NOT STATED IN THREAD as a rollback for this step. The inverse of Step 4 would be bin/rails runner 'FeatureFlag.disable(:auto_recognition_enqueue)'. NEEDS CONFIRMATION before use. Step 10. Scale workers back down (M10, 14:55:00Z) Who: Bryce Harmon Command: kubectl scale deployment/reward-worker --replicas=3 Verification: "Queue stable at 0. Incident resolved." (M10). The thread does not show the command that confirmed this. State change: Yes (replica count). Rollback: NOT STATED IN THREAD. The inverse would be kubectl scale deployment/reward-worker --replicas=6, but this is not in the thread. NEEDS CONFIRMATION. Open items needing confirmation: - Step 3: command used to inspect the dead set. - Step 4: verification of the enqueue pause. - Step 5: command, count removed, timing, coordination, and rollback for clearing the dead set. This is the only step with an unrecorded irreversible state change. - Step 9 and Step 10: rollback commands not stated. - Step 10: verification command not stated.
First error 2026-09-03T14:01:12Z — reward-service: “Redis::TimeoutError: Connection to Redis at redis-primary:6379 timed out after 5s”. Cascade in timestamp order (all UTC, 2026-09-03) 1. 14:01:20, 14:01:30, 14:01:40 — reward-service reports retries exhausted for RewardGiveJob. 2. 14:01:40 — sidekiq reports RewardGiveJob failed with Redis::TimeoutError; retrying in 60s. 3. 14:01:46 — earliest failure in sidekiq_jobs.csv: J-00005, RewardGiveJob. Additional RewardGiveJob failures follow. 4. 14:02:28 — sidekiq logs another RewardGiveJob failure and retry. 5. 14:02:30 — sidekiq warns that queue reward depth is above 10,000. 6. 14:02:36 — RecognitionDigestJob also fails with Redis::TimeoutError (J-00013). 7. 14:03:05 — api-gateway reports a 502 upstream timeout calling reward-service /gives. 8. 14:03:30 — web-app reports Give form submission failed because of an upstream 502 from api-gateway. 9. Through 14:06:52 — job failures/retries, gateway timeouts, and form failures continue in the slice. 10. 14:22:10 — reward-service reports Redis connection restored and job processing resuming. 11. 14:24:45 — sidekiq reports queue reward depth below 500. Services and jobs The first observed failure is in reward-service; sidekiq processes the affected jobs. api-gateway and web-app subsequently report upstream failures. The job file contains 12 RewardGiveJob failures + 4 RecognitionDigestJob failures = 16 recorded failed jobs, all with Redis::TimeoutError. Datadog query to confirm the first error Set the UTC time window to 2026-09-03 14:00:00–14:02:00, sort oldest first, and search: service:reward-service status:error "Redis::TimeoutError" "redis-primary:6379" "timed out after 5s" What the logs do not show - Why Redis timed out, or whether Redis itself, networking, or another dependency caused it. - Request/trace IDs linking the job failures, gateway errors, and form failures; the sequence is observed, not proof of causation. - Exact outage onset or continuous unavailability. First error to connection-restored message is 14:22:10 − 14:01:12 = 20m 58s, not a proven outage duration. - Successful completion of every failed job, a fully drained queue, restored form submissions, or the number of affected users or lost/duplicate gives. - Any PostgreSQL error; only successful checkpoint messages appear.
**Flags with code references (6)** 1. recognition_streaks_v2 — on; segment:beta_companies; 42 companies. Controls StreakTracker.record(give) in recognition.rb when enabled. 2. points_budget_guardrails — on; all_companies; 220 companies. Controls BudgetService.enforce! in budget_service.rb. 3. slack_dm_nudges — on; segment:region_na; 87 companies. Gates SlackDm.send_nudge in nudge_job.rb. 4. redeem_flow_redesign — off; targeted_list; 12 companies. Switches redeem_controller between RedeemV2Component and RedeemV1Component. 5. analytics_dashboard_v3 — on; segment:tier_three; 65 companies. Sets @dashboard = AnalyticsV3 in analytics_controller.rb. 6. ms_teams_app_v2 — off; targeted_list; 9 companies. Controls TeamsAppV2.install in teams_installer.rb. **Flags with no code reference (3)** 7. legacy_give_modal — off; segment:legacy_plan; 14 companies. No usage found in the code excerpt. 8. survey_boosters_q3 — on; segment:legacy_plan; 7 companies. No usage found in the code excerpt. 9. paused_offboard_cleanup — off; no targeting rules; 0 companies. No usage found in the code excerpt. **Notes** - All 9 export rows appear above; the code excerpt references exactly the 6 flags in section 1. legacy_give_modal, survey_boosters_q3, and paused_offboard_cleanup have state and targets in the export but no code excerpt usage. - Both survey_boosters_q3 (on) and legacy_give_modal (off) target segment:legacy_plan. - paused_offboard_cleanup is fully off with no rules and 0 companies — no rollout. - On flags with positive counts: 220 (guardrails) + 87 (nudges) + 65 (analytics v3) + 42 (streaks) + 7 (survey boosters) = 421 company-flag enablements. The export gives per-flag counts only; overlapping membership between segments cannot be determined from this data, so 421 is a sum of counts, not a count of distinct companies.
- NDA-1 — GREEN (standard approval): “Term: two (2) years from the Effective Date; obligations survive for three (3) years after termination.” The term and Delaware governing law are stated, and the agreement includes standard confidentiality carve-outs. - NDA-2 — YELLOW (counsel review): “neither party shall solicit for employment or hire any employee of the other party with whom it came into contact under this Agreement.” This is an embedded non-solicit lasting 18 months after the three-year term; review the restriction before approval. - NDA-3 — RED (full legal review): “Recipient shall not, directly or indirectly, engage in or provide services to any business that competes with Discloser's business.” The three-year non-compete, one-way confidentiality with no stated carve-outs, and exclusive Irish jurisdiction warrant full legal review.