Number of Seats/Users: Productboard offers discounts based on the number of users or seats. A higher volume typically leads to a better discount structure, especially for enterprise-level usage.

Commitment to a Long-Term Contract: Discounts are often provided to companies that commit to using the service for a longer period (e.g., 1-year or 3-year contracts). A longer commitment shows Productboard that the company is serious and willing to invest in the platform long-term.

No Active Discounts: Companies that are not already receiving other active discounts may have a better chance of qualifying for additional discounts from Productboard. Productboard reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: Productboard offers discounts if you agree to a minimum amount of usage or transaction volume. This could be based on data storage, transactions, or other metrics tied to how much you will use the platform.

Enterprise-Level Negotiation: Companies that qualify as “enterprise” due to their size or complexity (e.g., having large teams, multiple departments, or geographical presence) may be eligible for additional discounts from Productboard. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: Productboard often offers discounts if you renew early or prepay for the entire contract period. This is a common approach to securing a lower price.

Here at Spendbase our internal data shows that Productboard is generally very well‑regarded by Spendbase clients, especially product-led software companies that care a lot about customer feedback and roadmap clarity.

Overall sentiment
– Average rating across the sample sits around 4.6/5.
– Most feedback is strongly positive, with a small but vocal group flagging UX/search and “too many tools” overlap as pain points.

What Spendbase clients like most

1) Centralizing feedback and insights
– Productboard becomes a single place for:
– Customer feedback from Slack, Intercom, Salesforce, Zendesk, email, Chrome extension
– Internal ideas and notes
– Clients highlight the “Insights” inbox as critical for:
– Tagging and categorizing feedback
– Linking snippets directly to features
– Seeing who requested what and why

2) Roadmapping and alignment
– Productboard is used to:
– Prioritize features based on user impact scores and company objectives
– Build clean, visual, shareable roadmaps for stakeholders and clients
– Keep PMs, engineering, CS, and sales aligned on what’s coming next

3) UX and day‑to‑day use
– The interface is often described as intuitive, clean, and “a joy to use.”
– Many teams effectively run their whole product management workflow inside it.

Common friction points

Our internal data also shows recurring gaps that matter when negotiating price and rollout scope:

• Feedback & search structure
• Some clients complain about fragmented search (different searches for different object types).

• Lack of custom fields on notes and cluttered inboxes can make large-scale feedback management harder.

• Integrations & missing features

• Frequently requested: deeper GitLab, Asana, Segment, CRM, and persona management capabilities.

• Some clients say they still rely on spreadsheets or other tools for dependencies, forecasting, or classic project management (Gantt, etc.).

• Adoption across the company

• Non‑PM users can struggle with onboarding and understanding how to submit feedback properly.
• To get full value (and justify spend), teams often need to “go all in” and replace overlapping tools.

How this impacts Spendbase negotiations

When we negotiate Productboard contracts for clients, we typically:
– Leverage gaps in search, integrations, and project management as discount arguments.
– Push for better pricing or add‑ons when clients are centralizing multiple tools into Productboard.
– Ensure renewal terms reflect the fact that some “must‑have later” features are still on Productboard’s own roadmap.