When should you use it?
- You prospect on LinkedIn and the steps blur together
- You want to see which signals and messages convert
- You're comfortable reviewing messages before they go out
Not for: Blasting unreviewed messages at volume; Platforms whose terms prohibit automated outreach on your account
What do you need, and what do you get?
You need
- Your ideal customer profile and disqualifiers
- A source of buying signals, such as engagement with competitors
- An enrichment source and a LinkedIn outreach tool
You get
- A ranked list of fitting prospects with research notes
- Personalized message drafts
- Reply handling and a weekly view of what converts
How does it work, step by step?
- Write the ICP and disqualifiersGive the fit-check role clear rules so bad fits are dropped before any research is spent.
- Choose your signalsDecide what counts as intent, such as engaging with a competitor's post or hiring for a relevant role.
- Research, then enrichHave one role find the angle and another fill in contact data, so each output is checkable.
- Draft and approveLet the copywriting role draft; you approve before the outreach role sends.
- Qualify repliesRoute positive replies through qualification questions before any meeting gets booked.
- Review conversion weeklyHave an analyst role report which segments, triggers and messages led to meetings.
The prompt
Our own prompt, inspired by Roman (@romanbuildsaas) and written to work in Grok Bot, Claude, ChatGPT and others. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Act as the {role} in my outbound team. Our ICP: {icp}. Disqualifiers: {disqualifiers}. Input from the previous role: {handoff}. Do only your job: {role_task}. Output a structured handoff for the next role ({next_role}) with fields {fields}. If information is missing or a prospect fails a disqualifier, stop and say why. Never send messages; drafts go to me for approval.
Inspired by Roman (@romanbuildsaas): We open-sourced our entire outbound team.. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- The post is a product launch with a comment-to-get-it call to action; judge the roster idea separately from the vendor.
- LinkedIn limits and terms apply to automated messaging; keep volumes human-scale.
Our take
The handoff chain is the part worth borrowing. Writing out who does what, from signal to fit check to research to message to reply, forces you to define each step's input and output, and that's where most outbound processes are vague. You don't need thirteen agents to benefit; three or four roles with the same boundaries will show you where prospects fall out. Keep sending behind your approval, at least until the copy is consistently good, because a LinkedIn message carries your name and repeated low-quality outreach can get an account restricted. The analyst role is underrated: a weekly note on which signals produced meetings is what lets you cut the roles that aren't earning their keep. Be skeptical of the launch framing and the comment-for-access tactic, and evaluate any MCP or data vendor on data quality and terms. Start with one ICP, review every draft for two weeks, and only then add the follow-up role.
Where the time goes back: Research and first drafts arrive ready for review instead of being done prospect by prospect.
FAQ
Do I need GojiberryAI?
Why so many agents?
Source and credit
Inspired by Roman (@romanbuildsaas). We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- We open-sourced our entire outbound team.
- Creator
- Roman (@romanbuildsaas)
- Published on
- X
- Original date
- Sep 1, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Grok Bot
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS (desk check, not a live run in the vendor's app). Replaces an earlier templated dry-run note.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.