Private sales discovery and scoping notes on Mac

Enterprise sales discovery and technical scoping calls form the foundation of high-value B2B software transactions. During these critical qualification sessions, account executives, solutions architects, and sales engineers engage enterprise buyers to uncover organizational pain points, evaluate current technical infrastructure, identify the Economic Buyer, map procurement decision processes, and scope proof-of-concept (POC) validation criteria.

However, capturing complex enterprise sales discovery presents an acute operational conflict:

Sales professionals must practice active, empathetic listening: observing subtle hesitation, unearthing hidden stakeholder agendas, and asking probing second-order questions. Expecting a sales engineer to simultaneously maintain rigorous notes on complex network topologies and compliance constraints degrades conversational rapport. Yet introducing a cloud-based sales intelligence recording bot into an enterprise call is a major liability: enterprise security leaders and compliance officers routinely refuse to speak with vendors whose automated bots record and upload proprietary technical discussions to multi-tenant cloud databases.

Oyma resolves this commercial dilemma on macOS. Leveraging Apple’s native ScreenCaptureKit framework, Oyma captures the audio of your enterprise qualification and scoping calls silently, without injecting an automated bot into your Zoom, Google Meet, or Microsoft Teams meeting. Transcription executes 100% on-device on Apple Silicon using local Whisper models, converting spoken buyer requirements into structured, actionable Markdown qualification dossiers stored exclusively on your Mac.

The behavioral and technical dynamics of enterprise sales discovery

Winning complex enterprise software deals requires trust, technical precision, and absolute discretion:

1. The infosec backlash against recording bots: Enterprise IT and security executives are trained to protect corporate communications. When a third-party sales bot enters a technical discovery call, prospects frequently request that recording be terminated or decline to discuss internal infrastructure vulnerabilities.
2. Confidentiality of prospect technical topologies: Technical scoping discussions involve detailed diagrams of internal firewalls, legacy database bottlenecks, cloud spending figures, and compliance audit findings. Uploading this sensitive buyer intelligence to third-party cloud transcription databases violates buyer trust and non-disclosure agreements.
3. The qualification synthesis bottleneck: Translating an hour of technical dialogue into a structured MEDDPICC or BANT qualification summary is an arduous administrative burden that busy account executives routinely delay, leading to inaccurate sales forecasts.
4. Disconnection between sales discovery and technical delivery: Technical requirements captured in proprietary CRM portals rarely translate into clear guidance for solutions architects and implementation engineers, creating scope creep during post-sale deployment.

The sales engineer’s deal vault in plain Markdown

Oyma organizes enterprise sales opportunities directly into an interconnected, sovereign Markdown knowledge base on your local disk:

vault/
├── deals/
│   ├── crest-financial/
│   │   ├── 2026-10-04-initial-discovery.md
│   │   ├── 2026-10-09-technical-scoping.md
│   │   └── meddpicc-scorecard.md
│   └── apex-technologies/
│       └── technical-discovery.md
└── poc-plans/
    └── crest-financial-poc-criteria.md

Connecting discovery notes to MEDDPICC scorecards and technical POC plans via [[wikilinks]] ensures flawless alignment across the entire sales cycle.

Sample on-device sales discovery and scoping note

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

---
opportunityName: "Crest Financial - Enterprise Observability Pipeline"
dealStage: Stage 2 - Technical Scoping & Validation
targetACV: "$65,000 / year"
closeDateTarget: 2026-11-30
primaryContact: "[[contacts/marcus-vance]]"
accountExecutive: "Liam Montgomery"
salesEngineer: "Sarah Chen"
callDate: 2026-10-09
duration: 47m
tags:
  - sales-discovery
  - meddpicc
  - technical-scoping
---

# Sales Discovery & Technical Scoping: Crest Financial (2026-10-09)

## 1. Executive Summary & Qualification Overview
Sarah Chen and Liam Montgomery conducted a deep technical scoping session with Marcus Vance (Head of Enterprise Architecture) and Dave Kaufman (Staff Infrastructure Lead). The prospect validated an urgent need to deploy on-device log normalization to eliminate $1.4M in annual cloud log overage penalties.

## 2. MEDDPICC Enterprise Qualification Breakdown
| MEDDPICC Element | Prospect Reality & Findings | Validation Status |
| :--- | :--- | :--- |
| **M - Metrics** | Reduce annual Datadog/Splunk ingest overage by at least 60% ($840k target savings). | Validated by Marcus |
| **E - Economic Buyer** | Chief Information Security Officer (Elena Rostova); holds sole discretionary sign-off above $50k. | Identified; meeting requested |
| **D - Decision Criteria** | Zero cloud egress of raw logs, sub-15ms p99 throughput latency, Okta SAML 2.0 integration. | Documented in [[poc-plans/crest-financial-poc-criteria]] |
| **D - Decision Process** | 2-week staging POC validation -> Infosec review -> Legal MSA -> Purchase Order issuance. | 30-day target timeline |
| **P - Paper Process** | Standard procurement review with finance; requires mutual NDA and SOC 2 Type II report. | Verified with procurement |
| **I - Identified Pain** | Ingestion pipeline outages triggered by retry storms; legacy Python scripts failing under load. | Acute; high urgency |
| **C - Champion** | Marcus Vance; actively advocating for on-device normalization architecture to his CISO. | Strong internal sponsor |

## 3. Technical Scoping & Architecture Constraints
- **Infrastructure Footprint:** Crest operates 350 bare-metal Kubernetes nodes across two co-location data centers and AWS us-east-1.
- **Log Ingest Volume:** Average 4.2 TB / day; peak burst ingestion reaches 12.8 TB / day during market open.
- **Protocol Requirements:** Solution must ingest legacy syslog RFC 5424, JSON over TLS, and OpenTelemetry gRPC streams.

## 4. Key Deal Risks & Competitor Context
- **Risk:** CISO approval requires air-gapped deployment proof before staging sandbox access is granted.
- **Mitigation:** Demonstrate our <a href="/features/local-only-mode">Local-only mode</a> and verifiable egress log to Elena Rostova on the upcoming executive briefing call.

## 5. Sales Action Items & Next Steps
| Priority | Action Item | Assignee | Target Date | Status |
| :--- | :--- | :--- | :--- | :--- |
| P0 | Draft 2-week POC validation plan with agreed success criteria | Sarah Chen | 2026-10-12 | Open |
| P0 | Send executive summary and zero-egress architecture doc to Marcus | Liam Montgomery | 2026-10-13 | Open |
| P1 | Schedule 30-minute CISO alignment session with Elena Rostova | Liam Montgomery | 2026-10-18 | Open |

The technical sales discovery workflow: from qualification to closed deal

Closing complex enterprise transactions requires a structured, security-conscious discovery cadence:

1. Discreet discovery recording without attendee friction

When starting a technical scoping session on Zoom, Microsoft Teams, or Webex, engage Oyma‘s background audio recorder. Utilizing macOS ScreenCaptureKit at the operating system tier, recording occurs quietly. No automated sales bot enters the room, allowing enterprise architects to discuss internal infrastructure friction with complete openness.

2. High-precision technical speech recognition

Spoken dialogue is processed immediately by local Whisper models running on Apple Silicon. Technical infrastructure specifications, protocol names, compliance standards, and commercial budget figures undergo on-device speech recognition without a single packet transmitted across external networks.

3. Extracting MEDDPICC scorecards and technical constraints

Following the call, apply Oyma‘s sales qualification extraction prompt using local Ollama models (such as Llama 3) or your private API key. The summary engine isolates:

• Quantified business metrics and economic buyer identification
• Technical decision criteria and procurement timelines
• Acute operational pain points and existing vendor workarounds
• Identified deal risks and immediate sales follow-up commitments

4. Direct integration into your deal repository

The structured Markdown qualification note saves directly into your local sales directory. Through bidirectional wikilinks, buyer requirements link to technical POC plans and executive meeting notes in Obsidian, ensuring complete alignment across your revenue team.

Protecting confidential prospect infrastructure intelligence

Sales discovery files contain confidential technical and financial data that must be safeguarded:

• Infosec compliance: Keeping prospect technical notes on local encrypted storage ensures that sensitive architectural diagrams and security vulnerabilities are never exposed to multi-tenant cloud SaaS vendors.
• Verifiable deal history: While CRM records are often overwritten or updated without historical context, your local Markdown qualification dossiers preserve a permanent, timestamped record of every buyer commitment.
• Air-gapped operation: With Local-only mode, sales engineers can review prospect dossiers, prepare POC validation plans, and navigate deal graphs completely offline.

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.