These are examples, not the full menu. Bring the workflow your team needs most.
Reads ad spend against pipeline in the CRM. Flags where spend rose and qualified pipeline didn't, then proposes the budget move.
Gate · You approve every change
Scores your ad creatives against competitors' live ads on one fixed rubric. Rewrites the bottom quartile and re-scores until the average moves.
Gate · You pick what runs
Rolls buying signals across target accounts into a reason to reach out, and hands sales a ranked list with the why attached.
Gate · Reps choose who to contact
A ticket queue that moves each piece from brief to evidence to draft to lint to critic. You see the third pass, never draft one.
Gate · Nothing ships without a yes
Mines each teammate's own call recordings every week, drafts one post in their voice, and sends it to them in Slack.
Gate · Each person decides to post
Scores how AI answer engines describe you on a fixed set of buying questions each week, then drafts the page fixes.
Gate · You approve every site edit
Tracks what competitors changed in pricing, launches, ads and reviews. Explains why it matters and drafts battlecard updates.
Gate · You approve battlecard edits
Every deal-related ask from sales becomes a tracked ticket. The agent drafts the asset from deal context and ships it to the deal thread.
Gate · Marketing approves first
The newest workflow we added, and what broke on the way.
Arjun walks through workflows on the tools they actually run on, as many as the hour allows.
Your workflow, your blockers, your questions.
Skip any of these four and you get confident, generic output. Every session puts them in place first, whatever you build.
Brand, ICP and banned claims live in files the agent must obey. Hex codes and explicit nevers, never adjectives.
A second agent returns SHIP or REVISE with ordered fixes, scored against a written rubric.
One fact per file, plus an index the agent reads to decide what matters right now.
Read-only connections first. Then every send, publish, spend change and delete needs a person's yes.
Most marketing teams are on rung one. All eight examples sit on rung three or four.
You prompt, it answers, you rewrite most of it.
You do everything
It produces, a critic rejects, you read the third pass.
You approve output
It runs on a clock and hands you finished work.
Examples 1 · 2 · 3 · 6 · 7
You approve exceptions
It acts inside rules you wrote, gated on a reply.
Examples 4 · 5 · 8
You set the rules
Forward this to IT and security
| Scopes | Read-only connections first. Write access only after we've watched it read. |
| Approvals | Every send, publish, spend change and delete needs an explicit human yes. |
| Credentials | Agents never enter passwords, payment details or IDs. Humans only. |
| Environments | Sandbox for every test. Never pilot against live customer data. |
| Audit | Proposals and approvals happen in Slack, a tool your company already governs. |
Cofounder and CEO, Docket · Host of Rethink Revenue
Arjun builds and runs these workflows inside Docket's own marketing team. Each session shows what is working now, including what broke along the way.
“Right now one person on your team is good at AI. Package their workflow and the whole team runs it.”
Watch real workflows run. Leave with one of your own.
A paid ads copilot, creative benchmarking, outbound signals, content to live, social posts from call recordings and weekly AEO scoring. Built and run by our own team.
.png)
See it in action.