Every part of your business, in one shared workspace.
TulipFarm is an AI workspace where small-business owners keep deals, purchases, decisions and weekly status together. Agents help with recurring work, and everyone on your team uses 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 you meet the rest of the company.
As the owner, you trade work with Sales, Finance, Operations and Support, even when each is one person. Each handoff stays in the same workspace, so the next person picks up the original record.
Coming in
SalestoOwner
Pipeline
Sales keeps deals in a shared Deals table with stage, value and next step. Ask in chat which deals moved this week, and the Monday status reads the same rows.
TulipFarm for sales teamsBack to the mapFinancetoOwner
Purchase requests
Finance keeps bills and purchase requests in a shared Purchases table, with the invoice files in Files beside it. A workflow can hold large requests until you respond, and Finance pays from the rows you approved.
TulipFarm for finance teamsBack to the mapSupporttoOwner
Customer issues
Support logs refund requests and repeat complaints in a shared table. Ask in chat what's waiting on you, and the weekly status counts what's still open.
TulipFarm for customer support teamsBack to the map
Going out
OwnertoOperations
Decisions
Record each decision in a Decisions table with the date, owner and reason, and share it with Operations. They work from the row, and the reason is still there when someone asks why.
TulipFarm for operations teamsBack to the map
The work that lands on your desk every week.
Records go in tables, policies and price lists in Files, and the recurring work to agents or workflows. Set a job up once in chat, and the next run and the next person start from there.
In these examples, Clover is the agent you set up to help run the business.
Weekly status
When: Mondays
Schedule Clover to run on Monday mornings. It reads the deals, purchases and support tables your team keeps and drafts one status update in a private task for you to review.
Purchase approvals
When: As requests come in
Set up a workflow in chat that pauses when a purchase is over your limit. The run waits until you respond, and run history shows what was approved.
Decision log
When: Ongoing
Keep decisions in one table with the date, owner and reason. Ask in chat what you decided about a supplier or a price, and the answer comes from the row.
How we do things
When: When it changes
Keep price lists, policies and how-to notes in Files. Save the steps you repeat, like quoting a job, as a skill and add it to Clover. Someone on your team saves and turns on each skill.
Bigger projects
When: Each project
Give a large piece of work, like switching suppliers or opening a second location, its own project with its files, instructions, chats and members.
TulipFarm doesn't pay bills, run payroll or keep your books. Your team still does that in the tools it uses today.
One purchase approval, start to finish.
An example: Dan runs a 15-person landscaping company. Here's how a large purchase request moves and where he stays in charge.
What the workflow and run statuses mean
Saved
Dan saved the workflow from chat. Nothing runs yet.
Activated
He turned it on. A new row in the Purchases table can now start a run.
Run started
Finance added the van repair, so a run began.
Completed
Dan approved, so the run marked the request Approved, posted the decision to #ops and finished.
Set up a workflow: when a purchase over $2,000 is added to the Purchases table, have Clover check it against our supplier list and summarize it for me. If I approve, mark it Approved and post the decision to #ops.
- Trigger
Finance adds a $3,400 van repair to the Purchases table.
Request added - Condition
Checks whether the amount is over $2,000. If it isn't, the run stops here.
Passed: $3,400 - Agent
Clover checks the request against the approved supplier list in Files and writes a short summary.
Summary ready - Review
The run pauses until Dan reviews the summary and approves or declines.
Dan approved - Table
Marks the request Approved in the Purchases table.
Marked Approved - Slack
Posts the decision to #ops once Dan approves the exact message. Nothing is sent before that.
Approved, sent to #ops
Completed means the run finished its steps. Check the run history to see what each step did.
What stays when people come and go.
When a manager leaves or you take a week off, nobody has to rebuild the work from memory.
- Records
- Deals, purchase requests, decisions and open issues stay in their tables.
- Context
- Price lists, policies and supplier notes stay in Files. Each project's chats stay in the 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 stay ready, so a new hire starts with the same steps.
Questions from small-business owners
What is TulipFarm for small businesses?
TulipFarm is an AI workspace where a small company keeps its records, files and recurring work, with agents and workflows for the repeat jobs. Sales, finance, operations and support work in the same workspace, so the weekly status, approvals and decisions come from one set of records instead of copies across apps. TulipFarm Cloud is in public beta and open to everyone.
Does TulipFarm replace my accounting, CRM or email tools?
No. TulipFarm doesn't pay bills, run payroll or keep your books, and it isn't built to replace your CRM or email. It holds the work around those tools: the weekly status, approvals, decisions, procedures and handoffs between people. You can start with one recurring job, such as the Monday status update.
How do approvals 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 I see my employees' private chats in TulipFarm as the owner?
No. Private chats and agent tasks are visible only to the person who owns them, and workspace admins can't see them either. Share the work you both need through a project, a table or Files. The same rule keeps your own private chats private.
Does TulipFarm work with Google Workspace and Slack?
Yes. Each person can connect their own Google account for Gmail, Google Calendar, Drive, Docs, Sheets and Slides, and a workspace can connect Slack. Changes in Google, such as sending an email or creating a calendar event, wait until the account owner approves the exact request.
How do I get started with TulipFarm for a small business, 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 weekly job.
Sign up for TulipFarm Cloud and set up the job you repeat most, like the Monday status update or purchase approvals. 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.