Your product work, in one place with the rest of the company.
TulipFarm is an AI workspace where product teams keep the roadmap, customer feedback, specs and release checklists. Agents help with recurring work, and Engineering, Marketing, Support and Sales 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 product meets the other teams.
Product trades work with Engineering, Marketing, Support and Sales. Each handoff stays in the same workspace, so the next team picks up the original record.
Coming in
SupporttoProduct
Customer feedback
Support adds feedback to a table you share, with the customer's words and the product area. Your weekly summary reads from those rows.
TulipFarm for customer support teamsBack to the mapSalestoProduct
Feature requests
Sales logs feature requests from open deals in the same table, with the deal stage. You can see which requests come from live deals before you plan the quarter.
TulipFarm for sales teamsBack to the map
Going out
ProducttoEngineering
Specs
Write each spec in Files, inside the feature's project. Engineering plans from that one current version, not from copies pasted into chat threads.
TulipFarm for engineering teamsBack to the mapProducttoMarketing
Launch notes
Add launch notes to the release row in the Releases table and mark it Ready. That change can start Marketing's launch workflow, and their agent drafts from the notes you wrote.
TulipFarm for marketing teamsBack to the map
The product work that comes back every week.
The roadmap and feedback go in tables, specs 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 product agent.
Roadmap
When: Ongoing
Keep every initiative in one table, with owner, status, target quarter and the feedback behind it. Ask in chat what's slipping or what's planned for next quarter.
Feedback synthesis
When: Fridays
Schedule Clover to run on Friday afternoons. It reads the week's rows from Support and Sales, groups them by theme and drafts a summary in a private task for you to review.
Specs and PRDs
When: Each feature
Give each feature a project that holds its spec, files, instructions and chats. Ask chat to write the spec as a Word document in Files, or to propose a Google Doc that you approve before it's uploaded.
Release readiness
When: Each release
Save your release checklist as a skill and add it to Clover. Clover checks each release against it and lists what's missing before you mark the release Ready. Someone on your team saves and turns on each skill.
Launch notes to Marketing
When: Each release
Write the launch notes in the release row. When you mark it Ready, Marketing's launch workflow can start from what you wrote, so nobody copies notes between apps.
TulipFarm doesn't publish your changelog or release notes. Your team still publishes from the tools it uses today.
One release check, start to finish.
An example: Lena, a product manager, is getting release 3.1 ready. Here's how the check moves and where she stays in charge.
What the workflow and run statuses mean
Saved
Lena saved the workflow from chat. Nothing runs yet.
Activated
She turned it on. A change to a release row can now start a run.
Run started
Engineering moved 3.1 to Review, so a run began.
Completed
The run posted the approved summary to #release and finished. When the open items close, Lena marks 3.1 Ready herself.
Set up a workflow: when a release in the Releases table moves to Review, have Clover check it against our release checklist and the spec, and list anything missing. Check with me before anything goes to #release in Slack.
- Trigger
Engineering moves release 3.1 to Review in the Releases table.
3.1 moved to Review - Condition
Checks whether 3.1 has a spec linked in its row. If it doesn't, the run stops here.
Passed: spec linked - Agent
Clover reads the spec in Files and the notes in the release row.
Read spec and notes - Agent
Clover checks 3.1 against the Release checklist skill and lists the open items.
3 open items listed - Review
The run pauses until Lena reviews the list and responds.
Lena responded - Slack
Posts the readiness summary to #release once Lena approves the exact message. Nothing is sent before that.
Approved, sent to #release
Completed means the run finished its steps. Check the run history to see what each step did.
What stays when the release ships.
When someone changes teams or a new planning cycle starts, nobody has to rebuild the reasoning from memory.
- Records
- Roadmap rows, feedback and releases stay in their tables.
- Context
- Specs, checklists and launch notes stay in Files. Each feature's chats stay in its project.
- Decisions
- Workflow runs and approvals stay in run history, so you can see what was checked and what was sent.
- Procedures
- Skills, saved agents and workflows are ready for the next release, so a new teammate starts with the same steps.
Questions from product teams
What is TulipFarm for product teams?
TulipFarm is an AI workspace where a product team keeps its roadmap, customer feedback, specs and release checklists, with agents and workflows for the recurring parts. Engineering, marketing, support and sales work in the same workspace, so feedback, specs and launch notes can stay in one place instead of being copied between apps. TulipFarm Cloud is in public beta and open to everyone.
Does TulipFarm replace our roadmap tool or issue tracker?
You don't have to replace them. TulipFarm isn't built to replace your issue tracker or design tools. It can hold the roadmap, feedback, specs, release checks and launch notes, so other teams work from the same records. You can start with one recurring job, such as the weekly feedback summary.
How does customer feedback from Support and Sales get into TulipFarm?
Support and Sales add it to a table you share, either row by row or by importing an export from the tools they already use. A workflow can also start from a source your workspace has set up, such as a new Gmail message or a Google Sheets row. A scheduled agent can then group the week's feedback by theme for you to review.
Can a TulipFarm agent change the roadmap without my approval?
No. 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 also pause until a person responds before it continues.
Who can see our specs and roadmap in TulipFarm?
Only people you share them 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.
Does TulipFarm publish release notes or update our changelog?
Not on its own. TulipFarm doesn't publish to your website or changelog tool, so your team publishes launch notes there. If you've connected Confluence, chat or an agent can propose a release-notes page that's created only after you approve it. If your workspace connects Slack, a workflow can post a release update after you approve the exact message.
How do I get started with TulipFarm for product teams, 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 release.
Sign up for TulipFarm Cloud and set up the job you repeat most, like the weekly feedback summary or the release checklist. 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.