Your marketing work, in one place with the rest of the company.
TulipFarm is an AI workspace where marketing teams keep the content calendar, briefs, brand rules 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 marketing meets the other teams.
Marketing trades work with Product, Sales, Support and Finance. Each handoff stays in the same workspace, so the next team picks up the original record.
Coming in
ProducttoMarketing
Launch notes
Product keeps release dates and notes in a shared Releases table. When Product marks a release Ready, that change can start your launch workflow, and your marketing agent drafts from the notes Product wrote.
TulipFarm for product teamsBack to the map
Going out
MarketingtoSales
Campaign leads
Import the lead list from an event or form into a table you share with Sales. Each row records the campaign it came from, and the talking points sit in Files next to the brief.
TulipFarm for sales teamsBack to the mapMarketingtoSupport
Launch FAQs
Write the launch FAQ once and keep it in Files. When Support's agents answer questions about the release, they can cite it.
TulipFarm for customer support teamsBack to the mapMarketingtoFinance
Campaign spend
Track campaign spend, invoices and event bookings in a table you share with Finance. The invoice files stay in Files beside it.
TulipFarm for finance teamsBack to the map
The marketing work that comes back every week.
Records go in tables, briefs and brand rules 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, Sprout is your team's marketing agent.
Content calendar
When: Ongoing
Keep every post, email and blog piece in one table, with owner, channel, status and publish date. Ask in chat what's due this week or what's still waiting for a draft.
Campaign briefs
When: Each campaign
Give each campaign a project that holds its brief, files, instructions and chats. Ask chat to write the brief as a Word document in Files, or to propose a Google Doc that you approve before it's uploaded.
Brand-voice checks
When: Every draft
Save your tone, banned phrases and style rules as a skill and add it to Sprout. Sprout checks every draft against those rules before a person reviews it. Someone on your team saves and turns on each skill.
Weekly performance recap
When: Mondays
Schedule Sprout to run on Monday mornings. It reads the numbers your team added to the results table and drafts the recap in a private task for you to review.
Launch coordination
When: Each release
Set up a launch workflow in chat. When Product marks a release Ready, Sprout drafts the announcement, the run waits for your review, then Slack gets only the message you approved.
TulipFarm doesn't publish posts or send campaigns. Your team still publishes from the tools it uses today.
One launch, start to finish.
An example: Maya, a marketing lead, is announcing her company's 2.4 release. Here's how the work moves and where she stays in charge.
What the workflow and run statuses mean
Saved
Maya 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
Product marked 2.4 Ready, so a run began.
Completed
The run sent the approved note to #sales and finished. The email draft stays in the run, ready to paste into your email tool.
Set up a workflow: when a customer-facing release is marked Ready, have Sprout draft the announcement email and a #sales note from the release notes and our campaign brief. Check with me before anything goes to Slack.
- Trigger
Product sets release 2.4 to Ready in the Releases table.
2.4 set to Ready - Condition
Checks whether 2.4 is customer-facing. If it's internal only, the run stops here.
Passed: customer-facing - Agent
Sprout reads the release notes and Maya's campaign brief.
Read notes and brief - Agent
Sprout drafts the announcement email and a short #sales note, using the Brand voice skill.
2 drafts ready - Review
The run pauses until Maya reviews the drafts and responds.
Maya responded - Slack
Posts the note to #sales once Maya 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 the campaign ends.
When someone goes on leave or a new quarter starts, nobody has to rebuild the work from memory.
- Records
- Calendar rows, lead lists and spend stay in their tables.
- Context
- Briefs, brand rules and launch notes stay in Files. The campaign'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 campaign, so a new teammate starts with the same steps.
Questions from marketing teams
What is TulipFarm for marketing teams?
TulipFarm is an AI workspace where a marketing team keeps its content calendar, campaign briefs, brand rules and weekly recaps, with agents and workflows for the recurring parts. Sales, support, product and finance work in the same workspace, so launch notes, leads and spend 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 marketing tools?
You keep them. TulipFarm isn't built to replace your email marketing, social, ad or analytics tools. It holds the work around them: the calendar, briefs, brand rules, recaps and handoffs to other teams. You can start with one recurring job, such as the weekly recap.
How do review and approval work for marketing content 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.
Does TulipFarm post to social media or send marketing emails?
No. TulipFarm doesn't connect to social networks, ad platforms or email marketing tools, so it doesn't publish posts, buy ads or send campaigns. Your team can draft and review the copy in TulipFarm, then publish it from the tools you already use. If your workspace connects Slack, a workflow can send a Slack message after you approve the exact text.
Can other teams see our campaign records 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.
Can TulipFarm pull campaign results from my ad or analytics accounts?
Not directly. TulipFarm doesn't connect to ad platforms or analytics tools. Your team adds the numbers by importing an export into a table or uploading a report to Files. A scheduled agent can then draft the weekly recap from what your team added.
How do I get started with TulipFarm for marketing, 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 campaign.
Sign up for TulipFarm Cloud and set up the job you repeat most, like the Monday recap or the content calendar. 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.