Private customer discovery call notes on Mac

Customer discovery is the lifeblood of B2B product strategy and early-stage venture validation. Whether conducted by startup founders searching for product-market fit or enterprise product managers evaluating expansion opportunities, discovery calls serve a singular goal: uncovering the authentic operational friction, organizational workarounds, and budgetary thresholds of prospective commercial buyers.

Yet capturing high-stakes discovery conversations presents a severe methodological barrier:

If the interviewer spends the call frantically typing notes, they fail to listen actively, miss crucial emotional hesitations, and neglect to probe deeper into unexpected customer remarks. However, if the interviewer invites an automated cloud AI bot into the conference bridge, the prospect immediately becomes defensive. Enterprise buyers will not disclose embarrassing workflow breakdowns, internal compliance failures, or confidential budget constraints to a stranger whose automated bot is broadcasting a recording indicator.

Oyma resolves this discovery dilemma on macOS. Leveraging Apple’s native ScreenCaptureKit framework, Oyma records discovery calls silently without introducing an intrusive AI bot into your Zoom, Google Meet, or Microsoft Teams meeting. Transcription executes 100% locally on Apple Silicon using on-device Whisper models, converting spoken buyer feedback into structured, actionable Markdown files stored securely on your Mac.

The behavioral psychology of B2B customer discovery

Effective discovery calls rely on unearthing raw, unfiltered truth rather than polite corporate platitudes:

1. The chilling effect of visual recording bots: Enterprise prospects are hyper-sensitive to corporate communications monitoring. When an automated AI bot appears in the meeting with a banner such as "Sales Intelligence Notetaker", prospects assume the recording will be shared with vendor marketing teams. They revert to safe, rehearsed answers, hiding their genuine operational pain points.
2. Confidentiality of enterprise architecture and budget: Prospects frequently disclose sensitive internal details: legacy software vendors they despise, regulatory compliance deadlines, internal team headcounts, and available procurement budgets. Streaming this sensitive commercial data to third-party cloud transcription databases violates standard business courtesy and NDA agreements.
3. The problem-validation synthesis bottleneck: Conducting thirty discovery calls produces dozens of hours of spoken dialogue. Without structured, searchable Markdown notes, founders and product managers struggle to identify recurring patterns, leading to biased product roadmap decisions.
4. Disconnection between discovery and engineering: Buyer feedback captured in proprietary CRM portals or sales transcription repositories rarely reaches the software engineers writing code. Critical customer context remains siloed away from technical architecture planning.

The founder’s discovery dossier architecture in plain Markdown

Oyma organizes customer discovery findings directly into an interconnected Markdown vault on your local disk:

vault/
├── discovery/
│   ├── prospects/
│   │   ├── 2026-10-04-acme-corp.md
│   │   ├── 2026-10-07-beacon-health.md
│   │   └── 2026-10-09-crest-financial.md
│   └── synthesis/
│       ├── pain-point-matrix.md
│       └── pricing-objections.md
└── roadmaps/
    ├── PRD-enterprise-sso.md
    └── PRD-audit-logs.md

Connecting individual customer interviews to feature requirements documents via [[wikilinks]] ensures that every roadmap ticket is backed by verified buyer evidence.

Sample on-device customer discovery call note

Here is an authentic Markdown artifact generated during an enterprise customer discovery call in Oyma:

---
company: Crest Financial
contact: "Marcus Vance (Head of Enterprise Architecture)"
annualRevenueTier: "$500M - $1B"
currentSolution: "Splunk + Custom Python Scripts"
evaluationStage: Initial Problem Discovery
callDate: 2026-10-09
duration: 38m
tags:
  - customer-discovery
  - enterprise-buyer
  - observability
---

# Customer Discovery: Crest Financial (Marcus Vance)

## 1. Executive Summary & Buyer Context
Marcus Vance oversees enterprise data infrastructure and security architecture across 1,200 developers. His team is actively seeking to consolidate disconnected logging pipelines to reduce annual SaaS ingest licensing fees.

## 2. Core Problem Statements & Operational Pain
- **Current Workaround:** Engineers write bespoke Python scripts to export audit logs to local disks before bulk ingestion to avoid Splunk overage tiers.
- **Observed Pain Point:** Script failures frequently leave compliance gaps during quarterly SOC 2 audit reconciliations.
- **Verbatim Quote:**
  > "We spent $1.4M last year on ingest overage penalties alone. If a solution can normalize our log streams locally before transmission, it pays for itself in sixty days."

## 3. Commercial Validation & Decision Criteria Matrix
| Criterion | Prospect Requirement | Current Status | Validation Evidence |
| :--- | :--- | :--- | :--- |
| Data Residency | Zero cloud storage of raw payload logs | Mandatory P0 | Confirmed our on-device architecture satisfies strict financial infosec |
| Latency SLA | Ingest normalization under 15ms p99 | Mandatory P0 | Requires benchmarking on prospect's test sample logs |
| Identity & Access | SAML 2.0 / Okta SSO integration | Mandatory P1 | Stated in [[roadmaps/PRD-enterprise-sso]] |
| Pricing Willingness | $45k - $60k annual contract value (ACV) | Validated | Marcus confirmed discretionary budget ceiling of $75k without procurement committee |

## 4. Key Objections & Competitive Context
- **Legacy Vendor Inertia:** Enterprise security operations team is deeply entrenched in Splunk search query language; migration friction is substantial.
- **Implementation Bandwidth:** Marcus's team has zero spare engineering capacity for complex on-premise agent configurations. Solution must deploy as a binary with minimal configuration.

## 5. Strategic Takeaways for Product Roadmap
1. Validate that our local normalization parser supports legacy syslog RFC 5424 formats out of the box.
2. Link Marcus's pricing feedback into [[discovery/synthesis/pricing-objections]] to refine enterprise tier packaging.
3. Follow up with Marcus on 2026-10-16 with a sample sanitized benchmark report.

The customer discovery synthesis cycle: from interview to validated thesis

Converting exploratory prospect discussions into validated product requirements follows a streamlined, zero-leak methodology:

1. Activating discreet dual-channel audio capture

When initiating a scheduled evaluation call across Zoom, Teams, or Meet, engage Oyma‘s background listener. Operating at the macOS ScreenCaptureKit layer, recording commences silently. Without an automated bot appearing in the video roster, prospective buyers remain candid about legacy vendor frustration and procurement hurdles.

2. On-device acoustic recognition on Apple Silicon

Spoken buyer commentary—including technical infrastructure terminology, competing product names, and budget estimates—is parsed immediately by local Whisper models. Audio remains 100% on-device, preserving prospective customer security requirements.

3. Parsing commercial pain points and purchase triggers

Following the interview, execute Oyma‘s customer discovery extraction prompt using local Ollama models or your own API key. The summary engine isolates:

• Validated enterprise problem statements and active technical workarounds
• Mandatory purchasing criteria and procurement governance timelines
• Verbatim customer quotes conveying acute operational pain
• Contract value thresholds and budget allocation indicators

4. Mapping buyer insights into your product repository

The finalized discovery file saves directly into your local Markdown vault. By using bidirectional wikilinks, buyer quotes link into draft PRDs and market sizing dossiers in Obsidian.

Protecting confidential prospect business intelligence

Early-stage discovery calls uncover sensitive commercial insights that demand strict confidentiality:

• Enterprise security compliance: Prospective clients often reveal unpatched internal vulnerabilities, compliance gaps, and budget numbers. Keeping these records strictly on your local encrypted drive prevents third-party data leaks.
• Competitive advantage: Your unique problem-validation findings and customer quotes are irreplaceable intellectual property. Cloud transcription services that reserve training rights on user data compromise your competitive edge.
• Air-gapped review: With Local-only mode, you can synthesize discovery trends, search customer quotes, and draft PRDs without internet connectivity.

To learn more about our local audio architecture, read about botless meeting recording, explore spreadsheet-like Markdown tables, or review our zero-leak privacy architecture.