Sleekplan
Customer feedback, roadmap, and changelog tool for collecting and prioritizing user requests
Sleekplan is shipping enterprise-grade B2B features at speed: SCIM, account-level feedback groups, and internal product documentation in a single sprint.
◆Recent moves
- 9d ago
Groups: see your feedback by account
⚡ SPARKGroups shifts Sleekplan's feedback analysis from individual vote counts to account-weighted signals — twenty upvotes now shows whether that's twenty trial signups or three enterprise accounts, which is a fundamentally different input for B2B prioritization.
View source ↗ - 15d ago
Customer Identity Controls: Random Usernames & Hidden Names 🔒
Random username and hidden-name options let B2B teams run public feedback boards without revealing their customer list to competitors — solving a real enterprise blocker where public boards were previously treated as a competitive intelligence risk.
View source ↗ - 15d ago
Introducing Directory Sync (SCIM)
⚡ SPARKSCIM directory sync with Okta, Entra ID, and OneLogin automates user provisioning and deprovisioning, removing the manual access management that was a prerequisite objection for IT-controlled enterprise deployments.
View source ↗ - 23d ago
Internal statuses
Internal-only statuses let teams track granular workflow progress (e.g., 'In spec review', 'Waiting on design') without exposing that detail to customers, who see the public status you designate — separating internal process transparency from customer-facing communication.
View source ↗ - 29d ago
Introducing Components: the second axis your board was missing
Components add a product-area taxonomy (Widget, API, Billing, Mobile) as a second, independent axis alongside request type — posts can now carry both dimensions, enabling per-component feedback aggregation and roadmap filtering.
View source ↗ - 29d ago
Introducing Documents: the thinking behind your feedback, in one place 📝
Documents add an internal PRD and decision-record layer directly beside feedback posts, keeping the reasoning that drove a decision (or a rejection) in the same place as the customer request — reducing the Notion/Confluence context-switching for product teams.
View source ↗