I am a [your role] at [your company, one-line description]. I want to reach [name, role at target company]. Specific signal I have noticed about them: [a project they shipped, a hire they made, a tool stack mentioned, a public post]. Draft a cold email under 80 words: lowercase subject under 7 words, body 60-80 words referencing the specific signal, single binary CTA. No phrases like 'leverage', 'transform', 'circle back', 'I hope this finds you well'.

Original cold email I sent on [date] to [name]: [paste original]. No response. Draft a follow-up under 40 words. Reference a fresh angle (not the same offer reframed). Single binary CTA. Do not say 'just following up', 'circling back', or 'bumping this up'.

I have sent [N] emails to [name] over [time period] with no response. Final touch. Draft an under-50-word email that respects their inbox, leaves the door open without pressure, and offers one specific resource (case study, calculator, post) they could use without ever talking to me. No guilt language. No 'final attempt' urgency tropes.

Already connected on LinkedIn with [name, role at target company]. Draft a 2-3 sentence DM referencing [specific signal I have noticed about them]. Single question CTA. LinkedIn-native voice, not email voice. Under 40 words. No 'thanks for connecting' opener.

Account: [company name]. ICP fit: [yes/no with one-sentence reasoning]. Stakeholders I want to reach: [list 3-4 names with roles]. Draft an outreach plan: who to reach first, what specific signal each one gets in their email, what the sequence is across the 4-stakeholder set over 2 weeks. No mass-blast; each touch references something specific to that person.

Triggering event for [company]: [funding round, exec hire, product launch, layoff, M&A, regulatory action, public post by exec]. Draft a 60-80 word cold email to [name, role] that references the event, names the implication for their work, and offers one specific resource. Do not pretend the event is good news if it is bad news; calibrate tone to the event.

I sent a cold email to [name]. Their reply: [paste]. They have shown interest but have not committed to a meeting. Draft a 50-70 word response that advances the conversation: confirms a specific question or constraint they raised, offers a 20-minute frame, gives them a single binary yes/no. Do not re-pitch.

I sent a cold email to [name]. Their reply contained this objection: [paste their objection]. Draft a 50-80 word response that takes the objection seriously, offers one piece of evidence or reframe specific to their objection, and ends with either a binary CTA or an explicit 'no worries if not' close. Do not pretend the objection is invalid.

Target: [name, role at target company]. I have read these public sources about their work: [paste 1-3 quotes/links]. Draft a 70-90 word cold email where the first sentence references something specific from the research that proves I read their work. Body 50-60 words. Single CTA. No flattery; specificity replaces flattery.

Target account: [company]. Senior contact I want to reach: [name, senior role]. Likely internal champion who would benefit from my product before getting senior buy-in: [name, role of champion]. Draft a cold email to the champion that names the senior decision-maker, frames the offer as 'help you build the business case', and ends with a binary CTA.

Account: [company]. Stakeholders on the call: [names with roles]. Source material I have: [paste 10-K excerpts, recent news, LinkedIn posts, prior call notes, anything specific]. Build a pre-call brief structured for a 10-minute prep window before a 30-minute discovery call: account in one paragraph, why-now signals (3 bullets), per-stakeholder profile (role, tenure, one signal that matters), what they likely care about (3-5 bullets), recommended opening (1-2 sentences). Do not invent any fact not in source material.

Buyer role I am meeting: [exact title and seniority]. Their likely priorities at a [stage] [industry] company: [list 2-3]. My product solves: [one sentence]. Draft 12-15 discovery questions structured by category: situation questions (3-4), pain questions (4-5), implication questions (3-4), commitment questions (2-3). Each question is open-ended, not yes/no. None of the questions are leading.

Demo audience: [role and seniority of attendee, plus any others]. Their stated priority based on discovery: [paste]. My product's strongest match for their priority: [feature/workflow]. Build a 30-minute demo agenda: 5 minutes context recap, 18 minutes product walk focused entirely on their stated priority, 4 minutes objection-anticipation Q&A, 3 minutes mutual next-step. Do not include feature tours of unrelated areas.

Customer's current workflow for [the problem]: [paste their description]. Pain points they named: [paste]. Build a demo storyline that walks through their workflow step-by-step in my product, highlighting where my product removes a step or compresses a step. Story arc: their problem -> their current pain -> my product's specific step-by-step replacement -> the named outcome they would see. Do not pitch features; tell the workflow story.

Discovery call I just finished: [paste transcript or notes]. Build a structured debrief: headline (1 sentence), attendees, decisions made (bullets), next steps with owner and date (bullets), MEDDIC update with explicit unknowns marked as such, risks and friction surfaced (bullets), 2-3 coaching observations on my own performance, recommended next-call action (1-2 sentences). Distinguish what the customer said from what I inferred.

Demo I just finished with [name(s), role(s)]. Their stated priority: [paste]. What I showed in the demo: [paste outline]. Their reactions and questions: [paste]. Draft a follow-up email under 200 words: thanks them for time, recaps the one specific thing that resonated (their language not mine), names the 2-3 next-step options with timing, ends with a single binary CTA. No 'as discussed' filler.

Account: [name]. Where I am in the deal: [stage]. What I know so far: [paste any context about the buyer, their needs, prior calls]. Build a MEDDIC scorecard: each letter scored 0-3 with evidence, gaps explicitly marked, top 2-3 questions I need to ask in the next call to close the biggest gaps. Score based on documented evidence, not my confidence. 'AE thinks' is a 1; 'PO issued' is a 3.

I am in stage [N] with [account]. My current contact is [name, role]. I do not yet know who the economic buyer is. Draft 4-5 discovery questions that surface the economic buyer naturally without making my contact feel demoted. Each question is operational (about how decisions are made for this category) not personal (about who has authority). Phrasing should be peer-to-peer, not investigative.

Demo audience: [3-5 stakeholders with roles]. Each stakeholder's likely priority: [list per person]. Build a multi-stakeholder demo agenda for 45 minutes: opening 5 min, role-by-role workflow walk (3-5 min each), shared Q&A (10-15 min), mutual next-step (5 min). For each role's segment, name what specific feature or workflow connects to their stated priority. No generic feature tour.

Exec on the call: [name, exec title]. Their public statements about [topic]: [paste 2-3 quotes from earnings calls, podcasts, LinkedIn]. Build a 5-minute exec-skim brief: their stated priority in their own words, the specific business outcome they care about, one specific way my product maps to that outcome, three questions to ask that respect their time. Exec-language not vendor-language. Under 250 words.

I am a [founder/PM] at [stage company]. The problem I am exploring: [one sentence]. The hypothetical customer I am interviewing: [their role and stage]. Draft 12-15 customer development interview questions: 3-4 about their current workflow (no leading), 4-5 about pain in that workflow (no leading), 3-4 about what they have tried already, 2-3 about what would have to be true for a new tool to be worth switching to. Questions must not pitch the product. None should be answerable with yes/no.

Customer dev call I just finished. Customer: [role, company stage]. My hypothesis going in: [paste]. What they actually said: [paste transcript or notes]. Build a synthesis: who I talked to (1 line), what they said in their own words (4-6 quoted snippets), where their reality matched my hypothesis (2-3 bullets), where their reality contradicted my hypothesis (2-3 bullets), validation rating (validated / partially / not), recommended next step. Bias toward their words not mine.

I have done [N] customer dev calls in the last [timeframe]. Notes from each: [paste each call's notes/synthesis]. Find the patterns: which pain points appeared in 3+ calls, which workflow steps were named consistently, which 'what would have to be true' answers converged. Output: a table of patterns with frequency count, plus a 1-paragraph summary of what is now validated, what is still ambiguous, what needs more calls.

Customer dev round just completed. [N] calls. Hypothesis we tested: [paste]. Findings: [paste pattern detection output]. Draft a validation memo for the internal team: headline (1 sentence: validated, partially, or not), evidence (3-5 bullets quoting customers), what changes about the build plan (1 paragraph), what additional research is still needed (1 paragraph). Honest read; do not soften 'not validated' into 'partially validated'.

Account I am meeting tomorrow: [name]. Source material I have: [paste 10-K excerpts, news, LinkedIn profiles, podcast quotes, prior notes]. Build a 10-minute pre-call brief: account in one paragraph, why-now signals (3 bullets), per-stakeholder profile (role, tenure, one signal that matters), what they care about (3-5 bullets), conversation angles (3-5 specific topic-bridges), risks and traps (2-3 bullets), recommended opening (1-2 sentences). Cite source for every specific fact; omit anything not sourced.

Founder-led sales call I just finished. Account: [name]. The call: [paste notes]. Build a founder-debrief: what the buyer said about my product specifically (in their words), what they said about their own situation (in their words), what they did NOT say that I expected them to (the gap), what part of my pitch landed and what fell flat, recommended next step. Founder-tone not AE-tone; honest about my own performance.

I am about to do a reference call between my prospect [name, company] and my existing customer [name, company]. Goal: prospect hears authentic value validation. Draft a 5-minute prep brief for my customer (the reference): what topics to cover, what NOT to discuss (open issues, pricing specifics), 4-5 question prompts the prospect is likely to ask. Customer should sound like themselves, not like a marketing testimonial.

I am running win-loss interviews on the last [N] deals. Win interviews: 8-10 questions covering why-us, why-now, what almost killed the deal, what would have made it close faster. Loss interviews: 8-10 questions covering why not us, what we got wrong, what the winner did better, would they reconsider. Each script under 25 minutes. Open questions only. No leading.

Win-loss interviews I have run in Q[N]: [paste notes from each, win and loss separately]. Build a synthesis: top 3 reasons we won (with frequency), top 3 reasons we lost (with frequency), one pattern in won deals that we should systematize, one pattern in lost deals that we should fix, what stays the same, what changes. Honest about losses; do not soften.

I am hosting a Customer Advisory Board with [N] customers. Stage of company: [stage]. What I want input on: [paste 2-3 strategic questions]. Draft an agenda for a 90-minute session: opening 10 min (context-setting), 3 discussion blocks of 20 minutes each (one strategic question per block, with 3-4 prompt questions per block), closing 10 min (commitments and next CAB date). Discussion not presentation; customers should talk 70%+ of the time.

Period: [week or month]. Audience: my manager. Numbers: [paste 3-5 metrics with prior-period comparison]. Wins: [paste 2-3]. Risks: [paste 1-2]. Asks: [paste 1-3 or 'none']. Draft an under-400-word weekly status: headline (1 sentence), numbers (3-5 lines), what landed (2-3 bullets), what we are watching (1-2 bullets), asks (named or 'no asks this period'), next milestone (1 line). Direct operational tone. No 'exciting progress' or 'continue to focus on' filler.

Period: [month]. Audience: exec team (CEO, peer functional leads). Numbers: [paste]. Wins: [paste 2-3]. Risks: [paste 1-2]. Asks: [paste]. Draft an under-600-word monthly review: headline-first (the one thing they should remember), the numbers, named wins with owners, named risks with what we are doing, asks called out as their own section. Exec-tone: short on operational detail, long on direction.

Period: [month]. Audience: existing investors. Numbers: [paste ARR, MRR, growth, runway, customer count, NRR if available]. What landed: [paste]. What slipped: [paste]. Asks: [paste]. Draft an under-600-word investor update following the structure: subject line under 8 words, headline (1 sentence honest about the period), 4-5 metrics with comparison, what we shipped, what slipped (do not soften), 1-3 specific asks, next milestone with date. Honesty bias; bad news leads.

Board meeting in [N] days. Period covered: [quarter]. Numbers I will share: [paste]. Strategic decisions on the table: [paste]. Build a board pre-read under 800 words: cover headline (the thing the board should know), numbers section, strategic decision context (what we recommend, what we considered, what we rejected), risks the team is watching, asks of the board. Slide-by-slide outline structure.

Period: [week or month]. Audience: whole team. Wins: [paste]. Customer stories: [paste]. Roadmap update: [paste]. Asks of the team: [paste]. Draft an under-500-word all-hands update: opening hook, named wins with owners, customer stories (in customer's words where possible), roadmap update with what changed, asks of the team. Energizing tone but not hype; specific not abstract.

My team: [function]. Audience team: [function]. Period: [week]. What my team did that affects them: [paste]. What we need from them: [paste]. Draft an under-300-word cross-functional update: what we shipped that they should know about, what is changing that affects their work, what we need from them with specific ask and owner. Operational tone; respect their time. No politics.

Project: [name]. Original target: [date or milestone]. Current state: behind. Reason: [paste honest]. New target: [date]. What is needed to hit the new target: [paste]. Draft an under-300-word status: lead with 'we are behind on X' (do not soften), root cause (1 sentence), what we are changing, new target with date, asks. Honest tone; stalled-project status updates that hide the slip create worse outcomes than honest ones.

Quarter: [Q]. Plan I committed to at quarter start: [paste]. Where I am at midpoint: [paste, honest including misses]. Forecast for end of quarter: [paste]. Draft an under-400-word mid-quarter check-in: where I am vs plan (named hits and misses), forecast for quarter end with confidence level, what I am changing, what I need from manager. Self-aware tone; soft mid-quarter checks become bad surprises at quarter end.

Period: [week]. KPIs to report: [paste 5-8 KPIs with current value and prior-period value]. Targets: [paste targets]. Draft a structured KPI scorecard: each KPI on its own line with current / prior / target / variance, 2-3 sentences of commentary on the most important variance, recommended action (if any). No padding.

Incident in progress: [paste description]. When it started: [time]. Customer impact: [scope]. Current status: [investigating / mitigating / resolved]. Audience: internal stakeholders. Draft an under-200-word status update: what is happening, who is impacted, what we are doing, when next update will go out. Calm tone; specific not vague. No 'we are working hard on this' filler.

Deal: [account name, dollar amount, stage]. Last activity: [type, date, substance]. Stakeholders engaged: [list with roles]. AE-claimed close date: [date]. AE-stated context: [paste]. Score this deal: MEDDIC (each letter 0-3 with evidence, gaps marked), risk flags (stage inflation, single-threading, stale, phantom champion, late-changing close, procurement skip, verbal commit), 2-4 specific coaching questions for my 1:1 with the AE, recommended action this week. Be honest; do not soften because the AE is confident.

All deals up for discussion: [paste account / amount / stage / last activity / claimed close date for each]. Build a pipeline scrub: rank deals from weakest to strongest, name the top 3 most-likely-to-slip and why, name the top 3 most-likely-to-close and why, recommend the single highest-leverage action across the pipeline this week. No softening on the weak deals.

My forecast: [paste deals categorized as commit / upside / risk]. Manager will challenge me on each. Draft a structured prep doc: per deal, the one-sentence reason it is in the category I claimed, the one piece of evidence the manager will probably push back on, my response. Honest where the evidence is thin. No happy-path padding.

AE forecast I am about to inspect: [paste]. Per deal, build the inspection plan: what I will ask the AE about each deal (specific question), what would change my opinion on the category (specific evidence), what coaching opportunity I should surface in 1:1. No deal accepted at face value; every category requires evidence.

Deal: [account name, ACV, lost reason claimed]. Timeline of the deal: [paste key milestones]. What was working: [paste]. What broke: [paste]. Build a deal post-mortem: root cause (specific not vague), contributing factors (3-5), what we missed in earlier stages, what would change about the playbook, pattern check (does this resemble other lost deals). Honest read; the goal is learning.

Deal: [account name, ACV]. Won, but with friction. Timeline: [paste]. The moments we almost lost: [paste]. What saved it: [paste]. Build a post-mortem on a near-loss-converted-to-win: which moment was actually decisive, what we did right at that moment, what we got lucky on, what part of the playbook needs to be hardened so we do not need luck next time.

Champion in this deal: [name, role]. Evidence I have of their advocacy: [paste]. Build a champion test: 5-7 specific things a real champion would have done by this stage that this person either has or has not done (introduced me to the EB, shared internal docs, defended us in their team meeting, provided the data I need, told me about their internal politics). Score honestly: real champion or hopeful champion.

Account: [name]. Stakeholders engaged so far: [list with roles, last interaction date]. Map the multi-thread: which key roles are still unengaged (CFO, CIO, head of department, end-user lead), which engaged stakeholder is going stale (no contact in 14+ days), where the relationship is dangerously single-threaded. Recommend the 1-2 specific outreach moves this week.

Deal stuck at stage [N] for [N] days. Last meaningful activity: [date]. AE-stated reason for the stall: [paste]. Build a stuck-deal recovery plan: investigate (1-2 specific questions to ask the champion this week), reset (a specific value-restoration move), escalate (when this becomes manager-owned). Do not pretend a stalled deal is just 'maturing'.

Quarter: [Q]. AEs reporting to me: [N]. Quarter outcome: [hit / miss number]. Pipeline going into next quarter: [paste]. Draft a 1-page review for my VP: hit/miss with one-sentence reason (do not soften), top 3 wins with named drivers, top 3 misses with root cause, one structural change I am making, asks of VP. Honest tone.

Account: [name, ACV, segment, tenure]. Current health score: [N out of 100]. Trend: [paste up/down/stable + delta over time period]. Drivers: usage [paste], support [paste], sentiment [paste], engagement [paste]. Renewal in [N] days. Build a health read under 300 words: current score with category, trend, drivers in weighted order, root cause read (1-2 sentences naming the specific pattern), recommended action (1-3 specific moves with owners and timing), renewal-distance calibration.

Account: [name, ACV]. Health score: [N, dropped from M]. Root cause: [paste champion change / integration drift / exec departure / etc]. Renewal in [N] days. Build a 90-day save play: days 1-7 investigation moves (specific calls and data to pull), days 8-30 value-restoration moves (specific actions tied to root cause), days 31-60 re-engagement moves (exec re-alignment, expanded usage), days 61-90 trajectory check with decision (continued save / escalate / planned controlled churn). Specific escalation triggers per phase.

New customer: [name, ACV, segment]. Their stated priority: [paste]. Their team (named owners): [paste]. Build an onboarding kickoff plan: success criteria (3-5 specific outcomes by day 90), milestones (day 7, 30, 60, 90 with concrete checks), named owners on customer side and our side per workstream, executive alignment (sponsor named on each side, cadence), Time-To-Value target with specific date for first measurable outcome.

Account that just churned: [name, ACV at time of churn, tenure, segment]. Churn reason given: [paste]. Timeline of warning signs: [paste, ideally with health score history]. Build a churn post-mortem: root cause (specific pattern named, distinguished from contributing factors), 3-5 leading indicators that aligned, what should have triggered earlier action, pattern detection (do other accounts in the portfolio show this pattern, name them), recommended changes to health score weighting and save play design.

Account: [name]. Original use case: [paste]. Adoption metrics by feature/module: [paste]. Build an adoption gap analysis: which features are at expected adoption, which are below expected, which are unused entirely, root cause read (training, fit, champion, integration), recommended re-engagement moves prioritized by impact-to-effort. No 'the customer should try harder' framing; the gap is our signal.

Account: [name, ACV]. Executive sponsor on customer side just left: [their name, role]. New executive: [name, role, what we know about them]. Build a 30-day sponsor-transition plan: research (LinkedIn, public statements, prior role), introduction approach (warm if possible, cold-but-warm if not), what to surface in the first call, what NOT to bring up in the first call, what success looks like at day 30.

Account: [name]. Original champion: [name, role, departed/changed roles]. New likely champion candidate: [name, role]. Build a champion-rebuild plan: re-establish use case fit with the new champion, re-discover their definition of success (it may differ from original champion's), 30-day cadence to validate the new relationship, decision point at day 30 (committed champion / not really a champion / look further).

Account: [name]. Quarter covered: [Q]. Value delivered: [paste named outcomes]. Adoption read: [paste]. Support and health: [paste]. Roadmap items aligned to their priorities: [paste]. Draft a 6-slide QBR outline: slide 1 headline value (the one thing they should remember), slide 2 specific quantified outcomes, slide 3 adoption read with gaps named explicitly, slide 4 support and health trends, slide 5 roadmap alignment, slide 6 mutual asks (1-2 of customer, 1-2 of us). No marketing-pitch tone.

Renewals coming up in next [90 days]: [paste account / ACV / renewal date / health score / current state]. Build a renewal forecast table: each account categorized commit / upside / risk with one-sentence reason, total commit dollars, total upside dollars, total at-risk dollars, gap to NRR target (if known), top 3-5 plays this quarter to close the gap. Honest categorization; do not round Risk into Commit.

Account: [name, ACV]. Health: critical (below 40). Renewal in [N] days. CSM-owned save play has not recovered the account. Build a 1-page escalation memo for the VP CS or CRO: situation (1 paragraph), root cause (1 paragraph), what has been tried (bullets), what we are asking the exec to do (specific ask: a call, a concession authority, a product commitment), decision point. Honest; the escalation reader needs the real picture.

Account: [name]. Expansion signal observed: [paste, e.g. 89% seat utilization, new team announced on LinkedIn, module usage exceeding tier ceiling]. Champion: [name, role]. Draft an under-120-word expansion outreach: subject under 8 words specific to the signal, body referencing the signal in customer's terms (not ours), framing as 'we noticed X, here is one way Y could help', single binary CTA. No sales-pressure language.

Account: [name, ACV]. Renewal in [N] days (target: 90). Health score: [N]. Champion: [name]. Draft an under-150-word pre-renewal note: open the renewal conversation explicitly (do not let the customer be surprised at day 30), surface what they would lose if they did not renew (specific outcomes from the year), invite the conversation about multi-year or expansion. No urgency tropes.

Pre-renewal conversation just happened with [name]. Their stated priorities for next year: [paste]. Renewal pricing options I am proposing: [paste 2-3 options]. Draft an under-250-word renewal proposal email: thanks for the conversation, recap of their stated priorities (their words), the proposed options aligned to those priorities, what each option includes, their decision deadline (typically 5 business days from receipt). Do not pressure-test.

Account: [name, ACV]. Strong health, 12+ months in, champion is engaged. I want to propose a multi-year extension. Draft an under-150-word note that opens the multi-year conversation: lead with their progress (specific outcomes), name the multi-year option as a 'lock-in your pricing' (not 'commit to us longer'), single binary CTA for a 30-min conversation. Frame as their advantage not ours.

Renewal moved into procurement at [account]. Procurement contact: [name]. My champion: [name, still supportive]. Draft an under-100-word procurement-friendly note that confirms the renewal terms (no surprises), names my champion as the strategic owner (so procurement's discount-seeking does not strip the relationship), provides the documentation procurement will need. Cooperative tone; procurement is doing their job not adversarially.

Account: [name, ACV]. Renewal at risk because [paste reason: budget cut / competitor threat / champion left / value question]. Manager has approved a [pricing concession or term flexibility]. Draft an under-200-word note that opens the negotiation conversation: acknowledge their constraint specifically (not abstractly), present the concession as 'one way we could meet you', frame it as a partnership decision not a vendor giveaway. Single binary CTA for a call. Do not lead with the discount.

Account: [name]. They have hit [Nth] seat threshold for the year. Their team is growing. Draft an under-100-word email to my champion: name the milestone in their terms, propose adding [N] seats with the math, ask for the right operational contact to push the change through. Operational tone; this is a happy email.

Account: [name]. They are using [module/tier] heavily and recently asked for [feature that lives in higher tier]. Draft an under-150-word module add-on note: surface that the feature they asked for is in higher tier (transparently, no gotcha), present the upgrade math (cost, what they unlock, value justification), single CTA for a conversation. Customer-outcome-led not vendor-revenue-led.

Existing customer: [name, current contract scope]. Different team in the same company that would benefit: [team / use case]. Path to introduction: [paste, ideally my current champion]. Draft an under-150-word note to my current champion asking for a warm intro to the other team. Frame as 'your colleagues at [team] are probably hitting the same problem; happy to be introduced if you think it would help them'. Respect that this is asking for a favor.

Account: [name]. End of contract year. They have not had a formal QBR. Outcomes during the year: [paste]. Draft an under-300-word year-in-review note: top 3 specific outcomes (their numbers), top 2 things we are excited about for the new year together, one ask (multi-year, expansion, intro to another team, or just a 30-min sync). Customer-outcome-led.

Topic: [paste, ideally a specific observation or counter-take]. My background that gives me credibility on this topic: [one phrase]. Draft a 150-300 word LinkedIn post: hook (first line is strong enough to stop the scroll), body that tells one specific story or makes one specific observation (not a 5-bullet list of lessons), close that invites a single conversation (not 'thoughts?'). Operator tone not influencer tone. No emojis.

Niche insight I want to share: [paste]. My specific evidence (data, story, or observation): [paste]. Draft a 6-9 tweet thread: hook tweet (the contrarian or specific claim), 4-7 supporting tweets (each a single concrete fact or beat in the story), closing tweet (the implication, not 'follow me'). Each tweet under 280 chars. No 'a thread:' meta-language.

Topic: [paste]. The specific experience that prompted this post: [paste]. The audience: [paste]. Build a 6-8 section outline for an 1500-2500 word blog post: opening hook (the specific moment), context (what was the problem), the build (what I tried), what worked, what failed, what I would do differently, the generalizable lesson, the close. Each section gets one paragraph of guidance. Specific story not abstract framework.

Newsletter audience: [paste]. This issue's main piece: [paste topic]. Recent context that connects to the piece: [paste]. Draft a 100-150 word intro paragraph that hooks the reader: starts with a specific moment or observation, bridges to today's piece, ends with a one-sentence preview. Operator tone, no 'happy Monday' opener.

Talk topic: [paste]. Audience: [paste conference and audience profile]. Specific point I want to make: [paste]. Draft a 100-150 word abstract: the contrarian or specific claim, why it matters now, what the audience will take away, one specific story I will tell. No filler 'in this talk we will explore' opener; lead with the claim.

Podcast: [name, host, audience profile]. Episode topic: [paste]. The host's likely angle: [paste]. Build a prep doc: 3 specific stories I should be ready to tell, 3 contrarian takes I genuinely hold on this topic, 3 questions I should ask the host (not the audience), the one thing I want a listener to remember. Authentic-voice prep, not corporate talking points.

Customer: [name with permission]. Their starting situation: [paste]. What they implemented: [paste]. Specific outcomes: [paste, with quantified numbers and quote if available]. Draft an under-700-word case study: the situation in their voice, the change in their voice, the outcome with their specific numbers, what changed for their team. No marketing fluff; let the customer's words do the work.

Hire: [role and seniority]. Why this hire matters now: [paste]. The person joining: [name, prior role]. Draft an under-200-word announcement post: the strategic context (one sentence), why this person specifically (one paragraph in operator-tone), what they will own, what is now possible. No 'thrilled to announce' opener.

Round: [size, stage, lead, valuation]. Specific context that matters: [paste, e.g. specific milestone hit, specific use of funds, specific market moment]. Draft an under-300-word funding announcement in founder voice: open with the specific context not the round, the round detail, what we are doing with the funds (specific not vague), thanks (sincere not performative), what we are hiring for. No 'pleased to announce' or 'on a mission to'.

Launch: [product, feature, milestone]. Date: [paste]. The specific problem this solves: [paste]. Draft an under-200-word pre-launch post: the specific moment that made the problem visible, the product description (concrete not abstract), one specific data point or story that shows it works, what happens on launch day. Curiosity not hype.

Role: [title, seniority]. Why this role exists at this company at this stage: [paste]. Hard requirements (evidence-based not pattern-match): [paste]. Soft signals: [paste]. Comp range: [paste]. Location/remote policy: [paste]. Draft an under-700-word JD: title, why this role exists, what first 90 days look like (3-5 concrete deliverables), hard requirements, soft signals, what we offer (explicit comp range, equity, location), how to apply. No 'rockstar', 'ninja', 'cultural fit', 'fast-paced'. No marketing copy.

Candidate: [name, current role and company]. Specific work they have done that I want to reference: [paste link or description]. Role I am sourcing for: [title, comp range]. Draft an under-80-word sourcing email: subject under 7 words, body referencing their specific work (not 'I came across your impressive profile'), one-sentence role description, single binary CTA. No first-name-token spray-pray. No 'amazing opportunity'.

Candidate: [name]. Resume: [paste]. Hard signals for the role: [paste]. Soft signals: [paste]. Anti-patterns: [paste]. Build a screening scorecard: hard signals scored 0-3 each with evidence from resume, soft signal indicators visible from resume so far, anti-pattern flags (if any), recommendation (advance / hold / decline) with 2-sentence rationale. Refuse to score on pattern-match proxies (school name, employer prestige) when the role calls for specific work evidence.

Role: [title, seniority]. Hiring loop stage: [phone screen / hiring manager / panel / final]. Interviewer focus area: [paste]. Time: [duration]. Build an interview rubric: 4-6 questions with scoring criteria each, what strong evidence looks like for each, what weak evidence looks like, anti-pattern signals to listen for. Calibrated so different interviewers score against the same scale.

Candidate: [name]. Interviewers: [list]. Each interviewer's feedback: [paste]. Build a debrief structure: decision (hire/no-hire/strong-hire/strong-no-hire), evidence for (specific bullets per interviewer), evidence against (specific bullets per interviewer), dissent (named: if any interviewer disagrees, capture their case explicitly), outstanding questions (if more data needed), recommended next step. Surface dissent rather than averaging consensus.

Candidate: [name]. Role: [title]. Comp: [base, equity %, vesting schedule]. Start date: [proposed]. Location/remote: [policy]. Decision deadline: [typically 5 business days]. Draft an under-300-word offer letter: explicit on every term (no surprises), what they own in first 30/60/90 days, who they report to, point of contact for questions, decision deadline. No salesy language; offers should read like the careful documents they are.

Candidate: [name]. Stage where rejected: [paste]. Reason for rejection: [paste, must be evidence-based not bias-coded]. Draft an under-200-word rejection note: thanks them by name, brief specific feedback when offered (tied to evidence not assumption), encourage future application if relevant, offer to keep in touch if relevant. Respectful of their time and dignity. No form-letter feel.

Candidate: [name]. Role we are considering them for: [title]. Reference being called: [name, relationship to candidate]. Build a 10-12 question reference set: 3-4 about candidate's actual work (specific examples), 3-4 about working style (with hypothetical scenarios), 2-3 about what could derail them at our stage, 1-2 about what they are looking for next. Open questions only. Calibrated to surface evidence not just confirm.

Candidate: [name]. Reference: [name, relationship]. What the reference said: [paste notes]. Build a reference synthesis: key evidence (3-5 specific examples from the call), strengths confirmed (tied to hard signals), gaps or concerns (tied to anti-patterns or unaddressed signals), questions the reference could not answer (areas where another reference is needed), recommendation (proceed / proceed with caveats / additional reference needed).

Role: [title]. Hiring manager: [name]. Why this role exists at this company at this stage (1 paragraph): [paste]. Hard signals: [paste 3-5]. Soft signals: [paste 3-5]. Anti-patterns: [paste 3-5]. Comp band: [paste]. Sourcing strategy: [paste]. Build a 1-page intake brief that the recruiter and hiring manager align on: this is the contract for the search; if signals change, the brief updates explicitly. No 'rockstar' or 'unicorn' filler.

Decision needed: [paste]. Context: [paste]. Options I am considering: [paste 2-3]. My recommendation with reasoning: [paste]. Audience: [decision-maker(s)]. Draft an under-400-word async decision memo: bottom line up front (the recommendation), context (1 paragraph), options with one-paragraph reasoning each, my recommendation with specific evidence, decision deadline. Reader should be able to make the decision without a meeting.

Project: [name]. Goal: [paste, specific not abstract]. Owner: [name]. Stakeholders: [list with roles]. Timeline: [paste]. Draft an under-500-word project kickoff doc: goal (specific outcome with measurable success criterion), why now, who owns what (named per workstream), timeline with named milestones, dependencies on other teams, communication cadence, decision-making process for issues that arise mid-project.

My week: shipped [paste], blocked on [paste], next week [paste]. Audience: my team. Draft an under-150-word async standup: shipped (1-2 lines), blocked on with specific ask (1-2 lines), next week (1-2 lines). Operational tone; respect that 5 people are reading 5 of these. No padding.

Working norm I am proposing: [paste]. Context that prompted this: [paste]. Trade-off involved: [paste]. Audience: my team. Draft an under-200-word Slack message: lead with the proposed norm (1 sentence), context (2-3 sentences), trade-off acknowledged, ask for input (specific: thumbs up / 'concern, will respond by X' / DM with concerns). Time-box the response window.

Initiative: [name]. Sponsor exec: [name]. Team: [list]. Period: [week]. Progress: [paste]. Risks: [paste]. Asks: [paste]. Draft an under-400-word async update: headline (one sentence on overall trajectory), progress against milestones (named with hit/miss), risks with named owner, asks of specific cross-functional partners. Reader should know in 90 seconds whether they need to do anything.

Disagreement with: [name, role]. The decision: [paste]. My position with reasoning: [paste]. Their position as I understand it: [paste]. Draft an under-400-word disagreement memo: state the decision plainly, my position with evidence, their position fairly stated (steel-manned), what would change my mind, what we propose if we cannot align (escalate to specific decision-maker). Honest tone; not adversarial.

New team member: [name, role, start date]. Their background: [paste]. The team they are joining: [paste]. Draft a 30-60-90 day onboarding plan: week 1 (people to meet, docs to read, no shipping yet), days 8-30 (first concrete deliverable, named owner), days 31-60 (second deliverable + first cross-functional partnership), days 61-90 (independent contribution + first feedback cycle). Specific not generic.

Project: [name]. Original target: [paste]. Actual outcome: [paste]. Gap: [paste]. Draft an under-500-word async post-mortem: lead with the gap (do not soften), root cause (specific not vague), contributing factors (3-5 with named owners), what worked despite the miss, what we are changing structurally, no individual blame language. Honest learning tone.

Senior person: [name, their role and how I know them]. Specific favor: [paste]. Why them specifically: [paste reason that respects their time]. Draft an under-200-word email: lead with respect for their time (one sentence acknowledging they get many of these), specific ask (named, scoped, time-bounded), why them specifically (the reason it is not anyone else), how this helps me, easy way to decline. No 'pick your brain' opener.

Disagreement with peer team: [other team]. Decision needed by: [date]. My position: [paste]. Their position: [paste]. We have not aligned in [N] meetings. Audience: shared exec sponsor. Draft an under-300-word escalation memo: decision needed (1 sentence), each side's position fairly stated, where we agree, where we disagree, the cost of further delay, what we are asking the exec to do (specific decision authority, not just 'help us align'). Respectful.