Feb 26, 2026
Client: an early-stage GTM data and automation platform (table-based enrichment and outbound workflows)
Channels: Reddit, cold email, LinkedIn
Result: 1,000 prepaid subscriptions at a founding-member discount, with no finished product
The situation
Our client had a strong idea and an unfinished product: a table-based GTM automation platform, built as a more affordable alternative to Clay.com. The core was there, but the product was not ready for a public launch, and there was no audience, no waitlist, and no brand.
The usual advice is to build more, launch on Product Hunt, and hope. We went the other direction: sell the outcome before the product exists, and let the money tell us who really wants it.
Prepaid subscriptions are the hardest validation there is. A waitlist signup costs nothing, but a credit card is a vote.
Step 1: Find the ICP by looking for pain, not job titles
Most agencies build an ICP from firmographics: company size, industry, title. We started with a complaint instead.
We spent the first week reading, not writing. We went through Reddit threads, LinkedIn comments, and community posts where GTM people talk honestly. Two patterns kept coming up:
"I'm overpaying for Clay." Credit burn, unpredictable costs, and pricing that punishes experimentation. Agencies and solo operators were the loudest.
"Other automation tools don't have tables." People using Zapier, Make, and similar tools for outbound felt they were duct-taping workflows. Without a real table layer to see, filter, enrich, and re-run data row by row, they had no control.
That gave us a precise ICP:
GTM operators, agency owners, and technical founders who already run outbound, already pay for tooling, and are frustrated by cost or lack of table-based control.
Why this ICP worked:
They already spend money. Nobody had to be convinced the category matters.
The pain was already articulated. We copied their language into our messaging instead of inventing our own.
They talk to each other. One happy operator brings in three more.
They can judge a product by a demo. No long enterprise cycle.
We deliberately excluded people with no outbound motion, "curious" founders, and anyone who had never paid for an enrichment tool. Narrow beat broad.
Step 2: Build the offer around education, not a pitch
With no product to demo, we couldn't lead with features. So we led with value that works without the product: playbooks.
Instead of "join our waitlist," the offer was:
Get free GTM playbooks. Join a private community where we share the exact plays that work. Get founding-member pricing if you decide you want the tool.
The playbooks covered things like:
Building lead tables from scratch with no expensive credits
Enrichment waterfalls that cut cost per lead
Signal-based outbound plays (hiring, funding, tech stack changes)
Reply-rate improvements for cold email sequences
Each one was practical enough to use that day. That did two things: it proved we knew the space, and it put our name next to results before we asked for a cent.
Step 3: Outreach on three channels, one message
Reddit: earn trust first
Reddit punishes promotion, so we didn't promote. We answered real questions in GTM and cold email communities with detailed, useful replies, and shared playbook excerpts where they fit the thread. When people asked how we did something, we pointed them to the full playbook and the community. Slower than ads, but the people who arrived were warm and self-selected.
Cold email: pain-first, short, specific
We built lists of agency owners, RevOps leads, and founders who showed signals of running outbound (job posts, tech stack, public content). Emails were short, with no product pitch:
One line referencing their likely pain (tool costs, workflow limits)
One line offering a specific playbook
A soft CTA: "Want me to send it over?"
The offer was a free asset, not a meeting, which made replying easy.
LinkedIn: authority and conversation
We posted playbook breakdowns on the founder's profile and ran light, personalized DMs to people who engaged. Comments became conversations, and conversations became Slack invites.
Every channel drove to the same place: the playbook, then the private Slack channel.
Step 4: The private Slack channel as the conversion engine
The Slack community was the center of the whole plan. It gave us:
A place to teach. We dropped plays, templates, and teardowns daily.
Live feedback. Members told us what they needed, which shaped the product roadmap.
Social proof. People saw others getting value and asking the same questions.
Trust. By the time the offer came, they'd been learning from us for days.
We kept it high-signal: no spam, no hype, real tactical content, and fast replies from the team. People joined for playbooks and stayed because the channel was useful.
Step 5: The one-week conversion window
Rather than dripping an offer out for months, we ran a compressed conversion week with a clear structure:
Days 1–2: Teach. Deliver the highest-value plays and show the problem clearly (what you're really paying for with existing tools).
Days 3–4: Show the solution. Walk through the product vision, the table-based approach, and real workflows it would replace.
Days 5–6: Make the offer. Founding-member pricing, a big discount for prepaying, locked in for early supporters.
Day 7: Close. A clear deadline and a final reminder.
The discount was real and the deadline was honest. Early buyers got a meaningfully better price for taking a risk on an unfinished product, which is a fair trade.
Step 6: Handling objections
Selling an unfinished product means objections are predictable. We prepared for each one and answered it openly.
"The product isn't finished. Why should I pay now?"
Because you're buying at a founding price, shaping the roadmap, and getting priority access. We were upfront about what was built and what wasn't, and showed the timeline.
"What if it never ships?"
We addressed this directly with a transparent roadmap, regular build updates in Slack, and a clear refund policy for anyone unhappy. Removing the risk of loss made the decision much easier.
"I'm happy with Clay / my current stack."
We didn't argue. We asked what they spend monthly and what they wish worked differently. Often the honest numbers made the case themselves.
"Will it actually replace my current tools?"
We were honest about overlap and gaps. Not overselling built more trust than any feature list.
"I'll wait until it's launched."
We explained that the founding price would not return, and that waiting meant paying more later without influencing what got built.
Honesty did most of the work. In a community where people could see our updates daily, bluffing would have been obvious.
Step 7: Results
1,000 prepaid subscriptions before the product was complete
A validated ICP with real buying behavior behind it
A paid, engaged community that now acts as a feedback loop, a source of testimonials, and a distribution channel
Cash in hand to fund development, without outside capital
A repeatable playbook for launching B2B SaaS without a finished product
What made it work
ICP from pain, not demographics. We found people already complaining about the problem.
Education before the pitch. Playbooks proved value without the product.
One conversion path across channels. Reddit, email, and LinkedIn all led to the Slack community.
A community as a trust engine. People buy from those they've learned from.
A compressed, honest offer window. Real discount, real deadline, no tricks.
Radical transparency on objections. Admitting what wasn't built yet made the offer more credible, not less.
The takeaway
You don't need a finished product to sell. You need a sharply defined buyer, a problem they already feel, and enough trust that they'll back you before the demo exists. Teach first, build community, then make a fair offer.
That's how we turned an unfinished product into 1,000 paying customers.