Free resource · Setup prep
Before Your Setup Call: Revenue Partner Agent Prep
You're about to get an AI employee that lives on its own cloud computer, talks to you in Slack, and connects to your tools.
Our setup call takes about an hour, as long as the items below are done before we start. Anything not done here becomes time we spend clicking instead of building.
Print this, or keep it open. There's a fill-in block at the bottom you'll paste into the installer on the call.
1. Accounts to create (15 to 20 minutes total)
Orgo ↗: your agent's computer
- Sign up at Orgo. The Hacker plan ($29/mo) is all you need.
- We worked out a deal with Orgo: use our link and get 25% off your first three months on a monthly plan, or your first year on a yearly plan.
- Copy two things and keep them in your notes:
- Workspace ID: top left, Computers, then Workspace settings
- API key: top right blue bubble, then API, then Get API key
- Don't create a computer yet. The installer does that.
OpenRouter ↗: the brain (pay per use, pennies)
- Sign up at openrouter.ai, then Keys, then Create key, and copy it.
- Add a payment method (you start with a small free credit). Your agent runs on an open-source model that costs about 25 cents per million tokens, so a normal month is a few dollars.
Composio ↗: connects your tools (free)
- Sign up at composio.dev, then Get started for free.
- Connect Apps: connect the tools your agent should use. Gmail, Google Calendar, your CRM, and anything else you want it to touch.
- Settings, then API key, and copy it.
Slack: where you'll talk to it
- You need a Slack workspace where you're allowed to install apps. If you don't have one, create a free workspace (2 minutes).
- Note the workspace name.
- Make sure you can log in at api.slack.com/apps in your browser. We'll create the app there during the call (two copy-pastes; we walk you through it).
Codex (recommended) or Claude Code: the installer runs inside one of these
- Codex (OpenAI): the $20 plan is fine. It does the Slack steps for you.
- Claude Code works too. It will ask you to paste your keys yourself and run one command.
- Either way, be logged in before the call.
Optional
- Telegram: only if you want to talk to your agent there too (we'll create a bot token together).
- Wispr Flow (wisprflow.ai, spelled W-I-S-P-R; beware the copycats in the App Store): the fastest way to do the brain dump in section 2. Talk, it types.
2. Your agent's identity: write this before the call
This is the part that makes the difference between a generic bot and your employee. Talk it out with Wispr Flow or type it. Bullet points are fine. Aim for 300 to 800 words total. You'll paste it into the fill-in block below.
2a. Name and look
- Name (this replaces "Revenue Partner" everywhere):
- One-line description (shows in Slack):
- Optional: an avatar image (a ChatGPT-generated portrait works great).
2b. The SOUL: who your agent is
Answer in your own words:
- In one sentence, why does this agent exist? What is it here to make happen for you?
- Who does it serve: you, your team, your customers, your community members? Name the groups.
- Describe its personality in three words, then give one example of how it would say "good morning."
- What does it care about most when it makes a decision? (Speed? Accuracy? Protecting your time? Making members feel seen?)
- What should it never do or say? (Tone it should never use, promises it should never make, topics it stays out of.)
- How should it address you, and how formal should it be with everyone else?
- What does "a great week" look like for this agent? What did it get done, and how did people feel dealing with it?
- Who are the two or three types of people it will meet most (your avatars)? A sentence on each: what they want and how to talk to them.
2c. The JOB: what your agent does
- Its title and a one-paragraph job description.
- The first three things you want it doing this week.
- Daily duties (what it checks, sends, updates and reports, and when).
- Weekly duties (the Monday numbers, the Friday reminders, the content review).
- Every tool and platform it must use, and whether it needs a login on its computer (Skool, WhatsApp, Instagram, your CRM, your calendar, email).
- Who it talks to and through what (DMs in Slack? a shared channel? WhatsApp to members? email to prospects?).
- The reports you want, in the format you want them (for example, "Monday 7am: revenue, spend, bookings, top post and why").
- House rules: brand voice examples (paste a message that sounds like you), banned words, when to escalate to a human, what to do when unsure.
- Who is allowed to give it instructions besides you?
Example: Professor X, a community setter
SOUL: Professor X exists so no man who joins our community falls through the cracks. He serves new members, existing members, and me. Warm, direct, curious: "Morning, Josh. Quick one: what made you join this week?" He cares most about making every man feel seen and getting him to the next right step. He never pressures, never talks about pricing in DMs, never gives medical advice. He calls me Josh; everyone else by first name, mate to mate. A great week: every new member welcomed within an hour, ten real conversations, two calls booked. Avatars: the Magnetic Man guy (career, wants a better life at home) and the Luminary guy (business owner, wants his time back).
JOB: Community Setter. Watch for new members and buyers, welcome them, find out what they came for, point them to the right resource, and book a call with Josh when it fits. First three things: welcome this week's new members, draft the Monday numbers report, review last week's posts and tell me which one worked and why. Tools: Skool (logged in as me), WhatsApp (logged in as me), Google Calendar, Gmail. Reports: Monday 7am numbers plus content review. Voice: short, warm, no corporate words, never more than three lines in a first message. Escalate anything about refunds or personal crises to me immediately.
3. Logins to have handy on the call
Your agent gets a real computer with a browser. Anything you want it to do as you (post in Skool, send WhatsApp messages, follow up on Instagram) needs you to log in once on that computer during the call. Have those passwords ready, and 2FA on your phone.
4. The day of the call
- Keys in a private text file. Never post them in a public channel or on a shared screen.
- Codex or Claude Code open and logged in.
- Bring your admin or operations person. The agent is for them to run. You're the CEO; this isn't your role.
- Ten minutes before we start, paste the block below into the installer so it builds while we talk.
5. Fill-in block (paste this into the installer)
AGENT_NAME: PRESET: # we'll tell you which one (e.g. community-setter, go-to-market, head-of-ops) CHANNELS: slack SKILLS: # optional, e.g. skool, whatsapp ORGO_API_KEY: ORGO_WORKSPACE_ID: OPENROUTER_API_KEY: COMPOSIO_API_KEY: # optional SLACK_WORKSPACE: SLACK_ALLOWED_USER_IDS: # optional, leave blank TELEGRAM_BOT_TOKEN: # optional SOUL: (paste your answers from 2b) JOB: (paste your answers from 2c)
Fill this in a private file on your own computer. Don't paste your keys into email, Slack channels or anywhere public.
6. After the call: your first five prompts
- "Introduce yourself and tell me what you understand your job to be."
- "Here's our Slack channel for leads. From now on, watch it and draft replies for me to approve."
- "Pull my calendar for the week and flag anything that shouldn't be there."
- "Write the Monday report format we agreed on and send me a sample."
- "What do you need from me to do your job better?"
Then connect any remaining tools in Composio, and bring your questions to the weekly support call in the group.