Your sales work, in one place with the rest of the company.
TulipFarm is an AI workspace where sales teams keep the pipeline, account notes, call notes and recaps. 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 sales meets the other teams.
Sales trades work with Marketing, Product, Customer success and Finance. Each handoff stays in the same workspace, so the next team picks up the original record.
Coming in
MarketingtoSales
Campaign leads
Marketing imports the lead list from an event or form into a table it shares with you. Each row records the campaign it came from, and the talking points sit in Files next to the brief.
TulipFarm for marketing teamsBack to the map
Going out
SalestoProduct
Feature requests
When a prospect asks for something the product doesn't do yet, log it in a Requests table you share with Product. Each row records the deal and the call it came from.
TulipFarm for product teamsBack to the mapSalestoCustomer success
Closed deals
When a deal closes, a workflow can have your sales agent draft the handoff note from the deal row and your call notes. Customer success gets the note in Slack after you approve it, and the deal row stays in the table you share.
TulipFarm for customer success teamsBack to the mapSalestoFinance
Signed orders
Keep deal terms in a table you share with Finance, and the signed order forms in Files beside it. Invoicing starts from the same record your team closed.
TulipFarm for finance teamsBack to the map
The sales work that comes back every week.
Deals go in tables, call notes and order forms 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 sales agent.
Pipeline table
When: Ongoing
Keep every open deal in one table, with owner, stage, value, next step and close date. Ask in chat which deals have no next step or which ones close this month.
Account research
When: Before each call
Give each key account a project that holds its notes, files, instructions and chats. Before a call, ask in the project's chat for a summary of what your team already has on the account.
Call notes
When: Every call
Upload call notes or a transcript to Files. Clover pulls out the next steps and proposes updates to the deal's row, and you approve the exact changes before they're saved.
Follow-up drafts
When: After each call
Save your follow-up format as a skill and add it to Clover. Clover drafts the follow-up from your call notes and can propose it as a Gmail draft, which is created only after you approve it.
Weekly pipeline recap
When: Mondays
Schedule Clover to run on Monday mornings. It reads the pipeline table and drafts the recap in a private task for you to review.
TulipFarm doesn't update your CRM or run email sequences. A new HubSpot deal can start a workflow, and any Gmail draft it proposes waits for your approval.
One closed deal, start to finish.
An example: Daniel, an account executive, has just closed a new customer. Here's how the handoff moves and where he stays in charge.
What the workflow and run statuses mean
Saved
Daniel saved the workflow from chat. Nothing runs yet.
Activated
He turned it on. A change to a deal row can now start a run.
Run started
Daniel marked 1042 Closed won, so a run began.
Completed
The run sent the approved note to #customer-success and finished. The deal row stays in the Pipeline table you share with Customer success.
Set up a workflow: when a deal moves to Closed won, have Clover draft a handoff note for #customer-success from the deal row and my call notes. Check with me before anything goes to Slack.
- Trigger
Daniel moves deal 1042 to Closed won in the Pipeline table.
1042 set to Closed won - Condition
Checks whether 1042 is a new customer. If it's an expansion, the run stops here.
Passed: new customer - Agent
Clover reads the deal row and Daniel's call notes.
Read deal and notes - Agent
Clover drafts a handoff note with the customer's goals, contacts and agreed dates, using the Handoff skill.
Draft ready - Review
The run pauses until Daniel reviews the draft and responds.
Daniel responded - Slack
Posts the note to #customer-success once Daniel approves the exact message. Nothing is sent before that.
Approved, sent to #customer-success
Completed means the run finished its steps. Check the run history to see what each step did.
What stays when a rep moves on.
When someone changes territory or a new quarter starts, nobody has to rebuild account history from memory.
- Records
- Deal rows, lead lists and feature requests stay in their tables.
- Context
- Call notes and order forms stay in Files. Each account'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 quarter, so a new rep starts with the same steps.
Questions from sales teams
What is TulipFarm for sales teams?
TulipFarm is an AI workspace where a sales team keeps its pipeline, account notes, call notes and weekly recaps, with agents and workflows for the recurring parts. Marketing, product, customer success and finance work in the same workspace, so leads, feature requests and closed deals 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?
No. TulipFarm isn't built to replace a CRM, and it doesn't change records in one. A new HubSpot contact, company or deal can start a workflow. Keep a pipeline in a TulipFarm table or import a CRM export for recaps and handoffs to other teams. You can start with one recurring job, such as the weekly pipeline recap.
Can TulipFarm send follow-up emails for me?
Not without your approval. If you connect your Google account, chat or an agent can propose a Gmail draft from your call notes. Every Gmail change it proposes, including creating a draft, waits until you approve the exact content. TulipFarm doesn't run email sequences.
How do review and approval work for sales records in TulipFarm?
An agent proposes changes to table records, such as a deal's stage or next step, 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 other teams see our pipeline in TulipFarm?
Only if you share it. 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.
Does TulipFarm record or transcribe sales calls?
No. TulipFarm doesn't join, record or transcribe calls. Upload notes or a transcript from your call tool to Files, and an agent can pull out next steps and propose updates to the deal's row for you to approve.
How do I get started with TulipFarm for sales, 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 pipeline.
Sign up for TulipFarm Cloud and set up the job you repeat most, like the Monday pipeline recap or call-note follow-ups. 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.