B2B Client Onboarding: Start a Service Project Clearly

An accepted quote confirms a commercial agreement. It does not guarantee that content is available, that the right person can make decisions or that the necessary tools are accessible. The kickoff turns that agreement into work you can execute. For a small agency or an independent service provider, this means getting enough clarity to produce a useful first version, without waiting for a perfect project file or proceeding on hidden assumptions.

Start with a sentence describing the expected outcome of the first milestone. “Improve our communication” remains too vague. “Get the structure of three service pages approved before writing the copy” lets you prepare the work and check its acceptance. This milestone should depend mainly on your service. A sales figure, a Google ranking or a third party's decision does not become controllable simply because it appears in a presentation.

Distinguish three dates: the administrative start of the relationship, the earliest feasible start of production and the expected first submission. They may coincide, but they do not have to. If an essential input is missing, explain what remains possible and what must wait. Do not turn a preferred date into an implied commitment. Confirm the consequences with the client under the applicable contract.

This method concerns delivery after the sale. Sales handoff and its CRM context address a related question: passing on what has been learned and promised accurately. Here, the objective is different: deciding together how the work starts and how it will be approved.

The kickoff brief is neither a second quote nor a set of rules imposed after signing. It makes the agreement usable in everyday work. If it reveals a contradiction with the contract, do not quietly choose the version that suits you: raise the issue and have the appropriate people confirm the adjustment. For a legal question, consult a qualified professional rather than relying on an improvised template.

Prepare a brief with eight headings: first milestone objective, included deliverables, exclusions, inputs expected from the client, responsible people, decisions to make, approval conditions and the next meeting. Add the reference and version of the contractual document, along with the location of the latest approved brief. Readers should be able to distinguish a proposal, a confirmed decision and an open question without reconstructing ten conversations.

The France Num resource on website specifications, consulted on November 1, 2026, highlights the value of documenting objectives, needs and constraints. For an engagement that has already been signed, retain only the information needed to get started. A small copywriting assignment does not need the technical documentation required for a complete website redesign.

Also write down two or three specific exclusions. For three service pages, translation, a new visual identity or a website migration may be outside the scope. A clear exclusion is not an invitation to reject every request. It helps you recognize a change, estimate its effects and obtain a decision before committing additional time.

An available contact does not always have approval authority. Ask who approves the first deliverable, who supplies information and who can resolve a contradiction. In a very small business, one person may hold all three roles. At a small client agency, several specialists may contribute, but final approval scattered across every participant remains difficult to interpret.

For each important decision, record a primary decision-maker and a backup where that is realistic. Specify the scope of the decision too. The marketing manager may approve the tone while a business owner confirms commercial claims. Do not assume either can commit the other. If their feedback conflicts, request a consolidated position rather than producing two incompatible versions without a decision.

Agree on one place for feedback and a channel for urgent issues. For example, detailed comments stay in the working document, while a short message flags a decision that is blocking progress. This is a proposed way of organizing the work, not a universal requirement. It should remain compatible with the client's habits and accessibility needs.

The hidden cost often comes from the number of approval routes, not just the number of people. Verbal feedback, an attached file and a direct edit may express three different states of the same sentence. Designate a reference version and record decisions made elsewhere. The note can remain very short: the issue discussed, the choice made, the responsible person and the consequence for the next step.

A list of twenty documents may feel reassuring, but it can slow the client down without reducing your uncertainty. For every request, ask two questions: what decision will this document help you make, and do you need that answer before the first milestone? If you cannot answer, remove the request or postpone it until an appropriate stage.

Classify inputs into three categories. Essential inputs block a specific deliverable, such as the approved characteristics of a service you need to describe. Useful inputs improve the work, such as examples of wording the client likes. Optional inputs enrich the context without determining whether you can start. State this classification in your request, together with the preferred format and the person responsible for supplying it.

Ask for a usable example rather than an abstract concept. “Send us your positioning” can be confusing; “describe two situations in which clients call you and what you do next” invites a practical answer. Do not impose a new tool when a simple document meets the need. Offer a short assisted information-gathering session when the client is not accustomed to writing things down.

Create an inventory of materials received: name, version, date, owner and intended use. An old logo is not necessarily the approved logo; a testimonial that has been forwarded is not automatically cleared for publication. Ask for confirmation about rights and sensitive material. You should not infer permission to use a photograph or client reference merely because it appears in a shared folder.

Finally, close the initial collection stage. Acknowledge the useful materials, list only what is still missing and explain what can start. Without this summary, the client may believe their submission is sufficient while you are still waiting for something essential.

Never include a password request in a kickoff form. Ask the client to use the invitations and roles provided by their tools. Identify the people who need access and the functions they need. A copywriter does not automatically need to manage billing, users or website infrastructure.

The CNIL recommends securing exchanges with external parties, including protecting transfers and controlling recipients. Apply that principle when collecting information: avoid public links containing confidential material, limit access to actual needs and plan for its removal. The convenience of an email attachment is not enough to establish that an exchange is appropriate.

If the engagement involves processing personal data on the client's behalf, clarify roles and obligations before that processing begins. The CNIL guidance on processors, checked on November 1, 2026, explains the need for an appropriate contractual framework. A simple kickoff file does not replace that framework.

Test access without changing the live environment. Check that the designated person can view the intended workspace and identify what they cannot do. Record “invitation sent,” “access confirmed” or “access missing,” rather than simply “done.” Plan the end of the engagement too: who removes permissions, which materials will be handed over and what must be deleted or retained under the applicable agreements.

Send the preparatory brief before the meeting, including the questions that remain open. The session should not be used to read an unfamiliar document aloud. Suggest a short agenda: objective, first deliverable, dependencies, approval and next action. Leave room for the client's concerns, particularly those that did not emerge in the sales discussions.

Start by asking participants to restate the expected outcome. A disagreement about “three pages” can conceal an important difference: the client expects published pages, while the service includes copy to be added to the website. Resolve that difference before discussing colors, headings or tools. Being precise about the outcome avoids creating the appearance of agreement around two different projects.

For each open issue, seek a decision or an explicit next step. “We will see” should become, for example, “the client checks which photographs are available before the layout is prepared.” If an answer is missing, identify who will supply it and what depends on it. Do not force an immediate decision when the appropriate person is absent.

Finish by reviewing both sides' commitments. Then send a record limited to decisions, open issues and any changes. Request confirmation of important points through your agreed process. Silence should not become an automatic approval rule invented after the event. If there is a disagreement, correct the shared understanding before multiplying versions of the deliverable.

Copy the following grid into your kickoff document. It examines the first milestone, rather than certifying the entire engagement. Replace the examples with your own deliverables and retain accessible evidence for every row.

Then assign one of three states: ready, partial start or waiting. “Ready” means the inputs for the first milestone are sufficient. “Partial start” means a clearly isolated work package can proceed without making other decisions irreversible. “Waiting” means an essential dependency prevents useful production. None of these states is a punishment for the client.

The distinction matters for cash flow as well as the relationship. Working for free on a risky assumption to appear responsive does not remove the dependency. Conversely, blocking the entire project over a photograph intended for a later phase may be unnecessary. Explain your choice in terms of the work that is possible, not a general impression that the client is “organized” or “difficult.”

Before announcing a date, compare this start with your agency capacity plan. An engagement that is ready on the client's side may not have an available slot on the provider's side. This check remains separate from the kickoff brief: one concerns your capacity, while the other concerns the operational ability to start the agreed work package.

Consider an entirely fictional example, with no observed client results. An independent copywriter must write three service pages for a professional maintenance business. The quote covers the copy and one consolidated revision round, not its integration into the website. The client wants to show an initial version to their team before a business meeting.

The brief describes the first milestone: approve the outline of the three pages and the information they should contain. The business owner approves claims about the services, while a coordinator gathers the documents. The writer asks for the list of services actually provided, the areas covered and an example of a frequent request. She asks for neither the entire CRM nor the contact details of end clients.

Two service descriptions are confirmed. The third contains an availability promise that nobody can substantiate. The grid leads to a partial start: prepare the common structure and the two documented pages, leaving the disputed promise out of the copy. The question is assigned to the business owner. The date for the third text remains to be confirmed, without silently delaying the entire project or publishing an uncertain claim.

During the meeting, the client also requests an English version. The writer acknowledges a legitimate need that falls outside the agreed scope. She offers to price this option separately and explain its effect on the schedule. She neither adds it for free out of habit nor treats the request as wrongdoing.

This example demonstrates no quantified time saving. It shows an observable decision: authorized work is separated from missing information and new requests. That separation is what you can reproduce, even for a very different engagement.

A well-prepared kickoff does not eliminate changes. It makes them recognizable. When a request arrives, classify it: necessary clarification, correction of an error, modification to the agreed deliverable or an additional service. These categories must be considered alongside your contract; they are not a way to charge arbitrarily for every comment.

Respond by describing the concrete effect. “Adding a fourth page requires new information gathering and an additional approval” is more helpful than “that is not included.” Offer a choice: keep the scope, replace an element where appropriate, or agree on an extension. Confirm the effects on price, stages and dates before carrying out work that requires a new agreement.

If the client does not respond, restate the decision needed and what remains blocked. Avoid follow-ups that merely ask for “an update.” A useful message identifies the relevant document, the precise question and the step that can follow. Do not invent a penalty, suspension or tacit acceptance rule that does not appear in the applicable agreements.

Finally, maintain a lightweight change log. Four columns may be enough: request, decision, effect and confirmation. This log also protects the client against the provider's omissions. It distinguishes an accepted change from an idea merely mentioned in conversation. A good relationship does not require heavy documentation of everything; it requires important decisions to be retrievable.

The kickoff ends when the first work can proceed within a shared framework. It should not become a parallel project of forms and meetings. Archive the confirmed version of the brief, keep remaining dependencies visible and move into production. At the first submission, check that the approval process actually works and adjust it with the client if necessary.

After the first milestone, record the causes of back-and-forth: missing information, the wrong contact, a different understanding of scope, untested access or a poorly described deliverable. Separate issues involving your preparation from those caused by a new event. The objective is not to rank clients, but to improve a request or a decision in your next kickoff.

Do not measure quality by the number of completed fields. Instead, observe whether the first submission meets the agreed need, feedback arrives in the right place and someone can actually decide. Across a few engagements, these observations remain qualitative: they do not establish a universal productivity gain.

To preserve continuity before signing, a CRM with next actions and commercial context can help prevent qualification information from being lost. The kickoff brief nevertheless has its own role: organizing delivery with the client. Do not assume a prospecting tool replaces your contract, document workspace or project management. Start with the tools already available and add software only when a concrete difficulty justifies it.