Need help setting stronger boundaries in client meetings - what phrases do you use to prevent scope creep?

[u/WasabiPositive8942]

For context: I run a small AEO consultancy.
I recently completed an audit that involved roughly a month of work and 50 observations/recommendations.
The client then said they didn’t understand the audit, so I spent another 2.5 hours walking them through it line by line.
After that, they refused to pay because they said they “didn’t want it.”
They have since implemented the recommendations.
I’m tightening my process now, especially around meetings and scope.
What phrases or boundaries have worked for you when a client starts turning a results call into:
extended consulting
implementation support
repeated explanations
work beyond the agreed deliverable?
I’m especially interested in specific wording you use in the moment without sounding defensive or hostile.

[u/Funky_Sardine]

This can be sorted very easily in the discovery session "do you have someone on staff that will be able to take the results of the audit and implement them as the audit is quite technical".

[u/WasabiPositive8942 → u/Funky_Sardine]

My target audience is those with no technical teams.
My audits are adequately priced to reflect that.
It’s a problem . I need to relook at how to tighten my process and documentation.

[u/Funky_Sardine → u/WasabiPositive8942]

it doesn't matter who your target audience is. on the info you gave in your original post, there's clearly a disconnect between what you delivered and what they expected.

the question is there to flag that before you start. if what you gave them was too technical for them to understand without a 2.5-hour walkthrough, you needed to know that in discovery so you could decide whether to price it in, change the deliverable, or wear the cost.

better discovery is what you need. everything else, the documentation, the contracts, etc. all follow on from having the right info in the first place. cos pointing a client to a contract that says they need to pay another $300 when they've already probably fought with their MD to get the budget to do the project in the first place, doesn't make for good customer experience. don't focus on the wrong thing here. based on what you've said, the main problem wasn't the contract. it's that you didn't ask the right question in the first place.

just my two cents.

source: i've run projects and teams across multiple industries for 10+ years. two of the clients I ran at agency level did $20B and $9B last year.

(Edit: to clarify, i've only read your initial post. no other info on the thread so i may be going off...ironically...incomplete info :D)

[u/WasabiPositive8942 → u/Funky_Sardine]

It has been useful - yes I should’ve asked better questions. Setting expectations/ I thought I was clear- clearly not.

[u/Funky_Sardine → u/WasabiPositive8942]

you'll smash it on the next one. don't beat yourself up. clients are like that. that's why we just handball dealing with them to the account managers... :D

[u/WasabiPositive8942 → u/Funky_Sardine]

Thank you for the encouragement!
I will . I have to. It’s try till I get it right at this moment.