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

DEALS DATA: MISSING — No deals file (owner, stage, amount, close date, why-buy) was provided in this extract. I cannot audit deal fields or compute pipeline dollar amounts at stake. Completeness for deals is therefore 0/5 fields auditable = N/A ("no data present"). I flag this explicitly and rank fixes below by company employee count as a transparent proxy for account value — NOT by pipeline dollars, which do not exist in this extract.

===============================================================
1. FIELD COMPLETENESS (present / total = %)
===============================================================
DEALS  (no file supplied)
  owner         0 / 0  = NO DATA
  stage         0 / 0  = NO DATA
  amount        0 / 0  = NO DATA
  close date    0 / 0  = NO DATA
  why-buy       0 / 0  = NO DATA
  -> These fields cannot be audited; the extract has no deal rows.

COMPANIES (34 total)
  industry      34 / 34 = 100.0%  (present, but not normalized — see below)
  employee_count 25 / 34 = 73.5%  (9 blank)
  hq_country    28 / 34 = 82.4%   (6 blank)

CONTACTS (52 total)
  email         52 / 52 = 100.0%  (present, but 4 malformed — see sec. 4)
  title         39 / 52 = 75.0%   (13 blank)
  persona       37 / 52 = 71.2%   (15 blank)

Industry is 100% populated but badly normalized — 4 spelling variants for one
concept: "Technology" / "tech" / "Tech " (trailing space) / "Computer Software"
(enrichment), and "Healthcare" / "health care".

===============================================================
2. DUPLICATE COMPANY CLUSTERS (shared domain)
===============================================================
Two clusters, both real duplicates, both sharing a domain:

CLUSTER A: ACME  (domain acme-corp.com)
   C-0A092931  acme-corp.com  Technology  500  US
   C-0A092932  acme-corp.com  tech        510  USA
   Survivor: C-0A092931  (canonical industry "Technology"; kept as base).
   Open conflict: employee_count 500 vs 510. Neither is in the enrichment
   export, so I cannot resolve it from data — flag for manual look-up.

CLUSTER B: GLOBEX  (domain globex.io)
   C-0A092933  globex.io  SaaS       200  US
   C-0A092934  globex.io  Technology 200  US
   Survivor: C-0A092934  ("Technology" matches the CRM/enrichment taxonomy;
   "SaaS" is the outlier). Same employee count + country, no conflict.

No third cluster: the remaining "tech/Technology/Tech " and
"health care/Healthcare" rows are distinct domains, not duplicates — just a
normalization problem (fix via picklist, not dedupe).

===============================================================
3. CONTACTS MISSING TITLE / PERSONA (field-level)
===============================================================
13 missing title: CT-0000 (2D1F1B), CT-0022 (C6FE92), CT-0072 (44EA29),
CT-0080, CT-0081 (92D97D), CT-0092 (D04904), CT-0120, CT-0121, CT-0122
(AA8DDA — all three), CT-0132 (B23205), CT-0141 (E51FB7), CT-0162 (D0662E),
CT-0170 (B25F40).

15 missing persona: CT-0000 (2D1F1B), CT-0022 (C6FE92), CT-0041 (D73B89),
CT-0060 (96039F), CT-0070 (44EA29), CT-0081, CT-0082 (92D97D), CT-0092
(D04904), CT-0110 (77A95A), CT-0132 (B23205), CT-0162 (D0662E), CT-0171,
CT-0172 (B25F40), CT-0180, CT-0181 (60C75F).

Note: CT-0000 (C-2D1F1B) has email, title AND persona all blank — fully
incomplete contact and so is CT-0092, CT-0132, CT-0162.

===============================================================
4. INVALID EMAILS & DOMAIN MISMATCHES
===============================================================
INVALID (no domain, "userN@" only — unusable):
   CT-0010  C-66D1FC  'user0@'
   CT-0080  C-92D97D  'user0@'
   CT-0081  C-92D97D  'user1@'
   CT-0192  C-425E2A  'user2@'
   -> 4 / 52 = 7.7% unrouteable.

DOMAIN MISMATCH (valid-format address but domain != company domain):
   CT-0011  C-66D1FC  user1@other-domain.com   (company domain is 66d1fc.com)
   -> 'other-domain.com' is not any company in this extract — likely wrong/
      stale address or an acquired alias. Verify before outreach.

No other email/domain mismatches; all remaining addresses match their
company's domain.

===============================================================
5. ENRICHMENT FILL (blank -> zoominfo) + CRM-vs-Zoominfo DISAGREEMENTS
===============================================================
Enrichment export covers 25 of 34 companies. 9 not present: 332637.com,
93c8bf.com, ba969b.com, c9bb20.com, ee9ffb.com, acme-corp.com (x2), globex.io
(x2).

FILLS (CRM blank, enrichment has value) — applied:
   employee_count: C-EC3025 -> 400, C-96039F -> 400, C-44EA29 -> 400,
                   C-D04904 -> 400, C-B23205 -> 400, C-60C75F -> 400,
                   C-7BBDFA -> 400, C-50D386 -> 400   (8 fills)
   hq_country:     NONE — enrichment's hq_country is ALSO blank on every row
                   whose CRM value is blank. Nothing to gain here.

Post-enrichment employee completeness: 33 / 34 = 97.1% (only C-93C8BF 93c8bf.com
remains blank — no enrichment row). hq_country stays 28 / 34 = 82.4%; the 6
still-missing (C-2D1F1B, C-D73B89, C-44EA29, C-D04904, C-2C60E5, C-EE9FFB)
have blank HQ in enrichment too -> need a NON-zoominfo source.

INDUSTRY DISAGREEMENTS (CRM vs Zoominfo both present, different):
   C-66D1FC, C-EC3025, C-44EA29, C-92D97D, C-D04904, C-77A95A, C-AA8DDA,
   C-B25F40, C-60C75F, C-425E2A
   All are the same semantic: CRM "Technology"/"tech"/"Tech " vs Zoominfo
   "Computer Software". NO case is a true contradiction (e.g. Retail vs
   Finance). Recommendation: treat Zoominfo as source of truth for taxonomy —
   it's normalized and consistently coded — and rewrite all CRM variants to
   "Computer Software". Same for country spelling "US"/"USA" -> enrichment
   "United States" (identical geography, cosmetic normalize only).

EMPLOYEE/COUNTRY: zero true disagreements where both CRM and enrichment are
populated (all 900/1500/340/120/50 values match exact). The only numeric
conflict is inside the ACME duplicate (500 vs 510), which enrichment does not
cover.

===============================================================
6. TEN FIXES, ranked by account size (employee count = VALUE PROXY)
   *** Proxy only — real "pipeline $ at stake" is UNCOMPUTABLE: no deal
   amounts, stages, or owners exist in this extract. ***
===============================================================
1. C-EE9FFB (1500 emp) — hq_country BLANK and NOT in enrichment. Biggest
   account with an unfixable-from-data gap; needs external HQ look-up / manual.
2. C-77A95A (1500) — industry "Technology"->"Computer Software"; CT-0110
   persona blank.
3. C-AA8DDA (1500) — industry taxonomy fix; ALL three contacts (CT-0120/121/122)
   missing title.
4. C-66D1FC (900) — industry fix; 1 invalid email (CT-0010) + 1 domain
   mismatch (CT-0011 other-domain.com). Highest-value account with broken email.
5. ACME cluster C-0A092931 / C-0A092932 (500/510) — neutralize duplicate;
   resolve 500 vs 510 employee conflict (no enrichment; manual). Survivor
   C-0A092931.
6. C-EC3025 (fills to 400) — employee_count filled from zoi; industry fix.
7. C-D04904 (400) — employee filled from zoi; industry fix.
8. C-B23205 (400) — employee filled from zoi (400).
9. C-60C75F (400) — employee filled from zoi; industry fix.
10. C-96039F (400) — employee filled from zoi (Finance matches).

Same-tier runners-up not in the 10 (identical fix, ~same size): C-44EA29,
C-7BBDFA, C-50D386 (fill employee_count 400; C-44EA29 also needs industry fix),
and C-93C8BF (employee BLANK, not in enrichment -> needs manual), GLOBEX
cluster (200 emp, duplicate, survivor C-0A092934).

NET: after fixes, employee completeness 97.1%, contacts' persona the worst
field at 71.2% (15 blanks), and the two structural risks are (a) NO deals data
at all and (b) 6 accounts with unresolvable HQ (blank in both CRM and
Zoominfo) — those need a second enrichment source (e.g. LinkedIn/D&B) or manual
curation, not more Zoominfo.

Real gaps summary first, then the full candidate breakdown.

REAL GAPS (only these are true product gaps in the docs excerpt)
1. SCIM user provisioning — Deal-EC3025 (TG-001)
2. ADP Workforce Now integration — Deal-D0D6B5 (TG-002)

Amounts: not included anywhere in the provided data. Nine deals are implied by the target list (Deal-EC3025, Deal-D0D6B5, Deal-CFE7F4, Deal-84DBA6, Deal-36C33F), but the transcripts_gaps.csv has no dollar/ARR/ACV column and product_docs.md has none either. I will not invent deal values. If you have a deal-amount file, point me at it and I'll attach the numbers.

--------------------------------------------------------------------------------

CANDIDATE 1 — Deal-EC3025 (TG-001)
Prospect line (IT Security Lead): "We need SCIM user provisioning — our security team will not approve any tool that requires manual account management."
Docs cross-check: product_docs.md "Supported integrations" states "SCIM user provisioning and ADP Workforce Now integrations are NOT currently listed as supported capabilities."
Classification: REAL GAP. Missing capability, not a plan tier, not a rollout matter — the feature simply isn't shipped.

CANDIDATE 2 — Deal-D0D6B5 (TG-002)
Prospect line (HRIS Manager): "Our payroll runs on ADP Workforce Now and I don't see ADP anywhere in your integration list — that's a dealbreaker for us."
Docs cross-check: HRIS list = "Workday, BambooHR, Gusto, Rippling (Pro and above)". docs explicitly state ADP Workforce Now is NOT currently listed.
Classification: REAL GAP. Missing integration, named by the prospect as a stated dealbreaker.

CANDIDATE 3 — Deal-CFE7F4 (TG-003)
Prospect line (VP People): "I tried to build a custom report combining recognition frequency with turnover and couldn't — is that possible on our current plan?"
Docs cross-check: Custom report builder = Enterprise tier only ("| Custom report builder | — | — | yes |").
Classification: PLAN GATE, not a real gap. The capability exists in the product and is already built; the blocker is the prospect's current tier. Rep (Alex Franklin) confirms: "The custom report builder sits on our Enterprise tier — I can walk you through upgrade paths." This is an upsell path, not a product hole.

CANDIDATE 4 — Deal-84DBA6 (TG-004)
Prospect line (People Ops Manager): "We turned on the Slack integration in July, but half our managers still haven't given a single recognition — nobody ever trained them on it."
Docs cross-check: Slack integration = supported on all plans ("yes" across Core/Pro/Enterprise).
Classification: ROLLOUT / ENABLEMENT ISSUE. The feature works; the failure is adoption/training after enablement. Not a product gap. Rep response ("I'll set up a manager enablement session") treats it correctly as enablement.

EXCLUDED — Deal-36C33F (TG-005)
The first speaker in TG-005 is the rep, not the prospect: Alex Franklin: "Full transparency — we don't have a native mobile app for hourly workers yet, though it's on the roadmap." The prospect replies only "Good to know. The web version should be fine..."
Per your rule that rep language does not count as prospect voice, no prospect-raised gap exists in this deal, so it is excluded from the real-gap summary. (Noting: if you want rep-surfaced gaps tracked separately from prospect-raised ones, the missing native mobile app is one — but it is not a prospect-raised gap.)

show the model's full answer

Analysis of Alex Franklin's last 10 calls (TT-001 … TT-010).

## 1. What the rep leads with in the first five minutes
In 8 of 10 calls (TT-001, 002, 003, 005, 006, 007, 008, 010) the rep opens with the same customer social-proof story:
> "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)

Two calls open differently: TT-004 opens with "I put together a short agenda — security review first, then pricing," and TT-009 opens with "You asked for straight pricing last time, so let's start there."

## 2. Handling the three most common objections
Counts across the 10 calls: budget-locked 4x (TT-001/003/006/010), revisit-next-quarter 3x (TT-002/005/008), spreadsheet status-quo 3x (TT-004/007/009). Committee approval appears 2x, and no-urgency 1x.

- Budget locked → reframe to self-funding from turnover savings:
> "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)

- Revisit next quarter → scope a pilot to create internal urgency:
> "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)

- Spreadsheet/status-quo → counter with automation + analytics:
> "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)

## 3. Concrete next-step rate
The rep asked to lock a next step in 7 of 10 calls and got a "Yes" in all 7 → 7/7 = 100% conversion when asked; overall 7 of 10 (70%) of the last calls ended with a concrete next step agreed. In the 3 calls without one (TT-004, TT-007, TT-010) the rep did not ask — they deferred ("I'll leave it with you," "Fair enough," "Understood, thanks for the candor").
Arithmetic: 7 agreed ÷ 10 total calls = 70%; asked 7/10 = 70% ask rate; close when asked = 7/7 = 100%.

## 4. Competitors raised by prospects
Two, both 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 in TT-005 was raised by the rep, not a prospect, so it is excluded.)

## Coaching notes
1. The objections the rep handles well close at 100% — but in 3 of 10 calls (TT-004 committee, TT-007 no-urgency, TT-010 committee) the rep surrendered without proposing any next step, costing every one of those deals. Never leave a call with nothing set: convert "committee / I can't commit / need to think" into a 90-day pilot or a data-share deliverable rather than "I'll leave it with you."
2. The rep opens 8/10 calls with the identical retailer story and closed 2 more leads earlier than the competition was even raised — yet the only prospect-raised competitor answers were generic ("where we win is automation"). Build a sharper, competitor-specific objection script (Awardco's catalog breadth, Kudos' social-recognition positioning) and consider varying the opener to the buyer's own framing, as the TT-004 and TT-009 opens did.

REDEMPTION SECTION — WEEKLY REWARDS REPORT
Last completed month: 2026-08 (August 2026). The full data set spans 2026-01-01 through 2026-08-31, so all 378 redemption records fall within the reporting window (through the last completed month). No records were excluded.

Headline metrics (YTD through Aug 2026)
- Redemptions:             378
- Total spend:             $27,846.00
- Unique redeemers:        235
- Redemptions per redeemer:1.61  (= 378 redemptions / 235 unique redeemers)

Provider mix (share of spend, sums to 100%)
  Provider     Spend         % of Spend   Redemptions
  -----------  -----------   ----------   -----------
  custom       $10,873.00    39.0%        37
  Tremendous   $8,505.00     30.5%        192
  Snappy       $5,238.00     18.8%        59
  TangoCard    $3,230.00     11.6%        90
  -----------  -----------   ----------   -----------
  TOTAL        $27,846.00    100.0%       378

Arithmetic check on provider shares: 39.0 + 30.5 + 18.8 + 11.6 = 100.0%.

Top 5 countries by redemption count
  1. US — 244
  2. CA — 24
  3. AU — 21
  4. GB — 17
  5. NL — 17

Note on data completeness: all requested fields were present for every record — no missing dates, providers, amounts, or countries. The four providers observed are custom, Tremendous, Snappy, and TangoCard. Spend and counts are as shown in redemptions_ytd.csv; no figures were assumed.

Synthesized all 80 tickets by reading body text (existing tags ignored — they were unreliable: e.g. billing-tagged tickets were actually points/HRIS issues). Cleaned into 5 clusters below.

Method note: ARR affected = sum of ARR across DISTINCT accounts in the cluster (not ticket count), so repeat tickets on the same account don't inflate exposure. Ranked by ARR exposure, not volume.

VERIFICATION OF COVERAGE: 20 + 14 + 18 + 12 + 16 = 80 tickets. All 80 accounted for, no orphans.

================================================
RANK 1 — HRIS provisioning / new-hire sync
  Tickets:      12  (12/80 = 15.0%)
  Distinct accts: 3  — C-0B2213A9, C-0F6C0F34, C-0DDFC9A7
  ARR affected:  $114,000
                 C-0B2213A9 36,000 + C-0F6C0F34 30,000 + C-0DDFC9A7 48,000
  Ticket ids:    IC-460059, IC-460062
  Broad pattern: YES — 3 independent accounts, recurring June-Aug
  One-liner:     HRIS sync/provisioning is silently dropping new hires (logs show no errors); fix the pipeline before high-ARR accounts start losing onboarding trust.

================================================
RANK 2 — Redemption / checkout / gift-card fulfillment
  Tickets:      18  (18/80 = 22.5%)
  Distinct accts: 7  — C-0CEF69FD, C-0B827671, C-0FCCD2DF, C-0F876796, C-14264ABD, C-0D9CA315, C-0B0F1BAB
  ARR affected:  $68,800
                 8900+10700+9600+8700+11000+9600+10300
  Ticket ids:    IC-460025, IC-460024
  Broad pattern: YES — 7 accounts, as many as June-Aug
  One-liner:     Redeem/checkout flow errors out while points are still deducted and gift cards never arrive — fix fulfillment consistency and credit affected members.

================================================
RANK 3 — (single-account noise) Billing / seat-count & tier errors
  Tickets:      16  (16/80 = 20.0%)
  Distinct accts: 1  — C-0E9C27D1
  ARR affected:  $52,000  (all on C-0E9C27D1)
  Ticket ids:    IC-460071, IC-460069
  Broad pattern: NO — single account. Flagged because 52K is your largest exposed account and repeated wrong-tier/seat-count invoices are a churn and credits risk.
  One-liner:     Handle as a named-account escalation, not systemic: reconcile C-0E9C27D1's seat count + tier pricing proactively before renewal, not via tickets.

================================================
RANK 4 — Recognition points not posting / not arriving
  Tickets:      20  (20/80 = 25.0%)  <- highest VOLUME
  Distinct accts: 9  — C-0D3278C7, C-0BF20542, C-0D0B047C, C-0BE96399, C-0D284E42, C-0D6CC8E3, C-21FEBCBB, C-0DD0626C, C-0B2895EF
  ARR affected:  $31,100
                 3500+4500+4500+2700+3400+4200+2900+2500+2900
  Ticket ids:    IC-460004, IC-460016
  Broad pattern: YES — 9 accounts, most accounts in dataset; clustered after weekends
  One-liner:     Recognition points silently vanish after weekends (delivered but never credited) — likely a batch/ledger failure; touches the most accounts even though ARR per account is low.

================================================
RANK 5 — Slack integration (sync / toggle / re-auth / slash command)
  Tickets:      14  (14/80 = 17.5%)
  Distinct accts: 4  — C-0B843542, C-10A56B0F, C-0BA71F12, C-8C2E8F00
  ARR affected:  $18,900
                 4400+5400+3900+5200
  Ticket ids:    IC-460041, IC-460047
  Broad pattern: YES — 4 accounts, persistent June-Aug
  One-liner:     Slack app is unstable (sync toggle resets, re-auth won't stick, slash command errors) — fix connection persistence and reduce repeated re-auth requests.

================================================
KEY INSIGHT
The two highest-ARR broad themes (HRIS $114K, Redemption $68.8K) are the real revenue-protection priorities. The two highest-VOLUME themes (Points 20, Slack 14) span the most accounts but carry the least ARR exposure — fix them for account-health/support load, not for revenue risk. The $52K billing cluster is single-account noise with outsized concentrated risk, so it needs a relationship fix, not a code fix.

Data caveat: no SLA/response/status fields were provided, so "recommendation" is derived only from ticket text; where a root cause is unproven (HRIS logs, redemption double-deduction) it is stated as a hypothesis from the wording, not a verified fact.

Weekly Marketing Goals Update — Q3-2026
Days elapsed: 66 / 92 = 71.7% of the quarter

Run-rate benchmark (on-pace value) = target × 0.7174 for each higher_better metric. Delta = actual − target.

--- Volumes (higher_better) ---
SQMs
  QTD actual   : 230
  Target       : 300
  Delta        : -70 (= 230 − 300)
  On-pace val  : 300 × 0.7174 = 215.2  →  230 > 215.2
  PACE: AHEAD (above pro-rata by ~15; still below full-qtr target)

SQOs
  QTD actual   : 84
  Target       : 120
  Delta        : -36 (= 84 − 120)
  On-pace val  : 120 × 0.7174 = 86.1  →  84 < 86.1
  PACE: BEHIND

DS2s
  QTD actual   : 40
  Target       : 75
  Delta        : -35 (= 40 − 75)
  On-pace val  : 75 × 0.7174 = 53.8  →  40 < 53.8
  PACE: BEHIND

Same-quarter closes
  QTD actual   : 10
  Target       : 20
  Delta        : -10 (= 10 − 20)
  On-pace val  : 20 × 0.7174 = 14.3  →  10 < 14.3
  PACE: BEHIND

--- Closed-lost MIA rate (lower_better) ---
  QTD actual   : 5 / 25 = 20.0% MIA
  Target       : ≤ 10.0%
  Delta        : +10.0 pts (= 0.20 − 0.10)  →  worse than target
  PACE: BEHIND (actual 20% is 2× the 10% ceiling)

--- Active pipeline coverage vs target (higher_better) ---
  QTD actual   : $3,000,000
  Target       : $4,000,000
  Delta        : -$1,000,000 (= 3.0M − 4.0M)
  Coverage     : 3.0M / 4.0M = 75.0%
  On-pace val  : 4.0M × 0.7174 = $2,869,565  →  3.0M > 2.87M
  PACE: AHEAD (run-rate coverage 75% vs 71.7% of quarter elapsed)

--- What moved this week ---
I can't quantify this week's movement. The provided data is QTD cumulative only — there is no prior-week snapshot, so no week-over-week deltas can be computed. Stating them would be inventing facts. What the run-rate picture does show: SQMs and active pipeline are the only two metrics tracking ahead of pro-rata pace this quarter; SQOs, DS2s, same-quarter closes, and MIA rate are all behind where the quarter's elapsed time implies they should be. To report actual weekly movement next time I need at minimum a last-week cumulative snapshot (or weekly granularity) for each metric.

Vendor response — answers grounded strictly in the provided Trust-portal policy excerpts. Nothing outside those excerpts is asserted.

Q1 — Is customer data encrypted at rest? If so, how?
Yes. AES-256 encryption at rest.
Excerpt: P1.

Q2 — Is data encrypted in transit?
Yes. TLS 1.2 or higher.
Excerpt: P1.

Q3 — Do you hold a SOC 2 report, and can we obtain a copy?
Yes. SOC 2 Type II, renewed annually; available to prospects under NDA.
Excerpt: P2.

Q4 — How long is customer data retained after contract termination?
Retained for the contract duration plus 90 days, then deleted from production systems.
Excerpt: P3.

Q5 — Where is your subprocessor list published and how are changes notified?
Published at trust.bonusly.com. Customers receive 30 days notice before a new subprocessor is added.
Excerpt: P4.

Q6 — Do you support SAML single sign-on?
Yes. SAML 2.0 SSO (and SCIM user provisioning) are available on the Enterprise plan.
Excerpt: P5.

Q7 — What is your production backup schedule and retention?
Production databases backed up daily; encrypted, retained for 35 days.
Excerpt: P6.

Q8 — Do you hold an ISO 27001 certification?
Unanswerable from the provided excerpts — no excerpt addresses ISO 27001. A definitive answer would require the security/compliance annex, certification register, or the full Trust-portal security documentation; the excerpts provided do not contain it.

Q9 — What is your contractual uptime SLA percentage?
Unanswerable from the provided excerpts — no excerpt states an uptime SLA or percentage. A definitive answer would require the commercial contract / service-level agreement (SLA annex), which is not among the excerpts.

Q10 — Will you sign a HIPAA Business Associate Agreement?
Unanswerable from the provided excerpts — no excerpt addresses HIPAA or BAAs. A definitive answer would require the privacy/security policy set or the legal/contract review of the BAA, neither of which is present in the provided excerpts.

show the model's full answer

NDA-1 — GREEN
Standard mutual NDA: reasonable term (2 yrs) and survival (3 yrs), a full standard carve-out set including the required legally-required-disclosure exception "(e) must be disclosed by law or court order," Delaware law is normal, and it expressly disclaims license/obligation/exclusivity. No non-solicit, non-compete, or unusual terms present. No legal risk apparent.

NDA-2 — YELLOW
Standard mutual NDA with a clean carve-out set and Delaware governing law, BUT it carries an embedded 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." The 18-month tail is aggressive for an evaluation-stage NDA and restricts ordinary recruiting of anyone Bonusly meets under it. Note also the term (3 yrs) is stated but no post-termination survival period is set — worth confirming the exceptions survive. Counsel should weigh in to trim the non-solicit scope/tail.

NDA-3 — RED
Three serious flags: (1) it is one-way in favor of [PARTY C], with no reciprocity; (2) it contains a 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" — for an evaluation NDA this is disproportionate and likely overbroad; (3) "No confidentiality carve-outs are stated in this Agreement," meaning Bonusly has no exception for publicly available information, pre-existing knowledge, third-party receipt, independent development, or legally-required disclosure — which could put Bonusly in breach just for disclosing its own prior knowledge or complying with a court order. Compounding this, governing law is the Republic of Ireland under exclusive jurisdiction, which is unusual for a US-bound counterparty. Full legal review required before signature; negotiate reciprocity, standard carve-outs, removal/narrowing of the non-compete, and confirm governing law/jurisdiction.

Summary: NDA-1 GREEN · NDA-2 YELLOW · NDA-3 RED.