GTM philosophy

01What is it?
Turns proven go-to-market practices into repeatable principles for scaling outbound, sales, messaging, and revenue execution. It stands out by giving go-to-market work a defined shape, so the agent asks for better context and returns a more usable result.
02Inputs
Context for go-to-market work: your goals, audience, constraints, and any source material the skill asks for.
03Output
A ready-to-use result for go-to-market work: the analysis, copy, or recommendations the agent produces.
Paste-ready

Install as a package

Installs this one skill package for your coding agent, including any supporting files that skill ships with — not every skill in the repository. Read the tutorial.

Terminal
$ npx skills add sachacoldiq/coldiq-s-gtm-skills --skill gtm-philosophy

Use in Profound

Copy this file into a new Profound Skill. That's it, nothing else to install.

Copy and create in Profound
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?

How do I install GTM philosophy in Cursor, Claude Code, or Codex?

Run npx skills add sachacoldiq/coldiq-s-gtm-skills --skill gtm-philosophy in the project where you want it, then ask your agent for the skill by name. The --skill flag installs only GTM philosophy, not every skill in the repository.

Where does GTM philosophy come from and what license is it under?

GTM philosophy comes from the sachacoldiq/coldiq-s-gtm-skills repository on GitHub. That repository has 184 GitHub stars. No license was detected on the source repository, so check with the author before redistributing it.

Prefer plain text? Read the GTM philosophy guide as markdown.