Three months in, you are doing twice the work you quoted. The client is happy. You are not. And if you trace the problem back to where it started, you will almost always land in the same place: the first two weeks of the engagement.
Not the middle of the project. Not the moment she asked for the thing outside the original scope. The onboarding. That is where the conditions for scope creep were set, quietly, before either of you realized it.
Onboarding is where the relationship is architected
Most founders treat onboarding as administrative. Sign the contract. Send the welcome email. Schedule the kickoff call. Get to work. And because the work itself is good, the relationship starts well. But good relationships built on vague foundations are fragile. They feel fine until they do not.
Onboarding is not where paperwork happens. It is where the client forms her understanding of what this engagement is, what it is not, what to expect from you, what you expect from her, and what happens when either of those expectations is not met. If you do not define those things explicitly, she will define them herself. And she will define them generously, because she hired you and she is optimistic and she does not yet know where the edges are.
Vague onboarding creates vague expectations. Vague expectations create scope creep. Scope creep creates resentment. Resentment ends relationships. All of it starts in the first two weeks.
The four things onboarding must make explicit
What is included, in specific terms. Not "strategic support" or "ongoing guidance." What are the actual deliverables, the actual cadence, the actual output she will hold at the end of each month? The more specific you are here, the less room there is for her to fill in the blanks with things you did not intend to provide.
What is not included, and what happens when she asks for it. This is the part most founders skip because it feels confrontational to name what you will not do before you have even started. But naming it upfront is an act of professionalism, not defensiveness. "Requests outside this scope will be quoted as add-ons" is a single sentence that prevents every difficult conversation you might otherwise have at month three.
How she reaches you and how quickly you respond. If she does not know your response time, she will expect the fastest possible one. If she does not know your preferred channel, she will use all of them. Defining this at onboarding sets a communication standard that protects your time and gives her certainty, which is what she actually wants.
What success looks like at the end of the engagement. Ask her. Write it down. Make it specific enough that you can both point to it later and say whether you got there. This question alone changes the nature of the engagement because it forces alignment before the work begins instead of discovering misalignment after it ends.
The welcome kit is not a nicety. It is a structural document.
Everything above belongs in a written document the client receives before the kickoff call, not during it, not after it. Before. So she reads it. So she arrives at the kickoff with questions instead of assumptions. So the first conversation you have about the work is grounded in a shared understanding of what you agreed to.
That document does not need to be long. A single page with four sections is enough: what we are doing together, what is outside this engagement, how we communicate, and what we are aiming for. Formatted in plain language. Not legal language. The goal is clarity, not protection.
A client who is well-onboarded does not ask for things outside the scope because she already understands where the scope ends. You built that understanding. That is the work.
What to do if your current onboarding is a kickoff call and a contract
You are not alone. Most service founders land here because they built their onboarding around the deal, not around the relationship. The contract protects you legally. The onboarding process protects the relationship operationally. You need both.
Start by writing down what you wish every client understood in the first two weeks of working with you. Not what you hope they figure out. What you wish you could hand them on day one. That document is the beginning of your onboarding process. It does not need to be perfect. It needs to exist, so you can refine it over time instead of rebuilding it from nothing every time a client relationship gets difficult.
The clients who stay longest, who refer most often, and who expand their engagement rather than quietly exiting are almost always the clients who were well-onboarded. They knew what to expect. They got it. And when they needed more, they knew how to ask for it the right way because you told them how.