Name: Creatio
Brand: Creatio
Rating: 4.7 (909 reviews)

Published Oct 23, 2026

01Common complaints

Organizations should consider alternatives if any of the following apply: - The primary requirement is a simple CRM with minimal configuration and rapid time-to-value; other vendors may provide faster deployment for basic sales pipelines. - The organization lacks implementation capacity or governance capability; success with this platform is frequently dependent on partner quality and careful requirements analysis. - Users are highly sensitive to user experience and performance constraints in specific portal or mobile scenarios; validate performance characteristics for expected data volumes and usage patterns before a full rollout. - The organization requires clearly documented, externally verified compliance for niche regulations (e.g., HIPAA, PCI) and those certifications or attestations are not present in the vendor documentation; confirm scope of SOC 2 / ISO 27001 reports and additional compliance measures during vendor evaluation.

Deal disqualifiers (poor fit)

Requirement for a minimal-configuration CRM for a small sales team with no internal implementation capacity
Inability to allocate implementation resources while expecting low-code to obviate complexity

Commonly cited limitations

Learning curve and initial setup complexity noted by multiple independent reviewers.
Documentation and training resources may lag rapid product changes in some areas.
Integration connector gaps for particular systems can increase integration effort even where APIs are available.
User experience and performance complaints in certain deployments, particularly in some portal or high-latency scenarios.

Roadmap / future features

The vendor highlights an emphasis on AI-related features and agent-like capabilities in public messaging. Specific roadmap timelines and commitments were not validated in the material reviewed; enterprise buyers should request formal roadmap details under appropriate confidentiality arrangements and confirm which features are generally available versus in preview.

02Why they buy

Differentiators supported by customer evidence

Combined workflow and CRM capability: reviewers commonly cite the platform's visual workflow building and the ability to customize process flows alongside CRM data.
Autonomy for admins and business users: multiple reviewers note that many changes and automations can be implemented with low-code tools, though non-trivial customizations can require development resources.

Where competitors clearly have advantages

Ecosystem breadth: larger vendors often provide a wider partner ecosystem and more third-party applications.
Out-of-box simplicity: some competitors are better suited for smaller teams needing minimal setup and faster time-to-value.

Why customers chose Creatio vs alternatives

In third-party reviews, some customers reported selecting the platform because it was more affordable for their use case and offered a level of customization perceived as easier to implement than some alternatives; other reviewers noted trade-offs in breadth compared with larger ecosystems.

03Field reports

Review-platform sentiment (G2)

The product is very highly rated on G2; review volume on the platform is substantial. Independent review platforms list both positive and critical feedback; platform metadata and review sourcing should be considered when interpreting scores. Representative user feedback summarized from reviews: - Positive themes: reviewers note the platform's low-code tools and visual designers for workflow building, and the availability of APIs and integration options. - Critical themes: some reviewers cite the user interface as dated and note a steep learning curve for initial setup and customization.

TrustRadius (pros/cons, implementation reality)

TrustRadius reviews highlight the platform's flexibility, visual process building, and availability of marketplace applications. Reported drawbacks include documentation that can lag product updates, connector gaps for specific integrations, and challenges in governance and prioritization due to the platform's breadth. An implementation example on TrustRadius indicates that outcomes can depend heavily on implementation partners; one reviewer reported hiring additional analysts after an implementation that required more internal resources than initially anticipated.

Trustpilot (polarized feedback)

Trustpilot feedback sampled for this report shows a polarized distribution, with both positive and negative experiences. Negative themes often derive from portal deployments or specific implementations and include comments about navigation, performance, and cases where no-code expectations did not match implementation reality. Positive themes include that some users find the platform learnable and that certain features (including AI-related capabilities) are available. Interpretation caution: third-party review platforms can reflect a range of deployment contexts (for example, consumer-facing portals built on the platform versus enterprise CRM deployments), so reviewers should consider the context of each review when assessing product suitability.

Why some customers leave / churn signals

Published and third-party reviews do not provide a direct churn metric, but common drivers for dissatisfaction and potential churn include:

Performance issues at scale or in specific UI patterns
Mismatch between no-code expectations and actual implementation complexity
Strong dependence on implementation partners and variability in partner quality

Vendor-published outcomes (examples)

Vendor-published case study summaries include reported outcomes such as:

A national sports retailer: an increase in average order size and a deployment supporting a large user base with a small administrative team.
A major online property platform: reported increases in lead volume and conversion metrics.
A large national supplier/retailer: a broad rollout across many locations in a short timeframe.

Critical evaluation of case study claims

These are vendor-published summaries. Important considerations when assessing such claims include: - Methodology and baselines for reported improvements are typically not provided in short summaries. - Attribution: clarify what portion of results derived from process changes, training, data cleanup, or other parallel initiatives. - Timeline details: confirm whether reported timelines include discovery, integration, data migration, and full user adoption phases. Buyers should request full case study documentation, references, and clarify measurement methodology and sustainability of results.

Mixed results / projects that struggled

Public vendor materials rarely highlight failed implementations. Independent review platforms include examples where implementations encountered challenges related to partner selection, requirements analysis, and internal resourcing.

04Best fit

Company size

Typical strong fit: mid-market to enterprise organizations where processes vary by region, product line, or channel and require orchestration.
SMB suitability: possible for smaller teams that can invest in configuration and governance, but some reviewers find the platform more complex than alternatives tailored to SMBs.

Industries / verticals

The vendor markets the platform across multiple verticals, including banking, insurance, manufacturing, and public sector use cases.

Roles / personas

Business operations leaders (e.g., RevOps, Sales Ops, Service Ops)
CRM administrators and process owners
IT application owners responsible for integration and governance
Business users who build workflows with low-code tools (citizen developers)

Pain points addressed

Fragmented CRM and workflow tools across departments
Slow delivery of workflow changes in traditional CRM environments
Requirement for configurable processes without full custom development in every case

Deal qualifiers (strong fit)

A clear workflow transformation agenda (beyond basic sales pipeline tracking)
Availability of a product owner, admin, and integration support resources
Willingness to invest in governance for low-code/no-code use at scale

05The pitch

What the product does (core value proposition)

Creatio describes its product as a CRM and workflow platform that combines CRM applications (sales, marketing, service) and workflow/process automation on a single low-code/no-code platform, and includes AI-related features marketed as "AI agents." The practical value proposition typically observed in vendor materials and user feedback is: - Replace or extend traditional CRM suites with a configurable system that combines workflow automation and CRM functionality. - Allow business users and IT teams to build and extend applications and processes using visual designers, with the option to add code where required. The vendor frames the product as an automation-centric CRM suite (CRM + BPM/workflow automation + low/no-code tooling).

Target market and positioning

Primary fit: mid-market to enterprise organizations that require significant customization, workflow orchestration, and cross-department process automation (sales, service, marketing, operations).
Secondary fit: smaller teams may adopt the platform, but independent reviews indicate it can be complex for organizations seeking a minimal-configuration CRM.

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

Download full report →

Published Oct 23, 2026

01Common complaints

Organizations should consider alternatives if any of the following apply:

The primary requirement is a simple CRM with minimal configuration and rapid time-to-value; other vendors may provide faster deployment for basic sales pipelines.
The organization lacks implementation capacity or governance capability; success with this platform is frequently dependent on partner quality and careful requirements analysis.
Users are highly sensitive to user experience and performance constraints in specific portal or mobile scenarios; validate performance characteristics for expected data volumes and usage patterns before a full rollout.
The organization requires clearly documented, externally verified compliance for niche regulations (e.g., HIPAA, PCI) and those certifications or attestations are not present in the vendor documentation; confirm scope of SOC 2 / ISO 27001 reports and additional compliance measures during vendor evaluation.

Deal disqualifiers (poor fit)

Requirement for a minimal-configuration CRM for a small sales team with no internal implementation capacity
Inability to allocate implementation resources while expecting low-code to obviate complexity

Commonly cited limitations

Learning curve and initial setup complexity noted by multiple independent reviewers.
Documentation and training resources may lag rapid product changes in some areas.
Integration connector gaps for particular systems can increase integration effort even where APIs are available.
User experience and performance complaints in certain deployments, particularly in some portal or high-latency scenarios.

Roadmap / future features

02Why they buy

Differentiators supported by customer evidence

Combined workflow and CRM capability: reviewers commonly cite the platform's visual workflow building and the ability to customize process flows alongside CRM data.
Autonomy for admins and business users: multiple reviewers note that many changes and automations can be implemented with low-code tools, though non-trivial customizations can require development resources.

Where competitors clearly have advantages

Ecosystem breadth: larger vendors often provide a wider partner ecosystem and more third-party applications.
Out-of-box simplicity: some competitors are better suited for smaller teams needing minimal setup and faster time-to-value.

Why customers chose Creatio vs alternatives

03Field reports

Review-platform sentiment (G2)

Representative user feedback summarized from reviews:

Positive themes: reviewers note the platform's low-code tools and visual designers for workflow building, and the availability of APIs and integration options.
Critical themes: some reviewers cite the user interface as dated and note a steep learning curve for initial setup and customization.

TrustRadius (pros/cons, implementation reality)

An implementation example on TrustRadius indicates that outcomes can depend heavily on implementation partners; one reviewer reported hiring additional analysts after an implementation that required more internal resources than initially anticipated.

Trustpilot (polarized feedback)

Interpretation caution: third-party review platforms can reflect a range of deployment contexts (for example, consumer-facing portals built on the platform versus enterprise CRM deployments), so reviewers should consider the context of each review when assessing product suitability.

Why some customers leave / churn signals

Published and third-party reviews do not provide a direct churn metric, but common drivers for dissatisfaction and potential churn include:

Performance issues at scale or in specific UI patterns
Mismatch between no-code expectations and actual implementation complexity
Strong dependence on implementation partners and variability in partner quality

Vendor-published outcomes (examples)

Vendor-published case study summaries include reported outcomes such as:

A national sports retailer: an increase in average order size and a deployment supporting a large user base with a small administrative team.
A major online property platform: reported increases in lead volume and conversion metrics.
A large national supplier/retailer: a broad rollout across many locations in a short timeframe.

Critical evaluation of case study claims

These are vendor-published summaries. Important considerations when assessing such claims include:

Methodology and baselines for reported improvements are typically not provided in short summaries.
Attribution: clarify what portion of results derived from process changes, training, data cleanup, or other parallel initiatives.
Timeline details: confirm whether reported timelines include discovery, integration, data migration, and full user adoption phases.

Buyers should request full case study documentation, references, and clarify measurement methodology and sustainability of results.

Mixed results / projects that struggled

04Best fit

Company size

Typical strong fit: mid-market to enterprise organizations where processes vary by region, product line, or channel and require orchestration.
SMB suitability: possible for smaller teams that can invest in configuration and governance, but some reviewers find the platform more complex than alternatives tailored to SMBs.

Industries / verticals

The vendor markets the platform across multiple verticals, including banking, insurance, manufacturing, and public sector use cases.

Roles / personas

Business operations leaders (e.g., RevOps, Sales Ops, Service Ops)
CRM administrators and process owners
IT application owners responsible for integration and governance
Business users who build workflows with low-code tools (citizen developers)

Pain points addressed

Fragmented CRM and workflow tools across departments
Slow delivery of workflow changes in traditional CRM environments
Requirement for configurable processes without full custom development in every case

Deal qualifiers (strong fit)

A clear workflow transformation agenda (beyond basic sales pipeline tracking)
Availability of a product owner, admin, and integration support resources
Willingness to invest in governance for low-code/no-code use at scale

05The pitch

What the product does (core value proposition)

Replace or extend traditional CRM suites with a configurable system that combines workflow automation and CRM functionality.
Allow business users and IT teams to build and extend applications and processes using visual designers, with the option to add code where required.

The vendor frames the product as an automation-centric CRM suite (CRM + BPM/workflow automation + low/no-code tooling).

Target market and positioning

Primary fit: mid-market to enterprise organizations that require significant customization, workflow orchestration, and cross-department process automation (sales, service, marketing, operations).
Secondary fit: smaller teams may adopt the platform, but independent reviews indicate it can be complex for organizations seeking a minimal-configuration CRM.

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

Download full report →