Inside Rival: How We Use What We Build
This blog is part of Inside Rival, a series where our team shares how we use Rival in our everyday work. From favorite tools to AI agents and automations, we're showing you what we're building, how we're using it and what we've learned along the way.
The Monday problem: your week is eaten by busy work
Your marketing team doesn't need another tool to log into. It needs the repetitive parts of the job to run on their own.
I'm the Associate Director of Enterprise Strategy at Rival, and I'm definitely not a coding expert. Still, over the past couple of weeks I built five marketing agents without writing a single line of code. Each one started as one RivalBot prompt. Here are all five, word for word, so you can build the same agents for your work.
Why I built these with RivalBot
RivalBot is Rival's conversational builder. You describe the agent you want in plain language, and it sets up the instructions, tools, connectors (like Google Drive or Gmail) and rituals (tasks the agent runs on a schedule) for you. No code, no setup docs. New to it? Start with Using RivalBot: A Complete Guide.
From there, you test it in the chat preview, tweak it, and it's yours. That's the whole build loop.
How to use these prompts
Each entry gives the exact build prompt, the problem behind it, what RivalBot set up, and how to adapt it. Swap the brackets for your own details and paste it in.
The five agents
1. The Weekly Performance Briefer: your Monday mornings back
Best for: replacing the exec update you assemble by hand.
Steal my prompt: “Build me an agent that turns last week's paid media results into a leadership update. It should read the performance sheet in my Google Drive, compare each channel (LinkedIn, Google, Meta) to the prior week, and write short bullets with bold lead-ins, specific metrics, and a final "Next:" line of action items. Set up a ritual to send me the draft every Monday at 8 am ET.”
What I needed: pulling together our weekly exec update was eating my Monday mornings.
What RivalBot set up: instructions for the comparison and format, a Google Drive connector scoped to the performance sheet, and a Monday ritual, so the draft is waiting before I open my laptop.
Make it yours: spell out the exact format your execs read, and name the metrics they care about. Then point the agent to your data source and swap in your channels. That format instruction is the difference between a draft you rewrite and a draft you send.
2. The Asana Task Manager: no task slips through
Best for: keeping the board clean and making sure meeting action items actually happen.
Steal my prompt: “Build me an agent that keeps my team's marketing work on track in Asana. Every weekday at 8:30 am ET, review the [Marketing] project and send me a prioritized list of tasks that are overdue, due in the next 48 hours, or missing an owner or due date. When I paste in meeting notes, turn each action item into a draft Asana task with an owner, due date and project, and show me the list to approve before you create anything. When I ask you to update a task (a new due date, owner or status), make the change and confirm it.”
What I needed: tasks were slipping because nobody had time to groom the board, and action items from meetings never made it into Asana.
What RivalBot set up: an Asana connector, a weekday morning ritual for the task sweep, and instructions to draft tasks from notes with an approval step before anything is created. I also added the ability to edit tasks right from the agent, so small updates take seconds instead of a trip into the board.
Make it yours: keep the approval step, since it’s the key line. Then swap in your own tool, projects, and schedule, and tune the sweep to flag what actually slips on your team. The agent does the busywork, and you stay in control of what lands on your board.
3. The Project Timeline Builder: launch dates that actually hold
Best for: skipping the backward whiteboarding session at every kickoff.
Steal my prompt: “Build an agent that drafts project timelines. When I give it a launch date, a list of deliverables, and who's on the team, work backward to build a timeline with milestones, owners, dependencies and review gates. Assume [5] business days for brand and legal review. Flag anything that can't realistically fit before the launch date and suggest what to cut or move. Output it as a table I can paste into Asana or a spreadsheet.
What I needed: every campaign kickoff started with an hour of whiteboarding backward from a date, and review time was always the first thing we forgot.
What RivalBot set up: planning instructions that work backward from the launch date, a built-in review buffer, and a fixed table output that drops straight into my Asana Task Manager. The result is an easy-to-follow timeline I can share internally and with external partners.
Make it yours: bake your real constraints into the prompt (review cycles, team size, blackout dates). A timeline that ignores them is just a wish list.
4. The Dev Team Liaison: marketing and engineering on the same page
Best for: keeping development teams and project managers working toward the same goals.
Steal my prompt: Build an agent that bridges our project team and our developers. When I describe a new client build, create a project brief with goals, scope, required inputs and assets, budget, and launch date, plus a checklist developers can use to confirm they have everything before work starts. Once a project is underway, send me a status update every Friday that tracks progress against the timeline and budget and flags anything at risk.
What I needed: we're always creating custom builds for clients. That takes strong communication with our development team and making sure they have every input they need up front. This agent makes sure we're crossing our t's and dotting our i's before a project launches.
What RivalBot set up: two modes in one agent: a brief creator that produces a project brief and developer checklist for every new build, and a status update manager that keeps projects on track and on budget.
Make it yours: build the checklist into the brief, and fill it with what your developers actually need on day one. Connect the agent to wherever your projects are tracked so the weekly update reflects real progress. Then set the cadence, channel, and risk thresholds that fit your team. When developers can confirm they have everything up front, projects start faster and stay on budget.
5. The Launch Kit Builder: one feature description, every asset
Best for: shipping strategic launches with a lean team.
Steal my prompt: “Build an agent that creates a full launch kit from one feature description. Use the brand guidelines doc in my Google Drive for voice. For each feature I give you, produce a launch email for individual users, a one-page overview for enterprise buyers, five social posts, and a checklist of everything the launch needs before it goes out. Keep the messaging consistent across every asset.”
What I needed: we're constantly rolling out platform updates and new product features. With a small team, every announcement needs to be streamlined and consistent across our channels. Strong organization is what makes each launch happen on time and with the biggest impact.
What RivalBot set up: content instructions for all three formats, a Google Drive connector pointed at our brand guidelines, a single input for the feature description, and a launch checklist so nothing gets missed.
Make it yours: Keep the single input and swap in the rest. Point the agent to wherever your brand voice lives, name the audiences you actually sell to, and list the assets your launches need, whether that’s release notes, a sales one-pager, or an in-app banner. Then add your own pre-launch steps to the checklist. Describe the feature once and every asset stays on message.
The anatomy of a good RivalBot prompt
Every prompt above covers the same five things. Check yours against this list before you paste it in, and RivalBot can build a working agent on the first try:
The job: what the agent produces, in one sentence.
The inputs: what you'll hand it each time (a launch date, meeting notes, a new client build).
The sources: which connectors it needs, like a Drive folder or a spreadsheet.
The output format: word caps, bullet styles, a fixed number of ideas.
The schedule: a ritual, if it should run without you asking.
For the deeper build (instructions, capabilities, publishing), see How to Build an Agent on Rival.
Test it, then share it
Don't trust the first draft. Run the agent in the chat preview with real inputs, spot the one thing it missed, fix it, and run it again. That loop is what turns a demo into a dependable agent. Prompting Best Practices on Rival covers the iteration pattern in detail.
Once it's consistent, decide what's next. Keep it private for your team, or publish it to the Rival Marketplace, where builders earn 85% of every run under Rival's Payout Policy. See How to Publish to the Marketplace on Rival.
Alexa Rifkin is Associate Director of Enterprise Strategy at Rival, where she helps organizations put AI to work in practical, meaningful ways. From building AI agents and automating workflows to managing complex client projects, she focuses on making technology easier to use and more valuable for the people behind it. She works closely with enterprise clients to turn big ideas into solutions that save time, simplify work and deliver real results.