Client onboarding: from first contact to delivery
First client I had, came in tight on deadline. I said: “you want it fast or done right?” He picked done right. Then he waited, and waited. Felt like I disappeared.
Delivery was good. He liked the result. But experience? Horrible. Never asked again.
I learned that results are half of it. The other half is how you run the process.
The briefing form
Before I touch code, I collect information. And I do it properly. Not “what’s the scope?”
My form asks:
“What’s your biggest business obstacle?” Not interested if you want an e-commerce site, interested in whether your problem is lack of sales, lack of visibility, lack of control.
“Who’s your ideal customer?” I need to understand the audience, not generic “small businesses”.
“What’s the real deadline?” Not the one the client thinks it is.
“What’s the budget?” Transparency. If I say R$ 15,000 and he expected R$ 5,000, nobody wins.
I send the form, leave 2 days. Client comes back with answers. Then we schedule the kick-off.
Kick-off call of 1 hour
It’s a real call. Camera on, both talking.
I start like this: “I’ll explain how my process works. Then you ask questions.”
I explain:
Week 1 is discovery. I understand the project, create a document with your understanding signed by you, make a proposal. If you approve, week 2 we start.
Week 2-3 is build. You get updates daily on Slack. You can comment, ask for changes.
Week 4 is refinement. We review together, create a delivery document with a feature list.
Week 5 is go live. Deploy, monitoring, support.
Client wants to skip ahead? We talk about parallelization or reduced scope.
After that, he asks questions. Says “I want the pricing page to be more aggressive.” That’s when I understand what he really wants.
Weekly checkpoints
Every Tuesday, 10:30am. 15-minute call.
I show what I built. Not code, screenshots, video of how it looks. Client sees progress.
He says “I like it, but remove that part”. I take a note.
This consistency is gold. Client knows you’re working, knows you listen, knows the process is real.
Saw many devs just send a screenshot on Slack. Client wonders if anything’s moving.
With a 15-minute call every week, client sleeps well.
Delivery document
Week 4, one week before deployment, the document is generated.
It has everything that was built:
- Feature list (what was delivered)
- Staging URLs
- Test login
- How to navigate
- Known limitations
- Next steps
I send it, client signs (digitally, DocuSign style if formal).
This is protection for both. Client can’t later say “oh, I wanted that”. The document says he wanted that other thing.
Made this mistake before. Client charged me for a feature he thought was in scope. Big fight.
The document changes everything.
Go live and handoff
Go live is simple. Deploy to Vercel, configure DNS, SSL.
Then comes handoff. Sat with AutoPars Pro client for 2 hours.
Showed: how to log in, create an account, schedule, cancel, see history, recover password, use integrations.
Like a mini-training. Not abandoning him.
Then I leave a written guide: “5 steps to do X”. When client has questions months later, he checks the guide first. Reduces support tickets.
Post-sale support
First 30 days is included. Client finds a bug? I fix it. Client wants a small change? I do it.
After 30 days, changes are hourly. R$ 150/hour.
Client knows this from day one. No surprises.
With charging for small tweaks, I talked about how this changes when you professionalize.
Why this matters for business
When you professionalize onboarding, clients go crazy recommending you.
Not because of the result, but because of the experience. Nobody recommends a bad experience.
Had a client who paid R$ 12,000. Result was good but experience was mediocre. Never heard from him again.
Had a client who paid R$ 8,000 but experience was excellent. He referred me to 4 people. Became the foundation of growth.
Onboarding is a silent differentiator that works.
With being an independent developer without becoming an agency, this process is what lets you not become an agency. Because process is scalable, replicable.
By the third client you onboard, you have a sharp routine. By the fifth, it comes together quick and good.
- Create briefing form with 5-7 critical questions
- Document your 5-week process
- Schedule kick-off call as part of workflow
- Create visual checkpoint template
- Generate automated delivery document
- Prepare 5-step handoff guide per feature
- Document post-sale support SLA
Process is the structure that allows growth without chaos.
Example kick-off email
I send this template to clients, works great:
“Hi [Name],
All good? I blocked the week of [date] to start the project. Before touching code, I want everything crystal clear.
Week 1 (Apr 15-19): Full discovery. Conversation, understanding, document signed by you confirming what we agreed.
Week 2-3 (Apr 22-May 5): Development. You see progress daily on Slack. Monday has an update, Wednesday has another.
Week 4 (May 8-12): Polish. We sit together, review, create final delivery document.
Week 5 (May 15-19): Go live. Deploy, DNS, monitoring, training on how to use.
You approve the proposal Monday, ok? Read carefully, ask questions, we move forward.
Talk soon, [your name]”
Simple, clear, expectations already set.
Reducing scope creep
Scope creep is when the client asks for more than was hired. Stretches week 5 to week 8, project becomes endless.
A scope document helps. But there’s a better tactic: in the briefing form, ask for priorities.
“What’s most important: scheduling, landing page or blog?”
Client picks one. You focus on that. If they later want to change, it’s a change request, it’s extra hours.
With Family Pilates, client asked for scheduling, landing page, and integrations. I said: “we have 4 weeks. Scheduling happens in 3, landing in 2. Integrations come next sprint or you extend the deadline.”
Client chose to extend to 6 weeks. Problem solved, expectations clear.
First week is discovery for real
Made the mistake of starting to code week 1. Thought it was wasting time.
It’s not. Good discovery saves weeks later.
Get into:
- What’s the client’s audience
- What’s the real problem (not what they think it is)
- What’s the goal (sell more? rank on Google? organize?)
- What’s the constraint (image budget, expensive API, legacy integrations?)
Week 1 done right = rest of project fast.
Signed acceptance document
Used DocuSign a few times but found it expensive. Now I use Gmail attachment plus client’s confirming reply.
Simple template:
PROJECT SCOPE
Client: [name]
Developer: [you]
Date: [date]
Timeline: [5 weeks]
Value: R$ [amount]
DELIVERABLES:
- Responsive homepage
- Online scheduling page
- 10 blog posts
- Google Calendar integration
- SSL certificate
TIMELINE:
Week 1: Discovery (May 15-19)
Week 2-3: Development (May 22 - Jun 5)
Week 4: Refinement (Jun 8-12)
Week 5: Deploy (Jun 15-19)
CHANGES AND COSTS:
Scope changes: R$ 150/hour
Delays from client: deadline extended no extra charge
APPROVAL:
Client: _____________
Date: _____________Client signs, you sign, copy to file. Protection for both.
Clean exit: handoff checklist
Delivered a project last week. Client felt “abandoned” after.
Created a handoff checklist:
Day 1: 1.5 hour webinar
- 15min: show admin panel
- 15min: how to create new appointment
- 15min: how to see calendar
- 15min: how to cancel reservation
- 15min: how integration works
- 15min: how support works
Day 3: Send written document with screenshot of each step.
Day 7: Check-in email: “everything working? any questions?”
Client feels cared for. Later for maintenance, they’re happy to pay.
When the client is difficult
Have a client who changes their mind daily. Started doing it. Then understood: scope document is a barrier.
When client wants to change, I say: “is it in the scope? No. That’s R$ 150/hour extra or delivery next week.” Never changed again.
A clean process naturally weeds out bad clients. Clients who want professionalism accept it. Clients who want chaos leave.
Quick formula to repeat
- Briefing form (2 days to respond)
- Kick-off call (1h, explain process)
- Week 1 discovery (document everything)
- Week 2-3 build (daily Slack updates)
- Week 4 refinement (review call)
- Week 5 deploy (go live)
- Handoff (1.5h training)
- 30 days included (bug fixes)
- After that maintenance or done
Repeat with every client. Third client comes together in 4 weeks because you’re already smooth on the process.
- Create briefing form in Google Forms
- Write kick-off call template
- Document your 5-week process
- Create signable scope template
- Build handoff checklist
- Define post-sale support SLA (30 days included)
- Train one client with new process
Professional onboarding became a market differentiator.