all guides

Get your first paying customers, one playbook at a time.

23 distribution playbooks, written out message by message: what to send, on which day, to whom, and when to stop. Type your product once and every template fills itself in.

free library
  • 23 playbooks
  • 71 ready-to-send messages
  • 7 buying moments
  • 123 post templates
Findwho's ready this weekReachpick one playbookSendfollow the sequenceMeasurewhat paid, weeklyEVERY WEEKrun more ofwhat paid

Type it once. Every template updates.

Saved only in this browser. Anything left empty stays as a highlighted slot you fill in by hand, so it can never be sent by mistake.

1 · make it yours

make it yours

showing an example product, shipnote. paste your site and we fill it in, or type yours once, and every template, search and message across the libraries switches to it.

paste your site and we read that public page on our server to fill these, keeping the result for 24 hours. what you type stays in this browser, unless you press “write it for me” on the offer post, which sends these fields to write it and keeps nothing.

the free autofills on this connection are used up for this hour

a shared connection counts as one, so this can happen on your first try. it resets within the hour, or join the waitlist and get 5 more today.

one email when vibedraft opens, and a short build note now and then. one click to leave.

Get the vibedraft newsletter, launch updates, and a chance to become a beta tester. Unsubscribe any time.

you · offer post previewexample

shipnote is for solo founders who ship weekly. what it does: writes release notes from commits what it fixes: writing the changelog by hand every friday $19 a month. link in the reply.

filled from the example product{slot} you fill in by hand

add your product's name and who it is for (or what it does) above, and it can write this for you.

Pick your stage. Start with the plays that fit it.

Each stage lists three plays to start with and more that raise your odds once those are running. Running everything at once is how founders end up with lots of activity and no result, so add one play at a time, after the last one has a readout.

2 · where are you
Your stage

Pick the one that sounds most like you right now.

Each playbook, step by step.

A playbook is one repeatable way to reach one kind of buyer. Pick one: what it does, four facts, a timeline, then every message in order with when it goes out, the channel, and whether you send it or it can be scheduled. Last, what you are offering and the result that tells you to stop.

3 · run the playbook

23 of 23 playbooks

Community answers

Listen and reply3 steps

Find the thread where someone asks the question your product answers, and give the best answer in it.

where it runs
Reddit, Hacker News, X
your time
30 min a day
the one number
replies, then visits
works best when
taking stock; doing it by hand; tried it and it failed
  1. day 0Reddit · HN · Xyou send
  2. day 2same threadyou send
  3. day 7X, your accountscheduled
1day 0Reddit ·HN · X2day 2same thread3day 7X, youraccount

you send, a person every time scheduled, can be set up once

  1. day 0Answer in the threadyou sendReddit · HN · X
    {their situation in your words} is exactly where I was with shipnote.
    
    what worked: {specific step}, then {specific step}. took about {time}.
    
    the thing I'd skip: {common wrong move}. it cost me {real cost}.
    5 open

    Answer fully. No link unless the community allows it and they ask.

  2. day 2Follow up, only if they repliedyou sendsame thread
    glad it helped. one more thing that matters at your stage: {detail specific to their numbers}.
    
    I wrote up the full setup if you want it. happy to drop it here.
    1 open

    They engaged, so offer more. The link goes in only after a yes.

  3. day 7Turn it into a postscheduledX, your account
    {n} people asked me some version of "{question}" this week.
    
    short answer: {answer}.
    
    the longer version, with the exact setup, is in the reply.
    3 open

    Generalize it. Never name or quote anyone without their permission.

the offerThe answer itself. The product only if they ask.

when to stop10 answers and 0 visits: change where you're looking, not the wording.

About this motion: listen and reply

Answering people who are already asking. The motion behind most first customers: find the thread, answer the question in their words, and only then say what you built.

Answer first, pitch never first. The reply has to be useful with the product removed. The link comes after they ask, or in the next message.
Inside the window. Most asks are answered within a day. A reply three days late helps nobody and reads as a pitch.
A person sends it. Templates give you a draft. You post it, every time.

the loop every play in this motion runs

  1. Watch the watering holessubreddits, X searches and forums, for asks and pain
  2. Judge the matchis this a real person with the problem, inside the window?
  3. Draft the answerin your voice, using the thread's own words; no link
  4. Post it yourselfby hand, every time
  5. Follow up only on a replya DM or a second reply once they answer, never before
  6. Measure per placesignups per subreddit, search or forum; drop places that never convert

what it is, in industry terms

Social listening
also: community-led sellingWatching the places buyers talk and answering in public, in their words.
Signal-based selling
also: intent-based outboundReaching people right after they show the problem in public, and only them.
Reply guy (done well)
also: engagement-led growthBeing the most useful reply under posts your buyers already read.
Speed to lead
also: response timeThe thread gets answered within a day; the play only works inside that window.

Seven moments that mean someone needs you this week.

Most people who fit your product are not looking right now. These are the moments when they are, and when they say so in public. Outreach that starts from one of these gets answered; outreach that does not usually gets ignored. See all 24 on the buying moments map.

4 · who is ready to buy

the window after a launch

Scroll the timeline sideways to see all 60 days.

day 0day 7day 14day 21day 28day 35day 45day 60day 3 to 45: looking for help, still open to changemonth onelaunchsettled in,harder to reach

After a launch, the stretch from about day 3 to day 45 is when a founder is looking for a way out of the silence and has not yet accepted it. A starting guess, not a measured figure.

1

Tried it and it failed

They did the obvious thing and it didn't work.

looks like
Launched, got a handful of upvotes and no signups.
find it in
Launch directories with dates: Uneed, Fazier, Startup Fame, Smol Launch.
opening line

saw your launch on {platform}. {their result} after that much work is rough.

2 open
playbooks for it
2

Unhappy with their current tool

Budget exists and they already understand the category. The current tool is letting them down.

looks like
Complaining about or cancelling a competitor.
find it in
Switching threads, cancellation posts, review-site complaints.
opening line

what made you want to leave beamer? asking because I built the other kind.

playbooks for it
3

Set up, but no results

All the setup, none of the payoff.

looks like
Payments connected and people signing up, but $0 revenue.
find it in
Public revenue boards like TrustMRR that show payments set up with zero revenue.
opening line

you've got payments wired and people signing up. the gap between that and a first payment is usually one thing.

playbooks for it
4

Taking stock

They shared their results in public and asked what they mean.

looks like
A 'month one' or 'year in review' post.
find it in
Search for 'month one', 'year in review', open-startup pages. Spikes about four to five weeks after launch.
opening line

thanks for posting real numbers. the one I'd look at first is {their weakest step}.

1 open
playbooks for it
5

Doing it by hand

A spreadsheet, a script, a ritual they resent.

looks like
Writing every post by hand, tracking leads in a sheet.
find it in
'I built a script for this', template downloads, questions about the manual method.
opening line

the spreadsheet version of this works until about {n}. after that it eats your week.

1 open
playbooks for it
6

Crossed a threshold

Funding, a first hire, a plan limit, a deadline.

looks like
First hire, second product, outgrew a free tier.
find it in
Announcements, job posts, changelog and pricing-page changes.
opening line

congrats on {milestone}. that's usually when writing the changelog by hand every friday stops being doable by hand.

1 open
playbooks for it
7

Trying again

Back for a second attempt after the first one didn't work.

looks like
Relaunching the same product.
find it in
The same product showing up twice across launch sites.
opening line

second launch of {their product}? what's different this time is the part people want to hear.

1 open
playbooks for it

Once a week, find the one step that is leaking.

Count five numbers from reach to payment. The weakest step is your constraint, and next week's only change goes there. Everything else stays the same so you can tell what worked.

5 · measure what paid
One week, one playbookexample numbers
reached31messages sent
replied929%
visited12clicked a link
signed up2count only
paid1$49/mo

Constraint: visited to signed up. 12 visited, 2 signed up.

The message worked; the landing page didn't. Next week: same people, same playbook, a landing page written for them. Nothing else changes.

how much to trust a number

under 10
Report the count only. "2 signups" is a fact; "17%" is noise.
10 to 29
A direction. Good enough to keep going, not to declare a winner.
30 and up
A rate you can quote, with a range around it.
about 100 per side
Before you call one version of a message better than another.

Ask every new customer “how did you hear about us?” and keep the answer next to your tracked links. Plenty of buyers read a thread on their phone and come back a week later; the link will not catch that, the question will.

123 single posts for your own accounts.

For the days a playbook calls for a post, or you just need one. Each card names what it is built to move. Your product details from step 1 fill in here too.

6 · post templates

123 of 123 posts

Launch day (Product Hunt and friends)

A sequence for one 24-hour ranking day. Product Hunt resets at 12:01am Pacific; the same arc works for Hacker News, Uneed or PeerPush.

Warmup, 3 to 5 days out
moves profile clicks3 open
shipnote goes live on {platform} on {day}.

it started because {specific moment you hit the problem}.

it does one thing: writes release notes from commits for solo founders who ship weekly.

if that's you, the notify link is in the reply.

why it works. One problem, one audience, one date. The origin line is what makes a stranger care before launch.

moves bookmarks2 open
before shipnote launches on {day}, here's what's in it and what isn't:

in: {thing}
in: {thing}
not yet: {thing}
not ever: {thing}

the 'not ever' line is the real positioning.

why it works. Saying what you refuse to build sharpens who it's for, and in/out lists get saved.

moves replies3 open
launching shipnote {day}.

one question before I do: when you {situation}, what do you open first?

I'm checking if my guess about {assumption} is right.

why it works. Turns the pre-launch post into research, and every reply is a warm contact for launch morning.

Go-live
moves signups2 open
shipnote is live on {platform}.

it writes release notes from commits for solo founders who ship weekly, without writing the changelog by hand every friday.

{n} months, built alone after work.

link in the reply. feedback in the comments there helps more than anything.

why it works. Clear value line first, story second. The ask is for comments, which rank better than silent upvotes.

moves profile clicks5 open
today's the day for shipnote.

the shortest version of why:
I was {doing task} every {frequency} and it took {time}.
now it takes {new time}.

it's on {platform} until midnight PT. link below.

why it works. Before and after in time units does the selling. The deadline is real, so it isn't manufactured urgency.

Mid-day
moves replies3 open
{n} hours into launch day.

the comment I didn't expect: {real comment, paraphrased}

it made me rethink {feature or assumption}. anyone else read it that way?

why it works. Real-time surprise gives the second post of the day a new reason to exist.

moves bookmarks4 open
the question I've answered most today: how is shipnote different from {category tool}?

{difference 1}
{difference 2}
{difference 3}

the third one is why I built it.

why it works. Answers the comparison everyone is silently making, and becomes a reusable positioning post.

The ask
moves signups2 open
I don't ask for much here.

today I'm asking for one thing: if anything I've posted about {topic} has been useful, a look at shipnote on {platform} would mean a lot.

link in the reply. thank you either way.

why it works. Spends earned goodwill once, explicitly. Works only if you rarely ask, so use it one time.

moves replies1 open
two ways to help shipnote today, pick whichever is easier:

1. a comment on the {platform} page saying what you'd use it for
2. a reply here telling me what's missing

both go straight into the roadmap.

why it works. Low-effort options raise participation, and both produce something you can use.

Results
moves bookmarks5 open
shipnote finished #{rank} on {platform}.

visits: {n}
signups: {n}
paid: {n}

what drove the signups: {channel}
what I'd skip next time: {thing}

full breakdown in the reply.

why it works. Funnel numbers from a launch are rare. Founders save these for their own launch.

moves replies3 open
one week after launch day:

still using it: {n} of {n}
best feedback: {paraphrase}
biggest bug: {bug}

launch day was {n} signups. the week after decided whether it worked.

why it works. Retention after the spike is the honest number, and the last line invites founders to compare.

Product launch

The weeks around a launch, from the first hint to the 30-day readout.

Pre-launch
moves replies2 open
building something for solo founders who ship weekly who {situation}.

not showing it yet. one question first:

what's the most annoying part of {task} for you right now?

why it works. A pre-launch question that collects the exact words your landing page should use.

moves signups6 open
{n} days until shipnote.

problem {k} of {total} it fixes: {specific pain}.

last {timeframe} that cost me {real cost}.

waitlist in the reply.

why it works. A countdown where each day names one concrete pain. Each post is a different reason to join.

moves replies1 open
would you pay $19 a month/mo for something that {core outcome}?

not selling yet. trying to price it before I build the billing page, and I'd rather hear 'no' now.

why it works. Pricing questions get honest answers when the stakes are clearly low.

Launch day
moves signups2 open
shipnote is out.

what: {one line}
for: solo founders who ship weekly
why now: {reason}
price: $19 a month

link in the reply. tell me what breaks.

why it works. The what/for/why/price grid answers every question a buyer has in four lines.

moves profile clicks3 open
I needed shipnote {timeframe} ago and couldn't find it.

so I built it. it's live today.

if you {specific activity}, it should save you {measured time}. if it doesn't, tell me.

why it works. The founder-as-first-customer story, with a promise you can check.

Feature drops
moves signups4 open
new in shipnote: {feature}.

before: {old workflow in one line}
after: {new workflow in one line}

asked for by {n} users. live now for everyone.

why it works. Before/after shows the value without explaining it. The request count shows you listen.

moves bookmarks3 open
{feature} shipped today. how to use it in 30 seconds:

1. {step}
2. {step}
3. {result}

most people will miss step 2.

why it works. A tiny tutorial with a reason to read carefully. Gets saved by users and seen by prospects.

Social proof
moves profile clicks3 open
a user sent this today:

"{their words, with permission}"

they're a {role} using it for {use case}. I didn't build it for that. I'm glad they found it.

why it works. Unexpected use cases are more convincing than the one you planned.

moves signups5 open
{n} signups in the first {hours} hours.

{x} came from {channel}, which I almost didn't post in.

the lesson for anyone launching: {lesson}.

why it works. Velocity plus attribution. The lesson is what makes non-customers share it.

Follow-up
moves bookmarks2 open
30 days after launching shipnote:

signups: {n}
paying: {n}
churned: {n}
most used: {feature}
never used: {feature}

next month I'm cutting {feature}.

why it works. A public cut is a stronger signal than a public add, and it shows you read the data.

moves replies1 open
launch month, what I expected vs what happened:

expected: {thing}
got: {thing}

expected: {thing}
got: {thing}

the gap I'm working on first: {thing}.

why it works. Expected/actual pairs are relatable to anyone who has launched.

Build in public

Updates from inside the work. The good ones carry a number and a lesson; the best ones carry a bad number.

Milestones
moves bookmarks4 open
{milestone} today.

{timeframe} ago it was {starting number}.

what changed between then and now, honestly: {one specific thing}.

everything else I tried barely moved it.

why it works. Specific start, specific end, one cause. Credit concentrated on one lever is what people save.

moves replies3 open
first paying customer for shipnote.

they found it through {channel}.
they paid because {reason they gave}.
I almost {thing you nearly did instead}.

what was your first customer's reason?

why it works. The first-customer story is always read. The closing question invites others to share theirs.

Four rules hold for every play.

7 · the four rules and the words
You send the first message. To a stranger, always a human-sent message. Templates draft it; you press send.
Real numbers only. If you don't have the figure, delete the line. Don't round up.
Links go in the first reply. On X, posts with a link in the body tend to reach fewer people.
One follow-up, then stop. No reply after one nudge means not now. Respect it.

plain definitions

Play
Also called a playbook. One repeatable way to reach one kind of buyer, like answering their questions on Reddit or emailing trials that stalled.
Next moves
Also called a sequence or cadence. The messages inside a play, in order, with the day each one goes out and when to stop.
Moment
A situation that makes someone ready to buy, like a launch that flopped or a tool they pay for and dislike. Also called a trigger event.
Signal
One sighting of one real person in a moment: a post, a listing, a review. Also called an intent signal.
Campaign
One group of people, one play, one offer, and an end date. You run one at a time per group.
Activation
The first action in your product that predicts someone will pay. You decide what it is.
Constraint
Also called the bottleneck. The weakest step between reaching someone and getting paid. Fix that one first.
Kill rule
Also called kill criteria. The result that tells you to stop a play and try another, decided before you start.
Tracked link
A link that records which message it came from, so a payment can be traced to the conversation that caused it.

want this run for you? vibedraft finds the people ready to buy on X and in your own signups, drafts the right move in your voice, keeps your channels posting and learns what pays. you approve everything that goes out.

Start here

Kill rules and timings are starting points, not laws; adjust them to your numbers. Example funnel figures are illustrative and marked as such. Launch directories and revenue boards named in the buying moments are public; check each one's terms before collecting from it.

Runs in your browser. Nothing you type here is sent anywhere.