# The 60% Problem: How Consultancies Can Reclaim Partner Time Without Hiring a Sales Ops Team

> Reps lose 60% of the week to non-selling admin. Six connectors and five skills in Claude's co-work hand that time back without a sales ops hire.

**Type:** Breakdown · **Read time:** 9 min · **For:** Managing Partner, COO · **Published:** 2 Apr 2026

**Video companion:** https://www.youtube.com/watch?v=dWPS58Qe6eo

[All resources](https://aigenticlab.com/resources) · [View as HTML](https://aigenticlab.com/resources/the-60-percent-problem-sales-ops-for-consultancies)

---

### Start here
## Sixty per cent of the week is not spent selling

Salesforce surveyed more than 4,000 sales professionals across 22 countries and found something every Managing Partner should sit with: reps still spend 60% of their week on non-selling tasks. Data entry, prospecting, building quotes, drafting follow-ups.

At a large enterprise, that work lands on a dedicated sales ops team. At most consultancies of 30 to 50 staff, it lands on partners who are already billing 40 hours a week. That is the gap — and the market is making it more expensive by the day.

> The villain is not the partner and it is not the market. It is the assumption that the only way to fix this is to hire.

### Why it bites
## The status quo is getting more expensive

DelTec's benchmark data shows professional services EBITDA fell to 9.8% last year — the lowest in five years. Margins are thinning. A dedicated sales ops hire costs £65,000 to £80,000 in year one, and with only five to ten business development leads in the business, that hire rarely makes financial sense.

So pipeline management becomes a side task. Deals slip because nobody followed up. Proposals go out late because the partner got pulled back into delivery. Win rates stay flat — not because the offer is weak, but because the operational friction is too high.

### The shift
## What changes with Claude's co-work

Claude's co-work environment connects directly to the tools your sales workflow already runs on. Six connectors give it the context it needs to act. Five custom skills tell it what to do.

This is not a CRM replacement. It is an operations layer that sits on top of what you already have and removes the manual work that stops partners from selling.

- **HubSpot (or your CRM of choice).** The non-negotiable. Deal stages, contact history, company data. Every other workflow depends on it — if you install only one connector, make it your CRM.
- **Gmail.** Reads your email threads with any lead, giving co-work conversation context no CRM field captures: the tone of a relationship, what was said informally, where things actually stand.
- **Notion.** Where your team captures meeting notes and call documentation. If you use a different tool, connect wherever your call notes live.
- **Apollo.** Lead database and enrichment across more than 275 million contacts, with company data, job titles, and recent activity. For most consultancies it covers the need without the cost of heavier tools. Clay enriches across hundreds of providers at scale, but it is significantly more expensive and more technical to set up.
- **Apify.** LinkedIn scraping — profile data, post engagement, company pages. The research layer Apollo does not cover.
- **Unipile.** Once leads are qualified, it handles LinkedIn outreach: connection requests, follow-up sequences, response tracking. It also supports WhatsApp and X.

### The five skills
## Connectors give access. Skills give a process.

Anthropic ships a built-in sales plugin with pre-made skills — account research, call prep, call summary, competitive intelligence. A reasonable starting point, but generic, built for any business rather than consultancy sales.

The real value comes from customising those skills to your process, or building your own. The method is simple: do the workflow manually once with co-work, then ask it to save the process as a skill. These are the five that matter most for consultancy business development.

- **Prospect research, qualification, and outreach.** Feed it a LinkedIn post URL or a company list. It scrapes engagements and contacts, enriches through Apollo, then qualifies against your ICP — company size, sector, role, location. The output is a CSV of qualified leads, plus personalised connection requests grounded in that enriched data; Unipile handles the outreach and follow-up. What takes a partner two to three hours takes co-work fifteen minutes. For lists over fifty leads, tell co-work explicitly to use sub-agents — they run in parallel, keep the context window clean, and make the whole process far faster.
- **Automated call prep.** Probably the most immediately useful skill. It checks HubSpot for deal stage, contact history, and company data, reads recent Gmail threads for context, and pulls prior meeting notes from Notion into a consolidated briefing. With scheduled tasks, set it to run at 7 a.m., check your calendar, and prepare a briefing for every meeting that day. You open your laptop and the preparation is done.
- **Follow-up drafting.** How many deals has your firm lost not because someone decided not to follow up, but because the partner got pulled back into delivery? After a call, the skill reads the Notion notes, checks the HubSpot deal stage, reviews the Gmail thread, and drafts a personalised follow-up referencing specific discussion points. You review, edit, and send.
- **Pipeline review and lost lead mining.** Two skills in sequence. The pipeline review pulls active deals from HubSpot and flags stale ones — no activity in fourteen days, or your threshold — cross-referencing email activity to separate genuinely stale deals from live conversations happening outside the CRM. Lost lead mining scans your closed-lost column and re-searches those companies through Apollo for changed circumstances: new funding, leadership change, strategic shift. Leads cold six months ago are often back in a buying cycle, and far easier to reopen because context already exists. Run the review weekly, the mining monthly.
- **Win/loss analysis.** The skill that would normally need a dedicated sales ops person or a quarterly exercise that never happens. It pulls won and lost deals from HubSpot, reads Notion notes, scans Gmail threads, and generates a structured report — common traits in your wins, patterns in your losses, the objections that kill deals, your strongest customer profile. The output is specific enough to be genuinely useful: you win 70% of deals when the COO is in the first meeting but only 20% when it is delegated to a project lead; deals under £30,000 close in two weeks, deals over £50,000 take three months at half the rate. Send it to a Google Doc or Notion page and run it monthly — the patterns only surface over time.

### Straight talk
## Limitations worth knowing

None of this is magic, and pretending otherwise sets a firm up to be disappointed.

- **Scheduled tasks need the desktop app open.** There is no cloud execution. Close the laptop and the task does not run.
- **Sub-agents are essential for bulk work,** but co-work does not always default to parallel processing — you sometimes have to tell it explicitly.
- **Your first skill will not be perfect.** Do the workflow manually once, build the skill, then iterate.
- **Garbage in, garbage out.** If your HubSpot data is a mess, the output will reflect it. Fix CRM hygiene first.
- **Unipile outreach still needs human oversight.** Automate the drafting; review the messages and response rates before you scale.

### The numbers
## A fraction of a single ops hire

A sales ops hire runs £65,000 to £80,000 in year one, all in. A co-work team plan for five business development leads is roughly £100 per month. Add Apollo at the basic tier and HubSpot Starter for the full stack and you are looking at around £620 per user per month.

That is a fraction of one ops hire. It scales without adding headcount, and it hands your existing partners back time currently lost to admin. Most firms at the 30-to-50 mark cannot justify a dedicated hire — this is the practical alternative, and it costs less per year than a single month of that salary.

### Where it sits
## The Workflow layer, made real

These five skills sit at the Workflow layer of the KWA framework — Knowledge, Workflow, Agents. They work because the connectors give co-work access to structured knowledge (your CRM, email threads, call notes) and the skills give it a repeatable process to follow. The Agents layer, where co-work acts more autonomously across longer tasks, comes next — once the workflow layer is stable and the inputs are clean.

The firms that pull ahead here are not the ones with the biggest tech budgets. They are the ones who stopped treating pipeline admin as an unavoidable tax on partner time and started treating it as a workflow that can be documented, standardised, and handed off. The 60% problem is not a hiring problem. It is a design problem — and it is fixable this quarter.