Lindy Buyer's Checklist: 8 Checks Before Your Team Signs Up

Lindy (often searched as Lindy AI) is worth buying when three things hold: your team already works in Slack (a new install needs a paid Slack plan), you accept that every person who touches it becomes a billed seat, and you can live with a credit pool that pauses work instead of billing overage. Its pricing page starts at $29.99 per user a month for 3,000 credits; on some visits the same page instead opens at $49.99 per user a month for 5,000 credits ^[1]. If your team runs on Microsoft Teams, or needs HIPAA coverage without an Enterprise contract, stop here. Everyone else should clear eight checks before the first invite goes out.

Does your team already live in Slack?

The shared teammate lives in Slack. An admin installs it, each teammate links with one tap, and anyone can then @mention it in a channel thread. New Slack installations need a paid Slack plan ^[2]; a workspace that was already connected can reconnect on a free Slack plan, and Slack's AI agent view also needs a paid plan. Teams that do not use Slack get the personal assistant, not the shared teammate. Lindy's docs list Microsoft Teams as coming soon, with no date attached.

Without Slack, one person still gets a private Lindy through the web app, iMessage or SMS, Lindy's own email address, voice memos, a phone line and a Chrome extension. That extension works in Gmail only; Outlook is listed as coming soon. Workspace routines, the ones that run for the whole team, need the Slack teammate set up. Inside shared channels Lindy uses web search, image generation, public Slack search and Notion, while calendar, email, SMS, reminders and meeting reads stay in each person's DMs.

• Confirm your Slack plan is paid before a new install.
• List who works mainly in Outlook; the extension will not reach them.
• Decide which channels Lindy joins, since private channels need an invite.

Who turns into a billed seat, and at what price

Anyone who uses Lindy takes a seat: signing up directly, joining the workspace, or @mentioning Lindy in Slack for the first time. Slack joiners get a 7-day free trial before their seat is billed, once per person; direct signups are billed right away. Trial seats added through connected integrations can convert to paid seats unless someone removes them before the trial ends, and every admin gets an email with a one-click removal link for each Slack joiner. A curious colleague who tags Lindy once can become a seat. That is the trap.

Seats need active pruning. Removing someone does not refund the month. A removed seat stays active through the paid cycle with no mid-cycle proration, and Lindy will not re-add a person an admin took off. A teammate who signs up separately at lindy.ai lands in a separate workspace without the team's skills, files or meetings, so send invites instead. The pricing page groups the three paid plans under one card called Team, but the plans themselves are Plus, Pro and Max, with Enterprise above them for custom contracts.

Plus starts at $29.99 per user a month for 3,000 credits, yet on some visits the page opens at $49.99 per user a month for 5,000 credits. Check the option on your screen before you buy. By our arithmetic, five people cost $149.95 a month with 15,000 pooled credits on the $29.99 opening, or $249.95 a month with 25,000 pooled credits on the $49.99 opening. Lindy's pricing page prints only monthly prices; it shows no annual plan. Budget month by month.

• Count everyone who might @mention Lindy, not only the planned users.
• Name one admin to watch the Slack-joiner emails during each trial week.
• Note which entry option the pricing page showed you.

What happens when the shared credit pool runs dry

Every seat adds its credits to one workspace balance, and admins can buy top-ups at $10 per 1,000 credits. Monthly plan credits reset each billing cycle and do not roll over; purchased top-ups carry over and never expire. When the pool hits zero, Lindy pauses credit-using actions until the reset or a top-up. No overage bill arrives. Work simply stops, which matters if a routine sends client follow-ups or a receptionist line depends on the same balance.

Credits are not equal. Spend varies by job. Lindy's pricing page gives ranges: everyday asks run 2 to 250 credits, deep work such as a competitor research report 250 to 1,000, and big builds such as complex dashboards 1,000 to 2,500. Lindy's docs say every message in a thread re-reads everything above it, so long threads cost more credits with each turn. A workspace routine spends for the whole team each time it fires. When a task uses far more than usual, Lindy pauses it and asks whether to continue or stop.

Admins and owners can set a monthly credit limit per person. At the cap, that person's credit-using actions pause, although a task that started under the limit runs to completion. Without a cap, one teammate can drain the whole workspace balance. Settings, then Members, shows each person's draw this cycle in a Credits column. By our arithmetic, Pro and Max credits cost between $5.71 and $7.50 per 1,000, against $10 per 1,000 on the entry options and top-ups. Heavy teams should price both.

• Set a cap for every heavy user before the first cycle.
• Start long research in a fresh thread.
• Decide who is allowed to buy top-ups.

What Lindy may do without asking

By default, anything with outside impact waits for approval: sending an email, updating a ticket, posting to another channel, publishing a doc. Read-only lookups from approved sources do not wait. Approvals arrive as Approve and Deny buttons in Slack that the requester or any owner or admin can press. Email drafts land in the user's drafts folder, and outbound phone calls need approval of destination and purpose. Users can loosen all of this as trust grows, and follow-up emails can switch to auto-send.

Guardrails are narrower. Per-integration guardrails come in three settings, Always allow, Require approval and Do not offer, and they apply only in shared Slack threads ^[3]. Web chat, Slack DMs, iMessage and SMS skip them. One guardrail covers every account under an integration, so work and personal Gmail cannot yet follow different rules. MCP guardrails are set per person, and saved API credentials sit outside guardrails entirely. Enterprise adds named approvers. Lindy's docs also warn that it can make mistakes and that people should review its actions before relying on them.

• Map which integrations need Require approval.
• Tell staff that DMs bypass the guardrails.
• Limit who may share API credentials with the workspace.

Where your data goes, and the Enterprise gate for HIPAA

Lindy is sold by Crivello Corp, doing business as Lindy, a company registered in Oregon; that is the party on a BAA or on data-processing terms. The security page lists SOC 2 Type II, audited by Johanson Group, alongside GDPR and PIPEDA, and SOC 2 reports can be requested for vendor review. Data is encrypted in transit and at rest. Lindy states it does not sell data and that neither it nor its providers use customer data to train AI models.

Hosting is in the US. The service is hosted in the United States, so use from other regions means data is processed there; Data Processing Terms for the GDPR processor role are offered. The Privacy Notice names providers that may receive personal information: Anthropic, OpenAI, Perplexity AI, Exa Labs, ElevenLabs and Deepgram, plus Google Cloud, AWS, DigitalOcean, MongoDB and Cloudflare. HIPAA-covered work needs the Enterprise plan with a signed BAA; without a BAA the service is not tailored to HIPAA. Clinics should read our Lindy for healthcare guide before any pilot.

• Send the provider list to whoever runs vendor review.
• Request the SOC 2 report early.
• Keep patient data out of Plus, Pro and Max.

Refunds, renewals and the plan gates

Lindy's Terms state that all purchases are non-refundable . Charges renew automatically until canceled, and canceling, in the account or by contacting Lindy, takes effect at the end of the paid term. The workspace stays active through that cycle with no proration, then credit-using actions stop. Upgrades apply at once; downgrades wait for the end of the term. The Terms also give no guarantee that the service is available at all times. Lindy's docs say it takes all major credit and debit cards through Stripe.

Plan choice matters here. Computer use, where Lindy drives a browser like a person, is the gate that changes most decisions here. It lets Lindy work in a tool that has no ready connection, alongside 3,000+ integrations plus MCP. Computer use comes with Pro and Max, so budget those plans for the people whose workflows depend on a browser. Inbox limits matter for assistants covering several mailboxes. Our Lindy pricing guide puts these gates next to every credit option.

• List the people whose workflows need a browser before picking Pro or Max.
• Count connected inboxes per person against the plan limit.
• Read the cancellation timing before the renewal date.

Run all eight checks in one pilot channel first

Install Lindy in a paid Slack workspace and start in one pilot channel, invite only the people you plan to pay for, and set a credit cap for each of them on day one. During the 7-day Slack trial, watch the Members credits column, try approvals inside a shared thread, and send the provider list to vendor review. If the pool lasts the month and nobody needs Enterprise, scale seat by seat. Our Lindy review covers what the assistant does well once those gates are cleared.