Leapsome Problems & Issues

Real user-reported problems, complaints, and limitations for Leapsome. Based on analysis of 12 signals.

Overall score: 68/100

Issues by Category

usability3 issues

Leapsome sends too many notifications and emails

Notification overload is the most repeated complaint on G2 and OMR: reminders arrive by email, Slack and Teams, some users stop reading them, and a few still get reminders for cancelled or one-off meetings. Per-user controls exist (Personal Settings) but users say they are rigid and survey reminders cannot be turned off for a single survey.

Frequency: 7%Sentiment: -0.50/1003 sources
Impact
5

Leapsome navigation feels cluttered

Navigation difficulty appears in about 130 G2 reviews. Occasional users (managers who only log in for review season) struggle to find features because pages are nested and the menu is overloaded, and a few reviewers call the design plain or dated.

Frequency: 6%Sentiment: -0.30/1003 sources
Impact
4

Leapsome Learning module less mature than the rest

Several reviewers on Capterra and OMR say the Learning module leaves a lot to be desired compared with performance and feedback, including missing calendar sync for live trainings. The content library is a paid add-on (from €1 per employee per month).

Frequency: 3%Sentiment: -0.30/1002 sources
Impact
4
customization3 issues

Missing features and limited customization in Leapsome

'Missing features' is the single most-cited con on G2 (around 140 reviews), especially integrations and edge cases like bonus calculations that don't fit the system's logic. Capterra reviewers ask for more customization in performance management and self-assessments.

Frequency: 7%Sentiment: -0.40/1003 sources
Impact
5

Leapsome reporting and exports are limited

Reviewers want more flexible reports, ad hoc analysis and advanced filters for performance data, and say exporting review data is awkward. Survey exports apply the anonymity threshold only at survey level, so they don't match what the dashboard shows.

Frequency: 5%Sentiment: -0.40/1003 sources
Impact
5

Leapsome goals and OKRs feel rigid

OMR reviewers want more flexibility in goal tracking, such as responsibility structures and mid-cycle adjustments. Jira can be linked to goals, but key-result numbers are not pulled automatically; Leapsome points to its API or Zapier for that.

Frequency: 4%Sentiment: -0.30/1002 sources
Impact
4
pricing2 issues

Why is Leapsome so expensive? Modules are priced separately

Every Talent Suite module is billed per employee per month on top of a required platform plan: Performance Reviews €7, Recruiting €5, Goals €4, Surveys €4, Learning €4, Compensation €3, Time Tracking €3, plus €7-10 for the HRIS platform. A company that wants reviews, goals and surveys pays well over €20 per employee per month at list price, and small teams on OMR and Capterra call the total too high for the value.

Frequency: 7%Sentiment: -0.60/1004 sources
Impact
7

Can you cancel Leapsome? Two months' notice, no refunds

Under Leapsome's North America terms, annual plans auto-renew for 12 months unless cancelled with two months' notice before the term ends (two weeks for monthly plans), fees are non-refundable, and discounts don't automatically carry into the renewal term. After termination you get 30 days to export data as CSV.

Frequency: 4%Sentiment: -0.50/1002 sources
Impact
7
onboarding1 issue

Leapsome setup is complex and has a learning curve

Learning curve is one of the top-cited cons on G2 (130+ mentions), and OMR reviewers describe the initial configuration of review cycles, visibility rules and integrations as complex and time-consuming. Leapsome lists an 'Accelerator Program' worth €24,000 for implementation, which shows how much setup a full rollout can involve.

Frequency: 7%Sentiment: -0.40/1003 sources
Impact
6
performance1 issue

Leapsome slow with large teams and many reviews

Some G2 and Capterra reviewers report that loading and reporting get sluggish with big teams or many review cycles, and that information-heavy pages can feel slower than expected.

Frequency: 4%Sentiment: -0.40/1002 sources
Impact
5
mobile1 issue

Is there a Leapsome mobile app? No native app

Leapsome's own help center says there is no Leapsome mobile app and suggests saving the website as a home-screen shortcut on iOS or Android. Reviewers say the mobile web experience is limited and slower than desktop, which hurts frontline or travelling staff.

Frequency: 5%Sentiment: -0.50/1003 sources
Impact
5
integrations1 issue

Leapsome Slack, Teams and HRIS sync depends on matching emails

Slack, Microsoft Teams, calendar, Jira and SSO all match people by email address. When the Leapsome email differs from the HRIS, Slack or identity provider email, users silently don't sync, and a 'Successful' HRIS sync can still skip employees with missing emails or duplicates.

Frequency: 5%Sentiment: -0.40/1003 sources
Impact
6

Regret Patterns

Common reasons users regret choosing Leapsome.

Module costs stacked up after the pilot

Teams start with reviews, then add goals, surveys and learning, and each adds a per-employee fee on top of the platform plan, so the bill ends up far above the first quote.

Frequency: 6%At the first renewal

Missed the two-month cancellation window

Annual contracts auto-renew for 12 months unless notice is given two months before the end, and fees are non-refundable, so a late decision to switch costs a full extra year.

Frequency: 4%Two months before renewal

Setup took far longer than expected

Configuring review cycles, visibility rules, HRIS sync and integrations needed more admin time and training than planned.

Frequency: 5%First 1-3 months

Employees tuned out the notifications

Heavy email and chat reminders led some employees to ignore Leapsome messages entirely, hurting completion rates.

Frequency: 5%First review or survey cycle

Reporting didn't meet leadership's needs

HR teams found they had to export and rework data elsewhere to get the cuts leadership asked for.

Frequency: 4%After the first full review cycle

Mobile users left out

Without a native app, staff who work away from a desk found it awkward to complete reviews and surveys.

Frequency: 3%First rollout to the whole company

When Leapsome Breaks Down

Specific scenarios where Leapsome fails or underperforms.

Employee email differs between HRIS, Slack and Leapsome

Slack, Teams, calendar, Jira and SSO all match on email, so those people silently don't sync or can't log in.

Small teams in engagement surveys

Teams below the anonymity threshold show N/A, and stacking filters raises the threshold further, so small-team results disappear.

Large companies running many review cycles

Some users report slower loading and reporting with big teams and lots of review data.

Switching identity provider

Leapsome supports only one SAML identity provider at a time, so a migration from Okta to Entra ID has to be planned to avoid login failures.

Meetings created by someone else in Outlook

Only the Outlook meeting owner can link it to a Leapsome 1:1, so assistants or schedulers break the calendar sync.

Budget cuts mid-contract

Fees are non-refundable and you remain liable until the end of the term, so you can't scale down mid-year.