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

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

Early Renewal or Prepayment: absence.io 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 absence.io is generally well liked, especially by small and mid-sized companies that need simple absence and time tracking without heavy HR suites.

Overall sentiment is strongly positive, with a few important red flags around billing and support that are relevant when negotiating or deciding contract length.

Key strengths our Spendbase clients highlight:

• Very easy to roll out and adopt, even across multiple teams
• Clear, shared calendar for vacations and absences
• Strong fit for distributed and remote teams
• Good UI/UX and mobile apps
• Useful integrations:
• Slack (mentioned repeatedly as “seamless” and “fantastic”)
• Google Calendar and MS Teams either available or in progress in some accounts
• Good customer support in many cases: “on fire,” “outstanding,” “very quick and professional”

Core use cases that come up often:

• Replacing spreadsheets and paper forms
• Faster approvals via email (Accept/Decline)
• Visibility on team and company-wide absences for capacity planning
• Simple time tracking and PTO balance visibility

Main pain points and risks:

• Cost sensitivity:
• Several Spendbase clients felt pricing became an issue as they scaled
• Some downgraded or switched to cheaper alternatives
• Support and billing edge cases:
• A few cases of suspended accounts while still being charged
• Friction and extra steps when trying to cancel, described as “unacceptable”
• Product limitations:
• Limited handling of US/multinational leave policies and accruals
• Complexity with part-time schedules and changing work contracts
• Confusing year-end balance adjustments and modifying existing requests
• Missing or immature integrations with some HR/payroll tools
• UX issues:
• Interface not always intuitive, especially calendar and approvals
• German defaults (language, holidays, date formats) can confuse non‑EU teams
• Some UI feels “twitchy” or not fully polished

How we typically advise Spendbase customers:

• Strong candidate for:
• Small to mid-sized, mainly European organizations
• Teams heavily using Slack and simple PTO rules
• Be careful with:
• Larger, multi-country setups needing complex accrual logic
• Long-term contracts without a clear cancellation and SLA agreement
• Negotiation angles:
• Price flexibility as seat count grows
• Support responsiveness and clear escalation paths
• Roadmap commitments around integrations and advanced HR features