Private client intake and scoping notes on Mac

In professional services, management consulting, and specialized advisory practices, the initial client intake session sets the trajectory for the entire commercial relationship. During these high-stakes onboarding briefings, senior partners and engagement managers meet with prospective client executives to diagnose organizational pain points, establish project objectives, map technical constraints, and define the boundaries of the engagement.

However, capturing these critical intake sessions accurately presents acute commercial and confidentiality challenges:

Prospective clients share sensitive internal details: organizational friction between executives, proprietary revenue architectures, regulatory vulnerabilities, and unannounced strategic pivots. If an advisor brings a third-party cloud recording bot into this delicate briefing, the client’s legal counsel or executive sponsor will often object immediately. Even when permitted, the presence of a visual recording bot creates an atmosphere of caution, preventing the client from sharing the candid, unvarnished realities that consultants need to design effective interventions.

Furthermore, verbal intake conversations are notorious for ambiguity. What the client describes as a “quick baseline review” can easily balloon into weeks of uncompensated analysis unless clear boundaries are established from the start.

Oyma resolves this advisory workflow challenge on macOS. Utilizing Apple’s native ScreenCaptureKit framework, Oyma captures intake sessions silently without deploying an intrusive AI bot into your Zoom, Microsoft Teams, or Google Meet room. On-device Whisper models transcribe client dialogue locally on your Apple Silicon hardware, transforming unstructured briefing conversations into precise, structured Markdown scoping documents and Statement of Work (SOW) outlines stored solely on your Mac.

The core operational challenges in client intake and scoping

Establishing a profitable, legally sound advisory engagement requires mastering several critical hurdles:

1. Client confidentiality and NDA compliance: Enterprise clients routinely sign bilateral non-disclosure agreements before intake meetings. Transmitting their operational challenges to third-party cloud transcription SaaS providers violates these confidentiality commitments.
2. The chilling effect of visual recording bots: Advisory relationships are built on trust and candid disclosure. When an automated bot is visibly present in the participant list, clients become guarded and offer sanitized, superficial descriptions of their challenges.
3. Preventing unbillable scope creep: During enthusiastic brainstorming sessions, consultants often verbally agree to explore tangential topics. Without verbatim, searchable records of what was discussed, firms struggle to establish firm scope boundaries in subsequent commercial negotiations.
4. The unbillable proposal drafting burden: Translating hours of free-flowing client dialogue into structured deliverables, resource estimates, and project timelines requires substantial unbillable effort that cuts directly into firm margins.

The consultant’s engagement vault in plain Markdown

Oyma organizes advisory intake and scoping documentation directly into an interconnected, sovereign Markdown knowledge base on your local disk:

vault/
├── clients/
│   ├── vanguard-logistics/
│   │   ├── intake-session-2026-10-09.md
│   │   ├── statement-of-work-draft.md
│   │   └── stakeholder-matrix.md
│   └── templates/
│       └── advisory-scoping-template.md
└── practices/
    ├── supply-chain-optimization/
    └── deliverables-library/

Connecting client intake notes to past project post-mortems, proposal templates, and practice playbooks via [[wikilinks]] creates a powerful institutional memory that accelerates proposal drafting across engagements.

Sample on-device client scoping and intake note

Here is an authentic Markdown artifact synthesized from a live enterprise advisory intake session in Oyma:

---
clientId: "CLI-8821"
clientName: "Vanguard Global Logistics"
engagementName: "Supply Chain Telemetry Modernization"
sessionType: "Initial Discovery & Scoping Session"
date: 2026-10-09
leadPartner: "[[partners/eleanor-vance]]"
engagementManager: "[[consultants/julian-mercer]]"
clientSponsors:
  - "Marcus Sterling, Chief Operating Officer"
  - "Dr. Aris Thorne, VP Logistics Technology"
targetEngagementStart: "2026-11-01"
estimatedDuration: "10 Weeks"
ndaStatus: "Executed (Mutual Bilateral)"
tags:
  - client-intake
  - project-scoping
  - statement-of-work
  - advisory
---

# Client Intake & Scoping: Vanguard Global Logistics

## 1. Executive Summary & Core Business Problem
Vanguard operates 1,400 long-haul distribution hubs across North America. Their legacy inventory tracking software experiences 4-hour synchronization delays between regional distribution centers and central fleet dispatch. This lag results in an estimated $14M in annual excess dwell time and lost transit capacity. Marcus Sterling has engaged our advisory practice to design an event-driven edge telemetry architecture to reduce dispatch latency to under 60 seconds.

## 2. Agreed Deliverables & Scope Matrix

| Phase | Core Deliverable | Acceptance Criteria | Target Week |
| :--- | :--- | :--- | :--- |
| **Phase 1: Current-State Audit** | Architectural assessment report & bottleneck heat map | Identification of top 5 latency bottlenecks across 3 flagship distribution hubs | Week 1–3 |
| **Phase 2: Target Architecture** | Event-driven reference architecture specification | High-level system design document supporting 50k events/sec with sub-minute delivery | Week 4–6 |
| **Phase 3: Vendor Evaluation** | Vendor selection scorecard & evaluation matrix | Comparative analysis of 4 edge streaming platforms scored across latency, TCO, and security | Week 7–8 |
| **Phase 4: Implementation Roadmap** | Phased rollout plan & budget model | Executive-ready roadmap with resource model, timeline, and risk mitigation plan | Week 9–10 |

## 3. Explicit Out-of-Scope Non-Goals (Scope Boundary Log)
- **Hands-on Production Code Implementation:** Dr. Thorne requested assistance with writing Kafka production consumer logic. *Clarified:* This engagement is strictly architectural advisory; production implementation requires a separate Phase 2 engineering statement of work.
- **Legacy Database Migration Execution:** Performing the physical database migration from legacy Oracle instances to cloud data stores is explicitly excluded.
- **End-User Training Program:** Developing training curricula for dispatch floor operators is excluded from this strategic engagement.

## 4. Key Client Statements & Verbatim Requirements
> *"If we don't have this architectural roadmap approved by the board before the Q1 budget freeze in December, the entire multi-region rollout gets delayed by a full year."* — Marcus Sterling, COO (Timestamp 18:42)

> *"Our primary internal constraint is that whatever edge streaming solution you recommend must interface with our legacy SAP warehouse management system without requiring an upfront ERP upgrade."* — Dr. Aris Thorne, VP Tech (Timestamp 41:15)

## 5. Next Steps & Proposal Action Items
- [ ] Incorporate the deliverables matrix into the draft Statement of Work `[[clients/vanguard-logistics/statement-of-work-draft]]`.
- [ ] Review legacy SAP integration constraints with our internal enterprise architecture practice lead `[[practices/enterprise-architecture/sap-adapters]]`.
- [ ] Deliver final engagement proposal and staffing model to Marcus Sterling by Friday, October 16.

How Oyma accelerates advisory scoping on macOS

Oyma provides consulting practices and independent advisors with automated scoping capabilities while protecting client trust:

1. Inaudible botless audio capture via ScreenCaptureKit

Oyma records client intake sessions directly through macOS system audio APIs. No third-party meeting bot enters the video call, allowing prospective clients to speak candidly about sensitive organizational bottlenecks.

2. On-device speech recognition via Whisper models

Client dialogue—including proprietary financial metrics, internal stakeholder tensions, and strategic plans—is transcribed 100% locally on Apple Silicon. Audio data never touches external cloud servers, ensuring complete compliance with client non-disclosure agreements.

3. Automated scope boundary extraction

Using specialized advisory templates, Oyma parses unstructured client conversations into clean, structured tables: agreed deliverables, project phases, and explicit scope exclusions. This automated structure saves hours of manual proposal drafting.

4. Sovereign local markdown notes

Scoping records are stored as plain text Markdown files in your local vault. They integrate effortlessly with your firm’s proposal templates, rate cards, and engagement archives, creating an enduring knowledge base that enhances future client work.

Step-by-step workflow: From intake call to finalized SOW

Adopting Oyma for your advisory practice is straightforward:

Step 1: Launch silent capture during the intake consultation

When beginning an introductory discovery or scoping session on Zoom, Teams, or Google Meet, start Oyma from your macOS menu bar. The application records both your microphone and client audio without introducing a bot to the call.

Step 2: Engage deeply without the distraction of manual note-taking

Focus on diagnosing the client’s underlying business problems and asking strategic questions. Because Oyma captures the conversation locally, you do not need to look away to type frantic notes.

Step 3: Run the local advisory scoping template

After the session concludes, choose the “Advisory Scoping & SOW” template. The local LLM processes the transcript on-device, generating a structured executive summary, deliverables matrix, and scope boundary log.

Step 4: Transfer findings directly into your engagement proposal

Open the generated Markdown file in your preferred editor. Refine the project milestones, copy the deliverables table directly into your firm’s Statement of Work template, and link the note into your client knowledge base.

Why leading advisory practices build sovereign client vaults

In professional services, client trust and analytical precision are your most valuable assets. Uploading confidential client briefings to multi-tenant cloud transcription services violates client non-disclosure agreements and exposes sensitive business data to external security risks.

By maintaining your client intake and scoping records in a private, sovereign Markdown vault on macOS with Oyma, your practice safeguards client confidentiality, eliminates scope creep, and streamlines proposal generation across every engagement.