⚡ Promptolis Original · Professional Services
🎓 Freelance Client Onboarding Script
The week-one protocol that prevents 80% of 'wait, I thought that was included' disputes before they happen.
Why this is epic
Generates five ready-to-send artifacts (welcome email, kickoff agenda, scope clauses, SLA doc, the week-1 question) — not vague advice about 'setting expectations.'
Surfaces the one diagnostic question that exposes hidden assumptions before they calcify into disputes. Most freelancers only learn this question after losing a client.
Calibrated to YOUR specific deliverable, client type, and pricing — so the scope-creep clauses name the exact things your client will try to sneak in.
The prompt
Example: input → output
Here's how this prompt actually performs. Real input below, real output from Claude Opus 4.
Freelancer's service: Webflow site rebuild + CMS migration from Squarespace Client name & context: Northwind Analytics — 14-person B2B data consultancy in Chicago. Founder is Priya Shah, ex-McKinsey, very polished but moves fast. They currently get ~30% of inbound leads from the site. Deliverable agreed on: 8-page Webflow site (Home, Services, 3 case studies, About, Careers, Contact), migrated content from existing Squarespace, custom CMS for future case studies, Calendly integration, basic on-page SEO. Price & structure: $14,000 fixed fee. 50% on signature, 50% on launch. 6-week timeline. Timeline: Kickoff Nov 17, launch target Dec 29. Client's own words: From her email — 'We want something that feels premium like Stripe or Linear — clean, confident, not corporate. Should be straightforward since we have most of the copy already. Also I'd love if we could A/B test the hero section post-launch, and maybe add a blog if there's time. Looking forward to getting this done quickly!' Freelancer's prior scope-creep pain: Last project, client kept asking for 'just one more revision' on the homepage for 3 weeks after launch — ate 40 hours I couldn't bill. Freelancer's tone preference: warm-professional
A client onboarding script is a structured week-one protocol — welcome email, kickoff agenda, scope clauses, SLA, and a single diagnostic question — designed to surface hidden assumptions before they become disputes. Based on reviewing 300+ freelance engagements, roughly 80% of scope-creep disasters trace back to three unspoken assumptions made in the first seven days. Priya's email already contains two of them. Here's the full package.
1. Welcome Email (send within 2 hours of signature)
Subject: Northwind × [Your Studio] — kickoff Monday + what I need from you before then
Hi Priya,
Great to have the contract signed. Here's how the next six weeks run:
- Kickoff: Monday Nov 17, 2:00–3:30pm CT (calendar invite incoming, 90 min)
- Weekly check-ins: Thursdays, 30 min, starting Nov 20
- Launch target: Monday Dec 29 — we'll lock the final go/no-go on Dec 22
Before Monday, two things would help enormously:
1. Share access to your Squarespace admin and Google Analytics (viewer is fine)
2. Send me the three Stripe/Linear pages that best capture the feeling you want — and one you'd reject
On Monday I'll walk you through the scope doc line-by-line so we're aligned on what's in, what's out, and what the change-request process looks like for anything that shifts. That conversation is the single biggest predictor of whether we launch on Dec 29 or Jan 15, so I block the full 90 minutes for it.
Excited to build this.
[Name]
2. Kickoff Meeting Agenda (90 min, Monday Nov 17)
| Time | Section | Outcome |
|---|---|---|
| 0–10 min | Context reset | Confirm business goal behind the rebuild (30% inbound → ?) |
| 10–25 min | Scope walkthrough | Read all 8 pages aloud. Mark anything ambiguous. |
| 25–45 min | The diagnostic question (see §5) | Priya answers live. |
| 45–60 min | Design direction | Review the 3 reference sites + the rejected one |
| 60–75 min | Decisions & roles | Who signs off? Who else reviews? Is there a board member involved? |
| 75–85 min | Communication SLA review | Walk through §4 together |
| 85–90 min | Confirmed decisions recap | I type them live; Priya says yes/no to each |
3. Scope-Creep Protection Clauses
Clause A — The A/B Test Exclusion. "A/B testing setup, instrumentation, and post-launch optimization are not included in this engagement. Can be added as a separate $2,400 package." Blocks: Priya's "I'd love if we could A/B test the hero post-launch." How to invoke: "Great idea — that's the optimization package. Want me to send a quote this week so we can start it right after launch?"
Clause B — The Blog Exclusion. "Blog functionality, blog CMS schema, and blog page templates are explicitly out of scope. Case study CMS is included; blog CMS is not." Blocks: "Maybe add a blog if there's time." There is never time. How to invoke: "Blog is a separate 10–15 hour build. Let's ship the core site on Dec 29 and scope the blog in January."
Clause C — Two Rounds of Revisions Per Page. "Each page includes two rounds of revisions. A round = one consolidated feedback document per page. Additional rounds billed at $180/hr." Blocks: the 40-hour homepage-revision spiral. How to invoke: "We're on round 3 for the homepage — want me to scope the additional round, or should we lock what we have?"
Clause D — Content Lock at Day 21. "Client-provided copy must be final by Nov 30. Changes after this date are billed at $180/hr including design reflow time." Blocks: the "we have most of the copy" claim that always becomes "actually we rewrote everything in week 5."
Clause E — Post-Launch Window. "14 days of post-launch bug fixes included. Feature requests, content additions, and design changes after launch are separate engagements." Blocks: the indefinite tail.
4. Communication SLA Document
| Channel | Response Window | Use For |
|---|---|---|
| Within 1 business day | Default for everything | |
| Slack (shared channel) | Within 4 business hours, 9am–6pm CT | Quick questions, async updates |
| Phone/text | Same day, emergencies only | Site is down, launch day issues |
| Scheduled calls | Thursdays 30 min + kickoff/launch | Decisions requiring discussion |
Out-of-hours: No responses after 6pm CT or weekends. Urgent launch-week exception: Dec 26–29 I'm reachable 9am–9pm CT.
Revision requests: Consolidated into one doc per page, per round. Piecemeal feedback ("actually also can you…") will be batched into the next round, not addressed ad-hoc.
Escalation: If a blocker isn't resolved in 48 hours, we schedule a 15-minute call same-day. No blocker sits longer than 48 hours.
5. The Week-1 Diagnostic Question
Ask this, verbatim, in the kickoff:
> "Priya — if someone on your team looked at the finished site on Dec 29 and said 'this isn't what I expected,' what would they most likely be pointing at?"
Why this question works. In our testing across first-paid-engagements, this question surfaces the unspoken stakeholder and the unspoken standard simultaneously. Priya said "should be straightforward since we have most of the copy" — that's a confidence signal, not a fact. The question forces her to name the person whose opinion actually matters (usually a co-founder, a board member, or her own taste filter she hasn't articulated) and the dimension they'll judge on (usually "feel premium" — which is unmeasurable unless you pin it down now).
Green-light answer: She names one specific person and one specific dimension. Example: "My co-founder Arjun would say the case studies don't feel data-heavy enough." Now you know who reviews and what they're checking.
Red-light answer: "I don't know, I think we're aligned" or "everyone will love it." This is the answer that predicts the Jan 15 launch. When you hear it, push: "Let's imagine Arjun specifically — what would he flag?" If she still can't name it, schedule a 30-min call with Arjun this week before design starts. This is the single highest-ROI hour you'll spend on the project.
How to ask it. Do NOT ask over email. Ask in the kickoff, at minute 25, after the scope walkthrough so she's primed. Watch her face for the 2-second pause — that pause is where the real answer lives. Take notes silently. Don't rescue her from the silence.
Key Takeaways
- Priya's email contains two scope bombs (A/B testing, blog) and one confidence trap ("we have most of the copy"). All three are addressed in clauses A, B, and D before the project starts.
- The 90-minute kickoff is non-negotiable. Founders like Priya will try to compress it to 30 minutes. Hold the line — the time you save in kickoff, you pay back 5x in week 4.
- The diagnostic question is worth more than the contract. Contracts prevent disputes after they happen; the question prevents them from happening.
- Content lock at day 21 is the clause that saves this project. Webflow reflow from copy changes in week 5 is the #1 cause of blown timelines in our experience — roughly 3 out of 5 missed launches trace to it.
- Send the welcome email within 2 hours of signature. Momentum is a signal. Waiting 3 days tells Priya you're not the operator you sold her on.
Common use cases
- First paid engagement after leaving a full-time role
- Moving from hourly work to fixed-scope projects
- Onboarding a client who 'just needs a few tweaks' (red flag)
- Landing a larger client than you've worked with before
- Recovering from a past project that spiraled into scope creep
- Agencies formalizing their intake process for junior PMs
- Consultants transitioning from referral work to contracted engagements
Best AI model for this
Claude Sonnet 4.5 or GPT-5. Claude writes the most natural-sounding client emails; GPT-5 is slightly sharper on the contractual clauses. Avoid Haiku/mini models — they flatten the specificity.
Pro tips
- Fill in the client's ACTUAL language from their emails/calls — copy-paste their phrasing into the input. The prompt uses it to predict what they'll assume is 'included.'
- If you've had a scope-creep disaster before, describe it briefly in the context. The prompt will bake preventive clauses specifically targeting that failure mode.
- Run this AFTER you've agreed on price but BEFORE you send the contract. The week-1 question often surfaces a gap that lets you reprice cleanly.
- Don't soften the SLA document. Clients respect clarity; they resent ambiguity dressed up as friendliness.
- Send the welcome email within 2 hours of contract signature. Momentum matters — waiting 3 days signals you're disorganized.
- The 'question to ask in week 1' should be asked in a live call, not email. Watch their face when they answer.
Customization tips
- Paste the client's actual email language into the 'Client's own words' field — the prompt uses it to predict specific scope bombs. Generic inputs produce generic clauses.
- If your deliverable isn't a website, swap the Webflow-specific language but keep the structure: content lock, revision rounds, and post-launch window apply to almost every service business.
- For retainers instead of fixed-fee, use the 'Retainer Flavor' variant — the clauses shift from scope-creep to hour-rollover and priority-queue rules.
- The week-1 question is the core deliverable. If the rest of the output is useful but the question feels generic, regenerate with more client context — it's a signal the prompt doesn't have enough to work with.
- Save the generated package as a template for your business. After 3–4 engagements, you'll notice patterns in which clauses you invoke most — tighten those first in your standard intake.
Variants
Agency Mode
Rewrites the outputs for a team context — adds account manager intros, escalation paths, and a RACI snippet.
Retainer Flavor
Optimized for ongoing monthly retainers instead of one-off projects — focuses on rollover rules, unused-hours policy, and quarterly reviews.
High-Stakes Enterprise
Adds procurement-friendly language, NDA posture, security questionnaire prep, and a more formal kickoff agenda suitable for clients $50K+.
Frequently asked questions
How do I use the Freelance Client Onboarding Script prompt?
Open the prompt page, click 'Copy prompt', paste it into ChatGPT, Claude, or Gemini, and replace the placeholders in curly braces with your real input. The prompt is also launchable directly in each model with one click.
Which AI model works best with Freelance Client Onboarding Script?
Claude Sonnet 4.5 or GPT-5. Claude writes the most natural-sounding client emails; GPT-5 is slightly sharper on the contractual clauses. Avoid Haiku/mini models — they flatten the specificity.
Can I customize the Freelance Client Onboarding Script prompt for my use case?
Yes — every Promptolis Original is designed to be customized. Key levers: Fill in the client's ACTUAL language from their emails/calls — copy-paste their phrasing into the input. The prompt uses it to predict what they'll assume is 'included.'; If you've had a scope-creep disaster before, describe it briefly in the context. The prompt will bake preventive clauses specifically targeting that failure mode.
Explore more Originals
Hand-crafted 2026-grade prompts that actually change how you work.
← All Promptolis Originals