Pipefy runs the boring parts of the modern company.

01 // Who they are nowThe platform behind the platforms

Tuesday morning, somewhere in finance ops.

A purchase order lands in an inbox. In another life, it would have spawned a chain - one analyst, two managers, a Slack DM, a forgotten Excel file, an angry vendor on Friday. In this life, it slides into a Pipefy form. An AI agent reads the invoice, matches it to a contract, flags the variance, routes it for sign-off, posts the receipt back into the ERP. The analyst checks Pipefy at 10:42 and confirms the work that the software has, more or less, already done.

That is Pipefy in 2026: a no-code workflow platform sitting behind the desks of finance, HR, procurement, IT and customer service teams at 4,000+ companies in 150+ countries. It is not flashy. It does not pitch itself as a productivity revolution. It just keeps the back office from drifting into chaos.

"Pipefy is the BPM tool that doesn't require a BPM consultant."- YesPress, on first impression

02 // The problem they sawSpreadsheets are a coping mechanism

For most of the last two decades, business process management software fell into two camps. Either you bought something heavy from an enterprise vendor and spent eighteen months in implementation, or you ran your operations on a duct-taped collection of spreadsheets, shared inboxes and Trello boards. The first option was unaffordable for most teams. The second was unaffordable for the rest of the company.

The cost was rarely on a line item. It showed up in late approvals, missed renewals, onboarding tickets that vanished, vendor invoices paid twice. Operations leaders learned to live with it the way commuters learn to live with potholes.

The most expensive line item in any company is the one nobody bothered to put on the budget.- Field note from a procurement director

03 // The founders' betFrom Curitiba, with skepticism

Alessio Alionco had already sold one company (a classifieds portal called Acessozero, acquired by Apontador in 2012) when he started sketching what would become Pipefy in 2013. He talked to forty small and mid-size business owners. He listened to them describe their workarounds. Seventeen of them paid for the product before there was a product. That is either a stunning act of trust, or, more likely, a clean signal that the problem was worse than anyone wanted to admit.

Alionco's bet was small and stubborn. He believed that the person closest to the work should be the one building the workflow - not an IT consultant six floors away with a Gantt chart. So he and co-founders Kelvin Stinghen, Leandro Johann and Magnus Arantes built a tool around that premise: drag, drop, ship, iterate. They incorporated in 2015. They kept their engineering team in Curitiba, Brazil, because the talent was excellent and the rent was not San Francisco. They later opened a headquarters in San Francisco anyway, because that is where the customers eventually wanted them to be.

"The doer should be the builder. The builder should not need a ticket to think."- Founding bet, paraphrased

04 // The productThe drag-and-drop is the point

Pipefy's interface looks deceptively simple. You build a "pipe" - a visual representation of a process - with phases, fields, conditions and SLAs. Each card moves through phases the way a Kanban ticket does, except the card knows when it is overdue, who it is waiting on, whether the linked vendor in Salesforce is approved, and whether the AI agent has already drafted the approval email.

What separates Pipefy from the long line of Kanban-flavored productivity tools is the back end. The platform is built to handle audit trails, role-based access, conditional logic, integrations with ERP and HRIS systems, white-labeling for enterprise rollouts, and increasingly, autonomous AI agents that can read documents and execute decisions inside a workflow.

A workflow tool that hides its complexity is doing its job. A workflow tool that shows it off is trying to charge you for it.- Operating principle, observed

05 // The proofNames you recognize, processes you don't

The customer roster reads like the kind of list a sales team would tattoo on its own forearm. IBM. Volvo. GE Healthcare. Lacoste. Rivian. Magalu. Itau. Nubank. None of them bought Pipefy because they wanted to look modern in a press release. They bought it because the cost of running their procurement, onboarding or IT service flows on a spreadsheet had crossed a quiet, internal threshold.

The investors followed the same logic. Valor, Redpoint and 500 Startups in the seed round. Insight Partners through the middle stages. SoftBank's Latin America Fund leading the $75 million Series C in October 2021, with a $50 million check that pulled the total raise above $138 million at the time, and total funding to date north of $200 million.

"It is not glamorous software. It is software that pays for itself by the end of the second quarter."- A CFO, off the record

06 // The missionDoers, not deciders

The shorthand version is on the marketing site: empower the people closest to the work to build, run and improve the workflows that move their businesses forward. The longer version is more interesting. Pipefy is built around a slightly contrarian belief: that the operations analyst with three years on the job and a grudge against the current onboarding process is probably better positioned to redesign it than the systems integrator brought in for ninety days at three times the rate.

Empowering that analyst is partly cultural and partly technical. Technically, it means a visual builder, a templates library, a permissions model and an audit trail. Culturally, it means selling a platform to operations leaders, not just CIOs - and trusting that they will not blow up the company if you hand them the keys.

07 // Why it matters tomorrowAI agents need somewhere to live

Every enterprise software roadmap in 2026 talks about AI agents. Most of them have not figured out where those agents will live. A chatbot is a feature, not a workflow. An agent that drafts an invoice approval is interesting; an agent that drafts the approval, routes it for sign-off, attaches the receipt to the contract record, and gets out of the way is a system. The second kind requires a substrate - a place where work has structure, state and accountability.

Pipefy has been building exactly that substrate, almost accidentally, for a decade. Now it is the obvious place to drop AI agents in. The workflow is already there. The integrations are already there. The audit trail and permissions are already there. The customers, who used to come for the Kanban view, now stay for the autonomous execution.

The companies that wired up their workflows in 2018 are the same ones that get to deploy AI agents in 2026. Everyone else is going back to step one.- A thesis, gathering interest

08 // Back to Tuesday morningThe same purchase order, one year later

Tuesday morning, somewhere in finance ops. The purchase order lands. The form is the same. The card moves through the same six phases. The audit trail is the same.

What is different is the analyst. She has not opened her email inbox since 9:14. She is not chasing approvals. She is building the next process - the one for onboarding a new vendor, the one she has been complaining about for two years. She drags. She drops. She publishes. She moves on. The boring parts of the company are running themselves, which is what they should have been doing all along.

09 // ShareSend this to someone who still uses 14-email approvals