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

Deals
- No deals extract was provided.
- Owner, stage, amount, close date, and why-buys completeness cannot be calculated.
- Pipeline amount at stake cannot be calculated or attributed to fixes.

Companies — 34 records
- Industry: 34 / 34 = 100.00%
- Employee count: 25 / 34 = 73.53%
- HQ country: 28 / 34 = 82.35%

Contacts — 52 records
- Email populated: 52 / 52 = 100.00%
- Email syntactically valid: 48 / 52 = 92.31%
- Title: 39 / 52 = 75.00%
- Persona: 37 / 52 = 71.15%

MISSING COMPANY FIELDS AND ENRICHMENT FIXES

Safe fills supported by matching enrichment rows:
- C-EC3025: employee_count blank → 400
- C-96039F: employee_count blank → 400
- C-44EA29: employee_count blank → 400
- C-D04904: employee_count blank → 400
- C-B23205: employee_count blank → 400
- C-60C75F: employee_count blank → 400
- C-7BBDFA: employee_count blank → 400
- C-50D386: employee_count blank → 400

After these fills:
- Employee count: (25 + 8) / 34 = 33 / 34 = 97.06%

Missing fields that cannot be filled from the enrichment export:
- C-93C8BF: employee_count missing; no matching enrichment row
- C-2D1F1B: hq_country missing; matching enrichment value also blank
- C-D73B89: hq_country missing; matching enrichment value also blank
- C-44EA29: hq_country missing; matching enrichment value also blank
- C-D04904: hq_country missing; matching enrichment value also blank
- C-2C60E5: hq_country missing; matching enrichment value also blank
- C-EE9FFB: hq_country missing; no matching enrichment row

No industry values are missing.

CRM–ENRICHMENT DISAGREEMENTS

Recommendation: use enrichment for industry taxonomy and country standardization because its values are more consistently formatted. Preserve the previous CRM value in audit history. The data does not establish which source is factually authoritative.

- C-66D1FC
  - industry: CRM “tech”; enrichment “Computer Software” → recommend enrichment
  - hq_country: CRM “US”; enrichment “United States” → recommend enrichment as standardized form
- C-950043
  - hq_country: CRM “US”; enrichment “United States” → recommend enrichment as standardized form
- C-EC3025
  - industry: CRM “Technology”; enrichment “Computer Software” → recommend enrichment
  - hq_country: CRM “USA”; enrichment “United States” → recommend enrichment as standardized form
- C-96039F
  - hq_country: CRM “USA”; enrichment “United States” → recommend enrichment as standardized form
- C-44EA29
  - industry: CRM “tech”; enrichment “Computer Software” → recommend enrichment
- C-92D97D
  - industry: CRM “Technology”; enrichment “Computer Software” → recommend enrichment
- C-D04904
  - industry: CRM “Technology”; enrichment “Computer Software” → recommend enrichment
- C-77A95A
  - industry: CRM “Technology”; enrichment “Computer Software” → recommend enrichment
  - hq_country: CRM “US”; enrichment “United States” → recommend enrichment as standardized form
- C-AA8DDA
  - industry: CRM “Technology”; enrichment “Computer Software” → recommend enrichment
- C-B23205
  - hq_country: CRM “US”; enrichment “United States” → recommend enrichment as standardized form
- C-E51FB7
  - hq_country: CRM “USA”; enrichment “United States” → recommend enrichment as standardized form
- C-D0662E
  - hq_country: CRM “US”; enrichment “United States” → recommend enrichment as standardized form
- C-B25F40
  - industry: CRM “Technology”; enrichment “Computer Software” → recommend enrichment
- C-60C75F
  - industry: CRM “tech”; enrichment “Computer Software” → recommend enrichment
- C-425E2A
  - industry: CRM “Tech ”; enrichment “Computer Software” → recommend enrichment
  - hq_country: CRM “USA”; enrichment “United States” → recommend enrichment as standardized form
- C-2D7423
  - hq_country: CRM “USA”; enrichment “United States” → recommend enrichment as standardized form

DUPLICATE COMPANY CLUSTERS

Company names were not provided, so name-variant matching cannot be performed. Shared-domain matching identifies two clusters.

1. acme-corp.com
   - Records: C-0A092931, C-0A092932
   - Survivor: C-0A092931, using the lowest alias as a deterministic tie-break
   - Conflict requiring review:
     - industry: C-0A092931 = “Technology”; C-0A092932 = “tech”
     - employee_count: C-0A092931 = 500; C-0A092932 = 510
     - hq_country: C-0A092931 = “US”; C-0A092932 = “USA”
   - Fix: merge records, preserve both source values in audit history, and do not choose between 500 and 510 without another source.

2. globex.io
   - Records: C-0A092933, C-0A092934
   - Survivor: C-0A092933, using the lowest alias as a deterministic tie-break
   - Conflict requiring review:
     - industry: C-0A092933 = “SaaS”; C-0A092934 = “Technology”
   - Matching values:
     - employee_count = 200
     - hq_country = “US”
   - Fix: merge records and retain the conflicting industry values for review.

INVALID EMAILS

- CT-0010: “user0@”
- CT-0080: “user0@”
- CT-0081: “user1@”
- CT-0192: “user2@”

Fix: replace only from a verified source or clear the invalid value and queue it for enrichment. No replacement email was provided.

DOMAIN MISMATCHES

- CT-0011: email domain “other-domain.com” does not match contact/company domain “66d1fc.com”

Fix: verify company affiliation or correct the email from a trusted source. The provided data does not establish which value is correct.

MISSING CONTACT FIELDS

Missing title — 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

Missing persona — 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

Fix: enrich or manually research these fields; no source values were provided, so none can be safely filled.

TOP 10 FIXES BY PIPELINE AMOUNT AT STAKE

Cannot be produced: the deals extract—including deal aliases, company associations, amounts, owners, stages, close dates, and why-buys—was not provided. Therefore, no fix can be ranked by pipeline amount without inventing data.

Candidate assessment

1. Deal-EC3025 — Amount: not provided
Prospect: “We need SCIM user provisioning — our security team will not approve any tool that requires manual account management.”
Classification: Real gap
Basis: Product docs state that SCIM user provisioning is not currently listed as supported.

2. Deal-D0D6B5 — Amount: not provided
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
Basis: Product docs state that ADP Workforce Now integrations are not currently listed as supported.

3. Deal-CFE7F4 — Amount: not provided
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
Basis: The custom report builder exists, but only on the Enterprise tier.

4. Deal-84DBA6 — Amount: not provided
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
Basis: Slack integration is supported on all plans; the stated problem is lack of manager training.

Excluded: Deal-36C33F. The mobile-app limitation was raised by Alex Franklin, not the prospect, so it does not count as prospect voice.

Summary: true product gaps

- Deal-EC3025 — SCIM user provisioning — Amount: not provided
- Deal-D0D6B5 — ADP Workforce Now integration — Amount: not provided

show the model's full answer

1. First-five-minute lead

- Customer outcome story: 8/10 calls (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.”
- Agenda: 1/10 (10%) — Deal-403845.
  > “I put together a short agenda — security review first, then pricing.”
- Pricing: 1/10 (10%) — Deal-1E2498.
  > “You asked for straight pricing last time, so let's start there.”
- In Deal-C61CF7, the rep also proactively positioned against Workhuman at minute 2.

2. Three most common objections and handling

- Budget locked: 4/10 calls (40%) — Deal-D348E1, Deal-547B2B, Deal-60C2C2, Deal-84DBA6. He reframes the purchase around turnover savings and finance approval.
  > “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.”
- Timing/open-enrollment workload: 3/10 calls (30%) — Deal-5408B0, Deal-C61CF7, Deal-D9A12F. He proposes a limited 90-day pilot to create data 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?”
- Existing spreadsheet and gift-card process: 3/10 calls (30%) — Deal-403845, Deal-EDC141, Deal-1E2498. He differentiates through automated milestones and recognition 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.”

3. Concrete next-step rate

7 calls with an agreed date, time, and attendee ÷ 10 total calls = 70%.

Agreed: Deal-D348E1, Deal-5408B0, Deal-547B2B, Deal-C61CF7, Deal-60C2C2, Deal-D9A12F, Deal-1E2498.  
Not agreed: Deal-403845, Deal-EDC141, Deal-84DBA6.

> “Yes, Thursday at 2pm works — send the invite and I'll bring our HRIS manager.”

4. Competitors raised by prospects

- 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.”

Workhuman was raised by the rep, not a prospect.

Coaching notes

1. Preserve the outcome-led opening, but replace the repeated retailer story with discovery tied to each prospect’s situation; 8/10 calls use exactly the same opener.
2. When prospects defer to a committee or express no urgency, do not end with acknowledgment alone. Diagnose decision criteria and secure a concrete follow-up, since all three calls without an agreed next step ended this way.

Redemption section — through 2026-08

Last completed month: 2026-08

- Redemption count: 378
- Spend: $27,846.00
- Unique redeemers: 235
- Redemptions per redeemer: 378 ÷ 235 = 1.6085, or 1.61

Provider mix by 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%
- Total: 39.05% + 30.54% + 18.81% + 11.60% = 100.00%

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

Broad patterns — ranked by ARR exposure

1. HRIS provisioning/sync failures
- Count: 12
- Share: 12 ÷ 80 = 15.0%
- Distinct accounts: 3
- ARR affected: $30,000 + $36,000 + $48,000 = $114,000
- Example tickets: IC-460059, IC-460062
- Recommendation: Prioritize HRIS sync reliability and add alerts for skipped provisioning events and silent log failures.

2. Redemption and gift-card failures
- Count: 18
- Share: 18 ÷ 80 = 22.5%
- Distinct accounts: 7
- ARR affected: $8,900 + $10,700 + $9,600 + $8,700 + $11,000 + $9,600 + $10,300 = $68,800
- Example tickets: IC-460025, IC-460024
- Recommendation: Investigate checkout failures end-to-end and prevent point deductions until gift-card fulfillment succeeds.

3. Recognition points not posting
- Count: 20
- Share: 20 ÷ 80 = 25.0%
- Distinct accounts: 9
- ARR affected: $3,500 + $4,500 + $2,700 + $3,400 + $4,200 + $2,900 + $2,500 + $2,900 + $4,500 = $31,100
- Example tickets: IC-460004, IC-460016
- Recommendation: Audit recognition-to-balance processing and add reconciliation for delivered recognitions with missing points.

4. Slack integration/command failures
- Count: 14
- Share: 14 ÷ 80 = 17.5%
- Distinct accounts: 4
- ARR affected: $4,400 + $5,400 + $3,900 + $5,200 = $18,900
- Example tickets: IC-460041, IC-460049
- Recommendation: Stabilize Slack authentication, sync-toggle persistence, and slash-command execution.

Single-account noise — ranked by ARR exposure

5. Billing seat-count/tier errors
- Count: 16
- Share: 16 ÷ 80 = 20.0%
- Distinct accounts: 1
- ARR affected: $52,000
- Account: C-0E9C27D1
- Example tickets: IC-460071, IC-460078
- Recommendation: Escalate an account-specific billing correction and audit C-0E9C27D1’s seat-count and renewal-tier configuration.

Q3-2026 weekly marketing goals update — 66 of 92 days elapsed (66 ÷ 92 = 71.74%)

| Metric | QTD actual | Target | Delta (actual − target) | Pace |
|---|---:|---:|---:|---|
| SQMs | 230 | 300 | 230 − 300 = **−70** | **Ahead**: 230 ÷ 300 = 76.67%, versus 71.74% elapsed |
| SQOs | 84 | 120 | 84 − 120 = **−36** | **Behind**: 84 ÷ 120 = 70.00%, versus 71.74% elapsed |
| DS2s | 40 | 75 | 40 − 75 = **−35** | **Behind**: 40 ÷ 75 = 53.33%, versus 71.74% elapsed |
| Closed-lost MIA rate | 5 ÷ 25 = **20.00%** | ≤10.00% | 20.00% − 10.00% = **+10.00 pp unfavorable** | **Behind**: current rate exceeds the maximum target |
| Same-quarter close count | 10 | 20 | 10 − 20 = **−10** | **Behind**: 10 ÷ 20 = 50.00%, versus 71.74% elapsed |
| Active pipeline coverage | $3,000,000 ÷ $4,000,000 = **75.00% (0.75×)** | $4,000,000 | $3,000,000 − $4,000,000 = **−$1,000,000** | **Ahead**: 75.00% of target, versus 71.74% elapsed |

What moved this week cannot be determined: the provided data contains only current QTD values and no prior-week figures or weekly changes.

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

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

Q3. Yes. Bonusly maintains a SOC 2 Type II report, renewed annually. Prospects can obtain the report under NDA. [P2]

Q4. Customer data is retained for 90 days after contract termination, then deleted from production systems. [P3]

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

Q6. Yes. SAML 2.0 single sign-on is 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. An ISO 27001 certificate or certification statement would answer this question.

Q9. Unanswerable from the provided excerpts. The contractual Service Level Agreement or uptime policy would answer this question.

Q10. Unanswerable from the provided excerpts. Bonusly’s HIPAA/BAA policy or standard Business Associate Agreement terms would answer this question.

NDA-1 — GREEN — Standard mutual NDA: two-year term, three-year survival, Delaware law, and complete carve-outs, including information that “is independently developed” and “must be disclosed by law or court order.”

NDA-2 — YELLOW — Counsel review due to the embedded 18-month 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.”

NDA-3 — RED — Full legal review due to the broad three-year non-compete (“Recipient shall not, directly or indirectly, engage in or provide services to any business that competes with Discloser's business”), unusual Republic of Ireland law and exclusive jurisdiction (“the parties submit to the exclusive jurisdiction of its courts”), five-year one-way term, and absence of confidentiality carve-outs.