Sample drafts·Voice-matched replies

Four messages. One voice Quillhall already writes in.

Each card below is an anonymized inbox on the left and the founder-toned reply on the right. The names, companies and scenarios are all stand-ins — the point is the register, the timing, and the way an awkward thread gets closed without it feeling forced.

Every sender uses a placeholder name, every company is fictional, and a small “Sample scenario · all names fictional” eyebrow sits on each card so a reader never has to wonder.

  • Investor

    Sample scenario · all names fictional

    Same voice as the founder’s investor updates — warm, specific, no over-promising on hours.

    Tuesday morning — T+30 minutes after a seed investor asked for an updated deck ahead of a partner meeting.

    Incoming

    From: Alex Rivera (seed investor — [Fund A])

    Subject: Deck refresh before Thursday partner sit-down

    Hey — pulling together a one-pager for our Thursday partner meeting. Could you send the latest deck plus anything you have on traction this quarter? Happy to grab fifteen minutes after if useful.

    Draft reply

    Subject: Re: Deck refresh before Thursday partner sit-down

    Hi Alex — Thanks for the heads-up and apologies for the short turn. I'll send two things by end of day tomorrow (Wednesday, ~48h): • the refreshed deck with the Q2 traction cut on slides 7–11; • the one-pager you can hand the partners directly, drafted in the same shape as our last update. If anything in the deck needs to land differently for the partner audience — tone, depth, what to drop — let me know and we'll respin before Thursday afternoon. Best, The team

  • Partnership

    Sample scenario · all names fictional

    Same voice as the partnership reply on the landing page — warm, asks one qualifying question, defers the intro without burning the thread.

    Wednesday afternoon — an SDR at [Vendor B] asks for a warm intro to the founder’s CRO before a proof-point ships.

    Incoming

    From: Sam Okafor ([Vendor B] — partnerships)

    Subject: Quick intro to your CRO?

    Hey — we work with three of your peers and think there's a clean overlap with what your team is shipping. Could you intro me to your CRO for a 20-min call next week? Happy to send the one-pager first.

    Draft reply

    Subject: Re: Quick intro to your CRO?

    Hi Sam — Thanks for reaching out and for the offer of the one-pager — I'll read it. Before I make the intro, one qualifying question: which of the three peer references is closest to our segment, and what outcome did their team measure after the first ninety days? The reason I'm asking: we're about six weeks out from shipping a proof-point that will shape how this conversation actually goes. Once that's live I'd rather make the intro with real signal than ask our CRO to spend a slot on a hypothesis. I'll circle back as soon as the milestone lands. Best, The team

  • Customer escalation

    Sample scenario · all names fictional

    Same voice as the founder’s escalation replies — owns it personally, names the engineering owner, gives a 24h SLA, sets the update cadence.

    Friday 17:42 — top-10 enterprise account reports that SSO is down across their org; on-call paged the founder directly.

    Incoming

    From: [Customer C] — VP People Operations

    Subject: URGENT — SSO outage blocking our Monday close

    SSO is hard-down for roughly 240 of our staff. Pay runs Monday morning and managers can't approve anything without logging in. We need an owner tonight, a 24h SLA, and a number to call if this drifts past midnight. Sorry for the heat — escalating because we have no path forward.

    Draft reply

    Subject: Re: URGENT — SSO outage blocking our Monday close

    Hi — Thanks for the page and for the detail in your note — that helps a lot more than a screenshot would. I am the owner on this until it is closed. Engineering owner on our side is [Eng Lead], who is on a call with your IT lead in the next five minutes and will own the bridge through resolution. What we are committing to tonight: • a hard 24-hour SLA on full SSO restoration across all 240 affected seats; • a check-in from me or [Eng Lead] every other hour, in this thread, until green; • a coordinated comms note for your people team to forward internally, drafted by us within the next hour. If anything slips past midnight CET, the number to call is mine — I will keep it open. Apologies for the disruption. We will close the loop with a written post-mortem and credit on next month's invoice, regardless of root cause. — [Founder]

  • Vendor

    Sample scenario · all names fictional

    Short, kind no with a single-sentence reason, then the right referral — never leaves the thread hanging or cold.

    Monday morning — a recruiter/vendor pitch arrives clipped mid-thread, signed only by a first name.

    Incoming

    From: J. ([Vendor D] — outreach)

    Subject: [no subject — thread clipped at first line]

    …saw your profile and thought this might be a fit. Open to a 15-min intro this week?

    Draft reply

    Subject: Re: a quick no, with a referral

    Hi J. — Thanks for reaching out. Not the right fit on our side right now — we're not hiring for the role your threads have been pitching the last few months. If your clients tend to be startup operators moving from staff to principal, the friend I would point you to is [Contact E] at [Referral Co]; they have hired twice through similar intros in the last quarter. Best of luck with the search. — [Founder]

Get on the roster

Drafts like these, written from your inbox.

The samples above are written in the founder’s voice — Quillhall learns your voice from prior correspondence and ships drafts you can approve in a tap. Join the founding cohort to see yours.

Get started — connect your inboxSee pricing