Enterprise RFP Kickoff Notes

Template Overview

Responding to enterprise Requests for Proposals (RFPs) demands rapid coordination across sales engineering, legal counsel, security compliance, and product management. The Enterprise RFP Kickoff template establishes proposal ownership, maps security requirements, and enforces strict submission deadlines.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Enterprise RFP Kickoff: [Client Organization]"
date: [YYYY-MM-DD]
lead_account_executive: "[[Account Executive]]"
sales_engineer: "[[Sales Engineer]]"
client_name: "[Enterprise Client Organization]"
deal_arr_potential: "$120,000 / year"
submission_deadline: "[YYYY-MM-DD 17:00 EST]"
rfp_scope: "Enterprise Private Meeting Notes Deployment"
tags: [rfp, enterprise-sales, procurement, security, proposal]
---

# Enterprise RFP Kickoff — [Client Organization]

## 1. Procurement Context & Opportunity Overview
- **Customer Need:** Replacing existing cloud notetaker with a local-first software solution that meets strict healthcare data sovereignty mandates.
- **Estimated Seat Count:** 850 macOS developer and executive seats across North America and Europe.
- **Key Decision Criteria:** Zero audio/transcript cloud uploads, on-device Whisper transcription, and local Markdown file persistence.

## 2. Cross-Functional Response Team
| Section | Assignee | Reviewer | Completion Deadline |
|---|---|---|---|
| **Security & Privacy Architecture** | [[Sales Engineer]] | [[Security Lead]] | [YYYY-MM-DD] |
| **Product & Technical Capabilities** | [[Sales Engineer]] | [[Product Lead]] | [YYYY-MM-DD] |
| **Master Services Agreement & Terms** | [[Corporate Counsel]] | [[Finance VP]] | [YYYY-MM-DD] |
| **Commercial Pricing Schedule** | [[Account Executive]] | [[Head of Sales]] | [YYYY-MM-DD] |

## 3. Mandatory Security & Technical Questions
- **Question 3.1: "Does meeting audio or text ever transit vendor cloud servers?"**
  - *Response:* No. Oyma executes all audio recording, Whisper transcription, and note structuring locally on Apple Silicon hardware.
- **Question 3.2: "How are API credentials secured on employee machines?"**
  - *Response:* User-provided API keys are encrypted via Apple Security.framework within the macOS login Keychain.

## 4. Proposal Schedule & Review Gates
- **Draft 1 Review:** Internal cross-functional review on [YYYY-MM-DD].
- **Executive Sign-Off:** Final commercial and legal approval by [YYYY-MM-DD].
- **Formal Submission:** RFP delivery via client procurement portal on [YYYY-MM-DD].

## 5. Immediate Action Items
- [ ] [[Sales Engineer]] Complete security questionnaire questions 1 through 40.
- [ ] [[Corporate Counsel]] Review indemnification clause in client vendor rider.

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "RFP Kickoff: Nordic Health Systems"
date: 2026-10-06
lead_account_executive: "[[Rachel Adams]]"
sales_engineer: "[[Devin Zhao]]"
client_name: "Nordic Health Systems"
deal_arr_potential: "$85,000 / year"
tags: [rfp, enterprise-sales]
---

# RFP Kickoff: Nordic Health Systems

## 1. Opportunity Summary
Nordic Health Systems issued an RFP seeking an air-gapped meeting documentation tool for 400 clinical research specialists. Devin Zhao confirmed that our on-device Whisper models satisfy all clinical privacy requirements.

When to Use and When to Avoid

When to Use

• Use when kicking off complex enterprise RFP and RFI procurement responses.
• Use to coordinate parallel workstreams across sales, legal, engineering, and security.
• Use to establish rigid milestone deadlines leading to formal proposal submission.

When to Avoid

• Avoid using for transactional self-serve customer inquiries.
• Avoid using for initial unstructured discovery conversations.

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the enterprise RFP kickoff meeting audio recording:
1. Extract client procurement deadlines, estimated contract values, and seat counts.
2. Outline assigned response sections, technical question leads, and internal review dates.
3. List all compliance prerequisites and follow-up deliverables into clean Markdown.

Your data remains securely on your Mac with zero cloud exposure.