After this lesson you will be able to
- Build a one-page industry brief covering KPIs, regulations, language and buying patterns
- Use industry playbooks and customer conversations to learn fast without faking expertise
- Rewrite your discovery questions in the industry's own terms
- Know when to bring in someone with deeper industry experience
Know what expertise you actually need
You are not trying to become an operator in the industry. You are trying to be the AE who understands enough to ask sharp questions, follow the answers and connect them to how Salesforce could help. That is a much smaller target, and you can reach it in a week of focused work.
Aim for four things. The handful of numbers that leaders in the industry watch every week. The rules and regulations that constrain how they handle customers and data. The words they use for customers, transactions and roles. And how they typically buy technology, including who signs and what slows them down.
Write all four on one page and keep it next to you for every call in that vertical. Update it after every meeting. Within a month, it will be more useful than any generic training.
Days one and two: read with a purpose
Start with material written for the industry, not for salespeople. Read the trade association website, the top two trade publications, and the annual reports or investor letters of a few public companies in the space. Look for what leaders say they are worried about this year.
Then read our industry playbooks at /resources/playbooks/ and the industry pages at /industries/. They summarize common processes, pain points and Salesforce use cases by vertical, so you can see how the industry's problems map to the platform. For example, the manufacturing playbook at /resources/playbooks/manufacturing/ is a useful starting point for distributors and manufacturers.
As you read, fill in your one-page brief. Every time you see a number that leaders track, write it down with a plain definition. Every time you see a term you do not know, write it down and look it up.
Learn the KPIs and what moves them
Every industry has a short list of numbers that leaders live by. Knowing them changes your discovery. Instead of asking what keeps a leader up at night, you can ask about the specific number they are trying to move.
For each KPI, learn three things: what it measures, what a leader would consider good or bad for their business, and which processes drive it. You do not need industry benchmarks to do this. Ask the customer what good looks like for them, and you will learn more than a benchmark tells you.
Then connect each KPI to a process Salesforce could support. For example, in a home services business, first-time fix rate depends on scheduling, parts and technician information, which connects naturally to Field Service. That link is the start of a value hypothesis you can test with the ROI calculator at /salesforce-account-executives/roi-calculator/.
Respect the regulations without pretending to be a lawyer
Regulated industries have rules that shape every technology decision. Health care organizations in the United States must handle patient information under HIPAA. Financial services, insurance, education and the public sector each have their own rules about data, records and communication. You do not need to interpret these rules. You need to know they exist and ask how they affect the project.
Ask who in the organization owns compliance, which reviews a new system must pass, and what has caused problems with past vendors. Then involve the right people early. Never tell a customer that a product makes them compliant. Compliance depends on how a system is configured and used, and that is a question for their compliance team and the delivery team.
If the deal involves detailed regulatory requirements, bring in someone who has implemented in that industry before. A delivery partner with industry experience can join discovery and speak to configuration and process. The deal desk at /salesforce-account-executives/deal-desk/ is one way to find that help on a live deal.
Days three to five: talk to people who do the work
Reading gives you vocabulary. Conversations give you judgment. Talk to three kinds of people this week: a customer in the industry who already uses Salesforce, a colleague or partner who has sold or delivered there, and if you can, someone who has worked in the industry itself.
Ask each person what surprised them about the industry, what outsiders get wrong, and which questions earn respect in a first meeting. Ask the existing customer how they talk about their own work and what they wish their vendors understood. Take notes in your brief.
End the week by rewriting your standard discovery questions in the industry's language. A generic question about the sales process becomes a specific one about how a broker places business, how a distributor quotes a custom order, or how an agency tracks a client's renewal. Practice them out loud before your next call.
- Day 1: trade association, two trade publications, three annual reports or investor letters
- Day 2: our industry playbook and industry page, draft of your one-page brief
- Day 3: conversation with an existing customer in the vertical
- Day 4: conversation with a colleague or partner who has sold or delivered there
- Day 5: rewrite discovery questions, role-play one call, finalize the brief
Use what you learn without overplaying it
The fastest way to lose credibility is to act like an insider when you are not. Customers respect an AE who says what they know, admits what they are still learning and asks good questions. Use the industry's language, but do not perform it.
When you are unsure, say so and ask. A question like "I've read that X is a big focus this year; is that true for you?" shows preparation and gives the customer room to correct you. That correction is valuable, so write it in your brief.
Talk tracks
Opening a first meeting in a new vertical
“I've spent time learning how businesses like yours run, but you know it far better than I do. Which two or three numbers does your leadership team watch most closely right now?”
It shows preparation, invites correction and gets you to the KPIs quickly.
The customer uses a term you don't know
“I want to make sure I understand that correctly. When you say that, what does it mean in your business, and how does it affect your team's day?”
Honest curiosity builds more trust than nodding along.
Raising regulations in a regulated industry
“I know your industry has specific rules about data and records. Who owns compliance on your side, and what reviews would a new system need to pass?”
It shows awareness without pretending to interpret the rules.
The customer asks whether Salesforce makes them compliant
“Compliance depends on how the system is configured and used, so I'd want your compliance team and an experienced implementer in that conversation. I can help set that up.”
It avoids an overclaim and moves the conversation to the right people.
Connecting a KPI to a Salesforce use case
“You mentioned that number is your biggest focus. Which part of the process drives it most today, and where does information get lost along the way?”
It ties the industry metric to a process you can improve.
Asking an existing customer for help learning the industry
“I'm taking on more accounts in your industry and want to be useful to them. Could I have 20 minutes to ask what you wish vendors understood about your business?”
Most customers are glad to help someone who wants to understand them.
One-page industry brief
Use it on a live deal. Tick items off as you go; nothing you tick leaves this page.
Common mistakes
Pretending to be an insider
Customers spot it quickly. Say what you know, admit what you are learning and ask good questions.
Learning features instead of the business
Industry product features matter less than the KPIs and processes behind them. Start with the business.
Telling a customer a product makes them compliant
Compliance depends on configuration and use. Bring in their compliance team and an experienced implementer.
Quoting industry statistics you cannot source
One wrong number damages credibility. Ask the customer what good looks like for them instead.
Only reading, never talking to people
Reading builds vocabulary but not judgment. Schedule real conversations in the first week.
How you will know it is working
- Customers start using their own jargon freely with you instead of translating
- Your discovery notes name specific KPIs and processes, not general pain
- Prospects ask your opinion on how peers in their industry handle a problem
- Your industry brief changes after each call because customers correct and add to it
Questions
Can I really learn an industry in a week?
You can learn enough to run a credible first meeting and ask strong questions. Depth comes from the next few months of customer conversations. The one-week plan gets you started on the right foundation.
Where should I find industry KPIs if I have no contacts?
Start with trade association material, trade publications and the annual reports of public companies in the space, then our industry playbooks. In your first meetings, ask the customer which numbers they track. Their answer is the one that matters.
Should I use industry benchmarks in my business case?
Only if you can name and verify the source. It is usually stronger to build the business case from the customer's own numbers. That avoids arguments about whether a benchmark applies to them.
When should I bring in an industry specialist?
When the deal involves detailed regulatory requirements, unusual processes or industry systems you do not understand. A colleague or delivery partner with experience in that vertical can join discovery and add depth you cannot fake.

