Period: [month]. Audience: existing investors. Numbers: [paste ARR, MRR, growth rate, runway in months, customer count, NRR, gross margin if known]. What we shipped: [paste]. What slipped: [paste honestly, do not soften]. Asks of investors: [paste 1-3, or 'no specific asks this month']. Draft an under-600-word monthly investor update: subject line under 8 words, headline (1 sentence honest about the period), 4-5 metrics with prior-period comparison, what we shipped (named with owners), what slipped (root cause not excuse), specific asks called out as their own section, next milestone with date. Bad news leads. No 'crushing it' or 'on track' filler when it is not.

Quarter: [Q]. Audience: existing investors. Headline metric: [paste, e.g. ARR went from X to Y]. Strategic shifts during the quarter: [paste]. Numbers: [paste full set]. Customer wins: [paste 2-3]. Customer losses or near-losses: [paste]. Draft an under-1000-word quarterly investor update: subject under 8 words, headline, the strategic narrative for the quarter (1-2 paragraphs explaining the why behind the numbers, not just restating numbers), full metrics table, customer wins (named with quote if available), losses with root cause, what we are doing differently next quarter, asks. Honest tone; investors read these in 3 minutes and decide whether to lean in or back away.

Round we are planning: [size, instrument, target lead profile]. Timeline to formal raise: [paste, e.g. starting in 4 weeks]. Investor I am emailing: [name, fund, prior interaction]. Last update they received: [date]. Draft an under-200-word teaser email: subject under 7 words, body acknowledging timing, naming the round shape, asking for either a 30-min conversation or 'tell me when you are ready to see the deck'. Single binary CTA. No 'I hope you are well' opener. No urgency tropes.

Investor: [name, fund, partner I am reaching]. Specific reason this fund fits: [paste, e.g. they led X round at Y similar company; partner has written publicly about Z thesis we live in]. My company: [stage, ARR, sector in one phrase]. Draft an under-150-word cold investor email: subject under 7 words referencing their specific work, body 80-120 words connecting their thesis to my company specifically (not generic), single binary CTA for a 20-min conversation. Treat the investor as a sophisticated peer; do not pitch the company in the cold email.

Stage: Series A. ARR: [paste]. Growth rate: [paste]. Headline differentiator: [paste in one sentence]. Investors I will pitch: [paste profile]. Draft a 12-15 slide deck outline tuned for Series A pattern matching: slide 1 company in one sentence, slide 2 the problem in customer's words (with quote), slide 3 the product (specific), slide 4 traction (specific numbers and growth shape), slide 5 customers (named logos with outcome), slide 6 GTM motion, slide 7 unit economics, slide 8 market and timing, slide 9 competition (honest), slide 10 team (with credentials), slide 11 how we use the round, slide 12 the ask. Each slide one paragraph of guidance on what goes there. No filler slides.

Investor question I just got: [paste]. Context: [paste deck stage, prior conversation context]. The honest answer: [paste]. Draft an under-200-word email response that takes the question seriously, gives the honest answer, includes the supporting evidence, addresses the underlying concern not just the surface question. No deflection. No corporate filler. Investors who ask hard questions are testing whether you can answer them; deflection ends the process.

Term sheet I just received: [paste key terms: valuation, liquidation preference, board composition, anti-dilution, pro-rata, vesting, no-shop, conditions]. My priorities: [paste]. Draft a 1-page review for my own decision-making (not the investor): each term scored against my priorities (founder-favorable, market, founder-unfavorable), 3-5 items I should push back on with reasoning, 2-3 items where the friction is not worth fighting. Honest read; counterintuitive terms named. Do not draft the negotiation reply yet; this is my own scratch pad.

I am recruiting a board member. Profile I am looking for: [paste, e.g. operator who has scaled from $5M to $50M ARR in our category]. Target candidate: [name, current/prior roles]. Why them specifically: [paste]. Draft an under-200-word board outreach email: subject under 7 words, body 100-150 words specific to their work, framing as 'I am building a board of operators who have done this before', single binary CTA for a 30-min conversation. Treat as senior peer not as recruiter.

Investor passed on the round. Their stated reason: [paste]. Round status: [paste, e.g. closed without them, still open]. Draft an under-100-word response: thanks them by name, acknowledges the reason without arguing, leaves the door open for future ('I'll keep you posted on milestones'), no negotiation. Graceful tone; the next round is in 18-36 months and the relationship persists.

Year covered: [year]. Headline outcomes: [paste 3-5 things that genuinely defined the year, not just metrics]. What changed strategically: [paste]. What we got wrong: [paste honestly]. What we are committing to next year: [paste]. Draft an under-1500-word annual investor letter: opening hook (specific moment from the year), the strategic narrative, full metrics with prior year comparison, named wins, named misses with root cause, the year ahead (committed objectives not aspirational vision). Founder-voice; this letter compounds over years and shapes investor confidence.

Board meeting in [N] days. Period covered: [quarter]. Numbers I will share: [paste]. Strategic decisions on the table: [paste 2-3]. Risks the team is watching: [paste]. Asks of the board: [paste]. Draft an under-2500-word board pre-read structured as: cover headline (the thing the board should know in 30 seconds), period metrics (full table with prior comparison and budget variance), strategic decision context (each decision: what we recommend, what we considered, what we rejected, what we need from the board), risk register with named owners, asks of board (specific, named individuals where relevant). Board should be able to make decisions without us walking through every slide live.

Board meeting: [date, attendees]. Pre-read shipped: [date]. Specific decisions needed: [paste]. Discussion topics not requiring decision: [paste]. Build a 90-minute agenda: opening 10 min (CEO update, no slides), 30 min on decisions (each decision gets specific time block, not 'discussion'), 30 min on strategic discussion topics, 15 min closed session (no founder/CEO), 5 min wrap and action items. Time-boxed; if the meeting cannot decide in the time given, the decision was not pre-read sufficiently. No 'open Q&A' as a default block.

Period: [quarter]. Plan was: [paste budget]. Actual was: [paste]. Variances above 10%: [paste with reasoning]. Cash position: [paste current, monthly burn, runway in months]. Draft a 3-slide financial section: slide 1 plan vs actual table (revenue, expenses, EBITDA), slide 2 variance commentary (each variance over 10% explained in 2 sentences with corrective action), slide 3 cash and runway with scenarios at 80% / 100% / 120% of plan. CFO-quality numbers; do not invent.

Period: [quarter]. KPIs to report: [paste 5-8 KPIs with current and prior quarter values]. Draft a 2-3 slide non-financial section: slide 1 KPI dashboard (table format, current / prior quarter / change), slide 2 commentary on the most important variance, slide 3 (optional) cohort or retention curve if relevant. No marketing metrics that are not predictive of revenue. No vanity numbers.

Strategic decision the board needs to weigh in on: [paste]. Context: [paste]. Options I am considering: [paste 2-3 with one-paragraph reasoning each]. My recommendation: [paste]. Risks of the recommendation: [paste]. Draft a 2-page strategic memo: bottom line up front (the recommendation in one sentence), context (1-2 paragraphs), options analyzed honestly (including the option I am rejecting and why), my recommendation with specific evidence, risks, what I am asking the board to do (not 'discuss' but specific decision authority). Honest tone; boards that get advocacy memos disengage; boards that get decision memos engage.

Exec team: [list of attendees with functions]. Period: [quarter]. What we shipped: [paste]. What slipped: [paste]. Strategic moves under consideration: [paste]. Build a 3-hour quarterly exec sync agenda: hour 1 review (numbers, what shipped, what slipped, no slides — discussion), hour 2 strategic decisions (each decision time-boxed with named decision owner), hour 3 cross-functional asks (each function names asks of others). No status presentations; this is decision time, not reporting.

Exec team. Standing weekly. Time: [N] minutes. Build an agenda template that runs the same every week: opening 5 min CEO update (one specific thing), 10 min metric review (this week vs last, no commentary unless a metric is moving), 30 min decision queue (each decision pre-read by team, time-boxed), 10 min cross-functional asks, 5 min wrap and action items. Repeatable; any week that does not have decisions to make should be cancelled, not held.

Decision: [paste]. Audience: exec team. Context: [paste]. Options considered: [paste 2-3]. My recommendation with reasoning: [paste]. Draft an under-500-word async decision memo: bottom line up front (the recommendation), context (1 paragraph), options analyzed (the rejected ones too, with why), my recommendation with evidence, decision deadline (specific date and time). Reader should be able to vote without a meeting; if they cannot, the memo is incomplete.

Disagreement with: [name, role]. The decision: [paste]. My position with reasoning: [paste]. Their position as I understand it (steel-manned): [paste]. Draft an under-500-word disagreement memo for shared review: state the decision plainly, my position with evidence, their position fairly stated (steel-manned, no straw man), where we agree, where we disagree, what would change my mind, escalation path if we cannot align (named decision-maker or board referral). Honest but not adversarial; co-founder disputes that fester get worse, not better.

Annual planning offsite. Length: [paste, typically 2 days]. Attendees: [list]. Pre-work: [paste]. Build a 2-day agenda: day 1 morning company-level decisions (vision, strategy, top 3 priorities), day 1 afternoon function-level commitments (each function presents OKRs, board challenges them), day 2 morning resource allocation (headcount, budget by function), day 2 afternoon dependencies and risks. Output is a written annual plan, not a deck. No 'team building' time blocks; offsites are for decisions.

I am the founder of [company name, one-line description]. We just shipped [paste recent specific milestone]. Target: [name, role at target company]. Specific signal about them: [paste]. Draft an under-100-word founder-to-buyer cold email: subject under 7 words, body 60-80 words referencing the signal and using founder credibility (not third-person company voice), single binary CTA. Tone: peer to peer, not vendor to buyer. No 'reaching out' opener.

First discovery call with: [name, role, company, ICP fit yes/no]. My company stage: [paste]. What I know about them: [paste]. Draft a 45-min founder-discovery agenda: 5 min context (who I am, why I built this), 25 min discovery questions (their workflow, their pain, what they have tried, what would have to be true), 10 min product demonstration (only if discovery confirmed fit), 5 min mutual next-step. Founder discovery does not pitch in the first 30 minutes; founders earn the right to demo through good questions.

Demo I am giving in [N] days. Discovery findings: [paste]. Their stated priority: [paste]. My product's strongest match: [paste]. Build a 30-min founder demo flow: 5 min recap of their stated priority and what I heard, 18 min product walk anchored entirely to their priority (not a feature tour), 5 min addressing the objections I anticipate from discovery, 2 min mutual next-step. Founder demos are different because the founder can commit on roadmap; calibrate the walk for things the buyer would benefit from us building if they bought.

Buyer asked about pricing. Stage of conversation: [paste]. Buyer profile: [paste, e.g. seed-stage SaaS, 25 employees, no procurement]. My standard pricing: [paste]. Draft an under-200-word pricing email: subject under 7 words, body explaining the pricing logic (not just the numbers), the two-tier or three-tier options that fit their profile, single binary CTA for a 20-min call to walk through fit. Founder pricing conversations are easier than AE pricing because the founder has authority to flex; do not overuse that.

Account I have been running founder-led: [paste name, ACV, stage]. Reason for hand-off: [paste, e.g. we hired a VP Sales, account is now stage 4]. New owner: [name, role]. Champion at the customer: [name, role]. Draft an under-150-word email to the customer's champion: explain that [new owner] is taking over, why this is good for them (more attention, faster response, dedicated coverage), maintain the founder relationship as backup ('I am still around if you need me'). Reassuring tone; champion changes feel destabilizing for the customer if not framed properly.

Account: [name, ACV]. Stage: in negotiation. Friction: [paste, e.g. price, contract terms, security review]. Where I have authority to flex: [paste]. Where I cannot flex: [paste]. Draft an under-250-word negotiation positioning email: acknowledge their constraint (specifically), present the flex I can make, explain the constraints I cannot flex on (with reasoning, not just policy), single binary CTA. Founder tone; willingness to engage on the substance, not just rote policy enforcement.

I am exploring [problem]. Hypothetical customer profile: [paste]. Specific person I am interviewing: [name, role]. Draft 12-15 customer dev questions specifically tuned for founder credibility: 4 about their current workflow (no leading), 4 about pain in that workflow, 3 about what they have tried, 2 about what would have to be true for them to switch, 2 about what they would expect to pay (not 'how much' but 'what would feel like a no-brainer'). Open questions only. Founder voice acknowledges the founder is here to learn, not pitch.

Reference call between my prospect [name, company] and existing customer [name, company]. The customer is doing me a favor; I want them to share their authentic experience. Draft a 5-min founder-level prep brief I send the customer (the reference): topics to cover that match the prospect's stated priority, things they should not feel obligated to say (price, anything embarrassing for us), 4-5 question prompts the prospect is likely to ask. Treat the reference as a partner, not a marketing asset.

Buyer's objection: [paste, e.g. you are too small, you are too new, you might pivot, your roadmap might shift]. The honest answer: [paste]. Draft an under-150-word response that takes the objection seriously, gives the honest answer (including what is true about it), reframes around what only an early-stage founder-led product can offer them (direct founder access, flexible roadmap, ground-floor pricing), single binary CTA. Honest; objections about stage are usually correct, and pretending otherwise erodes trust.

Deal that died: [paste reason]. Buyer: [name]. Final touch I want to send. Draft an under-100-word email: thanks them by name for the time, acknowledges the reason without arguing, offers one specific resource they could use without ever talking to me again (a calculator, a guide, a relevant blog post), leaves the door open without urgency. Graceful; founders run into the same buyers in 18 months at different companies.

We have [N] customers, planning the first-20 founder cadence. Customer profile: [paste]. Draft a cadence plan for the founder's direct relationship with each of the first 20 customers: monthly 30-min check-in for first 90 days, quarterly thereafter, annual exec sync. Each meeting has a structured agenda (what is working, what is broken, what would unblock you, what should we build next). Output: a written cadence policy the team can execute against and a per-customer tracker template. Not optional; first-20 founder relationships shape product more than any other input.

Customer: [name, company, role]. They onboarded [N] weeks ago. Outcomes I have seen so far: [paste]. Draft an under-150-word founder check-in email: thanks for onboarding, names a specific outcome I observed (not generic 'glad you are using us'), asks what is working and what is not, single binary CTA for a 20-min sync. No 'how is everything going?' opener; specific check-ins surface real signal.

Existing customer: [name, role, company]. Tenure: [N months]. Goal: founder customer dev call to learn what is changing for them. Draft 8-10 customer dev questions: 3 about their current usage (specific, naming features), 3 about how their work has evolved since they started using us, 2 about what they would change if they had a magic wand, 2 about what they wish we shipped next. Open questions; founder voice; let them lead.

Customer: [name, ACV]. I am running a founder-level QBR (not a regular CSM QBR). Period: [year]. What I know: [paste outcomes, adoption, team changes]. Draft a 4-slide founder QBR: slide 1 the strategic narrative for our partnership (their business outcome, our role), slide 2 specific value delivered (their numbers), slide 3 where we have not delivered yet (honest), slide 4 mutual roadmap conversation (what we are building, what they need from us). Founder QBR is not a CSM QBR; it is a peer conversation about strategic alignment.

Account: [name, ACV]. CSM-owned save play has not recovered the account. Reason for founder intervention: [paste]. Draft a founder save play: specific email to my customer's exec sponsor offering a founder-to-exec call (not a sales pitch), agenda for that call (their pain, our roadmap commitment if any, decision point), what authority I am bringing to the conversation that the CSM does not have. Founder intervention is rare; if used too often it loses force. Use it for accounts where the relationship matters more than the deal.

New customer: [name, ACV, executive sponsor]. Their stated business outcome: [paste]. Why I am personally running the kickoff: [paste, e.g. strategic logo, multi-year potential, design partner]. Draft a 60-min founder-led kickoff agenda: 10 min relationship context (who I am, why this customer matters to us, why I am personally involved), 30 min joint definition of success (their words for what success looks like), 15 min mutual roadmap conversation (what we are building that maps to their priority, what they need from us), 5 min cadence and handoff (CSM owner, exec cadence, founder availability). Treat the customer as a partner.

Customer: [name]. Outcome: [paste, e.g. they expanded ahead of renewal, they referred two new customers, they spoke at our event]. Draft an under-150-word founder thank-you note: specific to what they did, names the outcome for our company without making them feel used, expresses real appreciation in founder voice (not corporate gratitude), no follow-up CTA (this is not a sales email). Sometimes the right move is just to say thank you.

Customer: [name, ACV]. I want to ask them to be a reference for prospects, a case study, or a speaker at our event. Why them specifically: [paste]. Draft an under-200-word founder ask: specific to their outcome (not generic 'you are awesome'), names the specific reference type I am asking for (1:1 reference call vs case study vs event speaker — not all at once), explains why their story matters, gives them an easy way to decline. Respect that this is asking for a favor; reference customers are doing us a favor not the other way around.

I am building a Customer Advisory Board with [N] customers. Stage of company: [paste]. CAB cadence and time commitment: [paste]. Customer I am inviting: [name, role]. Why them: [paste]. Draft an under-200-word CAB invitation: explains why I am building the board, why I want them specifically (their work, their experience), what the time commitment is (specific), what they get out of it (early product preview, peer network, founder access), single binary CTA. Treat as senior peer ask.

Customer that just churned: [name, ACV, tenure]. CSM has done the standard churn post-mortem. I am doing the founder-level review. Draft a 1-page founder-level post-mortem: the strategic question (was this customer ever a fit?), the pattern question (does this churn match other churned accounts?), the product question (what did this customer want that we did not build?), the team question (where did the relationship break, and was it preventable?), the structural takeaway (what changes about how we sell, onboard, or build because of this churn). Honest founder voice; no individual blame.

Role: [title, seniority, e.g. VP Engineering, first marketing hire]. Why this role exists at this stage: [paste]. Target candidate: [name, current/prior roles]. Specific reason them: [paste, e.g. they scaled a similar function from 5 to 50 at a company in our adjacent market]. Draft an under-150-word founder sourcing email: subject under 7 words, body 80-100 words referencing their specific work, framing as 'I am hiring for the role we both know is the inflection point', specific compensation range, single binary CTA for a 30-min conversation. Founder voice; treat as senior peer.

Role: first [function] hire. Company stage: [paste]. What this role exists to do in the first 90 days: [paste, e.g. ship the first marketing motion that produces 50 SQLs/month]. What this role exists to do in the first 12 months: [paste]. Draft a 1-page founder-voice role definition: specific 90-day deliverables (3-5), specific 12-month outcomes (3-5), what the role is not (so the hire does not waste time on adjacent work), reporting line, comp band, equity range. First hires fail when the JD is generic; this JD is specific to the actual problem.

Role: [title, seniority]. Recruiter or sourcer I am working with: [name]. Build a 1-page founder intake brief: why this role exists at this stage in 1 paragraph, hard signals (3-5 evidence-based not pattern-match), soft signals (3-5), anti-patterns (3-5 — what disqualifies, e.g. 'never operated below 200 employees' for an early-stage role), comp band including equity, sourcing strategy (what kinds of companies to source from, what kinds to skip). Treat as the contract for the search; if signals change, this brief updates explicitly.

Senior candidate: [name, role, prior companies]. Role I am hiring: [paste]. Draft an under-30-min founder interview structure: 5 min company context (real not pitch), 15 min their experience (specific, evidence-based — what did they actually do, not what their team did), 5 min how they would approach the first 90 days here (specific not 'I would assess'), 5 min their questions (treat as interview signal). Founder interview is calibrated to surface evidence and pattern fit, not to sell the company.

Candidate: [name, role being offered]. Initial offer: [paste base, equity %, vesting]. Their counter: [paste]. My authority: [paste, e.g. I can flex equity by X%, I cannot flex base above Y]. Draft an under-200-word negotiation response: acknowledge their constraint specifically, present what I can flex, explain what I cannot flex with reasoning (not just policy), single binary CTA for a 20-min call to align. Founder tone; willing to engage on the substance, not just rote enforcement.

Company stage: [paste]. Equity pool size: [paste]. Granting framework I am running: [paste]. Audience: internal (existing team, new hires). Draft a 1-page founder equity philosophy memo: how we think about equity (specific, not 'we believe equity matters'), how we calibrate grants by role and stage, how we handle refresh grants, how we think about acceleration, what we will not do (specific anti-patterns we have seen, e.g. peanut-butter equity, founder-favored ratchets). Honest founder voice; equity is a 7-year decision and clarity prevents drift.

Candidate: [name]. Grant being offered: [paste percent, vesting, cliff]. Their question: [paste, e.g. is this fair, what does it become, is it ISO/NSO, what about acceleration]. Draft an under-300-word explanation: acknowledge the question seriously (equity questions are sophisticated), explain the grant in real numbers (not 'this could be worth $X' speculation but 'at our current $Y valuation this is $Z'), explain vesting and cliff, address the specific concern they raised. Honest; do not over-promise outcomes.

Candidate: [name, role, where rejected]. Reason for the decision: [paste, evidence-based not pattern-match]. Their experience during the process: [paste, e.g. 4 rounds, two reference calls]. Draft an under-200-word rejection note: thanks them by name for the process, specific feedback when offered (tied to evidence not assumption), respect for their time and the depth of their engagement, offer to keep in touch with intent (not 'we will reach out if anything changes' boilerplate). Senior candidates remember senior rejections; this affects future referrals and recruiting reputation.

Conversation: [paste, adding a co-founder OR removing a co-founder]. Stage: [paste]. Equity implications: [paste current cap table and proposed change]. Draft a 1-2 page founder memo for the existing team and board: the strategic case for the change (1 paragraph), the equity adjustment with reasoning (specific numbers and dilution math), the role and authority changes, the timeline. This is one of the highest-stakes founder conversations; honest tone, board-ready.

Employee: [name, role, tenure]. Reason for separation: [paste]. Severance and equity treatment: [paste]. Draft a separation conversation script the founder can use: specific opening (no surprise pretext, name the decision in the first sentence), reason in business terms (not personal), specific terms of separation (severance amount, COBRA, equity treatment, references policy), space for their questions, what we will say externally if asked (already aligned). Founder voice; this conversation is hard but clarity prevents harm to both sides.