Spend less time repeating your company introduction and more time resolving the dependencies between your team and the client.
Bring the agreed scope
Start from the accepted version, including deliverables, fees, dates and any conditions. Highlight anything that changed during the sales discussion.
Asana’s guidance on client-facing kickoffs includes aligning scope, roles and communication. For a small consulting project, the most useful output is often a short dependency plan.
Complete the plan together
Fictional assignment: a service consultancy is reviewing a supplier-onboarding process.
| Input or decision | Owner | Needed by | What it enables |
|---|---|---|---|
| Current process documents | Client operations lead | 3 November | Initial process review |
| Two representative files | Client file owner | 3 November | Comparison with written process |
| Interview availability | Client coordinator | 5 November | Four staff interviews |
| Draft review | Client sponsor | 12 November | Corrections before final recommendation |
| Final decision meeting | Sponsor and process owner | 16 November | Agree implementation priorities |
Dates are illustrative. Use dates both sides can meet, taking holidays and availability into account.
The table should name an actual owner rather than “the client.” It should also show why each input matters. That makes a late item easier to discuss.
Agree how decisions will be made
Ask where questions should go and who can approve a change. Choose a practical communication channel and an expected review process.
Do not create several competing places for feedback. If comments arrive by email, document annotation and chat, agree who will consolidate them into one response.
If a reviewer is unavailable, identify the substitute or adjust the schedule now. A delivery date built on an absent approver is already fragile.
Confirm the first working step
A good kickoff ends with something specific: “We will review the two sample files once they arrive on Tuesday, then send the interview questions for your factual check.”
A vague “we’ll get started” leaves both sides guessing whether the next move belongs to them.
Send a short confirmation
Record the agreed inputs, owners, dates, first output and unresolved items. Do not quietly add a new deliverable in the meeting notes. New work needs a clear scope decision.
If an input is late, refer to this plan and discuss the effect before making a new promise. The point is coordination, not blame.
The kickoff is complete when the people doing the work know what to do next and what they are waiting for. That is a better foundation for delivery than a polished slide deck that leaves the same dependencies unresolved.