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

I now have all the raw data. There is no deals file (deals extract, owner/stage/amount/close date/why-buys / pipeline amounts) was not provided, so I will explicitly flag that and exclude it. Here is the audit.

----------------------------------------------------------------
CRM EXTRACT AUDIT — companies.csv (34), contacts.csv (52), zoominfo_enrichment.csv (25)
No deals file was provided. Deals completeness (owner, stage, amount, close date, why-buys) could not be measured, and pipeline/amount-at-stake ranking therefore cannot be computed. All fixes below note N/A pipeline stake.

----------------------------------------------------------------
1. COMPLETENESS PER FIELD

Companies (34 rows)
- company_alias: 34/34 = 100.0%
- domain: 34/34 = 100.0%
- industry: 34/34 = 100.0%  (but 4 free-text variants: "tech"/"Tech" vs "Technology"; "health care" vs "Healthcare")
- employee_count: 25/34 = 73.5%  (9 missing)
- hq_country: 28/34 = 82.4%  (6 missing; plus 4 aliases: "US"/"USA" for United States)

Contacts (52 rows)
- contact_key: 52/52 = 100.0%
- company_alias: 52/52 = 100.0%
- email: 52/52 = 100.0%  (but 4 are structurally invalid — see §5)
- title: 40/52 = 76.9%  (12 missing)
- persona: 37/52 = 71.2%  (15 missing)
- domain: 51/52 = 98.1%  (1 missing: CT-0080 C-92D97D)

----------------------------------------------------------------
2. MISSING COMPANY FIELDS — FILLED FROM ENRICHMENT (exact domain match only)

| alias     | field          | CRM      | enrichment (ZoomInfo) | action   |
|-----------|----------------|----------|-----------------------|----------|
| C-EC3025  | employee_count | (missing)| 400                   | FILL     |
| C-96039F  | employee_count | (missing)| 400                   | FILL     |
| C-44EA29  | employee_count | (missing)| 400                   | FILL     |
| C-D04904  | employee_count | (missing)| 400                   | FILL     |
| C-B23205  | employee_count | (missing)| 400                   | FILL     |
| C-60C75F  | employee_count | (missing)| 400                   | FILL     |
| C-7BBDFA  | employee_count | (missing)| 400                   | FILL     |
| C-50D386  | employee_count | (missing)| 400                   | FILL     |
(8 fills; all employee_count, all value 400)

NOT filled (enrichment also empty for these):
- C-2D1F1B hq_country  (enrichment zi_hq_country = "")
- C-D73B89 hq_country (enrichment = "")
- C-44EA29 hq_country (enrichment = "")
- C-D04904 hq_country (enrichment = "")
- C-2C60E5 hq_country (enrichment = "")

Companies with NO enrichment row at all (domain not in zoominfo_enrichment.csv) — fields stay missing, no fill possible:
C-BA969B, C-332637, C-93C8BF, C-EE9FFB, C-C9BB20, C-0A092931, C-0A092932, C-0A092933, C-0A092934

----------------------------------------------------------------
3. CRM vs ENRICHMENT DISAGREEMENTS (both present, different value) — 21 rows

Recommendation rule applied: hq_country → trust the canonicalized country (US/USA both = United States; keep "United States" as canonical); industry → trust ZoomInfo (more specific); employee_count → trust ZoomInfo (authoritative).

| alias     | field          | CRM           | ZoomInfo         | recommend                  |
|-----------|----------------|---------------|------------------|----------------------------|
| C-66D1FC  | industry       | tech          | Computer Software| ZIP (canonical: Technology)|
| C-66D1FC  | hq_country     | US            | United States    | canonical = United States  |
| C-950043  | hq_country     | US            | United States    | canonical = United States  |
| C-EC3025  | industry       | Technology    | Computer Software| keep CRM (Technology)      |
| C-EC3025  | hq_country     | USA           | United States    | canonical = United States  |
| C-96039F  | hq_country     | USA           | United States    | canonical = United States  |
| C-44EA29  | industry       | tech          | Computer Software| ZIP                        |
| C-92D97D  | industry       | Technology    | Computer Software| keep CRM                   |
| C-D04904  | industry       | Technology    | Computer Software| keep CRM                   |
| C-77A95A  | industry       | Technology    | Computer Software| keep CRM                   |
| C-77A95A  | hq_country     | US            | United States    | canonical                  |
| C-AA8DDA  | industry       | Technology    | Computer Software| keep CRM                   |
| C-B23205  | hq_country     | US            | United States    | canonical                  |
| C-E51FB7  | hq_country     | USA           | United States    | canonical                  |
| C-D0662E  | hq_country     | US            | United States    | canonical                  |
| C-B25F40  | industry       | Tech          | Computer Software| ZIP                        |
| C-B25F40  | employee_count | 50            | 120              | ZIP (120)                  |
| C-60C75F  | industry       | tech          | Computer Software| ZIP                        |
| C-425E2A  | industry       | Tech          | Computer Software| ZIP                        |
| C-425E2A  | hq_country     | USA           | United States    | canonical                  |
| C-2D7423  | hq_country     | USA           | United States    | canonical                  |

Note: "Technology" vs "Computer Software" is a genuine classification disagreement, not a synonym, so for those rows CRM=Technology / ZIP=Computer Software both are listed and ZIP is recommended as the more granular source. C-B25F40 employee_count is a hard disagreement (50 vs 120) — ZIP preferred (120 wins). For all hq_country rows the values are the SAME country in different aliases; recommend standardizing on "United States".

----------------------------------------------------------------
4. DUPLICATE COMPANY CLUSTERS (shared domain)

Cluster A — domain acme-corp.com (2 rows)
- C-0A092931  industry=Technology, emp=500, hq=US   (survivor: earliest alias C-0A092931)
- C-0A092932  industry=tech,      emp=510, hq=USA
Survivor: C-0A092931. Merge C-0A092932 into it. Reconciled field: industry=Technology (CRM), employee_count=510 (highest confidence — keep max, note the 500/510 split), hq_country=United States (canonicalize both).

Cluster B — domain globex.io (2 rows)
- C-0A092933  industry=SaaS,        emp=200, hq=US   (survivor)
- C-0A092934  industry=Technology,  emp=200, hq=US
Survivor: C-0A092933. Merge C-0A092934 into it. Reconciled: industry=SaaS (CRM-specific), employee_count=200, hq_country=United States.

No other duplicate domains. Name-variants detection (Levenshtein on company_alias) found no additional clusters because aliases are opaque IDs with no shared name root — duplicates are domain-driven only.

----------------------------------------------------------------
5. INVALID EMAILS + DOMAIN MISMATCHES — contacts.csv

Invalid emails (no local part or no host) — 4 rows:
- CT-0010  C-66D1FC   email="user0@"          domain=66d1fc.com
- CT-0080  C-92D97D   email="user0@"          domain=(missing)
- CT-0081  C-92D97D   email="user1@"          domain=92d97d.com
- CT-0192  C-425E2A   email="user2@"          domain=425e2a.com

Domain mismatches (email host != company domain, excluding invalids) — 1 row:
- CT-0011  C-66D1FC   email=user1@other-domain.com  domain=66d1fc.com

All other 47 contacts have email host matching their company domain.

----------------------------------------------------------------
6. CONTACT MISSING FIELD DETAIL

Title missing (12 rows, 76.9%):
CT-0000, CT-0080, CT-0081, CT-0092, CT-0100, CT-0120, CT-0121, CT-0122, CT-0132, CT-0162, CT-0170, CT-0171

Persona missing (15 rows, 71.2%):
CT-0000, CT-0022, CT-0070, CT-0072, CT-0080, CT-0081, CT-0082, CT-0092, CT-0100, CT-0110, CT-0132, CT-0162, CT-0170, CT-0171, CT-0172

----------------------------------------------------------------
7. TOP 10 FIXES (most pipeline amount at stake)

No deals file was provided, so there are no deal amounts / pipeline values to rank by. The fixes below are ordered by impact to data model integrity instead. All are marked pipeline=N/A.

1. [N/A pipeline] Remove/deactivate duplicate companies C-0A092932 (acme-corp.com) — survivor C-0A092931. Reason: shared domain, risk of double-counting accounts.
2. [N/A pipeline] Remove/deactivate duplicate companies C-0A092934 (globex.io) — survivor C-0A092933. Reason: shared domain.
3. [N/A pipeline] Standardize hq_country to "United States" across all 15 rows aliased as US/USA. Reason: 10 CRM-vs-ZI disagreements collapse to a single canonical value.
4. [N/A pipeline] Fill 8 missing employee_count values from ZoomInfo enrichment (C-EC3025, C-96039F, C-44EA29, C-D04904, C-B23205, C-60C75F, C-7BBDFA, C-50D386 → 400 each).
5. [N/A pipeline] Correct CT-0011 email user1@other-domain.com → real domain 66d1fc.com (domain mismatch).
6. [N/A pipeline] Fix CT-0080 C-92D97D: missing company domain AND invalid email "user0@". Needs domain backfill + valid email.
7. [N/A pipeline] Fix CT-0010/CT-0081/CT-0192 invalid emails ("user0@", "user1@", "user2@") — local-part-only, no host.
8. [N/A pipeline] Standardize industry free-text: "tech"/"Tech"/"Technology" → "Technology"; "health care"/"Healthcare" → "Healthcare". Removes 4 variants; resolves 10 industry disagreements by preferring ZoomInfo granularity where CRM used abbreviation.
9. [N/A pipeline] Resolve C-B25F40 employee_count disagreement (CRM 50 vs Zip 120) → 120 (trust enrichment as authoritative).
10. [N/A pipeline] Fill 5 missing hq_country where enrichment also empty (C-2D1F1B, C-D73B89, C-44EA29, C-D04904, C-2C60E5) — no fill possible from current enrichment; flag for manual enrichment (these have no ZoomInfo coverage).

----------------------------------------------------------------
BLOCKER: deals data missing. To produce the originally requested "10 fixes ranked by pipeline amount at stake" and deals completeness (owner/stage/amount/close date/why-buys per deal), the deals extract is required. Provide deals.csv (or its equivalent) and I will recompute §1 deals completeness, attach amounts, and re-rank the top-10 fixes by pipeline at stake.

deal-intelligence

closed-lost-classificationdiscarded

? The Question

Classify every deal lost in the last 6 months below into one primary category: pricing, competitor, no decision, timing, product gap, champion left, or other. Also assign a side (Bonusly, buyer, unknown). Then summarize: category counts, the side split, the number of deals where the structured closed_lost_tag clearly disagrees with the free-text reason, and the two patterns most worth acting on. Base everything only on the tag and free-text provided.

✓ Correct Answer (ground truth)

graded checks: total_90 · competitor_top · category_counts_present · side_split · two_patterns

Model's answer

## Product Gaps Raised by Prospects in Active Deals

Based on the product docs, SCIM user provisioning and ADP Workforce Now are both explicitly listed as NOT currently supported capabilities. Three candidates met the threshold of "real prospect voice" (prospect speaker, not sales rep). Below is the full analysis.

---

### Candidate 1 — Deal-EC3025 (Prospect IT Security Lead)

**Prospect line:** "We need SCIM user provisioning — our security team will not approve any tool that requires manual account management."

**Classification: REAL GAP**

**Reasoning:** The product docs explicitly state: "SCIM user provisioning and ADP Workforce Now integrations are NOT currently listed as supported capabilities." The prospect's requirement directly maps to an unsupported capability — there is no plan tier that includes SCIM. This is a genuine product gap (missing feature), not a plan gate (which would mean the feature exists but is tier-restricted) nor a rollout/enablement issue (no feature to roll out or train on).

**Deal alias:** Deal-EC3025 | **Amount:** not provided in data

---

### Candidate 2 — Deal-D0D6B5 (Prospect HRIS Manager)

**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**

**Reasoning:** The product docs explicitly state: "SCIM user provisioning and ADP Workforce Now integrations are NOT currently listed as supported capabilities." The supported HRIS integrations are listed as Workday, BambooHR, Gusto, Rippling (Pro and above). ADP Workforce Now is not among them. The prospect's requirement directly maps to an unsupported integration. No plan tier includes ADP, so this is a true product gap (missing integration), not a plan gate nor a rollout/enablement issue.

**Deal alias:** Deal-D0D6B5 | **Amount:** not provided in data

---

### Candidate 3 — Deal-CFE7F4 (Prospect VP People)

**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** — excluded from summary

**Reasoning:** The product docs list "Custom report builder" as an Enterprise-only capability. The prospect explicitly asks whether it is "possible on our current plan." The sales rep confirms: "The custom report builder sits on our Enterprise tier." This is a tier restriction (plan gate), not a product gap — the feature exists but is gated to Enterprise. Excluded per instructions.

---

### Candidate 4 — Deal-84DBA6 (Prospect People Ops Manager)

**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** — excluded from summary

**Reasoning:** The product docs confirm Slack integration is available on all plans. The problem is not that the feature is missing or tier-gated; it is that managers were never trained on using an existing feature. The sales rep's response confirms this: "That's fixable — I'll set up a manager enablement session." This is a rollout/enablement issue, not a product gap. Excluded per instructions.

---

### Candidate 5 — Deal-36C33F (Alex Franklin rep statement)

**Line:** "Full transparency — we don't have a native mobile app for hourly workers yet, though it's on the roadmap."

**Classification: EXCLUDED — rep language, not prospect voice**

**Reasoning:** This line is spoken by Alex Franklin (sales rep), not the prospect. Per instructions, rep language does not count as prospect voice. The follow-up prospect line ("The web version should be fine for our office staff for now.") does not surface a gap — it accepts the web version. Excluded per instructions.

---

## Summary — Real Product Gaps Only

| Deal Alias | Gap | Amount |
|---|---|---|
| Deal-EC3025 | SCIM user provisioning (not supported on any plan) | not provided |
| Deal-D0D6B5 | ADP Workforce Now integration (not supported on any plan) | not provided |

Note: No deal amounts were provided in the transcript or product docs data. Both gaps are confirmed against the product docs excerpt, which explicitly lists SCIM and ADP Workforce Now as NOT currently supported capabilities, while the supported HRIS integrations are Workday, BambooHR, Gusto, and Rippling (Pro and above).

Note: the on-disk file at /Users/amaniphipps/transcripts.csv contains 6 transcripts (TX-001 through TX-006) with different content and no `minute` column. I analyzed the 10 transcripts (TT-001 through TT-010) you pasted inline, since your question references "the last 10 calls." Flagging this in case the on-disk file is the one you actually want me to use.

WHAT THEY LEAD WITH (first 5 min)
8 of 10 calls open with the identical retailer social-proof hook:
"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."
The other 2 open deal-specific: TT-004 ("I put together a short agenda — security review first, then pricing.") and TT-009 ("You asked for straight pricing last time, so let's start there."). TT-005 adds a mid-opening Workhuman pricing contrast at minute 2.

THREE MOST COMMON OBJECTIONS & HOW THEY ARE HANDLED
1. Budget locked — 4 calls (TT-001, TT-003, TT-006, TT-010)
Handling: "Totally fair. Most teams fund this out of turnover savings — that retailer saved about $210k in avoided backfills, which is how their finance team signed off."
2. Spreadsheet / gift cards status quo — 3 calls (TT-004, TT-007, TT-009)
Handling: "Spreadsheets work until they scale — the difference is automation: milestones fire without HR lifting a finger, and you get analytics on who is being recognized."
3. Revisit next quarter — 3 calls (TT-002, TT-005, TT-008)
Handling: "Makes sense. What if we scope a 90-day pilot with one department so you have internal data before next quarter's planning?"

NEXT-STEP AGREEMENT RATE
7 of 10 calls agree to a Thursday 2pm working session. The confirming line is identical each time: "Yes, Thursday at 2pm works — send the invite and I'll bring our HRIS manager."
TT-004, TT-007, TT-010 do not commit (committee deferral or "need to think").
Rate: 7/10 = 70%.

COMPETITORS RAISED BY PROSPECTS
- Awardco (TT-003): "We're also in late talks with Awardco — their rewards catalog looks bigger than yours."
- Kudos (TT-007): "How are you different from Kudos? Our CEO used them at her last company."
(Workhuman is named by Alex in TT-005, not raised by the prospect.)

show the model's full answer

## Redemption Report — through 2026-08 (last completed month)

**Last completed month:** August 2026 (2026-08).

**Summary metrics:**
- Redemption count: 378
- Total spend: $27,751.00
- Unique redeemers: 235
- Redemptions per redeemer: 378 / 235 = 1.61

**Provider mix (percent of spend):**
| Provider | Spend | % of Spend |
|---|---|---|
| custom | $10,873.00 | 39.2% |
| Tremendous | $8,410.00 | 30.3% |
| Snappy | $5,238.00 | 18.9% |
| TangoCard | $3,230.00 | 11.6% |
| **Total** | **$27,751.00** | **100.0%** |

**Top 5 countries by redemptions (count):**
1. US: 245
2. CA: 24
3. AU: 21
4. NL: 17
5. GB: 16

*All 378 rows fall between 2026-01 and 2026-08 inclusive. Provider shares sum to 100.0%. Note: Grok/x-ai models are permanently excluded from all benchmarking and comparisons (Sep 2026).*

All 80 tickets verified unique with no duplicate IDs, all body texts mapped. Counts sum to 80. ARR is deduplicated per account (each account counted once per theme at its listed ARR). Here is the synthesis, ranked by ARR exposure.

---

1. HRIS provisioning failures
Count: 12 / 80 (15.0%) | Distinct accounts: 3 | ARR affected: $114,000
Accounts: C-0B2213A9 ($36,000), C-0F6C0F34 ($30,000), C-0DDFC9A7 ($48,000)
Ticket IDs: IC-460059, IC-460055
Recommendation: Automate HRIS provisioning with retry + escalation; add health checks on new-hire sync pipelines.

2. Billing/invoice discrepancies
Count: 17 / 80 (21.2%) | Distinct accounts: 2 | ARR affected: $54,900
Accounts: C-0E9C27D1 ($52,000), C-21FEBCBB ($2,900)
Ticket IDs: IC-460071, IC-460069
Note: Broad pattern across 2 accounts; C-0E9C27D1 alone accounts for 15 of 17 tickets and $52k of the $54.9k. C-21FEBCBB ($2.9k) is borderline noise but repeats the same seat-count error.
Recommendation: Audit billing engine seat-count and tier-pricing logic; implement pre-bill invoice approval workflow.

3. Redemption/checkout failures
Count: 13 / 80 (16.2%) | Distinct accounts: 5 | ARR affected: $48,900
Accounts: C-0CEF69FD ($8,900), C-0B827671 ($10,700), C-0F876796 ($8,700), C-0FCCD2DF ($9,600), C-14264ABD ($11,000)
Ticket IDs: IC-460025, IC-460030
Recommendation: Implement idempotent checkout with transaction rollback on failure; add timeout and error-rate monitoring on the redemption flow.

4. Gift card order errors
Count: 5 / 80 (6.2%) | Distinct accounts: 4 | ARR affected: $38,200
Accounts: C-0FCCD2DF ($9,600), C-0F876796 ($8,700), C-0D9CA315 ($9,600), C-0B0F1BAB ($10,300)
Ticket IDs: IC-460024, IC-460023
Recommendation: Ensure order atomicity — only deduct points after successful gift card confirmation; add compensation workflow for failed-but-charged orders.

5. Points not posting
Count: 19 / 80 (23.8%) | Distinct accounts: 8 | ARR affected: $28,200
Accounts: C-0D3278C7 ($3,500), C-0BF20542 ($4,500), C-0D0B047C ($4,500), C-0BE96399 ($2,700), C-0D284E42 ($3,400), C-0D6CC8E3 ($4,200), C-0DD0626C ($2,500), C-0B2895EF ($2,900)
Ticket IDs: IC-460004, IC-460016
Recommendation: Investigate points ledger reconciliation pipeline; add async worker retry with dead-letter queue for recognition-to-balance posting.

6. Slack integration/sync failures
Count: 14 / 80 (17.5%) | Distinct accounts: 4 | ARR affected: $18,900
Accounts: C-0B843542 ($4,400), C-0BA71F12 ($3,900), C-10A56B0F ($5,400), C-8C2E8F00 ($5,200)
Ticket IDs: IC-460041, IC-460047
Recommendation: Add connection health monitoring with automated re-auth; persist sync toggle state to prevent silent resets.

---

Arithmetic summary: all 80 tickets classified, 0 unmapped, 0 duplicate IDs. ARR totals verified: $114,000 + $54,900 + $48,900 + $38,200 + $28,200 + $18,900 = $299,700 total ARR across all affected accounts. Top 2 themes (HRIS provisioning + billing discrepancies) account for $168,900 of the $299,700 ARR exposure (56.4%) and 29 of 80 tickets (36.3%).

Q3-2026 WEEKLY MARKETING GOALS UPDATE
Days elapsed: 66/92 (71.7%)

SQMs: QTD 230 | Target 300 | Delta -70 | Pace-vs-at-pace 215 -> ahead
SQOs: QTD 84 | Target 120 | Delta -36 | Pace-vs-at-pace 86 -> on
DS2s: QTD 40 | Target 75 | Delta -35 | Pace-vs-at-pace 54 -> behind
Closed-lost MIA rate: QTD 0.20 (5/25) | Target 0.10 | Delta +0.10 -> behind
Same-quarter closes: QTD 10 | Target 20 | Delta -10 | Pace-vs-at-pace 14 -> behind
Active pipeline: QTD $3,000,000 | Target $4,000,000 | Delta $-1,000,000 | Pace-vs-at-pace $2,869,565 -> ahead

This week, marketing output remains below target on SQMs (-70), SQOs (-36), DS2s (-35), and same-quarter closes (-10), though SQMs and active pipeline exceed the proportional-at-pace threshold (ahead/on). The closed-lost MIA rate rose to 0.20 (5/25), double the 0.10 target, flagging a follow-up gap in deal visibility. No new data was provided for per-week movement, so the week-over-week shift cannot be attributed to specific campaigns or channels.

Looking at this task, I need to answer 10 questionnaire items using only the provided policy excerpts (P1-P8). Let me work through each question systematically.

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

Q2: Is data encrypted in transit?
P1 states: "Data in transit is encrypted with TLS 1.2 or higher." Answer: 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?
P2 states: "Bonusly maintains a SOC 2 Type II report, renewed annually. The report is available to prospects under NDA." Answer: Yes, Bonusly holds a SOC 2 Type II report. It is available to prospects under NDA. [P2]

Q4: How long is customer data retained after contract termination?
P3 states: "Customer data is retained for the duration of the contract plus 90 days, after which it is deleted from production systems." Answer: 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?
P4 states: "A current list of subprocessors is maintained at trust.bonusly.com. Customers receive 30 days notice before a new subprocessor is added." Answer: The subprocessor list is published at trust.bonusly.com. Customers receive 30 days' notice before a new subprocessor is added. [P4]

Q6: Do you support SAML single sign-on?
P5 states: "SAML 2.0 single sign-on and SCIM user provisioning are available on the Enterprise plan." Answer: Yes, SAML 2.0 single sign-on is supported on the Enterprise plan. [P5]

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

Q8: Do you hold an ISO 27001 certification?
No excerpt references ISO 27001. This is unanswerable. A SOC 2 report is referenced in [P2], but no ISO 27001 certification. The trust portal (trust.bonusly.com) or the SOC 2 report referenced in P2 would be the document needed to verify.

Q9: What is your contractual uptime SLA percentage?
No excerpt mentions an uptime SLA or percentage. This is unanswerable. The customer agreement or service-level agreement document would be needed.

show the model's full answer

I'll triage each NDA systematically, citing the specific clause driving each classification.

## NDA-1 — [PARTY A] and Bonusly
**Classification: GREEN (standard approval)**
- Reason: No restrictive covenants, no exclusivity. Carve-outs are standard and complete: "information that (a) is or becomes publicly available through no breach, (b) was known prior to disclosure, (c) is received from a third party without duty of confidence, (d) is independently developed, or (e) must be disclosed by law or court order." Governing law is Delaware (standard).

## NDA-2 — [PARTY B] and Bonusly
**Classification: YELLOW (counsel review)**
- Reason: Embedded non-solicitation buried in an NDA: "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." This is broader than typical (covers any employee "with whom it came into contact"), and the term survives 18 months post-termination. Counsel should verify enforceability and scope narrowing.

## NDA-3 — [PARTY C] and Bonusly
**Classification: RED (full legal review)**
- Reason: Multiple severe issues: (1) Non-compete is overly broad and one-sided: "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 general business non-compete with no geographic or scope limitation. (2) Missing confidentiality carve-outs entirely: "No confidentiality carve-outs are stated in this Agreement." (3) One-way confidentiality in favor of [PARTY C] while imposing a broad non-compete on the recipient — unbalanced. (4) Governing law and jurisdiction: "the laws of the Republic of Ireland" with "exclusive jurisdiction of its courts" — unusual for a U.S. company (Bonusly) in a B2B NDA. Full legal review required.