process-letter
Draft process letters and bid instructions for sell-side M&A processes. Covers initial indication of interest (IOI) instructions, final bid procedures, and management meeting logistics. Triggers on "process letter", "bid instructions", "IOI letter", "bid procedures", "final round letter", or "management meeting invite".
What this skill does
# Process Letter ## Workflow ### Step 1: Determine Letter Type - **Initial process letter**: Sent with teaser/CIM to outline the process and IOI requirements - **IOI instructions**: Specific requirements for first-round indications of interest - **Second round / final bid letter**: Instructions for submitting binding offers after diligence - **Management meeting invitation**: Logistics for in-person management presentations ### Step 2: Initial Process Letter / IOI Instructions **Header:** - Date, deal code name - "Confidential" - Addressed to prospective buyer **Sections:** 1. **Introduction**: Brief overview of the opportunity and the seller's objectives 2. **Process Overview**: Timeline, key dates, expected number of rounds 3. **IOI Requirements**: What to include in the initial indication: - Proposed valuation range (enterprise value) - Consideration form (cash, stock, earnout, rollover) - Financing sources and certainty - Key due diligence requirements - Indicative timeline to close - Any conditions or contingencies - Brief description of the buyer and strategic rationale 4. **Submission Details**: Where to send, deadline (date and time), format 5. **Confidentiality Reminder**: Reference to NDA, data room access 6. **Contact Information**: Banker contacts for questions ### Step 3: Final Bid / Second Round Letter Additional requirements beyond IOI: 1. **Markup of purchase agreement**: Provide the draft SPA/APA and request markup 2. **Detailed financing commitments**: Committed financing letters required 3. **Remaining diligence items**: Specify what confirmatory diligence is expected 4. **Exclusivity terms**: Duration and conditions of any exclusivity period 5. **Regulatory analysis**: Antitrust filing requirements and timeline 6. **Key personnel terms**: Employment agreements, compensation, rollover equity 7. **Binding vs. non-binding**: Clarify what is binding at this stage 8. **Evaluation criteria**: How bids will be evaluated (price, certainty, speed, fit) ### Step 4: Management Meeting Invitation 1. **Logistics**: Date, time, location (or video link), duration 2. **Attendees**: Who from the company will present, who from the buyer should attend 3. **Agenda**: Typical management presentation agenda (overview, financials, operations, growth, Q&A) 4. **Ground rules**: No recording, confidentiality, questions format 5. **Materials**: What will be distributed (presentation deck, data room access) 6. **Follow-up**: Process for submitting additional questions after the meeting ### Step 5: Output - Word document (.docx) with professional letter formatting - Firm letterhead placeholder - Track changes version for client review ## Important Notes - Process letters set the tone for the entire deal — be clear, professional, and organized - Deadlines should be firm but reasonable — typically 2-3 weeks for IOIs, 3-4 weeks for final bids - Always include the evaluation criteria — buyers want to know how they'll be judged - Coordinate with legal on any representations or commitments in the letter - Client should review and approve before sending — they may want to adjust tone or terms - Keep a log of who received each letter and when — this becomes the process tracker
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.