Audit the CRM extract for completeness and propose fixes. Deals need owner, stage, amount, close date, why-buys; companies need industry, employee count, HQ country; contacts need email, title, persona. Report completeness percent per field. Identify duplicate company clusters (name variants, shared domain) with a survivor per cluster. List invalid emails and domain mismatches. Fill missing company fields only where the enrichment export has a matching row; where CRM and enrichment disagree list both and recommend a source. Never invent a value. End with the 10 fixes with the most pipeline amount at stake.

cost $0.2744 · 264s · in 13,794 / out 25,044 tok

✓ dup_clusters✗ invalid_emails✓ survivor_language✓ completeness_pct✓ no_invent

✓ Correct Answer (ground truth)

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 completeness audit (only using provided files)

Deals completeness
- No deals dataset was provided. Cannot compute completeness for owner, stage, amount, close date, why-buys. Data missing.

Companies completeness (companies.csv)
- Industry: 34/34 = 100.0%
- Employee count: 25/34 = 73.5%
- HQ country: 28/34 = 82.4%

Contacts completeness (contacts.csv)
- Email: 52/52 = 100.0%
- Title: 39/52 = 75.0%
- Persona: 37/52 = 71.2%

Duplicate company clusters (shared domain; survivor chosen by most non-empty target fields, then smallest alias)
- acme-corp.com → aliases [C-0A092931, C-0A092932] → survivor C-0A092931
- globex.io → aliases [C-0A092933, C-0A092934] → survivor C-0A092933

Invalid emails (failing basic format user@domain.tld)
- CT-0010 (C-66D1FC): user0@
- CT-0080 (C-92D97D): user0@
- CT-0081 (C-92D97D): user1@
- CT-0192 (C-425E2A): user2@

Domain mismatches (email domain vs declared contact domain)
- CT-0011 (C-66D1FC): email_domain=other-domain.com, declared_domain=66d1fc.com

Company field fills from enrichment (only where CRM is blank and zoominfo_enrichment.csv has a value)
- C-EC3025 ec3025.com employee_count: fill 400 (source: zoominfo)
- C-96039F 96039f.com employee_count: fill 400 (source: zoominfo)
- C-44EA29 44ea29.com employee_count: fill 400 (source: zoominfo)
- C-D04904 d04904.com employee_count: fill 400 (source: zoominfo)
- C-B23205 b23205.com employee_count: fill 400 (source: zoominfo)
- C-60C75F 60c75f.com employee_count: fill 400 (source: zoominfo)
- C-7BBDFA 7bbdfa.com employee_count: fill 400 (source: zoominfo)
- C-50D386 50d386.com employee_count: fill 400 (source: zoominfo)
Note: No eligible HQ country fills; enrichment HQ is blank for the companies with missing CRM HQ.

CRM vs enrichment disagreements (list both; recommend source)
- C-66D1FC 66d1fc.com industry: CRM=tech vs ZI=Computer Software → recommend: zoominfo
- C-66D1FC 66d1fc.com hq_country: CRM=US vs ZI=United States → recommend: zoominfo
- C-950043 950043.com hq_country: CRM=US vs ZI=United States → recommend: zoominfo
- C-EC3025 ec3025.com industry: CRM=Technology vs ZI=Computer Software → recommend: zoominfo
- C-EC3025 ec3025.com hq_country: CRM=USA vs ZI=United States → recommend: zoominfo
- C-96039F 96039f.com hq_country: CRM=USA vs ZI=United States → recommend: zoominfo
- C-44EA29 44ea29.com industry: CRM=tech vs ZI=Computer Software → recommend: zoominfo
- C-92D97D 92d97d.com industry: CRM=Technology vs ZI=Computer Software → recommend: zoominfo
- C-D04904 d04904.com industry: CRM=Technology vs ZI=Computer Software → recommend: zoominfo
- C-77A95A 77a95a.com industry: CRM=Technology vs ZI=Computer Software → recommend: zoominfo
- C-77A95A 77a95a.com hq_country: CRM=US vs ZI=United States → recommend: zoominfo
- C-AA8DDA aa8dda.com industry: CRM=Technology vs ZI=Computer Software → recommend: zoominfo
- C-B23205 b23205.com hq_country: CRM=US vs ZI=United States → recommend: zoominfo
- C-E51FB7 e51fb7.com hq_country: CRM=USA vs ZI=United States → recommend: zoominfo
- C-D0662E d0662e.com hq_country: CRM=US vs ZI=United States → recommend: zoominfo
- C-B25F40 b25f40.com industry: CRM=Technology vs ZI=Computer Software → recommend: zoominfo
- C-60C75F 60c75f.com industry: CRM=tech vs ZI=Computer Software → recommend: zoominfo
- C-425E2A 425e2a.com industry: CRM=Tech  vs ZI=Computer Software → recommend: zoominfo
- C-425E2A 425e2a.com hq_country: CRM=USA vs ZI=United States → recommend: zoominfo
- C-2D7423 2d7423.com hq_country: CRM=USA vs ZI=United States → recommend: zoominfo

Proposed fixes
- Companies
  - Deduplicate by domain; merge non-survivors into survivors and enforce domain-unique constraint. Survivors: C-0A092931 for acme-corp.com; C-0A092933 for globex.io.
  - Fill missing employee_count from enrichment where available (8 fills listed above).
  - Normalize industry to ZoomInfo taxonomy (e.g., “tech”, “Tech ” → “Computer Software”) and HQ country to “United States/Canada/UK” as provided by enrichment; adopt ZoomInfo as the system of record for these fields.
  - Standardize country values; treat US/USA/United States as one value; enforce picklist.
- Contacts
  - Enforce RFC5322-like email validation; reject addresses missing a domain TLD.
  - Enforce email_domain == company domain unless explicitly allowed; flag CT-0011 for correction.
  - Make title and persona required; add picklists for title/role-persona mapping.
- Governance
  - Add nightly enrichment sync to backfill missing company attributes only when CRM is blank; on disagreements, log exceptions and route for review with ZoomInfo as default source of truth.

Arithmetic shown above as counts/total = percent.

Top 10 fixes by pipeline amount at stake
- Cannot compute or rank: no deals data (owner, stage, amount, close date, why-buys) was provided. To produce this, provide a deals extract with opportunity/company linkage and Amount per record.

Candidates
- Deal-EC3025 | Amount: MISSING
  - Prospect: 'We need SCIM user provisioning — our security team will not approve any tool that requires manual account management.'
  - Classification: real gap
  - Docs basis: “SCIM user provisioning … are NOT currently listed as supported capabilities.”

- Deal-D0D6B5 | Amount: MISSING
  - Prospect: 'Our payroll runs on ADP Workforce Now and I don't see ADP anywhere in your integration list — that's a dealbreaker for us.'
  - Classification: real gap
  - Docs basis: “ADP Workforce Now integrations are NOT currently listed as supported capabilities.”

- Deal-CFE7F4 | Amount: MISSING
  - Prospect: 'I tried to build a custom report combining recognition frequency with turnover and couldn't — is that possible on our current plan?'
  - Classification: plan gate
  - Docs basis: Plans table shows “Custom report builder | — | — | yes” (Enterprise-only).

- Deal-84DBA6 | Amount: MISSING
  - Prospect: '"We turned on the Slack integration in July, but half our managers still haven't given a single recognition — nobody ever trained them on it."'
  - Classification: rollout/enablement issue
  - Docs basis: “Slack, Microsoft Teams (all plans).” Issue is training/adoption, not capability.

Summary (real gaps only)
- Deal-EC3025 | Amount: MISSING | Gap: SCIM user provisioning not supported. Prospect: 'We need SCIM user provisioning — our security team will not approve any tool that requires manual account management.'
- Deal-D0D6B5 | Amount: MISSING | Gap: ADP Workforce Now integration not supported. Prospect: 'Our payroll runs on ADP Workforce Now and I don't see ADP anywhere in your integration list — that's a dealbreaker for us.'

Arithmetic
- Monetary amounts are not provided in the supplied files; no revenue calculations are possible.

Lead (first five minutes)
- Case-study ROI opener — 8/10 = 80%: "Quick one to kick off: a 400-person retailer we work with cut regretted turnover 18% in two quarters after automating milestone awards, and I wanted to walk you through exactly how they did it."
- Agenda-led — 1/10 = 10%: "I put together a short agenda — security review first, then pricing."
- Pricing-first — 1/10 = 10%: "You asked for straight pricing last time, so let's start there."

Handling of the three most common objections
- Budget locked until next FY — 4/10 = 40%: "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 (open enrollment) — 3/10 = 30%: "Makes sense. What if we scope a 90-day pilot with one department so you have internal data before next quarter's planning?"
- Already handling via spreadsheet/gift cards — 3/10 = 30%: "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 agreed / 10 total = 70.0%: "Yes, Thursday at 2pm works — send the invite and I'll bring our HRIS manager."

Competitors a prospect raised
- Awardco: "We're also in late talks with Awardco — their rewards catalog looks bigger than yours."
- Kudos: "How are you different from Kudos? Our CEO used them at her last company."

Coaching notes
- When budget/committee blocks progress, replace “Understood — I’ll leave it with you.” with a pencil-in and fallback (“Let’s pencil a 30-min for next Tuesday; if committee slips, we’ll convert it to a Q&A.”).
- After the spreadsheet objection, add a calibrated ask to secure momentum (“If we send a 2-week pilot plan today, can we align your HRIS manager on a kickoff date this week?”).

Last completed month: 2026-08

- Redemptions: 372
  Arithmetic: count(rows with redeemed_at ≤ 2026-08-31) = 372

- Spend (USD): 27,325.00
  Arithmetic: sum(amount_usd across 372 rows) = 27,325.00

- Unique redeemers: 232
  Arithmetic: count(distinct user_key) = 232

- Redemptions per redeemer: 1.60
  Arithmetic: 372 ÷ 232 = 1.6034 → 1.60

- Provider mix (% of spend; sums to 100.00%)
  Arithmetic base: total spend = 27,325.00
  • custom: 10,873.00 ÷ 27,325.00 = 39.79%
  • Tremendous: 8,505.00 ÷ 27,325.00 = 31.13%
  • Snappy: 4,717.00 ÷ 27,325.00 = 17.26%
  • TangoCard: 3,230.00 ÷ 27,325.00 = 11.82%
  Total: 39.79 + 31.13 + 17.26 + 11.82 = 100.00%

- Top 5 countries by redemptions (count)
  Arithmetic: count(rows by country), sorted desc
  1) US = 240
  2) CA = 24
  3) AU = 20
  4) GB = 17
  5) NL = 17

1. HRIS provisioning failures [Broad]
   - count/share: 12/80 = 15.0%
   - distinct accounts: 3
   - ARR affected: $114,000 (C-0B2213A9 $36,000 + C-0DDFC9A7 $48,000 + C-0F6C0F34 $30,000 = $114,000)
   - tickets: IC-460059, IC-460055
   - recommendation: Add retry + alert on zero-create runs; block billing sync when HRIS delta >0 but creates=0.

2. Redemption/checkout & gift card failures [Broad]
   - count/share: 18/80 = 22.5%
   - distinct accounts: 7
   - ARR affected: $68,800 (C-0B0F1BAB $10,300 + C-0B827671 $10,700 + C-0CEF69FD $8,900 + C-0D9CA315 $9,600 + C-0F876796 $8,700 + C-0FCCD2DF $9,600 + C-14264ABD $11,000 = $68,800)
   - tickets: IC-460025, IC-460030
   - recommendation: Add checkout timeout + idempotent code issuance; auto-refund on failure.

3. Billing/invoice seat-count or tier errors [Single-account]
   - count/share: 16/80 = 20.0%
   - distinct accounts: 1
   - ARR affected: $52,000 (C-0E9C27D1 $52,000 = $52,000)
   - tickets: IC-460071, IC-460069
   - recommendation: Lock invoice seat source to licensing-of-record; pre-bill diff alert for seat/tier deltas.

4. Recognition points not credited / balances not updating [Broad]
   - count/share: 20/80 = 25.0%
   - distinct accounts: 9
   - ARR affected: $31,100 (C-0B2895EF $2,900 + C-0BE96399 $2,700 + C-0BF20542 $4,500 + C-0D0B047C $4,500 + C-0D284E42 $3,400 + C-0D3278C7 $3,500 + C-0D6CC8E3 $4,200 + C-0DD0626C $2,500 + C-21FEBCBB $2,900 = $31,100)
   - tickets: IC-460004, IC-460016
   - recommendation: Add durable queue and reconciliation to backfill; alert when recognition->balance >5m.

5. Slack integration failures (sync, slash cmd, re-auth) [Broad]
   - count/share: 14/80 = 17.5%
   - distinct accounts: 4
   - ARR affected: $18,900 (C-0B843542 $4,400 + C-0BA71F12 $3,900 + C-10A56B0F $5,400 + C-8C2E8F00 $5,200 = $18,900)
   - tickets: IC-460041, IC-460047
   - recommendation: Detect revoked tokens and prompt reauth; health-check slash endpoint.

SQMs — QTD actual: 230; Target: 300; Delta: 230 - 300 = -70; Pace: ahead (expected by day: 300 * 66/92 = 215.22; 230 > 215.22).
SQOs — QTD actual: 84; Target: 120; Delta: 84 - 120 = -36; Pace: behind (expected by day: 120 * 66/92 = 86.09; 84 < 86.09).
DS2s — QTD actual: 40; Target: 75; Delta: 40 - 75 = -35; Pace: behind (expected by day: 75 * 66/92 = 53.80; 40 < 53.80).
closed-lost MIA rate — QTD actual: 5/25 = 0.20; Target: 0.10; Delta: 0.20 - 0.10 = 0.10; Pace: behind.
same-quarter closes — QTD actual: 10; Target: 20; Delta: 10 - 20 = -10; Pace: behind (expected by day: 20 * 66/92 = 14.35; 10 < 14.35).
active pipeline coverage against target — QTD actual: 3000000/4000000 = 0.75x; Target: 1.00x; Delta: 0.75x - 1.00x = -0.25x; Pace: behind.

What moved this week: No week-over-week data was provided (only QTD snapshots), so I cannot attribute changes versus last week. Based on current QTD standing, the largest gaps to target are DS2s (40 - 75 = -35), SQOs (84 - 120 = -36), same-quarter closes (10 - 20 = -10), and active pipeline coverage (3,000,000/4,000,000 = 0.75x vs 1.00x). Provide last week’s QTD to quantify movement.

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, available to prospects under NDA. [P2]
Q4: Customer data is retained for the duration of the contract plus 90 days, then deleted from production systems. [P3]
Q5: The subprocessor list is published at trust.bonusly.com, and customers receive 30 days notice before a new subprocessor is added. [P4]
Q6: Yes. SAML 2.0 single sign-on (and SCIM provisioning) 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 provided excerpts. This would be documented by an ISO 27001 certificate/attestation (e.g., on the trust portal or certifications page).
Q9: Unanswerable from provided excerpts. This would be defined in the contractual Service Level Agreement (SLA), typically within the MSA or SLA document.
Q10: Unanswerable from provided excerpts. This would be covered in the HIPAA/BAA policy or a Business Associate Agreement template/contract.

NDA-1 — GREEN — Standard mutual NDA with full carve‑outs; "Carve-outs: information that (a) is or becomes publicly available through no breach, (b) was known prior to disclosure, (c) is received from a third party without duty of confidence, (d) is independently developed, or (e) must be disclosed by law or court order." Arithmetic: 2-year term + 3-year survival = 5 years total confidentiality obligation.

NDA-2 — YELLOW — Embedded non-solicitation; "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." Arithmetic: 3-year term + 18 months = 4.5 years restraint.

NDA-3 — RED — One-way with broad non-compete and no carve-outs; "For a period of three (3) years following the Effective Date, Recipient shall not, directly or indirectly, engage in or provide services to any business that competes with Discloser's business." Also: no confidentiality carve-outs stated; 5-year term; exclusive Republic of Ireland governing law/jurisdiction.