What's in a pack.
Pain taxonomy, scoring rules, angle library, tone profile. Bundled per vertical.
A pack is the personality the pipeline takes on for a specific market. Same eleven stages, different priors. The Devtools & Infra pack will not flag the same signals as the Clinical Ops pack, will not score companies the same way, and will not write in the same voice.
Four files
Every pack is four YAML files in a directory. You can read them. You can fork them. You can ship a fork to your team without our involvement.
| File | Holds | Touches |
|---|---|---|
signals.yml | The pain taxonomy. 28-47 entries per pack. Each entry has a name, definition, severity rule, and example excerpts. | extract_signals() |
icp.yml | Scoring rules across the five ICP components. Weights and thresholds. | qualify() |
angles.yml | The angle library. Each angle has a hypothesis, the signals it requires, a tone profile, and a current reply-rate window. | draft_brief(), draft_email() |
tone.yml | Voice rules: banned phrases, sentence-length variance targets, salutation defaults, sign-off defaults. | draft_email() |
Live packs
Six are in production: Devtools & Infra, Fintech / B2B SaaS, Clinical Ops, Exec Recruiting, Logistics & 3PL, Performance Marketing. Two are in beta: Legal Ops and Founder-led GTM. The pack reference lists every signal in every pack.
When to fork or build
Fork a pack when the angle is right but the wording is wrong. Build a custom pack when the entire pain taxonomy is wrong, which usually means you are in a niche we have not shipped. Building a custom pack walks through the process. Forking covers the lighter case.