I Ran a Pre-Launch Landing Page for 30 Days — Here Is What the Signup Numbers Actually Meant

A one-page site, an email capture form, and thirty days of driving whatever traffic I could to it — the pre-launch landing page test is common advice for validating demand before writing code, and the part nobody explains well is what to actually do with the resulting number. 4.2% conversion sounds like a real, meaningful signal on its own. Breaking it down by where each signup actually came from told a very different, more useful story than the headline number did.

The page and the offer, briefly

The product idea: a tool for freelance consultants to auto-generate scope-of-work documents from a short intake questionnaire, reducing the time spent writing custom SOWs for each new client. The landing page had one headline, three bullet points explaining the value, and an email capture form with the promise of early access and a launch discount. Nothing elaborate — the whole point was testing demand cheaply before investing real build time.

The headline number: 4.2% conversion, 3,140 visitors, 132 signups

On its own, this number is nearly meaningless without more context — 4.2% could be a great result or a mediocre one depending entirely on where that traffic came from and how qualified it actually was, a distinction the aggregate number completely flattens. This is the mistake I nearly made: treating 4.2% as the finding, when the finding was actually buried one level deeper.

Breaking it down by traffic source

Source              Visitors   Signups   Conversion
Reddit (r/freelance)   890        61        6.9%
Cold LinkedIn DMs      340        34        10.0%
Twitter/X posts        1,240       21        1.7%
Google ads (branded)    670        16        2.4%

Four sources, four wildly different conversion rates, and — critically — four very different levels of how qualified that traffic actually was for the specific product being tested. The aggregate 4.2% averaged across all of this hides more than it reveals.

Why the highest-converting channel was almost misleading

Cold LinkedIn DMs converted at 10%, the best rate of any channel — and reading the actual signup list against who I'd messaged revealed a problem: I'd hand-picked people who were already freelance consultants doing exactly the kind of scope-of-work writing this tool targets, then messaged them personally and specifically about the exact pain point. That's an extremely favorable, hand-selected sample, not a representative signal of broader market demand — a 10% conversion rate from a warm, personally-curated audience of 340 people tells you almost nothing about whether a stranger encountering the page cold would convert anywhere near that rate. It's a real signal, just a much narrower one than the headline number implied: "people who are definitely in the target audience and already know me personally are interested," not "there's broad market demand for this."

Why the lowest-converting channel was actually the most informative

Twitter/X posts converted at only 1.7% — the worst rate — and this is the number that actually mattered most, because that traffic was the closest to a genuinely cold, unfiltered audience: people who saw a post in their feed with zero prior relationship or targeting, similar to what real organic discovery would eventually look like once the product actually launched. A 1.7% conversion rate from genuinely cold traffic is a far more honest baseline for "how interesting is this to a stranger" than the flattering LinkedIn number, and it's the number I should have weighted most heavily in deciding whether to actually build this, rather than anchoring on the more impressive-looking 10% from a curated audience.

The Reddit number, and why it needed its own separate read

Reddit's 6.9% sat in between, and its own context mattered just as much as the other two: r/freelance is a community of people who are, by definition, already freelancers — a genuinely relevant, if self-selected, audience, but a specific, product-adjacent forum, not a broad market. High engagement here says "people already thinking about freelance-specific problems find this interesting," which is a real, useful signal, but a narrower one than it might look like at a glance — it doesn't tell you much about whether a much larger addressable market beyond that specific subreddit's audience would respond the same way.

The actual decision this data supported

Weighing the cold-traffic Twitter number most heavily, alongside the narrower-but-real Reddit signal, and treating the LinkedIn number as a strong "people who already fit the target profile are interested" data point rather than a broad-market signal — the overall read was: real interest exists within the specific target audience (freelance consultants who write SOWs regularly), but broad, unfiltered appeal is unproven and likely much lower than the headline 4.2% suggests. That's a meaningfully different, more honest conclusion than "4.2% conversion, this is clearly validated, time to build," and it directly shaped the decision to build a narrower, more targeted MVP aimed specifically at the freelance-consultant niche rather than a broader "anyone who writes proposals" positioning the original landing page copy had loosely gestured toward.

Tracking each source cleanly, which the breakdown above depended on entirely

None of this per-source analysis would have been possible without distinct, trackable links for every channel from the start — a single shared landing page URL posted everywhere would have made this entire breakdown impossible to reconstruct after the fact. Every channel got its own short link, created through our own URL shortener, specifically so click and conversion data could be attributed cleanly per source rather than lumped into one undifferentiated number:

reddit post:     yoursite.com/s/r-freelance
linkedin dms:    yoursite.com/s/li-dm
twitter posts:   yoursite.com/s/tw-post
google ads:      yoursite.com/s/ga-brand

This is worth setting up before the first visitor ever arrives, not added retroactively once you're already curious which channel is working — by the time you're curious enough to want the breakdown, the early traffic that would have been most useful to analyze has usually already come and gone unattributed.

What the actual email replies added beyond the signup number

Thirty-one of the 132 signups replied to the automated confirmation email with an unprompted comment of their own — not requested, not incentivized, just people who felt strongly enough to add a sentence or two. Reading through those specifically added a layer the raw conversion numbers couldn't provide on their own: several replies described a specific, recent frustration with writing a scope-of-work document by hand, in enough concrete detail that it read as a genuine, lived pain point rather than a polite "sounds useful" reaction. A handful of others, by contrast, seemed to have signed up more out of general curiosity about a new tool than any specific problem they were currently facing — a distinction the signup count alone can't make, but the actual words in a reply frequently can.

This qualitative layer mattered most for interpreting the Reddit and Twitter numbers specifically, since the LinkedIn signups had already been pre-qualified through the personal messaging itself. A handful of the Twitter replies in particular described the exact SOW-writing pain point unprompted, which meaningfully increased confidence in that channel's low-but-cold 1.7% number — it wasn't just "some strangers clicked a button," a few of them arrived already carrying the specific problem this product was built to solve, described in their own words before ever being asked.

Deciding how long to run the test before acting on it

Thirty days was a somewhat arbitrary choice going in, not a number derived from any statistical power calculation — and in hindsight, the choice mattered because traffic and signups weren't evenly distributed across the month. A single viral-ish Reddit post in the first week accounted for a disproportionate share of the entire month's Reddit traffic, meaning a shorter test window that happened to miss that specific post, or a longer one that diluted its outsized effect further, could plausibly have told a meaningfully different story about that channel specifically. Running a test for a fixed calendar period rather than a fixed traffic volume introduces exactly this kind of luck-dependent variance, worth naming honestly rather than presenting the resulting numbers as more stable and cleanly reproducible than a single 30-day test window actually can genuinely guarantee on its own, no matter how carefully the rest of the test itself was actually run.

What I'd do differently on the next one

• Weight cold, unfiltered traffic more heavily than warm, curated traffic when deciding whether real signal exists — a hand-picked audience's enthusiasm is real but tells you about that specific audience, not the broader market you'll eventually need to reach.
• Set up per-channel tracking before driving any traffic at all, not after noticing the aggregate number looks interesting and wanting to understand it better.
• Treat a single 30-day window as one data point, not a final verdict. A different 30 days, with different specific posts and different luck in what happened to catch attention, could plausibly show meaningfully different numbers — one clean test is a reasonable start, not proof on its own.
• Ask what each channel's number actually implies about the audience it reached, not just whether the percentage looks good — the same headline conversion rate can mean genuinely different things depending on how qualified and how cold the underlying traffic actually was.

The number that gets shared in most "I validated my idea with a landing page" success stories is almost always the flattering aggregate, rarely the honest cold-traffic baseline sitting underneath it — worth remembering both when running your own test and when reading someone else's results before deciding whether your own idea is similarly promising, or whether the headline number just successfully hid the same complexity mine did.

This same per-source attribution discipline turned out to matter again after launch, in a completely different context — breaking down which free tool actually drove paying customers, not just traffic, covered in building a free tool as a lead magnet, relies on exactly the same tagged-link method this landing page test depended on to make its own breakdown possible in the first place.