1---2name: buying-moments3description: >-4 Turns won and lost deals, buyer interviews, sales notes and support tickets into the ideal customer, the buying5 group and the moments that start a search for the category, each traced to its sources, worded in the buyer's own6 phrasing and scored for priority. Writes the profile's Buyers and Buying moments sections, which seed ad themes,7 keyword selection and AI answer prompt panels. Returns READY, DRAFT, NEEDS DECISION or BLOCKED after its own8 check. Use it after positioning and before messaging, ads or search work, or when new interviews come in. Not for9 deciding the category or what makes the company different (use positioning) or for writing copy (use10 messaging-house).11license: MIT12compatibility: >-13 Works in Claude, ChatGPT, Codex, Cursor and any agent that reads SKILL.md. Uses a connected CRM, call recorder or14 help desk if the agent has one, otherwise exports, transcripts or pasted notes. Python 3 is optional, for scoring.15metadata:16 author: SHAKEUP17 version: "1.0.0"18 stage: make19 plugin: strategy-messaging20 homepage: https://www.shakeuphq.com/skills/buying-moments21---22 23# Buying moments24 25Finds who buys, who else has to agree, and the events that make them start looking, so ads, pages and prompt panels start where buyers start.26 27## Purpose28 29- One job: write `## Buyers` (ideal customer, bad fit, buying group) and `## Buying moments` in `company-profile.md` from buyer evidence.30- Stage: make. It ends with its own check, at most 2 rounds.31- A buying moment is an event that starts a search for the category, told from the buyer's side ("an audit date is set"), never a feature or a pain adjective.32- It never invents a buyer, a quote, a search phrase or a search volume. A phrase no buyer said is marked `inferred`.33 34## Use when / not35 36| Situation | Use |37| --- | --- |38| The profile has no buyers or buying moments, or they were written from opinion | this skill |39| New win and loss interviews, or a new segment is winning | this skill, to update |40| Before `ad-themes`, `keyword-selection` or `ai-answer-panel` on a new company | this skill first |41| You need the category and what makes the company different | `positioning` (run it first; this skill reads its best fit) |42| You need the words for a page or an ad | `messaging-house`, then the copy skills |43 44## Inputs45 46| Input | Required | Ways to provide, in order | If missing |47| --- | --- | --- | --- |48| Won and lost deals with why-now notes, contact roles and the role that signed | yes, or interviews | a connected CRM (closed deals, contact roles, first-call notes); a CRM export; a pasted table | ask once; without deals or interviews, `BLOCKED` |49| Switch interviews with recent buyers (and buyers who chose something else) | no, but primary | uploaded transcripts; a connected call recorder; pasted notes | moments come from deal notes only; coverage `partial`; offer the guide in `references/switch-interview.md` |50| Sales call notes and recordings | no | a connected call recorder; exports; pasted notes | fewer role objections; coverage `partial` |51| Support tickets, onboarding notes, reviews | no | a connected help desk; an export; pasted text | skip; only lines about why they bought count anyway |52| Search phrasing (Search Console queries, ad search terms) | no | a connected Search Console or ad account; an export; pasted rows | phrases stay as buyers said them or `inferred` |53 54## Profile read55 56From `company-profile.md`: `## Company` (category, business model, ACV, sales cycle, regions), `## Product`, `## Buyers` (the current version), `## Positioning` (best-fit customers, competitive alternatives, unique attributes), `## Competitors`, `## Accounts and data`, and every `## Learnings` entry for `buying-moments` with status `noted`, `fact` or `accepted`.57 58No profile: ask in one message for what the product does, the deal list or interview notes, and who usually signs. Say that `company-profile` saves this next time.59 60## Steps61 621. **Apply learnings.** Accepted learnings for this skill override the defaults below. Name each one that fires.63 642. **Label the evidence.** Give every item an id (`D1` deals, `I1` interviews, `C1` calls, `T1` tickets, `R1` reviews, `Q1` search rows). Sort each by what it can show:65 66 | Source | What it can show | Counts as |67 | --- | --- | --- |68 | Switch interview, decision in the last 12 months | The whole timeline, the 4 forces, the buyer's words | primary (memory of the first thought fades after a year) |69 | Won deal with why-now notes | The trigger, the roles, the signer | primary |70 | Lost or no-decision deal notes | What held them back, the role that blocked | primary for worries and habits |71 | Sales call transcript | Words, roles, objections | primary |72 | Ticket, onboarding note, review | Mostly use after purchase; only "why we bought" lines count | supporting |73 | Search rows | How buyers phrase a need | phrasing only, never a moment on its own |74 75 Drop how-to and bug tickets from moment work: they describe using the product, not starting a search.76 773. **Write the ideal customer and bad fit.**78 - If `## Positioning` has best-fit customers, start there and confirm it against this evidence. Don't re-decide it.79 - Otherwise, put a trait in the ideal customer when at least half of won deals share it (a majority describes the typical win, not an edge case), and add the situation they were in.80 - Bad fit: traits that show up in 3 or more lost, no-decision or churned deals and in fewer than a quarter of won deals.81 - If the evidence says the ideal customer differs from the profile's confirmed one or from `## Positioning`, stop at `NEEDS DECISION`.82 834. **Map the buying group.** List every role that appears in the deals: who found the product, who ran the evaluation, who signed, who blocked, who uses it.84 - Keep a role that appears in 3 or more deals. 1 or 2 appearances is that account's org chart, not the pattern.85 - For each role write: what they care about, their objection, and their part (`champion`, `decision maker`, `influencer`, `blocker`, `user`), each from the evidence with ids. An objection nobody voiced is `not available`, not a guess.86 - The decision maker is whoever signed or owned the budget in the deals, not the most senior title.87 885. **Rebuild each buyer's timeline.** For every interview and every won deal with enough notes, write the sequence in the buyer's words with dates where given: the first thought (what made the old way stop being good enough), passive looking, the event that turned it into active looking, active looking (what they searched, asked or who they asked), deciding (what almost stopped them), the purchase. Record the 4 forces in each:89 90 | Force | Question it answers |91 | --- | --- |92 | Push | What was going wrong with the current way? |93 | Pull | What did they hope the new way would give them? |94 | Worry | What did they fear could go wrong with something new? |95 | Habit | What kept them with the current way, even while it hurt? |96 97 Interview guide and how to recruit: `references/switch-interview.md`.98 996. **Group timelines into moments.** A moment is the event that turned passive looking into active looking, plus the situation it happens in. Describe each with 5 questions: who it happens to (the role), what they need done, when (the event or deadline), where (the meeting, team or tool where it surfaces), why now (the push).100 - Merge timelines with the same event, even when worded differently.101 - Split them when the role or the job differs: "an audit date is set" for a finance manager (clean receipts) and for an IT lead (access logs) are 2 moments, because the job differs.102 - Name the moment as the event, in the buyer's terms. Rewrite any name that is a feature ("needs multi-touch") or an adjective ("frustrated with data").103 1047. **Capture how they looked.** For each moment, quote what buyers typed into search, asked an AI assistant, or asked a peer or community, with the source id. When no buyer said it, write 1 or 2 candidate phrases marked `inferred` and send them to `keyword-selection` or `ai-answer-panel` to confirm. Never attach a search volume here.105 1068. **Score and prioritise.** Count the sources per moment, then run:107 108 ```109 python3 scripts/moment_score.py --json moments.json110 ```111 112 Without Python, apply the same rules by hand and say so:113 114 | Factor | Rule | Why |115 | --- | --- | --- |116 | Park | Credibility `none` (the product can't serve this moment yet) | A moment we can't win wastes the campaign that targets it |117 | Watch | Fewer than 2 sources | 1 source is an anecdote |118 | Commonness | Share of buyer stories (won, lost, interviews): 25% or more +3; 10% to 24% +2; under 10% +1 | 1 in 4 stories is common enough to carry its own campaign; 1 in 10 is a real supporting angle |119 | Win rate | With 5 or more decided deals where it appears: at or above overall +1; below overall by more than one deal's swing (100 / deals) -1 | Moments where we win deserve the budget first |120 | Deal size | Median ACV of its won deals at or above the overall median +1 | Bigger deals pay for more reach |121 | Competition | Low +1, medium 0, high -1, unknown 0 | A moment 2 or more competitors already own costs more to win |122 | Credibility | Full (a unique attribute or claim with proof covers it) +1; partial 0 | We can prove we solve it |123 | Priority | High 5 or more; medium 3 to 4; low 2 or less | |124 125 Competition comes from `ai-answer-panel` results, ad libraries or competitor pages when available: `high` when 2 or more competitors lead with the moment, `low` when none do. Without that data, write `unknown`.126 1279. **Write the sections.** Replace `## Buyers` and `## Buying moments` using the template's exact line formats:128 129 ```130 Ideal customer: <company type, size, industry, trigger>131 Bad fit: <who, and why, with deal ids>132 133 ### Buying group134 135 - <Role>: <what they care about> | <their objection> | <champion, decision maker, influencer or blocker>136 137 ## Buying moments138 139 - <Moment>: <what happens> | <what the buyer searches or asks> | <priority: high, medium, low>140 ```141 142 Parked and watch moments stay in the output, not in the profile. If the agent can't edit the profile file (a chat app, or a profile pasted into the chat), give both sections in one code block ready to paste and set `profile_sections_written: [] (ready to paste)`.143 144## Check and verdict145 146| Verdict | Condition (first match wins) |147| --- | --- |148| `BLOCKED` | No buyer evidence of any kind: no deals, interviews, call notes, tickets or reviews |149| `NEEDS DECISION` | The ideal customer the evidence shows conflicts with `## Positioning` best fit or the profile's confirmed ideal customer |150| `DRAFT` | Fewer than 3 primary sources; or a high-priority moment rests on a single source type; or a loop check still fails after 2 rounds |151| `READY` | Every loop check passes |152 153Named stops:154 155- `BLOCKED`: stop. Don't write the profile. Give the interview plan from `references/switch-interview.md` and the CRM report to pull. If the reader asks for a brainstorm anyway, label every line `hypothesis` and keep it out of the profile.156- `NEEDS DECISION`: stop. Show both ideal customers with the deal ids behind each. Write nothing until the reader picks, or reruns `positioning`.157- Overwriting a `## Buyers` the reader marked confirmed: show the old and new side by side and write after the reader says yes.158 159`DRAFT` writes the sections with every unproven line marked `hypothesis`. `READY` writes without a stop.160 161## Loop162 163Check the draft, fix what fails, check again. At most 2 rounds, then hand over with what is still open, labelled.164 165| Check | Fails when | Fix |166| --- | --- | --- |167| Sources | A moment in the profile has fewer than 2 sources | Move it to watch |168| Buyer words | A search phrase or objection has no source id and isn't marked `inferred` | Add the id, or mark it |169| No invented numbers | Any count, rate or volume isn't from the evidence | Remove it or write `not available` |170| Events, not features | A moment name is a feature, a product term or an adjective | Rename it as the event |171| Before the purchase | A moment comes only from after-purchase tickets | Drop it from moments |172| Roles | A buying group role lacks an objection or a part | Fill from evidence, or `not available` |173| Format | A line doesn't match the template format | Rewrite it to the format |174 175## Learn176 177Append to `## Learnings`:178 179- the reader changes a moment's priority or merges 2 moments: a `proposal` with their reason;180- results come back for a moment, such as the keywords `keyword-selection` confirmed, the prompts `ai-answer-panel` ran, or ad results by theme from `ad-themes`: a `fact` with the source;181- new interviews change a moment's count: a `fact` with the new count and ids.182 183Example: `- 2026-10-24 | buying-moments | fact | "A new CFO wants a faster month-end" seen in 2 more interviews, now 6 of 20 stories | Why: switch interviews I7, I8 (2026-10) | Status: noted`184 185## Output186 187```188Verdict: <READY | DRAFT | NEEDS DECISION | BLOCKED> · Coverage: <complete | partial (what's missing) | blocked> · Scoring: <script | by hand>189Evidence: <n> won, <n> lost, <n> interviews, <n> call notes, <n> supporting (<n> dropped as after-purchase)190 191Ideal customer: <line> (from <ids>)192Bad fit: <line> (from <ids>)193 194Buying group195| Role | Cares about | Objection | Part | Deals |196 197Moments198| Moment | Who | What happens | Searched or asked (source or inferred) | Sources | Points | Priority |199Watch: <moments with 1 source>200Parked: <moments the product can't serve yet>201 202Forces seen most often: push <..>, pull <..>, worry <..>, habit <..>203 204## Buyers and ## Buying moments (the sections as written, or "not written: <stop>")205 206Loop: round <1 or 2>, <checks passed>/<7>; open: <list>207Learnings applied: <list, or none>208```209 210Then the handoff block.211 212## Hand off213 214```handoff215skill: buying-moments216version: 1.0.0217verdict: READY218coverage: partial (no search data; 2 phrases inferred)219for: <company>220outputs:221 top_moments: ["An audit date is set", "A new CFO wants a faster month-end"]222 phrases: ["receipt matching software", "expense policy software (inferred)"]223 decision_maker: Controller224 blocker: IT reviewer225 profile_sections_written: [Buyers, Buying moments]226next: [messaging-house, keyword-selection, ad-themes, ai-answer-panel]227open: [confirm 2 inferred phrases with keyword-selection]228```229 230Made-up values for illustration. `messaging-house` reads the buying group and moments for pillar order; `keyword-selection` reads `phrases`; `ad-themes` reads `top_moments`; `ai-answer-panel` turns each high and medium moment into prompts.231 232## Failure modes233 234| Problem | Do this |235| --- | --- |236| Only the founder's or sales lead's opinion is available | Record it as `hypothesis`, verdict `DRAFT` at best; plan 5 switch interviews first |237| Interviews only with happy customers | Add buyers who chose something else or nothing; without them, worries and habits are blind; say so |238| The CRM has no contact roles | Use first-call notes and signers; mark the buying group coverage `partial` |239| Every moment looks the same ("needs better data") | The event is missing. Ask what happened the week they started looking |240| The reader wants search volumes per moment | Not this skill's job. Hand the phrases to `keyword-selection` |241| A moment only exists in one region or segment | Keep it, with the segment named in "who" |242 243## Influenced by244 245- Jenni Romaniuk's category entry points, as set out for B2B by LinkedIn's B2B Institute: the buying situations a brand should be linked to, described by who, what, when, where and why, and prioritised by how common, how contested and how credible they are: https://business.linkedin.com/advertise/resources/b2b-institute/cep-in-b2b246- Bob Moesta's switch interviews, which rebuild the timeline from the first thought to the purchase and the forces that pushed and held the buyer: https://businessofsoftware.org/talks/understanding-your-customer-jtbd/247- What we changed: the buying situations come from deal and interview evidence with ids, the 3 prioritising questions became a scored rule with thresholds, the switch timeline is the unit of evidence, every search phrase is quoted or marked inferred, and the result is written into the company profile for ad, keyword and AI answer skills to read.