Your customer success work, in one place with the rest of the company.
TulipFarm is an AI workspace where customer success teams keep account health, onboarding plans, QBR notes and renewal dates. Agents help with recurring work, and other teams use the same records.
Public beta, open to everyone. Your first signup includes $50 in free credits.
No account needed. The tour runs in your browser and doesn't connect to your accounts.
Where customer success meets the other teams.
Customer success trades work with Support, Sales, Product and Finance. Each handoff stays in the same workspace, so the next team picks up the original record.
Coming in
SupporttoCustomer success
Escalations
Support logs escalations in a shared Escalations table. Each row names the account, so you and Clover can see open issues before a check-in.
TulipFarm for customer support teamsBack to the mapFinancetoCustomer success
Contract dates
Finance keeps contract and invoice dates in a table it shares with you. Your renewal reminders read those dates, so nobody has to keep a second copy up to date.
TulipFarm for finance teamsBack to the map
Going out
Customer successtoSales
Expansion notes
When an account asks about more seats or another team, add a row to a table you share with Sales. The row keeps the account, the request and your notes, so Sales starts with the context.
TulipFarm for sales teamsBack to the mapCustomer successtoProduct
Feature requests
Log feature requests from customer calls in a table you share with Product. Each row records the account and its renewal date, so Product can see which requests come from accounts up for renewal.
TulipFarm for product teamsBack to the map
The customer success work that comes back every week.
Records go in tables, plans and call notes in Files, and the recurring work to agents or workflows. Set a job up once in chat, and the next run and the next teammate start from there.
In these examples, Clover is your team's customer success agent.
Account health table
When: Ongoing
Keep every account in one table, with owner, plan, renewal date, health and last check-in. Ask in chat which accounts are marked at risk or haven't had a check-in this month.
Onboarding plans
When: Each new customer
Give each new customer a project that holds its onboarding plan, files, instructions and chats. Ask chat to write the plan as a Word document in Files, or to propose a Google Doc that you approve before it's uploaded.
QBR prep
When: Each quarter
Ask Clover to gather an account's health notes, open escalations and feature requests into a QBR outline in a private task. Then ask chat to turn the outline into a PowerPoint file in Files, or to propose Google Slides that you approve before they're uploaded.
Renewal reminders
When: Mondays
Schedule Clover to run on Monday mornings. It reads the renewal dates in the Accounts table and drafts a list of renewals due in the next 90 days in a private task for you to review.
Expansion notes to Sales
When: Each request
Set up an expansion workflow in chat. When you mark an account Expansion, Clover drafts a note for Sales, the run waits for your review, then Slack gets only the message you approved.
TulipFarm doesn't update your CRM or reply to customers from your help desk. Your team still works with customers in the tools it uses today.
One expansion request, start to finish.
An example: Priya, a customer success manager, hears on a check-in call that one of her accounts wants to add a second team. Here's how the request reaches Sales and where she stays in charge.
What the workflow and run statuses mean
Saved
Priya saved the workflow from chat. Nothing runs yet.
Activated
She turned it on. A change to an account row can now start a run.
Run started
Priya marked the account Expansion, so a run began.
Completed
The run sent the approved note to #sales and finished. Sales picks up from the note and the account row.
Set up a workflow: when an account with Green health is marked Expansion in the Accounts table, have Clover draft a #sales note from the account row and my call notes. Check with me before anything goes to Slack.
- Trigger
Priya sets the account's stage to Expansion in the Accounts table.
Stage set to Expansion - Condition
Checks whether the account's health is Green. If it isn't, the run stops here.
Passed: health is Green - Agent
Clover reads the account row and Priya's call notes in Files.
Read row and notes - Agent
Clover drafts a short #sales note with the request, the main contacts and the renewal date.
Draft ready - Review
The run pauses until Priya reviews the draft and responds.
Priya responded - Slack
Posts the note to #sales once Priya approves the exact message. Nothing is sent before that.
Approved, sent to #sales
Completed means the run finished its steps. Check the run history to see what each step did.
What stays when an account changes hands.
When an account moves to a new manager or a new quarter starts, nobody has to rebuild its history from memory.
- Records
- Account rows, renewal dates and expansion notes stay in their tables.
- Context
- Onboarding plans, call notes and QBR decks stay in Files. Each customer's chats stay in its project.
- Decisions
- Workflow runs and approvals stay in run history, so you can see what was approved and what was sent.
- Procedures
- Skills, saved agents and workflows are ready for the next account, so a new teammate starts with the same steps.
Questions from customer success teams
What is TulipFarm for customer success teams?
TulipFarm is an AI workspace where a customer success team keeps account health, onboarding plans, QBR prep and renewal dates, with agents and workflows for the recurring parts. Sales, support, product and finance work in the same workspace, so escalations, expansion notes and contract dates can stay in one place instead of being copied between apps. TulipFarm Cloud is in public beta and open to everyone.
Does TulipFarm replace my CRM or customer success platform?
No. TulipFarm isn't built to replace your CRM, help desk or customer success platform. It holds the work around them: the account table, onboarding plans, QBR prep, renewal reminders and handoffs to other teams. You can start with one recurring job, such as the Monday renewal list.
Can TulipFarm pull account data from my CRM or help desk?
Not directly. Chats and agents can't read your CRM, and TulipFarm can't reply to customers from your help desk. A new record in HubSpot can start a workflow. Your team adds account data by importing an export into a table or uploading a report to Files, and a scheduled agent can draft renewal reminders from it.
How do review and approval work for customer success work in TulipFarm?
An agent proposes changes to table records, and the person who owns the task approves the exact change before it's saved. A workflow can pause until a person responds, and a workflow step that sends a Slack message waits for approval of that exact message. Slack messages sent from chat or an agent task aren't held for approval, so check an agent's tools before you activate it.
Can TulipFarm make QBR decks?
Yes, as a draft for you to review. Chat can create a PowerPoint file in Files, or propose a Google Slides file that you approve before it's uploaded to your Drive. Check and edit the deck before you present it.
Can other teams see our account notes in TulipFarm?
Only if you share them. Private chats and agent tasks are visible only to the person who owns them, and workspace admins can't see them either. Project members see their project's chats and files, and you can share tables and files with the people who need them.
How do I get started with TulipFarm for customer success, and what does it cost?
Sign up for TulipFarm Cloud. The public beta is open to everyone, and your first signup includes $50 in free credits. Public paid plans haven't been announced; see the pricing page to ask for more credits or apply for student, NGO or startup support. You can also take the browser tour, called Explore, without an account; it doesn't connect to your business accounts.
Start with one account list.
Sign up for TulipFarm Cloud and set up the job you repeat most, like the Monday renewal list or the account health table. The public beta is open to everyone, and your first signup includes $50 in free credits.
Want to check your tools first? Contact us about what your team uses.