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

Elvin Chauvel — Sat, 21 Mar 2026 23:35:41 +0000

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:

I posted to everyone instead of talking to anyone. 25k views on LinkedIn but zero calls, zero DMs, zero conversations. Broadcast ≠ sales.
My social proof was friends and students. If you're selling to founders and developers, testimonials from CS students don't move the needle.
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

I spent 6 months building a white-label customer support platform for SaaS founders

Elvin Chauvel — Mon, 16 Mar 2026 03:23:05 +0000

Over the past 6 months I’ve been building a SaaS product called Vicket.

The idea came from a frustration I kept running into while launching side projects.

Every time I needed to add customer support to a product, it felt unnecessarily complicated.

Most support platforms fall into one of these categories:

expensive tools built for large companies
products that force their own branding
external helpdesks that move users outside your product
complicated integrations

As a developer, it felt strange that adding a support system to a SaaS product wasn’t easier.

So I decided to try building my own.

The idea

The goal was simple:

Allow developers to embed a fully branded support system directly into their product.

Instead of sending users to an external portal, support could live directly inside the application.

That meant building:

a ticketing system
customizable ticket forms
automation workflows
a help center
a secure way for users to access their tickets

What the platform does

The platform allows SaaS founders to:

• embed a fully customizable support in their product
• create ticket templates with custom fields
• manage tickets from a central dashboard
• automate actions with workflows
• organize tickets using labels and priorities
• allow users to access tickets via secure tokenized links

The goal is to keep the entire support experience inside your own product and brand.

Tech stack

The project is split into two main parts.

Backend :

Go
PostgreSQL
Redis

Frontend :

Next.js
React
Tailwind

The backend exposes an API that the dashboard and embeddable components communicate with.

This approach makes it possible to integrate the support system into different environments while keeping a single backend.

Challenges while building it

One of the hardest parts wasn’t the ticketing system itself, but designing a structure that could support:

multi-organization setups
teams and permissions
automation workflows
customizable ticket templates

Another challenge was building a system where end users could interact with tickets without requiring accounts, which led to implementing secure tokenized links.

Why I built this

While working on multiple SaaS projects, I realized that customer support tools were often built for large companies, not for small teams or indie developers.

The goal with Vicket is to provide a developer-friendly support platform that is:

easy to integrate
fully white-label
flexible enough for different SaaS products

The project is now live

After 6 months of development, the first version is now live.

If you're building a SaaS or any product with users, I'd love to hear how you're currently handling support.

What tools are you using?

And what do you wish support platforms did better?

You can check out the project here:
https://vicket.app