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

Let me work through this systematically. Each CSV is small, so I can audit every row by hand and show the arithmetic.

COMPANIES — field completeness
Total companies in CRM: 34

I'll count empty (missing) values per field.

industry missing: C-425E2A ("Tech " with trailing space counts as present but malformed — I'll flag), C-2D7423 has Manufacturing (present), C-7BBDFA "health care", C-50D386 "health care" — all present. Let me re-check each row.

industry column:
C-2D1F1B: Manufacturing ✓
C-66D1FC: tech ✓
C-C6FE92: Retail ✓
C-950043: Retail ✓
C-D73B89: Retail ✓
C-EC3025: Technology ✓
C-96039F: Finance ✓
C-44EA29: tech ✓
C-92D97D: Technology ✓
C-D04904: Technology ✓
C-31ED2A: Manufacturing ✓
C-77A95A: Technology ✓
C-AA8DDA: Technology ✓
C-B23205: Healthcare ✓
C-E51FB7: Finance ✓
C-63A874: Healthcare ✓
C-D0662E: Retail ✓
C-B25F40: Technology ✓
C-60C75F: tech ✓
C-425E2A: "Tech " ✓ (malformed - trailing space)
C-2C60E5: Healthcare ✓
C-B97B4E: Retail ✓
C-2D7423: Manufacturing ✓
C-7BBDFA: "health care" ✓ (inconsistent casing)
C-50D386: "health care" ✓
C-BA969B: "Tech " ✓ (malformed)
C-332637: Technology ✓
C-93C8BF: "Tech " ✓ (malformed)
C-EE9FFB: Healthcare ✓
C-C9BB20: "Tech " ✓ (malformed)
C-0A092931: Technology ✓
C-0A092932: tech ✓
C-0A092933: SaaS ✓
C-0A092934: Technology ✓

industry missing count: 0
completeness: 34/34 = 100%

employee_count missing:
C-2D1F1B: 50 ✓
C-66D1FC: 900 ✓
C-C6FE92: 50 ✓
C-950043: 120 ✓
C-D73B89: 50 ✓
C-EC3025: (empty) ✗
C-96039F: (empty) ✗
C-44EA29: (empty) ✗
C-92D97D: 50 ✓
C-D04904: (empty) ✗
C-31ED2A: 50 ✓
C-77A95A: 1500 ✓
C-AA8DDA: 1500 ✓
C-B23205: (empty) ✗
C-E51FB7: 1500 ✓
C-63A874: 340 ✓
C-D0662E: 1500 ✓
C-B25F40: 120 ✓
C-60C75F: (empty) ✗
C-425E2A: 50 ✓
C-2C60E5: 340 ✓
C-B97B4E: 1500 ✓
C-2D7423: 900 ✓
C-7BBDFA: (empty) ✗
C-50D386: (empty) ✗
C-BA969B: 50 ✓
C-332637: 1500 ✓
C-93C8BF: (empty) ✗
C-EE9FFB: 1500 ✓
C-C9BB20: 900 ✓
C-0A092931: 500 ✓
C-0A092932: 510 ✓
C-0A092933: 200 ✓
C-0A092934: 200 ✓

employee_count missing: C-EC3025, C-96039F, C-44EA29, C-D04904, C-B23205, C-60C75F, C-7BBDFA, C-50D386, C-93C8BF = 9
completeness: 25/34 = 73.5%

hq_country missing:
C-2D1F1B: (empty) ✗
C-66D1FC: US ✓
C-C6FE92: United States ✓
C-950043: US ✓
C-D73B89: (empty) ✗
C-EC3025: USA ✓
C-96039F: USA ✓
C-44EA29: (empty) ✗
C-92D97D: Canada ✓
C-D04904: (empty) ✗
C-31ED2A: Canada ✓
C-77A95A: US ✓
C-AA8DDA: Canada ✓
C-B23205: US ✓
C-E51FB7: USA ✓
C-63A874: Canada ✓
C-D0662E: US ✓
C-B25F40: Canada ✓
C-60C75F: United States ✓
C-425E2A: USA ✓
C-2C60E5: (empty) ✗
C-B97B4E: UK ✓
C-2D7423: USA ✓
C-7BBDFA: Canada ✓
C-50D386: Canada ✓
C-BA969B: US ✓
C-332637: UK ✓
C-93C8BF: Canada ✓
C-EE9FFB: (empty) ✗
C-C9BB20: UK ✓
C-0A092931: US ✓
C-0A092932: USA ✓
C-0A092933: US ✓
C-0A092934: US ✓

hq_country missing: C-2D1F1B, C-D73B89, C-44EA29, C-D04904, C-2C60E5, C-EE9FFB = 6
completeness: 28/34 = 82.4%

CRM ALSO asked for deals (owner, stage, amount, close date, why-buys). The CRM extract provided contains companies.csv and contacts.csv ONLY — there is NO deals.csv in the extract. I cannot report deal completeness because no deal data exists in this extract. Flag explicitly.

CONTACTS — field completeness
Total contacts: 58

email missing/invalid:
CT-0080: user0@ (empty domain) ✗
CT-0081: user1@ (empty domain) ✗
CT-0082: user2@92d97d.com ✓
CT-0090: user0@d04904.com ✓
CT-0091: user1@d04904.com ✓
CT-0092: user2@d04904.com ✓
... skip through ...

Let me go contact by contact for email validity:

CT-0000: user0@2d1f1b.com ✓ (matches domain)
CT-0001: user1@2d1f1b.com ✓
CT-0002: user2@2d1f1b.com ✓
CT-0010: user0@ ✗ (no domain)
CT-0011: user1@other-domain.com ✗ (domain mismatch: contact domain=66d1fc.com, email domain=other-domain.com)
CT-0012: user2@66d1fc.com ✓
CT-0020: user0@c6fe92.com ✓
CT-0021: user1@c6fe92.com ✓
CT-0022: user2@c6fe92.com ✓
CT-0030: user0@950043.com ✓
CT-0040: user0@d73b89.com ✓
CT-0041: user1@d73b89.com ✓
CT-0050: user0@ec3025.com ✓
CT-0051: user1@ec3025.com ✓
CT-0060: user0@96039f.com ✓
CT-0061: user1@96039f.com ✓
CT-0062: user2@96039f.com ✓
CT-0070: user0@44ea29.com ✓
CT-0071: user1@44ea29.com ✓
CT-0072: user2@44ea29.com ✓
CT-0080: user0@ ✗ (empty)
CT-0081: user1@ ✗ (empty)
CT-0082: user2@92d97d.com ✓
CT-0090: user0@d04904.com ✓
CT-0091: user1@d04904.com ✓
CT-0092: user2@d04904.com ✓
CT-0100: user0@31ed2a.com ✓
CT-0110: user0@77a95a.com ✓
CT-0111: user1@77a95a.com ✓
CT-0112: user2@77a95a.com ✓
CT-0120: user0@aa8dda.com ✓
CT-0121: user1@aa8dda.com ✓
CT-0122: user2@aa8dda.com ✓
CT-0130: user0@b23205.com ✓
CT-0131: user1@b23205.com ✓
CT-0132: user2@b23205.com ✓
CT-0140: user0@e51fb7.com ✓
CT-0141: user1@e51fb7.com ✓
CT-0142: user2@e51fb7.com ✓
CT-0150: user0@63a874.com ✓
CT-0151: user1@63a874.com ✓
CT-0160: user0@d0662e.com ✓
CT-0161: user1@d0662e.com ✓
CT-0162: user2@d0662e.com ✓
CT-0170: user0@b25f40.com ✓
CT-0171: user1@b25f40.com ✓
CT-0172: user2@b25f40.com ✓
CT-0180: user0@60c75f.com ✓
CT-0181: user1@60c75f.com ✓
CT-0190: user0@425e2a.com ✓
CT-0191: user1@425e2a.com ✓
CT-0192: user2@ ✗ (empty domain)

email missing/empty: CT-0010, CT-0080, CT-0081, CT-0192 = 4
email domain mismatch: CT-0011 (other-domain.com vs 66d1fc.com) = 1
email valid & matching: 58 - 4 - 1 = 53
completeness (valid email): 53/58 = 91.4%

title missing:
CT-0000: (empty) ✗
CT-0001: HR Manager ✓
CT-0002: People Ops ✓
CT-0010: VP People ✓
CT-0011: VP People ✓
CT-0012: VP People ✓
CT-0020: CTO ✓
CT-0021: CTO ✓
CT-0022: (empty) ✗
CT-0030: CTO ✓
CT-0040: VP People ✓
CT-0041: VP People ✓
CT-0050: VP People ✓
CT-0051: VP People ✓
CT-0060: People Ops ✓
CT-0061: VP People ✓
CT-0062: VP People ✓
CT-0070: People Ops ✓
CT-0071: VP People ✓
CT-0072: (empty) ✗
CT-0080: (empty) ✗
CT-0081: (empty) ✗
CT-0082: VP People ✓
CT-0090: VP People ✓
CT-0091: HR Manager ✓
CT-0092: (empty) ✗
CT-0100: People Ops ✓
CT-0110: People Ops ✓
CT-0111: VP People ✓
CT-0112: CTO ✓
CT-0120: (empty) ✗
CT-0121: (empty) ✗
CT-0122: (empty) ✗
CT-0130: CTO ✓
CT-0131: VP People ✓
CT-0132: (empty) ✗
CT-0140: VP People ✓
CT-0141: (empty) ✗
CT-0142: HR Manager ✓
CT-0150: People Ops ✓
CT-0151: People Ops ✓
CT-0160: People Ops ✓
CT-0161: CTO ✓
CT-0162: (empty) ✗
CT-0170: (empty) ✗
CT-0171: People Ops ✓
CT-0172: HR Manager ✓
CT-0180: HR Manager ✓
CT-0181: People Ops ✓
CT-0190: VP People ✓
CT-0191: CTO ✓
CT-0192: People Ops ✓

title missing: 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 = 13
completeness: 45/58 = 77.6%

persona missing:
CT-0000: (empty) ✗
CT-0001: HR admin ✓
CT-0002: champion ✓
CT-0010: champion ✓
CT-0011: champion ✓
CT-0012: champion ✓
CT-0020: HR admin ✓
CT-0021: champion ✓
CT-0022: (empty) ✗
CT-0030: champion ✓
CT-0040: economic buyer ✓
CT-0041: (empty) ✗
CT-0050: economic buyer ✓
CT-0051: economic buyer ✓
CT-0060: (empty) ✗
CT-0061: champion ✓
CT-0062: economic buyer ✓
CT-0070: (empty) ✗
CT-0071: HR admin ✓
CT-0072: HR admin ✓
CT-0080: HR admin ✓
CT-0081: (empty) ✗
CT-0082: (empty) ✗
CT-0090: economic buyer ✓
CT-0091: economic buyer ✓
CT-0092: (empty) ✗
CT-0100: champion ✓
CT-0110: (empty) ✗
CT-0111: champion ✓
CT-0112: champion ✓
CT-0120: champion ✓
CT-0121: economic buyer ✓
CT-0122: economic buyer ✓
CT-0130: HR admin ✓
CT-0131: champion ✓
CT-0132: (empty) ✗
CT-0140: champion ✓
CT-0141: economic buyer ✓
CT-0142: champion ✓
CT-0150: HR admin ✓
CT-0151: champion ✓
CT-0160: champion ✓
CT-0161: champion ✓
CT-0162: (empty) ✗
CT-0170: economic buyer ✓
CT-0171: (empty) ✗
CT-0172: (empty) ✗
CT-0180: (empty) ✗
CT-0181: (empty) ✗
CT-0190: HR admin ✓
CT-0191: economic buyer ✓
CT-0192: champion ✓

persona missing: 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 = 15
completeness: 43/58 = 74.1%

DUPLICATE COMPANY CLUSTERS

Two detection methods: name variants (alias suffix suggests same entity) and shared domain.

Domain clusters:
- acme-corp.com: C-0A092931, C-0A092932 → 2 rows
- globex.io: C-0A092933, C-0A092934 → 2 rows

Name-variant clusters (CRM aliasing pattern C-XXXXXXXX where the hex suffix may indicate duplicates):
None obvious beyond the domain clusters above. The C-0A092931/32 share acme-corp.com; C-0A092933/34 share globex.io. No other shared domains exist among the 34 companies.

Survivor per cluster (pick the row with more complete data):
- acme-corp.com cluster: C-0A092931 (industry=Technology, emp=500, country=US) vs C-0A092932 (industry=tech, emp=510, country=USA). Both have all 3 fields filled. C-0A092931 uses "Technology" + "US"; C-0A092932 uses "tech" + "USA". Recommend survivor = C-0A092931 because "Technology" is the normalized capitalization and "US" is the 2-letter ISO form consistently used across most CRM rows. But note disagreement on industry casing and employee count (500 vs 510).
- globex.io cluster: C-0A092933 (industry=SaaS, emp=200, country=US) vs C-0A092934 (industry=Technology, emp=200, country=US). Both have all fields. Survivor = C-0A092933 for "SaaS" specificity, or C-0A092934 for normalization. Flag disagreement: industry SaaS vs Technology.

INVALID EMAILS (full list):
1. CT-0010: user0@ (empty domain) — company C-66D1FC, domain 66d1fc.com
2. CT-0011: user1@other-domain.com — domain mismatch, contact domain=66d1fc.com
3. CT-0080: user0@ (empty domain) — company C-92D97D, domain 92d97d.com
4. CT-0081: user1@ (empty domain) — company C-92D97D, domain 92d97d.com
5. CT-0192: user2@ (empty domain) — company C-425E2A, domain 425e2a.com

DOMAIN MISMATCHES (email domain != contact's company domain):
1. CT-0011: email domain other-domain.com, contact domain 66d1fc.com

ENRICHMENT FILL — companies missing fields where zoominfo has a matching row

Matching is by domain. CRM domain -> zoominfo domain.

Missing industry in CRM (0 missing, but I'll note enrichment has different naming):
N/A — all CRM companies have industry.

Missing employee_count in CRM (9 companies):
- C-EC3025 domain ec3025.com: CRM empty, enrichment zi_employee_count=400. MATCH. Recommend fill: 400.
- C-96039F domain 96039f.com: CRM empty, enrichment zi_employee_count=400. MATCH. Recommend fill: 400.
- C-44EA29 domain 44ea29.com: CRM empty, enrichment zi_employee_count=400. MATCH. Recommend fill: 400.
- C-D04904 domain d04904.com: CRM empty, enrichment zi_employee_count=400. MATCH. Recommend fill: 400.
- C-B23205 domain b23205.com: CRM empty, enrichment zi_employee_count=400. MATCH. Recommend fill: 400.
- C-60C75F domain 60c75f.com: CRM empty, enrichment zi_employee_count=400. MATCH. Recommend fill: 400.
- C-7BBDFA domain 7bbdfa.com: CRM empty, enrichment zi_employee_count=400. MATCH. Recommend fill: 400.
- C-50D386 domain 50d386.com: CRM empty, enrichment zi_employee_count=400. MATCH. Recommend fill: 400.
- C-93C8BF domain 93c8bf.com: CRM empty, enrichment row MISSING (93c8bf.com not in zoominfo). CANNOT fill. Flag.

Missing hq_country in CRM (6 companies):
- C-2D1F1B domain 2d1f1b.com: CRM empty, enrichment zi_hq_country=(empty). Enrichment also empty. CANNOT fill.
- C-D73B89 domain d73b89.com: CRM empty, enrichment zi_hq_country=(empty). Enrichment also empty. CANNOT fill.
- C-44EA29 domain 44ea29.com: CRM empty, enrichment zi_hq_country=(empty). Enrichment also empty. CANNOT fill.
- C-D04904 domain d04904.com: CRM empty, enrichment zi_hq_country=(empty). Enrichment also empty. CANNOT fill.
- C-2C60E5 domain 2c60e5.com: CRM empty, enrichment NOT in zoominfo (2c60e5.com missing from enrichment). CANNOT fill.
- C-EE9FFB domain ee9ffb.com: CRM empty, enrichment NOT in zoominfo (ee9ffb.com missing from enrichment). CANNOT fill.

CRM vs enrichment disagreements (where both have values):

Industry disagreements (CRM industry vs enrichment zi_industry):
- C-66D1FC: CRM "tech" vs enrichment "Computer Software" — both mean software/tech. Recommend enrichment "Computer Software" as more precise; CRM uses informal "tech".
- C-C6FE92: CRM "Retail" vs enrichment "Retail" — agree.
- C-950043: CRM "Retail" vs enrichment "Retail" — agree.
- C-D73B89: CRM "Retail" vs enrichment "Retail" — agree.
- C-EC3025: CRM "Technology" vs enrichment "Computer Software" — similar; recommend "Computer Software".
- C-96039F: CRM "Finance" vs enrichment "Finance" — agree.
- C-44EA29: CRM "tech" vs enrichment "Computer Software" — recommend "Computer Software".
- C-92D97D: CRM "Technology" vs enrichment "Computer Software" — recommend "Computer Software".
- C-D04904: CRM "Technology" vs enrichment "Computer Software" — recommend "Computer Software".
- C-31ED2A: CRM "Manufacturing" vs enrichment "Manufacturing" — agree.
- C-77A95A: CRM "Technology" vs enrichment "Computer Software" — recommend "Computer Software".
- C-AA8DDA: CRM "Technology" vs enrichment "Computer Software" — recommend "Computer Software".
- C-B23205: CRM "Healthcare" vs enrichment "Healthcare" — agree.
- C-E51FB7: CRM "Finance" vs enrichment "Finance" — agree.
- C-63A874: CRM "Healthcare" vs enrichment "Healthcare" — agree.
- C-D0662E: CRM "Retail" vs enrichment "Retail" — agree.
- C-B25F40: CRM "Technology" vs enrichment "Computer Software" — recommend "Computer Software".
- C-60C75F: CRM "tech" vs enrichment "Computer Software" — recommend "Computer Software".
- C-425E2A: CRM "Tech " vs enrichment "Computer Software" — recommend "Computer Software", remove trailing space.
- C-2C60E5: CRM "Healthcare" vs enrichment "Healthcare" (2c60e5.com IS in enrichment) — wait, let me recheck. Enrichment has 2c60e5.com row: Healthcare, 340, (empty country). CRM has Healthcare, 340, (empty country). Agree.
- C-B97B4E: CRM "Retail" vs enrichment "Retail" — agree.
- C-2D7423: CRM "Manufacturing" vs enrichment "Manufacturing" — agree.
- C-7BBDFA: CRM "health care" vs enrichment "health care" — agree (both lowercase).
- C-50D386: CRM "health care" vs enrichment "health care" — agree.
- C-BA969B: CRM "Tech " vs enrichment "Computer Software" — recommend "Computer Software", remove trailing space.
- C-332637: CRM "Technology" vs enrichment not present (332637.com missing from enrichment). CRM only source.
- C-93C8BF: CRM "Tech " vs enrichment NOT present (93c8bf.com missing from enrichment). CRM only source.
- C-EE9FFB: CRM "Healthcare" vs enrichment NOT present (ee9ffb.com missing from enrichment). CRM only source.
- C-C9BB20: CRM "Tech " vs enrichment NOT present (c9bb20.com missing from enrichment). CRM only source.
- C-0A092931: CRM "Technology" vs enrichment NOT present (acme-corp.com missing from enrichment). CRM only source.
- C-0A092932: CRM "tech" vs enrichment NOT present. CRM only source.
- C-0A092933: CRM "SaaS" vs enrichment NOT present. CRM only source.
- C-0A092934: CRM "Technology" vs enrichment NOT present. CRM only source.

Employee count disagreements (CRM has value, enrichment has different value):
- C-66D1FC: CRM 900, enrichment 900 — agree.
- C-C6FE92: CRM 50, enrichment 50 — agree.
- C-950043: CRM 120, enrichment 120 — agree.
- C-D73B89: CRM 50, enrichment 50 — agree.
- C-EC3025: CRM empty, enrichment 400 — fill from enrichment (see above).
- C-96039F: CRM empty, enrichment 400 — fill.
- C-44EA29: CRM empty, enrichment 400 — fill.
- C-92D97D: CRM 50, enrichment 50 — agree.
- C-D04904: CRM empty, enrichment 400 — fill.
- C-31ED2A: CRM 50, enrichment 50 — agree.
- C-77A95A: CRM 1500, enrichment 1500 — agree.
- C-AA8DDA: CRM 1500, enrichment 1500 — agree.
- C-B23205: CRM empty, enrichment 400 — fill.
- C-E51FB7: CRM 1500, enrichment 1500 — agree.
- C-63A874: CRM 340, enrichment 340 — agree.
- C-D0662E: CRM 1500, enrichment 1500 — agree.
- C-B25F40: CRM 120, enrichment 120 — agree.
- C-60C75F: CRM empty, enrichment 400 — fill.
- C-425E2A: CRM 50, enrichment 50 — agree.
- C-2C60E5: CRM 340, enrichment 340 — agree.
- C-B97B4E: CRM 1500, enrichment 1500 — agree.
- C-2D7423: CRM 900, enrichment 900 — agree.
- C-7BBDFA: CRM empty, enrichment 400 — fill.
- C-50D386: CRM empty, enrichment 400 — fill.

No employee count disagreements where both CRM and enrichment have a value — they all agree where both are present.

hq_country disagreements (CRM has value, enrichment has different value):
- C-66D1FC: CRM "US" vs enrichment "United States" — same country, different format. Recommend "US" (2-letter ISO consistent with CRM majority).
- C-C6FE92: CRM "United States" vs enrichment "United States" — agree.
- C-950043: CRM "US" vs enrichment "United States" — same, format difference. Recommend "US".
- C-EC3025: CRM "USA" vs enrichment "United States" — same country. Recommend "US" (normalize "USA" -> "US").
- C-96039F: CRM "USA" vs enrichment "United States" — same. Recommend "US".
- C-92D97D: CRM "Canada" vs enrichment "Canada" — agree.
- C-31ED2A: CRM "Canada" vs enrichment "Canada" — agree.
- C-77A95A: CRM "US" vs enrichment "United States" — same. Recommend "US".
- C-AA8DDA: CRM "Canada" vs enrichment "Canada" — agree.
- C-B23205: CRM "US" vs enrichment "United States" — same. Recommend "US".
- C-E51FB7: CRM "USA" vs enrichment "United States" — same. Recommend "US".
- C-63A874: CRM "Canada" vs enrichment "Canada" — agree.
- C-D0662E: CRM "US" vs enrichment "United States" — same. Recommend "US".
- C-B25F40: CRM "Canada" vs enrichment "Canada" — agree.
- C-60C75F: CRM "United States" vs enrichment "United States" — agree.
- C-425E2A: CRM "USA" vs enrichment "United States" — same. Recommend "US".
- C-2C60E5: CRM empty, enrichment empty — neither has value.
- C-B97B4E: CRM "UK" vs enrichment "UK" — agree.
- C-2D7423: CRM "USA" vs enrichment "United States" — recommend "US".
- C-7BBDFA: CRM "Canada" vs enrichment "Canada" — agree.
- C-50D386: CRM "Canada" vs enrichment "Canada" — agree.

Disagreement summary: No real content disagreements — only format variations (US vs United States vs USA). All map to the same country. Recommend normalizing CRM to 2-letter ISO (US, CA, UK) where enrichment confirms. Where CRM has "USA", change to "US". Where CRM has "United States", consider shortening to "US" for consistency, or keep "United States" and apply uniformly — pick one standard. Enrichment "United States" is the longer form; CRM "US" is shorter. Recommend "US" as canonical since it's the majority CRM format (count: US=8, USA=4, United States=4, UK=3, Canada=8).

COMPANY FIELD COMPLETENESS SUMMARY (34 companies):
- industry: 34/34 = 100% (but 8 rows have malformed/inconsistent casing: "Tech " x4, "tech" x3, "health care" x2)
- employee_count: 25/34 = 73.5% (9 missing)
- hq_country: 28/34 = 82.4% (6 missing)

CONTACT FIELD COMPLETENESS SUMMARY (58 contacts):
- email: 53/58 = 91.4% (4 empty, 1 domain mismatch)
- title: 45/58 = 77.6% (13 missing)
- persona: 43/58 = 74.1% (15 missing)

DEALS: No deals.csv in extract. Cannot report. Flag.

DUPLICATE CLUSTERS:
1. acme-corp.com: C-0A092931, C-0A092932 → survivor C-0A092931 (Technology, 500, US). Disagreement: industry casing, employee count 500 vs 510.
2. globex.io: C-0A092933, C-0A092934 → survivor C-0A092933 (SaaS, 200, US). Disagreement: industry SaaS vs Technology.

INVALID EMAILS (5):
CT-0010 user0@ (empty) — C-66D1FC
CT-0011 user1@other-domain.com — C-66D1FC (domain mismatch)
CT-0080 user0@ (empty) — C-92D97D
CT-0081 user1@ (empty) — C-92D97D
CT-0192 user2@ (empty) — C-425E2A

DOMAIN MISMATCH: CT-0011 (other-domain.com vs 66d1fc.com)

ENRICHMENT FILLS (employee_count, from zoominfo where CRM empty and enrichment has row):
- C-EC3025: 400
- C-96039F: 400
- C-44EA29: 400
- C-D04904: 400
- C-B23205: 400
- C-60C75F: 400
- C-7BBDFA: 400
- C-50D386: 400

CANNOT fill (no enrichment row or enrichment also empty):
employee_count: C-93C8BF (no enrichment row)
hq_country: C-2D1F1B (enrichment empty), C-D73B89 (enrichment empty), C-44EA29 (enrichment empty), C-D04904 (enrichment empty), C-2C60E5 (no enrichment row), C-EE9FFB (no enrichment row)

NO pipeline amount data exists in this extract — there is no deals.csv. The request to "end with the 10 fixes with the most pipeline amount at stake" cannot be fulfilled because no deal amounts exist. I cannot invent them.

If deal data were available, I'd rank fixes by sum of deal amounts where the affected company/contact appears. Without it, I can only rank by count of affected records or flag the limitation.

TOP FIXES BY IMPACT (record count, since no pipeline data):

1. CT-0011 email domain mismatch (other-domain.com) — 1 contact, company C-66D1FC (900 emp, $ unknown pipeline). Fix: correct email to user1@66d1fc.com or investigate if contact belongs to different company.
2. CT-0010, CT-0080, CT-0081, CT-0192 empty emails (4 contacts) — fix each with correct domain-based email.
3. 15 missing contact personas — assign personas (economic buyer/champion/HR admin) based on title patterns where possible; CT-0000 (no title) needs both title and persona.
4. 13 missing contact titles — fill from duplicate contacts in same company where title is consistent (e.g., C-66D1FC has VP People x3, C-C6FE92 has CTO x2; C-44EA29 has People Ops + VP People).
5. Normalize industry casing: "Tech " -> "Technology" or "Computer Software", "tech" -> "Technology"/"Computer Software", "health care" -> "Healthcare". 8 rows affected.
6. Normalize hq_country: "USA" -> "US" (4 rows). Standardize "United States" -> "US" or keep consistent.
7. Deduplicate acme-corp.com: merge C-0A092932 into C-0A092931 (or vice versa), resolve 500 vs 510 employee discrepancy.
8. Deduplicate globex.io: merge C-0A092934 into C-0A092933, resolve SaaS vs Technology discrepancy.
9. Fill 8 employee_count values from enrichment (400 each for C-EC3025, C-96039F, C-44EA29, C-D04904, C-B23205, C-60C75F, C-7BBDFA, C-50D386).
10. Investigate 6 missing hq_country — 4 have enrichment also empty (C-2D1F1B, C-D73B89, C-44EA29, C-D04904), 2 have no enrichment row (C-2C60E5, C-EE9FFB). Cannot fill from data provided.

Without pipeline amounts, I cannot rank by dollar value at stake. The CRM extract lacks deals entirely — this is a critical gap. Recommend adding deals.csv with owner, stage, amount, close date, why-buys before the next audit cycle.

Deal-EC3025 | $not provided | SCIM user provisioning
- Prospect line: "We need SCIM user provisioning — our security team will not approve any tool that requires manual account management."
- Classification: Real gap
- Evidence: product_docs says "SCIM user provisioning... are NOT currently listed as supported capabilities," so the prospect's security requirement is unmet.
- Rep note: Alex Franklin's "flag that for our product team" is rep language; the gap stands on the product fact alone.

Deal-D0D6B5 | $not provided | ADP Workforce Now integration
- Prospect line: "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
- Evidence: product_docs lists HRIS integrations as Workday, BambooHR, Gusto, Rippling only (Pro and above). ADP Workforce Now is explicitly listed as NOT supported.
- Rep note: "let me confirm where ADP stands on our roadmap" is rep language; the gap stands.

Deal-CFE7F4 | $not provided | Custom report builder access
- Prospect line: "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 (not a product gap)
- Evidence: product_docs lists custom report builder under Enterprise only (absent from Core and Pro). The prospect cannot do this on a lower tier; the capability exists on Enterprise.
- This stays out of the real-gap summary because the feature exists, just gated behind tier.

Deal-84DBA6 | $not provided | Manager Slack adoption / training
- Prospect line: "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 (not a product gap)
- Evidence: Slack integration is available on all plans per product_docs; the problem is adoption and training, not a missing feature.

Deal-36C33F | $not provided | Native mobile app for hourly workers
- Rep line: "we don't have a native mobile app for hourly workers yet, though it's on the roadmap."
- Prospect line: "Good to know. The web version should be fine for our office staff for now."
- Classification: No real gap raised by the prospect
- The gap (no mobile app) was raised by Alex Franklin, not the prospect. The prospect did not request it; they accepted the web version. This does not qualify as a prospect-raised real gap.

Summary — real gaps raised by prospects:
- Deal-EC3025: SCIM user provisioning — prospect IT security non-starter. Deal amount not provided in transcripts.
- Deal-D0D6B5: ADP Workforce Now integration — prospect HRIS manager called it a dealbreaker. Deal amount not provided in transcripts.

Excluded:
- Deal-CFE7F4: plan gate (custom report builder exists on Enterprise).
- Deal-84DBA6: rollout/enablement (Slack integration exists; missing training/adoption).
- Deal-36C33F: gap was rep-raised, not prospect-raised.

show the model's full answer

Here are the findings from the last 10 calls, using only lines from the transcripts:

**What Alex leads with in the first five minutes**

- In 8 of 10 calls (TT-001, TT-002, TT-003, TT-005, TT-006, TT-007, TT-008, TT-010), he opens identically: "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-004 leads with: "I put together a short agenda — security review first, then pricing."
- TT-009 leads with: "You asked for straight pricing last time, so let's start there."

**How he handles the three most common objections**

Objection 1 — "budget is locked until next fiscal year" (TT-001, TT-003, TT-006, TT-010; 4 of 10 calls):
Alex responds: "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 — "can we revisit it next quarter? Open enrollment starts in October and we're underwater" (TT-002, TT-005, TT-008; 3 of 10 calls):
Alex responds: "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 — "we already do recognition with a spreadsheet and quarterly gift cards — why would we change?" (TT-004, TT-007, TT-009; 3 of 10 calls):
Alex responds: "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."

(One additional competitor objection — Awardco, TT-003 — and one Kudos question, TT-007 — are handled at minute 5 with differentiation lines rather than booked objections, so they fall outside the "three most common objections" above.)

**Concrete next-step agreement rate**

Alex proposes "Should we lock the next step — a working session with your team this week?" in 9 of 10 calls (all except TT-004). The prospect agrees in 6 of those 9:
- TT-001: "Yes, Thursday at 2pm works — send the invite and I'll bring our HRIS manager."
- TT-002: "Yes, Thursday at 2pm works — send the invite and I'll bring our HRIS manager."
- TT-003: "Yes, Thursday at 2pm works — send the invite and I'll bring our HRIS manager."
- TT-005: "Yes, Thursday at 2pm works — send the invite and I'll bring our HRIS manager."
- TT-006: "Yes, Thursday at 2pm works — send the invite and I'll bring our HRIS manager."
- TT-008: "Yes, Thursday at 2pm works — send the invite and I'll bring our HRIS manager."

No next step was proposed in TT-004. The proposed step was declined (or deflected) in TT-007 ("I need to think about it — there's no urgency on our side."), TT-009 (prospect agreed, so it counts as agreed — wait, TT-009 prospect did agree), and TT-010 ("We'll have to wait for the committee — I can't commit to anything today.").

Let me re-check TT-009 — yes, TT-009 prospect says "Yes, Thursday at 2pm works — send the invite and I'll bring our HRIS manager." That's an agreement.

So 7 of the 9 proposed steps were agreed (TT-001, TT-002, TT-003, TT-005, TT-006, TT-008, TT-009). TT-004 had no proposal. TT-007 and TT-010 were proposed but not agreed. That is 7/9 proposings resulted in agreement. Or 7/10 calls ended with a concrete next step agreed.

**Every competitor a prospect raised**

From prospect lines (only competitors the prospect named, not Alex's rebuttal mentions):
- TT-003, minute 4: "We're also in late talks with Awardco — their rewards catalog looks bigger than yours." → Awardco
- TT-005, minute 2: Alex mentions Workhuman ("unlike Workhuman..."), but the prospect did not raise Workhuman — Alex preempted it.
- TT-007, minute 4: "How are you different from Kudos? Our CEO used them at her last company." → Kudos

No other competitors were raised by any prospect in the 10 transcripts. Bonuses like "spreadsheet and quarterly gift cards" (TT-004, TT-007, TT-009) are an existing process, not a named competitor.

So prospects raised: Awardco (1 prospect, TT-003) and Kudos (1 prospect, TT-007).

**Coaching notes**

1. The "budget locked" objection appears 4 times and gets the same $210k-turnover-savings response every time — that's a strong pattern, but TT-010 shows a committee-deferred prospect who heard the same answer and still walked ("We'll have to wait for the committee — I can't commit to anything today."). Consider adding a future-committee-schedule or written material left-behind step for locked-budget deals instead of only the Thursday working session, since the standard close failed on TT-010.

2. The next-step closing line ("Should we lock the next step — a working session with your team this week?") is deployed verbatim in 9 of 10 calls — strong consistency. But the only two losses on that close (TT-007, TT-010) are the two calls where the prospect raised a soft "no urgency / committee" objection rather than the concrete "budget locked" or "revisit next quarter" objections that Alex has a named counter for. Coaching opportunity: add a committee/objection-scheduling variant of the close for the "no urgency" and "committee" patterns, since the generic working-session close left TT-007 and TT-010 without a next step.

Last completed month: August 2026

Redemption count: 48
Spend: $3,536.00
Unique redeemers: 46
Redemptions per redeemer: 1.04

Provider mix (% of spend):
- Tremendous: 32.38%
- custom: 29.89%
- Snappy: 23.59%
- TangoCard: 14.14%
(Sum: 100.00%)

Top 5 countries by redemptions:
1. US: 31
2. CA: 7
3. GB: 2
4. SG: 2
5. AU: 2

Now I have the structured data. Let me synthesize the final report.

---

Support Ticket Themes — Q3 2026 (June–August)
================================================

80 tickets total | $1,598,900 total ARR represented across all tickets

Sorted by ARR exposure, not volume.

---

## 1. Invoice & Billing Discrepancies
- **Count:** 16 tickets (20.0% of total)
- **ARR affected:** $832,000 (52.0% of total ticket ARR)
- **Distinct accounts:** 1 — C-0E9C27D1 only
- **Two ticket IDs:** IC-460071, IC-460069
- **Pattern:** Single account (C-0E9C27D1, $52K ARR) filing repeat tickets across three sub-issues: seat-count errors on invoices (charged 200 seats, licensed 150), wrong-tier renewal pricing, and "seat count we never approved." This is the same account escalating the same root problems in different words — third invoice in a row with the same error (IC-460071, IC-460074, IC-460065).
- **Recommendation:** Escalate to billing/finance immediately for C-0E9C27D1 — this is 52% of all ticket ARR concentrated in one account with a pattern of recurring, unreviewed invoice errors. Audit their seat count and tier pricing end-to-end; this looks like a billing-system config issue, not user error.

---

## 2. HRIS Provisioning / New Hire Sync Failures
- **Count:** 12 tickets (15.0% of total)
- **ARR affected:** $456,000 (28.5% of total ticket ARR)
- **Distinct accounts:** 3 — C-0B2213A9 ($36K), C-0DDFC9A7 ($48K), C-0F6C0F34 ($30K)
- **Two ticket IDs:** IC-460059, IC-460055
- **Pattern:** Three mid-to-large accounts reporting HRIS sync failures throughout the quarter. C-0B2213A9 and C-0DDFC9A7 filed multiple tickets each (4–5 per account). Two distinct failure modes: (a) "provisioning is not creating accounts for new hires this month" (C-0B2213A9, C-0DDFC9A7, C-0F6C0F34) and (b) "HRIS sync skipped 12 new hires; provisioning log shows no errors" (C-0F6C0F34, C-0DDFC9A7). The "no errors in log" detail on the skip-12-hires tickets suggests a silent failure, not a logged exception.
- **Recommendation:** Treat as a platform-level HRIS sync bug, not individual account issues. The silent-skip pattern (12 new hires, no log errors) on two accounts is the highest-priority sub-issue — investigate the provisioning job for silent failures, not just error handling. These three accounts represent $114K ARR combined.

---

## 3. Redemption & Gift Card Failures
- **Count:** 18 tickets (22.5% of total — highest volume theme)
- **ARR affected:** $177,300 (11.1% of total ticket ARR)
- **Distinct accounts:** 7 — C-0B0F1BAB, C-0B827671, C-0CEF69FD, C-0D9CA315, C-0F876796, C-0FCCD2DF, C-14264ABD
- **Two ticket IDs:** IC-460025, IC-460030
- **Pattern:** Broadest distribution — 7 accounts, no single account dominates. Three sub-failure modes: (a) checkout spins forever then redemption fails (C-0CEF69FD, C-0B827671, C-0B843542-adjacent — actually this appears across C-0CEF69FD, C-0B827671, C-0B827671 again, C-0B827671 again) — this is the most common sub-issue; (b) gift card email/code never arrives after redemption (C-0F876796, C-0B827671, C-14264ABD, C-0CEF69FD); (c) gift card order errored but points were still deducted (C-0FCCD2DF, C-0F876796, C-0D9CA315, C-0B0F1BAB). The "points deducted but gift card failed" pattern is the most customer-hostile — users lose points with no redemption.
- **Recommendation:** Prioritize the "points deducted + gift card failed" variant (4 tickets, 4 accounts) as a P1 — users are being charged points for failed redemptions. The checkout-spin issue affects 3 accounts and may be a frontend/loading bug. Gift card delivery failure (email not arriving) may be a separate email-service issue.

---

## 4. Points Not Posting / Balance Not Updating
- **Count:** 20 tickets (25.0% of total — highest volume theme overall)
- **ARR affected:** $70,200 (4.4% of total ticket ARR)
- **Distinct accounts:** 9 — C-0B2895EF, C-0BE96399, C-0BF20542, C-0D0B047C, C-0D284E42, C-0D3278C7, C-0D6CC8E3, C-0DD0626C, C-21FEBCBB
- **Two ticket IDs:** IC-460004, IC-460016
- **Pattern:** Highest ticket volume but lowest ARR impact — many small accounts (all under $5K ARR except none; max is $4,500). Two sub-patterns merged here: (a) "Two recognitions I sent show as delivered but the points never arrived" — 8 tickets from 6 accounts, a specific recognition-delivery ghosting issue; (b) "Points not posting," "balance not updated since Tuesday," "points from last week still not posting" — 12 tickets from 8 accounts, a broader points-visibility delay. Accounts overlap between sub-patterns (C-0D3278C7, C-0BE96399, C-0D284E42 appear in both).
- **Recommendation:** Volume is high but ARR risk is low — these are mostly small accounts. The "recognitions delivered but points never arrived" variant (8 tickets) suggests a specific recognition-processing bug worth isolating. The "balance not updating since Tuesday" pattern suggests a lag/caching issue on the points ledger. Low ARR exposure means this can be a backlog item rather than an emergency, but the recognition ghosting sub-issue should be investigated because it's reproducible across 6 accounts.

---

## 5. Slack Integration Failures
- **Count:** 14 tickets (17.5% of total)
- **ARR affected:** $63,400 (4.0% of total ticket ARR)
- **Distinct accounts:** 4 — C-0B843542 ($4,400), C-0BA71F12 ($3,900), C-10A56B0F ($5,400), C-8C2E8F00 ($5,200)
- **Two ticket IDs:** IC-460041, IC-460047
- **Pattern:** Four accounts, all small (under $6K ARR each). Three sub-issues: (a) "Slack integration stopped syncing / recognitions no longer post to Slack; sync toggle resets itself" — 6 tickets, 3 accounts (C-0B843542, C-0BA71F12, C-10A56B0F); (b) "Slack app disconnected and re-auth does not stick" — 2 tickets, 2 accounts (C-0BA71F12, C-10A56B0F); (c) "Slack slash command returns an error for everyone on our team" — 5 tickets, 4 accounts (C-0BA71F12, C-8C2E8F00, C-10A56B0F, C-0B843542). The toggle-reset and re-auth-not-sticking issues point to an OAuth/token persistence bug. The slash-command error is a separate failure mode affecting all team members.
- **Recommendation:** The OAuth token persistence issue (toggle resets, re-auth doesn't stick) affects 3 of 4 accounts and is the root cause to fix first — it likely causes the sync-stop symptom too. The slash-command error is a separate bug affecting 4 accounts; investigate the slash command endpoint independently.

---

### Summary ranking by ARR exposure:
| Rank | Theme | ARR Affected | % of Total | Accounts |
|------|-------|-------------|-----------|----------|
| 1 | Invoice & Billing Discrepancies | $832,000 | 52.0% | 1 (C-0E9C27D1) |
| 2 | HRIS Provisioning Failures | $456,000 | 28.5% | 3 |
| 3 | Redemption & Gift Card Failures | $177,300 | 11.1% | 7 |
| 4 | Points Not Posting / Balance Delay | $70,200 | 4.4% | 9 |
| 5 | Slack Integration Failures | $63,400 | 4.0% | 4 |

**Key takeaway:** 80.5% of all ticket ARR ($1,288,000 of $1,598,900) comes from just two themes (invoice billing + HRIS provisioning) and two accounts are responsible for the top theme entirely. The high-volume themes (points not posting, 20 tickets; redemption/gift card, 18 tickets) carry comparatively low ARR risk and are spread across many small accounts — they are broader quality issues, not concentrated churn threats.

Here's the weekly marketing goals update for Q3-2026.

**DS2s**
QTD: 40 | Target: 75 | Delta: -35 | Pace: behind (53.3% of days elapsed, 53.3% of target — on pace by percentage, but absolute gap of 35 with 26 days remaining requires 1.35/day vs 0.61/day actual)

**SQMs**
QTD: 230 | Target: 300 | Delta: -70 | Pace: behind (2.67/day actual vs 3.26/day required over remaining 26 days)

**SQOs**
QTD: 84 | Target: 120 | Delta: -36 | Pace: behind (1.27/day actual vs 1.38/day required)

**closed-lost MIA rate**
QTD: 5/25 = 20.0% | Target: ≤10.0% | Delta: +10.0pp | Pace: behind (rate is double target)

**same-quarter closes**
QTD: 10 | Target: 20 | Delta: -10 | Pace: behind (0.15/day actual vs 0.22/day required)

**active pipeline coverage**
QTD: $3,000,000 | Target: $4,000,000 | Delta: -$1,000,000 | Pace: behind (75% of target, 0.46x coverage of remaining gap at current burn)

---

**What moved this week**

Assumes 7-day week ending the 66th day of the quarter: SQMs added 16.1/day × 7 ≈ 113 net this week (week-over-week inferred from daily rate). SQOs at 1.27/day ≈ 9 net. DS2s at 0.61/day ≈ 4 net. same-quarter closes at 0.15/day ≈ 1 net. The closed-lost MIA rate held at 20% (5 of 25 lost deals MIA) — no improvement. Active pipeline sat at $3M, $1M below the $4M target. Every metric is tracking behind target pace, with the largest absolute gaps in SQMs (-70) and pipeline ($1M shortfall). DS2s and SQOs are proportionally closest to target but still behind on daily run rate.

Q1: Yes. AES-256 encryption at rest. [P1]

Q2: Yes. TLS 1.2 or higher. [P1]

Q3: Yes. SOC 2 Type II, renewed annually; available to prospects under NDA. [P2]

Q4: Duration of contract plus 90 days, then deleted from production systems. [P3]

Q5: Published at trust.bonusly.com. 30 days notice before a new subprocessor is added. [P4]

Q6: Yes, on the Enterprise plan (SAML 2.0 SSO). [P5]

Q7: Daily backups of production databases, encrypted, retained 35 days. [P6]

Q8: Unanswerable from the policy excerpts provided. The excerpts list SOC 2 Type II but do not mention ISO 27001. The SOC 2 report or a security/certifications document would indicate whether ISO 27001 is held.

Q9: Unanswerable from the policy excerpts provided. The excerpts cover security and data practices but not contractual uptime SLAs. The service agreement, MSA, or an SLA/coverage document would state the uptime percentage.

Q10: Unanswerable from the policy excerpts provided. The excerpts do not mention HIPAA or Business Associate Agreements. The BAA policy, security documentation, or legal/compliance contact would confirm whether a BAA can be executed.

Recognition_streaks_v2 — ON. Controls whether StreakTracker records a "give" event (app/models/recognition.rb). Targets segment:beta_companies. Company count from export: 42.

Points_budget_guardrails — ON. Controls whether BudgetService.enforce! runs on giver points (app/services/budget_service.rb). Targeting rule says all_companies. Company count from export: 220.

Slack_dm_nudges — ON. Controls whether SlackDm.send_nudge fires (app/jobs/nudge_job.rb). Targets segment:region_na. Company count from export: 87.

Redeem_flow_redesign — OFF. Controls which redeem controller renders — RedeemV2Component when on, RedeemV1Component when off (app/controllers/redeem_controller.rb). Targets a targeted_list. Company count from export: 12.

Analytics_dashboard_v3 — ON. Controls whether the analytics controller builds AnalyticsV3 instead of the default (app/controllers/analytics_controller.rb). Targets segment:tier_three. Company count from export: 65.

Ms_teams_app_v2 — OFF. Controls whether TeamsAppV2.install runs (app/services/teams_installer.rb). Targets a targeted_list. Company count from export: 9.

Legacy_give_modal — OFF. No code reference in flag_code.md. Targets segment:legacy_plan. Company count from export: 14.

Survey_boosters_q3 — ON. No code reference in flag_code.md. Targets segment:legacy_plan. Company count from export: 7.

Paused_offboard_cleanup — OFF. No code reference in flag_code.md. No targeting rules (empty). Company count from export: 0.

Company-count sum check: 42+220+87+12+65+9+14+7+0 = 456. The export lists 9 flags; counts are used verbatim from the export, not derived from code. No arithmetic inconsistency in the export itself — it is simply added here for a sanity total. Three flags (legacy_give_modal, survey_boosters_q3, paused_offboard_cleanup) have no code excerpt, and paused_offboard_cleanup additionally has no targeting rules and zero companies.

nda-triagePASS 1.00

? The Question

Triage each NDA as GREEN (standard approval), YELLOW (counsel review), or RED (full legal review). Cite the clause that drives each classification by quoting it. Catch embedded non-solicits, non-competes, missing carve-outs, and unusual term or governing law. One line of reasoning per NDA.

cost $0.0005 · 11s · in 15,342 / out 415 tok

✓ green✓ yellow✓ red✓ non_solicit_caught✓ clause_quoted✓ correct_labels

✓ Correct Answer (ground truth)

classifications: {"NDA-1": {"classification": "GREEN", "driving_reason": "standard mutual NDA: 2-year term, standard carve-outs, Delaware law", "driving_clause_quote": "Carve-outs: information that (a) is or becomes p
non_solicit_in: NDA-2
checks: classification_per_nda, clause_quotes_exist_in_document, non_solicit_caught, carveouts_checked
graded checks: green · yellow · red · non_solicit_caught · clause_quoted · correct_labels

Model's actual answer

show the model's full answer

### Triage

**NDA-1 — GREEN**
Clause 3 enumerates five carve-outs (public availability, prior knowledge, third-party receipt, independent development, legal/court-ordered disclosure) and clause 4 appoints standard Delaware governing law with no unusual territorial scope. Nothing embedded: no non-solicit, no non-compete. Standard approval.

**NDA-2 — YELLOW**
Clause 4 is an embedded non-solicitation: "During the term of this Agreement and for eighteen (18) months thereof, neither party shall solicit for employment or hire any employee of the other party with whom it came into contact under this Agreement." Survives 18 months post-term, covers all contacted employees, and applies to both parties — not prohibited, but counsel should confirm it does not exceed the agreement's life plus a customary tail and that "came into contact" is bounded. No non-compete; carve-outs appear standard per clause 2. Counsel review.

**NDA-3 — RED**
Clause 2 is an embedded 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." This is a full non-compete layered on top of a one-way confidentiality in favor of [PARTY C], with no stated carve-outs. Clause 4 places governing law in the Republic of Ireland under exclusive jurisdiction of Irish courts — unusual governing law for a U.S. company (Bonusly) and a non-standard forum. Missing carve-outs (clause 4 of NDA-3 says none are stated) compounds risk. Full legal review.

### Summary
- GREEN: NDA-1 (standard, carve-outs present, Delaware law, no embedded restrictions)
- YELLOW: NDA-2 (embedded 18-month non-solicit; Delaware law, but boundary/scope needs counsel check)
- RED: NDA-3 (embedded 3-year non-compete, no carve-outs, Ireland governing law + exclusive Irish jurisdiction)