Freelance Project Kickoff Email: Scope Lock After They Said Yes

A freelance project kickoff email lands after they said yes—when the job is sold but the calendar is still empty because nobody named the first file, the shared folder, or the reply-all thread.

This page is Yes-Then-Kickoff. It is not proposal email + PDF (before yes). It is not contract vs invoice order (document sequence). It is not contracts and scope (the fence text). It is not deposit emails (payment chase copy).

Send four blocks: confirmed scope line, assets you need, timeline with first deliverable, and one channel rule. Then wait for the fence signature or deposit per your policy.

Not legal advice. Adjust for your niche and payment rules.

Table of contents

1. Yes-Then-Kickoff
2. The four blocks
3. Sample skeleton (customize names)
4. What kickoff is not
5. FAQ
6. Send kickoff within 24 hours of yes

Yes-Then-Kickoff

        YES-THEN-KICKOFF
  1. YES      → they accepted price + package (proposal done)
  2. LOCK     → one sentence restating the bought scope
  3. ASSETS   → list what you need before hour one
  4. DATE     → first internal milestone + client review window
  5. CHANNEL  → email vs Slack vs ticket—one primary thread

Kickoff is logistics, not persuasion. If you are still selling, you are in the proposal URL, not this one.

The four blocks

Block 1 — Scope lock. One sentence in their words. "You approved the four-page landing rewrite for the Sep 12 launch." If you cannot write that line, the yes was fuzzy—clarify before work.

Block 2 — Asset request. Bulleted list with deadlines. Brand PDF, logins, analytics view-only, legal disclaimer text—whatever your job actually needs. Missing assets is the main reason kickoff weeks vanish.

Block 3 — Timeline. First internal milestone ("outline by Thursday") plus first client touchpoint ("comment window Fri–Mon"). Not a Gantt chart—a date they can put on their calendar.

Block 4 — Channel rule. "Reply on this thread" or "Slack #project-name only." Multiple channels is how feedback disappears.

Optional fifth line: contract signature or deposit status—point to deposit emails for wording, not collection tone on day zero.

Sample skeleton (customize names)

Subject: Kickoff — [Project name] — assets + first draft date

Body outline:

1. Thanks + scope lock sentence.
2. "To start on [date], I need:" bullet list with due dates.
3. "First deliverable: [artifact] by [date]. Your review window: [dates]."
4. "Please keep updates on this email thread."
5. "Signed scope attached / deposit link below—work opens when [your rule]."

Replace every bracket with their product name. If a sentence works for any client, rewrite it.

What kickoff is not

• Not a second proposal — price was settled on the call.
• Not a contract rewrite — attach the fence; do not renegotiate scope in kickoff.
• Not onboarding SaaS — no portal tour unless they paid for one.
• Not a testimonial ask — that comes after delivery.

Platform clients: finish marketplace threads on Upwork or Fiverr before you use off-platform kickoff habits.

FAQ

When do you send a kickoff email?

After yes, before billable work—locks logistics.

Is this the proposal?

No. Proposal sells; kickoff runs.

Is this a contract?

No. Contracts own the fence text.

Before deposit clears?

Follow your rule; mention status plainly.

How long?

Four blocks, forwardable length.

Upwork messaging?

No. Platform bids stay on platform owners.

Not signed yet?

Do not start billable work; set sign-by date.

Where is the invoice?

After logistics/deposit per Fence-Then-Bill owner.

Send kickoff within 24 hours of yes

When a client says yes today, send kickoff tonight while the call is warm. Lock scope in one sentence, list assets with dates, name the first deliverable, pick one channel. Then open the contract or deposit path you already use—do not start hour one without the fence your policy requires.