We love Claude. We teach webinars on it, we give away free Claude sales skills, and most of us still open it every day.

So this isn’t a takedown. It’s what happened when we tried to run a real sales team on it, and the reason we ended up building Arrows the way we did.

The short version: Claude for sales works great for one rep. For a sales team, it broke in four places: someone always had to prompt it, context drifted, every rep ended up with their own version of the skills, and nobody owned the plan for each deal.

Our Claude and HubSpot setup

In January, our two reps (our head of sales and our senior AE) went all in. The rule was simple: work every deal through Claude. No opening HubSpot except to look at the pipeline. If something needed doing, Claude did it.

We pushed hard for it as a company, and then they held themselves to it.

The setup was about as good as it gets for one person:

  • Connected tools: Gmail, Google Calendar, Slack, Grain for call recordings, and HubSpot through the Claude HubSpot connector. (Here’s every sales tool that connects to Claude.)
  • Scheduled tasks in Cowork: a daily brief every weekday morning, deal nudges, and follow-up reminders that landed in Slack.
  • Post-call notes: dictated right after the call, cleaned up by Claude, and saved to the deal in HubSpot.

We wanted an honest answer to one question: how hard is it to run a sales team this way?

The first two weeks were great

Honestly, our Slack channels were a lot of “wait, it just did that?” The daily brief showed up before the first coffee. Follow-up tasks that used to get created by hand in HubSpot just stopped being needed, because Claude already had the context.

If you’ve set up Claude for yourself, you know the feeling. It’s real, and it’s why we still recommend it to every individual rep.

Then it started to break

Somewhere around week two or three, the tone changed. Not because Claude got worse. Because the work stopped being one person playing with a tool and started being a team running a pipeline.

Someone always had to ask

The scheduled tasks helped, but most of the work still started with a prompt. After every call, someone had to open Claude, point it at the right deal, and ask for the follow-up, the CRM update, and the next step. On a busy day, the deals that needed the most attention were the ones nobody had time to prompt for.

The complaint we heard most: “I keep having to prompt this.”

Context drifted

Claude worked from whatever was in front of it in that conversation. Our senior AE caught it pulling details from the wrong places. The pre-call brief kept surfacing a HubSpot field we’d stopped using months ago. Fixing that turned into ten minutes of re-prompting, when looking at the calendar would have taken one.

There were setup questions nobody had a good answer to either. One project per deal? One thread per deal? Everyone landed somewhere slightly different.

Two reps, two versions

This was the big one. Both reps started from the same skills. Within weeks, each had tweaked their own copy to fit how they work. Reasonable, and exactly what you’d want one person to do.

But now we had two versions of our sales process. When we improved a skill, everyone had to go in and manually replace it. Keeping two people in sync was a chore. Our CEO called the idea of doing it for twenty people a nightmare, and he wasn’t exaggerating.

Nobody owned the plan

Claude is great at the task you ask for. What it didn’t have was a plan for the deal: what happens after this call, what’s due next week, which deal is going quiet. As our senior AE put it, there was no sense of what Claude’s plan was.

And because it all lived in individual chats, there was no way to see the work across the team. If a deal fell through the cracks, nothing flagged it. It just quietly didn’t get worked.

What we learned

We kept going for months. We even taught other sales teams how to set it up, because for one rep it really does work.

But the experiment made the line clear. Claude is excellent when a person sits down and asks. A sales team needs the work to happen whether or not anyone asks, the same way for every rep, on every deal, with somebody keeping it current as the process changes.

Those four things aren’t about how smart the model is. They’re about who does the asking and who does the upkeep.

So we built that

That’s the gap Arrows is built for. Claude is built for every kind of work. Arrows is built for one: sales teams working their deals. Here’s what that looks like:

  • Nobody prompts it. After every call, email, and CRM change, Arrows does the work your playbook calls for: the follow-up, the CRM update, the call prep, and the sales room. Reps review it and approve it.
  • One playbook for the whole team. Every rep’s deals get worked the same way, so there’s no drift between copies.
  • Someone keeps it tuned. Your Agent Architect configures the playbook with you and keeps refining it, so nobody on your team ends up maintaining prompts.
  • Every deal has a gameplan. The next steps are written down and dated, so nothing quietly stops getting worked.

We put the full comparison on one page: Arrows vs. Claude for sales teams.

Is Claude good for sales teams?

Can you connect Claude to HubSpot?

Yes. With the HubSpot connector, Claude can search contacts, companies, and deals, log notes, and pull pipeline data when you ask it to. It’s how our reps worked deals without opening HubSpot. Our Claude for sales setup guide walks through it.

Is Claude good for a sales team?

For each rep on their own, yes. The trouble starts at the team level: keeping everyone’s prompts and skills in sync, making sure every deal gets worked even when nobody asks, and maintaining the setup as your process changes.

What’s the difference between Claude and Arrows?

Claude is built for every kind of work and does it when someone asks. Arrows is built for sales teams working their deals, and does the work your playbook calls for on its own. The full comparison is on Arrows vs. Claude for sales teams.

If you’re one rep, keep going

If you sell on your own, a good Claude setup might be all you need. Start with our free sales skills and the Cowork setup that runs your morning for you.

If you run a team and you’re starting to feel the drift, let’s talk. We’ve been exactly where you are.