Lindy AI Raises $75M Series B for No-Code Agent Builder
Lindy AI has closed a $75M Series B led by Andreessen Horowitz, bringing total funding to $110M. The company is using the capital to expand its no-code AI agent marketplace and deepen integrations with enterprise CRM and ERP systems.
Original sourceLindy AI, the no-code platform that lets non-technical users build and deploy AI agents, has raised $75M in a Series B round led by Andreessen Horowitz. The raise brings Lindy's total funding to $110M and signals continued investor appetite for platforms that abstract agent-building away from engineers and toward business operators.
The company plans to use the funding to expand its enterprise agent marketplace — a library of pre-built agents users can deploy and customize — and to deepen native integrations with CRM platforms like Salesforce and HubSpot and ERP systems like SAP and NetSuite. The bet is that enterprise adoption of AI agents is bottlenecked not by model capability but by integration complexity and the gap between IT teams and the business users who actually need the automation.
Lindy competes in a crowded no-code automation space that includes Zapier's AI layer, Make, and a growing number of agent-specific platforms like Relay.app and Cassidy. What differentiates Lindy's pitch is its focus on agents that can reason and take multi-step actions across integrated tools, rather than simple trigger-action automation. Whether that distinction holds up at enterprise scale is the question this funding round is designed to answer.
The a16z backing is notable given the firm's active portfolio in the agentic AI space, including investments in competing or adjacent platforms. The enterprise marketplace expansion suggests Lindy is moving up-market deliberately, which will test whether its no-code simplicity can survive the compliance, security, and customization demands that enterprise buyers typically bring.
Panel Takes
The Founder
Business & Market
“The buyer here is a VP of Operations or RevOps lead pulling from a software automation budget — that's a real, existing budget line, which is more than most agent startups can say. The moat question is what keeps this from being eaten by Salesforce Flow or SAP's own automation layer once those teams ship 80% of the value for free to existing customers. The enterprise marketplace is a smart expansion move only if Lindy gets sticky enough through workflow integration before the platform players wake up — and a16z's check gives them maybe 18 months to find out.”
The Skeptic
Reality Check
“No-code agent builders are a category that demos in 90 seconds and collapses the moment a real enterprise workflow touches it — conditional logic, error handling, and compliance requirements are where these tools go to die. The specific scenario that kills Lindy is an enterprise IT team asking for SSO, audit logs, and a data residency guarantee on the same day, because no-code platforms consistently underbuild the infrastructure layer while overbuilding the drag-and-drop surface. What kills this in 12 months is Salesforce shipping an Agentforce no-code tier that's already inside the CRM where the data actually lives — Lindy's biggest integration is also its biggest existential threat.”
The PM
Product Strategy
“The job-to-be-done is clear — let a business operator automate a multi-step workflow without filing an IT ticket — and that's a real, painful job with an obvious budget. The risk is that 'agent marketplace' is a feature checklist dressed up as a product strategy: a library of pre-built agents only works if the agents are opinionated enough to be immediately useful, not so generic that users spend three hours configuring them before getting value. If Lindy's onboarding puts a non-technical user at a working, live agent in under 10 minutes without touching a configuration screen, that's a ship — but marketplace expansions historically make onboarding worse, not better.”
The Futurist
Big Picture
“The thesis Lindy is betting on is falsifiable: enterprise AI adoption is blocked by the integration and operator gap, not model capability, and the team that wins is the one that owns the middleware layer between SaaS systems and business-logic agents before the SaaS platforms close that gap themselves. The second-order effect if this works is interesting — it shifts who in an organization has the power to build automation from IT and RevOps engineers to individual contributors and department heads, which is a genuine power redistribution inside companies, not just a productivity story. The dependency that has to hold is that Salesforce, SAP, and HubSpot don't each ship a competent native agent layer in the next 24 months, which is a dependency I wouldn't want to stake $75M on.”