Pipefy

Name: Pipefy
Brand: Pipefy
Rating: 4.2 (846 reviews)

Pipefy is a SaaS platform for designing, running, and improving business processes using configurable workflows, forms, automation rules, integrations, and AI assistants to standardize request intake, route approvals, and provide SLA visibility and reporting.

Est 2014|Valuation $795M|Raised $153.2M|107 Ref Customers

LinkedIn 117K|Web traffic 1.6M|FTEs 610|HQ San Francisco, California, US

MarketsProcure-to-Pay Business Process Management (BPM)Workflow Automation

Published Oct 23, 2026

01Common complaints

When deep ITSM/CMDB capabilities are required
- Platforms such as ServiceNow or Jira Service Management combined with asset tooling typically provide stronger support for ITIL-heavy ITSM and complex enterprise IT operations.
When workflows require complex logic beyond no-code limits
- Multiple reviews indicate ceilings around complex customization and logic; organizations requiring extensive developer extensibility should evaluate low-code or developer-focused platforms.
When the organization has high sensitivity to vendor support/billing risk
- Trustpilot and other complaint sources include allegations of support and billing problems. Even if such complaints are not representative of enterprise accounts, procurement teams should perform pilot tests, confirm cancellation terms in writing, and negotiate support SLAs.
When the primary need is project/task collaboration rather than process orchestration
- Solutions such as Asana or monday.com may be simpler, more transparent in pricing, and better aligned with project-centric work.
When automation/API volumes are extremely high
- Add-on packs for automation actions and API calls may become a recurring cost center; organizations should evaluate expected transaction volumes and compare pricing models across vendors.

Based on reviewed sources (reviews and help-center notes):

Complex logic/customization ceilings reported by multiple reviewers.
Integration friction reported in several reviews.
Mobile parity gaps: mobile app functionality is reported as less complete than the web application in some reviews.
Governance overhead at scale: administrative efforts increase with wider adoption.
Usage limits and add-ons: automation/API usage limits exist and may require paid add-ons; vendor documentation indicates add-ons are non-refundable.

Roadmap visibility: Public roadmap details and timelines were not found in the sources reviewed; customers may need to rely on vendor communications or community updates.

1. **When deep ITSM/CMDB capabilities are required** - Platforms such as ServiceNow or Jira Service Management combined with asset tooling typically provide stronger support for ITIL-heavy ITSM and complex enterprise IT operations. 2. **When workflows require complex logic beyond no-code limits** - Multiple reviews indicate ceilings around complex customization and logic; organizations requiring extensive developer extensibility should evaluate low-code or developer-focused platforms. 3. **When the organization has high sensitivity to vendor support/billing risk** - Trustpilot and other complaint sources include allegations of support and billing problems. Even if such complaints are not representative of enterprise accounts, procurement teams should perform pilot tests, confirm cancellation terms in writing, and negotiate support SLAs. 4. **When the primary need is project/task collaboration rather than process orchestration** - Solutions such as Asana or monday.com may be simpler, more transparent in pricing, and better aligned with project-centric work. 5. **When automation/API volumes are extremely high** - Add-on packs for automation actions and API calls may become a recurring cost center; organizations should evaluate expected transaction volumes and compare pricing models across vendors. Based on reviewed sources (reviews and help-center notes): - **Complex logic/customization ceilings** reported by multiple reviewers. - **Integration friction** reported in several reviews. - **Mobile parity gaps**: mobile app functionality is reported as less complete than the web application in some reviews. - **Governance overhead at scale**: administrative efforts increase with wider adoption. - **Usage limits and add-ons**: automation/API usage limits exist and may require paid add-ons; vendor documentation indicates add-ons are non-refundable. **Roadmap visibility:** Public roadmap details and timelines were not found in the sources reviewed; customers may need to rely on vendor communications or community updates.

Deal disqualifiers (poor fit)

The organization requires extremely complex branching logic or deep custom application development without constraints.
The organization requires fully transparent pricing without sales engagement.
The organization requires a complete ITSM suite with built-in asset/CMDB capabilities out of the box.

02Why they buy

Differentiators supported by customer/reviewer signals

No-code workflow creation that reviewers often describe as enabling faster setup and adoption.
Fit for standardized request workflows (intake, routing, approvals, visibility) compared to tools focused on task lists.

Differentiators primarily vendor-claimed (validate during evaluation)

Vendor claims around the breadth of "AI Agents" capabilities and governance for agent orchestration.
ROI metrics reported in a commissioned TEI study (for example, 260% ROI and payback under 6 months) that should be validated against an organization's baseline.

Where competitors may have clear advantages

monday.com/Asana: Collaboration-focused UX and transparent entry pricing.
ServiceNow: Enterprise ITSM depth, larger ecosystem for IT operations, and mature enterprise platform governance.
Kissflow: Platform-style low-code app building, but with a higher entry price.

03Field reports

This section includes both positive feedback and criticism, with direct quotes where available.

Review platform highlights (G2, Capterra, Gartner Peer Insights)

G2 (example review excerpt):

Positive: “Pipefy allows us to create and automate workflow every week without needing deep technical skills…”
Negative (same review): “Customization can be limited in some areas especially when trying to build complex logic.”

Capterra (examples):

Positive: “It gives us flexibility in process management” — Capterra listings are well rated overall. The reviewer emphasized configurability and that “the Pipefy team was easy to work with…”.
Mixed/negative points appearing in excerpts include:
- “Integration is a bit problematic” and “Needs a lot of bandwidth to operate.”
- “its mobile app is not as complete as the web app version.”
- “I cannot add many users to a single workflow instance” and “job progress is not updated in real-time…”, plus comments about community resources.

Gartner Peer Insights (example excerpts):

Mixed: “Great for repeatable, cross-team processes, but expect to invest in admin governance as usage grows.”
Positive: “Streamlined workflows, easy to use, and great for managing team processes…”
Mixed: “Automation Features Simplify Workflow Setup But May Challenge Complex Customization.”

**G2 (example review excerpt):** - Positive: “Pipefy allows us to create and automate workflow every week without needing deep technical skills…” - Negative (same review): “Customization can be limited in some areas especially when trying to build complex logic.” **Capterra (examples):** - Positive: “It gives us flexibility in process management” — Capterra listings are well rated overall. The reviewer emphasized configurability and that “the Pipefy team was easy to work with…”. - Mixed/negative points appearing in excerpts include: - “Integration is a bit problematic” and “Needs a lot of bandwidth to operate.” - “its mobile app is not as complete as the web app version.” - “I cannot add many users to a single workflow instance” and “job progress is not updated in real-time…”, plus comments about community resources. **Gartner Peer Insights (example excerpts):** - Mixed: “Great for repeatable, cross-team processes, but expect to invest in admin governance as usage grows.” - Positive: “Streamlined workflows, easy to use, and great for managing team processes…” - Mixed: “Automation Features Simplify Workflow Setup But May Challenge Complex Customization.”

Customer support sentiment (mixed)

Some reviews praise support: “Support team is exceptional.”
However, Trustpilot includes severe complaints:
- “No support whatsoever… they will take the money and will leave you to articles…”
- “After cancellation, I was charged again… their team disappeared. 0/10, feels like a scam.”

Interpretation caution: Trustpilot can include non-enterprise buyers and edge cases; nonetheless, billing/support complaints represent a risk signal that procurement teams should test early (for example, trial billing, cancellation terms, support SLA clarity).

- Some reviews praise support: “Support team is exceptional.” - However, Trustpilot includes severe complaints: - “No support whatsoever… they will take the money and will leave you to articles…” - “After cancellation, I was charged again… their team disappeared. 0/10, feels like a scam.” **Interpretation caution:** Trustpilot can include non-enterprise buyers and edge cases; nonetheless, billing/support complaints represent a risk signal that procurement teams should test early (for example, trial billing, cancellation terms, support SLA clarity).

Why customers choose Pipefy (themes)

Across review platforms, common reasons cited for selection include:

No-code setup and faster workflow creation
Standardization and visibility for cross-team processes
Availability of templates for common workflows

Why some customers leave or hesitate (themes)

Recurring concerns across review excerpts and community sentiment include:

Limits when implementing complex logic or customization
Integration friction
Expectations for real-time updates not always being met
Variability in support and billing experience

Forrester Total Economic Impact (TEI) — commissioned study

The vendor references a commissioned TEI study with outcomes framed as significant ROI and time savings for a modeled organization.

Critical evaluation:

Commissioned TEI studies are typically based on a composite organization model. The vendor indicates the study was built from a small number of vendor-identified interviewees to create a composite.
These figures should be treated as directional rather than guaranteed. Procurement teams should request the full methodology, interview sample characteristics, which benefits were measured versus estimated, and sensitivity analysis for the prospective customer's environment (for example, with fewer workflows, lower volumes, or higher integration complexity).

The vendor references a commissioned TEI study with outcomes framed as significant ROI and time savings for a modeled organization. **Critical evaluation:** - Commissioned TEI studies are typically based on a composite organization model. The vendor indicates the study was built from a small number of vendor-identified interviewees to create a composite. - These figures should be treated as directional rather than guaranteed. Procurement teams should request the full methodology, interview sample characteristics, which benefits were measured versus estimated, and sensitivity analysis for the prospective customer's environment (for example, with fewer workflows, lower volumes, or higher integration complexity).

Vendor-published customer metrics in marketing content

The vendor's site includes examples such as implemented counts for AI features and efficiency gains cited in customer testimonials.

Critical evaluation:

These items are vendor-provided metrics and testimonial-based; they were not independently validated in the public sources reviewed. Procurement teams should request underlying definitions (for example, the vendor definition of an "AI Agent," baseline measurements, timeframe, and the operational definition of "efficiency").

The vendor's site includes examples such as implemented counts for AI features and efficiency gains cited in customer testimonials. **Critical evaluation:** - These items are vendor-provided metrics and testimonial-based; they were not independently validated in the public sources reviewed. Procurement teams should request underlying definitions (for example, the vendor definition of an "AI Agent," baseline measurements, timeframe, and the operational definition of "efficiency").

04Best fit

Company sizes

Based on product design, pricing structure, and review-platform mix:

Most suitable: Mid-sized to large organizations, particularly those standardizing internal service workflows.
Also plausible: Smaller mid-sized teams with complex operational workflows and a need for structured approvals/SLAs.
Large enterprise: Feasible, but administrative governance and platform administration become critical.

Industries and verticals

Frequently referenced by vendor positioning and review samples:

Professional services, retail, consumer goods
Shared services organizations
Any industry requiring structured request intake (HR, procurement, IT ops)

Roles/personas

Economic buyers: COO, CIO/IT leadership (for governance), Heads of Shared Services, HR Ops, Finance Ops, Procurement leaders
Admins/builders: Ops excellence/process owners, business systems analysts, RevOps/IT ops, citizen builders
End users: Requesters and approvers across the business

Qualification criteria (suitable fit)

The organization has repeatable workflows with clear states, SLAs, approvals, and audit requirements.
The organization prefers business-led workflow configuration with IT guardrails.
The organization can assign ownership for workflow governance and template standards.

05The pitch

What the product does (objective value proposition)

Pipefy is a SaaS platform for designing, running, and improving business processes using configurable workflows ("pipes"), forms, automation rules, integrations, and, in newer positioning, features the vendor describes as AI assistants/agents. In practice, it is typically used to standardize request intake (HR requests, procurement requests, IT service requests), route approvals, manage SLAs, and provide visibility via dashboards and reporting.

Pipefy's marketing positions the product as an "AI Agents" capability and as a layer for unifying workflows, data, and governance in addition to its traditional BPM/workflow functionality.

Target market and market positioning

Primary target: Mid-market to enterprise operations teams that require repeatable, cross-team workflows without heavy engineering dependency.
Common departments: HR, Finance/AP, Procurement, IT service/request management, Legal, Shared Services.
Positioning themes: Emphasis on no-code/citizen development combined with governance and security; vendor messaging highlights an ability to manage processes end-to-end rather than only project management.

- **Primary target:** Mid-market to enterprise operations teams that require repeatable, cross-team workflows without heavy engineering dependency. - **Common departments:** HR, Finance/AP, Procurement, IT service/request management, Legal, Shared Services. - **Positioning themes:** Emphasis on no-code/citizen development combined with governance and security; vendor messaging highlights an ability to manage processes end-to-end rather than only project management.

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

Download full report →