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

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

Early Renewal or Prepayment: AddEvent 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 AddEvent is generally seen as a high‑value tool for driving attendance and managing event communications, with a few clear areas where we usually help clients optimize cost and usage.

Key strengths our Spendbase clients highlight:

• Attendance & engagement impact
• Noticeable jumps in live webinar/workshop show‑up rates.
• Events get added directly to Google, Outlook, Apple, etc., so time is blocked on attendees’ calendars.

• Subscription calendars and auto‑updates mean one URL can serve ongoing sessions and schedule changes.

• Ease of use (once set up)

• Fast to create events, clone them, and generate:
  • “Add to calendar” buttons
  • Landing pages
  • .ics files
• Works well across devices and calendar providers.

• Simple embed options for websites, Mailchimp, HubSpot, and other email tools.

• Functionality that supports marketing and ops

• RSVP and basic intent tracking.
• Reminders and time‑zone handling.
• Ability to push updates to all subscribers when events change.
• Strong, responsive human support that helps solve edge cases and custom workflows.

Main friction points our internal data surfaces:

• Pricing and plan fit
• Several Spendbase clients feel the product is slightly pricey for lighter or narrower usage.

• Common pattern: paying for features not fully used (advanced options, deeper customization) when only core “add to calendar” + reminders are needed.

• Usability and learning curve

• UI can feel confusing at first, especially:
  • Distinguishing calendar vs. event settings
  • Sharing options and display variants

• Some flows (e.g., setting events as “busy” in Google, or advanced RSVPs) are not obvious without support.

• Technical and UX gaps

• Outlook.com button behavior for external users is inconsistent; .ics is the safer fallback.
• Reminders/alerts sometimes don’t behave as expected due to end‑user calendar settings.
• Limited visual customization for widgets and embeds; harder to match strict brand guidelines.
• Some clients want:
  • Easier way for attendees to receive automatic update notifications
  • Visibility into who added events
  • Integrated payments.

From a Spendbase discount perspective, this all points to a clear strategy: right‑size plans based on actual feature usage, avoid overpaying for underused capabilities, and negotiate around the fact that many clients primarily rely on the core scheduling and “add to calendar” features that are already delivering strong ROI.