Claude becomes much more useful when it understands how you sell, where deal information lives, and what a good output looks like. This setup gives it those ingredients without turning configuration into a project.
Before you start
Have one recent call transcript, your qualification framework, and access to the tools where you keep email, calendar, notes, and CRM context.
1. Start with context, not prompts
A clever prompt cannot make up for missing facts. Claude should know your company, your buyer, your sales process, and the standard you expect before you ask it to draft follow-up or prepare a call.
Give it four layers of context
- Your company, product, positioning, and proof
- Your ideal customer and the problems they are trying to solve
- Your sales stages, qualification questions, and exit criteria
- Your voice, preferred formats, and examples of strong work
2. Connect the tools where deal context lives
Connect the smallest useful set first. Email and calendar reveal who is involved and what has happened. Call notes capture the buyer’s words. CRM data shows stage, ownership, and the team’s shared record.
- Connect email and calendar.
- Add your call transcript or note source.
- Point Claude to the account and opportunity records you actually use.
- Test one real deal before expanding access.
3. Build a reusable sales profile
Create one project or instruction set that defines how Claude should work with you. Keep facts separate from preferences so the profile stays easy to update.
| Include | Example | Why it matters |
|---|---|---|
| Buyer | Sales leaders at HubSpot teams | Keeps advice specific |
| Method | Stages and exit criteria | Anchors the work |
| Voice | Direct, useful, human | Makes drafts usable |
4. Turn repeatable moments into daily workflows
Start with moments that happen every day and have a clear input and output. A useful first set is morning deal review, call preparation, follow-up drafting, and end-of-day CRM cleanup.
- Morning: identify deals without a clear next step.
- Before a call: summarize context, open questions, and likely risks.
- After a call: draft the follow-up and propose record updates.
- End of day: flag commitments that still need an owner or date.
A useful test
If the output still needs a blank page and ten minutes of reconstruction, add context. If it only needs judgment and approval, the workflow is working.
5. Know when an individual setup reaches its limit
Claude is a strong starting point for an individual rep. Arrows is what happens when the team needs one playbook running across every active deal — with the gameplan current and the next work ready before anyone asks.
The shift is from asking Claude for help to operating a consistent sales system: connected to the context around every deal, aware of what should happen next, and ready to show its work for the rep to approve.
Put one gameplan to work across every deal.
See how Arrows turns your sales process into deal work your reps can review and run.
