Every way to get a customer.
Twelve channels. Every play under each one, with the number that tells you whether it is working. All of it free, no signup.
Landing Page & Conversion
Clarity beats creativity 10:1.
Your landing page is a measurement tool, not a marketing site. Build the cheap version, put one sentence your customers actually said at the top, and wire the analytics before you send a single visitor.
Pick the builder
Match the tool to what you are trying to learn. Founders who pick on looks lose two weeks to a CMS they never needed.
The decision rule
What you are testing decides the tool. Not the other way round.
Name the one thing you are testing before you open any tool
If you cannot say the hypothesis in one sentence, a page will not help you. You will decorate instead of learn.
Write the hypothesis in a single sentence, then pick the tool
Treat the page as a measurement tool, not a marketing site
The throwaway test page
The fastest way to find out whether anyone wants this. Built to be discarded.
References: Pretotyping (Alberto Savoia)
Ship a one-page test in under an hour
This is the Fake Door Test from Pretotyping. One job: measure whether the people you are building for will click.
- Up in under an hour, near-zero cost
Pick Carrd for the first version, every time
A founder replaced a $8k seven-page site with a 90-minute Carrd page
Let a technical buyer poke at the real thing
Engineers believe a running prototype and discount a screenshot. Pick this when your buyer writes code.
Ship an interactive prototype instead of a static page
The site that carries real traffic
Move up in fidelity only once the message works
Higher fidelity earns its keep when you are supporting paid traffic, not while you are still guessing at the headline.
Rebuild in Framer when you need a real site behind paid traffic
Let signal pay for pretty, not the other way round
Move up when the CMS need is real, not anticipated
A blog, a directory or dozens of programmatic pages justify it. For most founders before product-market fit, this is overkill.
Wait for a blog, a directory or programmatic pages before you move
Pay someone to build the second version
Your time is better spent on the message than on learning a builder you will use once.
References: Webflow Experts
Hire from Upwork, Fiverr or Webflow Experts for the rebuild
The per-campaign page
One page per ad campaign, so the variant test can actually settle.
Tools: Unbounce
Run a different page per paid campaign
Worth it only when you already have paid-search infrastructure and enough traffic to read a variant test.
Split a page per campaign once paid volume can settle the test
Write the hero
Three seconds to answer what this is, who it is for, and what changes for me. Words from customer calls beat words written alone at a desk.
Customer interview language
Their words, not yours.
References: The Mom Test (Rob Fitzpatrick)
Take the headline straight out of a customer call
When three founders independently describe the problem the same way, that sentence is your headline. Stop writing and copy it down.
Pull the exact phrasing customers used, not your paraphrase of it
Three founders saying the same sentence is the signal to use it
A hero nobody can decode kills the test before it starts
The 5-second test
Strangers decide whether the hero works. You do not.
Show it to five strangers who match your buyer
Ask one question: what does this do, and who is it for? If four of five cannot answer in five seconds, the hero failed and you rewrite it.
- 4 out of 5 in under 5 seconds, or rewrite
Use five people who fit the buyer and have never seen the page
Ask what it does and who it is for, nothing else
Rewrite the hero on failure instead of explaining it
Copy references
Read the people who do this well before your second draft.
References: Marketing Examples (Harry Dry)CopyhackersLaws of UX
Study the references between draft one and draft two
Marketing Examples is the best free reference for landing-page clarity. Read it after you have written something bad, when the lessons will stick.
Read the Marketing Examples landing-page guide before rewriting
What goes on the page
One headline, one buyer, one thing to click. Everything else is decoration.
Above the fold
The part that has to work before anyone scrolls.
Ship exactly one thing to click
Email capture, demo request or buy. Pick one. Three choices above the fold is the same as none.
Put one call to action above the fold, not three
Name one buyer on the page
A named buyer sells. A category does not. "Series A SaaS founders running 5-15 person sales teams" beats "B2B" every time.
- One ICP, named, beats a category label
Write the specific buyer, not the category they sit in
Email capture
Add it when demand is the open question, not before.
Tools: Waitlist APIWaitlister.me
Wire a waitlist only when you are testing whether anyone wants it
Twenty minutes of setup. Referral milestones exist, but gamifying a waitlist before you know there is demand solves the wrong problem.
- 20 minutes to wire up
Wire the waitlist in 20 minutes and move on
Skip referral milestones until demand is proven
Pre-sale offer
The only demand signal that clears a credit card.
References: $1,400 in pre-sales, step by step
Ask for money before the thing is finished
An email address costs nothing to give. A pre-order is the first honest answer you will get about demand.
Run the pre-sale off the second version of the site
Rebuild it once you know more
By now you have learned things the first page could not have known. Redo the old work with the new answers, and add what the product now needs.
The second version
Same questions, better answers.
Run the landing-page work again with what you now know
The copy, the visuals and the structure all move once you have talked to real buyers. This is not a redesign, it is a rewrite with evidence.
Repeat the hero and CTA work against real customer language
Add the visuals and app designs the first version could not show
Graduate off the simple builder
Unbounce, LeadPages or Instapage run out of room once the site has real work to do.
Move to a responsive builder when the simple one stops keeping up
Real-world page patterns
Pages that already work, filterable by industry.
Tools: Landingfolio
Steal the structure from pages in your own industry
Filter by industry and component so you are copying a solved problem rather than a nice-looking one.
Filter the library by industry and component before copying anything
UX audit checklist
A written list beats your judgment at 11pm.
Work a checklist before you call the page done
Copy a UX audit template into your own workspace and walk it. The same list works again when you design the product.
Copy the audit template into your own workspace and follow it
Animations and mockups
You do not have to make them. You do have to direct them.
Tools: LottieFilesUpworkFiverr
Storyboard it yourself, then pay someone to build it
Direction is the part only you can do. Execution is cheap. Three Lottie animations cost $150 on Upwork.
- 3 Lottie animations for $150 on Upwork
Storyboard the animation before you brief anyone
Use Lottie so the animation stays light enough for the page
Design people trust
Design is the first proof of competence a visitor gets. If the product looks amateur, your expertise does not get a hearing.
Figma design system
Rules, so you stop re-deciding the same things.
Tools: Figma
Define the variables once and stop picking colors
Main colors, backgrounds, text styles, animation speeds. A global style guide becomes the source of truth for every tool that later generates your code.
Name your colors, backgrounds, text styles and animation speeds
Keep one global style guide as the source of truth
Use rules and spacing instead of pushing pixels around
Grid and layout
Compartments a visitor can scan without effort.
Tools: UizardBentogrids
Put every feature in its own compartment
Each section gets one focus: one call to action or one number. Two focuses means neither lands.
- 1 call to action or 1 data point per section
Give each section a single focus and cut the rest
Pattern libraries
See how companies with real budgets solved it first.
Copy flows that already work at scale
Stop guessing at a signup flow somebody else has already tested on millions of people. Use Dribbble for taste, never for usability.
Study the actual flows top companies ship, then copy the structure
Take looks from inspiration galleries and usability from nowhere else
Micro-interactions
Small rewards that make the page feel alive.
Audit the one button that matters
Hover shadows and smooth transitions tell a visitor the page is responding to them. Add something satisfying to the primary action and leave the rest alone.
Add one small animation that rewards the primary action
Hide the advanced features until they are wanted
Put power-user features behind a mode, or reveal them as someone clicks deeper. A first-time visitor should not meet your whole feature list.
Put advanced features behind a power-user mode
Human variance
Proof a person made this, not just a model.
Break the grid on purpose
Products designed by AI look too perfect. A hand-drawn element, a grain texture or asymmetric type reads as human.
Add one hand-drawn, textured or asymmetric element
AI asset generation
Original images instead of stock nobody believes.
Tools: MidjourneyPlayground AI
Generate the moodboard and the images yourself
Moodboard first so you know what you are aiming at, then generate the real assets. Generic stock photos undo the trust the rest of the design just built.
Generate a moodboard before you make any final asset
Make original images instead of using generic stock photos
UX law triage
Two laws that fix most signup flows.
References: Laws of UXRefactoring UI
Audit the signup flow against two laws
Hick's Law says cut the number of choices. Fitts's Law says make the buttons big and easy to reach. Most broken signup flows fail one of those two.
Cut the number of choices in the flow, per Hick's Law
Measure the page
A landing page with no analytics is decoration. You should know by Friday whether to kill it or spend more.
Behavioral analytics
Watch what people actually did, not what you hoped they did.
Install exactly one analytics tool
Clarity is free with heatmaps and session recordings. Hotjar is paid with deeper funnels. Two tools double the setup and rarely double the signal.
Pick one tool and skip the second
Get analytics live before your first paid click
Watch recordings of the new version
Session recordings show you where people get confused. Users are too polite to tell you, and heatmaps do not lie.
Watch recordings to find where the new page confuses people
Kill or keep thresholds
Decide what counts as working before you have feelings about the result.
Write the threshold down before you run traffic
Click-through at or above 5% in a neutral channel is a green light. Below 3% on cold paid traffic means the message is wrong, so rewrite the hero before you add budget.
- Click-through at or above 5% in a neutral channel is a green light
- Below 3% on cold paid traffic means the message is wrong
Treat 5% click-through in a neutral channel as the green light
Rewrite the hero below 3% instead of buying more traffic
Keep the threshold in the same doc as your hypothesis
Page speed
The metric that decides whether any other metric gets measured. The 2-second mobile target here is the landing page kill threshold. The full Core Web Vitals targets live in Analytics & Unit Economics.
Tools: PageSpeed InsightsGTmetrix
Hold mobile load under 2 seconds
Miss this and nothing else counts, because half your visitors leave before the page renders.
- Mobile load under 2 seconds is non-negotiable
Test mobile load on PageSpeed Insights before you send traffic
Find the specific images and scripts costing you the load time
Structured data
Thirty minutes that make the page legible to AI answers.
References: Google Rich Results Test
Add Organization and Product schema
Two structured-data blocks make your site readable to ChatGPT, Perplexity and Google AI Overviews. About 30 minutes of work.
- About 30 minutes of work
Ship an Organization block and a Product block
Validate both blocks on the Rich Results Test
Onboarding & Retention
If your retention curve hits zero, you don't have a business; you have a leaky bucket.
Get a new signup to a real result in seconds, then find the one action that predicts who stays. Measure what people do, not what they say on a survey.
Speed to the first win
Count the seconds between signup and the first real result. That number, not your signup count, is the one to drive down.
The signup-to-first-win clock
Time to value is the metric. Activation just means someone made an account.
Measure time to value, not signups
Most founders track activation, which only proves a form got submitted. Track the gap between signup and the first win instead.
- TTV under 30 seconds
Target under 30 seconds from signup to the first win
A signup tells you an account exists, not that anyone got anything out of it
Cut the load before anyone complains about it
Waiting for support tickets means you find the friction after it has already cost you the user.
Walk every screen a new user sees and strip what they do not need in that moment
Anticipate the confusion instead of waiting for someone to ask for help
The click path to the activation action
Count the clicks between a fresh account and the action that predicts retention.
Run a friction audit on the path to first value
Open a brand new account and count. If the number is above five, the fix is deletion, not a tooltip.
- under 5 clicks
Reach the activation action in under 5 clicks, or cut clicks until you can
Audit against the activation action you measured, not the feature you like most
The first minutes with the product
The first few minutes, hours and days set what the user believes about the whole product.
Guide the new user to a success instead of letting them explore
Exploration is what a user does when nobody told them where to go. It is not a feature.
Treat the first few minutes, hours, days and weeks as the thing that decides everything
Use the first run to show how the product solves the problem, not to list what it does
Know which number a better first run actually moves
Onboarding work pays in three separate places. Pick the one you are short on before you start rebuilding screens.
A smooth first run cuts confusion and frustration, and that is what raises retention
Guiding someone through setup raises trial-to-paid conversion
Familiarity with the features is what makes adoption faster, so teach them in order of use
Find the action that predicts retention
Before you build a tour, know where you are leading people. The destination is one countable action, and the data already knows what it is.
Stayers compared against churners
Two cohorts, one question: what did the survivors do in week one that the leavers did not?
Find the one first-day action your retained users share
One action, done inside 24 hours, shared by nearly all the people who are still here a month later.
- 80% of 30-day retained users
- first 24 hours
Find the single action 80% of your 30-day retained users did in their first 24 hours
Write it as a countable event like "imported first 10 leads", never as "engaged with the product"
Compare day-30 stayers against the people who left
The churners are the control group you already paid for. Use them.
Ask what the stayers did in their first 7 days that the churners did not
Candidates to check: sent their first email, connected a second integration, invited a teammate
Once you find the action, redesign onboarding to drive every new user to it
Competitor signup flows
Three competitors have already tested their first-run flow on more users than you have.
Tools: Whimsical
Sign up for three competitors and screenshot every step
Do it yourself, with your own email, so you feel the friction instead of reading about it.
- 3 competitors
Sign up for 3 competitors and screenshot every single step
Put all three flows on one board and list the stitches they missed
The question you ask at signup
One question, asked before the dashboard loads, that changes what the dashboard shows.
Tools: Typeform
Ask the one thing they want, then show only that path
A new user has one job in mind. Showing them the other nine paths is how you lose them.
References: The Mom Test
Ask "What is the ONE thing you want to achieve right now?" inside the flow
Branch the flow so the user only sees the path to the answer they gave
Put the survey between signup and the dashboard so the answers qualify the user first
Usage depth per user
Your happiest users are often the quietest ones. They are in the data, not the survey results.
Find the power users who never answer a survey
Some of your best users will never fill out a form and will still be in the product half the working day.
- 4 hours a day
Track depth of engagement per user, not just whether they logged in
Find the users sitting in the product 4 hours a day and reach out to them by name
Build the first-run flow
A first run that ends in a result the user can point at. Not a tour, not a checklist, not an empty screen.
References: HubSpot guide to customer onboardingHubSpot Academy
The guided first-run flow
The one flow every new account walks through, ending in something that looks like a win.
Build a flow that ends in a win inside 30 seconds
A generated report or an automated email counts as a win. A green checkmark does not.
- under 30 seconds
Build the guided flow so the user sees a win in under 30 seconds
Make the win a generated report or an automated email, something the product produced
Design a race to value, not a feature tour
A tour explains the product. A race to value proves it. Only one of those keeps people.
Stop treating a feature tour as onboarding
Remove every ounce of friction between the signup and the moment the user gets it
Audit the flow against a psychology framework
Someone has already taken apart the onboarding flows of the apps you admire, screen by screen. Read their teardown before you draw your own.
References: Growth.design case studiesThe Psychology of Waiting Lines
Work through the Blinkist onboarding teardown as the worked example
Empty states
The screen a user hits before they have put anything in. Most products waste it.
Never show a screen with no data on it
A blank table teaches a new user nothing except that the product is empty.
Seed AI-generated sample data or drafts so the finished product is visible on day one
How much of the product you show at once
Every advanced feature on screen in minute one is a feature taxing the user who needs one thing.
Hide the advanced surface until the first value cycle is done
Earn the right to show the power features. The user tells you when by finishing the basic loop.
- 50% cut in cognitive load
Gate advanced features behind one completed value cycle
Target a 50% cut in what a new user has to process on first run
Guide people inside the product
Put the help on the screen where the user is stuck. A help doc they never open is not guidance.
Tooltips and walkthroughs
Build the tooltips without writing code
Guidance changes weekly while you are learning. Putting it behind a deploy queue kills the iteration speed.
Use a no-code builder so a non-engineer can ship a tooltip the same day
Pick a deeply customizable onboarding tool when the product itself is complex
Trigger the prompt off behaviour instead of blasting one tour
The same message shown to everyone at signup is a tour with extra steps.
Fire the message at the moment it is useful, not at every new signup
Usage data paired with in-app messages
Read where people stall on the complex features, then message them on that screen.
Guide people through the feature they keep abandoning
Complex features are where usage data and in-app messaging pay for themselves together.
Combine product usage analytics with in-app messaging on your most complex features
Nudges for a user frozen on a step
A user who has not moved in two minutes is not thinking. They are stuck.
Tools: IntercomHelp Scout
Message anyone who freezes on a setup step
Set the timer once and it catches every stuck user from then on, without anyone watching a dashboard.
- more than 2 minutes on one setup step
Fire an automated message when a user sits on one setup step for more than 2 minutes
Automate the nudge so it fires on its own, not when someone happens to notice
Emails triggered by what users do
Send off an event in the product, not off a calendar. Which platform you send from, and how healthy your list is, live in Email & Newsletter.
Onboarding email fired by a product event
The email arrives because the user did something, or pointedly did not.
Tools: Customer.io
Trigger the onboarding emails off real product events
A fixed five-day drip sends the same day-three email to someone who finished setup on day one.
Send when the user does a specific action, or skips it, rather than on a fixed schedule
Check whether your sending platform runs a startup program
The welcome email
The one email every single signup opens. Most founders waste it listing features.
Point the welcome email at one action
Email is still one of the best activation tools you have. Spend it on the action that predicts retention.
References: Welcome email examples
Treat email as an activation tool, not an announcement channel
Copy the structure from a roundup of welcome emails that already work
Transactional email
Receipts, password resets and alerts. Different consent rules from anything marketing sends.
Keep transactional and marketing sends apart
Mixing them is how a receipt ends up governed by marketing consent rules, or the other way round.
References: Marketing email vs transactional email
Read what separates marketing from transactional email before you mix the two
Consolidate into the platform you already run instead of bringing in a second vendor
Platform choice and list health live in Email & Newsletter
Support that teaches the product
Treat support as part of the first-run experience, so a new user feels held from the first click.
In-app chat
An answer on the screen where the question came up, while the user is still there.
Run chat on the screens where people get stuck
A user who has to leave the product to find an answer often does not come back to it.
Get on the Early Stage program while you still qualify as one
Pair automated support with the live chat so the repeat questions answer themselves
Knowledge base and support inbox
One place for the articles and one place for the replies, run by the same person.
Run the knowledge base and the support email from one place
A cleaner help desk beats a complete one while a founder is still answering the tickets.
Pick the human-centric help desk over the complex one while the team is small
When to move to a support suite
Enterprise-grade support software is a real answer to a problem you do not have yet.
Skip the enterprise support suites early
The suite is built for a support team with a manager. You are one founder with a laptop.
Treat the enterprise suites as overkill until the team is genuinely big
Stay on the lighter help desk until the size of the team forces the move
Measure whether people stay
Two ways to measure fit, and only one of them is honest. Ask the survey, then check it against what people actually did.
The Very Disappointed survey
One question, four options, one threshold that tells you whether to keep scaling.
References: The Superhuman PMF Engine (First Round Review)
Run the survey against 100 or more real users
The Sean Ellis 40% rule is still the standard answer to "do I have product-market fit?"
- 100+ existing users
- 40%+ "very disappointed"
Ask "How would you feel if you could no longer use [Product]?"
Send it to 100 or more existing users
Use the four options: very disappointed, somewhat disappointed, not disappointed, N/A
Below 40% "very disappointed" you do not have PMF, so stop scaling acquisition until you do
Run the survey as a loop, not a one-off
Superhuman turned the one-question survey into a cycle they ran again and again. That write-up is the playbook.
Follow the Superhuman write-up as the canonical playbook for using the survey
Halve whatever the survey tells you
People overclaim on surveys. Some want to be encouraging, some want a discount, and the number comes back inflated either way.
- multiply by 0.5
Multiply whatever the survey number is by 0.5 to get reality
Expect users to overclaim, because they want to encourage you or want a discount
What users actually do
Four behaviours past the novelty stage tell you more than any survey response.
Watch the four signals that do not flatter you
Day 7, day 30, the teammate invite and the unprompted upgrade. Count them past the novelty stage.
Check whether they came back on day 7 and on day 30
Check whether they invited a teammate and whether they upgraded without being asked
Only count behaviour from after the novelty stage has worn off
Measure both, then trust behaviour
Sentiment is worth collecting. It is not worth betting the roadmap on.
Measure sentiment and behaviour side by side, and trust behaviour when they disagree
Expect polite lies, because nobody wants to disappoint a founder they like
Cohort survival
Your first 50 users, 30 days later. The count is the whole answer.
Run the Cohort 0 audit
One number, pulled in an afternoon, that decides whether you scale or pivot.
- first 50 users
- below 20% active at 30 days
Pull your first 50 users and count how many are still active 30 days after signup
Below 20% still active at 30 days is a retention problem, so pivot before you scale
Refuse to grade yourself on a rigged cohort
A founder once showed off a beautiful retention chart built on 12 people from his investor's network, all on free plans.
- 12 people, hand-picked, all free
- 40 strangers
A 12-person cohort hand-picked from an investor network, all using it free, is not PMF
Ask whether 40 strangers would be very disappointed if you took this away tomorrow
Stop treating PMF as a vibes check on a dashboard you like the look of
Find the benchmark for your category before you judge your curve
A 25% month-3 curve is a disaster in one category and normal in another. Look it up before you panic.
References: Lenny's NewsletterReforge: Retention + Engagement
Search a retention benchmark archive for your category before you call your curve bad
Spotting your advocates in the usage data
If you cannot name your ten biggest fans from the data, you do not know who they are.
Name your top 10 advocates from usage alone
This is the input list for every referral, case study and testimonial ask you will make later.
- 10 users
Identify the 10 users most likely to refer a friend, using usage data alone
If you cannot produce that list, you do not yet know who your real fans are
Stop churn and grow the accounts you have
Retention leaks quietly. Catch the account while the user is still logging in, and build the upgrade moments into the workflow rather than on top of it.
Account health alerts
An alert that fires on silence, before the renewal date does the telling.
Alert on 3 days of silence from a high-value account
The email costs nothing to send. The churn it prevents costs hundreds to thousands of dollars.
- no login for 3 days
- hundreds-to-thousands of dollars
Trigger an alert when any high-value account goes 3 days without a login
Send a personalized "hey, anything we can fix?" email off that alert
Run it from your own script if you do not want another platform yet
Score account health once you cannot watch by hand
Manual watching works up to a point. Account-health scoring is what replaces you after it.
Move to account-health scoring with automated churn alerts when the account list outgrows you
Add advanced churn management only when the team is scaling past mid-market
The roadmap gate
The fastest way to lose product-market fit is to ship something that breaks the activation flow.
Gate the roadmap on the activation flow
Every new feature has to answer one question first: does it lengthen the path to first value?
Do not add complexity that breaks the activation flow
Once retention is positive, protect it before you chase anything new
Stop buying users you cannot keep
Acquisition spend against a curve that hits zero buys you a bigger number this month and nothing next month.
A retention curve that hits zero means you have a leaky bucket, not a business
Expansion moments inside the workflow
Three points in the product where more value is the obvious next thing to offer.
Bake the upgrade moments in instead of bolting them on
A prompt inside the workflow reads as help. The same prompt glued on top reads as a sales popup.
- three concrete moments
At the usage limit, show a gentle upgrade prompt
When a workflow completes, suggest the next workflow
Bake these three moments in. Do not bolt them on afterwards.
Retention compounds when users naturally adopt more of the product
Bring dormant users back
A lead who went quiet is dormant, not dead. Wait for them to show intent, then send one useful thing.
Return signals from dormant users
The moment a quiet user reappears on a pricing page is the moment worth spending a message on.
Set an alert for a dormant user coming back
Someone who has been gone two months and lands on your pricing page has told you something.
- 60+ days with no login
Alert when a user with 60 or more days of no logins comes back
Fire on a visit to the Scale pricing tier or a "How to Migrate" blog post
Fire when a dormant contact opens a 6-month-old email
The plain-text win-back email
Twenty words that name the thing they just looked at. No template, no campaign design.
Send a value bridge, not a check-in
Reference the specific thing they just did, name what shipped that fixes it, and ask for five minutes.
- 5-min Loom
Name the exact feature they were looking at again
Lead with the thing you just launched that handles their pain point
Offer a 5-minute Loom instead of asking for a meeting
Keep the draft near 20 words and make it reference their specific past usage
Ban the check-in email
Audit every template you own. "Just checking in" asks the reader to do the work of caring.
References: Copywriting Course
Delete any template containing "just checking in" or "circling back"
Replace it with "I have a new [ValueAsset] for you", so every touch carries something new
Send the nine-word question
The shortest re-engagement email that works, because answering it costs the reader almost nothing.
References: The 9-Word Email (Dean Jackson)
Send "Are you still looking for [Solution]?" to your old leads
It re-activates leads by cutting the friction of replying, not by improving the pitch
Win-back link and inbox checks
A second chance you get once. Do not spend it on a dead link or a rewritten subject line.
Tools: GlockApps
Audit every win-back link before you resend
A win-back that lands on a feature you retired in 2021 burns the one chance you had.
Point every win-back link at a current landing page, not a dead 2021 feature
Audit the win-back send so it reaches the primary inbox, not the promotions folder
Purging non-openers and protecting domain health live in Email & Newsletter
Check the benchmark before you rewrite the copy
Re-engagement open rates are low everywhere. Compare against the category average before you blame the words.
References: Email marketing benchmarks
Look up the industry average open and click rates for re-engagement campaigns first
The newsletter as long-tail nurture
When one-to-one has failed three times, move them somewhere you still own the connection.
Move unresponsive leads into the newsletter automatically
Set the rule once so nobody has to decide, one lead at a time, when to give up.
- 3 failed re-engagement attempts
Move the lead to the newsletter segment after 3 failed one-to-one attempts
Send them to a distribution channel you own rather than letting them go quiet
Score newsletter clicks and hand the hot ones to a human
An old lead clicking your links every week is a warm lead nobody has called.
Score which old leads are clicking links in your newsletter
When the newsletter lead score crosses your threshold, trigger a human-led intro
Analytics & Unit Economics
Scaling is only allowed when your unit economics are green.
Prove a customer is worth more than they cost, and that your data can prove it. Four numbers decide whether growth is real. The stack under them decides whether you can see the numbers at all.
Know what a customer costs and what they pay back
If you cannot explain the economics on the back of a napkin, you do not understand the business yet. Four numbers: fully-loaded CAC, LTV:CAC, payback period, net revenue retention.
Working out what a customer costs to buy
Three numbers, tracked weekly. Start with the one most founders calculate wrong.
Count the salaries in your CAC, not just the ad spend
Leaving salaries out is the step most founders skip, and it is why the CAC number looks fine until someone opens the P&L.
Divide sales spend, marketing spend and sales and marketing salaries by new customers
Skipping salaries is why CAC looks great right up until you read the P&L
Get the cash back inside 6 months B2B, 12 months B2C
Payback is the number that decides whether you can afford to buy the next customer before the last one has paid for themselves.
- < 6 months (B2B)
- < 12 months (B2C)
Recover CAC in under 6 months for B2B, under 12 months for B2C
Miss that window and you are not ready to scale paid acquisition
Payback over 12 months breaks cash flow during the scaling spend
Working out what a customer is worth
One ratio tells you whether to scale. One retention number tells you whether the business grows without new logos.
Hold the 3 to 1 floor before you scale anything
Below 3 to 1 the problem is the product or the price, not the funnel. Spending more on the funnel just buys the same bad trade faster.
- LTV / CAC
- 3:1 to scale
Divide LTV by CAC and require at least 3 to 1 before you scale
Below 3 to 1, fix the product or the pricing before you touch the funnel
Spending $2 to make $1 is not a business yet, it is a runway problem
Make net revenue retention the headline number
Track cohort revenue month over month. Expansion grows you without a single new logo, which is the cleanest signal you have a real business.
- 125%+ for SaaS
- 100 customers grow into the revenue of 125 in 12 months
Track cohort revenue month over month and aim for 125% or better in SaaS
100 customers today should grow into the revenue of 125 customers in 12 months with no new logos
Above 100% NRR your existing customers grow revenue on their own
Deciding whether you are allowed to scale
Scaling magnifies whatever is already true. Check the gates before you turn the dial up.
Clear three gates or fix the one that fails
Three numbers decide readiness. Topline growth is not one of them, and reading it as one is how founders scale into an 18-month cleanup.
Gate 1: LTV:CAC at 3 to 1 or better
Gate 2: revenue per employee at $300k or more, because below $200k you are scaling people, not margin
Gate 3: annual churn under 10% B2B or under 25% consumer
Do not pass the gate on topline growth alone
One company raised a Series B, tripled headcount in 9 months, watched growth stay flat, and spent 18 months unwinding it
Check the Rule of 40 before you raise a growth round
Investors read this one before they read your deck. Below 30 the terms get ugly.
- Growth Rate % + Profit Margin % > 40
- below 30 struggles to raise
Add growth rate percent to profit margin percent and clear 40
Below 30 you will struggle to raise a growth round at decent terms
Track revenue per employee every quarter
If revenue per employee flattens while headcount climbs, you are scaling cost faster than value. Stop hiring until the trend turns.
Stop hiring while revenue per employee is flat or falling as headcount grows
Explain the economics on the back of a napkin
The demo does not matter here. If the numbers only work inside a 40-tab model, you cannot defend them to an investor or to yourself.
If you cannot explain your unit economics on a napkin, you do not understand the business
Scaling with LTV:CAC below 3 to 1 accelerates you toward a wall
Know how long your cash lasts and what it buys
Two metrics tell you whether you are building something durable: how much you burn per dollar of new ARR, and how many months of cash sit behind you.
What each burned dollar buys you
Stop staring at the bank balance. Read burn velocity instead.
References: David Skok: SaaS Metrics 2.0SaaS Capital benchmarks
Calculate burn multiple every month
Net burn over net new ARR. David Sacks coined it, and it is the single most useful efficiency number in SaaS.
- Target < 1.0
- < 1 amazing, 1-1.5 great, 1.5-2 OK, > 2 suspect, > 3 bad
Divide total cash spent minus revenue by new ARR added in the same period
Under 1 is amazing, 1 to 1.5 great, 1.5 to 2 OK, over 2 suspect, over 3 bad
Under 1.0 means you spend less than $1 to make $1 of new ARR
Stay under 1.5 to be a fundable scale-stage company
Check yourself against outside benchmark data
Your burn multiple means nothing on its own. Compare it against the industry data before you decide it is fine.
References: The Cold Start Problem (Andrew Chen)
Read SaaS Metrics 2.0 before you set your first KPI
Check the annual SaaS Capital data on growth, retention and burn multiples across the industry
Protecting the months you have left
When the market turns, months of cash is the only number that matters.
Hold 18 to 24 months of cash at all times
Below 12 months you are in the red zone, and the cuts happen that week.
- 18-24 month runway minimum
- below 12 months is the red zone
Below 12 months, cut every non-revenue-generating fixed cost the same week
Do not wait for the board meeting to make the cut
Cancel the software nobody has opened in 60 days
This is not austerity. It is the legacy seats that quietly compound while nobody reads the invoice.
- unused for 60 days
- 5-10% of burn
Pull every recurring SaaS line item from the last 12 months of invoices
Point a quick AI agent at those 12 months of invoices to surface every charge
Bloated legacy seats quietly compound to 5 to 10% of burn
Write the Default Alive plan before you need it
The cuts you would make if the next round disappears. Written down, not assumed.
- break-even within 90 days
Document the exact cuts that reach break-even within 90 days if the next round disappears
Writing the plan down is what makes it real
Modeling the runway
A living model that moves when hiring and pricing move. Not a spreadsheet somebody last opened in March.
Build a bottom-up model that freezes hiring on its own
Tie hiring to revenue milestones inside the model. Miss the revenue target and hiring stops without a debate.
Tie hiring directly to revenue milestones so a missed target freezes hiring automatically
Cut the discretionary "we will figure it out" out of the plan
Model the decision before you make it
A price increase and a hiring freeze both move runway. See how far, in real time, before you commit to either.
Watch how a price increase or a hiring freeze moves runway before you decide
Pull Stripe, HR and CRM into one view instead of three exports
Idle cash sitting in the bank
Money you raised should not sit at zero yield while you burn it.
Tools: Arc Treasury
Sweep idle cash into a high-yield account
Automatic, boring, and it pays for a chunk of the burn you were going to eat anyway.
Move idle venture cash into high-yield, FDIC-insured treasury accounts automatically
Do not let dead cash subsidise your burn at zero yield
Buy the analytics stack your stage actually needs
Most founders pick a stack that is too light or too heavy. Both fail the same way: you redo the foundation at the worst possible moment.
The stack before product-market fit
One product analytics tool, your payment dashboard, and search data. That is the whole stack.
Tools: PostHogGoogle Search Console
Run the whole thing on free tiers under $10k MRR
PostHog covers product analytics, session recording, feature flags and heatmaps in one tool. Skip everything else until a question forces your hand.
- under $10k MRR
- about 95% of what you need
Under $10k MRR run the PostHog free tier, the Stripe dashboard and Google Search Console
Skip the CDP, skip the warehouse, skip Mixpanel at this stage
One free tool covers about 95% of what you need pre-PMF
Session recordings and heatmaps for the page itself live with the landing page work
Instrument 8 events and read the churn driver off one chart
A B2B SaaS at $200k ARR was running on Google Analytics, Stripe exports and a hand-maintained spreadsheet, and could not answer a basic retention question.
- 8 events
- 3x churn on Starter vs Pro
- 2-day fix
- about $30k of ARR
A spreadsheet cannot tell you day-30 retention by plan or which feature predicts an upgrade
Starter-plan users churned at 3 times the rate of Pro, and the cause was a feature gate on day 14
The fix took 2 days and added about $30k of ARR over the next quarter
Adding a customer data platform
A CDP earns its keep when you are sending the same events to three or more places.
Tools: SegmentRudderStack
Add a CDP only when you have 3 or more destinations
Analytics, email, ad pixels and the warehouse is four destinations. Two is not, and the middle layer is pure cost until then.
- $10k-$100k MRR
- 3+ destinations
Between $10k and $100k MRR with multiple destinations, add the CDP
Below three destinations, instrument straight into PostHog or Mixpanel and skip the middle layer
Pick the open-source option when you need the data to stay on your own infrastructure
Adding behavioral analytics and a warehouse
The layer you buy at $100k+ MRR, once the question spans more than one source.
Pick the behavioral tool by the question you keep asking
Funnels and cohorts pull one way. High-frequency usage analysis pulls another.
Mixpanel for funnels and cohort retention, Amplitude for high-frequency usage analysis
Use auto-capture to analyse retroactively when the product went years under-instrumented
Buy a warehouse only to join product events with Stripe and CRM data
A warehouse with nothing to join is a bill. Wait for the cross-source question.
Add the warehouse when you need to join product events with Stripe and CRM data
Snowflake, BigQuery, or a Postgres-backed option when those are more than you need
Reviewing the stack before you add to it
The tier-up trigger is a question, not a revenue number and not a competitor screenshot.
Name the question your current stack cannot answer
Tier up when you can name it. If you cannot name it, you are shopping, and the new tool will sit unopened next to the old one.
Tier up only when you can name the specific question your stack cannot answer
Watch for both failure modes, not just the light one
Snowflake, dbt and Looker before $100k ARR fails exactly like a spreadsheet does. You find out when you need a real decision.
Both the too-light and too-heavy stack force a redo, and the redo always lands at the worst moment
Do not buy Snowflake, dbt and Looker before $100k ARR
Adding in-product guidance
Tooltips, checklists and empty-state guides you can ship without an engineering ticket.
Buy the guidance layer when the tickets are the bottleneck
Pick the full suite if you want analytics with it, the lighter tool if you want tooltips live this week.
Add tooltips, checklists and empty-state guides without an engineering ticket
Take the lighter-weight tool when you want faster setup instead of a full suite
Instrument once, and instrument it properly
Bad instrumentation is worse than none. You make decisions on data that quietly contradicts itself, and you never find out. The discipline sits upstream of the tool.
The shared spec for your events
Event name, properties, naming convention, when it fires. Agreed before anyone writes the code.
Write the tracking plan before you ship tracking code
Two engineers naming the same event differently breaks your data at the source, and no analytics tool fixes it downstream.
If Login and Sign_In both exist, your data is broken at the source
Spec the event name, the properties, the naming convention and when it fires
Pick one home for the plan, then enforce it in review
Track 10 to 15 events, not 200
Under $100k MRR you do not need granular tracking. You need the handful of events that map to revenue and retention.
- 10-15 events, not 200
Cover signup, the activation moment, key feature use, paid conversion, upgrade, downgrade, cancel-flow start and session start
Stop tracking every button click, because the noise buries the signal
Server-side event collection
Cookieless attribution is the default now. The browser alone no longer sees your revenue.
Send revenue events from your server as well as the browser
Client-side tracking alone loses a third to half of your data. Wire the server side once, at the start.
- 30-50% data loss client-side
Client-side tracking alone loses 30 to 50% of data to iOS Safari, ad blockers and tracking prevention
Wire Meta's CAPI and Google's GA4 Measurement Protocol for revenue events specifically
Do it once at the start, because retrofitting after a year of client-only data is painful
Set attribution up before you ramp spend, not after
As cookies disappear, server-to-server tracking is the only way left to prove where a paid customer came from.
Fire server-side Stripe events so the affiliate stack pays out on real revenue
The weekly growth dashboard
Three numbers, one screen, every week. Anything more and nobody opens it.
Tools: June.soGrowthHackers
Put NRR, LTV:CAC and payback on one screen
If you cannot see all three at once, you are guessing at growth rather than measuring it.
If the three numbers are not on one screen, you are guessing
Use out-of-the-box product analytics for NRR, retention cohorts and growth loops instead of building the view yourself
Make the site fast and make the errors visible
Half your visitors leave before a slow page renders. Most of your bugs go unreported without error monitoring. Both systems are cheap and pay for themselves every quarter.
Loading speed on real traffic
Google publishes the thresholds and validates them against real user data. Test against those, not a local build.
Tools: PageSpeed Insights
References: web.dev: Core Web Vitals
Hit the four Core Web Vitals thresholds in production
LCP, INP, CLS and TTFB. Any threshold you blow makes everything downstream worse: SEO, conversion, retention.
- LCP <2.5s
- INP <200ms
- CLS <0.1
- TTFB <200ms
LCP under 2.5s, INP under 200ms, CLS under 0.1, TTFB under 200ms
Test against real user data in production, not a local dev build
Any threshold you blow makes SEO, conversion and retention worse
Half your visitors leave before the page renders when mobile load time is bad
Error monitoring in production
Turn error monitoring on from day 1
By the time a customer reports the bug, the retention damage is already done. The free tier covers early-stage volume.
- about 70% of production bugs invisible without it
About 70% of production bugs stay invisible until a customer complains
Pick one: client and server error tracking, or error tracking paired with replay of the crash
Get monitoring on before you send any meaningful traffic
The hosting stack under all of it
Pick one modern combination and stop shopping. The comparison spreadsheet is not the work.
Tools: VercelSupabaseCloudflare
Pick one modern stack and leave it alone
Frontend and edge functions on one side, Postgres with auth and storage on the other.
Vercel plus Supabase is the default for most early-stage SaaS
Take serverless Postgres on its own when the full platform is more than you need
Add a CDN and edge functions when you need global low latency
The quarterly architecture review
One recurring calendar entry that catches the things nobody notices until they break.
References: SaaS Startup CTO Checklist
Run your architecture against the CTO checklist every quarter
Security, scalability, observability and operational readiness, on a free and well-maintained reference.
Test a real restore, because "we have backups" is not the check
Review secrets management, dependency vulnerabilities, uptime targets and on-call response
Turn channels on in the right order
Get the math working at small scale, then the channels that borrow trust, then the ones you pay for. Skipping ahead is the most expensive mistake on this page.
References: Reforge: Growth LoopsDemand CurveLenny's Newsletter
The order you switch channels on
Three steps, and the order is the whole point.
Get the math working at small scale before you turn anything on
Ramping spend before retention is fixed pays to fill a bucket that leaks faster the bigger it gets.
Ad spend before retention is fixed fills a bucket that leaks faster as you scale
Fix the math first, turn on partner channels second, scale paid third
One Series A company put $1M into Meta ads at 15% monthly churn, loved the topline for 4 months, then laid off half the company
Revenue retention is the one metric that decides whether the growth is real
Start with the channel that borrows someone else's trust
Partner channels are cheap and arrive pre-trusted. Paid is fast and expensive. Run them in that order.
Partner channels are cheap and come with trust attached, paid is fast and expensive
Once the gates are open, partners are still the cheapest way to grow
Paid amplifies what is already there, including the broken parts
Knowing when a channel is topping out
Every channel has an S-curve. Read the shape so you can tell a plateau from a bad week.
References: Reforge: Scaling Series
Move to the next channel when the current one flattens
The framework for the S-curve exists. Learn it before you double the budget on a channel that is done.
Learn the S-curve so you can time the move from one channel to the next
Pair the speed mindset with margin discipline
Read the blitzscaling argument for the speed, then hold it against your own margins.
References: Blitzscaling (Reid Hoffman)
Growth at any cost is no longer the meta
Automate the outcome, not the busywork
The 2026 advantage is not the old playbook with AI sprinkled on top. It is a workflow where the agent owns the outcome end to end and a human steps in only when the outcome is wrong.
Recurring work an agent can own
Start with frequency. The tasks somebody repeats three times a week are the ones worth rebuilding.
Audit every task somebody does more than 3 times a week
Any function, not just engineering. Rank by frequency and take the top five.
- more than 3x per week
- the 5 highest-frequency manual tasks
List anything done more than 3 times a week in any function, then pick the 5 highest-frequency manual tasks
Name the outcome each task produces: a sent invoice, a qualified lead, a resolved ticket
Build the agent to own the outcome end to end
An agent that helps a human do the same steps is an assistant. You wanted the outcome produced without you.
Build for the outcome end to end, not to assist a human doing the same steps
Humans step in only when the outcome is wrong
Hire the operator who runs a fleet of agents
The most valuable 2026 hire architects, monitors and improves a fleet of agents. Hire or promote for that skill by name.
Hire the operator who architects and monitors agents, not another individual contributor
Ask: walk me through a workflow you automated end to end, what was the outcome metric, and what broke first when you scaled it
Enterprise pricing that charges for the result
Once the agents own outcomes, per-seat pricing stops matching what the customer is buying.
Move high-tier deals off per-seat pricing
Charge for the result instead of the login. It is easier to defend on a price increase and it lines the incentives up.
- past $1M ARR
- not below $1M ARR
Charge for campaigns shipped, deals closed or hours saved
Outcome pricing is easier to defend on a price increase
Do not try this below $1M ARR, because you cannot underwrite an outcome guarantee without the data
Pick one way of working and run it
The framework you keep replacing costs more than the one you picked. Switching is what kills shipping, not the methodology you passed on.
Choosing the operating framework
Three options that all work at 5 to 50 people. None of them works if you swap every quarter.
References: Shape Up (Basecamp / Ryan Singer)Measure What Matters (John Doerr)NCT Framework
Run one framework for 6 months minimum
Pick on adoption cost, not on elegance. Re-training, re-tooling and re-arguing every meeting costs more than the methodology saves.
- 6 months minimum
Pick whichever framework your most senior engineer or PM already knows
None of these is better in any sense that matters before $5M ARR
One 12-person team switched frameworks four times in a year, then ran Shape Up for 9 months and roughly tripled shipping velocity
Unwritten priorities and undefined ownership are the real problem, and no new framework fixes them
Know what each framework is actually for
They solve different problems, which is why the comparison argument never ends.
OKRs: 3 to 5 objectives with 3 to 5 measurable key results, on a quarterly cadence
Shape Up: 6-week bets with 2-week cooldowns, fixed time and variable scope, and the book is free
NCT: a paragraph of why, then 3 to 5 binary commitments, then tasks
NCT is project-cycle alignment and OKRs are company-level goal setting, so they can coexist
Judge the framework on whether your team runs it weekly
Either works at scale. Constantly switching between them does not.
Pick the one your team can execute weekly, then stop switching
The one tool the work lives in
Two tools means two sources of truth, which means none.
Tools: LinearClickUpMonday.comJiraNotion
References: The Linear Method
Standardize on one tool and leave it alone
The default for most growth-stage teams is Linear. The rest of the list exists for specific cases.
Two tools means two sources of truth, which means no source of truth
Linear is the default for product and engineering teams
Define your views before you adopt a flexible cross-functional board
Jira only at 100+ engineers or in a regulated industry, otherwise it is expensive bureaucracy
Pair Notion with Linear for docs and narratives, and never let both track issues
The weekly meeting rhythm
Written updates for visibility, one short meeting for blockers, one pre-mortem per cycle.
Tools: Geekbot
Replace the daily standup with an async writeup
Visibility and blockers both land better in writing than in a 9am call where half the team is on mute.
- three lines per person
- 30 seconds to write, 30 seconds to scan
Three lines per person in one channel: yesterday, today, blockers
30 seconds to write, 30 seconds to scan, threaded replies for follow-ups
Daily standups eat 5 hours a week of senior time per team
Keep one weekly 30-minute meeting, blockers only
Not status, not strategy. One thing each person is stuck on and who can unstick it.
- one 30-minute meeting a week
Each person names one thing they are stuck on and who can unstick it
If nobody is stuck, end at 5 minutes and give the time back
Status updates belong in writing, not in the meeting
Run a pre-mortem at the midpoint of every cycle
Gary Klein's technique. Asking what killed the cycle surfaces the risks the team has been quietly worrying about.
Ask the team to imagine the cycle just failed completely, then say what killed it
Re-scope or kill the at-risk commitments before the cycle ends with three half-finished features
AI inside the build loop
Cut the cost of building. Keep the decision about what to build with the humans.
Point AI at the boring parts, not the decision parts
These tools shorten the path from issue to PR. They do not decide what belongs in the cycle.
Use an AI-native IDE to shorten the time from issue to PR
Use an autonomous agent for prototype work and a fast UI tool for experiments tied to the cycle
None of these decides what to ship, they only cut what it costs to build
Get the paid tools cheap while you are small
Most of the stack on this page runs a startup program or a free tier that covers early-stage volume. Claim them before you are paying list price.
Vendor startup programs
Credits and discounted plans you apply for once and keep for a year or more.
Tools: Segment for StartupsMixpanel for StartupsAmplitude for StartupsPendo for Startups
Claim the $25k CDP startup credit before you pay list price
The default CDP runs a startup program worth $25k of credit. That is most of a year for an early team.
- $25k startup credit
Segment runs a startup program carrying $25k of credit
Apply through the startup page rather than signing up at list price
What you can run for free at the start
Free tiers and free playbooks that cover you until the volume forces a decision.
Start on the free tiers and pay only once you outgrow them
Product analytics and error monitoring both have free tiers built for early-stage volume.
The product analytics free tier is generous enough to be the default at early stage
Error tracking has a free tier that covers early-stage volume
Use the free playbooks instead of buying a course
The most disciplined small-team methodology and the standard architecture checklist are both free to read.
References: Shape Up (free book)SaaS Startup CTO Checklist
Shape Up has a free book online, which is why it carries no adoption tax
The CTO checklist is a free, well-maintained reference for the quarterly audit
Launch
Build the crowd and the digital footprint before the doors open.
Launch day amplifies what already exists. Spend six weeks earning citations and warming a list, then use the platforms to point at something real.
The checks before you pick a date
Three things have to be true before a date goes in the calendar. Miss one and you move the date.
The three pre-flight checks
The product, the plumbing and the people. All three, or no date.
Clear all three checks or move the date
Each one is a hard gate. Two out of three is not a launch, it is a date you move.
Ship an MVP that is feature-complete and load-tested
Incorporate, set up data and analytics, and get the tracking right first
Have a waitlist or early-access list that opens your emails and replies
Push the launch date if you cannot check all three
The crowd you launch into
A hundred people who already know you beats an announcement to nobody.
Get 100+ people waiting before you flip the switch
The crowd is the whole point. Everything on launch day is amplification, and amplifying zero gives you zero.
- 100+ people waiting
Have 100+ people waiting by the time you flip the switch
If launch day is the first time anyone hears about your product, you already lost
The same product on Product Hunt did nothing for a month cold, and 10x better after six weeks of audience work
Judge the list on replies, not size
A big list that never opens an email tells you nothing on launch day.
Count the people who open your emails and reply, not the raw list size
6-Week Pre-Launch Sprint
Six weeks of work so that by launch day other people are already talking about you, and the AI answers know who you are.
Mentions on sites you do not own
By launch day, someone who Googles your product should find other people talking about you, not only your own site.
Earn citations from 3 or more niche sources before launch day
Newsletters and publications in your space, lined up in the weeks before, not chased on the day.
- 3+ niche sources
Google your product and search it on Perplexity: both should show third-party citations, not just your own site
Aim to have Perplexity quoting your docs by 6am on launch day
AI answer engines before launch day
If the crawlers cannot read your pages, the AI answer about your product gets written from someone else's page.
References: Demand Curve: AI Visibility
Open your site to the AI crawlers
Three fixes. None of them takes a day.
Check robots.txt does not block GPTBot, PerplexityBot or other AI crawlers
Put a plain-English description of what the product does on every page
Add JSON-LD Organization and Product schema
Search yourself on Perplexity 7 days out, then again on launch day
A wrong answer 7 days out is still fixable. A wrong answer on launch day is not.
- 7 days before launch
Search your product name on Perplexity 7 days before launch and again on launch day
Fix the source the AI reads from when the answer is wrong: your FAQ, your docs, your Crunchbase entry
The one action that proves value
Pick the single action that proves a new user got something. The onboarding mechanics live in Onboarding & Retention.
Pick the value moment before you launch
Sent their first email, ran their first report, generated their first image. One action, named before launch day.
Get a new user to the value moment in under 60 seconds
Cut onboarding steps until it fits inside 60 seconds
Launch Day
Use the platforms to amplify momentum you already built, not to manufacture it from cold.
Product Hunt
Treat the comment thread as the launch. The upvote count is a scoreboard, not the work.
References: Product Hunt launch guide
Play comment quality over vote count
The 2026 algorithm weights deep, technical comment threads more than raw upvote counts.
- reply within 10 minutes
- the first 4 hours
Have your community ask hard technical questions in the comments
Reply to every comment within 10 minutes for the first 4 hours
Write substantive answers, never just thanks
Treat the comment thread as the actual launch
Read Product Hunt's current launch guide before you pick a date
The ranking rules move every year. Read the current ones, not the ones from last year.
Read Product Hunt's latest launch guide for the current algorithm
Announcement timing
One blast at one hour reaches one timezone. Three waves reach three.
Send three waves, not one blast
Hit local peak hours in Europe, the East Coast and the West Coast.
- 8am GMT
- 8am EST
- 8am PST
- 24-hour window
Hit 8am GMT for Europe, 8am EST for the East Coast and 8am PST for the West Coast
Re-trigger your email list at each wave so vote velocity holds through the 24-hour window
Post to the other launch rooms the same day
Different audiences, different reasons to care, same 24 hours.
Hit Indie Hackers, Hacker News and BetaList in parallel
Launch across multiple trust channels at once, not one at a time
Hacker News (Show HN)
Technical and developer-facing products do well here. Marketing language does not.
Lean technical on the Show HN post
The angle is what you built and how you built it.
Give Hacker News the technical angle on the same launch
Pick Show HN when the product is technical or developer-facing
Indie Hackers
A room of founders and developers who came for the build story.
Lead with what you learned building it
The build story is the post. The product is the footnote.
Give Indie Hackers the what-I-learned-building-this angle
Use Indie Hackers for product feedback and discovery from other founders
BetaList and BetaPage
Early-access signups before the main launch, for almost no effort.
Lead with the early-access perk
This audience signs up to be early. Give them a reason to be early.
Give BetaList the early-access perks angle
Expect your first 50 to 100 beta testers for almost no effort
The directory blitz
Get listed everywhere your category gets browsed, in one push rather than one submission a month.
Launch directories
A hundred-plus places that exist to list new products.
References: BetaList submit
Submit to the core four before anything else
Product Hunt, Indie Hackers, BetaList and BetaPage are the core stack.
Start with Product Hunt, Indie Hackers, BetaList and BetaPage
Product Hunt is the industry standard for initial momentum
Work the long tail after the core four
The list runs past 100 directories once you work the roundups.
- 100+ launch directories
List your startup in the top 100+ launch directories
Pull the long tail from betalist.com/submit and StarterStory's directory roundups
AI tool directories
They rank for "[your category] AI tools" searches, which is the reason to bother with them.
References: FuturepediaToolifyThere's an AI for that
List here only if the product really has AI in it
Worth the submissions when the product has AI functionality, and only then.
List on the AI directories only when your product has AI functionality
Submit to Futurepedia, Toolify and There's an AI for that
These rank surprisingly well for "[your category] AI tools" queries in 2026
The 30 days after launch
The launch fills the funnel. What happens to the people in it decides whether the launch worked.
Your first 50 power users
Onboard the most engaged signups by hand. It does not scale, and that is the point.
Concierge-onboard the first 50 power users
Reach the most engaged signups personally and walk them to the value moment.
- first 50 power users
Reach out personally by Loom, video call or text message
Get them to the value moment by hand
It does not scale, and that is the point, because you are still learning
The 48-hour stall email
A signup who has not hit the value moment in 48 hours gets one email from you.
Auto-trigger an email when a signup stalls for 48 hours
Plain English, from you, one suggestion and one question.
- 48 hours
Trigger the email when a signup has not taken the value-moment action within 48 hours
Send one specific suggestion and one question: what got in the way?
Judge it on reply rate, not open rate
The 5-day citation check
Five days in, go read what the AI tools say about you. Wrong answers trace back to your own pages.
Re-search your product 5 days after launch
Wrong category, wrong feature or wrong competitor all mean the source data is wrong.
- 5 days post-launch
Re-search yourself on Perplexity, ChatGPT search and Bing Copilot
Treat a wrong category, feature or competitor comparison as a source-data problem
Update your FAQ, docs or Crunchbase entry to fix what the AI reads
Expect AI tools to update citations within a few weeks once the source is fixed
The launch dashboard
Three numbers in one view, so you can see which wave worked and who stayed.
Tools: June.so
Track three numbers in one view
Signup velocity, activation rate, Day 7 retention. Nothing else on the screen.
- signups per hour
- % reaching value moment
- Day 7 retention
Track signup velocity in signups per hour
Track activation rate, the percent reaching the value moment
Track Day 7 retention
Judge the launch on day 30, not day 1
The spike is the easy number to watch and the least useful one.
What happens to the people in the funnel matters more than the launch-day spike
Week two momentum
Referral waitlists and milestone rewards stretch the spike past day one. The referral mechanics live in Partnerships & Referrals.
Tools: Viral Loops
Switch on referral milestones before the spike fades
The launch window is the reason to turn these on now rather than next quarter.
Set up referral waitlists and milestone rewards to extend launch momentum into week 2
Cold Outreach
Acquire from intent signals, not lists.
Reach buyers who never asked, with a reason they would accept. Pick people because something just changed at their company, then send few enough emails that every one of them can be true. The CRM at the end of this branch exists to remember what you promised next.
Make sure the email actually arrives
The guide calls this the survival audit. Align the DNS records, send from a domain you can afford to burn, and check every week where your mail is landing.
The DNS records on your sending domain
Three records have to agree before you send a single cold email.
Align SPF, DKIM and DMARC before the first send
This is the first action in the deliverability audit, and it comes before any volume.
Align SPF, DKIM and DMARC on the domain you send from
The domain you are willing to burn
Cold email goes out from separate sending domains, never from the one your company runs on.
Never send outbound from your primary domain
One rule, stated flatly in the chapter. Your primary domain stays out of every cold sequence.
Keep your primary domain out of every cold sequence
Run outbound from several warm sending domains instead
Let the sending platform manage the extra domains
Managing five sending domains by hand is a job. The outbound platforms exist to do it for you.
Tools: Instantly.aiSmartlead
Manage the warm sending domains inside one platform
Pick a platform built to scale outbound without hitting spam
Warming up the mailboxes
Warm-up and inbox rotation come built into the sending platforms. Turn both on before the first campaign.
Turn on automated warm-up and inbox rotation
A new mailbox needs a ramp. The platforms automate the ramp and spread the sends across inboxes.
Tools: Instantly.aiSmartlead
Let the platform warm new mailboxes instead of ramping them by hand
Rotate sends across several inboxes rather than hammering one
Warm the domain and rotate the inbox before the trigger campaign goes out
Checking where your mail lands
Audit inbox placement weekly, across Gmail, Outlook and Yahoo rather than the one inbox you own.
Audit your inbox placement every week
The chapter puts this in the execution checklist, at a weekly cadence, not a quarterly one.
Tools: GlockApps
Put a weekly inbox placement audit on the calendar
Check Gmail, Outlook and Yahoo, not just the inbox you own
Bounces that cost you the domain
Verification is cheap. A bounced send costs you reputation on the domain you just spent a month warming.
Verify every address before it enters a sequence
Two jobs, two tools in the chapter: verify at list build, then verify again in real time before the send.
- lists 100% clean before you hit Send
Tools: NeverBounceFindymail
Run real-time verification so the list is clean before you hit send
Verify lead addresses with Findymail or Hunter.io before the import
Verify addresses so bounces do not cost you the sending domain
Build the list of people you will email
Two jobs that founders collapse into one: finding the reason to write, and finding the address to write to. Different tools, different order.
Finding the reason to write
A name and a company is not a reason. Enrichment against outside data is where the reason comes from.
Enrich against many data sources to find the exact reason
The chapter calls this signal-based prospecting. The output you want is one sentence you could say out loud.
- 50+ data sources
Tools: Clay
Chase the exact reason for reaching out, not just the contact record
Filter the list on job changes, funding events, tech-stack changes and hiring signals
Enrich and filter prospects against 50+ data sources before you write anything
Finding the person and the address
The database comes second. Match the company first, then go looking for the decision maker.
Filter first, then find the contact details
The chapter sequences these two tools deliberately. Enrichment surfaces the match, the database finds the human.
Tools: Apollo.io
Surface the matching companies first, then look up the decision maker
Use the large B2B database for decision-maker contact info
Use the intent filters to find who is already researching you
The same database carries an intent filter. It narrows a huge list to the companies looking at your category now.
Tools: Apollo.io
Filter for companies already researching your category
Search a massive B2B database once you know who you want
The people who already trust you
The chapter defines cold outreach as finding people who already trust you, or who trust someone you know.
Start the list with people who already trust you or someone you know
Work the trusted names before the strangers. The reply rate difference is the whole reason the chapter opens this way.
Work the people who already trust you before you work strangers
Count the people your contacts trust as part of the same list
Bring a specific, helpful solution rather than a general pitch
Build the list at the account level, not the contact level
The 2026 version of this chapter targets groups of decision makers. One name per account is the old way.
Target groups of decision makers, not individual contacts
Build trust before you sell
Email people the week something changed
Pick people because something just happened at their company, not because they matched a filter last quarter. Three triggers, one at a time.
Events at the company you can see from outside
Hiring, funding, tool changes and public complaints. Pick three of them and stop there.
Pick three events that mean someone just got your problem
A trigger is an event in the world that created the need this week. Not a firmographic filter, an event.
- Pick 3 events
Pick three events that mean someone just developed the problem you solve
A company hiring its first sales rep now needs a CRM
A job listing for a Head of Data means a data warehouse is coming
A Series A means they are hiring fast and need HR tools
A 1-star review naming a feature gap hands you the opening line
The trigger has to mean warm right now, not warm three months ago
Run the signal stack audit and name your top three
The outbound chapter names the same three triggers for most B2B products. Start there if you have no better idea.
- top 3 triggers
Treat a funding round as trigger one, because the budget just appeared
Treat a new Director hire as trigger two
Treat a technology stack change as trigger three
Use real-world triggers to find people who need what you sell right now
Wire the alert so the trigger finds you
Checking for triggers by hand lasts about two weeks. Set the tool to tell you when one fires.
Set the tool to notify you automatically when a trigger fires
Build this week's list from that one trigger, in the same tool
Run one trigger a week and change it before you scale
The checklist item is weekly and small on purpose. You are testing the trigger, not the copy.
- 1 trigger this week
- 50 personalized emails
Pick one trigger this week and build the list from it
Send 50 personalized emails and track the reply rate
Iterate the trigger before you scale the volume
People already sitting on your website
Someone reading your pricing page is the warmest list you own, and the window is hours.
Identify the companies on your site right now
Visitor tracking turns anonymous traffic into a named account list. The chapter files it as warm inbound-outbound.
Run visitor tracking with Reveal, Clearbit or Warmly
Identify the people, not only the companies
Reach out within four hours of a high-intent visit
Four hours is the number in the chapter. After that you are emailing someone who has moved on.
- within 4 hours
Fire the outreach inside 4 hours of the visit
Treat a pricing page visit as a high-intent trigger
Treat a docs page visit as a high-intent trigger
Signals from inside your own product
A signup, a usage spike or an integration install is someone raising a hand without emailing you.
Alert on the three in-product signals
Product-led signals sit in your own database. They cost nothing to watch and they beat any bought list.
Tools: Common RoomDefault
Alert when someone new signs up
Alert when someone hits a usage limit
Alert when someone installs an integration
Decide how much homework each name gets
Every name costs you research time. Decide the budget before you build the list, or you will default to sending more.
How many people you send to
Both chapters give you the same trade in different numbers. Fewer emails, more homework.
Send 200 researched emails instead of 8,000 generic ones
The 200 all reference a specific trigger. That reference is what you are buying with the extra time.
- 200 personalized beats 8,000 generic
Reference the specific trigger in every one of the 200
Cut the list until every remaining name has a reason attached
Aim for ten times fewer messages and five times the replies
The chapter states the target as a ratio, so you can check it after one week rather than one quarter.
- 10x fewer messages
- 5x higher reply rates
Fifty emails with a clear reason beat five thousand generic blasts
Send only messages that have a clear reason behind them
Stop spraying and praying, and start from the signal
Move from static lists to real-time interest signals
What counts as research
The chapter spells out a research workflow. Three inputs, one gap, seventy-five words.
Run a research workflow instead of staring at a profile
Design it once as a repeatable micro-workflow, then run it per prospect. The chapter calls it agentic personalization prompting.
- last 3 LinkedIn posts
- latest 10-K report
- 75-word message
Review the prospect's last 3 LinkedIn posts
Read the company's latest 10-K report
Identify one specific gap and anchor the product to it
Hold the draft at 75 words
Name the trigger in the first sentence
The chapter gives the exact shape: the event by name, a human beat, then the reason you are writing.
Open with the trigger event by name, then say why you are writing
Where the AI stops
Light assist is allowed. A fully generated email is what the whole chapter is written against.
Write each email yourself, with light AI assist at most
Inboxes are full of generated mail. That is the stated reason this rule exists.
Never send a fully AI-generated email
Remember that AI spam is flooding the inbox you are writing into
Strip the sales jargon before it goes out
One pass through an editor that removes the salesy phrasing. The bar is that a helpful human could have written it.
Tools: Twain.ai
Run the draft through an editor that strips salesy jargon
Aim for something a helpful human would have written
Write the email a stranger will answer
Make the ask small and make the reason specific. Both instructions come straight from the chapter execution checklist.
References: Flip the Script (Becc Holland)Fanatical Prospecting (Jeb Blount)
The ask at the end of the email
A 15-minute meeting is a large ask from a stranger. Ask for interest instead.
Use a soft CTA
The chapter gives two exact lines you can copy, both of which ask for a yes rather than a calendar slot.
Stop asking for 15-minute meetings
Ask whether it is worth a chat
Offer to send over the 2 ideas you found
Asking for something other than a meeting
The chapter files this one under high reply rate, and it never mentions the product.
Ask for a one-sentence expert quote
You are asking a busy person for a sentence, not an hour. Then you publish it and cite them.
Ask for a 1-sentence expert quote for a research paper you are building
Cite the people you want as customers
How long the message is
Seventy-five words, anchored on one gap. That is the whole spec.
Keep the message to 75 words anchored on one gap
One gap, named. Everything that is not the gap or the ask comes out of the draft.
- 75 words
Anchor the product to the one gap you found
Draft to 75 words, not to a page
The reason you are writing
One named reason per message. The chapter example is a company that just launched a competitor to something you sell.
Write one named reason per message
The reason is what makes 50 sends beat 5,000. It has to be about them, and it has to be checkable.
Name the reason, for example that they just launched a competitor to X
Base each send on a clear reason rather than on the list
Judge outbound on signals and survival, not on volume
Follow up in more than one place
One email to one person is the weakest version of outbound. Orchestrate across channels and across the buying group.
Email, then LinkedIn
Three touches, three surfaces, in a fixed order.
Run the triple-tap
Email first, connection request second, and a DM that gives something third.
Send the email first
Send the LinkedIn connection request second
Make the third touch a DM that adds value
The buying committee
One champion cannot buy alone. Three to five people decide, so three to five people get the message.
Message the champion, the decider and the gatekeeper at once
The chapter calls this the committee consensus sequence. The point is one story, told to three roles at the same time.
Modern B2B decisions involve 3 to 5 stakeholders
Target the champion, who is the user
Target the decider, who is usually the manager
Target the gatekeeper in finance or ops
Run one cohesive narrative across all three roles
Send to all three at the same time, not one after the other
Demos people can watch without booking a call
A committee of five will not sit through five demos. Send one they can watch on their own time.
Send an on-demand demo instead of a calendar link
The chapter names Consensus and Loom for this. Both let a stakeholder watch without scheduling anything.
Point the whole committee at one on-demand demo
Use Consensus or Loom to record the on-demand demo
Get a phone number and use it
Before you can call anyone you need a direct dial. The guide covers exactly that: which enrichment tool gets you phone numbers, and which one to skip.
Getting a direct dial for someone who has not replied
Enrichment tools split on this. Some give you firmographics, one of them is built around phone numbers.
Use the lighter enrichment tool when you want phone numbers
The chapter names it as the lighter alternative, and direct dials are the reason you would add it.
Tools: Lusha
Add the lighter enrichment tool for direct dials
It is the lighter alternative, and direct dials are its focus
Skip the enterprise data tool until you have a sales team
The enterprise-grade option is priced for a team that dials all day. That is not a founder doing outbound between builds.
Tools: ZoomInfo
ZoomInfo is enterprise-grade and expensive
Wait until you have a dedicated SDR team before you buy it
Count replies and closes, not sends
Sends are the easiest number to grow and the least useful one to read. Score the list on replies, meetings and closed deals.
Replies and closes on two comparable lists
Two founders, same niche, same week, same product. The only difference was who they picked.
Score two lists side by side
This is the single most useful comparison in the guide, because it holds the product constant.
- 8,000 emails, 14 replies, 0 closed
- 200 emails, 41 replies, 9 closed
- selection beats volume by 30-50x
Founder A sent 8,000 emails to a generic list, got 14 replies and closed 0
Founder B sent 200 emails on a hiring trigger, got 41 replies and closed 9
Same product, different selection
Selection beats volume by 30 to 50 times once you have a real trigger
The winning trigger was a company hiring its second engineer inside 90 days
What good looks like on a cold list
Two conversion numbers to hold your campaign against, and a ratio to check after week one.
Compare your reply rate against the two benchmarks
A generic list and a trigger list are not the same activity. Judge them against different numbers.
- generic lists convert at under 1%
- trigger-based converts 10-20%
Generic lists convert at under 1%
Trigger-based outbound converts at 10 to 20% inside the right window
Hold yourself to the ratio, not the send count
Ten times fewer messages and five times the reply rate. Both halves have to move or the change did nothing.
- 10x fewer messages
- 5x higher reply rates
Track 10x fewer messages and 5x higher reply rates as the target
Meetings booked out of qualified replies
The rate that moves when your follow-up stops leaking, and the one number in the CRM chapter worth reporting.
Track meetings booked as a share of qualified replies
One founder doubled this without sending a single extra email, by fixing capture and follow-up.
- 14% to 31% of qualified replies
One founder moved from 14% to 31% of qualified replies
The rate moved because nothing was slipping through
Pick the CRM that fits your revenue
Most pre-PMF founders do not need one. Match the tool to the stage, write one sentence on why, then stop shopping.
When a spreadsheet is still the right answer
Under 50 prospects, five columns beat any tool you could set up this week.
Run a five-column sheet until you pass 50 prospects
Name, Company, Last Touch, Next Step, Stage. The columns are the whole system.
- 0-50 prospects
Use columns for Name, Company, Last Touch, Next Step and Stage
A spreadsheet handles 0 to 50 prospects fine
Do not spend a week setting up a CRM for 12 contacts
Setting up a CRM-shaped tool for 8 leads is procrastination
The first real CRM
Switch at 0 to 10k MRR with five or more live conversations a week. Auto-logging is the only feature that matters.
Switch off the sheet at five active conversations a week
Both of the tools named here log Gmail and Calendar with no human in the loop, and the free tier covers most early cases.
- 0-$10k MRR
- 5+ active conversations a week
Switch once you run 5 or more active conversations a week
Pick a tool that auto-logs Gmail and Calendar without human intervention
Auto-logging is the only thing you should care about at this stage
The free tier covers most early-stage cases
Judge the tool by whether you will use it
The chapter states this as the decision rule, and it settles most arguments before they start.
The CRM you will actually use beats the one that scores best on G2
Auto-capture beats manual entry every time the founder is also the salesperson
Write one sentence on why this CRM matches your stage and motion
The CRM that lives in Gmail
If you are already in Google Workspace and will not leave the inbox, put the CRM inside it.
Keep the CRM in the inbox you never leave
You trade analytical depth for friction, and friction is what kills CRM adoption at this size.
Tools: Copper
Pick the Gmail-native CRM if you are already in Google Workspace
Accept less analytical depth in exchange for much lower friction
When a salesperson owns the pipeline
At 10k to 100k MRR with a dedicated seller, the question becomes stage discipline.
Add stage discipline once a seller owns the pipeline
The pipeline-stage tool is the right call when the team already thinks in stages. Otherwise the earlier tool still works.
- $10k-$100k MRR
Attio still works at $10k to $100k MRR with a dedicated sales person
Pick the pipeline-stage tool if your team thinks in stages and wants strict discipline
Add the all-in-one suite only when marketing joins the CRM
Marketing automation next to the CRM is the trigger. Nothing else is.
Tools: HubSpot
Move when you start to need marketing automation alongside the CRM
The free tier is fine and the paid tiers escalate fast
The bundled suite at 100k and up
At 100k+ MRR with bundled marketing needs, the all-in-one suite earns its keep.
Let the all-in-one suite earn its keep at 100k+ MRR
The condition is bundled marketing needs, not headcount and not revenue on its own.
- $100k+ MRR
Tools: HubSpot
Adopt the bundled suite once the marketing needs are bundled too
Only buy Salesforce when procurement demands it
One enterprise customer requiring it in procurement is a separate decision from your CRM choice.
Treat an enterprise procurement requirement as its own decision
Do not preempt it before a deal actually requires it
What the wrong CRM at the wrong stage costs
A six-figure contract, three months, and about 40 logged contacts. Then they canceled it and the follow-up fixed itself.
Cancel the oversized contract instead of growing into it
The replacement was a free workspace that logged every Gmail conversation on its own, plus a 12-minute Loom.
- $30k MRR
- six-figure contract
- 40 contacts in 3 months
A founder at $30k MRR signed a six-figure contract on an advisor recommendation
Three months later a team of two had logged about 40 contacts
None of those contacts were enriched or followed up
They replaced it with a free workspace that auto-logged every Gmail conversation
A 12-minute Loom was the entire team rollout
The right CRM at the wrong stage is worse than no CRM
Make the CRM fill itself in
The biggest CRM failure is a founder typing notes the tool could have captured. Wire the capture first, because everything else is downstream of it.
Email and calendar sync
Ten minutes of setup. Skip it and the rest of the CRM work is pointless.
Connect email and calendar before anything else
Conversations and meetings land on the right contact record with no manual entry.
- 10 minutes to set up
Setup takes 10 minutes
Conversations and meetings log into the right contact record without manual entry
Skip this step and the rest of the chapter is moot
Kill the four-hour-a-week typing tax
Four hours a week of typing notes is the single biggest CRM failure mode in the chapter.
- 4 hours a week
Founders lose 4 hours a week typing notes the tool could have captured
Fix capture first, because everything else is downstream of it
Check the box only when there is no manual-typing tax left
Capture the conversations you forget you had
Inside a week of wiring auto-capture, one founder had records of conversations he no longer remembered.
Within a week every conversation was captured automatically
That included conversations the founder had forgotten he had
Enrichment at first contact
One moment needs enrichment: a new email lands and you want to know who they are without opening LinkedIn.
Enrich at the one moment you need it
Company, role and rough size, attached automatically when the email arrives. One tool, not three.
Enrich when a new email lands, not on a schedule
Get the company, the role and the rough company size without opening LinkedIn
Keep exactly one enrichment tool active for first-contact context
Pick the enrichment tool by what you need out of it
One of these builds a firmographic profile from an email address. The other adds outbound sequencing in the same tool.
Clearbit was acquired by HubSpot and is now part of HubSpot Breeze
Clearbit builds an automatic firmographic profile from any email address
Apollo does enrichment and outbound sequencing in one tool
Sales calls in the record
A 10-minute write-up becomes a 60-second automated summary. Free tiers cover early-stage volume.
Auto-summarize the call in 60 seconds, not 10 minutes
Transcribe the call and drop the summary straight onto the contact record.
- 60 seconds, not 10 minutes
Tools: FathomFireflies.ai
Auto-transcribe the call and drop the summary into the contact record
Free tiers cover early-stage call volume
Partner relationships visible in the record
If a partner already knows the account, the cold email is the wrong move. Wire the overlap into the CRM so you can see it.
Check for a warm path before you send the cold email
Account mapping syncs into the CRM and flags the accounts a partner already sells to.
Before any cold email, check whether a partner has a relationship with the account
Ask for the introduction instead of sending the cold email
Do not wire this up before you have at least one mapped partner
Only add this layer if you are running nearbound
Know who you owe an answer today
The CRM is good at one thing: telling you who to follow up with today. One saved view and one cadence per stage do the work.
The one view you open every morning
Deals where the next step is overdue. That is the whole list.
Build the view of deals where you owe a next step
Either build the saved view or use the default one. Then open it before anything else.
Filter to deals where the next-step date is past today and you have not done it
Treat that view as your morning checklist
Work what is in the view and leave the rest alone
Keep exactly one saved needs-follow-up-today view
Cadence set by deal stage
Four intervals, one per stage. The default 30-day reminder is not one of them.
Replace the default reminder with a real interval
Follow up in 30 days is how deals die. Set templates per stage instead.
- default 30-day reminders
Default 30-day reminders are how deals die
Set cadence templates per deal stage instead of defaults
Match the interval to the stage of the deal
The chapter gives four exact intervals. Pre-set them as templates if the CRM supports it.
- intro 48h
- first meeting 24h
- post-demo 3 days
- post-proposal weekly
Follow up an intro touch in 48 hours
Follow up a first meeting in 24 hours
Follow up after a demo in 3 days
Follow up weekly after a proposal until you get a decision or an explicit no
Pre-set these intervals as templates if the CRM supports them
Keeping the database honest
One purge a quarter. Six months of silence means archive, not nurture.
Purge the dead records every quarter
Archive anything with no activity for six months so the live deals stay visible.
- quarterly purge
- older than 6 months with no activity
Archive any record older than 6 months with no activity
Purge so the real signal is not buried under old records
The features to leave switched off
Intent scoring, AI-drafted emails and predictive analytics are overhead until human attention cannot keep up.
Skip intent scoring and AI drafting until volume forces it
The threshold in the chapter is around $200k ARR with multiple reps. Below that you are the scoring engine.
- $200k+ ARR with multiple reps
Intent scoring, AI-drafted emails and predictive analytics are overhead early
Wait until you have enough volume that human attention cannot handle it
That is usually $200k+ ARR with multiple reps
What the CRM is actually for
A tool for remembering: who you talked to, what you said, what they said, what you promised next.
Use it for remembering, not for intelligence
It fixes forgotten follow-ups. It does not fix a product that is not ready.
A CRM remembers who you talked to and what you promised next
It helps when you are losing deals because you forgot to follow up
It will not help when you are losing deals because the product is not ready
Community & Forums
Show up where your buyers ask questions.
Ten substantive answers a week in the subreddits, communities and forums where your ICP hangs out. Helpful first, never promotional.
Find the rooms your buyers sit in
Find where your target persona hangs out when they are frustrated. Then pick a few rooms and stay in them.
Discord servers
Live chat rooms where your niche talks every day. Learn the house rules before you speak.
Tools: Disboard
Join the top 5 servers in your niche
Five servers, joined and read, beats twenty you never open.
- top 5 servers
Find the top 5 servers in your niche and join them
Read the Rules channel carefully on every server you join
Reddit, TikTok and YouTube
The same pain gets described three different ways. Read all three before you pick your words.
Tools: BuzzAbout
See how the same pain gets described on each platform
One search across three platforms tells you which words the market already uses.
Run one niche search across Reddit, TikTok and YouTube to read the vibe of the niche
Newsletters, subreddits, Discords and search keywords
Your dream customers already hang out somewhere. A newsletter and a search keyword count as rooms too.
Shortlist 3 to 5 rooms and commit to them
Three to five rooms you show up in weekly, not twenty you lurk in once.
- 3-5 subreddits, Slack groups or Discord servers
Pick the 3 to 5 subreddits, Slack groups or Discord servers where your buyers actually hang out
Use a niche-community directory for Slack and Discord, and a Reddit mining tool for subreddits
Search for the people who already have the problem you are trying to solve
Show up with value before you ask for a signup
The signup ask comes much later. Sometimes it never comes and they find you anyway.
Count newsletters and specific search keywords as watering holes, not just subreddits and Discords
Show up there with value before you ever ask for a signup
Mine Reddit for real complaints
People are blunt when they are frustrated. That is free validation for your hypothesis if you go and read it.
References: How to find good product ideas on Reddit (Indie Hackers)Reddit for customer acquisition (Indie Hackers)
The idea subreddits
Three rooms where strangers post the thing they wish existed, for free, every day.
Join the three subreddits where people post what they wish existed
Subscribe once and the demand shows up in your feed instead of you hunting for it.
Join r/SomebodyMakeThis, which is pure demand
Join r/AppIdeas for high-volume software requests
Join r/Startup_Ideas for peer-vetted concepts
The builder subreddits
Three rooms where people building the same kind of thing post what is working this month.
Join the three subreddits where builders post what is working
Trends, solo build strategies and the small niches nobody writes headlines about.
Join r/SaaS for modern software trends
Join r/IndieHackers for high-leverage solo build strategies
Join r/MicroSaaS for small, highly profitable niches
Reddit search and the Top sort
Every complaint in your category is already written down there. You just have to query it properly.
Search the phrases people use when they are stuck
Three phrases mean somebody is stuck and shopping. Run all three in every target subreddit.
Search "How do I...", "Why is it so hard to..." and "Is there an app for..." in every target subreddit
Run site:reddit.com "how do I" [niche keyword] on Google to skip the noise and land on specific utility gaps
Read the Top posts backwards
Old demand that nobody served is still demand. Go and read it.
- Past Year
- All Time
Read the Top posts for the Past Year and for All Time
Treat a popular idea from 2 years ago with no high-quality solution as a structural inefficiency you can exploit
Wait for the problem to repeat before you build
One loud thread might just be one person having a bad week. Wait until it repeats.
- 3+ different subreddits
- 6 months
Require the same problem in 3+ different subreddits across 6 months before you call it a structural gap
Read the negative comments as your requirements list
The people explaining why it will not work are handing you the spec for free.
Turn the comments saying an idea will not work into your product requirements list for the edge cases
The subreddits where your buyers already post
Set the alerts once and new complaints arrive in your inbox instead of you going to look.
Tools: GummySearchReSurferGoogle AlertsPostponeLater for Reddit
Track the two phrases that mean someone is shopping
Search one phrase and you find people who want a product that does not exist. Search the other and you find people already paying a competitor.
- 20+ subreddits
Track "Is there an app for" across 20+ subreddits
Track "I hate [Competitor]" across the same subreddits
Get told the day new pain gets posted
A standing alert beats a weekly manual sweep, and it costs nothing.
Set a Google Alert for "r/[SubredditName] I wish" so new pain points reach you instantly
Post when the subreddit is awake
A good post at 2am gets the same result as no post at all.
- Tuesday and Wednesday mornings
Schedule Reddit posts for peak engagement times, usually Tuesday or Wednesday mornings
Answer Don't Pitch
A weekly quota of real answers in the rooms your buyers use. Nothing attached and nothing sold.
Subreddits where your buyers ask questions
The category subreddit is where a stranger asks the exact question you can answer better than anyone.
Post 10 substantive answers a week once you are growing
A quota, tracked like any other weekly number, on the subreddits where your ICP hangs out.
- 10 substantive answers per week
Post 10 substantive answers per week on the relevant subreddits, communities or forums where your ICP hangs out
Keep every answer helpful first and not promotional
Never turn an answer into a pitch
One promotional post costs you the room, and you do not get it back.
Expect promotional posts to get banned within a week and burn the channel forever
Slack groups and Discord servers
The 3 to 5 private rooms you committed to, worked every single week.
Answer 2 to 3 substantive questions a week while you are still validating
The starting cadence, before you know which rooms pay back. It rises to 10 a week once you are past validation and into growth.
- 2-3 substantive questions per week
Answer 2 to 3 substantive questions per week in the groups you picked
Answer them helpfully, with nothing attached
Earn trust before you ask
Ask for advice and you get users. Ask for users and you get ignored.
Public community threads
In the main thread, people read a dropped link as a pitch and a real question as real work.
Read three months of Top posts before you post anything
You are learning the words this room uses for the pain. You cannot fake that later.
- last 3 months of Top posts
Read the last 3 months of Top posts before you post
Write down the vocabulary the community uses to describe their pain
Post as someone asking for advice
Show them a real problem and they see a builder. Announce a launch and they see a seller.
Post a screenshot of the specific UI or logic problem you are solving
Say what you are building and ask how they would prefer it to handle a specific edge case
Post your link only after someone asks for it
The link is the reward for being useful, not the reason you showed up.
Never post a link in the main thread
Post the value, wait for someone to ask how they can try it, then reply with the link
Ask for advice, not for users
The whole protocol in one line, and the one people break first.
Ask for advice, get users. Ask for users, get ignored.
Direct messages inside the community
Someone who just posted a complaint about your competitor is the warmest prospect you will find this week.
DM the people complaining about your competitor
They already told the room what is broken. You are replying to that, not cold-opening.
- 5 people
Search the community for your competitors and read the complaints
Private message 5 people who posted complaints
Name the specific pain they posted about, offer a free look, and ask for an expert eye with no sales pitch
Your Reddit and X profile
People check who you are before they answer you. Give them somewhere to land.
Point your bio at your landing page before you start posting
Fix this once, before the first post, and every later post works harder.
Make sure your Reddit and X profile links to your landing page
Expect people to stalk your profile before they reply to your posts
Run your own room
Running your own community means starting with zero members and no reason for anyone to show up.
References: The Cold Start Problem (Andrew Chen)
Your own subreddit or community
An empty room with your name on it. Nobody is in it yet, and that is the whole problem to solve.
Plan the bridge from the idea to your first 10 users
Know how the first ten people arrive before you open the doors.
- first 10 users
Work out how you get from finding an idea to gathering your first 10 users in an empty subreddit
Learn how to seed a community from zero first
Seeding from zero is its own skill, and it is the one this manual points you at a book for.
Learn how to seed a new community from zero before you open one
Private groups you have to join
The rooms that never show up in a public feed. A directory or a Google operator is how you find them.
Tools: The Hive Index
Facebook Groups
Where non-technical buyers still gather, and Google indexed the group pages.
Find the groups, then let them ask for your link
One search operator gets you in. Waiting to be asked keeps you there.
Run site:facebook.com/groups "[niche]" on Google to find private groups in your niche
Post the value in the group and reply with your link only when somebody asks how to try it
Slack communities
Invite-based niche Slacks. Harder to get into than a public subreddit, and worth the trouble.
Find the Slack communities, then open with a question
Two ways in, and one opening line that works in both.
Run site:slack.com [niche] on Google to find private Slack communities
Search a niche-community directory for the Slack groups in your topic
Open by asking for advice, not by asking for users
Circle communities
Creator-run and paid rooms, indexed by topic in the same directory as Slack and Discord.
Find the Circle communities, then drop the promotion
People pay to be in these rooms. They spot a pitch faster than anywhere else.
Use the directory that indexes Circle alongside Slack, Discord and Discourse
Skip overt promotion and lead with authentic engagement and advice-seeking
Discourse forums
Long-form niche forums, listed in the same directory as the chat platforms.
Find the forums, then learn their words first
Threads here stay readable for years, so the vocabulary is sitting there waiting for you.
Pull the Discourse forums for your topic from the same community directory
Read the forum's last 3 months of Top posts and use its own words for the pain
Telegram groups
Niche Telegram groups, found through the same directory that covers Slack and Discord.
Find the groups, then earn your place before you ask
In a small room, everyone notices the stranger who asks for something on day one.
Use the directory that covers niche Slack, Discord and Telegram groups
Gain trust in the group before you ask anyone for anything
Content Marketing
One anchor per week, ten atomized pieces.
Make one substantive thing a week, cut it into ten, and put something in it that nobody else has published. Posting more is not the fix. Having something to say is.
Say something the other ten pages did not
One standard sits under every post, every page and every pitch: concrete facts, original numbers, real case studies, opinions with the reasoning shown. If a model could have written it from a vague prompt, it earns you nothing.
Your blog and site pages
The bar is not "well written". The bar is "contains something that is not on five other pages".
Audit your top 10 pages for what only you could have written
Go post by post and ask one question. Anything that fails gets rewritten, not re-titled.
- one citable original fact per 300 words
Ask what each post contains that an AI could not generate from a vague prompt
Count only four things: original customer data, a specific numerical claim with sourcing, a case study with names and dates, or a contrarian opinion with the reasoning shown
Hold one piece of citable, original information per 300 words
When the answer is nothing, rewrite the post
Swap every generic claim for a number
A claim anyone could make gets quoted by nobody. A number with a method behind it gets quoted by everyone.
- 142 B2B SaaS companies surveyed
- 67% have a documented onboarding playbook
- 23% measure activation past day 30
Turn "most B2B companies struggle with onboarding" into "we surveyed 142 B2B SaaS companies, 67% have a documented onboarding playbook, only 23% measure activation past day 30"
Concrete numbers plus a cited method are citable, and generic claims are invisible to AI
Strip the fluff off your homepage
One superlative gives a model nothing to quote. Three numbers give it three things.
- 14M transactions per quarter
- 12bps fees
- 99.97% uptime over the last 18 months
"We are the leading platform for X" tells an AI nothing it can quote
"We process 14M transactions per quarter at 12bps fees, with 99.97% uptime over the last 18 months" gives it three citable facts
Audit the homepage and the top blog posts, then replace every generic claim with a number, a date, a method or a named comparison
Publish the teardown of your own failure, with the real numbers
A founder threw out 60 agency posts and replaced them with one honest post-mortem. The one post beat all 60.
- 60 posts, 8 months, $40k
- cited by 3 newsletters
- more qualified signups in 6 weeks than 60 posts in 8 months
60 agency-written SEO posts cost 8 months and $40k, ranked page 2 to 3, and converted close to nothing
One teardown of a failed launch, with the actual numbers, the real reasons and the investor post-mortem, got cited by 3 newsletters and showed up in Perplexity for the main query
Throw out the posts that rank page 2 to 3 and convert nothing
Information gain is not a buzzword, it is the only thing that worked here
Run the could-an-AI-have-written-this test before you schedule
Thirty seconds, out loud, on every post. It catches the paragraphs that say nothing before a reader has to.
Read the post out loud before you schedule it
If a generic model could have produced the same paragraph from a vague prompt, add a specific number, a contrarian take or a real story
Generic content is invisible to humans and to AI
Pillar and cluster structure on your blog
Six posts on six topics teach a search engine nothing. Six posts on one topic teach it that you own the topic.
Write one pillar and five supporting posts per topic
A fixed shape you can repeat. The pillar answers the big question, the five posts answer the follow-ups and link back.
- pillar at 3,000+ words
- 5 cluster posts at 1,000-1,500 words each
Write one comprehensive pillar post of 3,000 words or more, fully cross-linked
Write 5 supporting posts of 1,000 to 1,500 words each, every one linking back to the pillar
Use the fixed pattern: pillar is "what is X", clusters are "how to do X for [persona]", "X vs alternative", "common mistakes in X", "X case study", "tools for X"
Go deep on one topic instead of wide on six
Both Google and the answer engines reward semantic depth on a topic. Scattering posts across six topics buys depth on none of them.
Google and AI tools both reward semantic depth on a topic
Make one thing a week and cut it into ten
Most founders create from scratch every day and stop by month 4. One focused session a week produces the whole week, and the rest is cutting and queueing.
The one session that makes the week
One recording or one draft, done with your full attention. Everything you post that week comes out of it.
Pick one format and make it once, with full focus
Four formats to choose from. The right one is the one you can sustain and the one your buyers already use.
Pick the format that fits your strengths and the medium your buyers use
Record or write it once with full focus, because that session is the week’s content engine
Stop posting daily from cold
Skip a week before you post filler
A missed week costs you nothing. A mediocre week trains both readers and models to skip you.
Skip a week before you post mediocre filler
Quality beats frequency, and it beats it hardest on AI citations
Take next week’s anchor from the question people keep asking
The cheapest content input you have is the one your own users already wrote for you.
Source ideas from your Discord, your subreddit, your customer interviews and your newsletter replies
Turn the most-asked question of the week into next week’s anchor piece
Actual user questions, debates and objections keep the content grounded in real intent
One deep piece a week beats posting twice a day
The daily-from-scratch model is why founders quit content in month 4. Reuse is what makes it survivable.
- 1 deep piece per week atomized into 10 posts
- burn out by month 4
One deep piece per week, atomized into 10 platform-specific posts, beats posting twice a day on five platforms
Founders who create from scratch every day burn out by month 4
The ten pieces that come out of it
The target is ten platform-native pieces from one anchor. Not ten reposts of the same link.
References: Justin Welsh: The Content OSDemand Curve: Content Ecosystems
Get 10 platform-native pieces out of one anchor
One focused session should cover a week of presence. Each piece is rebuilt for the platform it lands on.
- 10 platform-native pieces from one anchor
Aim for 10 platform-native pieces from one anchor
One focused session should buy you a week of presence
Break the anchor into platform-native variants, not one link posted five times
Turn one newsletter issue into 3 to 5 social posts
The issue is the work. Social is where it gets distributed, and it splits along three angles plus a thread.
- 1 issue into 3-5 posts per week
- 3 LinkedIn posts
- 1 X thread
- 1 short-form video script
One Tuesday issue becomes 3 LinkedIn posts, 1 X thread and 1 short-form video script
Give the 3 LinkedIn posts three angles: the core insight, one specific tactic, one counterintuitive takeaway
Put the effort into the anchor, because atomization is downstream of it
Where AI belongs in the workflow
Resist AI for the personal layer. Use it for the production layer, where it saves hours and costs you nothing.
Hand AI the production work and keep the opinions
Transcripts, subtitles, clip-finding, meta descriptions and title variants are machine work. What you think is not.
Use AI to transcribe, generate subtitles and find the clip-worthy moments
Use AI to write meta descriptions and suggest title variants
AI video synthesis earns its place in translation, dubbing and accessibility
Podcast, video, essay or customer interview
Four formats carry a weekly anchor, and three of them are recorded. Pick one, get good at it, and cut the short clips out of what you already made.
The 30-minute podcast you host
Half an hour of recorded conversation, captured well enough to cut into a week of clips and quotes.
Record a 30-minute episode as the week’s anchor
Record it locally so a bad connection cannot cost you the episode, then edit the transcript instead of the waveform.
- 30-minute episode
Make a 30-minute podcast the week’s anchor format
Record locally for high-resolution audio and video instead of trusting the call connection
Edit the episode by editing its transcript, and cut the filler that way
The 15-minute video you record yourself
One take, one camera, fifteen minutes. It is the anchor and it is also the raw material for every clip you post that week.
Tools: Descript
References: Ali Abdaal: YouTube Guide
Record a 15-minute talking-head video as the week’s anchor
A single long recording gives the clippers something worth cutting. A pile of short takes does not.
- 15-minute video
Make a 15-minute talking-head video the week’s anchor format
The long recording is what the 60-second clips get cut out of
Cut the filler, add chapters and generate the transcript in one pass
Short vertical clips cut from the recording
You do not film these. You cut them out of the anchor you already recorded, and a tool picks the moments.
Auto-cut the 60-second clips out of the long recording
The clippers already know which moments travel, because they have watched millions of clips do it.
- 60-second clips
Auto-cut the most-shared 60-second clips out of the video or podcast
The clippers find the moments using engagement signals from millions of past clips
The 2,000-word essay
The written anchor. It atomizes by claim rather than by clip, which makes it the cheapest of the four to run.
Write one 2,000-word essay as the week’s anchor
Write it once, then mine it for the five to seven claims that stand on their own.
- 2,000 words
- 5-7 standalone posts
Make a 2,000-word essay the week’s anchor format
Pull out the 5 to 7 strongest claims as standalone LinkedIn or X posts
The recorded customer interview
A structured interview with a real customer. It records like a podcast and it cuts like one.
Record a structured customer interview as the week’s anchor
The format your buyers hear themselves in. Record it, transcribe it, cut it the same way you cut a podcast.
Make a structured customer interview the week’s anchor format
Pick it when a recorded interview is the medium your buyers actually use
Transcribe the interview and edit it by editing the text, the same as any other recording
Treat social as distribution, not as the work
The anchor is the work. LinkedIn and X are where the pieces land. You rent the reach on both, so every post points back at something you own.
Write three LinkedIn posts out of one anchor
Same source material, three different reasons to stop scrolling.
- 3 LinkedIn posts per issue
Post the core insight, then one specific tactic, then one counterintuitive takeaway
Pull the strongest claims out of an essay and post them as standalone LinkedIn posts
X
One thread per anchor, plus the claims that stand up on their own.
Tools: Hypefury
Cut one X thread out of every anchor
The thread is the long form of the platform. It carries the argument the single posts only gesture at.
- 1 X thread per issue
Cut 1 X thread out of every anchor issue
Post the 5 to 7 strongest claims from an essay as standalone X posts
Queueing the week
Write the week, queue the week, close the tab. Posting live is how the day disappears.
Queue the week’s posts at the start of the week
One queueing session, then nothing to decide for six days.
Stop posting in real time
Queue the whole week of posts in one session at the start of the week
Posting in real time is how founders end up doom-scrolling their own engagement
Post as yourself, not as the company
The posts nobody can generate for you are the ones where you lost money, broke the build, or repeated what a customer actually said. That is the whole edge.
Building in public
One update a day about the real work. Progress, failures and customer wins, posted while they are still happening.
Post one behind-the-scenes update a day
Aim at the parts a model cannot invent. The numbers that went the wrong way and the conversations that actually happened.
Share one behind-the-scenes update daily on LinkedIn or X
Post the losing money, the technical failures and the real customer conversations
Focus on the things AI-generated content cannot fake
Authenticity is the differentiator once everybody else is generating posts
Stop building where nobody can see it
Most startups die building in isolation. Posting the work as you do it is the cheapest fix available.
Most startups die because they build in isolation
Your own words, not a generated version of them
Readers are tuned to spot generated prose now. The reason a founder post works is that the founder wrote it.
Never hand your opinions to a model
Use AI on the production layer all you want. The moment it writes what you think, the post stops being worth reading.
Do not use AI to ghostwrite your opinions or fake a personal video
AI-flavored prose reads like AI-flavored prose, and audiences are now tuned to detect it
The point of you posting is that you are the one saying it
Do not clone yourself with an AI avatar
A founder sent AI avatar welcome videos to every new signup. Conversion did not move, and his hand-written follow-ups did.
- reply rate up 4x on hand-written follow-ups
- 90 seconds to write it yourself
AI avatars sending personalized welcome videos to every new signup did not move the conversion rate
Reply rate to his real, hand-written follow-ups went up 4x in the same period
Write the email yourself in 90 seconds or send nothing, because the middle is worst
Answer what your buyers already type
Buyers search before they ever reach a form. Write the answers they are searching for, and ship a small tool for the ones a page cannot answer.
The questions buyers already ask
You do not have to guess the topics. Your buyers have already typed them, in public, into two search boxes.
Read the questions before you pick a topic
Two searches, ten minutes, and you have the backlog. Read what people asked, not what a tool ranked.
Search "[your category] reddit" and "[your category] vs X" on Google and Perplexity
Read the questions people actually asked
Answer the 10 most common questions in long form
You are not writing these for this quarter. You are writing them so a model has something to quote when somebody asks the same thing next year.
- the 10 most common questions
- quoted 6 months from now
Answer the most common 10 questions in long form, on your own blog
Answer with specific numbers and named comparisons
The point is not SEO traffic, it is being the source AI tools quote when someone asks the same question 6 months from now
Buyers search before they ever reach your form
The shortlist gets built somewhere you do not control, before anyone types their email into anything of yours.
Modern B2B buyers search Perplexity, ChatGPT and category-specific subreddits before they ever fill out a form
AI search engines and high-intent communities are where modern decisions start
A small free tool
One page that does one useful calculation. It earns the search, and the inputs tell you whether the problem you assumed is real.
Ship a small free tool your buyers would search for
Build the thing with a query behind it, then read what people type into it.
Build something searchable: a burn rate calculator, a site scorecard
The data their inputs generate is your validation
If the inputs reveal the problem you assumed you are warm, and if they do not you are solving an imaginary one
SEO & AI Search
Build topic clusters, not individual posts
Ranking on Google is half the job. The other half is being the page ChatGPT, Perplexity and Bing Copilot quote back. Both are won by pages a machine can find, read, and lift a paragraph out of.
Find the queries worth writing for
Pick queries by what the searcher wants, not by the biggest number next to them. Then take the ones your competitors already rank for and you do not.
Query selection
Three or five topics, chosen from what your buyers search and read. Not from your product roadmap.
Chase intent, not the vanity keyword
A keyword with big volume that your buyer never types wins you nothing. Go after the queries that show someone with a problem and a budget.
Rank for the queries that drive intent, not vanity keywords
Aim to be the canonical source on the topics you cover, not just a page that ranks
Pin down the 3 to 5 topics your buyers actually search
Three to five topics is the whole list. Pull it out of a keyword tool, not out of a planning meeting.
- 3-5 core topics
Use a keyword research tool to identify the 3 to 5 core topics your buyers search
Find out what your buyers already read
Audience research tells you where the attention sits before you commit a quarter of writing to a topic.
Find exactly what your target customers read, watch and listen to
Competitor research
Your competitors already paid to find out which queries work. Read their list before you write yours.
Tools: Ahrefs
Pull the queries competitors rank for and you do not
One report gives you a content backlog you did not have to guess at.
Run the Content Gap report to find the queries competitors rank for and you do not
Tune the page before you publish it
The pre-publish pass. Check the page covers its topic, read its structure with a tool, and keep AI away from the parts a reader would call your opinion.
References: Backlinko (Brian Dean)Ahrefs AcademyDemand Curve: Content Playbooks
The draft before it goes live
Two checks and one rule about what AI is allowed to touch.
Tools: ClearscopeSurferSEO
Check the page covers the topic before you publish
A semantic completeness check names the subtopics the draft skipped, while you can still add them.
Run the semantic completeness check before publishing, not after
Read the page structure with an on-page editor
An on-page editor counts hundreds of structural signals you would never check by hand.
- 500+ structural signals
Run the draft through an on-page editor that analyzes 500+ structural signals
Hand AI the production layer, not the voice layer
Transcription, subtitles and meta descriptions are machine work. Your opinions are not.
Use AI for transcription, subtitles, meta descriptions and social-post variants
Do not use AI to write the actual opinions or stories
Write pages an AI answer can quote a paragraph from
The answer engines lift the passage where a heading is followed by a straight answer. Put one under every heading and you become quotable.
Google AI Overviews and Perplexity answers
Both engines reward the same shape: a question in the heading, a definite answer right under it.
Put a definite answer under every H2 and H3
Two sentences, straight after the heading. That is the whole rule.
Follow every H2 and H3 with a clear 2-sentence answer
AI summarization models preferentially extract content where the header is followed by a definite answer
Wall-of-text content gets passed over
Treat weak AI Overviews impressions as a structure problem
When the answer engines keep skipping you, the shape of the page is the first thing to check, not the topic.
Content the Overviews rarely surface lacks the structural clarity AI needs
Optimize the headers for extraction before you rewrite the topic
Prove you are the same company everywhere on the web
One identity, declared in markup, pointing at the profiles that confirm it. That is what makes an AI tool credit the quote to you and not to whoever wrote about you.
JSON-LD on your own site
Markup on your About page is the anchor the rest of your entity hangs off.
Put Organization and Person schema on your About page
The About page is where you say who you are in a form a machine can read.
Add JSON-LD Organization and Person schema on your About page
Point sameAs at your LinkedIn, Wikidata, Crunchbase and X profiles
Give the crawlers one identity to credit
Matching links across the web tell a crawler that one company wrote all of it.
sameAs links tell AI training-data crawlers you are the same entity across the web
A verified, consistent entity raises the odds AI tools attribute citations to you specifically
Count how often you get quoted
Two checks a week. One reads your impressions inside Google. The other asks the answer engines what your buyers ask and counts how often your name comes back.
Google Search impressions
Google now reports AI Overviews impressions on their own line. Read that line every week.
Tools: Google Search Console
Run the Search Console check every week
One weekly pass over impressions, with AI Overviews split out from everything else. It costs nothing.
- < 5% of total search impressions
- top 10 keywords
Track impressions in AI Overviews on their own line, because Google now reports them separately
Flag it when AI Overviews impressions fall under 5% of total search impressions for your top 10 keywords
Search Console is free and official, so there is no excuse for skipping it
Perplexity, ChatGPT search and Google AI Overviews
Ask them what your buyers ask, then count whose page they quote back.
Search your top 10 queries on Friday and count the citations
Same queries, same engines, same day each week. Repetition is what turns it into a measurement.
- top 10 queries in your category
Search Perplexity, ChatGPT search and Google AI Overviews for the top 10 queries in your category
Count how many of those answers cite you
Run the check on Friday, every week
Read a citation rate under 30% as a content problem
When the answer engines quote everyone except you, the pages are the bottleneck, not the engines.
- below 30% across your top queries
Below 30% across your top queries means information gain is the bottleneck
Earn links instead of buying them
Two things you never do, and the one reason people link to you anyway. Original data, because a writer has to source the claim from somewhere.
Your backlink profile
Two rules about where your links come from, and both of them are about what you refuse to do.
Tools: Connectively
Do not buy links and do not trade links
Two flat rules, and the chapter does not hedge either one. Earn the link or go without it.
Don't buy links
Don't trade links
Earn the citation instead
Two routes are legitimate. Answer a journalist query, or publish the number somebody has to cite.
Respond to journalist queries to earn high-authority backlinks
Sources cite content with original data because they need to source their claims
PR & Brand Mentions
PR is no longer about links pointing at your site.
Chase the small set of outlets an AI actually weights, publish numbers nobody else has, and count citations instead of clippings.
The handful of outlets worth chasing
Outlets are not interchangeable. A few carry real weight, most carry none, and the way you tell is whether an AI repeats them back to your buyer.
The Tier-1 outlets
The New York Times, the Wall Street Journal, and TechCrunch when a real reporter writes the piece.
Spend your effort at the top of the weighting curve
AI systems do not read every outlet the same way. Point your effort where the weight already sits.
Accept that AI training corpora and retrieval indexes do not treat all outlets equally
Value one NYT or WSJ mention at roughly 100 second-tier blog backlinks
Put Wikipedia in a category of its own, above every news outlet
Trade a hundred small mentions for one Tier-1 quote
The math is lopsided enough that volume is the wrong goal. One good quote is the goal.
One quote in a Tier-1 outlet outperforms 100 mentions on second-tier blogs
Write your Tier-1 list as NYT, WSJ and TechCrunch, and stop there
Pitch the reporter who writes, not the desk that republishes
The same masthead runs two products. One is reported. The other reprints press releases and counts for nothing.
Count TechCrunch only when a real reporter writes the piece
Give the press-release republishing version zero credit
Second-tier industry blogs
The surface a PR firm will fill for you, and the one with the clearest record of doing nothing.
Skip the tier-2 blog run a PR firm will sell you
One founder bought this exact package. Here is what $15k returned.
A B2B SaaS founder spent $15k on a PR firm and got four mentions in three months
Not one of those four mentions changed the conversation in a sales call
TechCrunch had not moved a single deal, and the ChatGPT mentions were closing them
Point the same budget at citations instead of clippings
Same money, different mechanic. Four moves replaced the agency retainer.
Spend the next $15k of effort on a benchmark report, three Reddit AMAs, hand-pitched Connectively quotes and FAQ schema
Six months later ChatGPT named the company in 7 of his 10 priority buyer queries
The AI answer your buyer reads
ChatGPT, Perplexity and Google AI Overviews are where the mention now lands. Treat the answer as the placement.
Aim to be one of the 3–5 sources the AI names
The target is a named citation in the answer, not a link in a footer.
- 3–5 sources
- 10–100x
Set the goal as being one of the 3–5 sources an AI cites for your category
Fewer outlets matter than in 2015, and the ones that do weight 10–100x more
Stop counting links pointing at your site as the result
Count citations, not press hits
Swap the quarterly mention count for the only number a buyer ever sees.
Drop "how many publications mentioned us this quarter" as the metric
Measure how often your brand shows up when a real buyer asks an AI about your category
Run the audit weekly on your top 10 buyer queries
Ten questions, three engines, one count. Thirty minutes a week tells you whether any of the rest is working.
Write down the top 10 questions a buyer would actually ask in your category
Search each query in Perplexity, ChatGPT Search and Google AI Overviews
Count how many of the three engines cite you
Below 30% across your top queries means the structural work is not done
Above 50% means you are winning the citation layer
Put the weekly audit on the calendar so it survives a busy month
Buy a tracking tool only once you have the volume for it
The tools track dozens of queries at scale. Below that, your own hands beat them and cost nothing.
- $1M+ ARR
Semrush AI Search Toolkit and Profound earn their price at $1M+ ARR across dozens of priority queries
Before that, manual weekly checks give better resolution and cost nothing
Answer the questions reporters are already asking
Reporters post what they need and wait. Answering the right one is a shorter path to a Tier-1 quote than any cold email.
References: Marketing Examples: PR Guide (Harry Dry)
The reporter query feeds
Reporters post specific queries. You reply with expertise a reporter can quote and attribute.
Tools: ConnectivelyQwoted
Reply with something a reporter can quote and source
The reply is the quote. Write it finished, attributable, and about the question they asked.
Reporters post specific queries, so answer only the ones you can actually answer
Write the reply as quotable, source-able expertise
Connectively is the HARO successor, now owned by Cision, and the standard for journalist queries
Qwoted runs similar volume with a cleaner interface
Send five replies every 30 days
A cadence you can check. Either five went out in the last month or they did not.
- Five Connectively or Qwoted replies
- last 30 days
Have five Connectively or Qwoted replies sent in the last 30 days
Drop the press-release blast
The query platforms replaced that motion. Cold email to a reporter is the slow lane now.
Pitch journalists via Connectively or Qwoted, not via cold email
These platforms are the modern replacement for blasting press releases
Hand-pitched expert quotes through Connectively were part of the $15k that worked
The B2B and SaaS query pool
A narrower feed, aimed at B2B and SaaS publications. Less volume, better odds if that is your category.
Tools: Help a B2B Writer
Work the narrower B2B pool as well as the big feeds
If your buyer is a business, the queries here are closer to your category than the general feeds.
Help a B2B Writer carries queries focused on B2B and SaaS publications
A named reporter’s inbox
When no query matches, go direct. One reporter who covers your exact beat, not a list.
Tools: Muck Rack
Find the reporter who covers your exact beat
Direct outreach only works when the reporter already writes about your category.
Use Muck Rack to find specific journalists by beat for direct outreach
Publish a number nobody else has, so writers have to cite you
You already sit on data no reporter can get. Package it once a quarter and the citations come to you.
Your own anonymized customer data
The one dataset a competitor cannot copy and a reporter cannot reproduce without doing the work.
Publish one benchmark report a quarter
Real numbers, anonymized, with the method attached. Four a year is the cadence.
Ship one original benchmark report every quarter
Build it from real customer data, anonymized
Attach a methodology note to every report
One founder built a 30-page benchmark report out of his own anonymized customer data
Give writers something they cannot get without doing the work
Reporters cite original data because there is nothing else in the piece they can attribute.
References: Lenny's Newsletter benchmarksSaaS Capital benchmarksFirst Round Review's data pieces
Reporters cite original data because they have nothing else they can quote without doing the work themselves
Model the format on a report that already gets cited
Get the first report out the door
One clear finish line. Published, with the method note, or it is not done.
Count the first report done only when it is published with a methodology note
Make every machine agree on who you are
A model has to resolve your company to one entity before it can cite you. Wikipedia settles it. Conflicting profiles break it.
Your Wikipedia entry
One of the most heavily weighted sources in AI training corpora, and the signal does not decay.
Pass notability before you write a word
The sourcing comes first. Write the page before you have it and it gets deleted.
- ≥3 independent, quality references
Notability requires at least 3 independent, quality references
Stack three different kinds: a TechCrunch piece, a published benchmark, a Forbes profile
Call notability assessed once three independent quality references are identified or in progress
Never pay an agency to write the page
Paid writing breaks Wikipedia policy. The page comes down and you are back where you started.
Tools: UpworkWiki Specialist
Paid Wikipedia writing is against policy and they will revert your page
Hire someone with a verified edit history through Upwork or Wiki Specialist
Or write a stub yourself once your sourcing is in place
Bank on it because the signal lasts
Unlike a press hit, a Wikipedia entry keeps paying long after the news cycle ends.
Wikipedia is one of the most heavily weighted sources in AI training corpora
The signal is durable once the entry is live
Your LinkedIn, Crunchbase, X and GitHub profiles
Four public records of who you are. When they disagree, the model cannot decide which company you are.
Make every profile say the same thing, word for word
One afternoon of copy and paste. Skip it and every citation you earn points at a company the model is not sure exists.
Keep company name, founder bio, mission, headquarters and external links identical everywhere
Check LinkedIn, Crunchbase, X and GitHub against each other
Match the strings exactly, do not paraphrase
Conflicting data breaks entity resolution and the model cannot decide which company you are
Call the entity consistency audit complete only when every profile matches
Get quoted out of the threads the models read
ChatGPT and Perplexity lean hard on Reddit and Hacker News. What you leave in those threads becomes a citation later.
The subreddits your buyer reads
Not the big ones. The narrow ones where your buyer actually hangs out.
Be useful for three months before you mention your product
The waiting period is the price of admission. Mention the product early and the thread turns on you.
- 3 months
Be helpful for 3 months in subreddits where your buyer actually hangs out
Only mention your product after those three months are behind you
Run AMAs in your target vertical
An AMA leaves a long, quotable thread with your name attached to every answer.
Three Reddit AMAs in the target vertical were part of the $15k of effort that worked
Never buy upvotes
The cheapest way to end this whole branch in one weekend.
The platforms detect paid upvotes
Getting caught is a brand risk you cannot recover from quickly
Hacker News threads
The other community the models weight heavily. Same rules, shorter fuse.
Show up as yourself, not as a campaign
Authentic presence is the whole instruction. There is no growth hack version of this one.
Show up authentically in Reddit and Hacker News
Both are heavily weighted by ChatGPT and Perplexity for ranking and citations
The wire, and the one announcement that pays for it
Legacy distribution, still expensive, still the only route to a terminal. Buy it for the announcement that needs that pickup and for nothing else.
The newswire
PR Newswire and Business Wire push a release into terminals and syndication feeds. That is the whole product.
Skip the wire until the announcement needs terminal placement
The gate is terminal pickup, not importance. Most announcements do not clear it.
Tools: PR NewswireBusiness Wire
PR Newswire and Business Wire are legacy distribution, and expensive
Only a major announcement that needs terminal placement is worth the spend
Buy the all-in-one PR tool after you hire the comms person
Software with nobody to run it is a subscription. Hire first, then buy.
Tools: Prowly
Prowly bundles the PR workflow into one piece of software
It becomes useful once you have a dedicated comms hire
Borrow an audience someone else already earned
Find the shows and newsletters your buyer already trusts, then ask to give their audience something. Not to sell yours.
Podcasts your buyer already trusts
An hour on a show your buyer already listens to buys trust you cannot pay for.
Find the shows before you pitch anything
Research first. Pitching shows your buyer does not listen to is a slower way to get nothing.
Tools: SparkToro
Use SparkToro to find which podcasts your target audience already trusts
SparkToro tells you what your target customers read, watch and listen to
Pitch an appearance that gives their audience something
The host owes you nothing. Lead with what their listeners get.
Never send a "promote my product" pitch
Pitch only the shows your target audience already trusts
Newsletters your buyer already reads
Same motion as a podcast, in writing. One issue in front of a list that already trusts the writer.
Pitch a guest issue to the newsletters they trust
Find them the same way you found the shows, then make the same offer.
Tools: SparkToro
Email & Newsletter
A newsletter is the only audience asset you actually own.
Build a list you keep when the feed turns against you. Pick one platform and grind out the first 1,000 subscribers. Give away one thing worth an email address. Then watch opens and clicks, not the subscriber count.
Set the list up and get the first 1,000 people on it
Three real platforms, each strong at a different job. Pick on the job you want done, commit for a year, then grind through the first 1,000 subscribers.
Choosing one platform and staying on it
The wrong move is not the wrong platform. It is moving three times in year one.
Pick on the goal you actually want
Name the one job the newsletter has to do, then pick the platform that is strongest at that job.
- at least 12 months
Write down a one-sentence reason for the platform you picked
Commit to that platform for at least 12 months
Switching platforms three times in your first year is the real mistake, not picking the wrong one
Skip the legacy option
One of the four names you already know is not a real choice in 2026.
Don't start a newsletter on Mailchimp in 2026
The three current options replace it for newsletters and cost an order of magnitude less at scale
Growth and money tools built into the platform
One job: give you the growth and revenue machinery without a second vendor.
Tools: Beehiiv
Turn on the growth stack the platform already ships
You already pay for it. Switch it on before you go looking for another tool.
- 100% revenue retention
Cross-newsletter recommendations, a native referral system, paid subscriptions and an ad network all ship built in
Keep 100% of the revenue, with no platform cut
Choose this when growth and monetization are both priorities
Being found by other newsletters' readers
One job: put you in front of readers who already subscribe to someone like you.
Tools: Substack
Trade a cut of paid subs for discovery
Easier subscriber acquisition for a writer with a personal brand, at a price you should say out loud.
- 10% platform cut on paid subs
Pay a 10% platform cut on paid subscriptions
Accept less control over the list: export is allowed, but you sit inside their ecosystem
Choose this when getting discovered as a writer in that category is the value
Automatic magnet handoff and tagging
One job: hand over the magnet, tag the person, and start the sequence without you touching it.
Tools: Kit
Automate the magnet handoff and the tagging
Worth the setup time when the newsletter is one part of a bigger funnel.
Strongest automations, lead-magnet delivery sequences and granular tagging
Expect a higher learning curve than the other two
Choose this when the newsletter is one funnel inside a larger creator or SaaS product
Getting through the first 1,000 subscribers
The hardest stretch of the whole thing. Nothing compounds yet, so you do the three moves by hand and in order.
Run the three moves in priority order
Free and instant first. Manual and slow second. Paid last.
Plug into the cross-newsletter recommendation engine on day 1
Hand-recruit 5 to 10 newsletter swaps second
Run paid referrals third, at a quality cost per subscriber
Expect no help from anything until you clear 1,000
Every mechanism that makes newsletters grow needs a list you do not have yet.
- first 1,000
Recommendation networks barely surface you below 1,000 subscribers
Organic search has not kicked in and you have no referral flywheel yet
The first 1,000 buys you the right to start optimizing for the next 10,000
Turning a social following into subscribers
You rent the followers and you own the emails. Do the conversion math before you spend another year on the rented one.
Do the follower-to-email math before you spend another year
One founder ran this experiment for 14 months. The number is worth reading before you repeat it.
- 47k followers
- 0.3% converted to email
- ~140 subscribers
- 14 months
One founder spent 14 months building 47k Twitter followers and converted 0.3% of them to email, about 140 subscribers
An algorithm change can cut your reach 70% overnight, and your email list will not notice
Give away one thing worth an email address
One bar decides whether a magnet works: does it do something the reader could not easily build themselves? Pick the format after you clear the bar.
The bar a magnet has to clear
One test, run before you build anything.
Test the idea against one bar before you build it
No format saves a magnet that fails this test, so run the test first.
The magnet has to do something the reader could not easily build themselves
Decide the utility first and let the format follow
A template they fill in
An asset the reader opens on a real work day and types into.
Ship an asset they use, not one they read
The reader does the work in your template. That is the whole point of the format.
Build a hiring scorecard, an investor-update template or a project tracker
Action-oriented assets get used, not read
A prompt library for one job
A vetted set for one role or one workflow, not a dump of everything you saved.
Ship 15 to 30 prompts you have actually tested
A vetted set for one role beats a hundred prompts scraped off a thread.
- 15-30 vetted prompts
Cover one specific role or workflow, not everything
Vet all 15 to 30 prompts before they go in
A calculator or a spreadsheet
Math your reader does badly by hand, done properly once.
Give them a working model instead of an article
Burn, ICP fit, deliverability, runway. Build the one number your reader has to get right.
Build a burn rate calculator, an ICP scorecard, a deliverability score or a runway model
A short email course
A few days of email aimed at one outcome, sent automatically.
Run a 5-day course aimed at one transformation
Five sends, one thing the reader can do at the end that they could not do at the start.
- 5-day course
Build the sequence around one specific transformation
A PDF with real research behind it
The format is fine. What was missing in the ones you hate is the utility.
Ship a PDF only when it carries something new
Run the PDF through the same utility bar as everything else, then ship it without apologising for the format.
Ship a curated directory with research behind the picks, original benchmark data, or a condensed playbook of non-obvious tactics
Don't ship a 5-page repackaged blog post
Free PDF guides got a bad name because most of them had no utility, not because the format is broken
Get other newsletters to point at you
Two ways to borrow a list you did not build. One is a switch inside your platform. The other is ten emails you send by hand.
The platform's own recommendation network
A free switch that puts your newsletter in front of readers of newsletters like yours.
Turn recommendations on before your first issue
An hour of configuration, done on day 1, ahead of any writing.
Beehiiv calls them boosts and recommendations, Substack calls them Recommendations
Spend an hour configuring it before you write your first issue
It costs nothing to enable
It is the single biggest move for the first 1,000 subscribers
Reciprocal swaps with peer newsletters
You mention them, they mention you, and both lists meet someone worth reading.
Hand-recruit 5 to 10 swaps yourself
Nobody automates this part. You find the newsletters and you send the pitch.
- 10 newsletters
- your size or 1.5-3x bigger
- 3 consecutive issues
Find 10 newsletters serving the same ICP as you
Target newsletters at roughly your size or 1.5 to 3 times bigger
Pitch a reciprocal cross-promotion where each of you mentions the other in 3 consecutive issues
Write a real endorsement, not a generic plug
The endorsement is the whole trade. A lazy one converts ten times worse.
- ~5% of recipients
- <0.5%
Write one real paragraph, not "you should subscribe to my friend's newsletter"
Real endorsements convert about 5% of recipients, generic blasts under 0.5%
One strong swap beats five lazy ones
See what day-one recommendations plus 8 swaps produced
One founder ran recommendations, hand-recruited swaps and paid referrals together for three months. Here is what came out.
- 8 newsletter swaps
- 4,200 subscribers
- 38% open rate
- 12 newsletters cross-recommending
One founder plugged into the recommendation engine on day 1 and hand-recruited 8 swaps with peers in his vertical
Three months later he had 4,200 subscribers, a 38% open rate and 12 newsletters cross-recommending him
Land in the inbox and keep people reading
Two ways a list dies quietly. The mail stops reaching the inbox, or it reaches three different readers and speaks to none of them.
The domain your email is sent from
Get the DNS records and the from address right once, before anyone is on the list.
Align SPF, DKIM and DMARC before you launch
Nobody warns you when these are wrong. Gmail and Outlook just stop showing your email.
SPF, DKIM and DMARC have to align on your sending domain
When they do not align, Gmail and Outlook quietly drop you into promotions or spam
Send from your own domain, never a free mailbox
Every platform worth using supports a custom domain, so there is no excuse for a free address.
Never use a free Gmail or Yahoo address as your "from" address
Beehiiv, Substack and Kit all support custom domains, so use one
Testing where your email actually lands
Test placement before launch and after every DNS change
Two moments matter: the first send, and any time somebody touches DNS.
- $50 per test
Run a $50 inbox-placement test before launch and again after any DNS change
Check placement across Gmail, Outlook and Yahoo
Use Mailgun deliverability tools if your team runs its own sending infrastructure
Who the newsletter is written for
One reader, described in one sentence. Three readers means nobody.
Write to one ICP, not three
A concentrated audience forwards more, gets recommended more, and prices higher.
Describe your reader in one sentence: role, stage and one specific pain point
Readers forward to peers who match the ICP
Recommendations from newsletters serving the same ICP land harder
A concentrated audience raises your sponsorship pricing
Your weekly engagement check
Two numbers, read every week, with a threshold that tells you what to fix.
Judge the newsletter on opens and clicks, not the subscriber count
Each threshold points at a different fix: content, subject lines, or the CTA.
- open rate >35%
- open rate <25%
- click rate >3%
An open rate above 35% means the content is hitting
An open rate below 25% means weak subject lines or a stale list
A click rate above 3% means the CTAs are working
Fix the content before you add more subscribers
Growth on top of bad retention just makes the leak bigger.
- die at 5k
Below either threshold, fix the content before you add subscribers
Pouring more subscribers into a leaky bucket is how newsletters die at 5k
Subscriber growth without retention is a leaky bucket
Partnerships & Referrals
The cheapest, most-trusted growth channel is someone else's audience pre-recommending you.
Borrow trust you did not build. Map the overlap with companies your buyer already pays, pay a real commission to the few people who promote you, and build the invite into the product. Turn this on before paid, not after.
Sell through the people who already sold to your buyer
Someone your buyer already trusts can warm-introduce you. The work is finding which of your prospects are already their customers.
References: Nearbound.com playbooks
The tools your buyer already pays for
Before you pick a partner, write down the software already sitting next to you in your customer stack.
Write down 5 to 10 companies your buyer already uses
Their CRM, billing tool, analytics platform, comms tool and vertical software. Start from the category, not the brand name.
- 5-10 ecosystem partners
Pull the recurring names out of your top 10 customers' tech stacks, from Slack, BuiltWith, or by asking them
If you sell a CRM, start with their email tool, their calendar tool and their meeting tool
Keep direct competitors off the list
Narrow to 3 to 5 integration partners once you are scaling
Three to five integration partners is the working set once the scale gates are open.
- 3-5 integration partners
Look for tools whose customers already have the problem you solve
Pick three tools that share your ICP and do not compete with you
Check that this is your mechanic before you spend a quarter on it
Nearbound fits sales-led products with real deal sizes. A commission link fits self-serve.
Nearbound fits a sales-led or sales-assisted product at $5k+ ARR
Nearbound fits when a small group evaluates you and trust from existing vendors beats a 10% discount
Pick nearbound when your top-of-funnel pain is that you cannot get the meeting
Overlap between your prospect list and their customer list
The whole motion runs on one question: which of your prospects are already their customers?
Map the overlap with one partner before you formalise anything
Sync both CRMs and read the shared list. The overlap decides whether the partnership is worth structuring at all.
Sync both CRMs to see which of your prospects are their customers, and the other way round
Start on the free tier, which covers most early-stage use
Crossbeam and Reveal do the same job, so pick whichever your largest partner already runs
Swap CSVs when the software is overkill
The manual version. Two exports of customer domains, matched by hand.
Trade customer-domain exports and match the first 50 accounts by hand
Turn a mapped account into a warm introduction
Outbound cannot buy what a partner gives away for free, which is the buyer already believing the recommendation.
The first deal you close out of a partner intro is worth more than 100 cold emails
The one motion you put in front of a partner
Never open with a partnership. Open with a specific action and who does what.
Propose one concrete motion, not a partnership
One specific motion beats five vague ones.
Send 5 of their customers a teardown of their workflow with your tool inserted, and ask for intros into 5 of yours
Run a joint webinar on the shared problem, 3 emails from each list, then split the leads by ICP fit
Do not say "let us partner", say the specific action you will take first
Build a real integration, not a logo on a partner page
A logo on a partner page is not an integration, and it does not survive their next reorg.
Run a joint webinar or publish a co-branded report on top of the integration
Ask for warm intros into the accounts you mapped
Same product, same buyers, different mechanic. This is where the pipeline shows up.
Partner-sourced pipeline went from $0 to roughly $180k in two months
Integration pages on your own site
One page per partner. It captures buyer-intent traffic and gives the partner something concrete to link to.
Ship one page per partner at /integrations/[partner-slug]
A durable asset. It works for search, for the partner, and for the buyer comparing stacks.
References: Nearbound.com playbooks
Title it "How [Your Product] + [Partner] solve [specific buyer problem]"
The page doubles as an SEO asset for "[partner] integrations" queries
Give the partner a concrete URL to link to
Your CRM record of who introduced the deal
If you cannot say which partner sourced which deal, you cannot say which partner deserves more of your time.
Add a partner-influence field and fill it from day one
Partner-influenced ARR is the metric that proves the programme works, or proves it does not.
Attribute the revenue to the partner who made the warm intro or gave the context
Keep it binary, partner-sourced yes or no, below $1M ARR
Pay outsiders a cut when they bring you a customer
The link-and-commission motion. It ships in a week, and it goes nowhere unless you hand-recruit the people who promote it.
Your own programme, wired to your billing
A live programme is a week of work. The mistakes are a commission nobody would pitch, and treating the thing as passive.
Tools: RewardfulFirstPromoter
Check that a commission link is your mechanic before you build one
A 10% commission link generates one or two sign-ups a month for most B2B SaaS and rounds to zero on the P&L.
Affiliate fits a self-serve product under about $500 a month ACV with high sign-up volume
Affiliate fits when one person decides in under 2 weeks
Ship the programme in a week, and ship only this one first
Pick the platform that matches how you bill. Most early teams should get one mechanic working before starting the second.
Use Rewardful if you bill through Stripe or Paddle, and it is live in under an hour
Use FirstPromoter for multi-tier commissions or non-Stripe billing
Affiliate launches fastest, nearbound takes longer to set up and produces higher-quality pipeline once it runs
Set a commission somebody would actually pitch
Bake the commission into your unit economics before you publish it, not after the first payout run.
20 to 30% recurring is the standard floor for serious SaaS affiliates
10% lifetime is what founders set when they are testing whether anyone will work for free, and the answer is usually no
If a 25% recurring commission breaks your CAC payback, your CAC payback was already broken
Write the one outcome you want before you launch
If you cannot name the outcome in a single sentence, do not launch yet.
Write it as "3 deals a quarter sourced by partner X" or "200 affiliate trial sign-ups a month"
Put the 30/60/90 review on the calendar on launch day
A programme that limps for a year is worse than one you killed at day 90.
If the outcome metric is not hit by day 90, change the mechanic, the partners or the commission
Marketplaces where affiliates already shop for programmes
You are renting distribution to people who promote software for a living. It only pays at real scale.
Move onto a marketplace only when the scale justifies it
A marketplace puts your programme in front of affiliates who already pitch deals in your category. It does not replace recruiting.
Reditus exposes your programme to affiliates already pitching SaaS deals
Wait for $50k+ a month in MRR before you pay for managed onboarding
Impact.com, ShareASale and CJ Affiliate are overkill pre-Series A and carry high fraud-monitoring overhead
Creators and community leaders who already talk about your category
A programme nobody promotes makes 1 to 2 sales a month forever. The recruiting is the work.
Hand-recruit the first 5 affiliates by name
Pick 5 specific people, pitch each one by name, and onboard them yourself. Cold sign-ups from a public page rarely beat this.
- first 5 affiliates
Pick 5 creators, consultants or community leaders who already talk about your category
Offer a custom commission boost for their first 90 days and onboard each one in a 20-minute call
A programme nobody promotes generates 1 to 2 sales a month forever
Recruit for trust, not follower count
Niche experts with high trust, not accounts with high follower counts.
Recruit niche experts with high trust, not high follower counts
Track their revenue, not their reach
Find and check micro-influencers before you sign them
Discovery tools find, analyse and track the micro-influencers in your niche, so you are not guessing from a follower count.
Tools: ModashSocial CatAha.inc
Use a discovery tool to find, analyse and track the micro-influencers in your niche
Find 5 micro-influencers or industry experts in your niche and turn them into affiliates with a real revenue share
Search results and ads carrying your own brand name
Two guardrails stop an affiliate programme from charging you a commission on customers you already had.
Tools: BrandVerity
Set the clawback and ban brand-keyword bidding
Both guardrails go in before you open the programme to anyone you did not recruit yourself.
Run a 60-day clawback so you do not pay out on customers who churn in month 1
Stop affiliates bidding against you on your own brand keywords, and enforce it with a monitoring tool
Build the next customer into the product
The cheapest channel is the one your product creates for itself. Four mechanics exist. Pick one and build it properly.
Work your users send to people who have no account
A meeting link, a recording, a design frame. The artifact arrives in front of someone who has never heard of you.
Pick sharing when users already send work to non-users
One user sends a piece of work to a non-user, and that person meets the product for the first time.
Calendly meeting links, Loom videos and Figma frames all reach non-users
Shared workspaces and the network your users join
Two mechanics with the same shape. More people inside makes the product better.
Make the product worth more with a teammate in it
Slack, Notion and Linear all get better the moment a second person joins.
Pick collaboration when one user gets less out of the product than a pair does
Make each new user improve the product for everyone already in it
Marketplaces and social products are the two categories where this holds.
Marketplaces and social products get better for existing users with every new one
The invite prompt inside your product
Referral is the mechanic with an explicit reward attached to the invite.
Add an explicit incentive to invite
Dropbox and Airbnb both paid the user to bring the next user.
Dropbox and Airbnb are the reference cases for an explicit referral incentive
Pick exactly one mechanic and build it well
Sharing, collaboration, network effects or referral. One of the four.
Choose between sharing, collaboration, network effects and referral, then build that one well
Design a referral offer people will actually use
Ask at the right moment, reward both sides, pay out automatically. Get any one of those wrong and the loop stops.
The moment you ask
The request lands after the user has felt the product work.
Ask only after the user hits their first value milestone
Trigger the referral request on a real event in the product.
Trigger on a concrete event: they launched their first campaign, saved their first $100, or got 5-star feedback
The reward on both sides of the invite
People refer to raise their status, cut their cost or improve their workflow. Swag stopped working.
References: Growth.design: reward psychology
Reward the referrer and the referee, every time
A one-sided reward turns the referral into a sales pitch.
References: Airbnb's viral growth story
Always reward both the referrer and the referee, or only one side has a reason to act
Sell status, lower cost or a better workflow, not swag
The three reasons anyone forwards a product to somebody else.
People refer to increase status, lower cost or improve their workflow
Nobody refers a product for swag any more
Build the incentive stack in three layers
Physical rewards, digital utility and financial rewards, in one stack.
References: Dropbox: the 3900% growth loop
Physical rewards: branded swag and limited edition gear
Digital utility: store credits, feature unlocks and service upgrades
Financial rewards: cash back, discounts and affiliate commissions
Stack milestone tiers so there is a reason to keep going
Refer 3 people for one reward, refer 10 for a bigger one.
- refer 3
- refer 10
References: Morning Brew's referral school
Refer 3 people for the bonus guide, refer 10 for the physical hat
Match the incentive to who is buying
Give-to-get for consumer. Revenue share for B2B.
Give-to-get for consumer: give a friend $10, get $10 yourself
The link, the payout and the leaderboard
The plumbing. If any of it needs you in the loop, the engine is broken.
Automate the payout or the feature unlock
The reward has to land without you touching it.
If you have to send a gift card by hand, your referral engine is broken
Put the referral link within two clicks
A user should reach their referral link in under 2 clicks.
- under 2 clicks
Check that a user can find their referral link in under 2 clicks
Add fraud guardrails before you scale it
Minimum-usage rules are what stop bot farming.
References: Referral fraud teardown
Hold the reward until the referred user has been active for 30 days
Publish a leaderboard so status is part of the reward
A Founding Referrers circle gives people something to compete over.
Pick the referral plumbing that matches how you sell
Four business types, four different bits of plumbing. This family rewards your own customers. Paying an outsider a commission is the affiliate motion.
Newsletters and digital products
Milestone rewards, run against a list you already own.
Tools: SparkLoopReferralHero
Run milestone rewards on your own subscriber list
The ladder is the mechanic: a small reward early, a real one further up.
B2B SaaS billing through Stripe or Paddle
The reward lands as account credit rather than cash.
Tools: RewardfulFirstPromoter
Give account credits through your billing system
Integrate with the billing you already run so the reward is automatic.
Integrate directly with Stripe to offer account credits or affiliate payouts
Ecommerce and DTC stores
A next-order discount buys the new customer and the repeat purchase in one move.
Tools: ReferralCandyYotpo
Reward with a discount on the next order
One reward covers acquisition and retention at the same time.
Focus on next-order discounts to drive both acquisition and retention
Contests, waitlists and giveaways
Campaign-shaped loops, for when the referral sits around the product rather than in it.
Tools: UpViralViral Loops
Run a contest, a waitlist or a giveaway as the loop
These tools create viral contests, waitlists and giveaways.
References: Harry's pre-launch strategy
Prove the loop works before you pour money into it
One number decides whether you have a loop. Below 15% the invite is broken. Above 30% you have something worth funding.
The invite funnel in your product analytics
Invites sent and invites accepted, counted apart from general signups.
Track invite-conversion as its own metric
Invites accepted divided by invites sent. Lump it into general signups and you can no longer see the loop.
Track invites accepted over invites sent, and keep it out of the general signup number
Below 15% the invite UX is broken or the product is not worth recommending yet
Above 30% you have a real loop and should put fuel on it
Hold invite-conversion at 15% or better before you scale acquisition
The referrals you already get without a programme
If nobody refers you today, a programme will not change that.
Set up a referral programme only if the product fits
Check that people already recommend you before you pay them to.
A programme bolted onto a product nobody refers organically just leaks budget
Start with the first 100 users
Reward the first 100 users for inviting peers, then read what happened.
- first 100 users
Reward your first 100 users for inviting peers
Paid Ads
Don't run 5 channels at 20% effort.
Put 80% of the money into one channel and kill the bottom creative every Friday. Turn this on after retention and the unit economics are green, not before.
Budget and channel choice
Decide where the money goes before you decide what the ads say.
Channel choice
One channel, chosen by where your buyer already is.
Pick the one channel that fits your ICP
Google Search if your buyers search for your category. Meta if they scroll. LinkedIn if they are a title you can target. TikTok if they are under 30.
- 80% of budget in one channel until it works
Put 80% of the budget in one channel until it works
Running 5 channels at 20% effort each is how startups stall
Turn paid on only after the gates are green
Paid amplifies what is already there, including the broken parts.
Confirm annual churn is below 10% B2B or 25% consumer first
Confirm LTV:CAC is at least 3 to 1 with payback under 6 months B2B or 12 B2C
Test and scale budgets
Two pots. One proves a thing works, the other pours money into what already did.
Scale winners 15% every 48 hours
Raise budget in steps the algorithm can absorb. Doubling overnight resets learning.
- +15% every 48 hours
- never double overnight
Never double the budget overnight
30-day spend cap
Spend only what you can afford to lose on the first 30 days, and only once organic already works.
Cap the first 30 days at what you can afford to lose
You are buying data in the first 30 days, not conversions.
References: Google Ads Onboarding
Layer paid in only once organic is already working
Cap the first 30 days of spend at what you are comfortable losing entirely
Treat the data as the deliverable, not the conversions
Paid Search
Buy the queries where someone is already looking for what you sell.
Google Ads bidding
Bid on profit, not on clicks.
Tools: Optmyzr
Bid on profit margin, not just revenue
Feed real margin back into Google's Value-Based Bidding signal so the algorithm chases profit instead of volume.
Send margin, not revenue, as the conversion value
Scale budget 15% once you have 30 conversions
Raise budget 15% only once the account has real conversion volume behind it.
- +15% budget
- after 30 conversions in a 30-day window
Scale budget by 15% only after 30 conversions in 30 days
Google Ads campaign structure
One account, three jobs: protect the brand, capture intent, then expand discovery.
Give your ad account three separate jobs
Split the account into three jobs instead of one big undifferentiated campaign.
Layer 1 is exact-match brand protection, Layer 2 is broad-match intent capture with tCPA, Layer 3 is Performance Max discovery expansion
Feed Performance Max explicit Search Themes and a Customer Match List to bias it toward your ICP
Clean up your account before you scale
The setup mistakes that quietly tax every dollar you spend.
Verify you are running Expert Mode, not Smart Campaigns or Express Mode
Never launch without 4 sitelinks
Refresh Performance Max video assets every 30 days
Google Ads creative and copy
Write for the question your buyer is asking, then back it with images built for a visual results page.
Write ads around the problem, not the keyword
Structure copy around the problem your buyer is trying to solve, not the bare keyword.
Structure ad copy and landing pages around "How do I solve [problem]?" instead of just the keyword
Aim to win the snippet in Google AI Overviews and the citation in SearchGPT
Build an image library for your search ads
Search results are visual now. One stock image is not an asset library.
Upload a library of high-fidelity 1:1 and 4:5 images for your Search ads
Use AI to generate aesthetic-shock visuals that stand out in a text-heavy results page
Waste control
Block the traffic that was never going to buy before it eats the budget.
Tools: ClickCease
Block bots and scrapers from wasting your budget
Every dollar a bot or a scraper eats is a dollar that never had a shot at a customer.
Use IP-blocking tools or scripts to filter out LLM-scraper traffic
Keep the Negative Placement List current, and exclude mobile gaming apps and Made for Ads sites
Competitor and account intelligence
See what a competitor already paid to learn before you pay to learn it again.
Pull competitor keyword and ad-test history
A competitor already ran the experiment. Read the results instead of repeating them.
See every keyword a competitor has bought, every ad test they have run, and their organic rank history
Download the competitor scripts and landing pages that are already making money
Check search volume and CPC estimates before you commit budget
Automate the busywork, then audit Quality Score
Small budgets do not have room for manual account admin every week.
Run Quality Score audits that point at the fixes bringing click costs down
Run the 20-minute work week routine on smaller budgets
Paid Social
Feed the algorithm a real creative signal on Meta, TikTok and LinkedIn. Then treat the spend as one budget.
Meta
Give Meta clean signal and broad targeting room, then split the budget into a proof pot and a scale pot.
Send conversions from your server, not just the browser
The browser pixel alone is not enough signal anymore.
Implement Meta's Conversions API server-side, not just the browser pixel
Send hashed emails and purchase events straight from your server
Split your Meta budget into test and scale
Broad targeting beats manual audience layering once the creative earns it.
Run 20% of budget as a broad-targeting sandbox for rapid creative testing
Kill anything that misses target CPC or CPA within 72 hours
Move winners into an Advantage+ Shopping campaign holding the other 80%
TikTok
Study what already works natively before you post anything that looks like a company ad.
Tools: TikTok Creative Center
Study native hooks before you post company-style ads
The hooks working today are already sitting in the platform, free to study.
Browse the top-performing TikTok ads in your niche to see the native hooks working today
LinkedIn Ads
Target the job title that buys, once organic already proves the offer works.
Tools: LinkedIn Campaign Manager
Layer in LinkedIn ads once organic is already working
High-intent paid comes after organic proves the offer, not before.
Target by job title for B2B buyers
Launch your first test from the free LinkedIn Campaign Manager getting-started guide
One budget across platforms
Treat Meta, TikTok and X as one budget, not three separate bets.
Manage Meta, TikTok and X as one budget bucket
Move the money toward whichever platform is winning this week.
Reallocate spend daily toward the platform showing the best 7-day blended MER
Judge spend by total revenue, not per-platform ROAS
Platform-reported ROAS flatters you. MER, total revenue over total spend, does not.
Calculate total revenue over total ad spend as the one number that matters
Creative Testing
The gain sits in the creative, not the landing page. Test it like the budget depends on it, because it does.
Weekly test cycle
Most founders test landing pages because the tools make that easy. Test the creative instead.
Test creative, not landing pages
Landing page tests are the easy test to run. Creative is where the real gain sits.
Test 5 or more variants per week of headline and opening hook
Kill the bottom 3 every Friday
Making ad variants
AI makes testing 50 versions cost about the same as testing one.
Generate 20+ variations of your best hook
One hook, twenty tries, three archetypes.
- 20+ variations per angle
- test 50 videos for the cost of 1
Use AI to test 50 videos for the cost of 1
Test three archetypes: scientific proof charts, social mimicry UGC, and aesthetic-shock high-contrast visuals
Competitor creative research
Someone else already spent the money finding out what works. Go look.
Tools: ForeplayMeta Ad Library
Build a moodboard from ads already working
A competitor ad still running after a month is not luck. It is a winner.
Treat ads that have run for more than 30 days as the winners, because they are the ones making money
Save winning competitor hooks into one moodboard as you find them
Creative analytics
Know which part of the ad is winning before you scale it.
Tools: MotionApp
Break performance down by hook, body and CTA
Stop guessing at why an ad works and go find out.
See exactly which part, the hook, the body or the CTA, is driving your conversion rate
Ads from creator accounts
Run the ad from the creator, not the company. The trust transfers and the performance follows.
Meta Partnership Ads
The reader sees a recommendation from someone they trust, not an ad from a company.
Run the ad from the creator's handle
A reader trusts a recommendation from a person more than the same ad run from a company page.
- 2-3x cold-brand creative in most tests
References: Meta Partnership Ads
Run Partnership Ads so the ad posts under the creator's handle, not yours
Expect native creator ads to perform 2 to 3 times better than cold-brand creative in most tests
TikTok Spark Ads
Boost a post that is already earning trust under the creator's own name.
Boost the creator's own post so it stays in their name
The post keeps the creator's byline. Only the reach changes.
References: TikTok Spark Ads
Run Spark Ads so the post stays under the creator's own handle
LinkedIn Thought Leader Ads
Put budget behind a person's post, not the company page.
Promote a person's post, not the company page
A founder or an employee already has the credibility. Borrow it instead of building a new one from a logo.
Put budget behind a founder or employee post so the trust stays with the human
Paid Newsletter Referrals
Pay a bounty per qualified subscriber and cap it at what that subscriber is worth.
Paid subscriber referrals
A price per subscriber, paid through a network that already vets its newsletters.
Tools: SparkLoopBeehiiv Boosts
Pay per qualified subscriber from newsletters you vet
Price the bounty from what a subscriber is worth to you, not from a guess.
- $5-20 per qualified subscriber
- ~30% of lifetime value
Pay $5 to $20 per qualified subscriber from quality newsletters
Cap the price at about 30% of lifetime value, counting sponsorship revenue, product conversion and cross-sells
Point to a real bounty run as proof the mechanic works
One newsletter already ran this exact play and has the subscriber count to show for it.
- $15 per sub bounty for 60 days
- 4,200 subscribers in three months
One $15-per-sub bounty run for 60 days grew a list from a few hundred subscribers to 4,200 in three months
Pick one paid referral engine, not both
Running both splits the spend and muddies which one is actually working.
Run SparkLoop or Beehiiv Boosts, not both at the same time
Sponsorships and Placements
Buy a slot in someone else's newsletter instead of building your own campaign from zero.
Newsletter ad buying
A marketplace already lines up the newsletters. You just pick the placement.
Tools: PavedPassionFruit
Buy sponsorship slots through a newsletter marketplace
The marketplace already screened the newsletters. You are picking a placement, not cold-emailing a publisher.
- 5,000+ subscribers
Browse Paved, where listed newsletters start at 5,000 or more subscribers
Run the buy through PassionFruit instead
PassionFruit manages the ad inventory itself, or lines you up with a growth expert who already knows the space.
Use PassionFruit to manage ad inventory or match with a newsletter growth expert