Somewhere in the middle of a discovery call, it is easy to feel yourself shrink.
The client starts describing a real problem: their analysts are drowning in manual work, the monthly close takes too long, nobody trusts the workbook… and too many people copying and pasting data because, at some point years ago, that became “the process.”
And instead of saying, “Yes, this is exactly the kind of situation good Excel training can help with,” you hear yourself soften:
“Well, I mostly do training, so what I could maybe do is put together a session that, if it is helpful, walks your team through some of this.”
By the end of the sentence, you have basically apologized for showing up.
If you sell Excel training, you may know the feeling. Excel can be so familiar and so ordinary that it starts to feel like the lightweight offer. So when a client describes a messy reporting process or a fragile workbook, you may feel pressure to position yourself as something more serious than “the Excel trainer.”
I think that is the wrong frame.
In many organizations, Excel is where critical business happens after the official systems run out of road: where assumptions are made, where exceptions are handled, where reports get assembled, and where someone improvises a process that later becomes mission-critical without ever being formally designed.
So if Excel is where the work is actually happening, Excel training is not a side dish.
Excel training is not separate from the business problem
The apology usually starts with an assumption that “Excel training” and “solving the business problem” are two different things.
The client may say, “We need Excel help” or “Can you do something to help our finance reports run faster?” But underneath that request is usually something more practical: people are wasting time, files are too fragile, teams are relying on one or two spreadsheet heroes, and managers want better judgment rather than just prettier formulas.
That is why the job of the trainer is not to apologize for offering Excel training, but to connect the training to the work without pretending the work is simpler than it is.
You do not need their exact workbook to be relevant
One trap in selling training is thinking that relevance means you must prove you already know the client’s exact problem, exact data, exact systems, exact metrics, and exact internal chaos.
But your job is not clairvoyance. In fact, if their exact problem is so common that an outsider can name it instantly and solve it from a script, then either the problem is not very interesting or their business is more cookie-cutter than they probably believe it is.
Most Excel problems have patterns, but they also have local details. They have legacy files, informal ownership, hidden assumptions, and one person who knows why column H can never be deleted.
Good Excel training does not require turning the entire class into a live reenactment of that one unique process. The stronger position is somewhere in the middle: “I understand the patterns well enough to help your team build judgment around the specifics.”
That is a much better offer than “send me your exact data and I will make the lessons follow verbatim.”
Ultimately, the goal is to help people understand the pattern well enough to adapt when next month’s file is slightly different, because next month’s file is always slightly different.
Relevance is not the same as overfitting
Clients are right to worry about generic Excel training. Nobody wants to sit through three hours of sample sales data, menu tours, and toy examples that have nothing to do with their work.
But there is an opposite mistake too: overfitting the training so tightly to one internal workbook that nobody learns the broader pattern.
That may feel customized, but it can actually make the training less useful. If all you do is walk through one exact file, people may leave knowing how to survive that one exact file. That is not worthless, but it is not the same as learning how to think through the next messy export, the next broken model, the next reporting request, or the next workbook inherited from someone who left the company two years ago.
Good Excel training sits in the middle. It is not generic, and it is not a canned product tour. But it is also not a theatrical performance of one client’s internal process. The aim is to use familiar examples to teach transferable judgment.
| Less useful | More useful |
|---|---|
| Generic tour of Excel features | Excel concepts connected to familiar business work |
| Teaching only one exact workbook | Realistic examples that teach reusable patterns |
| One-off walkthrough | Practice recognizing what kind of problem this is |
| Memorizing steps | Understanding why the steps work |
This is an important distinction to make on a sales call, because many clients use “customization” as a proxy for relevance. That is understandable. But exact-data worship is not always the answer. Sometimes the abetter answer is:
“We can absolutely make the examples familiar to your team, but I do not want the session to become a guided tour of one workbook. The goal is for people to understand the patterns well enough to apply them when the next version of the problem shows up.”
The discovery call is where you show how you think
You do not prove relevance by promising to customize everything, but by asking questions that show you understand how Excel work actually breaks.
| Discovery question | What it helps reveal |
|---|---|
| What Excel work should people be able to do better after the session? | The business outcome |
| Where does the current workbook or reporting process break down? | The pain point behind the training request |
| What are people doing manually today? | The automation and cleanup opportunity |
| How are files currently built: Tables, PivotTables, Power Query, formulas, or mostly manual steps? | The team’s current Excel maturity |
| What examples would feel familiar without turning the session into one-file tech support? | The relevance layer |
| What should learners be able to recognize on their own afterward? | The judgment layer |
Those questions do more than gather information. They show the client how you think. They also keep you from making a promise that you can cover every contingency they are currently facing, to order. That last question is especially useful, because it keeps the conversation from collapsing into “Can you use our exact data?” as if exact data is the only path to relevance.
You are not the supplicant in this conversation
Put all of this together and the apology starts to disappear: you are not making a watered-down offer. You are offering one version of real help, and proving it with the way you diagnose the situation, scope the work, and separate transferable Excel patterns from local quirks.
If your team is trying to get more out of Excel without sitting through another generic feature tour, that is exactly the kind of work I do at Stringfest Analytics.
I help teams build practical Excel judgment around the work they already own: cleaner reports, less manual effort, better workflows, and more confidence when the next weird workbook shows up.
You can learn more about my approach on my How I Work page: