The 3 fastest-growing SaaS teams we studied all do this: they publish a public roadmap

Mark Walker — Fri, 26 Sep 2025 09:25:31 +0000

As a startup studio, we’ve worked with lots of young SaaS teams who are racing to product-market fit while juggling support, features, and constant feedback. One practice consistently separates the breakaway performers from the pack:

They work in public - specifically, they publish a c*lear, living public roadmap* and pair it with continuous changelogs and user feedback loops.

Why does this single habit move the needle? Because a public roadmap simultaneously:

Builds trust (“we’re listening, here’s what’s next”)
Reduces churn (customers see momentum and upcoming value)
Focuses the backlog (votes and comments sort signal from noise)
Aligns go-to-market (sales and success can point to what’s planned/GA)
Compounds SEO and credibility (shipping logs are proof, not promises)

Below we break down three well-known, high-growth product orgs with effective public roadmapping styles - GitLab, ClickUp, and Supabase - and extract practical patterns you can copy this week.

1) GitLab - “Direction” as a public product strategy (and roadmap)

How they do it

Instead of a single pretty board, GitLab publishes a comprehensive Product Direction site: multi-horizon strategy (3-year view), annual investment themes, and upcoming releases - all public and continuously updated. This gives customers and prospects a candid signal of where the platform is heading and how priorities are set across the DevSecOps lifecycle.

They also document how product is run (principles, processes, ownership) in a publicly accessible product handbook, which points readers back to “Product Direction” for what’s planned. This closes the loop between strategy (why), process (how), and roadmap (what/when). The GitLab Handbook

Why it works

**Credibility through context. **Not just a list of cards; you see the reasoning and themes guiding what ships next. That fosters enterprise-grade confidence even in SMB buyers.
Expectation management. Direction pages explicitly state that plans can change - useful transparency that protects trust when priorities shift.
Internal alignment. Sales, success, and community advocates can share one canonical source of truth.

How to replicate (lean version)

Publish a simple “Direction” page with three layers:
- 12–18 month themes (3–5 bullets, not everything)
- A now/next/later table linking to issues/epics
- A monthly changelog anchor (“what shipped”)
Label uncertainty. Use tags like exploratory, draft, or committed to signal maturity and manage risk.
Link feedback in-line. Each roadmap item should have a “Discuss / upvote” link (Canny, Usersloop, GitHub Discussion, etc.).
Assign DRIs visibly. A name or team next to each initiative raises accountability and answerability.

2) ClickUp - Public doc + Canny for suggestions and prioritization

How they do it

ClickUp maintains a public Roadmap doc and explicitly funnels feature requests through Canny. The doc serves as the “what’s planned” home base; Canny concentrates raw requests, votes, and comments into a prioritizable stream the team can act on.

Why it works

One link to rule them all. A single URL is shareable by support, success, and sales. New users get instant visibility.
Qual + quant together. Comments explain why something matters; votes show how many care. The combo hardens prioritization.
User participation boosts buy-in. When customers see their request appear on the roadmap (even tagged “under review”), satisfaction rises before you write a line of code.

How to replicate (lean version)

Stand up a hosted roadmap page (Notion/Docs page or Usersloop’s public roadmap) with:
- Sections: Now, Next, Later
- Status badges (Planned/In progress/Released/On hold)
- Links to discussion threads
Route all requests to one intake. If you already get requests via email/Slack/Twitter, reply with: “Great idea - could you add it here so others can upvote?” Over time, the roadmap naturally orders itself.
Ship a monthly roundup. Post “What shipped” + “What moved” + “Top new requests.” This creates a heartbeat customers come to expect.

3) Supabase - Open-source cadence with public discussions and a prolific changelog

How they do it

Supabase leans into the open-source playbook: they maintain a high-frequency public changelog and push roadmap discussions in the open (e.g., GitHub Discussions on upcoming packages/roadmaps). The cadence - lots of visible progress, clearly dated - gives developers confidence that the platform is moving fast and that their feedback is heard.

Why it works

Momentum reduces risk. A steady changelog (with statuses and target timelines where possible) reassures teams evaluating a core platform.
Community co-design. Discussions become living artifacts of decisions; newcomers can see rationale, trade-offs, and constraints.
Launch marketing = roadmap marketing. Each shipped slice earns attention, backlinks, and social proof.

How to replicate (lean version)

Create a public changelog (auto-generated or hand-rolled) with clear, dated entries and tags (feature, improvement, fix, deprecation).
Move “spicy” debates to public threads. For candidate features, open a thread (“Problem / Proposal / Open questions”) and link it from the roadmap.
Set light target windows. Month/quarter windows (Q4 ’25) beat exact dates for small teams. Mark slipped items with a short note > perfection.

Patterns the winners share

They don’t just list features - they publish direction.
A sentence or two about why it matters turns a card into strategy. GitLab’s “Direction” shows the playbook.
They make participation obvious.
ClickUp’s roadmap doc points users to Canny for requests and votes; it’s impossible to miss how to contribute.
They ship publicly, often.
Supabase’s changelog rhythm is a trust engine. Even modest releases, shipped consistently, create a perception of momentum.
They set expectations explicitly.
GitLab’s pages state that plans may change; this simple disclaimer maintains credibility when reality shifts.
They give GTM teams a shareable truth.
A single roadmap link keeps Sales/Success/Support aligned and reduces “When will X be ready?” thrash.

A step-by-step roadmap launch plan for a 1–50 person SaaS

Day 1–2: Decide the container

Hosted doc (fastest) or dedicated roadmap tool (Usersloop public roadmap, Linear+Productlane, Canny board). Aim for one shareable URL. (Linear + Productlane is a popular pairing for publicizing selected projects.)

Day 2–3: Draft the initial cut

Now (0–8 weeks): 3–6 items, each with one-line problem statements.
Next (1–2 quarters): 5–10 candidate items; mark confidence level.
Later (2+ quarters): themes only (e.g., “Team accounts,” “Analytics v2”).

Day 3: Wire feedback in

Every item gets a “Discuss / upvote” link.
Add a “Submit an idea” button that lands in your intake (e.g., Usersloop form or widget).

Week 1: Start shipping the heartbeat

Publish a monthly “What we shipped” update, even if small.
Add status badges and owner initials for each item.

Ongoing: Keep it honest

If something slips, change the badge and add a one-sentence reason.
Close the loop with requesters when an item ships (email/DM/Usersloop auto-notify).

Objections you’ll hear - and how to handle them

“Won’t competitors copy our roadmap?”
Maybe. But in early-stage SaaS, speed, quality, and customer intimacy are larger moats than secrecy. Public roadmaps raise the bar for rivals by forcing them to match your clarity and cadence. GitLab’s posture explicitly acknowledges change and still publishes direction.

“We’ll get yelled at if we miss dates.”
Don’t publish dates; publish windows and confidence labels. Be explicit that direction is subject to change (again, GitLab’s framing is a good model).

“It’s more overhead.”
A monthly 45-minute ritual to update the doc and changelog is far cheaper than dozens of one-off “ETA?” conversations across support and sales.

Metrics to watch after you go public

Changelog engagement: unique views, time on page, scroll depth
Request quality: duplicates down, “problem statements” up
Conversion & expansion: win-rate lift where roadmap items match prospect needs
Churn notes: fewer “product moving too slow / no visibility” reasons
Support deflection: fewer “is X planned?” tickets as your roadmap gains awareness

Do it affordably (and fast) with Usersloop

If you want the ClickUp-style public doc, Supabase-style changelog cadence, and GitLab-style direction - without stitching 3–4 tools - Usersloop gives you a lightweight, all-in-one path:

Public Roadmap (hosted page)
- Create Now / Next / Later lanes, add statuses, owners, and confidence labels.
- Expose an upvote / comment surface so customers can participate.
In-app Widget (chat + feedback + announcements)
- Let users submit ideas straight from your product (no context lost).
- Announce releases with targeted banners or messages in the widget.
- Offer helpdesk and support chat in the same place customers discover updates.
Changelog & Announcements
- Publish concise, tagged release notes (feature, fix, improvement).
- Auto-notify followers of a roadmap item when it ships, closing the loop.
Prioritization & Planning

Result: You replicate the best parts of GitLab’s “direction,” ClickUp’s public roadmap + Canny flow, and Supabase’s visible shipping cadence without buying multiple subscriptions - or duct-taping Notion, Canny, and a custom changelog together.

Check out Users Loop Here

New Feedback, Roadmap, Updates & Support tool for SaaS startups

Mark Walker — Tue, 16 Sep 2025 07:24:35 +0000

Pleased to announce the launch of Users Loop today! well really yesterday but a bit late....

Users Loop was born out of my own need for ways to easily manage the communication between users of our various SaaS products, and the product teams.

Various options existed already for certain parts, but nothing covered all the bases. And adding multiple subscriptions was too expensive when we launched new products so often skipped this, even though the early stage communication being the most important.

I actually started this project 9 years ago... November 2016 according to my original domain registration, though it never got off the ground then. But skip forward almost a decade, with fresh needs and focus, we got UsersLoop production ready at last.

So what does it do?

Users Loop is a tool to help tech products communicate with their customers to improve feedback, planning, training and support.

It consists of 3 key components:

1) Management System

This is where you team set things up and manage things like:

Feedback reports (feature requests, bug reports etc)
Your product roadmap
Helpdesk and FAQ's
Customer chats

2) In-App widgets

The in app widgets allow you to embed a few lines of code and place our user widget inside your web app.

The widget allows users to:

Send feedback
Chat with your team
Browse help guides, including recommended guides for the page they are currently on
View your latest updates and announcements

3) Public Boards

The public boards provide a public resource where your users and potential customers can see your plans and updates.

View, comment and subscribe to all feedback requests, so your users can vote on what matters to them, helping you prioritise plans effectively.
View your planned product roadmap to see what is coming soon
View past product updates and announcments
Browse your full help desk and FAQ's

Whats next?

We have various plans to enhance and evolve the product over the next few months. Some of which are already listed on our public roadmap (one of our existing features!

Also we would love to get more products onboard and using Users Loop. If you are interested then you can take advantage of special pricing with 30% off for life using the link
https://usersloop.com?ref=devto

If you have any questions or want to get in touch then contact me, Mark Walker

Forem: Mark Walker

The 3 fastest-growing SaaS teams we studied all do this: they publish a public roadmap

1) GitLab - “Direction” as a public product strategy (and roadmap)

How they do it

Why it works

How to replicate (lean version)

2) ClickUp - Public doc + Canny for suggestions and prioritization

How they do it

Why it works

How to replicate (lean version)

3) Supabase - Open-source cadence with public discussions and a prolific changelog

How they do it

Why it works

How to replicate (lean version)

Patterns the winners share

A step-by-step roadmap launch plan for a 1–50 person SaaS

Objections you’ll hear - and how to handle them

Metrics to watch after you go public

Do it affordably (and fast) with Usersloop

New Feedback, Roadmap, Updates & Support tool for SaaS startups

So what does it do?

Whats next?