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

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

Early Renewal or Prepayment: Wizzy 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 Wizzy tends to perform very well for teams focused on conversion and customer experience, especially in Magento environments.

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

1) Impact on sales and engagement
– Many clients report a clear uplift in:
– Product discovery
– On-site engagement (more clicks, more search usage)
– Conversions from search traffic
– The key drivers are:
– Highly relevant results
– Fast, instant search with no full page reloads

2) Search quality and speed
Our internal data shows that the 3R model (Reliability, Relevance, Rapidness) isn’t just a tagline:
– “Super fast” search is mentioned frequently
– Result quality is perceived as a major upgrade over default store search
– This helps reduce “zero results” scenarios and drop-offs after search

3) Ease of setup and integration
Spendbase clients usually highlight:
– Straightforward initial setup
– Smooth path from staging to production (often within days)
– Some technical familiarity is helpful, especially:
– Basic understanding of mustache.js for front-end customization

4) Support and issue resolution
This is one of Wizzy’s strongest areas based on what we see:
– Tech support is described as:
– Very responsive
– Knowledgeable
– Proactive in verifying search behavior before go-live
– Typical issues (like cache conflicts or limited info in result listings) were:
– Identified quickly
– Resolved in a few hours
– Often followed by product improvements

5) Common friction points
The negatives we see are usually minor and short-lived:
– Initial issues with caching on some setups
– Limited default data shown in search results (later customized)
– Need for some dev effort to fully leverage mustache.js

Overall Spendbase takeaway for cost-conscious teams:
– Wizzy tends to offer strong ROI when search is a revenue lever (mid to large catalogs, serious about UX).
– The vendor’s support reduces hidden “implementation costs,” which matters a lot for total cost of ownership.
– If your team can handle light front-end customization, Wizzy can be tuned very closely to your store’s needs, making it a solid candidate when negotiating for both performance and budget efficiency.