Customer escalation: [paste email]. Severity: [paste, e.g. churn threat / refund demand / executive complaint]. Reasonable parts of their complaint: [paste]. Unreasonable parts: [paste]. Draft an under-200-word response: subject under 7 words specific to the issue, lead with what we got wrong (specifically, no hedging), what we are doing in the next 24-48 hours (specific actions with named owner), what we cannot commit to and why (honest), single binary CTA for a 30-min call. No 'we hear you', no 'we apologize for any inconvenience', no 'thanks for the feedback'.

Customer escalation now at: [paste exec title escalating it on customer side]. Issue: [paste]. CSM and VP CS have not resolved. Founder/CEO is being pulled in. Draft a 250-word founder-to-customer-exec response: opens by acknowledging the escalation reached me directly (signal of severity), specific honest read of what went wrong, what changes structurally because of this (not just for them), what I am personally committing to (with specific timeline), single binary CTA for a 30-min direct call. Founder voice; executives reading other executives' apology emails detect platitude in two sentences.

Customer requesting: [paste, e.g. full refund / partial credit / contract termination]. Their stated reason: [paste]. Decision authority I have: [paste, e.g. up to $X without approval]. My decision: [paste granted / partial / denied with reasoning]. Draft an under-200-word decision communication: lead with the decision (no preamble), specific reasoning tied to facts not policy, what they get and what they do not get, what happens next operationally. No 'unfortunately' opener. No 'as a one-time courtesy' framing if it is not actually one-time.

Customer posted publicly: [paste post or review]. Severity: [paste]. Reasonable parts: [paste]. Inaccurate parts: [paste]. Draft an under-150-word public response: lead with the part of their complaint we own, correct the inaccurate parts factually without arguing, name what we are doing about it, offer to take it offline (without making it sound like we are hiding). No legal-team-sounding language. No defensive register. No 'we are committed to' filler.

Issue affected: [N] customers. Root cause: [paste]. Timeline: detected [date], mitigated [date], resolved [date]. Customer-facing impact: [paste]. Draft an under-500-word postmortem comms email going to all affected customers: subject under 8 words naming what happened, what happened in plain language (not jargon), customer impact in their terms (what they actually experienced), root cause in 1-2 sentences, what we have already changed, what we are still changing. Engineer's tone, not marketing's tone.

What we did wrong: [paste, specifically]. Customer affected: [paste]. Damage: [paste]. What we are doing about it: [paste]. Draft an under-150-word apology that is calibrated to the actual mistake: name the mistake plainly, name the impact on them (in their terms not ours), what we are doing differently (specific change not 'we will do better'), what they get if anything (concrete remedy). No 'with our deepest apologies'. No 'this is not who we are' (it just was, by definition).

Customer demanding: [paste demand]. Why it is unreasonable: [paste]. Their leverage if any: [paste]. Our position: [paste what we will and will not do]. Draft an under-200-word response that pushes back without escalating: acknowledge what we understand from their position (specifically), name what we cannot do and the structural reason why (not 'company policy' as the answer), present what we can do as an alternative, single binary CTA. Calm tone; the goal is to hold the line without pretending the customer's demand was reasonable.

Customer publicly announced churn: [paste post, link, context]. Their stated reason: [paste]. The actual reason as we understand it: [paste]. Draft an under-100-word response (LinkedIn or X reply): acknowledge their decision without arguing, do not list our defenses publicly, offer one specific gesture (1:1 call to learn more, not a save attempt), wish them well genuinely. No 'sorry to see you go' boilerplate. No 'we appreciate your business' filler.

Customer: [name, ACV]. Situation: [paste]. Why this needs leadership attention: [paste]. What I have done so far: [paste]. What I am asking for: [paste, e.g. exec call, pricing concession, product commitment]. Draft an under-400-word internal escalation memo: bottom line up front (the ask), situation in 2 paragraphs, what we have tried and the result, what I am asking for from leadership specifically, decision deadline. Honest tone; leadership reading escalation memos that hide context make worse decisions.

I just had a 1:1 call with: [paste customer name and role]. Their starting position: [paste]. What we agreed: [paste]. What is still open: [paste]. Draft an under-250-word follow-up email: thanks them for the call (specifically not generically), recaps what was agreed in their words where possible, names what is still open with specific owner and date, sets the next checkpoint. The goal is to make sure the call's outcome does not drift in either party's memory.

Deal: [account, ACV, stage]. Champion: [name, role]. Last meaningful contact: [date]. What we last discussed: [paste]. My read on why they went silent: [paste 2-3 hypotheses]. Draft an under-100-word breakthrough message that names the silence directly without guilt-tripping, offers a specific reason to respond (a useful resource, an industry development, a decision deadline of theirs), single binary CTA. No 'just checking in', no 'circling back', no 'I wanted to follow up'.

Account: [name, ACV]. Original champion: [name, role, departed/changed/promoted]. New buyer: [name, role, what we know about them]. Deal stage: [paste]. Draft a 200-word reset note to the new buyer: acknowledge the change without dwelling on it, recap the deal context in 2-3 sentences (what was being solved and why), explicit reset on discovery (what their priorities are, not assuming continuity), single binary CTA for a 30-min reset call. Treat as a new deal, not a continuation.

Account: [name, ACV]. Deal stage: in procurement. Days stuck: [N]. Procurement contact: [name]. Champion still supportive: [yes/no]. Specific friction: [paste, e.g. legal redlines, security review, pricing escalation]. Draft an under-150-word procurement-friendly note: confirm the terms that are not contested, specifically address the friction point with a concrete proposal, name the documentation we are providing, single binary CTA for a working session. Cooperative tone; procurement is doing their job, not opposing us.

Late-stage objection just surfaced: [paste]. This should have come up at stage [N], not [current stage]. My options: [paste, e.g. address head-on, escalate to manager, walk away]. Draft a 200-word response that takes the objection seriously, acknowledges that we should have surfaced it earlier (briefly), provides the substantive answer with evidence, names a specific next step that addresses the underlying concern not the surface objection. Honest tone; pretending the objection is normal at this stage erodes trust.

Account: [name, ACV]. Champion confirmed: budget [paused / cut / reassigned]. Reason: [paste, e.g. macro, internal restructure, priority shift]. Their relationship with the product: [paste]. Draft an under-200-word response that does not panic-discount, acknowledges the constraint specifically, surfaces what changes about the deal shape (smaller initial scope, longer term, deferred start), names what we will not do (cut value to match new budget without scope reduction), single binary CTA for a working session. Patience signals strength; pressure signals desperation.

Account: [name, ACV]. Competitor: [name]. How they got in: [paste, e.g. champion's friend recommended, RFP late addition]. Where they are winning: [paste their angle]. Where we are stronger: [paste specific 2-3 advantages with evidence]. Draft a 250-word competitive recovery note to the champion: surface that we know there is competition (do not pretend not to), acknowledge what the competitor does well (briefly, specifically), name the 2-3 specific reasons we believe we are the right fit (with evidence not adjectives), invite a working session focused on their actual decision criteria. No competitor disparagement.

Deal: [account, ACV]. Verbal commitment received: [paste date and from whom]. Signature still pending after [N] days. Specific friction: [paste if known]. Draft an under-150-word note that pulls on the verbal commitment without weaponizing it: confirms what was committed verbally, names a specific date by which we need signature for the start date they wanted, offers help with whatever is blocking (legal review, IT review, internal approval), single binary CTA. Firm without being passive-aggressive.

Account: [name, ACV]. Pricing pushback escalated to: [their exec title]. Their argument: [paste]. Our pricing logic: [paste]. Authority I have: [paste flex]. Draft a 250-word executive-to-executive pricing response: respect their pricing argument (specifically, what part is reasonable), explain our pricing logic in business terms not 'this is our pricing', name what we can flex on and what we cannot (with structural reasoning), single binary CTA for a 30-min exec-to-exec call. Treat the buyer's exec as a peer.

Deal: [account, ACV]. Was committed to close in Q[N]. Now slipping to Q[N+1]. Reason: [paste honestly]. Forecast adjustment: [paste]. Draft an under-300-word internal note to my manager and VP Sales: lead with the slip (do not soften), root cause in 1-2 sentences (specific not vague), what is still on track for the deal vs what changed, new commit date with confidence level, what I am doing differently. Honest; soft updates that hide slips create worse forecast outcomes than honest ones.

Deal: [account, ACV]. Reason walking away: [paste honestly]. Sunk cost so far: [paste]. Path I am closing the deal down on: [paste]. Draft an under-150-word respectful close-down note to the buyer: thanks them for the time, names that the fit is not right at this stage (specifically, briefly), leaves the door open without urgency, offers one resource they could use without working with us. Walking away well preserves the relationship for the next role they take.

Layoff: [paste percent and absolute number]. Reason (real, not corporate): [paste]. Severance package: [paste]. Affected functions: [paste]. Draft an under-600-word all-hands script: leads with the decision (no setup), names the specific number of people, names the actual reason (revenue miss, runway, restructure — not 'changing market conditions'), names what every leaving employee gets (severance, healthcare, equity treatment, references), names what every staying employee should know about why this is the right shape now. Founder voice; no platitudes; respect that everyone in the room has been hurt by something they had no role in causing.

Layoff just communicated internally. External announcement needed for: [press / customers / partners]. Approved messaging: [paste]. Things we are not commenting on: [paste]. Draft an under-300-word external announcement: factual statement of what happened (specific number), reason in business terms (not euphemism), what changes about company operations going forward (specifically nothing for customers if that is true, or specific changes if not), how affected employees are being supported. No 'reorganization to better serve' filler.

Employee: [name, role, tenure, reporting line]. Reason for inclusion in the reduction: [paste, e.g. function-wide cut not performance]. Their severance package: [paste base, weeks, healthcare, equity, references policy]. Draft a 1-on-1 conversation script: opening sentence names the decision in the first 30 seconds (no preamble), the specific reason (no hiding behind euphemism), the package (specific numbers and timeline), space for their questions, what we will say about them externally (already aligned). Direct delivery; the manager's job is clarity, not comfort.

Employee: [name, role, tenure]. Reason for separation: performance, not reduction. Documentation: [paste, e.g. PIP completed, multiple feedback cycles, manager and HR alignment]. Severance offered: [paste]. Draft a 1-on-1 separation conversation script: opens with the decision in the first sentence (no PIP-recap preamble), reason in performance terms specifically (with reference to documented expectations), the offered package, what they should expect operationally (last day, transition, references), space for them to respond. Honest tone; performance separations that pretend to be 'mutual decisions' produce worse outcomes.

Separation type: [paste reduction / performance / mutual]. Severance terms: [base weeks, healthcare COBRA, equity treatment, non-disparagement, reference policy]. Draft a 250-word severance email: confirms the separation date, the specific monetary and non-monetary terms (each itemized), what they are agreeing to in exchange (release of claims, non-disparagement, return of property), what we are not asking them to agree to (no non-compete if not legally enforceable, no extended non-solicit beyond standard), point of contact for questions. Plain language; severance documents that read like legalese damage the relationship even when the terms are fair.

Departing employee: [name, role, tenure]. Separation type: [paste]. What they are doing next: [paste if they want to share, or 'TBD' if not]. What they want said: [paste their preference if you asked them]. Draft an under-200-word farewell announcement to the team: lead with their tenure and contribution (specific examples, not 'all-around great teammate'), what is happening (without revealing more than they want shared), how to keep in touch if they consent, no awkward 'we are sad to see them go' platitudes if the separation was not voluntary.

Layoff just happened. My team lost [N] people. Remaining team: [N]. The work that needs to be redistributed: [paste]. The team's likely emotional state: shaken. Draft a 1-on-1 manager script for the day-after team meeting: opens by acknowledging what happened (specific not vague), names the people who left and what they contributed, names the new shape of the team (who owns what now), names what we are not changing (commitments to existing customers, the work that matters), space for their questions and concerns. Calm tone; team meetings that pretend nothing happened make the trauma worse.

Restructure: [paste, e.g. team realigned, new reporting lines, function consolidated]. Headcount impact: zero (or specific). Effective date: [paste]. Reason: [paste honest, e.g. growth necessitating specialization]. Draft an under-400-word announcement: leads with what is changing structurally (specifically), names the new reporting lines (who reports to whom), names what is not changing (work continuity, customer relationships), names why now (specific business reason). Avoid 'optimizing for our future' filler.

Separated employee: [name, role, tenure]. What they actually contributed: [paste 3-4 specific things]. Why they left: [paste]. My honest read of their strengths: [paste]. Draft a 200-300 word reference letter or LinkedIn recommendation: specific examples not adjectives, scoped to what I genuinely observed (do not over-claim), honest about strengths in a way that lets a future employer make a real decision. No generic 'team player' / 'highly recommend' boilerplate. Signed in operator voice.

Senior employee: [name, role, tenure]. Separation: [paste reason]. They are choosing not to announce it publicly. Risk: speculation if we say nothing, harm if we say too much. Draft an internal Slack guidance for the team about what to say externally: aligned messaging on what to say if asked (factual short answer), what not to speculate about, who to refer escalating questions to. Respect the departed employee's choice; do not let speculation fill the vacuum.

Cofounder: [name, role]. Disagreement on: [paste decision, e.g. fundraise timing, GTM strategy, hiring sequence]. My position with reasoning: [paste]. Their position as I understand it (steel-manned): [paste]. Draft a 500-word cofounder memo for shared review: state the decision plainly, my position with evidence, their position fairly stated (no straw man), where we agree, where we disagree, what would change my mind, what I propose if we cannot align (specific named decision-maker or board referral). Honest tone; cofounder disputes that fester are existential.

Disagreement with: board majority. The decision: [paste]. Board's position: [paste]. My position: [paste]. Stakes: [paste]. Draft a 600-word strategic memo to the board: state the decision plainly, the board's position fairly stated, my position with evidence (data, customer conversations, market context), where I would defer if pushed but with named conditions, what I would resign over if compelled. Honest tone; CEO-board disputes that resolve via passive resistance instead of explicit memo destroy companies slowly.

Disagreement with: [name, peer exec title]. The decision: [paste]. Their position: [paste]. My position: [paste]. Shared context: we both report to [name]. Draft a 400-word memo for our shared manager: name the decision plainly, both positions fairly stated, the cost of further delay, what each of us would commit to if the decision goes the other way, what we are asking the manager to do (specific decision authority, not 'help us align'). Respectful tone; peer exec disputes that dragon for weeks waste leadership time and erode team confidence.

Direct report: [name, role]. They have raised: [paste their concern with strategic decision I have made]. Their reasoning: [paste]. The decision is made: [yes]. Draft a 200-word response that takes their concern seriously without reopening the decision: acknowledge the part of their concern that is reasonable, explain the decision in terms they can advocate for to their team, name what would cause us to revisit (specific signal not vague), commit to checking in at a specific date. Direct report dissent that is suppressed becomes silent quitting; respect it without folding.

Conflict: [paste, e.g. manager and direct report unable to align on performance, communication style, work allocation]. HR involvement triggered by: [paste, e.g. formal complaint, manager request, escalation]. Draft a 400-word memo to HR: facts of the situation (no editorializing), what each party's position is as I understand it, what has been tried, what I am recommending (specific intervention: mediation, role change, separation), my own potential bias I want HR to check. HR partners benefit from operators who lay out the situation honestly, not advocates.

Peer leader: [name, role]. Decision they are overriding (mine or my team's): [paste]. Their stated reason: [paste]. Why I think the override is wrong: [paste with evidence]. Draft a 300-word memo: state the decision and the override plainly, my evidence for the original decision, peer leader's stated reasoning fairly captured, the cost to my team and the work if the override stands, what I am asking (escalation to shared manager, OR my acceptance with stated conditions). Pick the path; do not fester.

Situation: I am [a board member / cofounder / exec] asking the board to override the CEO on: [paste decision]. The CEO's position: [paste]. My position: [paste]. Why I am escalating: [paste]. Draft a 600-word board memo: state plainly that I am asking for override (not for influence), the decision and both positions, the stakes if the CEO's decision stands, what I am asking the board to do specifically, what happens to the CEO relationship if the board overrides. This is one of the most consequential memos a senior person ever writes; clarity protects everyone.

Exec: [name, role]. Their comp ask: [paste]. My ability to grant: [paste]. Disconnect: [paste]. Draft a 300-word response: acknowledge their comp request specifically, name what we can do in the current framework, name what we cannot and why structurally (not 'company policy'), invite a specific timeline for revisiting if growth or scope changes warrant it. Honest; comp disputes that are softened with vague reassurances become turnover.

Disagreement is not strategic but values-based: [paste, e.g. how we treat departed employees, how we communicate misses externally, how we handle a customer who is also a friend]. Other party: [name, role]. Their position: [paste]. My position: [paste]. Draft a 400-word memo that does not pretend the values disagreement is a strategic disagreement: name that this is a values question, where my values come from, where I think theirs come from, what would happen to my role here if our values diverge structurally, propose a forum to surface this beyond the immediate decision. Values disputes that get treated as strategy disputes never resolve.

Dispute with: [name, role]. Has been ongoing for: [N] weeks. Decision needed by: [specific date]. Cost of further delay: [paste]. Draft a 200-word note to the other party: name that we have been at this for N weeks, the decision needs resolution by [date] for these specific reasons, propose three paths to resolution (one alignment session this week, escalation to shared manager next week, accept-and-commit on either side), single binary CTA. Pick the path within 48 hours of this note. The cost of dispute drift is higher than any single resolution path.

Quarter: [Q]. Missed: [paste, e.g. revenue 18% below plan]. Reason (real): [paste]. What we are changing: [paste]. Runway impact: [paste in months]. Draft a 600-word missed-quarter investor update: subject under 8 words naming the miss, headline (1 sentence honest about the period), the numbers with prior quarter and budget comparison, root cause in business terms (no 'macro headwinds' filler unless macro was actually the cause), what we are changing structurally, runway and the decisions that fall out of the new runway, what we are asking from investors. Honest tone; investors prefer painful honesty over softened spin.

Investor question: [paste, e.g. 'how much runway do you have at current burn']. My honest answer: [paste]. The decisions that follow from the answer: [paste]. Draft a 250-word response: lead with the specific runway number (months), the burn assumption that produced it, the lever I am most likely to pull if runway dips below [X] months (extend runway, raise, cut, or grow into the cost), the trigger that would force action. Specific tone; vague runway answers terrify investors more than honest tight answers.

Bridge round needed: [size, instrument, terms]. Reason: [paste honest]. Existing investors I am asking: [list]. Their typical bridge participation: [paste]. Draft a 400-word email opening the bridge conversation: honest framing (this is a bridge, not a new round), the size and terms, why we need it (specific not vague), what we will achieve with the bridge that justifies it, who is leading and what their participation level is, single binary CTA for a 30-min conversation. Bridge requests that hide why they are needed get worse terms.

Down round under consideration: [paste new valuation vs prior]. Reason: [paste]. Cap table impact: [paste in dilution]. Existing investors' anti-dilution and pro-rata implications: [paste]. Draft a 500-word memo: honestly name that this is a down round, the valuation and why (market or company-specific reasons), cap table impact specifically, what existing investors lose and what they keep, the alternative (no round, fold, or more aggressive cut), the CTA for the conversation. Down rounds that are not handled honestly destroy investor relationships.

Investor: [name, fund, board seat or not]. Their pressure: [paste, e.g. push to expand internationally before US is settled, push to raise prices, push to fire a specific exec]. My position: [paste]. Draft a 400-word response: acknowledge the strategic logic of their position (specifically), explain my counter-view with specific evidence, name what would change my position (specific signal), propose a checkpoint date where we revisit. Founder voice; investor pressure that is not engaged honestly festers into board-level conflict.

Founder: [me / my cofounder]. Situation: [paste, e.g. burnout, medical issue, family crisis, bandwidth problem]. Operating impact: [paste]. What we are doing: [paste]. Draft a 400-word disclosure note to existing investors: specific about what is happening (not euphemism), honest about operating impact, what we are doing structurally (not just personally), what we are asking the investors for (typically: patience, support for an interim arrangement, no public disclosure), what changes about the next milestones. Vulnerable but not collapsed; investors generally support founders who disclose honestly.

Cofounder: [name, role, equity]. Leaving: [paste reason and timing]. Equity treatment: [paste]. Operating impact: [paste]. Draft a 500-word investor disclosure: factual statement of departure (specific date), the actual reason (within bounds of what departing cofounder consented to share), how we are covering their function, equity treatment specifics (vesting acceleration if any, repurchase if any), what we are committing to investors going forward. Honest tone; cofounder departures are leading indicators investors track closely.

Crisis: [paste briefly]. What is true: [paste]. What is being misreported: [paste]. Our position: [paste approved messaging]. Draft a 600-word investor briefing: factual chronology of what happened, what we are responsible for and what we are not, our public statement and what we are not commenting on, operating impact estimated, what we are asking investors not to do (typically: not comment publicly, not speculate). Crisis briefings that are vague invite freelance investor responses that worsen the situation.

Round: [paste size, terms]. Lead investor: [name, fund]. Stage: [paste, e.g. term sheet signed but not closed, verbal commit not signed, due diligence in flight]. Their stated reason: [paste]. Draft a 400-word response: acknowledge their decision without arguing, ask the specific question that determines the path forward (was this preventable, is the round still viable, is this a soft no I can revisit), state what I am doing now (running an alternative process, pausing the round, restructuring). Honest; pretending a lead pull-out is okay does not make it okay.

Board call in [N] days. Period was: [paste honest assessment]. Headline metric: [paste]. Strategic decisions on the table: [paste]. Draft a 400-word board pre-read for a bad quarter: open with the headline (no setup), the numbers honest, root cause read, what we are changing, what we are not changing yet and why, the asks of the board. Calm founder voice; board calls about bad quarters that are well-prepared run shorter than board calls about good quarters that are unprepared.

Trigger: [paste, e.g. major customer churn, security incident, exec departure, fundraise emergency]. Required attendance: [list of board members]. Decision needed: [paste, specific not 'discuss']. Draft a 200-word emergency board meeting request: subject under 8 words specific to the trigger, the situation in 2-3 sentences (no preamble), the specific decisions that need board input or authorization, proposed time within 48 hours, the materials I will send 12 hours before. Treat the emergency as the emergency it is; do not soften.

Board member: [name, role on board]. Behavior: [paste, e.g. micromanaging an exec, going around the CEO to direct reports, public criticism of the team]. Frequency: [paste]. Impact: [paste]. Draft a 300-word memo to the board chair (or the lead investor if no chair): factual description of the behavior with specific examples, the impact on the team and the company, what I have already tried, what I am asking the chair to do (specific intervention: a direct conversation, a board norms reset, a removal). Document the behavior for the corporate record; do not handle alone.

Board member: [name]. Apparent conflict: [paste, e.g. portfolio company is competitor, family member is supplier, side investment in a deal we are considering]. Materiality: [paste]. Draft a 400-word memo to the board chair and corporate counsel: factual description of the conflict, what should be disclosed to the full board, what restrictions on participation should follow (recusal from certain decisions, information walls), what we will document going forward. Conflicts that are not surfaced create future legal and governance exposure.

Disagreement between: me (founder) and board chair. Decision: [paste]. Chair's position: [paste]. My position: [paste]. We have not been able to align in: [N weeks]. Draft a 400-word memo for the full board: state the disagreement plainly, both positions fairly captured, what each of us would commit to if the decision went the other way, what we are asking the full board to do (decision, not adjudication). Founder voice; chairs and founders who fight in private until one quits damage the company more than honest board memos.

Board member to remove: [name]. Reason: [paste, e.g. consistently absent, consistently disruptive, conflict of interest, past their useful contribution]. Their reaction expected: [paste]. Path to removal: [paste, e.g. expiration of seat, request to step down, vote]. Draft a 400-word memo to the board chair and corporate counsel: factual case for removal, the path I am proposing (preferred and fallback), what we say externally if asked, what their post-removal relationship to the company is. Board removals that are handled poorly become public and shape future board recruitment.

Board has voted to override me on: [paste decision]. Vote count: [paste]. My position is preserved in the minutes: [yes]. Path forward: [paste]. Draft a 300-word memo for the company record and for my own reference: factual statement of the override decision, my reservations (preserved for the record), my commitment going forward (I will execute the board's decision; I will note in the minutes if the outcome contradicts my prediction), what I would resign over if the next override is similar. Founder voice; the relationship between CEO and board is fiduciary, not personal.

Executive session: [date]. Attendees: independent and outside directors only. CEO/founder excluded. Topic: [paste, e.g. CEO performance review, exec comp]. Draft a 200-word communication from the board chair to the CEO after the session: factual summary of what was discussed (not the full content, but the topic and key resolutions), any feedback or directives the CEO needs to receive, the next checkpoint. Executive sessions are appropriate; how the board communicates after them shapes the CEO-board trust.

Board has completed CEO performance review. Verdict: [paste, e.g. on track / falling short / serious concerns]. Specific feedback: [paste]. Path forward: [paste, e.g. continue with check-ins, formal performance plan, replacement search]. Draft a 600-word memo from the board chair to the CEO: opens with the headline verdict, the specific feedback (factual, evidence-based), what is being asked of the CEO going forward (specific changes), the consequence path if changes are not made, the support being offered. Honest tone; CEO reviews that are softened set up worse outcomes.

Authority I am requesting: [paste, e.g. expanded hiring authority, exec hire signoff, M&A authority]. Current authority: [paste]. Reason for the request: [paste]. Draft a 400-word memo to the board: state the request plainly, the operating reason behind it (specific, not 'efficiency'), what scaffolding I commit to in return (reporting cadence, decision logging, trigger thresholds for board involvement), the trial period if any. Authority expansions that come with no scaffolding feel like power grabs; with scaffolding they feel like governance maturity.

Decision: [paste]. Vote: [paste count]. Dissents: [list with stated reasons]. Corporate counsel review: [yes]. Draft a 400-word memo for the corporate record: factual statement of the decision, the vote with named dissents and their stated reasoning, the precedent or fiduciary duty implication if any, the implementation timeline, who will execute. Board decisions that are well-documented protect the company in future litigation; decisions that are poorly documented become liabilities.

Incident: [paste type, e.g. data exposure, credential leak, breach]. Detected: [date]. Customer impact: [paste, e.g. specific data fields exposed, number of records, geography]. Draft a 300-word initial customer notification: subject under 8 words specific to incident type, lead with what happened in plain language (not 'we may have detected'), the specific data fields involved, when it happened and when it was contained, what the customer should do operationally, our point of contact for questions, when the next update will go out (specific time). No 'we take security very seriously' opener.

Incident type: [paste]. Jurisdictions affected: [paste]. Records involved: [paste count and types]. Detected: [date]. Reportable under: [paste relevant law]. Draft a regulatory notification template: factual chronology, scope (specific not estimated), affected data subjects (categories and counts), our containment and remediation actions, our point of contact, any cross-border or third-party processor implications. Plain factual tone; regulators read these to decide if cooperation is genuine.

Incident now public knowledge or about to be. Approved messaging: [paste]. What we are not commenting on: [paste, e.g. attribution, ongoing law enforcement, individual data details]. Draft a 250-word public statement: factual description of what happened, customer impact at scope (not under-stated), our containment and remediation, what customers should do, our point of contact. No 'sophisticated attack' / 'state-level actor' framing unless verified. No 'no evidence of misuse' phrasing if the investigation is incomplete.

Incident: [paste]. Timeline: detected [date], contained [date], remediated [date]. Root cause: [paste]. Customer impact: [paste]. Draft a 600-word postmortem in engineer's voice: factual timeline with specific times (UTC), root cause (technical and process), contributing factors, customer impact in detail, what we have changed in detection, prevention, and response, action items with owners and dates. Honest tone; postmortems that omit contributing factors lose internal trust as well as external.

Customer: [name, ACV, specific impact to them]. Incident overall: [paste]. Their specific exposure: [paste]. What we are doing for them: [paste, e.g. credit monitoring, dedicated support, contract amendments]. Draft a 200-word direct outreach email from the CSM or CISO: their specific impact (not generic), what we are doing for them specifically, what we are not asking them to do (e.g. they do not need to take action on X), our direct contact for any questions, when the next update will come. Personalized; mass-blast incident comms damage major accounts.

Researcher: [name, organization, contact]. Vulnerability: [paste, severity, scope]. Their disclosure timeline: [paste]. Our remediation timeline: [paste]. Draft a 200-word response to the researcher: thanks them specifically for the disclosure (not boilerplate), confirms our understanding of the vulnerability and severity, our remediation timeline (specific dates), our public disclosure plan, recognition we will offer if they want it (CVE, hall of fame, bounty). Treat researchers as partners; defensive responses to disclosures damage long-term security posture.

Incident: [paste, e.g. user violation of TOS, harassment in product, fraudulent account, content moderation issue]. Affected users: [paste]. Action taken: [paste]. Draft a 250-word communication to affected users: factual description of what happened (without identifying the bad actor inappropriately), what we did about it, what affected users should know (their account or data is fine, or specific actions they should take), what we are changing in detection or policy. Calibrated to the nature of the trust failure; do not over-claim safety guarantees.

Request: [paste type, e.g. subpoena, NSL, MLAT, civil discovery]. Issuing authority: [paste]. Scope: [paste]. Counsel review: [yes]. Draft a 400-word internal memo for leadership: factual description of the request, our legal obligations (what we must produce, what we may produce, what we must not produce), our process for responding, what gets disclosed to affected users and when, what gets disclosed to the public if anything. Internal memos for legal requests must be factual and counsel-aligned; this is not the place for advocacy.

Auditor finding: [paste, e.g. SOC 2 control gap, ISO finding, internal audit issue]. Severity: [paste]. Customer-facing implication: [paste]. Draft a 300-word communication for affected customers: factual description of the finding (in their terms, not auditor jargon), what it means for them specifically, what we are doing about it (with timeline), what changes about their use of our product if anything, our point of contact for questions. Plain language; trust gaps that customers learn about from third parties are worse than gaps they learn about from us.

Public claim: [paste]. New information: [paste why the claim is no longer accurate]. Path: [paste, e.g. update marketing, customer notification, regulatory notification if applicable]. Draft a 250-word communication: lead with the correction (not 'we want to clarify'), the new accurate information, why we are correcting now (new information not 'we want to be clearer'), what affected customers should do operationally, our point of contact. Honest tone; security claims that are walked back quietly become public scandal.

Recent churns: [paste names, ACVs, churn dates, stated reasons]. Time window: [paste, e.g. last 90 days]. Build a pattern-detection memo: list each churn with its stated reason and our internal read of the actual reason, identify the patterns (champion changes, integration issues, pricing competition, value gaps), name which customers in the active portfolio match the pattern (specifically), the action we are taking on each at-risk match. Honest tone; pattern detection that softens individual churns into 'unique' loses the cascade signal.

Churn problem: [paste, e.g. logo churn doubled, NRR dropped from X to Y, specific segment imploding]. Time window: [paste]. Suspected root cause: [paste]. Draft a 400-word memo to the CEO and exec team: lead with the magnitude (do not soften), the pattern, suspected root cause, what we have done so far, what we need from leadership (specific decisions: pricing flexibility, product priorities, exec sponsor coverage). Honest tone; exec escalation memos that bury the lede waste leadership time.

Segment churning: [paste, e.g. mid-market customers in a specific industry]. Common pattern: [paste]. Active customers in the segment: [list]. Draft a 250-word communication that is sent personally to each: acknowledges that we have noticed a pattern in the segment (without naming individual churns), surfaces the question we want to discuss with them specifically (their experience, their concerns), proposes a 30-min call. Cohort-specific outreach that goes generic loses the relationship signal.

Account: [name, ACV, ICP segment]. They are signaling churn intent. Churning them would trigger cascade in: [paste similar accounts]. Draft a 300-word founder-to-customer-exec note: acknowledges what is broken specifically, names what changes we are making structurally (not just for them), commits to a specific timeline, asks for what we need from them (a window of patience, a specific data point, a meeting). Founder voice; cascade prevention requires founder-level commitment that AE-level emails cannot make.

Cohort: [paste, e.g. customers with renewal in next 90 days, NRR in red zone]. Common risk pattern: [paste]. Customer-by-customer renewal date: [paste]. Build a per-customer outreach plan for the next 30 days: each customer gets a specific outreach calibrated to their renewal date and risk pattern, named owner (CSM, founder, or VP CS), specific decision point (continue save / escalate / accept controlled churn). Honest categorization; pretending all renewals are commits creates Q-end disasters.

Churn root cause we have detected: [paste, e.g. a specific feature gap, a specific integration issue, a specific UX failure]. Affected customers: [paste]. Magnitude: [paste in NRR or logo churn]. Draft a 500-word memo to Product leadership: factual evidence of the root cause (with customer quotes), magnitude in revenue terms not just count, what fixing it would change about retention, what we are asking Product to do (specific: prioritize a fix, document a workaround, accept the churn). Honest tone; CSM-Product relationships that hide churn data degrade quickly.

Pattern: [paste, e.g. customers in segment X are leaving for cheaper competitor Y]. Magnitude: [paste]. Pricing review under consideration: [paste, e.g. discount the segment, restructure tiers, hold pricing]. Draft a 400-word memo to the CEO and CFO: factual evidence of the pattern, the cohort math (if we discount, what is the revenue impact, what is the retention upside), what we are recommending, what we are not recommending and why. Honest tone; pricing decisions in response to churn require evidence, not panic.

CAB: [list of members]. Emergency session triggered by: [paste, e.g. cluster of CAB members threatening churn, common feedback pattern]. Topic: [paste]. Draft a 200-word CAB invitation: name the trigger honestly (these are CAB members; they will see through softening), the specific feedback or pattern we want to discuss with them, the decision authority we are bringing to the session (founder, exec sponsor), the time and format. Treat the CAB as partners; emergency sessions that pretend to be regular sessions damage the relationship.

Press inquiry: [paste, e.g. journalist asking about specific named customers leaving, industry analyst asking about retention metrics]. Approved messaging: [paste]. What we will not comment on: [paste]. Draft a 200-word response: factual on what we will say (typical retention metrics if we share them, our position on customer movements as normal in our category), specific on what we will not comment on (individual customer relationships), our point of contact for follow-up. No 'we are confident in our customer relationships' filler.

Team: [paste, e.g. all-hands, sales+CS+product]. Situation: we have a churn problem. Magnitude: [paste]. What changes: [paste]. Draft a 500-word internal communication: open with the problem (specific magnitude, do not soften), what we know about the root cause, what is changing structurally (not just 'we will work harder'), what is not changing (commitment to existing customers, the work that matters), what we need from each function. Calibrated to the team's emotional state; team comms that hide churn problems lose internal trust faster than they lose customers.

Vendor: [name, contract scope]. SLA missed: [paste specific metric and threshold]. Customer impact: [paste]. Their explanation: [paste]. Draft a 250-word vendor communication: factual statement of the SLA breach, customer impact in business terms (not technical), what we expect from them under the contract (credits, root cause, remediation), what we will do if the breach repeats (specific consequence, not vague threat). Cooperative tone; vendors who get vague SLA escalations escalate slowly.

Partner: [name, deal type]. Commitment: [paste, e.g. co-marketing campaign, co-sell motion, technical integration]. Their delivery: [paste, e.g. behind, off, ghosting]. Time window: [paste]. Draft a 300-word direct note to my counterpart at the partner: factual statement of what was committed, what has actually happened, the cost to my company specifically, what I am asking for in the next 14-21 days (specific actions with named owners on their side), what changes about the partnership if delivery does not happen. Direct without being adversarial.

Conflict: [paste, e.g. reseller and direct sales team competing on same account, reseller pricing undercutting]. Affected accounts: [paste]. Channel agreement terms: [paste]. Draft a 300-word note to the reseller's leadership: factual description of the conflict, the channel agreement provisions involved, what we are proposing (deal registration enforcement, specific account allocation, joint engagement), what we are not willing to do (compromise direct relationships). Treat the channel as partners; conflicts that escalate to legal damage future channel.

Partner: [name]. Integration: [paste]. Breakdown: [paste, e.g. their API broke ours, our update broke theirs, version sync failed]. Customer impact: [paste]. Draft a 400-word technical comms note: factual chronology, where the breakdown happened (specific not blame-shifting), customer impact, our remediation in flight, what we expect from them in the next 24-72 hours, the path forward for the integration (continue, redesign, sunset). Engineer's tone; technical partnerships that get political instead of factual fail in court of public opinion.

Partnership announcement: [paste, e.g. joint launch, customer-facing co-product]. We are ready: [paste]. They are not: [paste reason]. Original announce date: [paste]. Draft a 200-word note to the partner's lead: factual statement that we are ready and they are not, the cost to us of further delay (specific: customer expectations, internal commitments, marketing windows), what I am asking for (a new firm date or an honest 'this is not happening'), the consequence path. Direct; public partnership announcements that drift are harder to recover from than partnerships that get explicitly redesigned.

Vendor: [name, contract scope]. Price increase ask: [paste percent, reason given]. Renewal context: [paste, e.g. mid-contract, renewal]. Our leverage: [paste]. Draft a 300-word response: acknowledge the ask, name our position (accept, partial accept with concessions, decline), the specific structural reasoning (not 'budget'), what we are willing to negotiate (multi-year commit, scope reduction, payment terms), what we are not willing to negotiate. Cooperative tone; vendors who get adversarial responses to price asks escalate to leverage.

Situation: my company has been acquired. Integration period: [paste]. Acquirer pressure: [paste, e.g. forcing tooling change, demanding rebrand, pulling key team members]. Original acquisition agreement: [paste relevant terms]. Draft a 400-word memo to the acquirer's integration lead: factual statement of the pressure, the original agreement terms, what is reasonable in normal integration vs what crosses the agreement, what I am proposing (a specific decision path, escalation to acquirer's CEO if needed), the cost to acquisition value if the pressure continues. This is delicate; tone should be professional and grounded in the agreement, not adversarial.

Partner: [name]. Behavior: attempting to migrate our shared customer to their competing product. Evidence: [paste]. Customer relationship: [paste, e.g. they are still our customer but considering]. Draft a 300-word direct note to the partner's leadership: factual statement of the behavior with evidence, the partnership-agreement provisions involved (non-compete, non-solicit if applicable), what we expect (cease the poach, formal apology, contract amendment), the consequence path (terminate partnership, public statement, legal). Direct; partners who poach customers respond to firm legal-grounded letters faster than to relational appeals.

Vendor: [name]. Status: [paste, e.g. layoffs, missed payments, public filings, no response to escalations]. Our exposure: [paste, e.g. data hosted, integrations, contracts]. Customer impact: [paste]. Draft a 400-word internal continuity memo: factual assessment of vendor health, our specific exposure mapped to customer impact, the immediate steps (data export, alternate vendor evaluation, customer comms), the medium-term plan (migration, replacement, in-house). Then draft a 200-word customer-facing communication only if customer impact is real (do not pre-announce panic). Treat vendor death as ops emergency, not partnership grief.

Partner: [name]. Threat: [paste, e.g. cease-and-desist, breach claim, IP allegation]. Counsel involved: [yes/no]. My read of the merit: [paste]. Draft a 400-word internal memo to leadership and counsel: factual chronology of what led here, the partner's specific claims with our read on each, our exposure (financial, reputational, operational), what counsel is recommending, what I am recommending (settle, fight, document and wait). This is not the document where I draft the response to the partner; this is the document where leadership decides the strategy. Counsel-aligned; do not include statements that could be discoverable as admission.

Article: [paste headline, publication, journalist, key claims]. Claims that are true: [paste]. Claims that are false: [paste with evidence]. Approved external messaging: [paste]. Draft a 300-word public response: factual on the parts that are true (acknowledge specifically), factually correcting the parts that are false (with evidence, not denial), what we are doing about the substantive issues if any, our point of contact for follow-up. No 'we are deeply troubled', no 'reports of', no 'allegedly'.

Post: [paste link or content]. Reach: [paste estimate]. Specific complaint: [paste]. Reasonable parts: [paste]. Inaccurate parts: [paste]. Draft a 150-word public response (LinkedIn, X, or wherever the post is): acknowledges the reasonable parts specifically, corrects the inaccurate parts factually, names what we are doing, offers to take it offline. No defensive register; viral posts that get defensive responses go more viral.

Scandal: [paste, e.g. inappropriate behavior allegation, financial impropriety, public dispute]. Person involved: [paste]. Approved messaging: [paste]. What we are not commenting on: [paste]. Draft a 300-word company statement: factual on what happened (within bounds we can disclose), the action being taken (specific, not vague), the company's position separate from the individual, the next update timing. Do not pre-judge investigation outcomes; do not minimize the harm; do not make the statement about the company's reputation when the harm was to a specific person.

Pattern: [paste, e.g. multiple coordinated negative reviews, single severe review, ex-employee post going viral]. Specific claims: [paste]. Reasonable parts: [paste]. Inaccurate parts: [paste]. Draft a 250-word internal team communication AND a 100-word optional public response: internal is honest about what part of the criticism we accept and what we are changing; public response (if any) is short, factual, and does not engage on every claim. Do not over-respond; do not under-respond.

Customer: [name, role at company]. Their post: [paste, including specific complaints]. Our relationship history: [paste]. Resolution attempts so far: [paste]. Draft a 200-word direct outreach to the customer (private not public): acknowledges their post, the parts of the complaint that are accurate (specifically), what we have done since, what we are doing now, an offer to discuss directly. Do not respond publicly first; private resolution before public engagement preserves the relationship.

Employee: [name, current role and tenure]. Their public post: [paste]. Reasonable parts: [paste]. Parts that violated norms or contracts: [paste]. Draft a 300-word internal HR response document: factual statement of what was posted, what crosses contractual or policy lines (with reference to specific policies), what intervention is appropriate (conversation, formal warning, termination), what we will say externally if asked. Do not respond publicly to the employee; address it through normal HR process.

Situation: [paste, e.g. founder's personal politics, founder's personal relationships, founder's other business activity]. Public attention: [paste]. Internal team reaction: [paste]. Customer reaction: [paste]. Draft a 400-word internal memo from CEO or board chair to leadership: factual statement of the situation, the company's separation from the founder's personal activity (or alignment, depending on context), what we will say externally if asked, what is changing about company governance if anything. This is delicate; treat the founder as a person, not a brand asset.

Lawsuit: [paste, e.g. employment, IP, customer dispute]. Filed by: [paste]. Their public statements: [paste]. Our position: [paste, counsel-aligned]. Draft a 200-word public statement: factual on what we are commenting on (typically: 'we have just received the filing and will respond through the legal process'), what we are not commenting on (the substantive merits), our point of contact for media. Do not litigate in public; statements that argue the merits before discovery damage the case.

Trigger: [paste, e.g. competitor launched a competing product, competitor lowered prices significantly, competitor announced a feature parity]. Customer reaction: [paste]. Risk: [paste]. Draft a 400-word customer-facing positioning: factual on what the competitor announced (do not minimize), specific on what differs about our offering (with evidence), what we are doing to address gaps if real, what is not changing about our commitments to existing customers. No 'unique value proposition' filler; specific differentiators only.

Marketing claim: [paste]. Why it is no longer accurate: [paste]. Public visibility: [paste]. Draft a 200-word internal communication and a 100-word optional external statement: internal explains what we are changing in our positioning and why; external (only if claim was high-profile) factually corrects the claim and provides updated information. Do not announce the retraction louder than the original claim was made; quiet correction is appropriate for most cases.