What is Lindy?
Lindy trades control for time-to-first-automation, and that trade is the entire buying decision. You describe a role in plain English, connect the apps it needs (email, calendar, CRM, Slack), and the platform infers the triggers, memory, and tool calls instead of making you wire each step the way Zapier does. The thing you are actually buying is the inference step. When the agent guesses your workflow correctly you ship in an afternoon. When it guesses wrong you have less visibility into why than you would with an explicit Zapier or Make build, because the logic you would inspect was never written down. That is the central tension, and where you land on it should decide the purchase.
Where it earns its rating
The 4.3 reflects strength in a narrow band and weakness outside it. Lindy is genuinely good at email and calendar work: inbox triage, meeting scheduling, follow-up drafting all have strong defaults that hold up without tuning. The CRM connectors (HubSpot, Salesforce) make it a real sales-ops tool rather than a demo. Multi-agent handoff works for the canonical chain (a research agent feeds an outreach agent feeds a CRM-update agent), and the approval gates on sensitive actions are not an afterthought, which matters the first time an agent is one step from emailing a customer.
The rating is not higher because the inference model that is the selling point is also the failure mode. On workflows with branching logic or strict ordering, the natural-language definition gives you less determinism and less debuggability than an explicit builder. Lindy is a 4.3 for inbox-and-CRM ops and roughly a 3 for anything that needs auditable branching.
Who should buy it, and who should not
Buy it if you are a sales-ops, founder-led GTM, or small-to-mid customer-success team whose automations are mostly email, calendar, and CRM updates, and you have no appetite for owning an integration platform. That is the band where Lindy beats wiring it yourself.
The recommendation flips in two cases. If your workflow has compliance-grade branching or hard ordering requirements, pick an explicit builder (Make for branching depth, Zapier for linear simplicity); the debuggability you give up with Lindy costs more than the setup time you save. And if you already run an integration platform your team knows, adding Lindy is a second system to operate, not a shortcut. The candid pitch is narrow on purpose: in its band it is excellent, and outside it the natural-language abstraction is a liability, not a feature.
Pricing
A free tier covers solo evaluation. Team plans start around $50/mo per seat, with usage-based credits metering agent runs on top of the seat fee. Model the credit burn before you commit at team scale; the seat price is the predictable part and the run-based credits are the part that surprises finance on a high-volume workflow.