Client Onboarding

Client Onboarding Prompts for Freelance Developers

Most freelance projects don't fail at the code — they fail at the handoff. Here's how to onboard clients so clearly that scope creep, miscommunication, and last-minute chaos stop eating your margins.

I used to think scope creep was the client's fault. Then I realized I was the common factor. Not because I'm a bad developer — because I was terrible at the messy middle: setting expectations, confirming what's included, and communicating progress without babysitting.

This is the client onboarding system I now use, built from the same prompts in the Freelance Prompt Kit.

1. The kickoff message that kills ambiguity

Most freelance projects start with a vague message like "I need a website." The problem isn't the client — it's that we jump to building without confirming. Here's the prompt I use to force clarity before any work begins:

You are an expert freelance developer. A new client just hired me for [PROJECT_TYPE]. Draft a 5-bullet kickoff message that: (1) restates the project in my own words, (2) lists exactly what's included (and explicitly what's NOT), (3) asks 3 specific questions that will prevent scope creep, (4) states the communication rhythm (how often, what tool), and (5) proposes a 30-min kickoff call. Keep it under 150 words. Tone: professional, confident, reassuring.

2. The "here's what you'll get" doc

The single biggest source of client frustration is not knowing what's happening. A short deliverables doc prevents 80% of "is it done yet?" messages:

I'm starting [PROJECT] for a client. Create a deliverables doc with: (1) exactly what they receive at the end (file formats, access details, documentation), (2) a timeline with 3 milestones, (3) what I need from them at each milestone (feedback, credentials, content), (4) a one-line revision policy (max 2 rounds, 48h each), and (5) what happens after launch (warranty period, handoff). Format as a clean bullet list.

3. The late-payment nudge

Chasing payments is a skill. A polite, firm nudge works better than awkward calls:

A client is [N] days late on a $[AMOUNT] invoice for [PROJECT]. Draft a 3-sentence email that: (1) assumes good intent (maybe they missed it), (2) links the invoice clearly, (3) states the next step gently (a 5% late fee after 30 days, or pausing work). No anger, no threats. Professional.

4. The project-close email that gets repeat business

Most freelancers disappear after delivery. A close email turns one-off work into referrals:

I just delivered [PROJECT] for a client. Draft a close email that: (1) confirms everything is delivered, (2) lists 3 things I enjoyed about the project (specific, genuine), (3) gives them one tip to get the most value from what I built, (4) mentions I'm available for future work, and (5) asks for one referral if they know anyone who'd benefit. Under 120 words.

Why this works

These four prompts cover the entire client lifecycle:

• Kickoff → kills ambiguity before it starts
• Deliverables doc → sets expectations so clear that scope creep has nothing to grab onto
• Payment nudge → protects income without burning bridges
• Close email → turns one client into a pipeline

Every prompt is plain text. No SaaS, no lock-in — paste into ChatGPT, Claude, or any LLM and customize for your client.