The first 48 hours of a consulting engagement set the tone for the next six months. A client who signs a proposal and then waits a week for the next step learns immediately that this engagement will move at the slowest reasonable pace. A client who signs and gets a confident, organized welcome the same day learns the opposite.
This is the operational checklist for getting a new consulting engagement from "proposal signed" to "first deliverable in motion" cleanly.
What to send in the first 24 hours
The day the proposal is signed, the client should receive — in one email or one portal notification — the following:
A welcome message that confirms what was just decided. Restate the engagement name, the scope, the timing, and the total fee. This is not redundant; it's the moment of low-friction confirmation before either party gets second thoughts.
The kickoff meeting invitation. Within five business days, ideally. A meeting on the calendar within a week of signing converts "I bought consulting" into "consulting starts Monday" emotionally.
The first invoice (if applicable). If your engagement letter specifies a deposit on signing, send the invoice the same day. Don't wait. Letting a deposit invoice sit a week after signing trains the client that your billing is informal.
A portal access link. The client should have a single URL that opens to their engagement — deliverables, messages, invoices, calendar, in one place. If the client has to bookmark three tools to find their work with you, the engagement experience is already fragmented.
A pre-kickoff prep request. Two or three specific items you need from them before the kickoff meeting (the org chart, the current state of X, three documents). This sets the expectation that the engagement is collaborative, not a service the client passively receives.
The kickoff meeting structure
A consulting kickoff meeting should run 60–90 minutes and produce three outputs: shared understanding of the goal, agreement on the working cadence, and clarity on the immediate next steps.
A working agenda:
Reintroduction (5 min). Even if you've been in 8 sales calls together, formally restart. Who is on your side, who is on theirs, what each person's role is in this engagement specifically.
The "what good looks like" conversation (15 min). Ask the client to describe, in their own words, what success looks like at the end of the engagement. Then describe it back. Get to written alignment in the meeting.
The constraints conversation (15 min). What can't change. Budgets you can't touch, vendors you can't replace, decisions already made that you're working around. Constraints surfaced in the kickoff are negotiable; constraints discovered in week 6 are conflicts.
The cadence agreement (10 min). How often do you meet? Who attends? How are decisions made between meetings? Who has approval authority on the client side? This is the most overlooked section of every kickoff meeting.
The communication channels conversation (5 min). Email for what? Portal for what? Phone for what? Default expectations save weeks of friction.
Immediate next steps (10 min). Three to five specific actions, each with an owner and a due date. Both sides leave with concrete commitments.
Document the kickoup decisions in writing within 24 hours. The meeting was the alignment moment; the document is the artifact.
The operational setup that should happen the same week
While the relational work is happening — kickoff meeting, prep conversations, expectations setting — there's a parallel operational setup that should be completed in the first week:
Engagement record created. Whatever tool you use, the engagement should exist as a discrete object: name, start date, scope, fee, status, owner.
Deliverables defined as records. Every promised deliverable should be a real thing in your system, with a target date, an owner, and a status. Don't leave them in the engagement letter PDF; promote them to first-class records so they can be tracked.
Milestones defined. If your engagement has 3–5 distinct phases, set them up as milestones with target dates. Milestones are the most useful unit for "where are we" status conversations.
Folder structure for the engagement. Whatever your document management approach — a portal, a Drive folder, a Notion workspace — the structure should exist before the first document needs to live somewhere.
Recurring meeting on the calendar. Whatever cadence you agreed to in kickoff, the meeting should be on both calendars before kickoff ends. Calendaring decisions that don't happen in the meeting tend not to happen at all.
The first 30 days
The first month of a consulting engagement is when the client decides whether they got what they thought they paid for. Two practices increase the probability of "yes":
A 30-day check-in built into the engagement letter. A scheduled conversation, separate from the working cadence, to assess "is this working." It's much easier to have this conversation if it's pre-scheduled than to schedule it because something is wrong.
A visible status indicator the client can see anytime. Whether it's a status dashboard, a weekly written update, or a real-time engagement view in the portal — the client should never have to ask "where are we?" The answer should be one click away.
The thing nobody tells you about onboarding
The biggest predictor of an engagement that runs smoothly is not the kickoff meeting or the engagement letter. It's whether the client felt the same level of organization in week one that they felt in the sales conversation. Sales calls are usually polished; week one of an engagement is often improvised. The clients who feel the gap notice — and they remember.
The onboarding checklist isn't a checklist; it's a system for closing that gap.
Ready to systematize your consulting onboarding so it runs the same way every time? Start your free trial and see how ConsultBase keeps engagements, deliverables, and milestones in one organized record from day one.