Early-stage SaaS teams collect customer input everywhere at once: a Typeform waitlist, a Slack channel for bugs, a Notion page for the roadmap, and docs on a subdomain nobody bookmarks. Every launch adds another link. Support asks “where do I vote on feature X?” and you paste a fourth URL.
A public customer hub is the opposite pattern: one canonical URL per product where customers see what you choose to expose-feedback, roadmap, waitlist, and more-without you rebuilding the stack on every release.
What a customer hub actually is
ProductDesk gives each project a board at your-slug.productdesk.dev. That
hostname is the hub. Inside it, tabs are independent surfaces you enable per
project:
- Feedback - public board; customers submit ideas and upvote with email verification (no customer accounts).
- Roadmap - kanban-style view driven by feedback status (Planned, In Progress, Completed).
- Waitlist - pre-launch signups when you are not ready for open feedback yet.
- Community, docs, help, and more - toggled when you need them.
Customers learn one link. You turn tabs on in Settings as the product matures, without changing the URL printed in your app footer.
What to enable first (and what is still coming)
If you are already shipping, start with Feedback and Roadmap. That pair answers the two questions users repeat: “What should we build?” and “What are you building now?”
Move a request to Planned or In Progress in the dashboard and it appears on the public roadmap automatically. Complete it and the board shows Completed-no duplicate spreadsheet.
Waitlist is the right first tab when you are pre-launch and want emails before you open a public board.
A few hub tabs are on the public roadmap for ProductDesk itself (not hidden, just not shipped on boards yet): the changelog editor on the board, embedded feedback widget, and help center articles. You can leave those tabs off until they ship; the hub URL stays the same.
How voting works without customer accounts
Most feedback tools force voters to create an account. That friction kills participation-especially for busy users who only want to upvote one idea.
On a ProductDesk board, anyone can browse feedback and filter by status without signing in. To submit, upvote, or comment, they confirm their email once via a magic link. You get identifiable voters without maintaining a customer login system.
If your users are already signed in to your app, owner identify lets you vouch for them server-side so they skip the extra email step on the board. Anonymous visitors still work as guests.
One URL vs stitching tools
| Approach | Customer experience | Operator cost |
|---|---|---|
| Stitched stack (Typeform + Canny + Notion + docs host) | Four bookmarks, four brands, four logins | Multiple bills, manual sync, link rot in emails |
| Single hub | One link in app, site, and support macros | One dashboard; statuses drive the roadmap |
You do not need enterprise workflow builders to get value. Founders we talk to want: collect input, prioritize in public, ship, repeat.
A simple operating loop
- Share
https://your-slug.productdesk.devfrom your app settings, marketing site, and onboarding emails. - Review new feedback in the dashboard; reply in-thread when you need context.
- Promote real commitments to Planned / In Progress so the roadmap stays honest.
- Ship, then mark items Completed-customers see progress without a separate “status update” post.
When you are ready for a hands-on walkthrough, read Set up a public feedback board in 5 minutes.
Pricing and getting started
Plans start at $1/month for the Hobby tier, with a launch offer of the first month free on any plan. See pricing for limits on posts, tags, and tabs.
Create a project and publish your hub before your next release-one URL beats four.