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

Audit scope:
- companies.csv: 34 company rows
- contacts.csv: 52 contact rows
- zoominfo_enrichment.csv: 25 enrichment rows
- deals file: not provided

Because no deals data was provided, I cannot calculate deal-field completeness or pipeline amount at stake.

1. Completeness by field

Deals:
- owner: cannot calculate; no deals data provided
- stage: cannot calculate; no deals data provided
- amount: cannot calculate; no deals data provided
- close date: cannot calculate; no deals data provided
- why-buys: cannot calculate; no deals data provided

Companies, denominator = 34:
- industry: 34 / 34 = 100.0%
- employee_count: 25 / 34 = 73.5%
- hq_country: 28 / 34 = 82.4%

Contacts, denominator = 52:
- email present: 52 / 52 = 100.0%
- title present: 39 / 52 = 75.0%
- persona present: 37 / 52 = 71.2%

Email quality note:
- valid email format: 48 / 52 = 92.3%
- invalid email format: 4 / 52 = 7.7%

2. Duplicate company clusters

Duplicate logic used: shared domain. No company name field was provided, so name-variant matching cannot be performed beyond the aliases/domains given.

Cluster: acme-corp.com
- C-0A092931: domain = acme-corp.com, industry = Technology, employee_count = 500, hq_country = US
- C-0A092932: domain = acme-corp.com, industry = tech, employee_count = 510, hq_country = USA
- Survivor: C-0A092931
- Rationale: both are 3 / 3 complete; C-0A092931 has the cleaner industry value. Employee count conflicts, 500 vs 510, and there is no enrichment row for acme-corp.com, so do not invent the correct value.

Cluster: globex.io
- C-0A092933: domain = globex.io, industry = SaaS, employee_count = 200, hq_country = US
- C-0A092934: domain = globex.io, industry = Technology, employee_count = 200, hq_country = US
- Survivor: C-0A092933
- Rationale: both are 3 / 3 complete; employee_count and hq_country agree. C-0A092933 has the more specific industry value, SaaS. There is no enrichment row for globex.io, so do not overwrite without a source decision.

3. Invalid emails

Invalid email records:
- CT-0010, company_alias = C-66D1FC, email = user0@
- CT-0080, company_alias = C-92D97D, email = user0@
- CT-0081, company_alias = C-92D97D, email = user1@
- CT-0192, company_alias = C-425E2A, email = user2@

Arithmetic:
- total contacts = 52
- invalid emails = 4
- valid emails = 52 - 4 = 48
- valid email rate = 48 / 52 = 92.3%

4. Domain mismatches

Email-domain mismatch:
- CT-0011, company_alias = C-66D1FC
  - email = user1@other-domain.com
  - email domain = other-domain.com
  - contact domain = 66d1fc.com
  - linked company domain = 66d1fc.com
  - mismatch = other-domain.com vs 66d1fc.com

Contact domain vs linked company domain:
- 0 mismatches found
- arithmetic: 52 / 52 contact domain values match the linked company domain = 100.0%

5. Missing company fields that can be filled from enrichment

Only fields with a matching enrichment row and a nonblank enrichment value should be filled.

Safe fills:
- C-EC3025, ec3025.com: employee_count blank -> 400
- C-96039F, 96039f.com: employee_count blank -> 400
- C-44EA29, 44ea29.com: employee_count blank -> 400
- C-D04904, d04904.com: employee_count blank -> 400
- C-B23205, b23205.com: employee_count blank -> 400
- C-60C75F, 60c75f.com: employee_count blank -> 400
- C-7BBDFA, 7bbdfa.com: employee_count blank -> 400
- C-50D386, 50d386.com: employee_count blank -> 400

Arithmetic:
- employee_count missing before fills = 9
- fillable employee_count blanks = 8
- employee_count still missing after safe fills = 1, C-93C8BF
- employee_count completeness after safe fills = 33 / 34 = 97.1%

Company fields still missing because enrichment is blank or no enrichment row exists:
- C-2D1F1B, 2d1f1b.com: hq_country blank in CRM; hq_country blank in enrichment
- C-D73B89, d73b89.com: hq_country blank in CRM; hq_country blank in enrichment
- C-44EA29, 44ea29.com: hq_country blank in CRM; hq_country blank in enrichment
- C-D04904, d04904.com: hq_country blank in CRM; hq_country blank in enrichment
- C-2C60E5, 2c60e5.com: hq_country blank in CRM; hq_country blank in enrichment
- C-93C8BF, 93c8bf.com: employee_count blank in CRM; no matching enrichment row
- C-EE9FFB, ee9ffb.com: hq_country blank in CRM; no matching enrichment row

6. CRM vs enrichment disagreements

These are exact-value disagreements where both CRM and enrichment have nonblank values.

- C-66D1FC, 66d1fc.com, industry:
  - CRM = tech
  - enrichment = Computer Software
  - recommend: enrichment, for standardized industry taxonomy

- C-66D1FC, 66d1fc.com, hq_country:
  - CRM = US
  - enrichment = United States
  - recommend: enrichment, for standardized country formatting

- C-950043, 950043.com, hq_country:
  - CRM = US
  - enrichment = United States
  - recommend: enrichment, for standardized country formatting

- C-EC3025, ec3025.com, industry:
  - CRM = Technology
  - enrichment = Computer Software
  - recommend: enrichment, for standardized industry taxonomy

- C-EC3025, ec3025.com, hq_country:
  - CRM = USA
  - enrichment = United States
  - recommend: enrichment, for standardized country formatting

- C-96039F, 96039f.com, hq_country:
  - CRM = USA
  - enrichment = United States
  - recommend: enrichment, for standardized country formatting

- C-44EA29, 44ea29.com, industry:
  - CRM = tech
  - enrichment = Computer Software
  - recommend: enrichment, for standardized industry taxonomy

- C-92D97D, 92d97d.com, industry:
  - CRM = Technology
  - enrichment = Computer Software
  - recommend: enrichment, for standardized industry taxonomy

- C-D04904, d04904.com, industry:
  - CRM = Technology
  - enrichment = Computer Software
  - recommend: enrichment, for standardized industry taxonomy

- C-77A95A, 77a95a.com, industry:
  - CRM = Technology
  - enrichment = Computer Software
  - recommend: enrichment, for standardized industry taxonomy

- C-77A95A, 77a95a.com, hq_country:
  - CRM = US
  - enrichment = United States
  - recommend: enrichment, for standardized country formatting

- C-AA8DDA, aa8dda.com, industry:
  - CRM = Technology
  - enrichment = Computer Software
  - recommend: enrichment, for standardized industry taxonomy

- C-B23205, b23205.com, hq_country:
  - CRM = US
  - enrichment = United States
  - recommend: enrichment, for standardized country formatting

- C-E51FB7, e51fb7.com, hq_country:
  - CRM = USA
  - enrichment = United States
  - recommend: enrichment, for standardized country formatting

- C-D0662E, d0662e.com, hq_country:
  - CRM = US
  - enrichment = United States
  - recommend: enrichment, for standardized country formatting

- C-B25F40, b25f40.com, industry:
  - CRM = Technology
  - enrichment = Computer Software
  - recommend: enrichment, for standardized industry taxonomy

- C-60C75F, 60c75f.com, industry:
  - CRM = tech
  - enrichment = Computer Software
  - recommend: enrichment, for standardized industry taxonomy

- C-425E2A, 425e2a.com, industry:
  - CRM = Tech 
  - enrichment = Computer Software
  - recommend: enrichment, for standardized industry taxonomy

- C-425E2A, 425e2a.com, hq_country:
  - CRM = USA
  - enrichment = United States
  - recommend: enrichment, for standardized country formatting

- C-2D7423, 2d7423.com, hq_country:
  - CRM = USA
  - enrichment = United States
  - recommend: enrichment, for standardized country formatting

7. Proposed fixes

Company fixes:
- Fill 8 missing employee_count values from enrichment:
  - C-EC3025 = 400
  - C-96039F = 400
  - C-44EA29 = 400
  - C-D04904 = 400
  - C-B23205 = 400
  - C-60C75F = 400
  - C-7BBDFA = 400
  - C-50D386 = 400
- Do not fill C-93C8BF employee_count; no matching enrichment row.
- Do not fill missing hq_country values where enrichment is blank or absent.
- Standardize hq_country values where enrichment confirms United States.
- Standardize tech / Technology / Tech  values to Computer Software where enrichment confirms Computer Software.
- Resolve duplicate cluster acme-corp.com with survivor C-0A092931; do not invent employee_count because 500 vs 510 conflicts.
- Resolve duplicate cluster globex.io with survivor C-0A092933; do not overwrite industry without confirming whether SaaS or Technology should be the CRM taxonomy value.

Contact fixes:
- Correct invalid emails:
  - CT-0010
  - CT-0080
  - CT-0081
  - CT-0192
- Investigate email-domain mismatch:
  - CT-0011
- Do not fill missing titles or personas from the provided data; no contact enrichment file was provided.

8. 10 fixes with the most pipeline amount at stake

Cannot rank fixes by pipeline amount at stake because no deals data, deal aliases, deal-company mappings, or deal amounts were provided.

The 10 concrete fixes identifiable from the provided data are below, but pipeline amount at stake is unavailable for every row:

1. Resolve duplicate company cluster acme-corp.com: C-0A092931 / C-0A092932
   - pipeline amount at stake: cannot calculate; no deals data provided

2. Resolve duplicate company cluster globex.io: C-0A092933 / C-0A092934
   - pipeline amount at stake: cannot calculate; no deals data provided

3. Fix invalid email CT-0010, company_alias = C-66D1FC, email = user0@
   - pipeline amount at stake: cannot calculate; no deals data provided

4. Investigate domain mismatch CT-0011, company_alias = C-66D1FC, email = user1@other-domain.com vs domain = 66d1fc.com
   - pipeline amount at stake: cannot calculate; no deals data provided

5. Fix invalid email CT-0080, company_alias = C-92D97D, email = user0@
   - pipeline amount at stake: cannot calculate; no deals data provided

6. Fix invalid email CT-0081, company_alias = C-92D97D, email = user1@
   - pipeline amount at stake: cannot calculate; no deals data provided

7. Fix invalid email CT-0192, company_alias = C-425E2A, email = user2@
   - pipeline amount at stake: cannot calculate; no deals data provided

8. Fill C-EC3025 employee_count from enrichment: blank -> 400
   - pipeline amount at stake: cannot calculate; no deals data provided

9. Fill C-96039F employee_count from enrichment: blank -> 400
   - pipeline amount at stake: cannot calculate; no deals data provided

10. Fill C-44EA29 employee_count from enrichment: blank -> 400
   - pipeline amount at stake: cannot calculate; no deals data provided

Data limitations:
- No deal amount field is provided, so all deal amounts are missing.
- No company aliases are provided, only deal aliases.

Candidate classifications:

| Deal alias | Amount | Prospect line | Product-doc basis | Classification |
|---|---:|---|---|---|
| Deal-EC3025 | Missing | “We need SCIM user provisioning — our security team will not approve any tool that requires manual account management.” | Docs state: “SCIM user provisioning and ADP Workforce Now integrations are NOT currently listed as supported capabilities.” | Real gap |
| Deal-D0D6B5 | Missing | “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 state: “SCIM user provisioning and ADP Workforce Now integrations are NOT currently listed as supported capabilities.” | Real gap |
| Deal-CFE7F4 | Missing | “I tried to build a custom report combining recognition frequency with turnover and couldn't — is that possible on our current plan?” | Docs show “Custom report builder” is available only on Enterprise. | Plan gate |
| Deal-84DBA6 | Missing | “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.” | Docs state Slack integration is supported on all plans. The issue is training/adoption. | Rollout/enablement issue |

Excluded:
- Deal-36C33F: Rep said, “we don't have a native mobile app for hourly workers yet,” but rep language does not count as prospect voice. The prospect said: “Good to know. The web version should be fine for our office staff for now.” This is not a prospect-raised product gap.

Arithmetic:
- Prospect lines reviewed: 5
- Candidate prospect-raised issues: 4
- Real gaps: 2
- Plan gates: 1
- Rollout/enablement issues: 1
- Excluded because not prospect-raised gap: 1

Real gap rate among candidate prospect-raised issues:
- 2 / 4 = 50%

Real gap rate among all prospect lines reviewed:
- 2 / 5 = 40%

Summary: true product gaps only

1. Deal-EC3025 — Amount: Missing
   - Gap: SCIM user provisioning
   - Prospect quote: “We need SCIM user provisioning — our security team will not approve any tool that requires manual account management.”

2. Deal-D0D6B5 — Amount: Missing
   - Gap: ADP Workforce Now integration
   - Prospect quote: “Our payroll runs on ADP Workforce Now and I don't see ADP anywhere in your integration list — that's a dealbreaker for us.”

Lead in first five minutes:
- Main pattern: Alex Franklin leads with the 400-person retailer proof story in 8 of 10 calls: Deal-D348E1, Deal-5408B0, Deal-547B2B, Deal-C61CF7, Deal-60C2C2, Deal-EDC141, Deal-D9A12F, Deal-84DBA6.
- Arithmetic: 8 / 10 = 80%.
- Quote: “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.”
- Exceptions: Deal-403845 leads with security/pricing agenda; Deal-1E2498 leads with straight pricing. Arithmetic: 2 / 10 = 20%.

Three most common objections and handling:

1. Budget locked until next fiscal year
- Deals: Deal-D348E1, Deal-547B2B, Deal-60C2C2, Deal-84DBA6.
- Arithmetic: 4 / 10 = 40%.
- Handling: reframes spend as fundable from turnover savings, citing $210k in avoided backfills.
- Quote: “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.”

2. Revisit next quarter / timing pressure
- Deals: Deal-5408B0, Deal-C61CF7, Deal-D9A12F.
- Arithmetic: 3 / 10 = 30%.
- Handling: proposes a 90-day one-department pilot to create internal data before planning.
- Quote: “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 / quarterly gift card process
- Deals: Deal-403845, Deal-EDC141, Deal-1E2498.
- Arithmetic: 3 / 10 = 30%.
- Handling: contrasts manual process with automated milestones and recognition analytics.
- Quote: “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:
- Agreed in 7 calls: Deal-D348E1, Deal-5408B0, Deal-547B2B, Deal-C61CF7, Deal-60C2C2, Deal-D9A12F, Deal-1E2498.
- Not agreed in 3 calls: Deal-403845, Deal-EDC141, Deal-84DBA6.
- Arithmetic: 7 / 10 = 70%.
- Quote: “Yes, Thursday at 2pm works — send the invite and I'll bring our HRIS manager.”

Competitors prospects raised:
- Awardco: Deal-547B2B.
  Quote: “We're also in late talks with Awardco — their rewards catalog looks bigger than yours.”
- Kudos: Deal-EDC141.
  Quote: “How are you different from Kudos? Our CEO used them at her last company.”
- Workhuman is not counted because it was raised by Alex Franklin, not by a prospect, in Deal-C61CF7.

Coaching notes:
1. Keep leading with the retailer proof story: it appears in 8 / 10 calls and is present in 6 of the 7 calls with agreed next steps.
2. Improve late-stage next-step control: committee/no-urgency stalls in Deal-403845, Deal-EDC141, and Deal-84DBA6 produced 0 / 3 agreed next steps.

Last completed month: 2026-08

Redemption section through 2026-08:
- Redemption count: 378
- Spend: $27,846.00
- Unique redeemers: 236
- Redemptions per redeemer: 378 / 236 = 1.6017 = 1.60

Spend arithmetic:
- TangoCard: $3,230.00
- Tremendous: $8,505.00
- custom: $10,873.00
- Snappy: $5,238.00
- Total spend: $3,230.00 + $8,505.00 + $10,873.00 + $5,238.00 = $27,846.00

Provider mix, percent 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%

Provider share sum: 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

Total tickets: 80
ARR affected calculation: sum each distinct account’s ARR once per theme.

Broad patterns ranked by ARR exposure:

1. HRIS provisioning / sync failures
- Count: 12
- Share: 12 / 80 = 15.0%
- Distinct accounts: 3 — C-0B2213A9, C-0F6C0F34, C-0DDFC9A7
- ARR affected: $36,000 + $30,000 + $48,000 = $114,000
- Ticket ids: IC-460059, IC-460062
- Recommendation: Prioritize HRIS sync/provisioning fixes and add alerting for silent skipped-new-hire failures.

2. Redemption / gift card checkout failures
- Count: 18
- Share: 18 / 80 = 22.5%
- Distinct accounts: 7 — C-0CEF69FD, C-0B827671, C-0FCCD2DF, C-0F876796, C-14264ABD, C-0D9CA315, C-0B0F1BAB
- ARR affected: $8,900 + $10,700 + $9,600 + $8,700 + $11,000 + $9,600 + $10,300 = $68,800
- Ticket ids: IC-460025, IC-460024
- Recommendation: Treat failed redemptions with deducted points as a cross-account product incident and add automated refund/retry handling.

3. Recognition points not posting / balances not updating
- Count: 20
- Share: 20 / 80 = 25.0%
- Distinct accounts: 9 — C-0D3278C7, C-0BF20542, C-0D0B047C, C-0BE96399, C-0D284E42, C-0D6CC8E3, C-21FEBCBB, C-0DD0626C, C-0B2895EF
- ARR affected: $3,500 + $4,500 + $4,500 + $2,700 + $3,400 + $4,200 + $2,900 + $2,500 + $2,900 = $31,100
- Ticket ids: IC-460004, IC-460016
- Recommendation: Investigate the recognition-to-points posting pipeline and proactively reconcile missing balances for affected accounts.

4. Slack integration / sync / auth / command failures
- Count: 14
- Share: 14 / 80 = 17.5%
- Distinct accounts: 4 — C-0B843542, C-10A56B0F, C-0BA71F12, C-8C2E8F00
- ARR affected: $4,400 + $5,400 + $3,900 + $5,200 = $18,900
- Ticket ids: IC-460041, IC-460047
- Recommendation: Fix Slack auth persistence, recognition sync, and slash-command reliability before asking admins to re-authenticate.

Single-account noise:

5. Billing invoice / seat-count / tier-price errors
- Count: 16
- Share: 16 / 80 = 20.0%
- Distinct accounts: 1 — C-0E9C27D1
- ARR affected: $52,000 = $52,000
- Ticket ids: IC-460071, IC-460069
- Recommendation: Escalate C-0E9C27D1 to Finance/RevOps for account-specific billing reconciliation, but do not treat it as a broad product pattern without more affected accounts.

Quarter: Q3-2026. Days elapsed: 66 / 92 = 71.7%.

| Metric | QTD actual | Target | Delta vs target | Pace |
|---|---:|---:|---:|---|
| SQMs | 230 | 300 | -70 | ahead |
| SQOs | 84 | 120 | -36 | behind |
| DS2s | 40 | 75 | -35 | behind |
| Closed-lost MIA rate | 5 / 25 = 20.0% | 10.0% | +10.0 pp | behind |
| Same-quarter closes | 10 | 20 | -10 | behind |
| Active pipeline coverage against target | $3,000,000 / $4,000,000 = 75.0% | 100.0% | -25.0 pp; -$1,000,000 | ahead |

Arithmetic:
SQMs: 230 / 300 = 76.7%; 76.7% vs 71.7% elapsed = ahead.
SQOs: 84 / 120 = 70.0%; 70.0% vs 71.7% elapsed = behind.
DS2s: 40 / 75 = 53.3%; 53.3% vs 71.7% elapsed = behind.
Closed-lost MIA rate: 5 / 25 = 20.0%; target is 10.0%, lower is better, so 20.0% - 10.0% = +10.0 pp = behind.
Same-quarter closes: 10 / 20 = 50.0%; 50.0% vs 71.7% elapsed = behind.
Active pipeline coverage: $3,000,000 / $4,000,000 = 75.0%; 75.0% vs 71.7% elapsed = ahead.

What moved this week: The provided data includes only QTD actuals, targets, and quarter timing. It does not include prior-week values or week-over-week changes, so what moved this week cannot be calculated from the data provided.

| item_id | Vendor response |
|---|---|
| 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. [P2] |
| Q4 | Customer data is retained for the duration of the contract plus 90 days, then deleted from production systems. Arithmetic: contract termination date + 90 days = production deletion date. [P3] |
| Q5 | The current subprocessor list is maintained 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. Arithmetic: 1 backup cadence per day × 35 days retention = 35-day backup retention window. [P6] |
| Q8 | Unanswerable from the provided excerpts. None of [P1]-[P8] states whether Bonusly holds ISO 27001 certification. An ISO 27001 certificate or compliance certifications document would answer this. |
| Q9 | Unanswerable from the provided excerpts. None of [P1]-[P8] states a contractual uptime SLA percentage. A Service Level Agreement or Master Services Agreement would answer this. |
| Q10 | Unanswerable from the provided excerpts. None of [P1]-[P8] states whether Bonusly will sign a HIPAA Business Associate Agreement. A HIPAA/BAA policy, BAA template, or contracting/legal terms document would answer this. |

NDA-1 — [PARTY A] and Bonusly — GREEN: “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”; standard mutual NDA with standard carve-outs, Delaware law, no exclusivity, and term arithmetic of 2 years + 3-year survival = 5 years maximum if terminated at end of term.

NDA-2 — [PARTY B] and Bonusly — YELLOW: “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”; counsel review needed because the NDA embeds a non-solicit/no-hire restriction, with arithmetic of 3-year term + 18-month tail = 4.5 years.

NDA-3 — [PARTY C] and Bonusly — RED: “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”; full legal review needed because it includes a 3-year non-compete, one-way confidentiality favoring [PARTY C], “No confidentiality carve-outs are stated in this Agreement,” and governing law/jurisdiction is the “Republic of Ireland.”