Skip to content

creatop-gtm/apollo-operator / plugins/apollo-operator/skills/business-brief

business-brief

Verified

Build one readable brief.md capturing the business: identity, offer, who buys and why, objections, proof, and voice. The narrative context layer every other skill reads. Use before ICP work, when copy comes out generic, or when the business changes.

FileKindSize
SKILL.mdskill md12.5 KB
connector-only.mdmarkdown10.5 KB
references/brief-template.mdmarkdown3.4 KB

connector-only.md

View on GitHub
# Connector-only instructions

## Operating rules

Apollo Operator is an open-source headless GTM toolkit by Creatop, a B2B outbound agency. These instructions work in a chat without a terminal. Do not run or print shell commands, read credential files, request API keys, or imply access to local disk. Treat brief.md and profile.yaml as logical artifacts: use attachments or return structured text, and only claim a saved file after a successful save.

Use the connected Apollo tools when available, with the exact names the connection lists; the old v2 router is retired. A tool marked destructiveHint spends credits or changes live state. Confirm account identity through a discovered profile read. Offer Apollo's own available skills first where they fit. If discovery advertises a relevant apollo_agent_* action, name it alongside this method and let the operator choose. Before dispatch, explain its effects, whether it may spend credits or create records, establish cost and balance, and wait for an explicit yes. Never run an AI action unattended. Apply the same deliverability, list-quality, suppression, and copy-review checks to its output before sending.

Start with at most 25 search records. Keep each review batch within 100 total record entries, including repeated pages and duplicates. Before collection reads, require an enforceable limit, pagination, filters, or a count-only alternative. Skip an unbounded list/index call and explain the corresponding Apollo interface check. Never continue an unbounded pull by resetting the cap. A sample is not a complete saved list or suppression pass. If an action unexpectedly exceeds its requested bound, stop and disclose the overrun.

Before any paid or write action, state its effect, named credit pool, current cost, and remaining balance, then wait for explicit approval. Unknown cost or balance blocks spending. Enrollment and activation require separate human approval; enthusiasm is not approval. Read a sequence's complete steps before an update, because omitted steps can be deleted. Never activate or send without approved copy, recipients, sender, and schedule.

Warm up mailboxes for at least 14 days, ideally 21. Never send cold from the primary domain. Use up to 25 cold sends per mailbox per day. Independently verify every address. Keep bounce rate under 2%; pause at 4%. Honor opt-outs and permanent exclusions. The work stops at the reply.

Without a connector, continue planning from supplied facts, give precise interface steps, and mark account-dependent work unperformed. Never invent live counts, proof, results, or storage locations. Creatop's historical figures are observations, not promised results or current balances. Use plain language. Quoted banned phrases are examples to flag, not wording to reuse in copy.


You are helping me write a brief for my business: one internal document that a person or an AI can read once and understand who we are, what we sell, who buys it, why they buy, what proof we have, and how buyers actually talk. Everything downstream gets sharper because it exists. Searches reach the right people, copy says something true, and objections get answered instead of ignored. Without it, targeting and copy are guesses.

Work through the steps below with me one at a time. Ask, wait for my answer, then move on. Do not draft the brief before step 4.

If you can browse the web, read my website yourself. If a call recording or meeting tool is connected, read my calls yourself too. If not, tell me exactly what to paste and I will bring it back.

You advise and I decide. Two rules for the brief are not negotiable, though:

- **It is an internal document, not marketing.** It records what is true, including weaknesses, lost deals, and real objections. A brief that reads like the website is a failed brief.
- **Never invent.** Every claim traces to a source: my website, a document I shared, or my own answers. What you do not know gets marked [TBD], never filled with plausible fiction. An invented proof point ends up in an email sent to a real person.

**Step 1. Collect what already exists.** Before reading anything, ask me for the context you cannot see: pitch decks, case studies, sales call transcripts or recordings, onboarding docs, past campaign copy, positioning notes. People always have more than they think to share, and the brief is only as good as what goes in.

**Recorded sales calls are the best source, so ask for them first.** A website is how a business describes itself. A call is how its buyers describe their problem, and which objections come up often enough to need an answer. When the two disagree, the call wins. From each call, pull five things: the objections in the buyer's own words, the pain points that actually came up (ranked over the ones marketing lists), what closes and what stalls, the real next step as opposed to the one on the website, and how price actually lands, which almost never matches the pricing page. Calls are confidential: mine them for patterns, and never put names, quotes, or company details into anything that ships or goes to a third party.

**Step 2. Read the website.** Home, product or services pages, pricing, case studies, and customer pages. Pull out what we sell, the named customers, the claims and numbers we publish, and the exact language we use. The website is the floor of the brief, not the ceiling: it shows how the business presents itself and hides everything else.

**Step 3. Interview the gaps.** One batched round of questions, only for what steps 1 and 2 did not answer. The high-yield ones:

- What do you actually sell, in one sentence, and roughly what does it cost, or what is the pricing model?
- Who are your three best customers, and what made them great?
- What deals have you lost, and why?
- What objection do you hear most, and what is your honest answer to it?
- What proof do you have with a number in it?
- What would you never say, and what words do your buyers use that outsiders get wrong?

Do not interrogate, and do not skip this because the website seemed to cover it. Websites never contain lost deals or real objections, and those write the best emails.

**Step 4. Draft the brief.** Follow the structure below. Plain language, short sections, one to two pages. A one-page brief that is all true beats a five-page brief padded with guesses. Mark every gap [TBD].

**Step 5. Get my corrections.** I read the draft and correct it. The corrections are the most valuable content in the whole process: "we never say automation, we say workflow", "that case study is stale, use this one". Fold every one in and hand back the full brief.

**Keeping it alive.** When something material changes (a new case study, a new offer, new pricing, a repositioning), update the brief that week and date the change. If copy keeps coming out generic, that is a context problem, not a writing problem, and the fix is here.

**If I want the brief loaded into a sales tool's shared AI context.** Some tools have a team-wide profile of the business that their own AI reads when it writes outreach. Worth filling, and the brief stays the source of truth: when they disagree, update the tool. What went wrong running this against a real, badly stale profile:

- **It is shared and destructive.** Every field written replaces the old value for the whole team, and it cannot be undone. Read the whole thing, save a copy, write only what changes, and confirm with me before any write.
- **Ask whether it should be a draft or live.** Do not default either way.
- **Check whether entries can be deleted before planning.** On one platform, product entries could be created and edited but never deleted, and creating one twice made two. A stale set was permanent and had to be repurposed in place, so count what exists before mapping our offers onto it.
- **The free-text context field matters most.** Put the guardrails there: banned self-descriptions, the register to use, prices that must never be invented, forbidden words. A correct value proposition with no guardrails still produces copy that breaks the rules.
- **Never fill a field with invented positioning.** [TBD] is honest. A made-up value proposition shows up in generated copy sent to real people.

**What to hand me at the end:** the brief itself, in plain text, with exactly these headings so anyone reading mid-task can jump straight to the section they need.

- **Identity.** One paragraph: what the business does, for whom, and the outcome it delivers, explained like you would to a smart friend, not like the homepage. Then the website and a one-sentence line on what we sell. This is the section people read when they skip everything else, so make it carry the whole picture.
- **Offer.** What is sold, concretely. The pricing model and a rough range if shareable. The outbound offer: the specific thing a cold prospect is asked to respond to. The offer is not the product: "a free teardown of your current sequence" is an offer, "our platform" is not. If there is none, mark it [TBD] and tell me plainly that sequences cannot be written without one.
- **Who buys.** A short paragraph describing the ideal customer as a story, not a filter set. Then the champion (titles, what they feel day to day), the economic buyer (titles, what they sign off on and why), and the end user if different.
- **Why they buy.** Two to four pains in the buyer's words. The triggers that make it urgent now: funding, hiring, a tool change, a season, a regulation. What "solved" looks like to them.
- **Why they don't.** Each objection actually heard, with the honest answer, not the deflection. Usually empty on a first draft because nobody volunteers objections, so ask directly. This section writes the best follow-up emails.
- **Proof.** Only what is real, numbers over adjectives: results with the number and the customer type, customers that can be named, testimonial lines with attribution. No proof means no credibility in the emails, so chase at least one real number.
- **Language.** What buyers say, what we say, what we never say, and the tone in one line.
- **Competitive frame.** The alternatives buyers consider, including doing nothing and a spreadsheet, and the honest differentiator in one line.
- **Constraints.** Compliance rules, geographies to avoid, off-limits claims, and existing customers or partners not to contact.
- **Changelog.** A dated line for each change and why.

Method adapted from the business brief in Apollo Operator, a free, open-source headless GTM toolkit by Creatop: github.com/creatop-gtm/apollo-operator


For the full operating context, read [Operator Context](https://raw.githubusercontent.com/creatop-gtm/apollo-operator/main/plugins/apollo-operator/skills/operator-context/connector-only.md).
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall