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 Report

## Completeness Percentages

| Entity | Field | Filled | Total | % |
|--------|-------|--------|-------|---|
| Company | industry | 34 | 34 | 100.0% |
| Company | employee_count | 25 | 34 | 73.5% |
| Company | hq_country | 28 | 34 | 82.4% |
| Contact | email | 52 | 52 | 100.0% |
| Contact | title | 39 | 52 | 75.0% |
| Contact | persona | 37 | 52 | 71.2% |
| Deal | owner | - | - | **MISSING FILE** |
| Deal | stage | - | - | **MISSING FILE** |
| Deal | amount | - | - | **MISSING FILE** |
| Deal | close_date | - | - | **MISSING FILE** |
| Deal | why_buys | - | - | **MISSING FILE** |

---

## Duplicate Company Clusters

### Cluster 1: acme-corp.com
- C-0A092931: industry=Technology, employee_count=500, hq_country=US
- C-0A092932: industry=tech, employee_count=510, hq_country=USA
- **Survivor: C-0A092931** (most complete record)

### Cluster 2: globex.io
- C-0A092933: industry=SaaS, employee_count=200, hq_country=US
- C-0A092934: industry=Technology, employee_count=200, hq_country=US
- **Survivor: C-0A092933** (most complete record)

---

## Invalid Emails (4 records)

| contact_key | company_alias | email | Issue |
|-------------|---------------|-------|-------|
| CT-0010 | C-66D1FC | user0@ | Missing domain |
| CT-0080 | C-92D97D | user0@ | Missing domain |
| CT-0081 | C-92D97D | user1@ | Missing domain |
| CT-0192 | C-425E2A | user2@ | Missing domain |

---

## Domain Mismatches (5 records)

| contact_key | company_alias | email | contact_domain | Issue |
|-------------|---------------|-------|----------------|-------|
| CT-0010 | C-66D1FC | user0@ | 66d1fc.com | Empty email |
| CT-0011 | C-66D1FC | user1@other-domain.com | 66d1fc.com | **Wrong domain** |
| CT-0080 | C-92D97D | user0@ | 92d97d.com | Empty email |
| CT-0081 | C-92D97D | user1@ | 92d97d.com | Empty email |
| CT-0192 | C-425E2A | user2@ | 425e2a.com | Empty email |

---

## Fill Missing Company Fields from Enrichment

Only fill where CRM is empty AND enrichment has a matching row:

| company_alias | domain | field | CRM value | ZI value | Action |
|---------------|--------|-------|-----------|----------|--------|
| C-EC3025 | ec3025.com | employee_count | (empty) | 400 | Fill from ZI |
| C-96039F | 96039f.com | employee_count | (empty) | 400 | Fill from ZI |
| C-44EA29 | 44ea29.com | employee_count | (empty) | 400 | Fill from ZI |
| C-D04904 | d04904.com | employee_count | (empty) | 400 | Fill from ZI |
| C-B23205 | b23205.com | employee_count | (empty) | 400 | Fill from ZI |
| C-60C75F | 60c75f.com | employee_count | (empty) | 400 | Fill from ZI |
| C-7BBDFA | 7bbdfa.com | employee_count | (empty) | 400 | Fill from ZI |
| C-50D386 | 50d386.com | employee_count | (empty) | 400 | Fill from ZI |

---

## CRM vs Enrichment Disagreements

Where both CRM and enrichment have values but they differ:

| company_alias | domain | field | CRM | ZI | Recommendation |
|---------------|--------|-------|-----|----|----------------|
| C-66D1FC | 66d1fc.com | hq_country | US | United States | Standardize to ZI |
| C-950043 | 950043.com | hq_country | US | United States | Standardize to ZI |
| C-EC3025 | ec3025.com | hq_country | USA | United States | Standardize to ZI |
| C-96039F | 96039f.com | hq_country | USA | United States | Standardize to ZI |
| C-77A95A | 77a95a.com | hq_country | US | United States | Standardize to ZI |
| C-B23205 | b23205.com | hq_country | US | United States | Standardize to ZI |
| C-E51FB7 | e51fb7.com | hq_country | USA | United States | Standardize to ZI |
| C-D0662E | d0662e.com | hq_country | US | United States | Standardize to ZI |
| C-425E2A | 425e2a.com | hq_country | USA | United States | Standardize to ZI |
| C-2D7423 | 2d7423.com | hq_country | USA | United States | Standardize to ZI |

**Recommendation:** Standardize all country values to "United States" (ZI standard format). US/USA/USA are the same country — the disagreement is purely formatting.

---

## 10 Fixes with Most Pipeline at Stake

**CANNOT CALCULATE** — No deals.csv file was provided. Pipeline analysis requires deal amounts, owners, and stages to prioritize fixes by revenue impact.

**Workaround:** Once deals.csv is available, join deals to companies via company_alias and sum amount by:
- Companies with missing fields that can be filled from enrichment
- Duplicate company clusters that need merging
- Contacts with invalid emails that block outreach

---

## Summary of Available Fixes

| Fix Type | Count | Priority |
|----------|-------|----------|
| Fill employee_count from ZI | 8 | High |
| Standardize hq_country to "United States" | 10 | Medium |
| Fix invalid emails (empty domains) | 4 | High |
| Fix domain mismatch (CT-0011) | 1 | High |
| Merge duplicate company clusters | 2 | Medium |

## Analysis of Prospect-Raised Product Gaps

| Transcript | Prospect Quote | Classification | Deal | Amount |
|---|---|---|---|---|
| TG-001 | "We need SCIM user provisioning — our security team will not approve any tool that requires manual account management." | **REAL GAP** — SCIM user provisioning not listed as supported in product docs | Deal-EC3025 | *[not provided]* |
| TG-002 | "Our payroll runs on ADP Workforce Now and I don't see ADP anywhere in your integration list — that's a dealbreaker for us." | **REAL GAP** — ADP Workforce Now integration not listed as supported in product docs | Deal-D0D6B5 | *[not provided]* |
| TG-003 | "I tried to build a custom report combining recognition frequency with turnover and couldn't — is that possible on our current plan?" | **Plan Gate** — Custom report builder exists but requires Enterprise tier (docs: "Custom report builder — yes" for Enterprise only) | Deal-CFE7F4 | *[not provided]* |
| TG-004 | "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." | **Rollout/Enablement Issue** — Slack integration is available on all plans; issue is training, not product capability | Deal-84DBA6 | *[not provided]* |
| TG-005 | (Prospect response to Alex's disclosure about no mobile app) "Good to know. The web version should be fine for our office staff for now." | **Not a gap** — Prospect accepted limitation; also, the gap came from Alex, not prospect | Deal-36C33F | *[not provided]* |

---

## Summary: Real Product Gaps

1. **SCIM User Provisioning** — cited by Deal-EC3025 prospect
   - Prospect quote: *"We need SCIM user provisioning — our security team will not approve any tool that requires manual account management."*

2. **ADP Workforce Now Integration** — cited by Deal-D0D6B5 prospect
   - 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."*

---

**Note:** Deal amounts were not provided in the source data.

## Call Analysis: Alex Franklin (10 calls)

### Lead (first 5 minutes)

| Call | Lead |
|------|------|
| 8 calls | "Quick one to kick off: a 400-person retailer we work with cut regretted turnover 18% in two quarters after automating milestone awards..." |
| TT-004 | "I put together a short agenda — security review first, then pricing." |
| TT-009 | "You asked for straight pricing last time, so let's start there." |

**Finding:** 8/10 calls open with the same retailer case study. Two calls deviate (agenda-driven, pricing-driven).

---

### Three Most Common Objections & Responses

**Objection 1 — Budget locked until next fiscal year** (4 calls: TT-001, TT-003, TT-006, TT-010)
> "Honestly, budget is locked until next fiscal year — I can't add a new line item right now."

**Response:**
> "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."

---

**Objection 2 — Revisit next quarter / open enrollment** (3 calls: TT-002, TT-005, TT-008)
> "This is good, but can we revisit it next quarter? Open enrollment starts in October and we're underwater."

**Response:**
> "Makes sense. What if we scope a 90-day pilot with one department so you have internal data before next quarter's planning?"

---

**Objection 3 — Already using spreadsheets/gift cards** (3 calls: TT-004, TT-007, TT-009)
> "We already do recognition with a spreadsheet and quarterly gift cards — why would we change?"

**Response:**
> "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."

---

### Next Step Agreement Rate

| Call | Next Step Locked? |
|------|-------------------|
| TT-001 | Yes |
| TT-002 | Yes |
| TT-003 | Yes |
| TT-004 | No (Alex withdrew) |
| TT-005 | Yes |
| TT-006 | Yes |
| TT-007 | No ("I need to think about it") |
| TT-008 | Yes |
| TT-009 | Yes |
| TT-010 | No ("I can't commit to anything today") |

**Rate: 7/10 = 70%**

---

### Competitors Raised by Prospects

| Deal | Competitor |
|------|------------|
| TT-003 (Deal-547B2B) | Awardco |
| TT-007 (Deal-EDC141) | Kudos |

---

### Two Coaching Notes

1. **Objection handling is consistent but reactive.** Alex has solid pivots (turnover savings, pilot scope, analytics value), yet he never pushes back on the "budget locked" objection with a direct question — e.g., "What's one thing that would make this worth exploring before fiscal year?" This could surface buying signals or real constraints.

2. **Lead variety is low.** 80% of calls open with identical case study language. TT-009 proves he can adapt ("You asked for straight pricing"), yet defaults to the retailer story. Testing two or three opening angles based on prospect signals (prior conversation, company size, industry) would likely increase engagement.

Last completed month: **August 2026**

---

**REDEMPTION METRICS (through 2026-08)**
- Redemption count: **48**
- Total spend: **$3,536.00**
- Unique redeemers: **46**
- Redemptions per redeemer: **1.04** (48 ÷ 46)

---

**PROVIDER MIX (% of spend)**
| Provider   | % of Spend |
|------------|------------|
| Tremendous | 32.4%      |
| custom     | 29.9%      |
| Snappy     | 23.6%      |
| TangoCard  | 14.1%      |
| **TOTAL**  | **100.0%** |

---

**TOP 5 COUNTRIES BY REDEMPTIONS**
| Country | Redemptions |
|---------|-------------|
| US      | 31          |
| CA      | 7           |
| GB      | 2           |
| SG      | 2           |
| AU      | 2           |

---

**Arithmetic check:**
- 48 redemptions ÷ 46 unique users = 1.04 redemptions per user
- $1,145 + $1,057 + $834 + $500 = $3,536 total
- 32.4% + 29.9% + 23.6% + 14.1% = 100.0%

Now I have the clear picture. Let me synthesize this properly, separating single-account noise from broad patterns:

**QUARTERLY SUPPORT TICKET THEMES (Q2-Q3 2026)**

Total: 80 tickets | 24 accounts | $1,598,900 ARR portfolio

---

**1. HRIS/PROVISIONING FAILURES**
- **Count:** 12 (15% of tickets)
- **Share:** 15.0%
- **Distinct accounts:** 3
- **ARR affected:** $114,000 (7.1% of portfolio)
- **Ticket IDs:** IC-460059, IC-460055
- **Accounts:** C-0B2213A9 ($36K), C-0F6C0F34 ($30K), C-0DDFC9A7 ($48K)
- **Recommendation:** Investigate HRIS sync logic — three mid-market accounts blocked on new hire provisioning for 3+ months. Risk of churn escalation.

---

**2. GIFT CARD/REDEMPTION FAILURES**
- **Count:** 14 (17.5%)
- **Share:** 17.5%
- **Distinct accounts:** 7
- **ARR affected:** $68,800 (4.3%)
- **Ticket IDs:** IC-460024, IC-460035
- **Recommendation:** Audit gift card fulfillment pipeline — points deducted but rewards never delivered across 7 accounts.

---

**3. POINTS NOT POSTING**
- **Count:** 20 (25%)
- **Share:** 25.0%
- **Distinct accounts:** 9
- **ARR affected:** $31,100 (1.9%)
- **Ticket IDs:** IC-460004, IC-460016
- **Recommendation:** Root-cause recognition credit timing issue — affects 9 accounts broadly.

---

**4. SLACK INTEGRATION FAILURES**
- **Count:** 14 (17.5%)
- **Share:** 17.5%
- **Distinct accounts:** 4
- **ARR affected:** $18,900 (1.2%)
- **Ticket IDs:** IC-460041, IC-460047
- **Recommendation:** Fix Slack sync toggle persistence — auth token refresh or permission drift.

---

**5. BILLING/INVOICE ERRORS — SINGLE-ACCOUNT NOISE**
- **Count:** 16 (20%)
- **Share:** 20.0%
- **Distinct accounts:** 1 (C-0E9C27D1)
- **ARR affected:** $52,000 (3.3%)
- **Ticket IDs:** IC-460071, IC-460069
- **Recommendation:** Account-specific billing config issue — C-0E9C27D1 has recurring seat count mismatch (charged 200 vs. licensed 150). Escalate to accounting for manual reconciliation.

---

**SUMMARY:**

| Theme | Count | Accounts | ARR | Type |
|-------|-------|----------|-----|------|
| HRIS/Provisioning | 12 | 3 | $114K | Broad pattern |
| Gift Card Failures | 14 | 7 | $68.8K | Broad pattern |
| Points Not Posting | 20 | 9 | $31.1K | Broad pattern |
| Slack Integration | 14 | 4 | $18.9K | Broad pattern |
| Billing/Invoice | 16 | 1 | $52K | Single-account noise |

Broad patterns (4 themes, 50 tickets, $232.8K ARR) ranked by ARR exposure. Billing/Invoice isolated as single-account noise — 16 tickets from C-0E9C27D1 alone represent 20% of volume but only 3.3% of portfolio ARR.

## Q3-2026 Weekly Marketing Goals Update

### Performance Summary

| Metric | QTD Actual | Target | Delta | Pace |
|--------|-----------|--------|-------|------|
| SQMs | 230 | 300 | -70 | **Ahead** (230 vs 215 expected) |
| SQOs | 84 | 120 | -36 | Behind (84 vs 86 expected) |
| DS2s | 40 | 75 | -35 | Behind (40 vs 54 expected) |
| Closed-Lost MIA Rate | 20% | 10% | +10pp | Behind (20% vs 10% expected) |
| Same-Quarter Closes | 10 | 20 | -10 | Behind (10 vs 14 expected) |
| Active Pipeline | $3.0M | $4.0M | -$1.0M | **Ahead** ($3.0M vs $2.87M expected) |

### Calculations

**Pace formula:** Expected = Target × (Days Elapsed ÷ Days in Quarter) = Target × (66 ÷ 92) = Target × 0.7174

- **SQMs:** 230 actual vs 215 expected → **AHEAD** by 15 units
- **SQOs:** 84 actual vs 86 expected → **BEHIND** by 2 units  
- **DS2s:** 40 actual vs 54 expected → **BEHIND** by 14 units
- **MIA Rate:** (5 MIA ÷ 25 total closed-lost) = 20% vs 10% target → **BEHIND** (lower is better)
- **Same-Quarter Closes:** 10 actual vs 14 expected → **BEHIND** by 4 units
- **Active Pipeline:** $3.0M actual vs $2.87M expected → **AHEAD** by ~$130K

### What Moved This Week

I cannot determine week-over-week movement from the provided data — the files contain only quarter-to-date totals, not prior week snapshots. To report what moved this week, I would need either a previous week's snapshot or a delta field tracking week-over-week changes.

# Security & Compliance Questionnaire Responses

**Q1: Is customer data encrypted at rest? If so, how?**
Yes. All customer data is encrypted at rest using AES-256. [P1]

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

**Q3: Do you hold a SOC 2 report, and can we obtain a copy?**
Yes. Bonusly maintains a SOC 2 Type II report, renewed annually. The report is available to prospects under NDA. [P2]

**Q4: How long is customer data retained after contract termination?**
Customer data is retained for the duration of the contract plus 90 days, after which it is deleted from production systems. [P3]

**Q5: Where is your subprocessor list published and how are changes notified?**
The subprocessor list is maintained at trust.bonusly.com. Customers receive 30 days notice before a new subprocessor is added. [P4]

**Q6: Do you support SAML single sign-on?**
Yes. SAML 2.0 single sign-on is available on the Enterprise plan. [P5]

**Q7: What is your production backup schedule and retention?**
Production databases are backed up daily. Backups are encrypted and retained for 35 days. [P6]

**Q8: Do you hold an ISO 27001 certification?**
Unanswerable from the provided excerpts. This information would be found in the formal certification portfolio or trust documentation.

**Q9: What is your contractual uptime SLA percentage?**
Unanswerable from the provided excerpts. This information would be found in the Master Services Agreement (MSA) or SLA documentation.

show the model's full answer

## NDA Triage Results

---

### NDA-1 — [PARTY A] and Bonusly

**Classification: GREEN**

Reasoning: Standard mutual NDA with no concerning provisions. Term (2 years), survival (3 years), carve-outs (publicly available, prior knowledge, third-party receipt, independent development, legal disclosure), and Delaware law are all market-standard. No non-solicit, non-compete, or exclusivity clauses.

---

### NDA-2 — [PARTY B] and Bonusly

**Classification: YELLOW**

Reasoning: Adds a **non-solicitation clause** (clause 4): *"neither party shall solicit for employment or hire any employee of the other party with whom it came into contact under this Agreement"* — 18 months post-term. The clause is narrowly scoped to employees "contacted under this Agreement," which limits risk, but the clause itself is a departure from standard NDAs and warrants counsel review to confirm the scope is acceptable.

---

### NDA-3 — [PARTY C] and Bonusly

**Classification: RED**

Reasoning: **Four critical issues:**

1. **One-way confidentiality** (clause 1) — Bonusly receives no protection; only Party C's information is protected.

2. **Non-compete clause** (clause 2): *"Recipient shall not...engage in or provide services to any business that competes with Discloser's business"* — 3-year term with **no geographic limitation**, **no customer/prospect restriction**, and **no carve-out for general employment**. This is overly broad and potentially enforceable against Bonusly employees.

3. **Missing carve-outs** — Clause 3 explicitly states *"No confidentiality carve-outs are stated in this Agreement."* This means information that becomes public, is independently developed, or received from third parties may still be deemed confidential — a significant liability.

4. **Governing law** (clause 3): Irish law — unusual for a US company (Bonusly), introduces unfamiliar legal jurisdiction and potential enforcement complexity.

This NDA requires full legal review before execution.