Okay — thanks everyone for making time. I know you're all busy, so I'll, I'll keep this focused. What I want to do today is walk you through where we are on phase one, and then share the plan for the sales team adoption. Sound good?
"I'll keep this focused" reassures busy people you won't waste their time. "walk you through" = take you through step by step (common presenting phrase). "Sound good?" checks buy-in before starting. A good presenter sets out the structure first.
Great, yes. I've got the exec team asking me for an update, so — good timing.
Sarah signals pressure from above: "the exec team asking me for an update". Whatever the team says, she repeats it upstairs. She means "make me look good to my bosses". Presenters should hear that and be clear and credible.
Perfect. So — I'll present, but jump in any time with questions. Don't wait for the end.
"jump in any time... don't wait for the end" signals confidence: "I'm comfortable being questioned". It keeps the audience engaged — the opposite of a nervous presenter who holds all questions to the end.
So, phase one. The headline is: we're on track for Q3. The three systems feeding the Q3 reporting are mapped, mostly clean, and the build is, um, it's about sixty percent done.
"the headline is..." = the single most important takeaway → give the main message first, details after. Busy stakeholders want the conclusion up front, not a slow build-up.
Priya, do you want to say a word on the technical side?
Sure. So the architecture's holding up well. We did hit one surprise — the sales data had a lot of duplicate records. Same customer entered three, four times, slightly different each time. But we, we built a cleanup step for it. Nothing that changes the Q3 picture.
The detail is CONCRETE but plain: "duplicate records — same customer entered three, four times". Anyone understands it — no jargon. Priya raises the problem, then neutralises it: "we built a cleanup step... nothing that changes the Q3 picture". Mention issues, but always land on the reassurance.
Yeah, and honestly, from our side — the business is pretty happy with what they've seen so far.
Tom (client side) backing the story is powerful — not just the vendor saying it's going well. When the client's own side confirms good news, it lands far more credibly with the senior stakeholder.
Quick one on those duplicates — is that going to affect the numbers? If the same customer's in there four times, are the reports going to be wrong?
Sarah asks a smart, non-technical question that gets to the real risk: do the duplicates make the reports wrong? Stakeholders don't need to be technical to ask dangerous questions. She frames it in plain business terms, and the team must answer in the same plain terms.
Good question — no, and here's why. The cleanup step runs before any reporting. It matches the duplicates up and merges them into one record. So by the time the numbers are calculated, each customer's counted once. We, we actually tested that on last quarter's data and it matched.
Priya explains a technical process WITHOUT jargon: "cleanup runs first → matches duplicates → merges → counted once". Just cause and effect. Then proof: "we tested it on last quarter's data and it matched". When answering a technical question to a non-technical audience, explain the logic in plain steps and back it with evidence. Jargon here would lose the room.
Okay, good. That's, that's the kind of thing the exec team will ask me.
Sarah reveals why she asked: she needs it for her own bosses. Answer a stakeholder's question clearly and you're arming them for their next conversation. Good presenters give answers the stakeholder can repeat.
Can I add something — on the sixty percent. It's, it's true, but the last forty is not evenly spread. The reporting layer is the tricky part, and that's, that's mostly still ahead of us. I just want to be honest about that.
Marco gently complicates David's clean "sixty percent" with a real caveat: the hard part is still ahead. "I just want to be honest about that" — flagging a risk within your own team's story, in front of the client, takes maturity. It's more credible than pretending everything's smooth. But note: it's said calmly, as information, not alarm.
Right — so should I be worried about that? Is sixty percent actually more like, I don't know, forty in terms of effort?
Sarah immediately picks up Marco's caveat and pushes: is the real progress worse than the number suggests? This is what honesty invites — a sharper question. But it's better to face it now than have it blow up later. The team has to answer without either panicking or dismissing her.
It's a fair challenge. I'd say — the sixty percent is real, but Marco's right that the remaining work is the harder part. That's exactly why we built in a buffer before Q3. We're, we're not counting on everything going perfectly. So: on track, but with eyes open. Not complacent.
David does something subtle and strong: he agrees with his own teammate AND with the client's worry, without collapsing his position. "the sixty percent is real, but... the remaining work is harder" — both true. "we built in a buffer... eyes open, not complacent" — reassures without over-promising. You can concede a point and still hold your overall position. That's more convincing than either denying the risk or caving to it.
Okay. "On track with eyes open." I can work with that.
Sarah repeats David's phrase back — a sign it landed. "I can work with that" (callback to Pack 1's language) = an honest, slightly qualified answer she can accept and repeat upstairs. Honesty framed well beats false confidence.
Okay — so the second part. The sales team, the legacy CRM problem. Rather than force a switch, we've landed on a phased approach. Let me walk you through it.
"the second part" / "let me walk you through it" — clear signposting tells the audience you're moving on. Always mark transitions, or people get lost. "rather than X, we've landed on Y" frames the decision cleanly.
So first, we talk to the sales team directly — understand why they don't trust the new system. Then we find a champion inside sales, run peer-led training built around their actual concerns, and switch off the old system on a clear, announced date.
David lists the plan as ordered steps ("first... then... and..."). A plan as a sequence is easy to follow and sounds thought-through. The ordering itself signals competence.
Can I jump in on the champion idea? I like it, but — what if we can't find one? What if nobody in sales actually wants the new system?
Tom raises the scenario where the plan breaks: what if there's no willing champion? "I like it, but — what if..." is the polite way to stress-test a plan. Every good plan gets this question. The presenter must have thought about failure modes, not just the happy path.
Honestly, that's the risk I worry about most. If there's genuinely no one, then the whole peer-led idea falls down. But — that's actually why we talk to sales first. Those conversations tell us fast whether a champion exists. If they don't, we, we rethink before we've committed to anything.
David doesn't pretend the risk isn't real: "that's the risk I worry about most" — owning it builds trust. Then he shows the plan already handles it: the early sales conversations are a cheap test. "we rethink before we've committed" = we'll fail cheap, not expensive. Owning your biggest risk, then showing how you've de-risked it, is far stronger than pretending there's no risk.
Okay. Can I stop you there? This all sounds sensible, but it also takes time. Does this push the sales team onto the new system before or after Q3? I need a straight answer.
"Can I stop you there?" signals a challenge. Sarah cuts through to what she cares about: timing vs Q3. "I need a straight answer" = no waffle, a clear yes/no. This is pressure — weak presenters ramble here. (The "hmm" is in the audio, not the clean text.)
That's a fair question. Let me be straight — the sales adoption is not on the Q3 critical path. Q3 reporting works whether or not sales have fully switched. So the honest answer is: after Q3, and deliberately so.
Structure: (1) "that's a fair question" — acknowledge, buy a second. (2) "let me be straight" — meet her demand for directness. (3) a clear answer, no rambling. The model: acknowledge → answer directly → give the reason. "That's a fair question" buys you a moment to think.
Deliberately? Explain that.
A two-word challenge: "Explain that." Senior people test whether your answer holds up. A follow-up isn't hostility, it's due diligence. Stay calm and expand.
Sure. If we rush sales onto the system before Q3, while we're still fixing bugs, and they hit problems — we lose their trust for good. We'd rather get Q3 solid first, then move them onto something that already works. Slower, but much safer.
David gives the logic: rushing = bugs = lost trust. "we'd rather X, then Y" frames it as a deliberate trade-off, not a delay. "slower but much safer" names the trade-off honestly. Good answers give the reasoning, so the decision sounds chosen, not accidental.
Okay. That actually makes sense. Thank you.
"that actually makes sense" — handle a hard question with a calm, reasoned answer and you build credibility. The pressure moment became a trust-building moment.
One more. What's this going to cost? The adoption piece — training, the champion, all of it. Do we have a number?
Here comes the question the team hasn't fully worked out — cost. Every presenter faces a question they can't fully answer. The next lines show the RIGHT way, versus bluffing a number (the classic mistake).
Honestly — not a precise one yet. I don't want to give you a number I'd have to walk back later. What I can tell you is it's small relative to the build — mostly internal time, not new spend. Can I come back to you with a proper figure by end of week?
The most valuable moment in the pack. No bluff, no panic. Structure: (1) honest admission. (2) reason it's the right call: "a number I'd have to walk back" — turns the gap into professionalism. (3) give what you DO know. (4) commit to a follow-up with a date. "I don't know yet, but I'll get you an answer by X" is a STRENGTH. Bluffing destroys trust.
Yeah, that's fine. I'd rather have the right number than a fast one.
"I'd rather have the right number than a fast one" — senior people respect "I'll find out" far more than a confident guess that turns out wrong.
And I can help with that number. A lot of it touches the data side, so — I've got a good sense of the effort involved.
Marco offers to help close the gap. The team backing each other up shows a united, capable front, and quietly reassures the client the follow-up will happen.
Okay — let me pull it together. Phase one's on track for Q3, sixty percent built, harder part still ahead but buffered, and the duplicate issue is handled. The sales adoption is a deliberate, phased plan that lands after Q3, on purpose. And I'll get you a cost figure by Friday.
David recaps the key points — including the honest caveat (harder part ahead) and the promised follow-up. A strong close mirrors the strong open: tell them what you told them. Restating commitments ("cost figure by Friday") puts them on the record.
That's really helpful. Honestly, this is exactly what I needed to take upstairs. Good work, all of you.
"exactly what I needed to take upstairs" — recall her opening worry (the exec team). She's now equipped. A presentation succeeds when the stakeholder can confidently repeat your story to THEIR bosses. "take upstairs" callbacks to Pack 1.
Thank you — really appreciate the questions, genuinely. They make the plan stronger. We'll get that number over to you and, uh, speak Friday.
David thanks Sarah for the tough questions: "they make the plan stronger". A confident, mature close — treating challenge as helpful, not hostile. A pro welcomes scrutiny; it makes the next hard question easier to receive.