agentleFS
Frontal-soFrontal-so/outbound-skills/skills/gtm-philosophy/SKILL.md

gtm-philosophy

Skill8 starsChanged 4 months agoMITView on GitHub

Core GTM philosophy principles and multi-channel coordination strategy. Use when defining outbound strategy, training sales teams, or establishing GTM fundamentals.

2 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use specific numbers, not vague claims

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Core GTM Philosophy

Fundamental Principles

  1. Scale what top performers do - Study best reps, systematize their approach
  2. Diagnose before prescribing - BIPSY framework: Behaviors, Individual, Process, Skill, You
  3. Signal-based outreach = 3-4x higher contract values
  4. You can't burn your TAM - Re-engage with new angles
  5. Lead with pain, not features - HockeyStack approach: "Do you have problems tying brand awareness to revenue?"
  6. Segment and convert, don't over-personalize - Gorgias went from 200 sequences to 10 modular ones

Multi-Channel Coordination

The Data:

  • Email + ads + referrals = extra $2M ARR (case study)
  • ABM approach = 36% meeting rate vs 10% non-ABM
  • Warm before you touch principle

Coordination Strategy:

ChannelRoleTiming
AdsWarm up, build awarenessBefore outreach
EmailPrimary outreachDay 1
LinkedInSecondary touchDay 2-3
PhoneHigh-intent follow-upAfter engagement
ReferralsLeverage networkThroughout

Key Mindsets

On Personalization

  • Personalize to the person, not just the company
  • Use specific numbers, not vague claims
  • Research should inform approach, not just first line

On Volume vs Quality

  • Quality signals beat high volume
  • 100 signal-based emails > 1000 cold emails
  • Stack signals for heat scoring (3+ signals = reach out same day)

On Timing

  • New role signals peak at days 14-45
  • Website visitors: act within 24-48 hours
  • Funding announcements: wait 2-4 weeks

On Messaging

  • Lead with pain, not features
  • Soft CTAs outperform hard asks
  • Humor reduces tension and increases response

Combines with

SkillWhy
buying-signals-6Implement signal-based philosophy
outreach-4-categoriesCategorize leads properly
sdr-outbound-rulesApply philosophy to daily execution
josh-braun-copywritingWrite messages that lead with pain

Example prompts

How should I structure multi-channel coordination for a $50K ACV deal?
Explain the BIPSY framework for diagnosing my SDR team's issues.
How do I balance volume vs quality for a mid-market SaaS product?

Part of Frontal — free, open GTM skills for your AI agent. Browse the library →

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.