Oct 12, 2026 · 7 min read
Ommnium for Founder-Led Sales
Sell as a founder with a small Agent team that researches, drafts and stages the work, while every send and every big call stays yours.
Ana Ruiz still runs sales for the Ruiz & Okafor studio herself. She finds the accounts, writes the first emails, preps the calls, sends the recaps and keeps the deal sheet honest. Each job is small. Together they crowd out building and talking to customers.
This guide sets up one Project where a small Agent team researches, drafts and stages. Ana keeps the conversations that teach her how the studio sells: discovery, pricing and the yes. Nothing reaches a prospect until she presses send.
The team
People and Agents work in the same Channels. Sam and Lea can read every brief and draft, add a line in the thread, or @mention a seat themselves. There is no side chat you can't see.
| Agent | Its one job | Never does |
|---|---|---|
| Chief of Staff (@chief-of-staff), lead | One daily action list (with the Friday digest and a Monday revenue check), a monthly investor update draft; raises urgent customer issues at once | Sends anything |
| Seller (@seller) | Call briefs before, recaps and follow-ups after, stage proposals | Quotes pricing or terms without you |
| Sequencer (@sequencer) | The morning outbound batch and follow-up cadence on your deal sheet | Drafts to an open deal, a customer or anyone marked do-not-contact |
| Feedback Analyst (@feedback-analyst) | Weekly themes from feedback, calls and support mail | Contacts customers |
| Competitor Watch (@competitor-watch) | Checks the competitor pages you list, in its browser, and briefs real changes | Signs up or contacts anyone |
| Copycat (@copycat) | Posts, case studies and launch notes in your voice | Publishes |
| Social Watch (@social-watch) | Scans LinkedIn and target accounts' posts in its browser each weekday, drafts replies, hands people who engage to Sequencer | Posts, comments or connects without you |
People: Ana (founder; owns every send), Sam and Lea (product and design; they answer in threads).
Channels: #general (daily list, call briefs, the outbound batch, themes, urgent issues), #pipeline (one thread per deal: recaps and stage changes), #marketing (social replies and posts).
Set it up
- Install the team. Agents → "Agent teams" → Company HQ under "Ready to install". Open it to see its six Agents, the tools each needs and its suggested automations, then press "Install team".
- Choose a new Project and name it
company-hq. - Connect Gmail, Google Calendar, Google Sheets (your deal tracker), Granola for call notes, and Exa or Tavily for web research in the one list. Gmail is read plus drafts. HubSpot asks for your own OAuth app details in "Set up HubSpot"; Attio connects in one click. Stripe or Mercury powers the revenue check.
- Keep "Daily action list", "Outbound batch" and "Morning call prep" checked; add "Weekly customer themes", "Competitor pulse" or "Investor update draft" if you like. Every automation starts switched off and posts in
#general.
- Choose a new Project and name it
- Answer the kickoff. You land in
#general. Chief of Staff introduces the team and asks a few kickoff questions, one card at a time: who you sell to, where deals live, who is off limits, what counts as urgent, and whether Copycat should learn your voice now. - Add Channels. Project ⋯ → "New channel" for
pipelineandmarketing, each with its brief in "Description". Agents read the Channel description on every turn. Then Project → "People & Agents" → "Agents" "+" → "Deploy team" →#pipeline→ "Deploy to 1 channel". Seats wake only when mentioned. - Add Social Watch. Ask "Agent Builder" in a DM (prompt below), or + card → "Create agent". A Channel holds six Agents, so
#marketingstays small: on the profiles of Social Watch, Copycat, Competitor Watch and Sequencer, "Channels" → "Add to channel" →#marketing. Sign in to LinkedIn and X once in its browser yourself, including any two-factor step; Agents never type passwords. - Choose who can instruct them. For Sam and Lea: profile → "Setup" → "Who can instruct" → "Selected people". Anyone who can instruct an Agent can use its accounts, so choose carefully.
- Turn on the first three in the Project's "Automations" tab.
The team comes with instructions like these; change them with the team's ⋯ → "Edit":
Work in the open. @chief-of-staff leads and routes each ask by @mentioning one seat in the request's thread; each seat posts its result there or in its Channel. A seat's yes is never a person's yes: sends, posts, spending, calendar and CRM changes go through a card Ana approves. Stay quiet when nothing changed. Shared facts go to Project memory.
Prefer to build it yourself? Create the Project and Channels, create the six Agents (Copycat is in the + card chooser), then "New team" → "Create team" with the instructions above, "Deploy team", and ask each seat for its automations switched off.
What happens each day
Asks before it acts
Questions, drafts, and keys come to you as cards. Nothing is sent without a yes. A live demo with sample data; try it.
- 7:00,
#general. The outbound batch arrives, marked "From automation:". Each prospect is KEEP, HOLD or DQ with one line on why; KEEP rows come with email draft cards. LinkedIn notes are drafts too; when Ana says yes on the card, Sequencer sends them from LinkedIn in its browser. - 7:30,
#general. Seller posts a brief for each call in its own thread: who is on the invite, what past emails and Granola notes say, three questions. - 8:00,
#general. Chief of Staff posts the action list. Ana edits each draft card in place and presses "Send email". One she can't send yet gets "Remind me later" and returns under Inbox → "Needs action". - 9:00,
#general. Competitor Watch's pulse runs in its browser. One competitor changed its pricing page, so it posts the link and why it matters. - 9:30,
#marketing. Social Watch lists who engaged overnight on LinkedIn, with a drafted reply each, and @mentions @sequencer with the two who fit. - 11:40,
#pipeline. After a discovery call, Ana writes "@seller recap this" in the deal's thread. Seller posts a recap draft card and a question card: move the deal to the next stage? Her answer goes back to Seller, which updates the sheet, proposes two times for the follow-up call, and creates the invite once she picks one. - Friday. Feedback Analyst posts ranked themes as a visual in
#generaland @mentions Sam when one crosses Ana's bar. The Friday action list adds the pipeline digest as a board of deals by stage.
Copy these prompts
Kickoff, in #general (if you skipped the lead's questions):
@chief-of-staff Interview me with question cards, one at a time: what we sell and to whom, who buys versus who feels the pain, which accounts are off limits, and what counts as urgent from a customer. Save the shared answers to Project memory.
The daily list, in #general (if you didn't check it at install):
@chief-of-staff Every weekday at 8:00, post one action list here: drafts waiting for my send, replies I owe, today's calls, anything urgent. Merge what the other Agents posted since yesterday. One line if nothing needs me. Save it switched off; I'll turn it on.
A design-partner scan, in #general:
@sequencer Find ten companies that could be design partners: they match our customer profile in Project memory and show a fresh signal, like a relevant post or a new hire. Check my deal sheet and Gmail first so you never list a customer or an open conversation. Sort into KEEP, HOLD or DQ with one line on why, and draft a short first touch for KEEP only, opening with the signal.
In your DM with Agent Builder:
Make an Agent named Social Watch for our company-hq Project. Each weekday at 9:30 it checks LinkedIn in its browser for posts by our target accounts and people who engaged with mine, drafts a reply for each in #marketing, and @mentions @sequencer with the ones who fit our customer profile. It never posts, comments or connects without my yes.
Remember for this Project: pricing, discounts and contract terms always come to me first.
Rules that keep it healthy
- Drafts before sends. Email and Slack arrive as draft cards; only you press send.
- Lead with a reason. Every first touch opens with something the account did.
- Quiet when nothing changed. One line, or nothing.
- One voice to you. Only the Chief of Staff pings you; seats post in their Channels.
- Corrections become rules. Say it twice, then ask the Agent to remember it.
- Keep the calls that teach you. Discovery, pricing and the yes stay yours.
What it can't do yet
- No sends or sequence enrolments on its own. The cadence lives on your sheet as drafts.
- No one-click HubSpot or Salesforce. Both need your own OAuth app; Attio is one click.
- No code from themes. No Agent opens pull requests for you.
- Six Agents per Channel. That is why
#marketingholds four seats, not the whole team.