Your people work, in one place with the rest of the company.
TulipFarm is an AI workspace where HR teams keep the recruiting pipeline, onboarding checklists, policies and people requests. Agents help with recurring work, and other teams see only the records you share.
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 HR meets the other teams.
HR trades work with Engineering, Operations, Finance and Security. Each handoff stays in the same workspace, and each team sees only the records you share with it.
Coming in
EngineeringtoHR
Open roles
Engineering adds each open role to a Hiring table you share, with the hiring manager and interview panel. Your recruiting pipeline starts from that row, so nobody retypes the role.
TulipFarm for engineering teamsBack to the mapFinancetoHR
Headcount budget
Finance keeps approved headcount in a table it shares with you. Check each new opening against it before the role goes into your recruiting pipeline.
TulipFarm for finance teamsBack to the map
Going out
HRtoOperations
Start dates
Add each new hire's start date, location and equipment needs to an onboarding table you share with Operations. Operations sees what to prepare before the first day.
TulipFarm for operations teamsBack to the mapHRtoSecurity
Access requests
When someone joins or leaves, add a row to an access requests table you share with Security. Security grants or removes access in its own tools. TulipFarm doesn't manage accounts.
TulipFarm for security teamsBack to the map
The people work that comes back every week.
Records go in tables, policies and checklists 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 HR agent.
Recruiting pipeline
When: Ongoing
Keep every candidate in one table, with role, stage, owner and next step. Ask in chat who's still waiting for interview feedback or which roles have no one at the final stage.
Interview scheduling notes
When: Each interview
Give each open role a project that holds the interview plan, scorecards and the panel's chats. Ask chat to find open time on your connected Google calendars. It proposes the event, and nothing is added until you approve it.
Onboarding checklists
When: Each new hire
Keep the onboarding checklist in Files and each new hire in a table. Set up a workflow in chat, so marking a hire Offer accepted starts a run and Clover drafts the first-week plan for your review.
Policy docs
When: When policies change
Keep the handbook and policies in Files, and share each one with the people who need it. Ask chat to draft an update as a Word document, or to propose a Google Doc that you approve before it's uploaded.
People requests
When: Ongoing
Track requests for letters, equipment and policy answers in a table with owner and status. Save how your team answers common questions as a skill and add it to Clover. Clover drafts replies from your policy files, and a person on your team reviews and sends each one.
TulipFarm isn't an HR system or applicant tracking system. It doesn't post jobs, run payroll or manage benefits, so your team keeps the tools it uses for those.
One new hire, start to finish.
An example: Priya, a people lead, is onboarding Sam, a new engineer. Here's how the work moves 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 a new-hire row can now start a run.
Run started
Priya marked Sam's offer accepted, so a run began.
Completed
The run posted the approved note to #welcome and finished. The first-week plan stays in the run, ready to share with Sam's manager.
Set up a workflow: when a new hire is marked Offer accepted, have Clover draft a first-week plan from our onboarding checklist and a welcome note for #welcome. Check with me before anything goes to Slack.
- Trigger
Priya sets Sam's row to Offer accepted in the New hires table.
Sam set to Offer accepted - Condition
Checks that Sam's start date is filled in. If it's blank, the run stops here.
Passed: start date set - Agent
Clover reads Sam's row and the onboarding checklist in Files.
Read row and checklist - Agent
Clover drafts Sam's first-week plan and a short welcome note for #welcome.
2 drafts ready - Review
The run pauses until Priya reviews the drafts and responds.
Priya responded - Slack
Posts the welcome note to #welcome once Priya approves the exact message. Nothing is sent before that.
Approved, sent to #welcome
Completed means the run finished its steps. Check the run history to see what each step did.
What stays when your team changes.
When someone goes on leave or a new hiring round starts, nobody has to rebuild the work from memory.
- Records
- Candidates, new hires and people requests stay in their tables.
- Context
- The handbook, policies and interview plans stay in Files. Each role'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 hire, so a new teammate starts with the same steps.
Questions from HR and people teams
What is TulipFarm for HR teams?
TulipFarm is an AI workspace where an HR team keeps its recruiting pipeline, interview plans, onboarding checklists, policies and people requests, with agents and workflows for the recurring parts. Engineering, operations, finance and security work in the same workspace, so open roles, start dates and access requests don't have to be copied between apps. TulipFarm Cloud is in public beta and open to everyone.
Does TulipFarm replace my HR system or applicant tracking system?
No. TulipFarm isn't built to replace your HR system, applicant tracking, payroll or benefits tools. It holds the work around them: the pipeline view, interview plans, checklists, policies and handoffs to other teams. You can start with one recurring job, such as onboarding checklists.
Who can see candidate and employee information in TulipFarm?
Only the people you share it with. 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. Decide with your team which personal data belongs in TulipFarm and which stays in your HR system.
How do review and approval 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 schedule interviews?
Partly. Chat can look for open time across the Google calendars you've connected and propose an interview event, and the event is created only after you approve it. TulipFarm doesn't connect to applicant tracking or scheduling tools.
Can TulipFarm send offer letters or run payroll?
No. TulipFarm doesn't connect to payroll, benefits or e-signature tools, so it doesn't send offers, run payroll or change benefits. Chat can draft an offer letter as a Word document in Files for your team to review, and you send it from the tools you already use.
How do I get started with TulipFarm for HR, 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 new hire.
Sign up for TulipFarm Cloud and set up the job you repeat most, like onboarding checklists or the recruiting pipeline. 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.