Leapwork

Name: Leapwork
Brand: Leapwork

Move Fast. Break Less. Continuous Validation Engine trusted by the world's leading enterprises.

Est 2015|Valuation $270.8M|Raised $82.3M|7 Ref Customers

LinkedIn 19K|Web traffic 7K|FTEs 270

MarketsTest Automation

Published Oct 15, 2026

01Common complaints

1. Cost-sensitive teams or startups - Community posts and reviews cite licensing and implementation as comparatively expensive; open-source frameworks (Selenium/Playwright) or lower-cost solutions may be more appropriate. 2. Teams requiring heavy custom scripting and advanced frameworks - Some users report limitations compared with Selenium-style custom scripting and frameworks. 3. Highly volatile UI environments with limited capacity for maintenance - If releases frequently change UI locators/components and the organization lacks a disciplined strategy for test design, maintenance can be labor-intensive. 4. If an organization requires automatic SSO-driven role provisioning/authorization - Documentation indicates SSO is authentication-only and role assignment is not read from IdP claims; this may be a blocker for organizations needing full provisioning flows. 5. If independent proof of ROI is required - Many of the strongest ROI metrics are published in vendor case studies without full methodology disclosure; buyers should seek independent validation.

Deal disqualifiers (poor fit)

Organizations that require a fully code-centric framework with deep custom architecture control
Organizations with constrained budgets that cannot justify premium licensing
Organizations with extremely frequent UI changes and without disciplined component/test design practices (maintenance may offset productivity gains)

Limitations acknowledged by vendor documentation

SSO authorization gap: SSO integration supports authentication only; authorization must be configured manually.

Limitations frequently mentioned in reviews/community

Licensing and implementation costs are commonly described as high.
Limited customization or missing features are listed in some reviews.
Cloud deployment limitations are reported by some reviewers; specifics vary.
Stability and performance issues are reported in some environments.
Documentation is sometimes viewed as insufficient.

Roadmap / release notes

SSO documentation states availability starting from Release 2025.1.173 (feature timing is explicit in docs).

Where it struggles / is not ideal

Advanced dynamic test generation, highly custom validations, and deep integration logic may be better served by code-centric tools.
Network instability and legacy desktop element identification can increase flakiness and the learning curve, according to some reviewers.

02Why they buy

Validated by customer/reviewer evidence

Visual authoring and usability for non-coders are frequently mentioned in reviews and vendor case studies.
Support quality is commonly cited positively in enterprise reviews.
Governance-related features (audit logs, encryption, on-prem/hybrid deployment) are part of the platform messaging.

Less-validated / needs verification

Vendor claims of high-percentage productivity gains and error reduction should be independently verified before being relied upon in procurement decisions.

Where competitors have clear advantages

Tricentis Tosca: broader enterprise testing coverage and higher market penetration in some segments.
Code-first stacks (Selenium/Playwright): maximum flexibility, cost control, and a mature ecosystem, but require skilled engineers to develop and maintain frameworks.

Why customers chose Leapwork (themes)

Across review platforms and vendor case studies, recurring reasons include:

faster creation of automation for non-coders (visual building blocks)
support for both web and desktop in a single tool
vendor support and professional services cited as influential in successful rollouts
integration into DevOps pipelines

03Field reports

Review platform snapshots (what the market says)

- G2: very highly rated on G2. Pros/cons aggregation includes usability and customer support, and common negatives like cost, missing features, customization limits, cloud limitations, and licensing issues. - Capterra: well rated on Capterra. - Trustpilot: poorly rated on Trustpilot. - Sitejabber: poorly rated on Sitejabber. Interpretation: Business-facing review platforms indicate strong satisfaction among reviewers on those platforms, but consumer-style platforms with very low review volume show sharp negativity. This may reflect selection bias, different user segments, or outlier experiences and should be considered in context.

Direct quotes (positive)

"Reliable tool with excellent support and training"

This reviewer highlights stability, intuitive use, ability to handle both desktop and web apps, and strong support/training.

A vendor-published customer story states that the product is more user friendly than alternatives and lowers the requirement for hardcore developer skills to create flows.

Direct quotes (negative)

"The lack of code design options can be limiting… Unlike Selenium… does not allow for custom scripting… Additionally, the implementation cost is quite high."

"All Talk, No Results- Please Beware and Avoid"

Community posts also express concerns about cost and stability, with some teams deciding to discontinue use based on total cost of ownership or perceived reliability issues.

Why some customers leave / consider alternatives (themes)

Most common churn drivers from community and review excerpts:

cost / licensing viewed as high relative to alternatives
reported buggy behavior or performance issues in some environments
limitations of a low-code/no-code model for complex validations or dynamic logic
maintenance burden when UIs change frequently

Vendor-published customer story

Claims: - Vendor-published materials present substantial reductions in time to market, large-scale hours savings, and multi-fold ROI in one year. Critical evaluation: - These metrics are vendor-published within a vendor-hosted case study. - Methodology is not fully disclosed in the excerpt (e.g., baseline effort, attribution rules, how "hours saved" is calculated, whether savings were realized or theoretical). - Metrics are useful as directional evidence but should be validated by buyers.

Vendor internal case study webinar

The vendor produced an on-demand webinar describing how its own QA team uses the product to accelerate releases and improve customer experience.

Critical evaluation:

Internal case studies provide product usage context but are not independent evidence. Buyers should treat any ROI or time reduction metrics as illustrative unless corroborated by independently verifiable data.

04Best fit

Company size

Best fit tends to be mid-market to enterprise organizations.

Industries / verticals

Based on vendor and press examples:

Financial services / banking
Healthcare
Retail
Enterprises running packaged apps and complex business workflows

Roles and personas

QA Directors / Heads of Quality Engineering
Test Automation Leads
QA Engineers and citizen automators (manual testers, business analysts) who can author flows
DevOps/Platform teams responsible for execution infrastructure

Qualification criteria (good fit)

Organizations that need automation across desktop and web and prefer a single platform
Organizations that want to scale test authoring beyond code-heavy engineers
Organizations that value vendor support and are willing to budget for it
Organizations that require on-prem or hybrid deployment options

05The pitch

What the product does (objective core value proposition)

Leapwork is a visual, low-code/no-code test automation platform (previous coverage positioned it adjacent to process automation/RPA) designed to help teams build, run, and maintain automated tests for web and desktop applications, with integrations for mobile device clouds and common DevOps/ALM tools. The platform supports flowchart-style building blocks for authoring automation and also provides extension points for custom code when required. The vendor describes the platform as incorporating AI-assisted capabilities and deterministic execution characteristics; such vendor assertions should be treated cautiously and verified independently.

Target market and market positioning

Leapwork primarily targets mid-market to enterprise QA and testing organizations, especially those: - testing packaged enterprise apps (vendor messaging highlights major CRM and ERP ecosystems) - dealing with both legacy desktop and modern web apps - aiming to scale automation authoring beyond a small group of code-heavy test engineers In reviews, it tends to be adopted by organizations prioritizing: - relatively short onboarding for testers without strong coding skills - centralized governance (platform + agents) - vendor support/professional services for rollout

Get a comprehensive analysis of Leapwork including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 15, 2026

01Common complaints

Cost-sensitive teams or startups
- Community posts and reviews cite licensing and implementation as comparatively expensive; open-source frameworks (Selenium/Playwright) or lower-cost solutions may be more appropriate.
Teams requiring heavy custom scripting and advanced frameworks
- Some users report limitations compared with Selenium-style custom scripting and frameworks.
Highly volatile UI environments with limited capacity for maintenance
- If releases frequently change UI locators/components and the organization lacks a disciplined strategy for test design, maintenance can be labor-intensive.
If an organization requires automatic SSO-driven role provisioning/authorization
- Documentation indicates SSO is authentication-only and role assignment is not read from IdP claims; this may be a blocker for organizations needing full provisioning flows.
If independent proof of ROI is required
- Many of the strongest ROI metrics are published in vendor case studies without full methodology disclosure; buyers should seek independent validation.

Deal disqualifiers (poor fit)

Organizations that require a fully code-centric framework with deep custom architecture control
Organizations with constrained budgets that cannot justify premium licensing
Organizations with extremely frequent UI changes and without disciplined component/test design practices (maintenance may offset productivity gains)

Limitations acknowledged by vendor documentation

SSO authorization gap: SSO integration supports authentication only; authorization must be configured manually.

Limitations frequently mentioned in reviews/community

Licensing and implementation costs are commonly described as high.
Limited customization or missing features are listed in some reviews.
Cloud deployment limitations are reported by some reviewers; specifics vary.
Stability and performance issues are reported in some environments.
Documentation is sometimes viewed as insufficient.

Roadmap / release notes

SSO documentation states availability starting from Release 2025.1.173 (feature timing is explicit in docs).

Where it struggles / is not ideal

Advanced dynamic test generation, highly custom validations, and deep integration logic may be better served by code-centric tools.
Network instability and legacy desktop element identification can increase flakiness and the learning curve, according to some reviewers.

02Why they buy

Validated by customer/reviewer evidence

Visual authoring and usability for non-coders are frequently mentioned in reviews and vendor case studies.
Support quality is commonly cited positively in enterprise reviews.
Governance-related features (audit logs, encryption, on-prem/hybrid deployment) are part of the platform messaging.

Less-validated / needs verification

Vendor claims of high-percentage productivity gains and error reduction should be independently verified before being relied upon in procurement decisions.

Where competitors have clear advantages

Tricentis Tosca: broader enterprise testing coverage and higher market penetration in some segments.
Code-first stacks (Selenium/Playwright): maximum flexibility, cost control, and a mature ecosystem, but require skilled engineers to develop and maintain frameworks.

Why customers chose Leapwork (themes)

Across review platforms and vendor case studies, recurring reasons include:

faster creation of automation for non-coders (visual building blocks)
support for both web and desktop in a single tool
vendor support and professional services cited as influential in successful rollouts
integration into DevOps pipelines

03Field reports

Review platform snapshots (what the market says)

G2: very highly rated on G2. Pros/cons aggregation includes usability and customer support, and common negatives like cost, missing features, customization limits, cloud limitations, and licensing issues.
Capterra: well rated on Capterra.
Trustpilot: poorly rated on Trustpilot.
Sitejabber: poorly rated on Sitejabber.

Interpretation: Business-facing review platforms indicate strong satisfaction among reviewers on those platforms, but consumer-style platforms with very low review volume show sharp negativity. This may reflect selection bias, different user segments, or outlier experiences and should be considered in context.

Direct quotes (positive)

"Reliable tool with excellent support and training"

This reviewer highlights stability, intuitive use, ability to handle both desktop and web apps, and strong support/training.

A vendor-published customer story states that the product is more user friendly than alternatives and lowers the requirement for hardcore developer skills to create flows.

Direct quotes (negative)

"The lack of code design options can be limiting… Unlike Selenium… does not allow for custom scripting… Additionally, the implementation cost is quite high."

"All Talk, No Results- Please Beware and Avoid"

Community posts also express concerns about cost and stability, with some teams deciding to discontinue use based on total cost of ownership or perceived reliability issues.

Why some customers leave / consider alternatives (themes)

Most common churn drivers from community and review excerpts:

cost / licensing viewed as high relative to alternatives
reported buggy behavior or performance issues in some environments
limitations of a low-code/no-code model for complex validations or dynamic logic
maintenance burden when UIs change frequently

Vendor-published customer story

Claims:

Vendor-published materials present substantial reductions in time to market, large-scale hours savings, and multi-fold ROI in one year.

Critical evaluation:

These metrics are vendor-published within a vendor-hosted case study.
Methodology is not fully disclosed in the excerpt (e.g., baseline effort, attribution rules, how "hours saved" is calculated, whether savings were realized or theoretical).
Metrics are useful as directional evidence but should be validated by buyers.

Vendor internal case study webinar

The vendor produced an on-demand webinar describing how its own QA team uses the product to accelerate releases and improve customer experience.

Critical evaluation:

Internal case studies provide product usage context but are not independent evidence. Buyers should treat any ROI or time reduction metrics as illustrative unless corroborated by independently verifiable data.

04Best fit

Company size

Best fit tends to be mid-market to enterprise organizations.

Industries / verticals

Based on vendor and press examples:

Financial services / banking
Healthcare
Retail
Enterprises running packaged apps and complex business workflows

Roles and personas

QA Directors / Heads of Quality Engineering
Test Automation Leads
QA Engineers and citizen automators (manual testers, business analysts) who can author flows
DevOps/Platform teams responsible for execution infrastructure

Qualification criteria (good fit)

Organizations that need automation across desktop and web and prefer a single platform
Organizations that want to scale test authoring beyond code-heavy engineers
Organizations that value vendor support and are willing to budget for it
Organizations that require on-prem or hybrid deployment options

05The pitch

What the product does (objective core value proposition)

The vendor describes the platform as incorporating AI-assisted capabilities and deterministic execution characteristics; such vendor assertions should be treated cautiously and verified independently.

Target market and market positioning

Leapwork primarily targets mid-market to enterprise QA and testing organizations, especially those:

testing packaged enterprise apps (vendor messaging highlights major CRM and ERP ecosystems)
dealing with both legacy desktop and modern web apps
aiming to scale automation authoring beyond a small group of code-heavy test engineers

In reviews, it tends to be adopted by organizations prioritizing:

relatively short onboarding for testers without strong coding skills
centralized governance (platform + agents)
vendor support/professional services for rollout

Get a comprehensive analysis of Leapwork including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →