Number of Seats/Users: Requirements Portal 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 Requirements Portal 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 Requirements Portal. Requirements Portal reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: Requirements Portal 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 Requirements Portal. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: Requirements Portal 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 Requirements Portal is seen as a strong, fast‑improving option for hardware and embedded teams, especially those already in the Altium ecosystem.

From what Spendbase clients share, a few clear themes stand out:

1) What clients like most
– Single source of truth
– Central hub for requirements, verification, and design links
– Helpful for complex hardware products (satellites, aerospace, high‑reliability systems)
– Deep traceability
– End‑to‑end links from system requirements to:
– Schematics
– PCB layouts
– BOMs
– Test cases / verification evidence
– Makes audits and certifications easier and faster
– Strong Altium integration
– Fits naturally into Altium-based workflows (Develop, Agile Teams, Agile Enterprise)
– Reduces context switching and manual syncing
– Modern alternative to legacy tools
– Frequently mentioned as a better experience than classic tools like DOORS
– Supports smaller, agile teams that iterate quickly

2) Main pain points and risks
Our internal data also shows some consistent concerns:
– Product maturity
– Some features feel unfinished or still missing
– Occasional bugs and rough edges
– Change management
– Teams coming from spreadsheets or DOORS face a learning curve
– Process adjustments needed to fully benefit from traceability
– Performance and scale (for some larger orgs)
– Need to validate how it behaves with many projects and thousands of requirements

3) Support and vendor behavior
– Clients highlight fast, responsive support
– Vendor is open to feedback and sometimes aligns roadmap with customer needs
– This helps offset maturity risks but still needs to be factored into contracts and SLAs

4) Spendbase take from a cost/discount perspective
– Best value when:
– You already use Altium tools and want tighter integration
– You operate in regulated or safety‑critical domains where traceability saves audit and rework costs
– Cost‑saving levers we typically explore:
– Right‑sizing seat counts vs. occasional users
– Bundling with other Altium products
– Building in roadmap and support commitments into pricing negotiations

Overall, Spendbase clients see strong ROI potential, provided they account for the product’s evolving nature and negotiate pricing and terms accordingly.