Expectation Setting

Expectation setting is the opening move on the quick start call. Before you touch a single setting, share a screen, or ask for a login, you lay out what is about to happen: the timeline, who is responsible for what, and exactly what the client should expect over the next few weeks. This is not a formality. It is the foundation of a relationship that either runs smoothly or falls apart within the first 30 days.

Why This Matters

Clients who do not know what to expect fill the gap with assumptions. They assume the website will be done in three days. They assume you will post on their social media every day. They assume they can call you at 9pm on a Saturday. When those assumptions collide with reality, you get frustration, refund requests, and bad reviews. None of those outcomes are the client’s fault. They are yours, because you did not set the frame.

The first five minutes of the quick start call determine the dynamic for the entire engagement. If you jump straight into tech setup, you are implicitly telling the client that their role is to sit back and watch. Then when you need their login credentials, their brand assets, or their onboarding form returned, you are chasing someone who was never told they had homework. The power dynamic shifts from expert-client to vendor-customer, and that shift is nearly impossible to reverse.

Agencies that set expectations well have dramatically lower churn. The client knows the build takes two weeks, not two days. They know the onboarding form is their responsibility and that it gates the timeline. They know that training happens after the build, not during. When there is no ambiguity, there are no arguments.

How to Think About It

Think of expectation setting as a verbal contract. You are not reading terms of service. You are having a direct conversation about how this works. Start with the timeline: “Here is what the next two weeks look like.” Walk through the phases. Quick start call today, onboarding form due back within 48 hours, build phase, training sessions, launch. Give them a clear picture of the path.

Then cover roles. Be specific about what you handle and what they handle. You build the automations. They provide the content for the onboarding form. You configure the phone number. They authenticate their Google and social accounts. The more concrete you are, the less room there is for misunderstanding.

Finally, set communication norms. Tell them where to reach you and how fast to expect a response. If you use a Slack channel, say so. If you respond within 24 hours on business days, say that. If you do not take calls without appointments, say that too. Clients respect boundaries when they are stated clearly upfront. They resent them when they discover them by accident.

Common Mistakes

Skipping it because the client seems eager. Some clients come in hot. They want to get started, they are excited, and they want to see the platform right now. It is tempting to match their energy and jump into the setup. Do not. The eager clients are actually the most important ones to set expectations with, because their enthusiasm will curdle into impatience if the build does not match their imagined timeline.

Being vague about the timeline. Saying “a couple of weeks” is not setting expectations. Give specific milestones. “You will receive the onboarding form today. When you return it, we start the build. The build takes 7 to 10 business days. Training is scheduled after the build is complete.” Precision builds confidence.

Not explaining the onboarding form’s role. The onboarding form is the single biggest bottleneck in any agency’s process. If the client does not understand that their form submission starts the build clock, they will sit on it for two weeks and then wonder why nothing has been done. Make this crystal clear.

Letting the client dictate the process. Some clients will try to rearrange the order of operations. “Can we just do the website first?” “Can you skip the automations and just set up the calendar?” Your process exists for a reason. Explain that the sequence is intentional and that skipping steps creates problems downstream.

Failing to document what was said. Verbal expectations evaporate. Send a follow-up email or message after the call that recaps the timeline, responsibilities, and next steps. This is not about being legalistic. It is about giving both sides a reference point when questions come up later.

Tools Involved

Expectation setting itself does not require specific software, but the artifacts that support it do. Your onboarding form should be built in GHL Forms or a dedicated survey tool. Timeline tracking can live in your pipeline so you can see where every client sits in the process. Follow-up messages after the call should be automated through workflows to ensure nothing falls through the cracks. If you use Conversation AI for client communication, make sure the client knows which messages come from AI and which come from a human.

Where This Fits

Expectation setting is the first action on the quick start call, immediately after the sub-account has been provisioned (SAP). It happens before any technical setup: before Sub-Account Access, before Mobile App, before connections. Everything on the quick start call flows from the frame you set here. The Onboarding Form Preview at the end of the call reinforces the expectations you established at the beginning.

Common Questions

How long should expectation setting take on the call? Five to seven minutes. You are not giving a speech. You are walking through a clear, structured overview. If you have a visual timeline or a shared document, it goes even faster. The key is being direct and specific, not comprehensive.

What if the client pushes back on the timeline? Hold the line. If they want things faster, explain that rushing the build leads to errors and rework that actually takes longer. Your timeline exists because you have done this before and you know what works. If they cannot accept the timeline, that is a qualification red flag, and you may want to reconsider the engagement.

Should I send expectations in writing before the call? Some agencies do this in the welcome email. That is fine as a preview, but do not skip the verbal version. People skim emails. They do not skim a direct conversation. Set expectations live, then reinforce them in writing after the call.