DEV Community

Cover image for 1 week post-launch: 25 signups, 0 sales. Here's what I got wrong and what I'm changing
Elvin Chauvel
Elvin Chauvel

Posted on

1 week post-launch: 25 signups, 0 sales. Here's what I got wrong and what I'm changing

I launched Vicket last week a white-label customer support system for SaaS developers. Here's the honest debrief.

The product: Embeddable support components (React, Vue, Svelte) installable inside your app to get automated workflows, ticket scoring, knowledge base, team-based visibility scopes. Think Intercom but built to live inside your product, not alongside it.

The numbers:

  • 6 months of building
  • €90 in costs (mostly infra)
  • ProductHunt launch ✓
  • Posts on LinkedIn, Reddit, Twitter ✓
  • 25 signups
  • 0 paying customers

What I got wrong:

  1. I posted to everyone instead of talking to anyone. 25k views on LinkedIn but zero calls, zero DMs, zero conversations. Broadcast ≠ sales.
  2. My social proof was friends and students. If you're selling to founders and developers, testimonials from CS students don't move the needle.
  3. My hero copy talked about features, not the problem. "White-label customer support platform" cool, but so what?

What I'm changing this week:

  • Rewriting the landing page around the actual pain (embedding support without losing your brand or your budget)
  • Emailing my 25 signups personally to understand why they haven't upgraded
  • Doing 1-to-1 outreach to indie SaaS founders instead of broadcasting

If you've built something and navigated the 0→1 sales phase, I'd genuinely love to know what worked. And if you've ever struggled with integrating customer support into your product, I'd love to hear that pain it's literally what I built this for.

https://vicket.app

Top comments (8)

Collapse
 
universetwisters profile image
Jeroen Boers

Hey Elvin,

I have experienced the exact same thing half a year ago. I built your exact product (embeddable support) at instasupport.io and i made it all free.

What i found out is that it's an impossible market to get into, because there's already many great free ways of doing this. The smaller companies use email and are absolutely fine managing support that way, and the bigger companies have super affordable alternatives.

So really make sure there is actually customer pain that you are solving. I have changed into building different products now, but have learned alot from the experience. I think it's important to actually ask if people need your product at all.

Collapse
 
elvin_chauvel profile image
Elvin Chauvel

Totally fair take and honestly I think your conclusion makes sense from what you tested. But I don’t think it generalizes to the whole space.

What you’re describing is true if you position it as "just another support tool."
Then yeah:

small companies : stick to email
bigger ones : already locked into tools

That market is saturated.

Where I see it differently is this:

The problem isn’t handling support.
The problem is support inside the product vs outside the product.

Email "works", but it creates:

  • context switching
  • slower resolution
  • lower perceived product quality

And most tools (Zendesk, Intercom, etc.) are still:

  • external
  • expensive at scale
  • not truly white-label

So the angle isn’t competing on features or price it’s:

Making support feel like a native part of the SaaS

Collapse
 
universetwisters profile image
Jeroen Boers • Edited

It was free, completely without branding and fully whitelabel, and fully embeddable through a widget. Yet nobody was interested. A pretty clear signal that there's no market

Collapse
 
apex_stack profile image
Apex Stack

The "broadcast ≠ sales" lesson hits close to home. I sell digital products (AI automation skills on Gumroad) and made the exact same mistake — published 9 articles across Dev.to, Medium, and Hashnode with CTAs to my store, got decent readership, but zero conversions to actual purchases. Thousands of impressions, zero store visits that converted.

What I'm realizing is that content marketing for awareness and content marketing for conversion are completely different disciplines. The articles that got the most engagement were the ones where I shared real numbers and struggles (like this post) — but those readers are fellow builders who empathize, not necessarily buyers. The people who would actually pay for my tools are searching for specific solutions on Google, not browsing Dev.to.

Your plan to email the 25 signups personally is the highest-leverage move on your list. Those people already raised their hand — they just need a reason to pull out their wallet. When I started doing direct outreach instead of broadcasting, the quality of feedback improved dramatically even if the volume was tiny. One real conversation with a potential customer teaches you more than 25K LinkedIn impressions.

Curious what your signup-to-active-use ratio looks like — are people creating accounts and then bouncing, or are they actually trying the product before deciding not to pay?

Collapse
 
itskondrat profile image
Mykola Kondratiuk

the signups-to-sales gap is brutal and I think most people underestimate how much it hurts emotionally. 25 people showed enough interest to sign up - that's actually not nothing. in my experience the gap usually means either the pricing page isn't doing its job or you're attracting the wrong signups to begin with. curious what the conversion funnel looks like - are they activating and then not converting, or dropping off before they even see the value?

Collapse
 
bhoogle profile image
Prasanna

This really hit a nerve! Same situation here.

Broadcast is not sales, but for a consumer product like mine (a health support companion with long term memory, nursechapel.com) which most people only feel the need for when they are ill and treat as a toy otherwise.. I think the problem is with user discovery. Will folks taking care of chronic patients use it? will fitness enthusiasts use it?

and broadcast might help with discovery... or so I thought.

Collapse
 
justin_credible profile image
Justin • Edited

"White label" means different things to different people, so it helps to get clear on who you're actually targeting. Agencies want branded client-facing tools. Tech integrators want API access and flexibility. Enterprise customers often want full code access and self-hosting options. Each customer profile has a different definition of what white label means to them, and the benefit needs to be spelled out specifically for each, because the term on its own has become a bit of a fluff.

One practical thing worth looking at: your help center and documentation don't seem to have dedicated white label sections. Those pages tend to rank faster than your homepage when someone is actively searching for white label solutions.

I don't think you're doing anything fundamentally wrong. Customers rarely buy on first contact, and what you're really doing right now is building a digital footprint and establishing trust over time.

Worth following Gleap as a reference point. They made plenty of mistakes early on, took unconventional paths, but stayed consistent and it's paying off. This space rewards persistence and learning.

Some comments may only be visible to logged-in visitors. Sign in to view all comments.