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

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

Early Renewal or Prepayment: Favro 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 Favro generally lands well with teams that want flexible, visual planning, but there are some clear trade‑offs to keep in mind before you lock in a long‑term contract.

Overall sentiment
Most Spendbase clients rate Favro positively for day‑to‑day work management, especially small to mid‑sized, agile or cross‑functional teams. However, satisfaction drops when projects get large, when deep reporting is needed, or when billing and admin controls get more complex.

What Spendbase clients like most
Our data highlights these top strengths:

• Flexible structure
• Kanban boards, backlogs, collections, and swimlanes work together well
• Cards can live in multiple boards/backlogs and support hierarchies (parent–child)

• Works both for high‑level strategic planning and detailed task tracking

• Ease of use & adoption

• Very quick to set up and understand

• Good fit for mixed teams: engineering, design, product, ops, even personal use

• Collaboration & visibility

• Great for aligning multiple teams on one project
• Good visual overview of workloads and progress

• Integrations with Slack, GitHub and others help centralize work

• Support

• Many clients praise Favro’s support team as fast and helpful

Where clients struggle
Our internal feedback also surfaces consistent pain points:

• Pricing & billing
• Per‑user pricing feels steep to some, especially for small teams or personal use

• One severe case of unexpected auto‑upgrade/charge is a red flag for tighter admin controls

• UX & performance gaps

• Long loading times and occasional drag‑and‑drop or mobile app glitches
• UI called “text heavy” and not visually rich enough by some

• Notifications and “My work” view are weak for people with many tasks

• Missing / immature features

• Limited search (no simple global search across all data)
• Reporting and analytics not deep enough for serious planning and portfolio management
• API and data export are too basic for teams needing advanced metrics or custom tooling
• No true Gantt; timeline is focused on workload, not schedule planning
• QA workflows are harder (attachments in comments, mobile updates, bug reporting)

How we advise Spendbase clients
When negotiating Favro:

• Right‑size licenses; avoid over‑buying for occasional users
• Push for clarity on upgrade triggers and billing policies
• Validate that reporting, search, and API meet your needs before committing to long terms
• Consider pilot periods for larger teams to test performance and scaling

Used in the right context, Favro can be a very effective, agile planning hub. The key is not to overpay for capabilities your team may not fully use, and to be realistic about its limits for heavy reporting and large‑scale programs.