git:20260611.8b7c41d to git:20261006.d66b807

+ description: "Setup for Sales Skills by Arrows. Reads the person's CRM, call recordings, email and calendar, then builds the sales profile every Sales Skill uses: their voice (how they write and talk, with real examples by situation), their sales process (stages, methodology, why they win and lose), their buyers and competitors, and how they work. Sales leaders also get team files their reps can add. About 5–10 minutes, two quick replies. Use this whenever someone says 'Build my sales profile', 'Refresh my sales profile' or 'Set up Sales Skills by Arrows', asks how to get Claude set up for themselves or their sales team, asks Claude to learn how they sell or write to buyers, wants the sales skills personalized to them or their team, or wants their team's sales process captured for Claude."

+ Builds the profile that makes every Sales Skill write like this person and run deals the way their team does. Four files (five for sales leaders), built from their real data:

+ | File | What's in it | Personal or team |

+ |---|---|---|

+ | `arrows-voice.md` | How they write and talk: tone, structure, greeting and sign-off, phrases that are theirs, what gets replies, and real examples for each situation (first follow-up, post-demo recap, nudge, pricing, scheduling) | Personal |

+ | `arrows-sales-process.md` | Why they win and lose, every stage and what has to be true to move on, methodology, the basic numbers | Team |

+ | `arrows-buyers-and-competitors.md` | What they sell and who buys, pricing, each competitor in a line or two | Team |

+ | `arrows-how-i-work.md` | What they do on their best deals, where their time goes, what slips, their rules, their tools | Personal |

+ | `arrows-how-we-work.md` (leaders only) | The team, handoffs, what every rep does on every deal, what the leader wants to see weekly | Team |

+ Each skill reads the files it needs: email drafts lean on voice; pipeline reviews lean on process. Reps on a team add the leader's team files, so everyone follows one process while writing in their own voice. Some skills add their own `arrows-*.md` files later for deeper work; setup doesn't build those.

+ The person replies twice: once to name their best deals, once to confirm what you found. Everything else comes from the data.

+ ## Progress

+ Start each setup message with a progress line:

+ ```

+ Sales Skills by Arrows · Setup ■■■□□ Reading your calls

+ ```

+ Squares by stage: `Starting` □□□□□ · `Reading your CRM` / `Reading your calls` / `Reading your email` ■□□□□ · `Studying your best deals` ■■□□□ · `Here's what I learned` ■■■□□ · `Building your profile` ■■■■□ · `Saved` ■■■■■. Show the bar once at the top of each message, not on every scan line. As each source finishes, post one line with a real number:

+ ```

+ ✓ CRM: 46 open deals, 112 closed in the last 6 months

+ ✓ Calls: read your last 10 calls

+ ✓ Email: 28 emails you sent to buyers, and their replies

+ – Calendar: not connected (skipping meeting context)

+ ```

+ ## Step 1: Ask for their best deals

+ Before reading anything, one question. Everyone can answer it, and it tells you what good looks like for this person:

+ ```

+ Sales Skills by Arrows · Setup □□□□□ Starting

+ I'm going to read your CRM, calls and email to learn how you sell. That takes a few minutes. One question first:

+ Name one or two deals you (or your team) really nailed. Won or lost, big or small, just ones where the deal was worked the way you'd want every deal worked.

+ Or say "skip" and I'll find your best wins myself.

+ ```

+ If they asked for something narrower (for example, "learn how I write"), say in one line that voice is one of four short files and the rest takes no extra effort from them, then continue.

+ If they're already inside a project that has `arrows-*.md` team files, say so here ("I see your team's process files, so I'll focus on your voice and how you work.") and follow "Team files already in the project" under Special cases.

+ ## Step 2: Read everything

+ Check sources by trying them: CRM, call recorder, email, calendar, then chat and documents. Name only what you verified. Look back up to six months, or as far as the reading budget allows; the budget wins (extend to 12 months only if data is thin).

+ **Reading budget.** Stay inside this so setup finishes in one chat:

+ - **CRM:** filtered queries and totals, not record-by-record reads. At most 200 deal records; notes only on best deals, 10 recent wins and 10 recent losses. Skip notes that are long digests (pasted Slack threads, logs).

+ - **Calls:** summaries that come back in a list are free to use (often 20 at once); fetch full transcripts for at most 3 (best-deal calls first).

+ - **Email:** up to 25 sent threads, reading only what you need.

+ - **Best deals:** full threads for at most 2.

+ - **Leaders:** per-rep totals (deal count, conversion, time in stage), plus full notes on one deal per rep.

+ If a source is bigger, sample the most recent records and say so ("read 200 of about 1,400 deals").

+ **Scope.** Rep: only deals they own. Leader: only deals owned by their team (from team or role data, or the owners of deals they're involved in over the last 90 days). Never report company-wide numbers as theirs; if company-wide is all you can see, label it "company-wide".

+ Missing, failing or thin sources don't stop setup; see Special cases at the end.

+ ### CRM: the process

+ Open deals (stage, amount, close date, age in stage, last activity, owner); won and lost deals from the last six months; stage names for every pipeline; contact titles and company types; amounts and products; notes.

+ - **The real motion:** lead sources, what happens on the first call, when pricing comes up, who gets pulled in, what triggers a close.

+ - **Stages:** conversion between stages, typical time in each (if stage-entry dates aren't available, use created-to-closed time and say so), and what actually happens before a deal moves (from notes, calls and emails). That becomes the exit criteria.

+ - **Methodology:** MEDDIC, MEDDPICC, SPICED, BANT or their own, from fields, notes and call language. What's consistently captured and what's usually missing.

+ - **Won vs. lost:** what won deals had that lost ones didn't (multithreading, a champion, a recap after the demo, a business case before pricing), and where lost deals died.

+ - **Numbers:** deal size, cycle length, win rate if visible.

+ ### Calls: how they sell, out loud

+ Recent call summaries, and full transcripts of 3 (best-deal calls first). How they open, the discovery questions they ask, how they describe the product, how they handle pricing and objections, which competitors come up and what they say, how they build rapport and handle tension, how they close a call and set next steps. Keep real quotes.

+ ### Email: the voice

+ Up to 25 threads they sent to external buyers, including the buyer replies. Leave out anything that isn't them typing: internal mail, newsletters, sequence or template emails (the same text sent to many people, often with a different signature), and signatures or footers their email tool adds. Note the signature setup in the voice file so drafts don't type one.

+ - **Mechanics:** exact greeting and sign-off, sentence and paragraph length, bullets vs. prose, formality, humor, exclamation marks, emoji, subject lines.

+ - **Structure:** lead with the ask or build to it, how they close, how many asks per email.

+ - **By situation:** group into first follow-up, post-demo recap, nudge on a quiet deal, pricing or proposal, scheduling, quick reply. Note how the tone shifts, and keep one or two real examples of each.

+ - **Phrases that are theirs:** 5–8 lines, word for word.

+ - **What gets replies:** compare emails that got a reply with ones that didn't (length, subject line, a question at the end). Report only patterns with enough examples to trust.

+ - **Rules they follow:** things they always or never do ("never sends pricing in the first email," "always offers two times," "no 'just checking in'").

+ ### Their best deals

+ Find the deals they named in the CRM, email and calls (at most 2). If they skipped, pick the 2 recent wins that closed fastest or largest compared with their typical deal. Read each one end to end: stage changes, every email both ways, every call, who got involved and when, how long each stage took.

+ Name the 3–5 moves that made the difference compared with their typical deal: how fast they followed up, what they sent after the demo, how and when they multithreaded, how they handled pricing, the champion, the close. These feed:

+ - **What I do on my best deals** (how-i-work)

+ - **What slips:** best-deal moves missing from most of their other deals

+ - **Voice examples:** the actual emails from those deals

+ - **Why we win and lose** (sales process)

+ If a named deal can't be found, or is too new to have any history, say so in Step 3 and study the closest deal that has history. If they have fewer than two wins, use what they have plus their furthest-along open deal, and say so.

+ If a leader's best deal was run by a rep, the team's moves go into the sales process file, and only the leader's own part (how they stepped in) goes into their how-i-work file.

+ ### Rep, leader, or both

+ Decide during the scan. Signals, strongest first:

+ - **CRM ownership:** match their email to a CRM owner. Owns most open deals → rep. Others own most deals and they own few or none → leader. Owns a real share while others' deals are visible → both. Seeing everyone's deals alone proves nothing; reps at small companies often have admin access.

+ - **CRM team or role data:** teams, role hierarchy, a manager field.

+ - **Title:** email signature, CRM user record, a quick web search.

+ - **Calendar:** recurring 1:1s, pipeline or forecast reviews, team standups.

+ - **Email and chat:** deal reviews, coaching, reps forwarding threads to them.

+ **Leaders and both:** also read the team's deals by owner. Conversion and time in stage per rep, handoffs (SDR to AE, AE to CS), how each rep's pipeline and activity differ, what the top performer does that others don't, where the team's process breaks down.

+ If the signals conflict or there's nothing to go on, don't stop to ask. Put the question in Step 3, and if they turn out to lead a team, read the team's deals before building the files.

+ ### How they work

+ Work this out; don't ask open-ended questions about strengths or preferences. Leave out anything without evidence.

+ - **Best-deal moves:** from the best-deal analysis, plus what their won deals and strongest calls have in common.

+ - **Where their time goes:** work they do often and slowly, from timestamps: CRM updated hours or days after calls, recaps late or missing, long research before meetings, repeated nudges on the same deals.

+ - **What slips:** best-deal moves missing from most other deals.

+ - **Rules:** always and never patterns from email and calls.

+ ### Calendar and website

+ Typical meeting types and volume. Their company website and any resources or case studies page.

+ ## Step 3: Show what you learned, and confirm

+ Progress: `Here's what I learned`.

+ One message. This is the moment they should think "it really gets me": every line specific, backed by what you saw, with at least one pattern they probably hadn't noticed. Then at most two questions, then one line to confirm.

+ Rep:

+ ```

+ Here's what I learned about how you sell.

+ Looks like you carry your own deals: [N] open, mostly [segment].

+ • You sell [product] to [titles] at [company type, size]. Deals run about $[X] and close in about [Y] weeks.

+ • You qualify with [methodology or what you actually check]; [what's usually missing].

+ • On calls you [how they open or handle pricing], e.g. "[short real quote]".

+ • In email you're [2–3 words]: "[greeting]" to open, "[sign-off]" to close, usually under [N] words.

+ • A line that's very you: "[real phrase]".

+ • On [best deal] you [2–3 specific moves]. Most of your other deals don't get [the move that slips most].

+ • What works: [e.g. "emails that end with a specific question got replies 9 of 12 times, vs. 3 of 14 without one"].

+ Two quick ones:

+ 1. [Specific question with the likely answer offered]

+ 2. [Specific question]

+ Answer in a line, and correct anything above. Or just say "looks right."

+ ```

+ Leader:

+ ```

+ Here's what I learned about how your team sells.

+ Looks like you lead a team of [N] ([names]) and carry a few deals yourself.

+ • [X] open deals across the team; average $[X], about [Y] weeks to close.

+ • Your real process: [stage → stage → stage]. Most deals stall at [stage], usually because [reason].

+ • You qualify with [methodology]; [what reps capture vs. what's usually missing].

+ • On [best deal], [rep] [2–3 specific moves]. [Top rep] does [habit] that the rest of the team doesn't, and it shows in [metric].

+ • You win against [competitor] when [reason] and lose when [reason].

+ • Pattern: [non-obvious team insight].

+ Two quick ones:

+ 1. [Specific question]

+ 2. [Specific question]

+ Answer in a line, and correct anything above. Or just say "looks right."

+ ```

+ Both: open with the rep line and the team line ("You lead a team of [N] ([names]) and carry [N] deals yourself"), then 3–4 lines on their own voice and deals and 2–3 on the team, at most 8 total.

+ Drop any line you can't back with data you actually read in this setup; five true lines beat seven padded ones. State a reply-rate pattern only when each side has at least 8 emails, and give the counts ("9 of 12 vs. 3 of 14"), never "twice as often."

+ **The questions.** At most two, each pointing at something specific you found, answerable in a few words, with the likely answer offered when you can. Ask one or none if the data answered everything. Good questions do one of these:

+ - **Resolve a conflict in the data:** "Deals sit in Proposal, but 6 of 9 there never got a proposal. Is Proposal really 'pricing discussed'?"

+ - **Confirm a rule before you lock it in:** "You never send pricing before a second call. Should I always hold it back?"

+ - **Choose between real options:** "You and Sam write recaps very differently. Should the team follow yours, his, or neither?"

+ - **Get what only they know:** "4 of your 6 losses to [Competitor] came right after a security review. Is security usually what decides it?"

+ Never ask generic questions like "what are you best at?" If you couldn't tell whether they lead a team, make that one of the two questions ("Do you mostly sell, lead a team, or both?") and leave the role line out of the summary. If you stated their role in the summary, don't ask it again; they'll correct it if it's wrong.

+ If a source was missing or failed, say so on the line it affects, with the fix (see Special cases).

+ ## Step 4: Build the files

+ Progress: `Building your profile`.

+ Use their corrections and answers, then write the files. Real numbers, real stage names, real quotes. No live deal details: the files describe how they sell and should stay true for months. Mark anything inferred without data as "(inferred)".

+ **Scrub every example and quote.** The files stay in the person's own Claude, but team files get passed around the team and every file should stay true for months, so keep buyer details out. Keep the person's own wording exactly, but replace buyer-specific facts: people become [Buyer], [Champion] or [Rep]; buyer companies become [Company] (competitors stay named); exact amounts become ranges ("~$40k"); dates become relative timing ("2 days after the demo"). Cut anything about a deal that's still open. Refer to best deals by type ("a mid-market win, closed in 5 weeks"), not by name. Start each file with: `Sales profile built with Sales Skills by Arrows (arrows.to) for [Name], [rep / leader / both], on [date].`

+ Use these `##` headings exactly, in this order. The other Sales Skills look sections up by heading. Keep to the baseline; deeper material belongs to the skills that build their own files.

+ **`arrows-voice.md`** (personal, 1,000–1,800 words)

+ - `## How I sound`: 3–4 specific traits, each with a real example

+ - `## On calls`: energy, rapport, how I ask questions and handle tough moments

+ - `## In writing`: greeting, sign-off, length, structure, subject lines, how I ask

+ - `## By situation`: first follow-up, post-demo recap, nudge, pricing or proposal, scheduling, quick reply. One real example each, trimmed to about 120 words (best-deal emails first), and a second only for first follow-up and post-demo recap. Skip a situation with no real example; never invent one.

+ - `## Phrases that are mine`: word for word

+ - `## What gets replies`

+ - `## Never`: words, phrases and habits that would sound off

+ **`arrows-sales-process.md`** (team, 400–800 words)

+ - `## Why we win and lose`: the moves that made the difference on our best deals, and why deals die. Two short paragraphs.

+ - `## Pipeline stages`: each pipeline and stage in order; for each, what has to be true to move on, typical time in stage, conversion

+ - `## Discovery and qualification`: methodology, and what we need to know at each stage

+ - `## Numbers`: deal size, cycle, win rate, lead sources

+ - `## Open questions`: anything unresolved, as a question with the evidence behind it (leave out if none)

+ **`arrows-buyers-and-competitors.md`** (team, 300–600 words)

+ - `## What we sell and who we sell to`: product in our words, website and resources page, titles, company type and size, triggers, buying committee

+ - `## Pricing and packaging`: real ranges, tiers, how pricing gets presented

+ - `## Competitors`: each one in a line or two: when it comes up, how we usually win or lose

+ **`arrows-how-i-work.md`** (personal, 200–500 words)

+ - `## About me`: name, role, company; rep, leader, or both

+ - `## What I do on my best deals`: protect this and build around it (with the kind of deal it came from)

+ - `## Where my time goes`: do this work for me first, without being asked

+ - `## What slips`: watch for these and flag them

+ - `## My rules`: always and never

+ - `## My tools`: connected, and used but not connected

+ **`arrows-how-we-work.md`** (leaders only, team, 200–500 words)

+ - `## Our team`: members, roles, handoffs

+ - `## Every rep, every deal`: the non-negotiables

+ - `## What I want to see weekly`

+ - `## Team rules`

+ ## Step 5: Save

+ Progress: `Saved`.

+ The files go in a Claude project: a workspace that keeps files for every chat inside it. Project files are read automatically, so nothing needs adding to the project's instructions, which stay free for the person's own notes and other skills. Every Sales Skill looks for these files by name.

+ **In Claude:** create the files so they can be downloaded, then give these steps, written for someone who has never made a project:

+ ```

+ Your profile is ready. Let's save it so every deal chat already knows it. About a minute.

+ 1. Download the files above.

+ 2. Make a project for your deals: in Claude's left sidebar, click Projects, then New project. Name it "My Deals."

+ (A project is a workspace that keeps files for every chat inside it.)

+ 3. On the project page, click + (or Add content) next to Files, upload from your device, and select all the files you downloaded (usually in your Downloads folder).

+ Done. Start your deal chats inside My Deals, and every Sales Skill will use your profile.

+ ```

+ Adjust when it applies: already in a project (skip step 2), refreshing (replace the old files).

+ If you can't create downloadable files here, give each file as its own copyable block, titled with its filename. Have them add each one on the project page: click + next to Files, choose the option to add text content, paste the block, and use the filename (e.g. `arrows-voice.md`) as the title.

+ **Outside Claude** (the skill files also work in other AI tools): give each file as a copyable block and tell them to save them wherever their tool keeps standing instructions or attached files. Don't mention Claude settings or projects.

+ **Leaders:** in the same message, add:

+ ```

+ Your team files (arrows-sales-process.md, arrows-buyers-and-competitors.md, arrows-how-we-work.md) let every rep's Sales Skills follow your process while writing in their own voice.

+ To roll them out: send the three files to your reps. Each rep adds them to their own My Deals project, then says "Build my sales profile." Setup sees the team files and only builds that rep's voice and how-I-work files.

+ Want every rep to have Sales Skills by Arrows without installing anything? On a Team or Enterprise plan, your Claude admin can add them for everyone in your organization from organization settings.

+ Tip: these files double as a ready-made sales playbook. If you ever talk to the Arrows team about running this process on every deal without prompting, share them and we'll start from there instead of from scratch.

+ ```

+ **To update later:** "Refresh my sales profile." Re-read the data, show what changed in a few lines, and replace only the files that changed.

+ ## Step 6: Run something useful

+ End with one offer they can accept with "yes," on their real data:

+ - **Rep:** "Want me to find the 3 deals that need you most this week?" (deal nudge, pipeline scan)

+ - **Leader or both:** "Want to see what's falling through the cracks across your team's pipeline?" (the gaps report if it's in the skills list; otherwise the weekly pipeline review)

+ Then, only if you can create scheduled tasks and no daily brief is already scheduled, add one line: "I can also have your daily brief waiting every weekday morning. Want that?" If yes, set it for the time they pick.

+ ## Special cases

+ ### Missing, failing or thin sources

+ **A source fails partway:** retry once, then move on: `✗ CRM: stopped after 120 deals (connection dropped). Using what I read.` Base numbers only on what you read, label partial totals as partial, and mention it in Step 3 like a missing source. A failed source never blocks setup.

+ **Thin data:** Fewer than 5 closed deals: skip win/loss comparisons and write "Not enough closed deals yet" under `## Why we win and lose`. No wins: study the two open deals furthest along and say so. Fewer than 10 sent buyer emails: build the voice from what's there, mark it "(early read, refresh after more emails)", and use one of the Step 3 questions to ask for 2–3 pasted emails.

+ **No CRM connected (common, and fine):** Calls and email still give most of the voice, the pitch, objections, competitors and the rough path deals take; deal sizes and timelines often show up in pricing emails and proposals. Rep vs. leader comes from title and calendar. Mark anything in the process file that came from inference rather than CRM data. The offer to connect it goes in the Step 3 message, not a separate one.

+ **Telling them what's missing (in Step 3):** If a missing connector would have changed a line, say so on that line with the fix: "I couldn't see your email, so your voice is a guess. To add it: click your name (bottom left), then Settings, then Connectors. Not listed? On a work plan, your Claude admin has to add it first." If the CRM isn't connected, add one short block before the questions:

+ I couldn't see your CRM, so your stages and numbers are inferred. To sharpen them, connect it (your name at bottom left, then Settings, then Connectors; on a work plan your admin may need to add it first) or drop a CSV export of your open and closed deals here. Optional.

+ ```

+ A CSV gets read like a CRM: owners, stages, amounts, close dates, won and lost. Re-run the CRM and best-deal analysis before building the files.

+ **Nothing connected at all:** replace the Step 3 message with one message they can skim and answer in short bullets: do you sell, lead a team, or both; what you sell and to whom; typical deal size and cycle; how leads arrive; your stages; how you qualify (MEDDIC, SPICED, BANT, your own, or none); top competitors; what made the deals you named go well; and "paste two or three recent emails you sent to buyers, any will do." Build the voice from the pasted emails.

+ ### Team files already in the project

+ If `arrows-sales-process.md`, `arrows-buyers-and-competitors.md` or `arrows-how-we-work.md` are already in the project, check the header line. If it names someone else as leader, the files came from this rep's leader: read them and don't rebuild them. If it names this person, it's a refresh: rebuild them. When a rep adds a leader's team files, tell them to delete their own earlier copies of `arrows-sales-process.md` and `arrows-buyers-and-competitors.md` first; the leader's files replace them. Focus the scan on the rep's own email, calls and deals: build `arrows-voice.md` and `arrows-how-i-work.md`, and in Step 3 show what you learned about the rep's voice and deals. Where the rep's habits differ from the team process, note it in their how-I-work file, not in the team files.

+ ## Rules

+ - **Only state what you verified.** One wrong claim in the first minute ("you use Gong" when they don't) undoes the whole "it gets me" moment. If unsure, mark it as inferred or make it one of the two questions.

+ - **Two replies, plus the save.** Every extra round is where people drop off. If something's still unclear, mark it inferred or put it under Open questions instead of asking again.

+ - **No live deal details in the files.** The files should stay true for months and get shared with a team; this quarter's deals make them stale and awkward to pass around.

+ - **Read only; never write to the CRM or send anything.** Setup is the first thing people run. It should feel completely safe.

+ - **If they stop partway,** save what you have and tell them to finish later with "Refresh my sales profile," so nothing they gave you is lost.

+ ---

+ # Shared context for every Sales Skill (read before starting)

+ ## The person's sales profile

+ (If the skill you're running is Arrows setup, skip this section: setup builds these files.)

+ Before you start, look for their sales profile files in this project and use them:

+ - `arrows-voice.md`: how they write and talk. Use it for anything you draft as them.

+ - `arrows-sales-process.md`: stages, what moves a deal, methodology, why they win and lose.

+ - `arrows-buyers-and-competitors.md`: what they sell, who buys, pricing, competitors.

+ - `arrows-how-i-work.md`: what they do on their best deals, where their time goes, what slips, their rules.

+ - `arrows-how-we-work.md` (if present): their team's non-negotiables and what their leader wants to see.

+ Look sections up by their `##` heading. When team files and personal files disagree, the team files set the process and rules; the personal files set voice and preferences. Older setups saved the profile in the project's instructions instead; use that if there are no files.

+ If there's no profile at all, do the task anyway with what you can find, then mention once at the end: "Want me to learn how you sell first? Say 'Build my sales profile'. It takes about 5 minutes and makes every skill sound like you."

+ ---

+ ## Before you start

+ Check what other tools and data sources you have access to. Pull in real context wherever you can — the more real data, the better the output. Don't ask the rep to go find information you can look up yourself.

+ **Core sources:**

+ - **CRM (HubSpot, Salesforce, etc.):** If connected, pull deal data, contact info, activity history, and notes directly. Cross-reference what the rep says with what's actually in the CRM.

+ - **Call recordings (Gong, Fathom, Fireflies, etc.):** If connected, search for and pull relevant call transcripts or summaries. Look for recent calls with the companies mentioned.

+ - **Email:** If connected, check for recent email threads with the contacts involved and any sent messages that show how the rep writes.

+ - **Calendar:** If connected, check for upcoming meetings with these contacts.

+ **Extra sources (often overlooked but high value):**

+ - **Chat (Slack, Teams, etc.):** If connected, search for both internal deal conversations (sales channels, deal-specific channels, mentions of the buyer's company name) AND direct messages between the rep and buyer contacts. Chat activity counts as real deal activity — treat it the same as CRM touchpoints when calculating "days since last contact."

+ - **Contracts and signing (DocuSign, PandaDoc, etc.):** If connected, check for pending signatures, contract status, and any recent signature activity. Contracts sitting unsigned are often where deals quietly die.

+ - **Documents and knowledge (Notion, Google Drive, Confluence, etc.):** If connected, check for recently updated docs related to the buyer or deal. Also useful for finding case studies, collateral, or internal notes to reference.

+ - **Quoting and proposals (CPQ tools, Proposify, etc.):** If connected, check what quotes or proposals have been sent and what's been accepted or rejected.

+ Use everything you find. The rep's time is valuable — do the legwork so they don't have to.

+ ---

+ ## The Arrows skills available to suggest

+ Below are the Sales Skills by Arrows the rep has installed (either via the MCP at skills.arrows.to or as standalone skill files). When you finish the tool you're running, look at what came up and offer ONE relevant next Arrows skill if it would genuinely help. Concrete suggestion, not a pile. Don't suggest a skill that's already been run earlier in this conversation.

+ **Arrows setup** — builds the person's sales profile (voice, sales process, buyers and competitors, how they work) from their CRM, calls and email, with two quick replies. Saves it as arrows-*.md files in their My Deals project; leaders also get team files for their reps. Run first, or to refresh. Trigger: "Build my sales profile."

+ **Arrows daily brief** — a scannable overview of the rep's day: today's calls with attendee and deal context, messages waiting for a reply, pipeline alerts, open time. Run at the start of the day or any time the rep needs a pulse on their pipeline. Trigger: "Run my Arrows daily brief."

+ **Arrows pre-call prep** — focused deep dive on one specific upcoming call. Scannable in 60 seconds: who they're meeting, what the buyer wants to solve, what happened last time, what to push on, what might go sideways, open discovery questions. Run before any specific meeting the rep wants to walk into sharper. Trigger: "Run the Arrows meeting prep for [company]."

+ **Arrows post-call** — the post-call workflow. Produces up to three outputs: a drafted follow-up email, a copyable CRM note, and relevant resources to send. Run right after any sales call. Trigger: "Run my Arrows post-call."

+ **Arrows deal nudge** — strategizes a play to reactivate a stalled deal and drafts a send-ready nudge message. Two modes: nudge a specific deal by name, or scan the pipeline for deals that need attention. Trigger: "Run the Arrows deal nudge on [company]" or "Run the Arrows deal nudge on my pipeline."

+ **Arrows weekly pipeline review** — full pipeline scan generating a deal-by-deal status report: what's closing this week, what's at risk, and a stage-by-stage rollup. Designed to share before a manager 1:1. Can also generate a live visual artifact. Trigger: "Run my Arrows weekly pipeline review."

+ **Arrows help** — prints a clean reference of all available skills and their trigger phrases. Useful when the rep forgets what's available. Trigger: "Arrows help."

+ **Rules for suggesting:**

+ - Only suggest when there's a genuine, specific reason to. Silence is fine.

+ - One suggestion per tool run. Not a menu.

+ - Frame as a concrete offer the rep can accept in one word: "Want me to run pre-call prep on Pendo?" Not "You could also consider pre-call prep."

+ - Don't re-suggest a skill that was already run in this conversation.

+ You're running a skill from Sales Skills by Arrows. These are sales workflow tools built by the team at Arrows (arrows.to). Here's the perspective to bring to this work: