← Back to all sparks
S

Sleekplan

SUPPORT
Velocity8.8

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.

b2b-saasscimaccount-groupsenterprise-feedbackproduct-managementcustomer-support
Current state
Sleekplan has entered a period of rapid enterprise feature development following its 2.0 rebuild in June. The recent wave includes SCIM directory sync (Okta, Entra ID, OneLogin), account-level Groups that reweight feedback by company rather than individual user counts, identity privacy controls for public boards, internal-only status visibility, Components as a second taxonomy axis, and internal Documents for PRDs and decision records. This is not incremental polish — each addition addresses a distinct enterprise sales objection.
Where it's heading
Sleekplan is systematically closing the gap between a startup-friendly feedback tool and something IT and procurement teams can approve at mid-market and enterprise accounts. SCIM removes the manual provisioning burden, Groups make the feedback data credible for B2B prioritization decisions, and Documents keep the reasoning inside the tool rather than scattered across Notion or Confluence. The trajectory is clear: become the product feedback system of record for B2B SaaS teams.
Prediction
SSO (SAML) and role-based access controls are the next likely additions to complete the enterprise security checklist, and Groups will likely gain weighting by contract value (ARR) once customers start requesting customer-revenue-aware prioritization.

Recent moves

  1. 9d ago

    Groups: see your feedback by account

    ⚡ SPARK

    Groups 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 ↗
  2. 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 ↗
  3. 15d ago

    Introducing Directory Sync (SCIM)

    ⚡ SPARK

    SCIM 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 ↗
  4. 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 ↗
  5. 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 ↗
  6. 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 ↗