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

Summary of data status
- Data provided: companies.csv, contacts.csv, zoominfo_enrichment.csv. No deals.csv was provided.
- Action: audit using only provided data; do not invent values.

What is missing
- Deals: No deals/opp data present. Cannot compute per-field completeness or pipeline value for deals. Explicitly state: deals data is missing.
- Some company rows are missing HQ country or employee_count in CRM; enrichment provides matches for many of these, which I propose to align where appropriate.
- Some contacts have missing title or persona; email is present for all rows in this dataset.

Completeness by field (based on provided data)
- Deals
  - owner: data missing (no deals.csv)
  - stage: data missing
  - amount: data missing
  - close date: data missing
  - why-buys: data missing
  - Completeness: not computable from current data (0% demonstrable completion due to no records)

- Companies (33 total rows)
  - industry: 33/33 complete (100%)
  - employee_count: 23/33 complete ≈ 69.7%
  - HQ country: 27/33 complete ≈ 81.8%

- Contacts (52 data rows)
  - email: 52/52 complete = 100%
  - title: 34/52 complete ≈ 65.4%
  - persona: 35/52 complete ≈ 67.3%

Notes on duplicates and aliases
- Duplicate company clusters by shared domain:
  - acme-corp.com cluster
    - Aliases: C-0A092931 and C-0A092932
    - Survivor: C-0A092932 (domain acme-corp.com) with 510 employees vs 500 for the other; both CRM rows show domain acme-corp.com.
  - globex.io cluster
    - Aliases: C-0A092933 and C-0A092934
    - Survivor: pick one; both have 200 employees. I propose C-0A092934 as survivor for consistency in a single row (domain globex.io).
- All other domains appear unique in the CRM extract.

Invalid emails and domain mismatches (contacts.csv)
- Invalid emails: None observed (all emails are syntactically valid in this dataset).
- Domain mismatches (email domain vs domain column):
  - CT-0011: email user1@other-domain.com vs domain 66d1fc.com -> domain mismatch.
- Summary: 1 domain mismatch; 0 invalid emails.

Enrichment alignment (fill missing company fields only where enrichment has a match)
- What enrichment provides for domain matches ( zi_* fields ):
  - ec3025.com (C-EC3025): enrichment shows industry Computer Software, employee_count 400, HQ country United States. CRM has industry Technology; employee_count missing; HQ country USA. Action: fill employee_count = 400. Do not override industry (CRM currently lists Technology) unless explicitly requested to harmonize; note the discrepancy.
  - 96039f.com (C-96039F): enrichment Finance 400 United States. CRM already has Finance; fill employee_count = 400.
  - 44ea29.com (C-44EA29): enrichment Computer Software 400. CRM lists Tech; fill employee_count = 400.
  - d04904.com (C-D04904): enrichment Computer Software 400. CRM lists Technology; fill employee_count = 400.
  - 60c75f.com (C-60C75F): enrichment Computer Software 400 United States. CRM employee_count missing; fill employee_count = 400.
  - 7bbdfa.com (C-7BBDFA): enrichment health care 400 Canada. CRM has health care but employee_count missing; fill employee_count = 400.
  - 50d386.com (C-50D386): enrichment health care 400 Canada. CRM has health care but employee_count missing; fill employee_count = 400.
  - b23205.com (C-B23205): enrichment Healthcare 400 United States. CRM has Healthcare; employee_count missing; fill employee_count = 400.
  - 2c60e5.com (C-2C60E5): enrichment Healthcare 340. CRM has Healthcare 340; already aligned (no fill needed but alignment check passes).

Notes on how to interpret enrichment vs CRM
- When enrichment provides a field value and CRM has a blank for that field, the enrichment value can be applied (as above) to improve completeness.
- When enrichment provides a different value for a field that CRM already has, I did not override CRM value (per instruction to fill missing fields only; when disagreement occurs, list both and suggest source). For example:
  - C-EC3025: CRM industry is Technology vs enrichment says Computer Software. I did not overwrite; I list both and recommend source of truth (enrichment vs CRM policy).
  - acme-corp.com duplicates (C-0A092931 vs C-0A092932): enrichment does not cover these domains; proceed with CRM as the source, and use the survivor rule above for deduplication.

Proposed fixes (top10 fixes with the most pipeline value at stake)
Note: I cannot compute actual pipeline amounts because deals data is not provided. I instead prioritize fixes that would likely unlock the largest revenue value based on enrichment signals and data impact. Each item cites the exact alias(es) or cluster involved.

1) Resolve domain mismatch in contacts
- Alias: CT-0011
- Issue: email user1@other-domain.com, domain 66d1fc.com
- Action: verify authoritative source for contact’s email/domain; align CRM contact to a single authoritative domain. This affects potential win-rate for the 66d1fc.com account.

2) Merge acme-corp.com duplicates (CRM cluster)
- Duplicates: C-0A092931 and C-0A092932
- Survivor: C-0A092932 (510 employees)
- Action: consolidate to a single canonical record for acme-corp.com with domain acme-corp.com; choose one employee_count value and align related contacts.

3) Merge globex.io duplicates (CRM cluster)
- Duplicates: C-0A092933 and C-0A092934
- Survivor: C-0A092934 (tie on employees; select one)
- Action: consolidate to a single canonical record for globex.io; align fields and contacts.

4) Enrich C-EC3025 with employee_count from enrichment
- Alias: C-EC3025
- Action: set employee_count = 400 (enrichment value). Domain ec3025.com; helps reflect potential larger deal size.

5) Enrich C-96039F with employee_count from enrichment
- Alias: C-96039F
- Action: set employee_count = 400 (enrichment value).

6) Enrich C-44EA29 with employee_count from enrichment
- Alias: C-44EA29
- Action: set employee_count = 400 (enrichment value).

7) Enrich C-D04904 with employee_count from enrichment
- Alias: C-D04904
- Action: set employee_count = 400 (enrichment value).

8) Enrich C-60C75F with employee_count from enrichment
- Alias: C-60C75F
- Action: set employee_count = 400 (enrichment value).

9) Enrich C-7BBDFA with employee_count from enrichment
- Alias: C-7BBDFA
- Action: set employee_count = 400 (enrichment value). (Note: CRM shows domain 7bbdfa.com and health care; enrichment provides 400.)

10) Enrich C-50D386 with employee_count from enrichment
- Alias: C-50D386
- Action: set employee_count = 400 (enrichment value).

Additional recommended actions (quick wins, non-top10)
- For any other CRM rows where enrichment has a value for employee_count but CRM is blank (e.g., C-2D1F1B row11? and others), apply enrichment values where domain matches.
- Consider updating HQ country strings to a consistent canonical form (e.g., United States vs USA) across CRM to reduce downstream deduplication issues.
- Maintain a canonical-source policy for industry values when CRM vs enrichment disagree (list both in a note and Corr. source).

Citations to exact aliases and clusters
- Duplicates and survivors:
  - acme-corp.com cluster survivors: C-0A092932 (acme-corp.com) selected over C-0A092931 due to higher employee_count (510 vs 500).
  - globex.io cluster survivor: C-0A092934 (globex.io) selected.
- Domain mismatch example:
  - CT-0011 (domain 66d1fc.com) has email user1@other-domain.com; domain mismatch.

Arithmetic basics shown
- Company field completeness for employee_count:
  - 23 out of 33 non-empty -> 23/33 ≈ 0.697 => 69.7%
- Company field completeness for HQ country:
  - 27 out of 33 non-empty -> 27/33 ≈ 0.818 => 81.8%
- Industry completeness (33 of 33) -> 100%
- Contacts completeness:
  - Email completeness: 52/52 = 100%
  - Title completeness: 34/52 ≈ 65.4%
  - Persona completeness: 35/52 ≈ 67.3%

Deliverable notes
- I have not invented any values; all enrichment-derived fills are clearly labeled as suggestions based on domain matches.
- If you want, I can export a compact delta summary or produce a small patch to merge duplicates and apply enrichment fills in a controlled way.

Candidates and classifications
- Deal-EC3025
  - Prospect line: "We need SCIM user provisioning — our security team will not approve any tool that requires manual account management."
  - Classification: real gap
  - Amount: not provided
  - Rationale (product docs): Bonusly product docs excerpt shows SCIM user provisioning is NOT listed among supported capabilities.
  - Alias: Deal-EC3025

- Deal-D0D6B5
  - 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
  - Amount: not provided
  - Rationale (product docs): HRIS integrations listed in docs include Workday, BambooHR, Gusto, Rippling (Pro and above); ADP Workforce Now is not listed as supported.
  - Alias: Deal-D0D6B5

- Deal-36C33F
  - Prospect line: "Full transparency — we don't have a native mobile app for hourly workers yet, though it's on the roadmap."
  - Classification: real gap
  - Amount: not provided
  - Rationale (product docs): The docs do not mention a native mobile app, and roadmap status implies current absence of that capability.
  - Alias: Deal-36C33F

Summary of real gaps
- Deal-EC3025 — "We need SCIM user provisioning — our security team will not approve any tool that requires manual account management." Amount: not provided.
  - Rationale: SCIM provisioning is not listed as a supported capability in the product docs excerpt.

- Deal-D0D6B5 — "Our payroll runs on ADP Workforce Now and I don't see ADP anywhere in your integration list — that's a dealbreaker for us." Amount: not provided.
  - Rationale: ADP Workforce Now integrations are not listed as supported capabilities in the product docs excerpt.

- Deal-36C33F — "Full transparency — we don't have a native mobile app for hourly workers yet, though it's on the roadmap." Amount: not provided.
  - Rationale: No native mobile app capability is documented; roadmap status indicates current absence.

Arithmetic
- Total candidates surfaced: 3
- Real gaps identified: 3
- Real-gap share: 3/3 = 1.00 → 100%

Notes
- Amounts for all deals are not provided in the data you supplied. If you want, I can flag these as missing in a follow-up and track any updates to deal values.

Lead with (Deal-D348E1):
"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."

Objections (three most common):
- Budget constraint (Deal-D348E1): "Honestly, budget is locked until next fiscal year — I can't add a new line item right now."
- Preference for current process (Deal-403845): "We already do recognition with a spreadsheet and quarterly gift cards — why would we change?"
- Timing / next-quarter pressure (Deal-5408B0): "This is good, but can we revisit it next quarter? Open enrollment starts in October and we're underwater."

Concrete next steps rate:
Total calls analyzed: 10
Concrete next-step agreed: 7
Rate = 7/10 = 0.7 = 70%

Competitors raised:
- Awardco (Deal-547B2B): "We're also in late talks with Awardco — their rewards catalog looks bigger than yours."
- Kudos (Deal-EDC141): "How are you different from Kudos? Our CEO used them at her last company."

Two coaching notes:
- Prospects frequently push to revisit later or wait on budget; to counter, lock a concrete, time-bound next step (e.g., a 90-day pilot or working session with a fixed date) in the reply.
- Competitor mentions appear (Awardco, Kudos); develop a crisp differentiation response centered on automation and analytics, with a ready ROI example.

Last completed month: 2026-08 (August 2026)

Redemption count: 36
Spend: 3,062.00 USD
Unique redeemers: 34

Redemptions per redeemer:
U-4A3BD5: 1
U-011FB3: 1
U-F225B1: 1
U-13BD80: 1
U-5CDABE: 1
U-07742B: 1
U-4C2367: 1
U-BB275E: 1
U-046F5A: 1
U-B2EC03: 1
U-AD4EFE: 1
U-9F408C: 1
U-EF4179: 1
U-40A8B7: 1
U-4E67CE: 1
U-C1FC80: 1
U-0D807F: 2
U-4A0FE6: 2
U-9C436E: 1
U-2464AF: 1
U-1650B9: 1
U-1A7ABE: 1
U-517760: 1
U-B63C58: 1
U-1131A5: 1
U-A9D86A: 1
U-78E9EE: 1
U-9427B4: 1
U-464C79: 1
U-5E561C: 1
U-4E4CE5: 1
U-86C912: 1
U-208525: 1
U-8B14D5: 1

Provider mix (percent of spend):
TangoCard: 16%
Tremendous: 29%
custom: 35%
Snappy: 20%
Note: sums to 100%.

Top 5 countries by redemptions:
US: 22
CA: 6
AU: 2
SG: 2
CH: 1

Total ARR (quarter) from intercom_tickets.csv: 1,383,300.00

Invoicing and seat-count discrepancies
- Count: 14
- ARR affected: 728,000
- Share: 728000 / 1383300 * 100 = 52.63%
- Distinct accounts: C-0E9C27D1
- ARR share exact: 52.63%
- Two ticket IDs: IC-460071, IC-460069
- Accounts involved (sample): C-0E9C27D1
- Recommendation: Audit invoice discrepancies and seat-count misalignments; implement automated validation for seat counts and pricing tiers.

HRIS provisioning and new-hire provisioning failures
- Count: 9
- ARR affected: 354,000
- Share: 354000 / 1383300 * 100 = 25.59%
- Distinct accounts: C-0B2213A9, C-0DDFC9A7, C-0F6C0F34
- ARR share exact: 25.59%
- Two ticket IDs: IC-460059, IC-460058
- Accounts involved (sample): C-0B2213A9, C-0DDFC9A7, C-0F6C0F34
- Recommendation: Fix HRIS provisioning and new-hire sync failures; ensure HRIS sync runs daily and auto-provisions new hires.

Redemption/gift card failures and gift card emails
- Count: 18
- ARR affected: 177,300
- Share: 177300 / 1383300 * 100 = 12.82%
- Distinct accounts: C-0B0F1BAB, C-0B827671, C-0CEF69FD, C-0D9CA315, C-0F876796, C-0FCCD2DF, C-14264ABD
- ARR share exact: 12.82%
- Two ticket IDs: IC-460025, IC-460030
- Accounts involved (sample): C-0B0F1BAB, C-0B827671, C-0CEF69FD
- Recommendation: Stabilize redemption flow and gift-card email delivery; monitor checkout failures and email delivery events for root causes.

Points posting and balance update delays
- Count: 19
- ARR affected: 66,000
- Share: 66000 / 1383300 * 100 = 4.77%
- Distinct accounts: C-0B2895EF, C-0BE96399, C-0BF20542, C-0D0B047C, C-0D284E42, C-0D3278C7, C-0D6CC8E3, C-0DD0626C, C-21FEBCBB
- ARR share exact: 4.77%
- Two ticket IDs: IC-460004, IC-460016
- Accounts involved (sample): C-0B2895EF, C-0BE96399, C-0BF20542
- Recommendation: Investigate and fix posting delays; ensure balance updates occur promptly after recognitions.

Slack integration and Slack command reliability
- Count: 13
- ARR affected: 58,000
- Share: 58000 / 1383300 * 100 = 4.19%
- Distinct accounts: C-0B843542, C-0BA71F12, C-10A56B0F, C-8C2E8F00
- ARR share exact: 4.19%
- Two ticket IDs: IC-460041, IC-460047
- Accounts involved (sample): C-0B843542, C-0BA71F12, C-10A56B0F
- Recommendation: Stabilize Slack integration and slash-command reliability; address auth/token refresh issues and persistent sync toggles.

Weekly GTM update for Q3-2026 (days elapsed: 66 of 92)

SQMs: QTD_actual=230; Target=300; Delta=-70; Pace=ahead by 14.78 (pro-rated target 215.22)
SQOs: QTD_actual=84; Target=120; Delta=-36; Pace=behind by 2.09 (pro-rated target 86.09)
DS2s: QTD_actual=40; Target=75; Delta=-35; Pace=behind by 13.80 (pro-rated target 53.80)
closed_lost_mia_rate: QTD_actual=0.20; Target=0.10; Delta=+0.10; Pace=ahead by 0.1283 (12.83 pp) vs pro-rated target 0.07174
same_quarter_closes: QTD_actual=10; Target=20; Delta=-10; Pace=behind by 4.35 (pro-rated target 14.35)
active_pipeline: QTD_actual=3,000,000; Target=4,000,000; Delta=-1,000,000; Pace=ahead by 130,434.78 (pro-rated target 2,869,565.22)

What moved this week: SQMs are ahead of pro-rated pace by about 14.8 units, keeping a modest lead against the pro-rated target, while SQOs and DS2s remain behind pace by roughly 2.1 and 13.8 units respectively. The same-quarter closes trail pro-rated pace by about 4.35 closes, and the closed-lost MIA rate sits 0.10 above target, though the MIA pace is running about 12.8 percentage points ahead of the elapsed-time target. The active pipeline is ahead of pro-rated pace by about 130k, indicating potential upside if the current trajectory continues.

Q1: Yes. Data encrypted at rest using AES-256. [P1]

Q2: Yes. Data encrypted in transit with TLS 1.2 or higher. [P1]

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

Q4: Retained for the duration of the contract plus 90 days; after which it is deleted from production systems. Arithmetic: retention_days = contract_duration_days + 90. [P3]

Q5: Subprocessor list published at trust.bonusly.com; changes notified with 30 days notice before a new subprocessor is added. [P4]

Q6: Yes. SAML 2.0 single sign-on is available on the Enterprise plan. [P5]

Q7: Production backups daily; backups encrypted and retained for 35 days. [P6]

Q8: Unanswerable. ISO 27001 certification status is not mentioned in policy_excerpts.md. Document that would answer: ISO 27001 certification status. [P1, P2, P3, P4, P5, P6, P7, P8]

Q9: Unanswerable. Contractual uptime SLA percentage is not mentioned in policy_excerpts.md. Document that would answer: uptime SLA percentage. [P1, P2, P3, P4, P5, P6, P7, P8]

Q10: Unanswerable. HIPAA Business Associate Agreement status is not mentioned in policy_excerpts.md. Document that would answer: HIPAA BAA availability/terms. [P1, P2, P3, P4, P5, P6, P7, P8]

ops-maintenance

skill-file-reconciliationPASS 1.00

? The Question

Reconcile the skill set below against its manifest. Find and report (with severity CRITICAL/WARNING/INFO and an action type TRIM_DESC, UPDATE_BODY, DELETE_SKILL, MERGE, or REVIEW): (1) any two skills whose ALWAYS-trigger phrases overlap/duplicate, (2) any circular delegation chain between skills (name it), (3) any delegation target that does not exist (dangling, name it), (4) any version conflict and which skill should survive, (5) how many manifest descriptions exceed 1,024 characters, (6) any hardcoded page ids, dates, or person names in skill bodies, (7) manifest drift in BOTH directions (files with no manifest row, and manifest rows with no file). Make one proposal per finding; rewrite nothing.

cost $0.0065 · 50s · in 65,082 / out 8,012 tok

✓ duplicate_trigger_found✓ circular_chain✓ dangling_target✓ oversized_desc_count✓ hardcoded_values✓ manifest_drift✓ severity_and_action

✓ Correct Answer (ground truth)

graded checks: duplicate_trigger_found · circular_chain · dangling_target · oversized_desc_count · hardcoded_values · manifest_drift · severity_and_action

Model's actual answer

show the model's full answer

1) OVERLAP: ALWAYS-trigger phrases duplicate between skills
- Finding: email-drafter and comms-drafter both define ALWAYs triggers for writing external copy (email-focused prompts appear in both; e.g., “write me an email” vs “write me an email,” “draft a follow-up,” etc.).
- Severity: WARNING
- Rationale: Both skills respond to the same user signals, risking duplicate prompts and conflicting behavior at runtime.
- Proposed action (type MERGE): Merge email-drafter and comms-drafter into a single comms drafting capability (e.g., a unified comms-drafter) that handles email, follow-ups, rewrites, and partner/outbound copy with a single trigger set. Update body to reflect a single source of truth for drafting communications and adjust references in lane markers accordingly.

2) CIRCULAR DELEGATION CHAIN
- Finding: No explicit circular delegation chain is evidenced in the provided manifests (no skill directly delegates to another that then delegates back).
- Severity: INFO
- Rationale: The manifests show cross-skill handoffs in prose (e.g., “Cross-skill handoff” notes) but no concrete back-and-forth delegation loop is demonstrated.
- Proposed action: REVIEW to confirm there is no hidden or indirect cycle in the actual runner/orchestrator configuration; if a cycle exists, break it by removing or renaming the cyclical delegation link.

3) DANGLING DELEGATION TARGETS
- Finding: A cross-skill reference to prospect-research-multithreading appears (as a cross-skill handoff pathway) but there is no corresponding skill entry named prospect-research-multithreading in the provided skill set.
- Severity: CRITICAL
- Rationale: Dangling delegation targets break handoffs and can cause tasks to stall or be misrouted.
- Proposed action (type REVIEW): Create or expose prospect-research-multithreading as a defined skill, or replace the reference with an existing, properly defined cross-skill path. If the target exists elsewhere, ensure the manifest/documentation makes the linkage explicit.

4) VERSION CONFLICTS AND SURVIVAL
- Finding: No explicit version conflicts are visible across the manifests (only one version tag appears for pipeline-intelligence-report as v6; others are titled with descriptive versions or none). There is no evidenced rival version competing for survival.
- Severity: INFO
- Rationale: Without multiple competing versioned entries for the same skill, there’s nothing to adjudicate.
- Proposed action (type REVIEW): If future updates introduce competing version labels for the same skill name, resolve by merging into a single official version and declare survivor in a MERGE/UPDATE_BODY decision.

5) MANIFEST DESCRIPTION LENGTH (exceeds 1024 chars)
- Finding: Using the provided manifest descriptor lengths (description_chars column) for all 14 skills, none exceed 1,024 characters.
- Count: 0 exceedances out of 14 entries; total entries evaluated = 14.
- Evidence: description_chars values: 656, 897, 996, 792, 965, 676, 945, 1004, 1006, 962, 1006, 708, 762, 656.
- Severity: INFO
- Rationale: No manifest descriptions currently breach the 1,024-character threshold.
- Proposed action (type REVIEW): No change required based on this metric; consider maintaining a monitoring rule to flag any future long-form descriptions that approach the limit.

show the model's full answer

NDA-1 — [PARTY A] and Bonusly — GREEN — Reason: Term: two (2) years from the Effective Date; obligations survive for three (3) years after termination; Carve-outs: "Carve-outs: 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: "Governing law: the laws of the State of Delaware, USA."

NDA-2 — [PARTY B] and Bonusly — GREEN — Reason: Term: three (3) years; Carve-outs: "Carve-outs: standard — publicly available, previously known, third-party receipt, independent development, legally required disclosure." Governing law: "Governing law: the laws of the State of Delaware, USA." 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."

NDA-3 — [PARTY C] and Bonusly — RED — Reason: 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." Governing law: "This Agreement shall be governed by and construed in accordance with the laws of the Republic of Ireland, and the parties submit to the exclusive jurisdiction of its courts." No confidentiality carve-outs are stated: "No confidentiality carve-outs are stated in this Agreement."