Milestone — #1 Product of the Week on Product Hunt

Intro

In 4 months, we went from an idea to #1 Product of the Week & #3 of the Month on Product Hunt.

This is the story of how my friend and I identified a real market gap, validated it with users, found a technical co-founder through Y Combinator Matching platform, built an MVP, and launched to the world. Along the way I designed the entire product from scratch: the flow builder, the logic layer, the analytics dashboard, the onboarding system, and the corporate website. Here's what happened, what we shipped, and what I learned.

Origin Story

We kept seeing the same broken pattern.

Working as Product Designer in B2B, onboarding breaks as soon as the product moves fast. Frequent updates make custom tours expensive to maintain, and engineering time is rarely available. The tools I used produced generic flows that users skipped, with no real segmentation.

I partnered with my friend Anastasia, a Product Marketing Manager seeing the same issue from the GTM side.

We sanity-checked the idea with peers, then validated it with data:

Research

We saw the problem ourselves. Then we validated it rigorously.

Before defining the product, we ran 15 interviews across user and business perspectives in B2B SaaS.

This gave us two outcomes:

The insight that defined the architecture.

A consistent theme from teams building onboarding in-house: it was slow, engineering-heavy, and hard to maintain. That set a strict requirement — the product must be usable without developers, by product, design, or marketing teams.

Competitive analysis reinforced the direction.

Existing tools lack meaningful segmentation. Most deliver the same onboarding to every user, regardless of role, plan, or context. We made segmentation the core differentiator.

👥

Automatic segmentation

Users grouped by role, plan, or behavior automatically

🎯

Tailored flows per segment

Each segment gets a distinct onboarding path

⚡

Faster time to "aha"

Only relevant features introduced, no noise or overwhelm

Defining ICP

We mapped our Ideal Customer Profile using a Lean Canvas, focusing on early-stage B2B SaaS startups with PLG motions — PMMs, PMs, and founders at companies under 150 people.

Building the MVP

From blank canvas to live flow — in under 5 minutes.

To build the MVP, we needed a technical co-founder. We interviewed 20 engineers to find the right fit.

With a three-person team — Anastasia (CEO), Andrej (CTO), and me (COO, leading product and design) — we started building Milestone.

Milestone is a no-code gamification platform for product-led SaaS. The core mechanic: a Chrome Extension that lets you build interactive onboarding flows directly inside any web app — no developer needed. I designed every screen from scratch.

The Chrome Extension architecture

Flows run inside the customer's own product via a Chrome Extension. This meant we had zero control over the host environment — our UI had to survive collisions with any CSS. Every design decision had to work across hundreds of different web apps.

The product, end to end.

Design and launch interactive onboarding, segmented flows, and in-product rewards — without engineering.

Building a flow feels like using Figma — not writing a JIRA ticket.

A PM or founder could open the Chrome Extension, click any element in their product, and attach a step — tooltip, modal, or hotspot — in seconds. The right panel exposed just enough config without overwhelming.

Persona branching made visible.

The Flow Logic tab needed to make conditional branching understandable to non-technical users. I used a visual node canvas — each branch a visible path, not a dropdown condition.

The dashboard that tells you exactly what to fix.

I restructured analytics to lead with what matters: Aha-Moment Milestone, Activation Rate, Habit Milestone, First Purchase. Customers could see activation trending up the same week they launched their first flow.

Product Hunt Launch

How we launched Milestone.

After validating with beta customers and shipping V3 of the onboarding, we launched publicly on Product Hunt. We hadn't paid for placement. No sponsored slots. Just the product.

The launch

Alongside the launch, we ran a waitlist through our website — anyone who clicked 'Join Waitlist' filled out a short form sharing their use case and team context. This gave us both a demand signal and a qualified pipeline of 450+ potential customers before we'd built half the product.

What the community said.

Outcomes

From product hunt recognition to paying clients.

What We Learned

What this taught me about designing for activation.

The aha-moment framework is underrated as a design tool. When the whole team can name the exact moment a user first understands the value, every decision becomes easier to evaluate. The question stops being "is this good UX?" and becomes "does this get users to their aha-moment faster?" Persona-aware progressive disclosure, a single question at signup, zero backend complexity, pre-seeded templates, proved that the simplest implementation of a good idea consistently beats a sophisticated implementation of an average one.

Product Hunt is an underrated validation tool. Not just for distribution, for idea validation as well. Our launch gave us 1,093+ upvotes, 450+ waitlist signups, and direct feedback from the exact people we were building for. The comments told us which features resonated, which messaging landed, and what the market actually wanted next. It also converted our first paying customers. If you have a product and haven't launched on Product Hunt, you're leaving signal on the table.

Differentiation is a design decision. Going into a market with established players (Appcues, UserPilot, Chameleon) we had to be genuinely different, not just cheaper. The segmentation-first approach and the Chrome Extension architecture weren't just technical choices; they were the product's reason to exist. Blue ocean positioning starts in product, not in marketing copy.