NewOur sales playbook: 400+ pages, free to downloadDownload
Compare

Build your sales coach with Claude, or use a system that already works?

Claude is an excellent model. A sales coach is a system around it: your playbook, your data, skills per rep, a daily workflow, tracking and a reason for every rep to open it every day.

Build or buy

A model is not a system

You can build a lot with Claude. The hard part is everything around the model: getting your playbook ready, connecting your data, deriving the skills your reps need, delivering coaching every day and tracking whether it works. That system is the work. Taskbase is that system, with your playbook ready in hours instead of months.

One use case is easy. All of them is the work

A tool that cannot do everything is a tool reps drop. The more use cases you need, the harder it is to build them yourself.

You can try, and some teams get far

Most organisations that use Claude get feedback after a call, but nothing systematic, and nobody tracks it.

Adoption decides whether it pays off

A coach only works if every rep uses it every day. Build for that from the start: the same answers for everyone, one place to work, and a way to see whether it is used.

The heartbeat

Reps use a fraction of what AI can do. Taskbase goes to them first.

Most reps do not know how much AI can do for them. They open it when they think of it, and in our experience that is 5 to 10% of what is possible. A few reach 20 or 30%. Asking is not enough. Taskbase has a heartbeat in the background: it sees what each rep does every day, which deck they build for which client, when they write a business case, open a deal room or send a follow-up. From that it knows what it could take off their plate, and it asks first.

5–10%

of what AI can do is what most reps use, in our experience. The rest is work they never thought to hand over.

Slack· Taskbase

Taskbase08:15

Your demo with Northwind Freight is in 2 days.

  • Missing There is no slide deck for it yet.
  • Ready I have the account history, the last two calls and your playbook.

Noticed from your weekYou built a deck for every demo in the last six weeks.

Should I prepare the deck for you?

Yes, prepare itNot nowNot like this

Taskbase writes first, in the chat the rep already uses. The rep only has to say yes. Fictional names.

It learns the rhythm of every rep

Which decks, business cases, deal rooms and emails come up, for which client and when. That is the data behind the heartbeat.

It offers before the rep thinks of it

A demo in two days and no deck yet? Taskbase has the account history and your playbook, and asks whether to start. The rep answers yes.

It improves from every answer

A rep who says “not like this” teaches Taskbase, for that rep and within your standards. With a text skill, you can edit the skill, but the change is not consistent, and nobody tells you which reps rejected the result.

Skills versus apps

Why a text skill is not enough

  1. 01

    The model re-reads the instruction on every run

    A skill is a text the model has to read and work out again each time: what to search, what to read, how to present it. The more text, the more room for mistakes, and no run is exactly like the last. It is also slower, and it can use more tokens than needed.

  2. 02

    You cannot push it

    A skill sits in Claude until someone asks for it. You have to tell your reps it exists, and reps rarely ask. Nothing reaches them on its own, and that is the biggest hurdle.

  3. 03

    You cannot see what happens

    Whether a rep read the briefing, liked it or answered “that is not what I want” stays invisible. You find out afterwards, if at all, and the skill does not change by itself.

  4. 04

    You cannot fit it to each rep

    Some reps want a meeting briefing short, others want every detail. A skill is one text for everyone, so you push the same stand-up to all of them and cannot improve it from their feedback.

  5. 05

    A Taskbase app is code, not a prompt

    Our first version used skills and had exactly these problems. Now each use case is an app: coded functions, connected sources and a finished view. What must always happen the same way is fixed in code, and the model is used where judgement on this account or this call is needed. Text skills can call code too. The difference is that a Taskbase app is built and reviewed as code by default.

  6. 06

    Built in chat, reviewed by Taskbase

    A rep or leader describes a new app in plain language. Before anyone uses it, Taskbase reviews the code: does it do the job, how good is the result, how efficiently does it run and how well does it fit the use case. It adapts the app as the use case changes.

Skill or app

What a text skill looks like, and what a Taskbase app looks like

A skill is text: the model reads it and decides again on every run. An app is code: the sources, the steps and the finished view are fixed, and the model is used where judgement is needed. That is why the same request gives the same result every time, and why the app can be shared with every rep as it is.

A text skill

Skills / Meeting briefing

Catalogue

Description

Before every customer meeting, give the rep a briefing. Look up the company, read the last calls and the CRM record, and decide what matters. Keep it short unless the rep asks for more.

Purpose

Give the rep a personal read, not a summary of everything. It answers three questions in plain language:

  1. Who is in the meeting, and what do they care about?
  2. What was agreed last time, and what is still open?
  3. What is the one thing to get out of this meeting?

Rules

  • Subject is always the calling user.
  • Never list other reps or the team.
  • Resolve the org at runtime, never a hardcoded domain.
A Taskbase app

Meeting briefing

SharedBuildOpen view
OverviewTemplate
Slug
meeting-briefing
Data path
views/meeting-briefing.json
Endpoint
meeting-briefing-metrics
  • Published to other agents
  • Pinned for everyone

Fixed sources, fixed steps, one finished view

// the same sources, in the same order, every run
const account = await crm.account(meeting.accountId);
const calls = await recordings.last(account, { n: 2 });
const rules = await playbook.section('discovery');

// the model only judges what matters here
const focus = await model.pick({ account, calls, rules });

return render({ who: account.contacts, history: calls, open: focus });

Left: a skill as a document. Right: an app with its settings and the code behind it. Shortened and redrawn with fictional content.

Same use case, two ways

The meeting briefing, every morning

With a text skill the model decides how to answer each time. In a Taskbase app the briefing is built the same way every time.

As a text skill

  • The model chooses what to look up and how to lay it out, so the briefing looks different from one run to the next.
  • The rep has to ask for it.
  • You do not know whether it was read or what the rep thought of it.
  • Short or long is the same for every rep.

Why teams do not build it themselves

The differences that matter most

  1. 01

    Adoption

    The biggest difference. More than 80% of reps use Taskbase every single day. If you reach that with your own Claude setup, well done. We have rarely seen it with every rep, and across the go-to-market use cases rather than only meeting briefings and follow-ups.

  2. 02

    Spend

    Many teams come to us with a high Claude spend. One team told us a single coaching session used 40% of their credits. Taskbase includes unlimited coach chat interactions in every plan.

  3. 03

    Use cases Claude does not do out of the box

    Take the daily call list. Taskbase finds leads during the night, and in the morning you have a prioritised list of who to call right now, based on signals and your playbook. You do nothing. Lead research, call lists, briefings, follow-ups, decks, CRM updates and reporting come in one system.

  4. 04

    Consistency

    You want every user to get the same thing, and to use it every day. That needs output that does not vary or hallucinate too much. Users can adjust certain things, but in the end you want adoption. Taskbase runs each use case as a coded app, so the steps are the same every time and the model is used for judgement.

  5. 05

    Coaching as a system

    Claude can give feedback on one call from a transcript. Taskbase derives the skills your reps need from your playbook, coaches exactly those skills after every call, reminds reps along the way and checks whether their behaviour changes.

  6. 06

    Tracking

    We track how often people use it, what for, how much time it saves and whether skills improve. Do you measure that with Claude? If not, you cannot improve the system.

A use case you would have to build

A prioritised call list every morning

Taskbase finds leads overnight and ranks who to call right now from signals and your playbook. Behind it is an app, not a prompt: it reads the ICP from your live playbook, turns it into the filters your prospecting tool supports, runs the search and links every contact to its CRM record, in the same sequence every time.

Top cold call list of the day

Update list
1
Marc DuboisRegional Sales Director · Alpenwerk Security
HotReady for outreachPartner referral3,800 employeesGeneva, Switzerland

Alpenwerk Security is a Swiss cybersecurity provider offering managed security services, advisory and technology consulting.

Score: 75

Account fit 0Role fit +15Lead status +10Partner referral +50

Why now: recommended directly by a partner contact, and opened your lemlist sequence three times this week.

Open in HubSpot
2
Lena HartmannHead of Sales & Marketing · Brantec IT
HotReady for outreachPartner referral650 employeesBaden, Switzerland

Brantec IT provides managed services, SAP consulting, IT security and cloud solutions across industries in Switzerland.

Score: 75

Account fit 0Role fit +15Lead status +10Partner referral +50

Why now: recommended directly by a partner contact, and replied to your last lemlist email.

Open in HubSpot

The daily call list, built from signals in your CRM and outreach tools. All names are fictional.

A system, not a one-off answer

Skills per rep, tracked over time

Taskbase derives the skills your reps need from your playbook, coaches each rep on three focus skills and shows how they develop week by week.

Skill progressOpen full page

Anya — Skill dashboard

Updated just now

Focus skillsChange focus

Problem impact & business caseFocus since 31 AugCoach now17 27/100
Discovery depth & question progressionFocus since 05 OctCoach now67 75/100
Challenge-led value propositionFocus since todayCoach now59 54/100

Top strengths

Follow-through & commitment reliability100/100
Account relevance & preparation84/100
Active listening & shared understanding73/100
Problem impact & business case progress
Problem impact & business caseDiscovery depth & question progressionChallenge-led value proposition

Baseline 17 · Current 27 Up 10 points

3 Aug17 Aug31 Aug14 Sept28 SeptToday

Meetings per week

CW 32CW 33CW 34CW 35CW 36CW 37CW 38CW 39CW 40CW 41

▸ How the score works

A rep’s skill profile, scrolling through its sections. Example data; the person is fictional.

Feedback on a specific skill

Coaching after the call, on the skill the rep chose

One note in Slack: what went well, the biggest lever, the exact moment, better wording and why it matters. Tied to your playbook, and tracked.

TTaskbase16:20

✅ WHAT YOU DID WELL

📌 You got the buyer to name the cost of the problem

Skill: Discovery Depth & Question Progression

You asked what the slow follow-up process costs the team every week, and Tom named it himself: about two days of rep time. That gave you a number to work with.


⚡ BIGGEST LEVER · 🎯 one of your 3 focus areas

📌 Turn the cost into a business case the buyer owns

Skill: Problem Impact & Business Case

The moment in your call:

“So roughly two days a week get lost. Let me send you our pricing.”

How you could handle it better:

“Two days a week for a team of six is about twelve days a month. Before I send anything: what would it be worth to you to get half of that back, and who needs to see that number to approve this?”

Why it matters: Tom had just quantified the pain. Moving straight to pricing left the number with you instead of with him, so he has nothing to take to his finance lead. [Playbook: Business Case]

📈 PROGRESS SINCE LAST TIME

On 21 September, asking about the impact was your coaching lever and the score dropped to 12. Today you asked the impact question without being prompted. Since 31 August your Problem Impact & Business Case score has moved from 17 to 27.


🌟 Keep asking what the problem costs. At the next quantified pain, turn it into a number the buyer repeats back to you.


A coaching note in Slack on a focus skill. All names are fictional.

Side by side

A Claude setup versus Taskbase

Do it yourself with ClaudeTaskbase
Playbook readyYou write and structure it
Skills per rep, derived from the playbookYou build it
Feedback on specific skills after every call, tracked over timeFeedback on one call at a time
Daily call list and lead research overnightYou build it
The same quality for every repDepends on prompts and setup
The same steps on every runRe-interpreted from a text instruction each run
Pushed to reps, with a view of whether it was readReps have to ask, and you cannot see if they read it
Fits each rep, short or longOne text for everyone
Usage, time saved and skill growthYou build it
ModelsOne vendor, your choice
MaintenanceSomeone has to build and maintain it
SpendUsage-based

The secondary factors

What people usually talk about

  1. 01

    Maintenance

    Someone has to maintain the system. If the person who built it leaves, the next one has to get into it and keep building.

  2. 02

    Your playbook

    Taskbase does what your organisation wants because it works from your sales playbook. Claude on its own does what it thinks is good sales, which is not necessarily adapted to you.

  3. 03

    Fewer hires in RevOps

    When all calls are searchable and the playbook is in the system, you can make data-driven decisions without someone analysing every single thing. You may save a RevOps hire.

  4. 04

    The model

    If Claude is not the best model any more, why stay with it? New models keep arriving, cheaper at the same quality. We test models all the time.

  5. 05

    Cost

    For what you can use it for, Taskbase costs less than other systems.

Before you build

Six questions to ask yourself

  1. 1Do your reps get the briefing pushed, and can you see whether they read it and what they answered?
  2. 2Do you measure how often reps use it, and what for?
  3. 3Does every rep get the same quality of answer, every day?
  4. 4Does it coach specific skills over time, or only give feedback on single calls?
  5. 5Who maintains it when the person who built it leaves?
  6. 6What does one coaching session cost you in credits today?

This page compares building a sales coach yourself on a general AI model such as Claude with using Taskbase. It is not about the quality of any model. Figures from customers are examples from individual teams. The difference between a text skill and an app is architectural and directional, not a zero-hallucination claim: the model-driven parts inside an app can still vary, so test speed and cost against your own alternative.

Not sure whether to build? Talk to us first

Tell us what you have built or planned, and we will show you what it would take to reach every rep, every day.