Private Mac notes for sales engineers

Sales engineers, solutions architects, and technical pre-sales consultants bridge the critical divide between customer business requirements and complex enterprise software architecture. In an active deal cycle, a sales engineer leads in-depth technical discovery calls with prospect CISOs and enterprise architects, designs proof-of-concept (POC) architectures, responds to comprehensive security RFPs, and facilitates technical handoffs to post-sales implementation teams.

The differentiator in technical enterprise sales is deep listening and technical credibility. When a prospective enterprise customer explains their proprietary network perimeter, legacy database constraints, and compliance firewalls, the sales engineer must capture every nuance accurately to design an unassailable solution architecture.

Yet consumer AI meeting utilities actively sabotage sales engineers. Enterprise prospects—especially in banking, healthcare, and government—strictly ban third-party recording bots from entering company conference rooms. Deploying a noisy cloud bot makes an enterprise prospect defensive, violates their corporate IT policies, and threatens deal momentum. Furthermore, cloud recording services trap technical discovery notes in closed web portals, making it difficult to link customer requirements directly to engineering specifications.

Oyma is the technical pre-sales command center engineered for sales engineers on Apple Silicon Macs. Operating locally on your hardware, Oyma captures technical discovery calls silently via ScreenCaptureKit, runs speech recognition 100% on-device with Whisper, and organizes customer architectures and POC roadmaps in open Markdown documents stored on your encrypted local drive.

The enterprise discovery barrier: Why prospect CISOs block recording bots

In high-value enterprise sales, technological intrusion creates immediate deal friction:

1. Prospect IT security bot lockouts: Enterprise CISOs configure corporate Zoom, Teams, and Webex tenants to automatically kick or block external recording bots. When an AE or SE deploys a cloud bot, the meeting begins with an awkward IT security interruption.
2. Loss of prospect technical candor: When enterprise architects explain their internal infrastructure weaknesses and firewall limitations, the presence of a cloud bot causes them to become guarded and withhold the technical truths needed for POC scoping.
3. Requirement loss in sales-to-engineering handoffs: Complex architectural requirements verbalized during technical calls are rarely documented accurately in CRM text fields, leading to misaligned POC deliverables and post-sales implementation friction.
4. Proprietary cloud silos: Cloud notes apps trap customer requirements inside sales dashboards, preventing sales engineers from maintaining private offline customer dossiers or linking notes to technical RFCs.

The sales engineer’s deal architecture topology

Oyma organizes your sales pipeline into an interconnected, sovereign knowledge system:

┌────────────────────────────────────────────────────────────────────────┐
│                   SALES ENGINEERING DEAL TOPOLOGY                      │
├────────────────────────────────────────────────────────────────────────┤
│                                                                        │
│                    [[Opportunity: Apex Global Retail]]                 │
│                    deals/apex-global/technical-deal-profile.md         │
│                                ▲                                       │
│          ┌─────────────────────┼─────────────────────┐                 │
│          │                     │                     │                 │
│          ▼                     ▼                     ▼                 │
│  [Discovery: CISO Call]  [POC Scoping: Arch Review][Security RFP Memo] │
│  SSO & SAML constraints  Database replication SLA  SOC 2 verification  │
│  "Must run behind proxy" "P99 latency < 50ms"      "Audit export req"  │
│          │                     │                     │                 │
│          └─────────────────────┼─────────────────────┘                 │
│                                ▼                                       │
│                    [[POC Plan: Success Criteria]]                      │
│                    deals/apex-global/poc-success-matrix.md             │
│                                                                        │
└────────────────────────────────────────────────────────────────────────┘

Using bidirectional [[wikilinks]], each technical discovery call connects directly to the master POC success matrix and the opportunity’s technical profile. When leading the POC kickoff or answering complex RFP questions, you have the customer’s exact technical statements immediately at your fingertips.

Presales technical validation: From customer discovery to signed POC

1. Bot-free ScreenCaptureKit loopback on client calls

Whether whiteboarding in Zoom or answering CISO compliance questions on Teams, Oyma taps system audio silently via ScreenCaptureKit. No automated AI assistant enters the participant list, ensuring compliance with strict prospect security policies that ban unverified third-party bots.

2. Full consultative presence on architecture calls

Because your Mac records silently in the background, you keep total presence during discovery—reading customer body language, diagnosing legacy architectural debt, and tailoring value propositions without being distracted by manual typing.

3. Apple Silicon local Whisper transcription

As soon as the technical presentation wraps, Apple Silicon’s Neural Engine runs Whisper speech recognition locally. The model accurately transcribes technical enterprise jargon, SAML/SCIM protocols, latency SLAs, and database sharding terms without hitting cloud speech servers.

4. Structured POC scoping notes in pure Markdown

The resulting technical assessment formats directly into your opportunity directory as standard .md. You can verify customer constraints in Markdown tables, link to past implementation notes, and generate clean PDF architecture proposals for the customer’s evaluation committee.

Authentic sales engineering technical discovery note sample

Here is a realistic technical discovery note produced in Oyma:

---
title: "Technical Discovery: Apex Global Retail (Enterprise Architecture)"
date: 2026-10-08
opportunity: "Apex Global Retail (5,000 Seats)"
prospect_lead: "David Vance (Chief Enterprise Architect)"
stage: "Technical Validation / POC Scoping"
tags: [sales-engineering, discovery, enterprise, architecture, poc, rfp]
---

## Executive Architectural Summary
Conducted deep-dive technical discovery with David Vance regarding enterprise deployment constraints. Identified on-premise proxy routing, Okta SAML 2.0 single sign-on, and role-based workspace isolation as the three non-negotiable POC gates.

## Prospect Infrastructure Constraints & Architecture

| Parameter | Customer Requirement | Our Architectural Response | Status |
| :--- | :--- | :--- | :--- |
| Identity Provider | Okta SAML 2.0 with SCIM | Native SAML 2.0 assertion mapping | Supported |
| Egress Firewall | Outbound proxy via Squid | Configurable HTTP_PROXY / HTTPS_PROXY | Supported |
| Audio Storage | 0% cloud storage allowed | 100% on-device Whisper processing | **Competitive Advantage** |
| Data Residency | European data residency | Local-first Markdown files on APFS | Supported |

## POC Success Criteria & Milestones (Agreed with David)
1. **Milestone 1 (Week 1):** Deploy pilot client across 25 Mac workstations in retail engineering pod.
2. **Milestone 2 (Week 2):** Verify zero unauthorized network calls via built-in Egress Log under customer proxy inspection.
3. **Milestone 3 (Week 3):** Validate automated meeting detection on Zoom and Slack Huddles with zero attendee bots.

## Action Items & Next Deliverables
- [ ] Sales Engineer: Complete architectural questionnaire for David's security team by Friday
- [ ] Sales Engineer: Circulate finalized [[POC Plan: Success Criteria]] to Account Executive
- [ ] David: Provision sandbox Okta test credentials for pre-sales integration validation

Non-disclosure compliance for customer infrastructure topologies

Presales engineers regularly examine client network diagrams, ingress firewall rules, identity provider credentials, and sensitive audit findings. Sending customer security discussions to external cloud speech APIs breaches pre-sales non-disclosure agreements and risks deal disqualification.

Oyma satisfies the most demanding enterprise security requirements:

• Local-only execution boundary: Audio capture and summary extraction run entirely on your Mac’s Apple Silicon hardware with zero remote server connections.
• Client-verifiable zero network egress: Prove to the prospect’s security team that zero telemetry or audio data leaves your machine using the transparent Egress Log.
• Universal Markdown file persistence: Technical discovery notes remain plain text .md files on your encrypted local drive, easily integrated into Obsidian and local knowledge repositories.

Lead technical discovery with commanding authority, respect customer confidentiality, and keep presales architectures sovereign on your Mac.