What should sellers prepare before a Claude workshop?

Before a Claude workshop, prepare approved examples of your sales work, a short account of your sales process and a clear decision about which information participants can use. Confirm account access before the session. Sellers should arrive with a task to practise and a way to recognise a correct result—not a folder full of customer data nobody has approved.

What should sellers prepare before a Claude workshop?

Prepare the work, the context and the review rules. The practical sequence is:

1. Pick a recurring task, such as meeting preparation or a follow-up.
2. Collect approved notes and a representative finished example.
3. Explain your offer, ideal customer and sales stages.
4. Confirm which accounts and information participants can access.
5. Decide who checks the result and how corrections are captured.

If you are still choosing a provider, read the guide to choosing a Claude workshop. Preparation should match the agreed exercises, not an imaginary list of everything Claude might do.

Bring enough context to complete the task, but no more customer information than the task requires. That keeps the session practical without making unrestricted access a condition of learning.

Why preparation matters more than a prompt list

A useful follow-up depends on what happened in the meeting. It also depends on your offer, the seller's voice and the commitments the business is willing to make. A polished prompt does not supply those facts.

The same problem appears in meeting preparation. Without a clear purpose for the conversation, the result can become a long account summary that tells the rep little about what to ask next. Your preparation should make the desired output concrete.

For a B2B SaaS team, the useful test is whether the seller can repeat the task on an actual deal. Watching the facilitator produce an impressive answer is not the same thing. The workshop should leave room to inspect incorrect results and fix the instructions that caused them.

Start with a sales task, not a department-wide ambition

Avoid a brief such as making everyone more productive with AI. It gives the facilitator no useful boundary and the manager no clear acceptance test.

Choose something sellers already do. For meeting preparation, the output might be a brief containing the account situation, previous commitments and unanswered questions. For a follow-up, it might be an email draft with only the next steps agreed in the call.

Use the following preparation guide:

Task	Bring	A correct result contains	Keep outside the exercise
Meeting preparation	Approved account context and the meeting purpose	Relevant facts, open questions and source gaps	Unsupported claims about the buyer
Follow-up drafting	Approved notes and a representative seller email	Accurate commitments and a clear next step	Promises not made in the meeting
Proposed CRM update	Field definitions and approved meeting notes	Facts mapped to the correct fields	Guessed close dates or qualification answers

These are exercise boundaries, not claims that every workshop includes every task. Agree the agenda with the provider first. A smaller set of relevant exercises is more useful than a broad demonstration that nobody repeats afterwards.

Prepare context that sellers can correct

Your context pack should explain how your team sells. Start with the offer, the buyer, the sales process and the language your team actually uses. Existing material is usually a better starting point than a new document written solely for the workshop.

Bring the current version of your positioning and qualification rules. Mark anything disputed or out of date. If the sales leader and the website describe different offers, resolve the difference rather than letting the assistant choose between them.

Useful context includes:

• Your ideal customer and the problems you help them solve.
• The current offer and its boundaries.
• Sales stages and what counts as progress.
• Common objections and approved responses.
• Examples of clear seller communication.
• Rules for information that must remain unknown until confirmed.

A context pack is not a licence to copy every available document. Remove duplicate, obsolete and irrelevant material. The seller should be able to explain why a source belongs in the exercise.

Onwise's published workshop outline asks for an hour with the sales leader beforehand. Onwise uses that discussion and existing material to prepare the sales context pack. Confirm what the provider needs from you rather than creating a large new preparation project unnecessarily.

Bring examples of your voice, not just your brand guidelines

A seller's follow-up should sound like a person continuing a conversation. An approved email with clear next steps is often a more useful reference than a page of tone adjectives.

Choose an example that reflects how you want sellers to write now. Remove sensitive details that are unnecessary for the exercise. Explain which features matter: short paragraphs, a direct question, a restrained tone or a particular way of listing agreed actions.

Then bring a contrasting example that needs work. The facilitator can use it to show the difference between accurate content and suitable wording. An email can sound right and still contain a promise nobody made.

Ask the seller to identify the corrections before generating another version. That makes review part of the skill being taught instead of an invisible step performed by the facilitator.

Confirm accounts and access before the day

Ask the provider for the actual account requirements. Product access and available connections depend on the organisation's setup; do not rely on a screenshot from a previous workshop.

Have the relevant system owner approve intended access. Separate permission to read an example from permission to change a CRM record or send an email. Those actions carry different consequences.

Before connecting anything, confirm:

• Which account each participant will use.
• Whether that account has the required approved features.
• Which information the exercise can read.
• Whether the exercise can create drafts, change records or send messages.
• Who can revoke access afterwards.

Do not bring passwords or shared login details in the context pack. Participants should use the organisation's approved sign-in process. If access is unresolved, arrange sample material and keep the exercise separate from production systems.

A workshop should not become an unplanned decision about who can access customer information. Resolve that with the system owner before the facilitator asks anyone to connect an account.

What if you cannot use live customer information?

Use approved sample material with the same structure as the real task. A sample discovery-call note can still contain a business problem, an agreed action and an unanswered question without identifying an actual customer.

Preserve the difficult parts of the job. If the real workflow includes conflicting notes or missing fields, the sample should too. An artificially tidy example hides the review work sellers need to learn.

Ask the facilitator to distinguish the sample exercise from a production connection. Completing the exercise demonstrates a learning outcome. It does not prove that your organisation has approved a live integration or its permissions.

Agree what sellers should leave able to do

Define an observable result before the session. For a follow-up exercise, the seller should produce a draft, trace its commitments back to the notes and correct unsupported details. For CRM work, the seller should distinguish confirmed facts from assumptions.

Ask for a reusable reference rather than a prompt list without explanation. It should describe the inputs, the task and the checks. Include what to do when information is missing.

Assign a manager or process owner to collect problems afterwards. Otherwise each rep develops a different workaround and the shared context quickly stops reflecting how the team sells.

Onwise's workshop page describes 30 days of support, including a 20-minute weekly team sync, regular individual check-ins and a shared questions channel. Treat those as named activities to confirm in the proposal, not a guarantee of a particular adoption result.

The day-before checklist

Run the check with the people attending, not only with the person buying the workshop. A manager's working account does not establish that every seller is ready.

Confirm the selected task, the approved material, the account requirements and the person responsible for exceptions. Make sure participants know whether they are practising on sample data or live records. Remove anything unnecessary from the shared folder.

Bring a question the team has not resolved. For example, should an uncertain next step remain blank or be flagged for the seller? A useful workshop can expose that decision, but the business still owns the answer.

For hands-on work around your team's sales process, review the Onwise AI sales workshop and agree the preparation scope before booking. Onwise is a fit for sales teams seeking practical Claude exercises, rather than a general introduction for every department.

FAQ

One last thing: bring an incomplete example

Remove the agreed deadline from a sample follow-up brief. Ask the seller to explain what the draft should do with the missing detail.

The correct habit is to flag the gap, not reward a confident guess. That preparation choice teaches a more useful skill than another polished demonstration.

If your team needs help scoping the session, book a discovery call with the tasks and preparation questions you want to resolve.