Skip to content
SlashClone
DiscoverUse in ClaudeSubmit a link
Sign in
Made by@gtmengineer

Signal based outbound

@gtmengineer/signal-based-outbound

Define the buying signals that matter for your product (hiring, funding, leadership changes, tech changes, product usage, website intent, champion job changes) and turn each into a play: who to contact, the angle, the channel, how fast, and what it is worth. Produces a signals and plays playbook plus a machine-readable signals file any tool can use.

SkillRevOpsv1.0.0 (latest)
Use in Claude Save Like Clone Comment
Activity
New: be the first to try it
  1. 1# Signal-based outbound
  2. 2
  3. 3Works out which buying signals matter for your product and turns each one into a ready play: who to contact, what angle to use, which channel, and how fast. You get a readable playbook and a `signals.json` spec you can wire into any tool.
  4. 4
  5. 5## Who it is for
  6. 6
  7. 7GTM engineers, SDR leaders, and founders replacing "spray the list" outbound with outreach that has a reason to happen now. Vendor-neutral.
  8. 8
  9. 9## Example
  10. 10
  11. 11Input: "We sell forecasting and lead routing to RevOps teams at 200 to 2,000 person companies. Our last 8 wins: 5 had just opened a second sales team, 2 had a new RevOps leader, 1 came from a former champion."
  12. 12
  13. 13Output (`out/signals-playbook.md`):
  14. 14
  15. 15| Signal | Strength | Points | Decay | Play | Speed |
  16. 16| --- | --- | ---: | ---: | --- | --- |
  17. 17| Past champion joined a new company | Strong | 50 | 120 days | Champion reunion | 14 days |
  18. 18| Opening a new sales region | Strong | 40 | 60 days | New-team routing | 5 business days |
  19. 19| New RevOps or Sales Ops leader | Strong | 35 | 90 days | First 90 days | Day 30 to 60 |
  20. 20| Repeat pricing page visits | Medium | 20 | 14 days | Intent check-in | 2 business days |
  21. 21
  22. 22Plus one section per play and a test plan for unproven signals. See `examples/signals.json` for the spec format.
  23. 23
  24. 24## What it can access
  25. 25
  26. 26- Reads `data/` (plus the kit's own `examples/`), writes `out/`. No scripts, no network.
  27. 27
  28. 28## Setup
  29. 29
  30. 30None. Pairs well with tam-builder (who to watch) and sequence-writer (what to send).
Sign in to comment on a line