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 Extract Audit

**No deals/pipeline data provided.** The three files are companies.csv (35 rows), contacts.csv (42 rows), and zoominfo_enrichment.csv (26 rows). There is no deals.csv, opportunities.csv, or any file containing owner, stage, amount, close date, or why-buys fields. **"Pipeline amount at stake" cannot be computed** — the top-10-by-pipeline-amount section at the end will rank by deal count impacted instead, and I will say so explicitly.

---

## 1. Completeness % per field

### Companies (n=35)

| Field | Populated | Missing | % Complete |
|---|---|---|---|
| **industry** | 35 | 0 | **100.0%** |
| **employee_count** | 26 | 9 | **74.3%** |
| **hq_country** | 29 | 6 | **82.9%** |

Missing employee_count: C-EC3025, C-96039F, C-44EA29, C-D04904, C-B23205, C-60C75F, C-7BBDFA, C-50D386, C-93C8BF  
Missing hq_country: C-2D1F1B, C-D73B89, C-44EA29, C-D04904, C-2C60E5, C-EE9FFB

Industry is 100% populated but **not normalized** — 5 distinct forms: `Technology` (7), `tech` (3), `Tech ` (4, trailing space), `health care` (2, lowercase+space), `Healthcare` (3). This will cause segmentation failures.

### Contacts (n=42)

| Field | Populated | Empty | % Complete |
|---|---|---|---|
| **email** (field filled) | 42 | 0 | **100.0%** |
| **email** (valid) | 38 | 4 invalid | **90.5%** |
| **title** | 31 | 11 | **73.8%** |
| **persona** | 32 | 10 | **76.2%** |

Invalid emails (missing domain): CT-0010 `user0@`, CT-0080 `user0@`, CT-0081 `user1@`, CT-0192 `user2@`  
Missing titles: CT-0000, CT-0022, CT-0072, CT-0080, CT-0081, CT-0092, CT-0120, CT-0121, CT-0122, CT-0132, CT-0141  
Missing personas: CT-0000, CT-0022, CT-0041, CT-0060, CT-0070, CT-0081, CT-0082, CT-0092, CT-0110, CT-0132

### Deals — NO FILE PROVIDED
Owner, stage, amount, close date, why-buys: **0% completeness, no data exists.**

---

## 2. Duplicate company clusters

### Cluster A — acme-corp.com (shared domain)

| Alias | Domain | Industry | Emp | Country |
|---|---|---|---|---|
| C-0A092931 | acme-corp.com | Technology | 500 | US |
| C-0A092932 | acme-corp.com | tech | 510 | USA |

**Survivor: C-0A092931** — first entry, standard industry spelling, employee count 500 (lower of the two; keep conservative). Merge C-0A092932's 510 headcount as a note from a different data pull.

### Cluster B — globex.io (shared domain)

| Alias | Domain | Industry | Emp | Country |
|---|---|---|---|---|
| C-0A092933 | globex.io | SaaS | 200 | US |
| C-0A092934 | globex.io | Technology | 200 | US |

**Survivor: C-0A092934** — uses the standard industry taxonomy ("Technology" vs the less-standard "SaaS"). Employee counts agree (200). Flag C-0A092933 for deletion.

### Name-variant watch (different domains, same company possible)

| Aliases | Domains | Reason for suspicion |
|---|---|---|
| C-7BBDFA / C-50D386 | 7bbdfa.com / 50d386.com | Same non-normalized industry "health care" (lowercase, space), both Canada, both missing employee counts in CRM. Domains differ. **Not deduped** — no shared domain or name evidence; enrichment has separate rows for each. |

---

## 3. Invalid emails and domain mismatches

### Invalid emails (malformed — no domain after @)

| Contact | Company | Email |
|---|---|---|
| CT-0010 | C-66D1FC | `user0@` |
| CT-0080 | C-92D97D | `user0@` |
| CT-0081 | C-92D97D | `user1@` |
| CT-0192 | C-425E2A | `user2@` |

**Fix:** Append the contact's `domain` field to each: `user0@66d1fc.com`, `user0@92d97d.com`, `user1@92d97d.com`, `user2@425e2a.com`.

### Domain mismatch

| Contact | Company | Email domain | Declared domain | Issue |
|---|---|---|---|---|
| CT-0011 | C-66D1FC | `other-domain.com` | `66d1fc.com` | Email belongs to a different company. Either the email is wrong or the contact is assigned to the wrong company. |

**Fix:** Verify with the contact. If email is correct, reassign CT-0011 to the company owning `other-domain.com` (not in this CRM). If company is correct, the email is wrong — request the correct `@66d1fc.com` email.

---

## 4. Fill missing company fields from enrichment

**Matches found for 25 CRM domains in zoominfo_enrichment.csv** (9 CRM domains have no enrichment row: acme-corp.com, globex.io, 332637.com, 93c8bf.com, ee9ffb.com, c9bb20.com, ba969b.com, 2c60e5.com, b97b4e.com — wait, 2c60e5.com and b97b4e.com are in enrichment; let me recheck: enrichment has 2c60e5.com and b97b4e.com. So 7 CRM domains without enrichment: acme-corp.com, globex.io, 332637.com, 93c8bf.com, ee9ffb.com, ba969b.com, c9bb20.com.)

### Fill these CRM blanks from enrichment

| CRM Company | Missing Field | Enrichment Value | Action |
|---|---|---|---|
| C-EC3025 | employee_count | 400 | Fill from ZI |
| C-96039F | employee_count | 400 | Fill from ZI |
| C-44EA29 | employee_count, hq_country | 400, (empty) | Fill employee count; country stays blank |
| C-D04904 | employee_count, hq_country | 400, (empty) | Fill employee count; country stays blank |
| C-B23205 | employee_count | 400 | Fill from ZI |
| C-60C75F | employee_count | 400 | Fill from ZI |
| C-7BBDFA | employee_count | 400 | Fill from ZI |
| C-50D386 | employee_count | 400 | Fill from ZI |
| C-2D1F1B | hq_country | (empty in ZI too) | No source — leave blank |
| C-D73B89 | hq_country | (empty in ZI too) | No source — leave blank |
| C-2C60E5 | hq_country | (empty in ZI too) | No source — leave blank |
| C-EE9FFB | hq_country | (no enrichment row) | No source — leave blank |

### Disagreements (CRM value ≠ enrichment value, both populated)

| CRM Company | Field | CRM Says | Enrichment Says | Recommend |
|---|---|---|---|---|
| C-66D1FC | industry | `tech` | `Computer Software` | **Enrichment** — more specific, standard taxonomy |
| C-EC3025 | industry | `Technology` | `Computer Software` | **Enrichment** — specific sub-industry |
| C-44EA29 | industry | `tech` | `Computer Software` | **Enrichment** — standardize |
| C-92D97D | industry | `Technology` | `Computer Software` | **Enrichment** — more precise |
| C-D04904 | industry | `Technology` | `Computer Software` | **Enrichment** — more precise |
| C-77A95A | industry | `Technology` | `Computer Software` | **Enrichment** — more precise |
| C-AA8DDA | industry | `Technology` | `Computer Software` | **Enrichment** — more precise |
| C-B25F40 | industry | `Technology` | `Computer Software` | **Enrichment** — more precise |
| C-60C75F | industry | `tech` | `Computer Software` | **Enrichment** — standardize |
| C-425E2A | industry | `Tech ` (trailing space) | `Computer Software` | **Enrichment** — fix typo and standardize |
| C-0A092932 | industry | `tech` | (no enrichment row) | No source — keep `Technology` (from survivor) |
| C-0A092933 | industry | `SaaS` | (no enrichment row) | No source — merge into survivor's `Technology` |

**Country disagreements** are formatting only (US / USA / United States / Canada / UK) — semantically identical. No recommendation needed.

---

## 5. Top 10 fixes by deal count impacted (pipeline amount unavailable)

Since no deals/pipeline file was provided, fixes are ranked by **number of records they affect** (companies + contacts). This is the best proxy available.

| # | Fix | Records affected | Priority |
|---|---|---|---|
| 1 | **Dedupe acme-corp.com** — merge C-0A092932 into C-0A092931, survivor C-0A092931 | 1 company, 0 contacts | Deduplication |
| 2 | **Dedupe globex.io** — merge C-0A092933 into C-0A092934, survivor C-0A092934 | 1 company, 0 contacts | Deduplication |
| 3 | **Normalize industry values** — `tech`→`Technology`, `Tech `→`Technology`, `health care`→`Healthcare` across 9 companies | 9 companies | Data quality |
| 4 | **Fix 4 invalid emails** — append domain to `user0@`, `user1@`, `user2@` | 4 contacts | Reachability |
| 5 | **Fill employee_count from enrichment** — C-EC3025, C-96039F, C-44EA29, C-D04904, C-B23205, C-60C75F, C-7BBDFA, C-50D386 (8 companies) | 8 companies | Lead scoring |
| 6 | **Investigate CT-0011 domain mismatch** — email `user1@other-domain.com` doesn't match company domain `66d1fc.com` | 1 contact | Data integrity |
| 7 | **Fill missing titles** — 11 contacts need titles for persona-based outreach | 11 contacts | Outreach |
| 8 | **Fill missing personas** — 10 contacts need persona classification | 10 contacts | Segmentation |
| 9 | **Fill missing hq_country** — C-2D1F1B, C-D73B89, C-44EA29, C-D04904, C-2C60E5, C-EE9FFB (6 companies, 4 have no enrichment source) | 6 companies | Territory assignment |
| 10 | **Update CRM industry to Computer Software for 10 companies** — replace broad `Technology`/`tech` with enrichment's `Computer Software` | 10 companies | Segmentation |

---

**Summary:** 2 duplicate company clusters identified (acme-corp.com, globex.io), 4 invalid emails, 1 domain mismatch, 9 missing employee counts (8 fixable from enrichment), 6 missing countries (2 fixable), 11 missing titles, 10 missing personas, and 10 industry values that conflict with enrichment. **Without a deals file, pipeline-dollar prioritization is impossible.** If you can provide the deals/opportunities export, I will re-rank the top 10 by actual amount at stake.

## Analysis

### Candidate 1 — Deal-EC3025 (no amount given)
- **Prospect voice**: "We need SCIM user provisioning — our security team will not approve any tool that requires manual account management."
- **Product docs**: "SCIM user provisioning … NOT currently listed as supported capabilities."
- **Classification**: **Real gap** — the product genuinely lacks SCIM, and the prospect states it blocks security approval.
- **Deal**: Deal-EC3025, amount: **not provided in the data**.

---

### Candidate 2 — Deal-D0D6B5 (no amount given)
- **Prospect voice**: "Our payroll runs on ADP Workforce Now and I don't see ADP anywhere in your integration list — that's a dealbreaker for us."
- **Product docs**: "ADP Workforce Now integrations are NOT currently listed as supported capabilities."
- **Classification**: **Real gap** — ADP is absent from the integration list and the prospect calls it a dealbreaker.
- **Deal**: Deal-D0D6B5, amount: **not provided in the data**.

---

### Candidate 3 — Deal-CFE7F4 (no amount given)
- **Prospect voice**: "I tried to build a custom report combining recognition frequency with turnover and couldn't — is that possible on our current plan?"
- **Product docs**: "Custom report builder — Enterprise only."
- **Classification**: **Plan gate** — the feature exists but is gated behind the Enterprise tier. The prospect's question is about their *current plan*, not a product absence.
- **Excluded from summary**.

---

### Candidate 4 — Deal-84DBA6 (no amount given)
- **Prospect voice**: "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."
- **Product docs**: Slack integration is supported on all plans.
- **Classification**: **Rollout/enablement issue** — the product works; the problem is adoption and training.
- **Excluded from summary**.

---

### Candidate 5 — Deal-36C33F (no amount given)
- **Alex Franklin speaks first**: "Full transparency — we don't have a native mobile app for hourly workers yet, though it's on the roadmap."
- **Prospect voice**: "Good to know. The web version should be fine for our office staff for now."
- **Classification**: **Not a prospect-raised gap.** The prospect never asks for anything; they accept the web version. The "gap" is articulated by the rep, which the instructions say does not count as prospect voice.
- **Excluded from summary**.

---

### Summary of True Product Gaps

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

show the model's full answer

## Analysis: Alex Franklin — Last 10 Calls (Jul 28 – Sep 3, 2026)

---

### 1. What they lead with in the first five minutes

**8 of 10 calls** open with the same social-proof case study:

> "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." — TT-001 through TT-010 (8×)

**2 calls deviate:**
- **TT-004** (Deal-403845): *"I put together a short agenda — security review first, then pricing."* — agenda-based, no case study.
- **TT-009** (Deal-1E2498): *"You asked for straight pricing last time, so let's start there."* — reactive to a prior conversation.

Both deviations ended without a concrete next step agreed.

---

### 2. How they handle the three most common objections

**Objection #1 — Budget locked / can't add a line item** (appears 4×: 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."*

Alex responds with the turnover-savings reframe (same script all 4×):

> "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." — TT-001 min 8

**Objection #2 — "Revisit next quarter / open enrollment"** (appears 3×: 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."*

Alex pivots to a 90-day pilot (same script all 3×):

> "Makes sense. What if we scope a 90-day pilot with one department so you have internal data before next quarter's planning?" — TT-002 min 8

**Objection #3 — "We already use spreadsheets / why would we change?"** (appears 3×: TT-004, TT-007, TT-009)

> *"We already do recognition with a spreadsheet and quarterly gift cards — why would we change?"*

Alex answers with the automation + analytics argument (same script all 3×):

> "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." — TT-004 min 8

---

### 3. How often a concrete next step is agreed (rate)

| Outcome | Count | Deals |
|--------|-------|-------|
| Asks for working session | 7 | TT-001, -002, -003, -005, -006, -008, -009 |
| Prospect agrees | 7 | All 7 → **100% of asks** |
| No next step asked | 3 | TT-004, TT-007, TT-010 |
| **Overall agreement rate** | **7/10 = 70%** | |

In the 3 calls without an ask, Alex accepts a deferral and ends the call — no smaller commitment attempted.

---

### 4. Every competitor a prospect raised

| Call | Competitor | Quote |
|------|-----------|-------|
| TT-003 (Deal-547B2B) | **Awardco** | *"We're also in late talks with Awardco — their rewards catalog looks bigger than yours."* |
| TT-007 (Deal-EDC141) | **Kudos** | *"How are you different from Kudos? Our CEO used them at her last company."* |

**Note:** Workhuman is mentioned once (TT-005 min 2) but Alex raises it, not the prospect — excluded per the "prospect raised" criterion.

---

### 5. Two coaching notes

1. **You don't have a play for "no urgency / need to think about it."** In TT-007 the prospect says *"there's no urgency on our side"* and you reply *"Fair enough"* — no urgency created, no next step, no smaller ask. This objection will recur; script a response that creates a hook (e.g., a low-friction data-collection exercise or a calendar hold for when urgency materializes) instead of accepting silence.

2. **Your three objection scripts are effective but identical every time.** The budget-savings reframe, the 90-day pilot, and the "spreadsheets scale" argument are word-for-word repeats. Prospects who have read your LinkedIn or talked to peers will hear a recording. Tailor the *specific number or example* to each deal: when a prospect says "open enrollment," name their specific Q4 event; when they say "spreadsheet," ask how many people they have and calculate the break-point yourself. Generic scripts work at volume; tailored answers close at premium.

The last completed month is **August 2026**. Here are the metrics across all YTD redemptions through that month.

---

### Redemption Count: 270

### Total Spend: $22,401.00

### Unique Redeemers: 148 distinct user_keys

### Redemptions per Redeemer: 1.82 (270 ÷ 148)

### Provider Mix (% of spend)

| Provider      | Spend      | Share     |
|---------------|------------|-----------|
| TangoCard     | $3,175.00 | 14.17%    |
| Tremendous    | $6,540.00 | 29.19%    |
| custom        | $8,810.00 | 39.33%    |
| Snappy        | $3,876.00 | 17.30%    |
| **Total**     | **$22,401.00** | **100%** |

### Top 5 Countries by Redemption Count

| Country | Redemptions |
|---------|-------------|
| US      | 181         |
| CA      | 18          |
| GB      | 14          |
| AU      | 13          |
| NL      | 12          |

---

**Arithmetic summary:**
- All 270 rows in the CSV fall within Jan–Aug 2026. Two rows have `redeemed_at` of 2026-08-31 (RD-B7BEED, RD-226116), so August is fully represented.
- Provider spend: TangoCard $3,175 / Tremendous $6,540 / custom $8,810 / Snappy $3,876.
- Shares: ($3,175 ÷ $22,401) × 100 = 14.17%, ($6,540 ÷ $22,401) × 100 = 29.19%, ($8,810 ÷ $22,401) × 100 = 39.33%, ($3,876 ÷ $22,401) × 100 = 17.30%. These sum to 100.00%.
- Top 5 countries: US (181), CA (18), GB (14), AU (13), NL (12).

## Q2–Q3 2026 Support Ticket Synthesis (Jun 1 – Aug 29)

80 tickets analyzed by body text, ignoring existing tag labels. Ranked by ARR exposure.

---

### 1. HRIS provisioning silently fails to create accounts for new hires
**Tickets:** 12  ·  **Share:** 15%  ·  **Accounts:** 3  ·  **ARR affected:** $114,000

C-0B2213A9 ($36K) filed 7 tickets over 7 weeks — every new-hire batch fails. C-0DDFC9A7 ($48K) and C-0F6C0F34 ($30K) report the sync completes with no error log yet skips employees. A silent failure means these accounts have no way to know provisioning broke until a hire tries to log in.

**Sample tickets:** IC-460059, IC-460062  
**Recommendation:** Add HRIS sync monitoring — compare source-hire count vs. provisioned-account count per batch and alert on mismatch. Surface a sync-health metric in the admin panel so customers can self-detect.

---

### 2. Redemption checkout fails; points deducted but gift card never delivered
**Tickets:** 18  ·  **Share:** 22.5%  ·  **Accounts:** 7  ·  **ARR affected:** $68,800

7 distinct accounts across $8.7K–$11K ARR. Symptoms: checkout spinner that never completes, "failed twice today," and worst — points deducted from the user's balance with no gift card email. C-14264ABD ($11K) filed 3 times in 5 weeks. The financial exposure is lower than HRIS but the trust impact is acute: users lose real purchasing power.

**Sample tickets:** IC-460029, IC-460024  
**Recommendation:** Implement a two-phase redemption (reserve → confirm → release). If the downstream gift-card provider errors, reverse the point deduction automatically instead of leaving the user with a phantom charge.

---

### 3. Annual billing at wrong tier / seat-count errors on one large account
**Tickets:** 16  ·  **Share:** 20%  ·  **Accounts:** 1  ·  **ARR affected:** $52,000

Concentrated on C-0E9C27D1 ($52K). Charged for 200 seats when they license 150; renewal invoiced at the wrong tier price; "third invoice in a row with the same seat-count error" — the fix is not sticking. Single-account pattern but $52K is the second-largest ARR in the dataset, so it is not noise.

**Sample tickets:** IC-460069, IC-460078  
**Recommendation:** Deduplicate the billing system's seat-count source of truth (contract vs. invoice vs. usage). Assign an engineer to C-0E9C27D1's ticket queue until the root cause is resolved — repeated failures erode renewal confidence.

---

### 4. Recognition points not posting to user balances
**Tickets:** 20  ·  **Share:** 25%  ·  **Accounts:** 9  ·  **ARR affected:** $31,100

Highest volume (25% of all tickets) but lowest ARR exposure because affected accounts are all <$5K. Nine accounts reporting "shows as delivered but points never arrived," "my balance has not updated since Tuesday," and "whole team" scope — suggests a batch-processing delay or a queue that silently drops.

**Sample tickets:** IC-460004, IC-460016  
**Recommendation:** Add a point-posting audit log visible to admins (delivered → queued → credited). Set a 15-minute SLA on the posting job and page the on-call if it breaches. The volume is high but the revenue at risk is low — fix for retention, not ARR protection.

---

### 5. Slack integration broken (sync stops, slash commands error, re-auth doesn't stick)
**Tickets:** 14  ·  **Share:** 17.5%  ·  **Accounts:** 4  ·  **ARR affected:** $18,900

Three distinct symptoms (sync toggle resets, slash command returns error, app disconnects) but all trace to the Slack integration. C-0BA71F12 ($3.9K) filed 6 tickets alone. Low ARR but high-touch — these accounts are small and noisy, consuming disproportionate support time.

**Sample tickets:** IC-460049, IC-460051  
**Recommendation:** Run a one-week Slack integration bug bash: fix the toggle-reset, the slash-command error, and the re-auth loop in a single sprint. Then auto-test the integration on every deploy.

---

### Summary table

| Theme | Tickets | Share | Accounts | ARR affected | Two ticket IDs |
|---|---|---|---|---|---|
| HRIS provisioning silent failure | 12 | 15% | 3 | **$114,000** | IC-460059, IC-460062 |
| Redemption checkout failures | 18 | 22.5% | 7 | **$68,800** | IC-460029, IC-460024 |
| Billing wrong tier/seat count | 16 | 20% | 1 | **$52,000** | IC-460069, IC-460078 |
| Points not posting | 20 | 25% | 9 | $31,100 | IC-460004, IC-460016 |
| Slack integration broken | 14 | 17.5% | 4 | $18,900 | IC-460049, IC-460051 |

**Key takeaway:** The top three themes by ARR exposure — HRIS, redemption, billing — together affect $234,800 in annual revenue and are concentrated on 11 accounts. The highest-volume theme (points not posting) has the lowest ARR impact. Prioritize the HRIS and redemption fixes first; the billing fix is urgent for the single $52K account before renewal churn.

# Weekly Marketing Goals Update — Q3-2026 (66 of 92 days elapsed, 71.7%)

| Metric | QTD Actual | Target | Delta to Target | Pace (66d expected) | Delta to Pace | Status |
|---|---|---|---|---|---|---|
| **SQMs** | 230 | 300 | -70 | 215.2 | +14.8 | **AHEAD** ✓ |
| **SQOs** | 84 | 120 | -36 | 86.1 | -2.1 | **BEHIND** ✗ |
| **DS2s** | 40 | 75 | -35 | 53.8 | -13.8 | **BEHIND** ✗ |
| **Closed-Lost MIA Rate** | 20.0% (5/25) | 10.0% | +10pp (worse) | — | — | **BEHIND** ✗ |
| **Same-Quarter Closes** | 10 | 20 | -10 | 14.3 | -4.3 | **BEHIND** ✗ |
| **Active Pipeline** | $3,000,000 | $4,000,000 | -$1,000,000 | $2,869,565 | +$130,435 | **AHEAD** ✓ |

**Arithmetic** (pace = target ÷ 92 days × 66 days elapsed):
- SQMs: 300/92 × 66 = 215.2 → actual 230, ahead by 14.8
- SQOs: 120/92 × 66 = 86.1 → actual 84, behind by 2.1
- DS2s: 75/92 × 66 = 53.8 → actual 40, behind by 13.8
- Same-quarter closes: 20/92 × 66 = 14.3 → actual 10, behind by 4.3
- Active pipeline: $4,000,000/92 × 66 = $2,869,565 → actual $3,000,000, ahead by $130,435
- MIA rate: 5 MIA ÷ 25 closed-lost = 20%, double the 10% target

---

### What moved this week

**SQM generation is the bright spot** — 230 meetings against a 66-day pace of 215, running ahead. The team is sourcing more meetings than needed to hit quarterly target. However, **SQO conversion is the bottleneck**: 84 SQOs on 230 SQMs is a 36.5% SQM→SQO rate, but we're still 2.1 behind pace. **DS2s are the biggest gap** — 40 actual vs 53.8 pace, meaning deals are stalling or not advancing through stage 2 quickly enough. **MIA rate at 20%** is double the 10% threshold — 5 of 25 closed-lost deals went dark without reason, which flags either poor loss-capture discipline or deals slipping through without proper disqualification. **Same-quarter closes** are tracking behind (10 vs 14.3 pace), consistent with the DS2 bottleneck. **Active pipeline ($3M)** is ahead of pace ($2.87M) despite the conversion gaps, suggesting larger deal sizes or a healthy top-of-funnel carrying the dollar figure — worth watching whether that pipeline converts or ages out.

**Vendor Response: Bonusly Security & Compliance Questionnaire**

---

**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 current list of subprocessors 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 (and SCIM user provisioning) are 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. An ISO 27001 certificate or a trust portal statement on certifications would be needed.

**Q9 — What is your contractual uptime SLA percentage?**
Unanswerable from the provided excerpts. The contractual service-level agreement or uptime guarantee terms would be needed.

show the model's full answer

# NDA Triage — Bonusly

## NDA-1 — [PARTY A] | **GREEN** (standard approval)

**Driving clause:** Section 3 — all five standard carve-outs present: publicly available, prior knowledge, third-party receipt, independent development, and legally required disclosure.

**Reasoning:**
- Mutual confidentiality ✓
- 2-year term, 3-year survival — standard ✓
- Full carve-out set protects against inadvertent disclosure claims ✓
- Delaware governing law — standard US jurisdiction for a Delaware company ✓
- No non-solicit, no non-compete, no exclusivity ✓
- **Clean. Route for standard execution.**

---

## NDA-2 — [PARTY B] | **YELLOW** (counsel review)

**Driving clause:** Section 4 — 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."

**Reasoning:**
- Mutual confidentiality and standard carve-outs are fine ✓
- Non-solicit is embedded in the NDA, not a separate agreement — easy to miss on quick read
- Scope is reasonable (mutual, contact-based, 18-month tail), but still restricts Bonusly's hiring pipeline for any employee [PARTY B] introduces during eval
- **Counsel should confirm: (a) "solicit" includes indirect solicitation via recruiters, (b) carve-out for general job postings, (c) waiver if [PARTY B] later becomes a customer. Not a RED because it's mutual and contact-scoped.**

---

## NDA-3 — [PARTY C] | **RED** (full legal review)

**Driving clause:** Section 2 — non-compete:

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

**Reasoning:**
- **Three-year non-compete** with no geographic limit, no revenue threshold, no line-of-business carve-out. "Directly or indirectly engage" could sweep in any GTM/RevOps work Bonusly does if it touches [PARTY C]'s market.
- **One-way confidentiality** — [PARTY C] discloses; Bonusly receives only. Imbalanced but secondary to the non-compete.
- **Five-year term** — double the standard. Unusual for an eval NDA.
- **No carve-outs** — missing all five. Bonusly could be liable for info it independently developed or received from a third party.
- **Irish governing law + exclusive Irish jurisdiction** — forces dispute resolution abroad. High cost to enforce any protection.
- **Unenforceable or not, the clause exists and creates risk.** Full legal review required before signing.