Chapter 5: Leadership · Chapter 3: Knowledge & Wisdom · Chapter 2: Visioning
How to prepare for a first sales meeting with a new B2B prospect
By the Niles team · · 8 min read
The short answer
Decide the one thing you must leave with, such as who decides and how they buy. Research the company and each attendee, including what each might personally gain. Prepare a short opening, a few open questions and the objections you expect. Check your own online profile, arrive early, and know the next step you will propose.
- Set one objective before you go. If you can't name one, the meeting isn't ready.
- Research the people, not only the company: each attendee wants something personal from the decision.
- Rehearse questions and likely objections, not a word-perfect pitch.
- Know why this prospect should listen to you, and make sure that answer is visible before you arrive.
A first meeting with a new B2B prospect sets the tone for everything after it, and most of what decides it happens before you walk in. Good preparation is not a longer slide deck. It is knowing what you want from the hour, who you are meeting and what each of them cares about, and what you will say when the conversation turns.
Start with one question: why should this prospect listen to you?
Before any research, answer the question The Pharaoh's Pitch puts at the start of every first meeting: why does this prospect need to listen to me? If you can't answer it in a sentence, no amount of polishing will rescue the meeting. As Ivan Yong puts it in chapter 3:
I approach every sales meeting, especially when meeting the prospect for the first time, with the question, "Why do my clients or prospects need to listen to me?"
Chapter 3 frames this as authority: the right to be listened to, which you earn before you have any power to persuade. The book's route to it is knowing your field well enough to hold a real conversation about the client's world, not reciting product features. It also suggests that even a junior seller facing industry veterans can earn a hearing by bringing a clear view of what is coming next for their industry.
So write your answer down, and make it specific to this prospect. "We're a leading provider" is not an answer. "I've spent the last year working through the new e-invoicing rules with other mid-sized distributors" is.
Set one objective, and the next step you'll propose
Decide the single thing you must leave with. Chapter 5, on leadership, treats this as part of leading yourself before you try to lead a sales conversation. As Ivan Yong puts it in chapter 5:
It is critical to have a goal before you meet your prospect. If you do not have a goal, it's best to delay the meeting until you are certain.
The book's own examples of a meeting goal are finding out who the decision makers are, or what the buying process looks like. Other good ones: confirm whether there is a budget this year, find out what triggered their interest, or secure a second meeting with the technical lead. "Build rapport" is not an objective, because you can't tell afterwards whether you achieved it.
Then decide the next step you will propose if it goes well, and the words you will use: "Would it make sense to set up a session with your IT lead next week, so we can test the integration question properly?" Walking in with that sentence ready is the difference between a pleasant chat and a deal that moves.
Research the company, then the people in the room
Research the company enough to ask one informed question, then spend more of your time on the individuals. Companies don't decide; people do, and each of them wants something from the decision for themselves.
For the company, an hour covers most of it: recent news and announcements, the annual report or filings if it is listed, who its customers and competitors are, and any regulatory or market change heading its way. Pick one recent, relevant topic to open with. Chapter 2 recommends exactly this: move off the product quickly and bring up something current in their industry, so they start telling you about their business.
For the people, chapter 2 asks you to think at each buyer's personal level, not through their job title. It calls these "personal wins": what the person hopes the purchase will do for them, over and above the company's needs. In one of its examples, the economic buyer wanted a well-known software brand in his company's listing prospectus, while the IT lead saw the same system as a threat to his job and his influence.
A simple grid keeps this honest:
| Who | Their part in the decision | What they might personally want | Question to test it |
|---|---|---|---|
| CFO | Signs off the budget | A clean audit before a fundraise | "What does a good year-end look like for you?" |
| Head of HR | Owns the benefits budget | Fewer staff complaints about claims | "Where do claims cause the most friction today?" |
| IT lead | Can block on security | Nothing new to maintain | "What would worry you about adding another system?" |
The right-hand column is guesswork until the meeting confirms it, and that is the point. You walk in with hypotheses to test rather than a pitch to deliver.
If you are meeting a family-run firm in Kuala Lumpur or Singapore, add a line for who actually holds the decision, which may not be the person who booked the meeting. Selling to Malaysian and Singapore buyers covers that in more depth.
Check what they'll find, and send the agenda
Assume the prospect will look you up before the meeting, and make sure what they find supports your answer to "why should I listen?". Chapter 6 puts it plainly: your pitch begins before the meeting, because anyone can check your posts, comments and photos, and your reputation online introduces you before you arrive.
Spend ten minutes on your own LinkedIn profile. Does the headline say what you help clients do? Is there anything recent that shows you know their sector?
Chapter 6 singles out punctuality, especially at a first meeting, as a simple expectation you can't afford to miss, so plan the route and arrive early. Chapter 4 counts preparing for the meeting, being on time and dressing properly as basic respect.
Send a short agenda the day before. It confirms the time, shows you have thought about their business, and lets them correct you before the meeting rather than during it:
"Hi [Name], looking forward to Thursday at 10am at your office in Bangsar South. Here's what I thought we'd cover: how you handle [area] today and where you'd like to take it; a short look at how we've helped firms in a similar position; and whether a next step makes sense. Is there anything you'd like to add, or anyone else who should join?"
That last question often tells you who else is involved before you have even met.
Plan your opening and keep the deck short
Open by confirming the time and the agenda, then hand the conversation to them. Your own material should take a small share of the hour.
A workable opening:
"Thanks for making the time. I've got us down for 45 minutes, does that still work? I'd suggest we spend most of it on how things work for you today and where you're heading. I'll share briefly what we've seen with similar firms, and at the end we can decide together whether a next step makes sense. Anything you'd like to add before we start?"
The book is sceptical of the standard pitch deck. Chapter 6 describes decks that become so generic the only change between clients is the logo on the first slide, leaving buyers who see several vendors unable to tell them apart.
Chapter 5 suggests removing PowerPoint altogether if it gets in the way of an engaging conversation. Chapter 2 adds that if the buyer challenges your product, you shouldn't defend it: note what was said and who said it.
So bring two or three slides, or a single page, that you can put away the moment the conversation takes off.
Rehearse the questions and objections, not a script
Prepare a handful of open questions and the two or three objections you are most likely to hear, then picture the meeting as it is likely to go. Don't memorise a pitch.
Chapter 5 describes a mental rehearsal done just before meeting a client: picture the questions they are likely to ask and how they will ask them, including the mood they might be in, and picture your own response. The author also reminds himself that the client is with him, not against him. The same chapter warns against over-rehearsing, because a scripted seller can't react to what actually happens in the room.
Questions worth preparing for almost any first meeting:
- "What prompted you to take this meeting now?"
- "How are you handling this today, and what's working about it?"
- "If we fast-forward a year and this has gone well, what's different?"
- "Who else would be involved in a decision like this?"
For objections, write one calm line and one follow-up question for each. The two you are most likely to meet at this stage are covered in what to say when a prospect is happy with their current provider and the request for a price before you understand the need.
Then listen for what repeats.
Chapter 4 tells of a university dean who kept asking the same question while a sales team answered with data, case studies and surveys. What he wanted, the author concluded, was to be recognised as a thought leader in his field.
A question a prospect asks twice is often telling you what they really care about.
Rehearsing out loud helps more than rehearsing in your head. You can do that with a colleague, or see practising sales calls with AI for how to set up a realistic practice buyer. Niles has a meeting prep tool, and a role-play in which the AI plays your client and then debriefs you.
Debrief within the hour
Preparation for the second meeting starts the moment the first one ends. While it is fresh, write down what happened: what they said, what surprised you, which of your guesses about personal wins held up, and whether you met your objective.
The book's epilogue asks for exactly this habit: debrief yourself straight after every sales meeting, including the ones that went badly, and record what happened objectively, without emotion. Chapter 5 adds the other half, which is reviewing your own behaviour and the client's reactions so you can adjust next time.
Your notes then feed the follow-up. A recap that uses the prospect's own words and confirms the agreed next step is far easier to write from notes taken within the hour. The detail is in how to follow up after a sales meeting, and if trust was the thing missing from the room, start with building trust in the first meeting.
Frequently asked questions
What should you research about a prospect before a first meeting?
Cover the company's recent news, its customers and competitors, and any regulatory or market change heading its way. Then research each attendee: their role, how long they have been there, what they post about, and what they might personally gain or lose from a change. Finish with one specific question that shows you did the work.
What should a first sales meeting agenda include?
Three parts are enough: the prospect's current situation and plans, a brief account of how you have helped similar organisations, and an agreed next step. Send it a day ahead and invite them to add to it. Most of the time should go to the prospect talking, so keep your own section short and leave room for questions.
How do you prepare for likely objections in a first meeting?
List the two or three objections you hear most at this stage, such as being happy with a current supplier or wanting a price straight away. Write a one-line response and one follow-up question for each, then say them out loud. Aim to sound calm and curious rather than scripted, because a memorised rebuttal tends to sound defensive.
Should you bring a slide deck to a first sales meeting?
Bring a few slides or a one-page summary if they help the conversation, but do not let a deck run the meeting. A first meeting is mainly for understanding the prospect, and a long presentation leaves little room for that. If the slides would look the same for every client once you swapped the logo, leave them in your bag.