OTEAMS Go-To-Market Team

6Agents

5Phase Gates

7Anti-patterns

5Model Types

Team OGSM 團隊 OGSM 定義

O — OBJECTIVE

B2B company owners who watch the demo feel "this is not a toy, this is a tool" — and within one day of seeing the demo, they have produced real output from their own business data.

The feeling we are optimizing for: "I can't believe we weren't doing this before." Not "interesting technology." Not "maybe someday." Today.

G — GOAL

The first 3 test customers complete Free Scan → Install → First Article within 7 days. At least 1 of the 3 converts to paid at $499/month.

State Change: Prospect goes from "curious about AI content tools" → "paying customer who has already produced business value."

Success Criteria:
- Day 1: Free Scan delivered within 4 hours of first contact
- Day 2: Demo scheduled and completed
- Day 3: Install completed (≤30 min, no IT ticket needed)
- Day 7: First Article published on prospect's own site
- Day 7: Conversion decision made (yes/no — no ghosting)

---

S — STRATEGY

• S1: Prospect Researcher — Identify and qualify B2B company owners who have content gaps AND budget signals. Deliver a personalized dossier per prospect before any outreach.
• S2: Demo Builder — Build a live, customized demo that uses the prospect's own industry, products, and competitors — so they see their own business reflected back at them, not a generic example.
• S3: Outreach Writer — Write outreach that leads with a specific insight about the prospect's content gap — not a feature list. One email, one hook, one call to action.
• S4: Onboarding Manager — Make the first 72 hours frictionless. Handle install, first scan, first article — with the prospect doing as little as possible while feeling maximum ownership.
• S5: Success Tracker — Monitor progress for all active prospects. Flag any prospect who is behind schedule. Trigger intervention before they go cold.

Agent Roster Agent 成員

Agent 0: Team Leader

B2B company owners who watch the demo feel "this is not a toy, this is a tool" — and within one day of seeing the demo, they have produced real output from their own business data.

G: Every task output genuinely serves the O — not just "process completed" but "audience felt what O promised." Each touchpoint must move the prospect closer to the "not a toy, a tool" feeling, not just
Input: Company name + website URL + industry vertical (new prospect) OR pipeline status update (active prospect)
Output: Phase orchestration decisions + final acceptance signal + cohort retrospective entry

Opus

Agent 1: Prospect Researcher

The salesperson walks into a demo call knowing more about the prospect's content situation than the prospect does.

G: Raw company name → full prospect dossier with content gap analysis, budget signals, and 3 recommended hooks.
Input: Company name + website URL + industry vertical
Output: - `docs/oteams-gtm/prospects/{company-slug}/dossier.md` — full prospect brief

SonnetGeminiGPT

Agent 2: Demo Builder

The prospect watching the demo thinks "this is showing my industry, my products, my competitors" — not a generic technology demo.

G: Prospect dossier → live demo environment configured with prospect-specific industry, products, and competitor examples.
Input: - `docs/oteams-gtm/prospects/{company-slug}/dossier.md`
Output: - `docs/oteams-gtm/prospects/{company-slug}/demo-article.md` — sample article in prospect's voice

OpusSonnetScript

Agent 3: Outreach Writer

The prospect reads the first outreach message and thinks "they know something specific about my situation" — not "here is another mass email." They reply within 24 hours.

G: Prospect dossier + hooks → 1 outreach email + 1 follow-up that together produce a booked demo call.
Input: - `docs/oteams-gtm/prospects/{company-slug}/dossier.md`
Output: - `docs/oteams-gtm/prospects/{company-slug}/email-1.md` — initial outreach (Day 1)

Sonnet

Agent 4: Onboarding Manager

The prospect completes their first published article within 7 days of signing up — and feels like they did it themselves.

G: Signed prospect → installed, onboarded, first article published.
Input: - `docs/oteams-gtm/prospects/{company-slug}/dossier.md`
Output: - `docs/oteams-gtm/prospects/{company-slug}/onboarding-log.md` — timestamped log of all steps

OpusSonnet

Agent 5: Success Tracker

No prospect slips through the cracks.

G: All active prospects tracked in real-time dashboard.
Input: All prospect logs from Agents 1–4
Output: - `docs/oteams-gtm/pipeline/pipeline.md` — live pipeline (updated continuously)

Sonnet

Phase Gates 階段管控點

Gate 1

Phase Gate 1: After Agent 1 (Prospect Qualified)

Dossier complete with ≥3 content gaps AND budget signal AND 3 hooks.

Gate 2

Phase Gate 2: After Agent 2 (Demo Ready)

Demo article ≥600 words AND demo script exists AND demo config exists AND ready ≥4h before call.

Gate 3

Phase Gate 3: After Demo Call (Prospect Progresses)

Prospect agrees to install AND onboarding call scheduled.

Gate 4

Phase Gate 4: After Agent 4 Day 3 (Onboarding On Track)

Install confirmed AND first article draft in progress.

Gate 5

Phase Gate 5: Day 7 (Conversion Decision)

First article published AND conversion decision received (yes or no).

Anti-patterns 反模式（禁止行為）

NOT: Lead outreach with feature list →→INSTEAD: Lead with a specific verified insight about the prospect's content gap

NOT: Generic demo with stock examples →→INSTEAD: Demo pre-loaded with prospect's industry, products, and competitor names

NOT: "Imagine if you could..." framing →→INSTEAD: "Here is what we already found about your content situation"

NOT: Install requires IT ticket or >30 min →→INSTEAD: Customer installs themselves in ≤30 min; if not, escalate same day

NOT: First article is a template filler →→INSTEAD: First article is in the customer's exact voice with their exact products (use Opus)

NOT: Day 7 passes without a conversion decision →→INSTEAD: Send direct yes/no ask by Day 6. No ghosting tolerated.

NOT: Tracking in individual heads or Slack threads →→INSTEAD: All prospect status in pipeline.md, updated every 24h

---