Stoked to introduce our Campaign Strategist, powered by @Google Gemini 2.5 Flash 🚀
We took Gemini's insane capabilities and mixed them with everything we know about creator marketing. The result? An AI agent that completely changes how B2B brands plan creator campaigns.
Here's what makes it special:
- Analyzes hundreds of creators at once (thanks to Gemini's massive context window)
- Uses our battle-tested playbooks built right into the prompts
- Shows you performance projections before you spend a dime
- Gives you recommendations tailored to your exact product & audience
The magic? We've prompted Gemini to think like our best marketers - evaluating creator fit, predicting engagement, and optimizing budget allocation at speeds impossible for humans.
No more spreadsheet hell. No more manual vetting. Just smart campaign strategies in literal seconds.
@krystiangebis@zero__ms We are using the default db client for Zero and keeping Prisma for legacy/be only stuff!
Is prisma support planned? That would be nice
Launching Zest, and it's so cool.
Zest *is* your workspace. Not a feature. An operator. Always there, managing campaigns, handling outreach, analyzing what's working.
Technically, it's the most interesting thing we've built. Lives in a sandbox, writes its own code to analyze your data, uses sub-agents for long trajectories. Builds campaigns with hundreds of creators in minutes instead of days.
While we were at it, we also redesigned our website and it's one of the most beautiful things you are gonna see this week
https://t.co/Q00UQT3Bta
Creator-led GTM works. Scaling it hasn’t.
Until now.
🍋 Introducing Zest, the first AI agent for creator-led GTM.
From one prompt, Zest builds strategy, finds creators, runs outreach, manages campaigns, and turns results into clear next steps.
Modern GTM is creator-led. With Zest, it’s finally scalable.
We sent Froot to school 📚
They've been studying B2B creator marketing and honestly? Top of the class.
They're about to bring some serious zest to your workspace.
More next week 👀
Thinking more about this, the tool could be implemented as a just-bash custom command so it all becomes, well, just bash.
Main quirk would be that the command should limit max output length by default and return an error instructing the model to save to file first when exceeded (need for this could be offset with good documentation)
@cramforce Makes sense. The CLI tool idea was mostly to allow the model to chain operations but I guess a tool that supports programmatic tool calling could achieve a similar result
Do you have any thoughts on providing a CLI tool to the LLM that it can use to fetch/manage data (eg historical cases with the same customers)?
Should be very simple for the agent to store the response in a file and then work on it using whatever approach it wants. I’d assume this is also well covered by training.
Kind of letting the agent built it’s own filesystem vs providing it upfront
@prisma@bunjavascript@deno_land@nodejs Do we need to manually select to import from /browser.ts or /client.ts? Is it safe to always import from the browser import unless importing PrismaClient?
@karthikkalyan90 Append-only could be interesting, agreed!
Another thing our agent does a lot with search tool is parallel tool calling. Would parallel tool calls all end up in the same file right now?