Skip to main contentSkip to navigation

A domain track

Claude & AI for Sales

Sales, business-development and RevOps teams.

24 topics

A discovery call ends at 4:30. By the time the notes reach the CRM, the follow-up is written and the proposal is drafted, it is Thursday and the prospect has spoken to a competitor. Reps are rarely short on skill. They are short on hours, and every hour of admin is an hour not spent with a buyer. The workshop starts from a real call recording or transcript and turns it, within minutes, into a summary, a follow-up email and a CRM update.

The fear in sales is an email that sounds like a template, or a proposal that goes out with terms nobody approved. So Claude works only from what was said on the call and from the approved proposal template. Prices, payment terms and clauses are never rewritten. The rep reads every draft before it is sent and puts it in their own voice. The speed comes from the draft already waiting, not from skipping the read.

The material is your team's own: call recordings and transcripts, the approved proposal template, a CRM export with the fields nobody fills in, and the pipeline report someone assembles by hand before each review. From these the group builds a call summary, a proposal from the template and a pipeline dashboard. Each participant leaves having taken one call all the way from recording to a follow-up that is ready to send.

Online course

Start online, at your own pace

The material we teach in the room, recorded slide by slide. You go through it when it suits you, from any screen.

Claude & AI for Sales: the online course is on its way

Leave your email and we'll write once, the day it opens.

What happens to your details

Giving us these details is your choice, and no law requires it. Without the fields marked required, though, we can't finish what you came here to do.

What for: To email you once, the day the online course for your role opens. Nothing else.

Who gets it: Wider Group only. Your address sits with our infrastructure providers, Supabase and Vercel. Our email provider, Resend, sends us a note when you sign up. All three run servers outside Israel.

You can ask to see what we hold on you, correct it, or have it deleted, any time. Write to shahar@wider-group.com and we answer within 30 days. The full detail is in the Privacy Policy.

Rather do it live? See the live workshops

Today's challenges

  • Manual meeting prep and lead follow-up
  • Tailoring proposals and emails per prospect
  • Pipeline analysis and forecasting

Example use cases

  • Summarizing calls and building automated follow-ups
  • Tailored proposal drafts from a template
  • A pipeline dashboard from CRM data

What we teach here

Intro

A live opening session built to shift the room, not lecture it: real demos of what Claude can already do inside your workflows, run in front of the group. Participants leave with a working sense of where AI helps and where it doesn't, and enough curiosity to start using it that afternoon.

AI & LLM Basics

What tokens, context windows and hallucinations mean, explained without the math and without the hand-waving. Once a team understands why a model sometimes gets things wrong, it stops either trusting it blindly or dismissing it after one bad answer. Every other module in the program builds on this one.

Claude Intro

A new AI tool comes out every week, and you don't need to chase them. We map the main ones and what each does best, then explain why we spend the day in Claude. After that we set it up together: privacy settings, the one capability to switch on, and a tour of the screen. Face to face it is a live demo; in the online course it is a recorded tour.

Claude Skills

Claude Skills turn a procedure your team already does well into something Claude can repeat on its own: the same checklist, the same tone, the same edge cases covered every time. You build it once with the person who actually knows the process, and from then on every teammate gets that expertise on demand. For teams where quality depends on one or two people, this is how that stops being a bottleneck.

Prompt Engineering

Structure, context and role framing: the craft of asking in a way that gets a usable result on the first try instead of the fifth. Participants practice on real prompts from their own work, not toy examples, so what they take home already fits the job. Every other module assumes this fluency, which is why it comes early.

Claude Projects

Claude Projects hold your documents and instructions in one persistent workspace, so every conversation starts already knowing your company, your terminology and your rules. Teams that set this up once save the ten minutes of re-explaining context at the start of every session, every day. For anyone running the same kind of task repeatedly, this alone changes the math.

Design systems: your brand inside Claude

Without a design system, Claude decides how everything looks, and it comes out different every time. The session shows what a design system holds, how every slide, dashboard and app is built on it, how to make one from your website and a deck you already have, and how to keep several and switch between them.

Artifacts: from answer to deliverable

The difference between an answer and a deliverable. The session covers when something should become an artifact, every kind there is today, how they all come out on your design system, the four ways to change one, and what you do with it: connect it to apps, connect it to files, share it as a live place, or export a snapshot.

Agentic AI vs. Chat

The shift from asking Claude a question to handing it a multi-step task it completes on its own, checking in only where it matters. Participants learn what actually counts as an agent, when handing over work beats doing it turn by turn, and how supervision needs to change once Claude is running unattended. Get this wrong and you either babysit an agent that didn't need it or trust one that did.

Agentic workflows in the Claude chat

In the Claude chat you can hand over a whole job instead of asking a question. Claude plans the steps, searches the web, reads your files, runs code and hands back a finished document, spreadsheet or deck. On a big task it can split the work between several sub-agents running at once. Participants learn which work is worth handing over and how to brief it the way they'd brief a colleague, then practice staying in control while Claude works. They finish by turning a weekly chore into a scheduled task that runs on its own.

Claude Across Office

A full pass across the Office suite: drafting and redlining in Word, tables and analysis in Excel, decks in PowerPoint, and inbox triage in Outlook, taught as one connected workflow rather than four separate tricks. Every exercise uses documents close to what participants actually produce at work. It's the broadest module in the program, and the one most teams come back to most after training.

Routines in Claude

Tasks Claude runs on its own, on a schedule: a morning brief from your calendar and inbox, a weekly report, a competitor watch. Participants learn to tell a routine from its schedule, connect only the connectors it needs, and test every routine before it runs alone. They leave with one routine that works from the next morning.

Connectors & MCP

Connecting Claude to the systems your team actually runs on: drives, CRMs, databases, through connectors and MCP, with the permission boundaries covered before the connection ever gets made. Participants leave knowing exactly what to expose and what to keep out of reach. This is the module that turns Claude from a smart typewriter into something acting on real, current data.

CLAUDE.md

CLAUDE.md is a plain text file Claude Code reads at the start of every session, so whatever you'd explain to a new hire on day one, you write there once. Participants learn what goes in it and what stays out, when it's read, and where it lives: the organization, you, the project and a subfolder, all loading together. They leave with a draft from /init and one rule for growing it: what you corrected twice goes in the file.

Agents for non-engineers

How to build an agent without writing code: it gets a job description, a badge that limits what it can touch, and a bottom line it hands back. Participants see why the work goes to a separate room, take an agent file apart, and fill in the one-page charter that turns into the agent's file. They learn to hire for a role, not a task, and to tell when a job needs an agent rather than a skill. They leave knowing the hard part is the charter, and that the charter is their own expertise, written down.

Plugins: the department in a box

A plugin carries the agents, skills and hooks a team built, so another team installs the same department instead of rebuilding it. Participants see what goes in the box and what stays home: CLAUDE.md and the permission rules belong to each team. Then they ask Claude to build one, try it in a fresh session, and share it through a marketplace.

Context Management

How context windows, memory and cost interact, and what to do about it before a long working session starts drifting or the bill surprises someone. Participants learn to spot when Claude is still hauling a task that should have been closed an hour ago, and how to reset without losing what mattered. A short module with an outsized effect on both output quality and the invoice.

Safe AI at Work

The rules every employee needs before their first real session: what data is safe to share, what isn't, and what org-level guardrails should exist so individual judgment isn't the only safeguard. This module is usually the one legal and IT ask for by name. It replaces vague anxiety about compliance with a clear, specific policy people can actually follow.

Human in the Loop

Where people belong in an AI-assisted workflow: which steps need a review gate, which need an approval, and how to calibrate trust so oversight isn't either everywhere or nowhere. This pilot module gives teams a concrete framework instead of a gut feeling about what to check. Get the calibration right and quality goes up without slowing anything down.

Security & Privacy

Permissions, prompt injection and data boundaries: what makes an agent that can act also one that can go wrong, and how to run it anyway without carrying the risk. This pilot module is built for organizations moving agents past read-only demos into things that write, send and change data. It's the module security teams should sit in on.

Claude for Word

Claude inside Word for text-heavy roles: drafting from a brief, redlining a contract, controlling tone across a document, and automating the parts of writing that are really just formatting. This pilot module is aimed at HR, legal, marketing and sales, where documents are the daily output. It's the module that turns a quick-draft request into a five-minute job.

Claude for PowerPoint & Decks

Claude for PowerPoint is a side panel inside PowerPoint. It reads your template, builds new slides on your own layouts and makes charts and tables you can still edit. The session works on one deck that four people touched: put it back on the master, rebuild a chart that was pasted in as a picture, and check every number against the source before anyone presents it.

Claude in Slack & Teams

Coming soon

Coming soon: bringing Claude into Slack and Teams so summaries, answers and actions happen where the team already talks, instead of a separate tool people forget to open. This syllabus item covers both the setup and the etiquette of an agent inside a shared channel. Built for teams whose real workflow lives in chat, not in a dedicated app.

AI Policy & Governance

Coming soon

Coming soon: writing the AI policy an organization actually needs, usage rules, risk tiers and rollout governance, instead of a generic template nobody follows. This syllabus item is for leadership and compliance stakeholders shaping how AI gets adopted company-wide. Built to produce a document teams can point to, not a discussion that goes nowhere.

Hours back for the buyer

Four tools built on your CRM, your recordings and your templates, each taking over work that usually waits until the end of the day.

A follow-up that goes out the same day

A draft email waiting in the inbox minutes after the call, with what the buyer said, what was agreed and the next step. While the deal is warm it goes out that day, and the rep approves and sends it personally.

A proposal from the approved template

A quote assembled from the team template and the buyer's details, with the price list and legal clauses left untouched. The rep tunes the wording, and the sales manager signs off on any exception.

CRM fields that fill themselves

The fields nobody completes are drawn from the call summary: who decides, what the budget is, when the next step falls. The rep sees a proposed update and accepts it, so the record stays theirs.

A forecast you can defend

A pipeline dashboard built from CRM data, with a list of deals that have not moved and questions ready for the review. Whoever has to defend the number to a VP knows where each figure came from, and the call on every deal stays with them.

Questions people ask

Is there a Claude workshop for sales teams?

Yes. Wider Group runs a workshop for sales and RevOps teams, on site or remote, in Hebrew or English. It starts from a real call recording or transcript, and works on your CRM export and approved proposal template. The online course has a general version for sales people, but it is not open for purchase yet, so for a sales team the workshop is the better fit.

Can Claude write sales follow-up emails without making things up?

Claude works only from what was said on the call and from your approved proposal template. Prices, payment terms and clauses are never rewritten. In Wider Group's workshop the rep reads every draft before it is sent and puts it in their own voice, so the speed comes from a draft that is already waiting, not from skipping the read. The sales manager signs off on any exception.

How do I stop CRM fields from staying empty?

Fill them from the call itself. In Wider Group's workshop, the fields nobody completes, such as who decides, what the budget is and when the next step falls, are drawn from the call summary. The rep sees a proposed update and accepts it, so the record stays theirs. The pipeline report is then built from the CRM data, with no hand assembly before each review.

Before quarter end

Tailoring means working on your team's own calls and templates. You bring one or two recordings, the approved proposal and a CRM export, and once customer details are removed the exercises run on them. Reps leave with a call of their own, already processed. Tell us how many reps and when your quarter closes, and we'll send a quote.