client-onboarding

Full client onboarding: intelligence gathering, synthesis into Client Intelligence Package, and growth strategy generation. Phases 1-3 of the Client Launch Playbook.

381 stars

Best use case

client-onboarding is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Full client onboarding: intelligence gathering, synthesis into Client Intelligence Package, and growth strategy generation. Phases 1-3 of the Client Launch Playbook.

Teams using client-onboarding should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/client-onboarding/SKILL.md --create-dirs "https://raw.githubusercontent.com/gooseworks-ai/goose-skills/main/skills/playbooks/client-onboarding/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/client-onboarding/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How client-onboarding Compares

Feature / Agentclient-onboardingStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Full client onboarding: intelligence gathering, synthesis into Client Intelligence Package, and growth strategy generation. Phases 1-3 of the Client Launch Playbook.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Client Onboarding

Full onboarding playbook for a new client. Produces a Client Intelligence Package and Growth Strategy Recommendations.

Reference: docs/agency-playbook/client-launch-playbook.md for the full process documentation.

## When to Use

- "Onboard [company name] as a new client"
- "Run the full intelligence gathering for [company]"
- "Create a growth strategy for [company]"

## Prerequisites

- Company name and website URL
- Basic understanding of what the company does (or the agent will research it)

## Phase 1: Intelligence Gathering (~30 min parallel agent work)

### Setup

First, create the client folder structure:

```
clients/<client-name>/
├── context.md              # Will be populated during research
├── notes.md                # Running log
├── intelligence/           # All Phase 1 outputs go here
├── strategies/             # Will be populated after strategy approval
├── campaigns/
├── leads/
└── content/
```

### Step 1: Company Deep Research
- Deep web research: product, pricing, team, funding, customers, tech stack, recent news
- **Method**: Web search + web fetch
- **Output**: `clients/<client-name>/intelligence/company-research.md`

### Step 2: Competitor Deep Research
- Identify top 5-10 competitors, research positioning, pricing, strengths, weaknesses
- **Method**: Web search + web fetch
- **Output**: `clients/<client-name>/intelligence/competitor-research.md`

### Step 3: Founder Deep Research
- Research founders: backgrounds, LinkedIn presence, thought leadership, public visibility
- **Method**: Web search + linkedin-profile-post-scraper
- **Output**: `clients/<client-name>/intelligence/founder-research.md`

### Step 4: SEO Content Audit
- Full SEO footprint: content inventory, domain metrics, competitive gaps, brand voice
- **Skill**: seo-content-audit (orchestrates site-content-catalog + seo-domain-analyzer + brand-voice-extractor)
- **Output**: `clients/<client-name>/intelligence/seo-content-audit.md`

### Step 5: AEO Visibility Check
- Test visibility across AI answer engines for key queries
- **Skill**: aeo-visibility
- **Output**: `clients/<client-name>/intelligence/aeo-visibility.md`

### Step 6: Paid Ads Strategy Review
- Scrape active Meta and Google ads for client and top competitors
- **Skill**: meta-ad-scraper + google-ad-scraper
- **Output**: `clients/<client-name>/intelligence/ad-strategy.md`

### Step 7: Industry Intelligence Scan
- Scan everything happening in the client's industry in the past week
- **Skill**: industry-scanner
- **Output**: `clients/<client-name>/intelligence/industry-scan.md`

### Step 8: Current GTM Analysis
- Score the client's current GTM across all dimensions
- **Skill**: company-current-gtm-analysis
- **Output**: `clients/<client-name>/intelligence/gtm-analysis.md`

### Parallel Execution Plan

```
Parallel Group A (general research — run simultaneously):
  Step 1: Company Deep Research
  Step 2: Competitor Deep Research
  Step 3: Founder Deep Research

Parallel Group B (automated audits — run simultaneously):
  Step 4: SEO Content Audit
  Step 5: AEO Visibility Check
  Step 6: Paid Ads Strategy Review
  Step 7: Industry Intelligence Scan
  Step 8: Current GTM Analysis
```

Groups A and B can run in parallel with each other.

## Phase 2: Synthesis & Diagnosis

Read all Phase 1 outputs and synthesize into a single Client Intelligence Package.

**Reference framework**: docs/growth-frameworks.md

### Diagnostic Steps

1. **Assess PMF**: Does the retention curve flatten? (Pre-PMF / PMF / Strong PMF)
2. **Determine ACV tier**: What viable channels does their price point support?
3. **Identify growth motion**: Product-led, marketing-led, sales-led, or blended?
4. **Assess scaling stage**: Pre-PMF → PMF → GTM Fit → Growth & Moat
5. **Score current GTM**: Rate each dimension A-F (from gtm-analysis output)
6. **Map competitive landscape**: Top 5 competitors with strengths/weaknesses
7. **Identify opportunity gaps**: Which Growth Matrix cells are empty?
8. **Flag risk factors**: Competitive threats, market risks, internal constraints

### Output

**File**: `clients/<client-name>/intelligence-package.md`

Structure:
1. Company Profile
2. Stage Assessment (PMF, ACV, Motion, Scaling Stage)
3. Current GTM Scorecard (A-F per dimension)
4. Competitive Landscape
5. Industry Context
6. Opportunity Map (Growth Matrix gaps)
7. Risk Factors

## Phase 3: Strategy Generation

Read the Intelligence Package and generate prioritized growth strategies.

### Strategy Generation Process

For each identified opportunity gap:

1. **Name the system**: Map to the Growth Systems Taxonomy (Intelligence / Demand Creation / Pipeline)
2. **Describe the gap**: What's missing or broken?
3. **Propose the solution**: What system do we build? What skills power it?
4. **Estimate impact**: Expected lift based on available data
5. **Sequence**: P0 (immediate), P1 (4-6 weeks), P2 (8-10 weeks)
6. **Score**: ICE score (Impact x Confidence x Ease, each 1-10)
7. **Tag the execution pattern**: Add a structured `<!-- execution ... -->` YAML block identifying the pattern, signal type, required skills, estimated cost, and estimated lead volume. See [Structured Execution Tags](#structured-execution-tags) below for the format.

### Prioritization Rules

1. Activation before acquisition (if activation is broken, fix that first)
2. One channel deep before expanding
3. Engine over boost (compounding loops > one-time campaigns)
4. Always include at least one quick-win Pipeline strategy alongside longer-term Demand Creation
5. Match channel to ACV (no field sales for <$5K ACV)

### Output

**File**: `clients/<client-name>/growth-strategies.md`

Format: P0/P1/P2 grouped strategies with gap, solution, tactical steps, expected impact, timeline.

See `clients/vapi/growth-strategies.md` as a reference example.

### Structured Execution Tags

Every strategy in `growth-strategies.md` must include a machine-readable execution tag as an HTML comment block. This allows the `client-packet-engine` playbook to automatically route strategies to the correct skill chains.

#### Format

```markdown
<!-- execution
pattern: signal-outbound
signal_type: job-posting
signal_keywords: ["DevOps", "SRE", "platform engineer"]
target_titles: ["VP Engineering", "CTO", "Head of Platform"]
estimated_leads: 50
estimated_cost: 0.80
skills_required:
  - job-posting-intent
  - company-contact-finder
  - email-drafting
-->
```

#### Fields

| Field | Required | Description |
|-------|----------|-------------|
| `pattern` | Yes | Execution pattern: `signal-outbound`, `content-lead-gen`, `competitive-displacement`, `event-prospecting`, `lifecycle-timing`, or `manual` |
| `signal_type` | If signal-outbound | Signal source: `job-posting`, `linkedin-post`, `review-sentiment`, `funding`, `product-launch` |
| `signal_keywords` | If signal-outbound | Keywords to detect the signal |
| `target_titles` | If applicable | Decision-maker titles to target |
| `competitor_name` | If competitive-displacement | Competitor to displace |
| `event_keywords` | If event-prospecting | Keywords to find relevant events |
| `content_type` | If content-lead-gen | Asset type: `comparison-page`, `industry-report`, `blog-post`, `landing-page` |
| `trigger_type` | If lifecycle-timing | Trigger: `fiscal-year-end`, `contract-renewal`, `quarterly-review`, `seasonal` |
| `timing_window` | If lifecycle-timing | When to execute (e.g., "Q4", "30 days before renewal") |
| `estimated_leads` | Yes | Conservative estimate of leads this strategy will produce |
| `estimated_cost` | Yes | Estimated Apify/API cost in dollars |
| `skills_required` | Yes | Ordered list of skills in the execution chain |

#### Pattern Selection Guide

| Pattern | Use When | Primary Signal |
|---------|----------|---------------|
| `signal-outbound` | A buying signal (hiring, social activity, review complaints) maps to outreach | Job posts, LinkedIn posts, reviews |
| `content-lead-gen` | Strategy involves creating a content asset to attract or nurture leads | SEO gaps, thought leadership opportunities |
| `competitive-displacement` | Strategy targets a competitor's unhappy or at-risk customers | Negative reviews, competitor weaknesses, archived customer lists |
| `event-prospecting` | Strategy involves finding and engaging event attendees or speakers | Conferences, meetups, webinars |
| `lifecycle-timing` | Strategy depends on timing a trigger event (renewals, fiscal year, seasonal) | Business cycle triggers |
| `manual` | Strategy requires human judgment, relationships, or tools not yet automated | Partnerships, enterprise sales, brand campaigns |

#### Examples

**Signal-Outbound (job posting intent)**:
```markdown
### Strategy 1: DevOps Hiring Signal Outbound

Companies hiring DevOps/SRE roles likely need infrastructure tooling...

<!-- execution
pattern: signal-outbound
signal_type: job-posting
signal_keywords: ["DevOps", "SRE", "platform engineer", "infrastructure"]
target_titles: ["VP Engineering", "CTO", "Head of Platform"]
estimated_leads: 50
estimated_cost: 0.80
skills_required:
  - job-posting-intent
  - company-contact-finder
  - email-drafting
-->
```

**Competitive-Displacement**:
```markdown
### Strategy 3: Capture Unhappy BigCo Customers

BigCo has declining review scores on G2 and recent feature removals...

<!-- execution
pattern: competitive-displacement
competitor_name: BigCo
target_titles: ["Head of Operations", "VP Product", "CTO"]
estimated_leads: 30
estimated_cost: 1.20
skills_required:
  - web-archive-scraper
  - review-scraper
  - company-contact-finder
  - email-drafting
  - content-asset-creator
-->
```

**Manual (no automation available)**:
```markdown
### Strategy 6: Partner Co-Marketing Program

Build joint content and referral agreements with complementary tools...

<!-- execution
pattern: manual
estimated_leads: 0
estimated_cost: 0
skills_required: []
-->
```

#### Rules

1. **Every strategy gets tagged** — even manual ones. This ensures the packet engine can account for all strategies.
2. **Be specific with `signal_type`** — don't use generic descriptions. Map to the exact signal source the skill will scan.
3. **List all skills in chain** — in execution order. The packet engine uses this to plan parallel execution.
4. **Estimate conservatively** — overestimate cost, underestimate leads. Better to over-deliver than under-deliver.
5. **Use `manual` sparingly** — if a strategy can be even partially automated, tag it with the automatable pattern and note limitations in the strategy description.

## Human Checkpoints

- **After Phase 2**: Review the Intelligence Package for accuracy before generating strategies
- **After Phase 3**: Review strategies with client before implementation

Related Skills

client-packet-engine

381
from gooseworks-ai/goose-skills

Batch client packet generator. Takes company names/URLs, runs intelligence + strategy generation, presents strategies for human selection, executes selected strategies in pitch-packet mode (no live campaigns or paid enrichment), and packages into local delivery packets.

client-package-notion

381
from gooseworks-ai/goose-skills

Package all work done for a client into a shareable Notion page with subpages and Google Sheets. Reads the client's folder (strategies, campaigns, content, leads, notes) and builds a structured Notion workspace the client can browse. Lead list CSVs are uploaded to Google Sheets and linked from the Notion pages. Use when you want to deliver work to a client in a polished, navigable format.

client-package-local

381
from gooseworks-ai/goose-skills

Package all work done for a client into a local filesystem delivery package with .md files and Google Sheets. Reads the client's folder (strategies, campaigns, content, leads, notes) and builds a structured directory with dated deliverables. Lead lists are uploaded to Google Sheets and linked from the markdown files. Use when you want to deliver work to a client in a polished, navigable format without requiring Notion.

competitor-monitoring-system

381
from gooseworks-ai/goose-skills

Set up and run ongoing competitive intelligence monitoring for a client. Tracks competitor content, ads, reviews, social, and product moves.

lead-discovery

381
from gooseworks-ai/goose-skills

Orchestrator that runs first for lead generation requests. Gathers business context via website analysis or questions, identifies competitors, builds ICP, and routes to signal skills with pre-filled inputs.

serp-feature-sniper

381
from gooseworks-ai/goose-skills

Analyze SERP features per keyword (featured snippets, PAA, video carousels, knowledge panels, image packs) and produce optimized content structures to win them. Identifies which features are winnable, who currently holds them, and exactly how to format your content to steal them.

search-ad-keyword-architect

381
from gooseworks-ai/goose-skills

Deep keyword research for paid search. Analyzes competitor SEO keywords, review language, Reddit/community terminology, and existing site content to build a keyword architecture: branded vs non-branded, funnel stage mapping, match type recommendations, and estimated competition tiers. Use before building a Google Ads campaign or to audit an existing one.

sales-performance-review

381
from gooseworks-ai/goose-skills

Periodic sales performance review composite. Aggregates ALL sales initiatives taken in a given period — outbound campaigns, inbound efforts, events, partnerships, content, referrals — and measures the impact of each on pipeline and revenue. Produces a team-presentable report covering initiative-level performance, cross-initiative comparisons, pipeline attribution, what's working, what's not, and where to invest next. Tool-agnostic — pulls data from any combination of CRM, outreach tools, and tracking systems.

qbr-deck-builder

381
from gooseworks-ai/goose-skills

Pull customer usage highlights, support history, feature adoption, NPS/CSAT data, and ROI metrics into a structured QBR deck outline with slide-by-slide content. Outputs markdown slide content ready for HTML slides or Google Slides. Designed for CS teams at seed/Series A who run QBRs but don't have time to build decks from scratch.

customer-story-builder

381
from gooseworks-ai/goose-skills

Take raw customer inputs — interview transcripts, survey responses, Slack quotes, support tickets, review excerpts — and generate a structured case study draft with problem/solution/result narrative, pull-quotes, metric callouts, and multi-format outputs (full case study, one-pager, social proof snippet, sales deck slide). Pure reasoning skill. Use when a product marketing team has customer signal but no time to write the story.

content-repurposer

381
from gooseworks-ai/goose-skills

Take a long-form asset (blog post, webinar, podcast, LinkedIn article) and generate 10+ derivative pieces ready to publish: LinkedIn posts, tweets/X threads, email snippets, short-form hooks, and pull-quotes. Pure reasoning skill — no scripts, no scraping. Use when a founder or marketer has created one piece of content and needs to distribute it across multiple channels without writing each variant from scratch.

competitor-content-tracker

381
from gooseworks-ai/goose-skills

Monitor competitor content across blogs, LinkedIn, and Twitter/X on a recurring basis. Surfaces new posts, trending topics, and content gaps you can own. Chains blog-scraper, linkedin-profile-post-scraper, and twitter-scraper. Use when you want a weekly digest of what competitors are publishing and which topics are generating engagement.