n_companies: 34
n_contacts: 52
company_missing: industry=0; employee_count=9; hq_country=6
invalid_email_count: 4
invalid_emails: CT-0010, CT-0080, CT-0081, CT-0192
domain_mismatch_count: 1
domain_mismatches: CT-0011
duplicate_clusters: ['C-0A092931', 'C-0A092932'], ['C-0A092933', 'C-0A092934']
n_dup_clusters: 2
enrichment_matches: 25
graded checks: dup_clusters · invalid_emails · survivor_language · completeness_pct · no_invent

Model's actual answer

show the model's full answer

CRM audit

Deals
- No deals extract was provided.
- Cannot compute completeness for owner, stage, amount, close date, or why-buys.
- Cannot rank fixes by pipeline amount at stake without deal amounts and deal-to-company/contact linkage.

Companies (34 rows)
- industry: 34/34 = 100.00% complete; missing 0/34 = 0.00%
- employee_count: 25/34 = 73.53% complete; missing 9/34 = 26.47%
- hq_country: 28/34 = 82.35% complete; missing 6/34 = 17.65%

Missing company fields
- employee_count missing (9): C-EC3025, C-96039F, C-44EA29, C-D04904, C-B23205, C-60C75F, C-7BBDFA, C-50D386, C-93C8BF
- hq_country missing (6): C-2D1F1B, C-D73B89, C-44EA29, C-D04904, C-2C60E5, C-EE9FFB

Contacts (52 rows)
- email: 52/52 = 100.00% populated; invalid emails 4/52 = 7.69%
- title: 39/52 = 75.00% complete; missing 13/52 = 25.00%
- persona: 37/52 = 71.15% complete; missing 15/52 = 28.85%

Missing contact fields
- title missing (13): CT-0000, CT-0022, CT-0072, CT-0080, CT-0081, CT-0092, CT-0120, CT-0121, CT-0122, CT-0132, CT-0141, CT-0162, CT-0170
- persona missing (15): CT-0000, CT-0022, CT-0041, CT-0060, CT-0070, CT-0081, CT-0082, CT-0092, CT-0110, CT-0132, CT-0162, CT-0171, CT-0172, CT-0180, CT-0181

Duplicate company clusters
Note: name-variant duplicate detection is not possible from the provided data because companies.csv has no company name field. Shared-domain duplicate detection is possible.

1) acme-corp.com
- Members: C-0A092931, C-0A092932
- Survivor: C-0A092931
- Conflicts:
  - industry: Technology vs tech
  - employee_count: 500 vs 510
  - hq_country: US vs USA
- Recommendation: keep C-0A092931 as survivor, normalize text fields, manually review employee_count because there is no matching enrichment row.

2) globex.io
- Members: C-0A092933, C-0A092934
- Survivor: C-0A092933
- Conflicts:
  - industry: SaaS vs Technology
- employee_count and hq_country match: 200 and US
- Recommendation: keep C-0A092933 as survivor because SaaS is more specific than Technology; manually confirm industry because there is no matching enrichment row.

Invalid emails
- CT-0010 (C-66D1FC): user0@
- CT-0080 (C-92D97D): user0@
- CT-0081 (C-92D97D): user1@
- CT-0192 (C-425E2A): user2@

Domain mismatches
- CT-0011 (C-66D1FC): email user1@other-domain.com does not match domain 66d1fc.com

Missing company fields that can be filled from zoominfo_enrichment.csv
8/15 missing company fields are fillable = 53.33%

- C-EC3025: employee_count = 400
- C-96039F: employee_count = 400
- C-44EA29: employee_count = 400
- C-D04904: employee_count = 400
- C-B23205: employee_count = 400
- C-60C75F: employee_count = 400
- C-7BBDFA: employee_count = 400
- C-50D386: employee_count = 400

Missing company fields that cannot be filled from the provided enrichment
- C-2D1F1B: hq_country
- C-D73B89: hq_country
- C-44EA29: hq_country
- C-D04904: hq_country
- C-2C60E5: hq_country
- C-93C8BF: employee_count
- C-EE9FFB: hq_country

CRM vs enrichment disagreements
Recommendation below is based only on the provided files.

Industry disagreements: recommend zoominfo_enrichment.csv
- C-66D1FC: CRM tech vs enrichment Computer Software
- C-EC3025: CRM Technology vs enrichment Computer Software
- C-44EA29: CRM tech vs enrichment Computer Software
- C-92D97D: CRM Technology vs enrichment Computer Software
- C-D04904: CRM Technology vs enrichment Computer Software
- C-77A95A: CRM Technology vs enrichment Computer Software
- C-AA8DDA: CRM Technology vs enrichment Computer Software
- C-B25F40: CRM Technology vs enrichment Computer Software
- C-60C75F: CRM tech vs enrichment Computer Software
- C-425E2A: CRM Tech  vs enrichment Computer Software

HQ country disagreements: recommend zoominfo_enrichment.csv
- C-66D1FC: CRM US vs enrichment United States
- C-950043: CRM US vs enrichment United States
- C-EC3025: CRM USA vs enrichment United States
- C-96039F: CRM USA vs enrichment United States
- C-77A95A: CRM US vs enrichment United States
- C-B23205: CRM US vs enrichment United States
- C-E51FB7: CRM USA vs enrichment United States
- C-D0662E: CRM US vs enrichment United States
- C-425E2A: CRM USA vs enrichment United States
- C-2D7423: CRM USA vs enrichment United States

10 fixes with the most pipeline amount at stake
- Not rankable by pipeline amount from the provided data: no deals extract or deal amounts were provided.
- Unranked fixes visible in the provided data:
  1. Backfill employee_count from zoominfo_enrichment.csv for C-EC3025, C-96039F, C-44EA29, C-D04904, C-B23205, C-60C75F, C-7BBDFA, C-50D386.
  2. Manually source employee_count for C-93C8BF; no matching enrichment row/value was provided.
  3. Manually source hq_country for C-2D1F1B, C-D73B89, C-44EA29, C-D04904, C-2C60E5, C-EE9FFB; the provided enrichment does not supply those values.
  4. Merge acme-corp.com duplicates into survivor C-0A092931 and manually resolve employee_count 500 vs 510.
  5. Merge globex.io duplicates into survivor C-0A092933 and manually resolve industry SaaS vs Technology.
  6. Normalize 10 industry values to the zoominfo_enrichment.csv taxonomy where a matching row exists.
  7. Normalize 10 hq_country values to the zoominfo_enrichment.csv country format where a matching row exists.
  8. Correct invalid emails for CT-0010, CT-0080, CT-0081, CT-0192.
  9. Correct the domain mismatch for CT-0011.
  10. Backfill contact titles for 13 contacts and personas for 15 contacts.

I can classify the candidates from the transcript lines, but I cannot name the amount for each deal because no deal-amount file or amounts were provided.

Candidates

1) Deal-EC3025
Prospect line: “We need SCIM user provisioning — our security team will not approve any tool that requires manual account management.”
Classification: real gap
Why: product docs say “SCIM user provisioning … [is] NOT currently listed as supported capabilities.”
Amount: missing from provided data

2) Deal-D0D6B5
Prospect line: “Our payroll runs on ADP Workforce Now and I don't see ADP anywhere in your integration list — that's a dealbreaker for us.”
Classification: real gap
Why: product docs list HRIS integrations as “Workday, BambooHR, Gusto, Rippling” and say “ADP Workforce Now integrations are NOT currently listed as supported capabilities.”
Amount: missing from provided data

3) Deal-CFE7F4
Prospect line: “I tried to build a custom report combining recognition frequency with turnover and couldn't — is that possible on our current plan?”
Classification: plan gate
Why: product docs show “Custom report builder” = Enterprise only.
Amount: missing from provided data

4) Deal-84DBA6
Prospect line: “We turned on the Slack integration in July, but half our managers still haven't given a single recognition — nobody ever trained them on it.”
Classification: rollout/enablement issue
Why: product docs show “Slack … integration” is supported on all plans; the issue described is training/adoption, not missing capability.
Amount: missing from provided data

Excluded
Deal-36C33F is not a prospect-raised gap. The only gap statement is rep language, and the prospect says: “Good to know. The web version should be fine for our office staff for now.”

Summary of true product gaps only
Arithmetic:
- Candidate prospect-raised product-gap-related lines = 4
- Real gaps = 2
- Plan gates = 1
- Rollout/enablement issues = 1

True product gaps:
- Deal-EC3025: SCIM user provisioning
- Deal-D0D6B5: ADP Workforce Now integration

Amounts for both true gaps: missing from provided data

First five minutes
- ROI/retention customer story in 8 of 10 calls = 8 ÷ 10 = 80% (Deal-D348E1, Deal-5408B0, Deal-547B2B, Deal-C61CF7, Deal-60C2C2, Deal-EDC141, Deal-D9A12F, Deal-84DBA6).
  "Quick one to kick off: a 400-person retailer we work with cut regretted turnover 18% in two quarters after automating milestone awards, and I wanted to walk you through exactly how they did it."
- Security/pricing agenda lead in 1 of 10 calls = 1 ÷ 10 = 10% (Deal-403845).
  "I put together a short agenda — security review first, then pricing."
- Pricing-first lead in 1 of 10 calls = 1 ÷ 10 = 10% (Deal-1E2498).
  "You asked for straight pricing last time, so let's start there."
- One call added a first-five-minute competitive pricing contrast in 1 of 10 calls = 1 ÷ 10 = 10% (Deal-C61CF7).
  "And unlike Workhuman, our pricing includes the full rewards catalog with no extra margin."

Three most common objections and how they handle them
- Budget locked / no new line item: 4 of 10 calls = 4 ÷ 10 = 40% (Deal-D348E1, Deal-547B2B, Deal-60C2C2, Deal-84DBA6). He handles it by reframing to turnover-savings ROI and finance signoff.
  "Totally fair. Most teams fund this out of turnover savings — that retailer saved about $210k in avoided backfills, which is how their finance team signed off."
- Revisit next quarter / underwater due to open enrollment: 3 of 10 calls = 3 ÷ 10 = 30% (Deal-5408B0, Deal-C61CF7, Deal-D9A12F). He handles it by proposing a smaller pilot before planning.
  "Makes sense. What if we scope a 90-day pilot with one department so you have internal data before next quarter's planning?"
- Already using spreadsheets and gift cards: 3 of 10 calls = 3 ÷ 10 = 30% (Deal-403845, Deal-EDC141, Deal-1E2498). He handles it by contrasting manual process with automation and analytics.
  "Spreadsheets work until they scale — the difference is automation: milestones fire without HR lifting a finger, and you get analytics on who is being recognized."

Concrete next step agreed
- Rate: 7 of 10 calls = 7 ÷ 10 = 0.70 = 70%.
- Agreed in Deal-D348E1, Deal-5408B0, Deal-547B2B, Deal-C61CF7, Deal-60C2C2, Deal-D9A12F, and Deal-1E2498.
- Not agreed in Deal-403845, Deal-EDC141, and Deal-84DBA6.
  "Yes, Thursday at 2pm works — send the invite and I'll bring our HRIS manager."

Every competitor a prospect raised
- Awardco — Deal-547B2B.
  "We're also in late talks with Awardco — their rewards catalog looks bigger than yours."
- Kudos — Deal-EDC141.
  "How are you different from Kudos? Our CEO used them at her last company."
- No other prospect-raised competitors appear in the provided transcripts.

Coaching notes
1. The opener is overly repetitive: 8 ÷ 10 calls reuse the same retailer/18% turnover story. Add at least one alternate opener for pricing-led and security-led calls.
2. Committee/no-urgency stalls did not convert to a next step in Deal-403845, Deal-EDC141, and Deal-84DBA6; use a dated fallback ask instead of ending with a soft acknowledgment.

Last completed month: 2026-08

Redemption section through 2026-08
- Redemption count: 378
- Spend: $27,846.00
- Unique redeemers: 235
- Redemptions per redeemer: 378 / 235 = 1.6085106 = 1.61

Provider mix (% of spend)
- custom: $10,873.00 / $27,846.00 = 39.05%
- Tremendous: $8,505.00 / $27,846.00 = 30.54%
- Snappy: $5,238.00 / $27,846.00 = 18.81%
- TangoCard: $3,230.00 / $27,846.00 = 11.60%

Check: 39.05% + 30.54% + 18.81% + 11.60% = 100.00%

Top 5 countries by redemptions
1. US: 244
2. CA: 24
3. AU: 21
4. GB: 17
5. NL: 17

Quarter total: 80 tickets.

Broad patterns (ranked by ARR affected)

1. HRIS provisioning failures
   Count/share: 12 tickets; 15.0% = 12/80
   Distinct accounts: 3 — C-0B2213A9, C-0DDFC9A7, C-0F6C0F34
   ARR affected: $114,000 = $36,000 + $48,000 + $30,000
   Two ticket ids: IC-460059, IC-460060
   Recommendation: Fix and monitor the HRIS-to-provisioning path, with alerts when expected new hires are skipped.

2. Redemption / gift card checkout failures
   Count/share: 18 tickets; 22.5% = 18/80
   Distinct accounts: 7 — C-0CEF69FD, C-0B827671, C-0FCCD2DF, C-0F876796, C-14264ABD, C-0D9CA315, C-0B0F1BAB
   ARR affected: $68,800 = $8,900 + $10,700 + $9,600 + $8,700 + $11,000 + $9,600 + $10,300
   Two ticket ids: IC-460025, IC-460024
   Recommendation: Add checkout failure safeguards and redemption reconciliation so failed orders do not deduct points or lose gift card delivery.

3. Recognition points not posting / balance not updating
   Count/share: 20 tickets; 25.0% = 20/80
   Distinct accounts: 9 — C-0D3278C7, C-0BF20542, C-0D0B047C, C-0BE96399, C-0D284E42, C-0D6CC8E3, C-21FEBCBB, C-0DD0626C, C-0B2895EF
   ARR affected: $31,100 = $3,500 + $4,500 + $4,500 + $2,700 + $3,400 + $4,200 + $2,900 + $2,500 + $2,900
   Two ticket ids: IC-460004, IC-460018
   Recommendation: Audit the recognition-to-points ledger flow and add automated replay/reconciliation for stuck balance updates.

4. Slack integration / sync / slash command issues
   Count/share: 14 tickets; 17.5% = 14/80
   Distinct accounts: 4 — C-0B843542, C-10A56B0F, C-0BA71F12, C-8C2E8F00
   ARR affected: $18,900 = $4,400 + $5,400 + $3,900 + $5,200
   Two ticket ids: IC-460041, IC-460046
   Recommendation: Prioritize Slack auth/session persistence and slash-command reliability, with workspace health checks for disconnects.

Single-account noise

5. Billing accuracy / seat-count / tier-price issues
   Count/share: 16 tickets; 20.0% = 16/80
   Distinct accounts: 1 — C-0E9C27D1
   ARR affected: $52,000 = $52,000
   Two ticket ids: IC-460071, IC-460080
   Recommendation: Treat this as an account-specific billing escalation and audit C-0E9C27D1 seat-count source, tier mapping, and renewal pricing before the next invoice cycle.

Q3-2026 weekly marketing goals update

Days elapsed: 66/92 = 0.7174 = 71.74%

SQMs: QTD actual 230; target 300; delta = 230 - 300 = -70; pace: ahead. Expected by this point = 300 × 66/92 = 215.22, and 230 > 215.22.

SQOs: QTD actual 84; target 120; delta = 84 - 120 = -36; pace: behind. Expected by this point = 120 × 66/92 = 86.09, and 84 < 86.09.

DS2s: QTD actual 40; target 75; delta = 40 - 75 = -35; pace: behind. Expected by this point = 75 × 66/92 = 53.80, and 40 < 53.80.

Closed-lost MIA rate: QTD actual 5/25 = 0.20 = 20.0%; target 0.10 = 10.0%; delta = 20.0% - 10.0% = +10.0 pts; pace: behind. Lower is better, and 20.0% is above target.

Same-quarter close count: QTD actual 10; target 20; delta = 10 - 20 = -10; pace: behind. Expected by this point = 20 × 66/92 = 14.35, and 10 < 14.35.

Active pipeline coverage against target: QTD actual 3,000,000 / 4,000,000 = 0.75 = 75.0%; target 100.0%; delta = 75.0% - 100.0% = -25.0 pts; pace: ahead. Expected by this point = 66/92 = 71.74%, and 75.0% > 71.74%.

What moved this week: The provided data is QTD-only, so week-over-week movement is missing. Based on the current quarter snapshot only, SQMs and active pipeline coverage are pacing ahead of elapsed-quarter expectations, while SQOs, DS2s, same-quarter closes, and closed-lost MIA rate are behind target pace.

Marketing generated 46 SQMs against a target of 52, or 46/52 = 88.5% of plan, leaving a gap of 52 - 46 = 6. Webinar drove 18 of 46 SQMs, which is 18/46 = 39.1% of weekly volume, while paid search held cost per SQM at $150. The week’s signal: demand stayed productive, webinars carried a meaningful share of the load, and the path to target next week is clear.

Sales converted 14 SQOs, set 9 DS2 meetings, and created $310,000 in new pipeline. That equals 9/14 = 64.3% as many DS2s as SQOs, and $310,000/14 = $22,142.86 of pipeline per SQO. Same-quarter close count came in at 3, which is 3/14 = 21.4% relative to SQO volume. Net: solid pipeline creation, steady meeting progression, and closes still landing in-quarter.

CS saved 2 renewals this week, moved Team NPS to 61, and heads into next week with 3 open red-flag accounts. Put simply, the team protected 2 renewals while carrying a remaining red-flag load of 3, so 3/2 = 1.5 open red-flag accounts for every renewal saved this week. The retention story is moving in the right direction, with a strong NPS baseline and a defined risk queue to tackle next.

PLG added 412 new signups with activation at 31%, and 38 companies reached the aha moment of 10 recognition gives. The extract supports 412 × 0.31 = 127.72, so the exact activated signup count is not provided; the stated metric is the 31% activation rate. Aha-moment companies were 38/412 = 9.2% of signup volume. Bottom line: signup volume was healthy, activation has room to improve, and 38 companies crossed a meaningful product-value threshold.

partner-digest-section0.67

? The Question

Write the partner digest for the period. Every partner in the roster appears once: active plays get status with numbers, quiet partners get one line. Partner-sourced pipeline count and amount must match the deal data. Nothing omitted, nothing added.

cost $1.4767 · 176s · in 31,672 / out 2,925 tok

✓ all_partners✗ pipeline_amount✓ quiet_one_line

✓ Correct Answer (ground truth)

roster: partner_name=Apex Rewards Co; status=active | partner_name=HRCloud Partners; status=active | partner_name=CultureBridge; status=active | partner_name=WorkWell Group; status=active | partner_name=Recogniq; status=quiet | partner_name=KudosWave; status=quiet … (+2 more)
per_partner_pipeline: {"Apex Rewards Co": {"count": 2, "amount": 275000}, "HRCloud Partners": {"count": 1, "amount": 140000}, "CultureBridge": {"count": 2, "amount": 135000}}
partner_sourced_pipeline: count=5; amount=550000
quiet_partners: Recogniq, KudosWave, PeopleFirst Advisors, TotalPerk
active_no_deals: WorkWell Group
rule: every roster partner named exactly once; quiet partners get one line; no partners outside roster.
graded checks: all_partners · pipeline_amount · quiet_one_line

Model's actual answer

show the model's full answer

- Apex Rewards Co — active: 2 partner-sourced opps, $275,000 pipeline (Deal-DDAAF2 $180,000 + Deal-2CF33E $95,000 = $275,000). Slack: co-webinar locked for 09-15; both sourced opps are in DS1.
- HRCloud Partners — active: 1 partner-sourced opp, $140,000 pipeline (Deal-F1CDA5 $140,000 = $140,000). Slack: integration referral cleared security review and moved to DS2.
- CultureBridge — active: 2 partner-sourced opps, $135,000 pipeline (Deal-096E1D $60,000 + Deal-067213 $75,000 = $135,000). Slack: lunch-and-learn produced two sourced opps; both are early stage.
- WorkWell Group — active: 0 partner-sourced opps, $0 pipeline. Slack: no sourced deals this period; joint playbook restart targeted for Q4, with a planning call booked for 09-09.
- Recogniq — quiet: no Slack update or partner-sourced deal in the provided data.
- KudosWave — quiet: no Slack update or partner-sourced deal in the provided data.
- PeopleFirst Advisors — quiet: no Slack update or partner-sourced deal in the provided data.
- TotalPerk — quiet: no Slack update or partner-sourced deal in the provided data.

rfp-answer-from-policyPASS 1.00

? The Question

Answer the 10 questionnaire items from the policy excerpts only. Cite the excerpt id for every answer. Where the excerpts do not answer the question, mark it unanswerable and say what document would; do not guess. Tone: vendor response, direct.

cost $0.6828 · 37s · in 15,295 / out 1,244 tok

✓ answered_count✓ unanswerable_flagged✓ citations✓ no_guess

✓ Correct Answer (ground truth)

answered_count: 7
answer_map: {"Q1": ["P1"], "Q2": ["P1"], "Q3": ["P2"], "Q4": ["P3"], "Q5": ["P4"], "Q6": ["P5"], "Q7": ["P6"]}
unanswerable: Q8, Q9, Q10
valid_citation_ids: P1, P2, P3, P4, P5, P6, P7, P8
rule: unanswerable items must be flagged and the document that would answer them named; do not guess.
graded checks: answered_count · unanswerable_flagged · citations · no_guess

Model's actual answer

show the model's full answer

Q1: Yes. Customer data is encrypted at rest using AES-256. [P1]

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

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

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

Q5: The 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; ISO 27001 is not addressed in [P1]-[P8]. The ISO 27001 certificate or trust portal certifications page would answer this.

Q9: Unanswerable from the provided excerpts; contractual uptime SLA is not addressed in [P1]-[P8]. The MSA, order form, or service level agreement would answer this.

Q10: Unanswerable from the provided excerpts; HIPAA BAA terms are not addressed in [P1]-[P8]. The DPA, BAA template, or legal terms would answer this.

NDA-1 — [PARTY A] and Bonusly: GREEN — Standard mutual NDA with standard carve-outs and standard governing law; key clauses: "Mutual confidentiality," "Carve-outs: information that (a) is or becomes publicly available... (e) must be disclosed by law or court order," and "Governing law: the laws of the State of Delaware, USA"; term math: 2 years + 3 years survival = 5 years total confidentiality tail.

NDA-2 — [PARTY B] and Bonusly: YELLOW — Counsel review because it embeds a non-solicit: "During the term of this Agreement and for eighteen (18) months thereafter, neither party shall solicit for employment or hire any employee of the other party with whom it came into contact under this Agreement"; restricted period math: 3 years term + 18 months (1.5 years) after = 4.5 years of hiring restriction.

NDA-3 — [PARTY C] and Bonusly: RED — Full legal review because it contains a non-compete, has no carve-outs, and uses non-US governing law; driving clauses: "Recipient shall not, directly or indirectly, engage in or provide services to any business that competes with Discloser's business," "No confidentiality carve-outs are stated in this Agreement," and "the laws of the Republic of Ireland"; term math: 5-year one-way confidentiality term plus a 3-year non-compete.