Stop Coding on Day 1: A Freelancer's Guide to "Ironclad" Onboarding

Hamza El haissouf — Thu, 20 Nov 2025 10:08:51 +0000

used to make the same mistake with every new freelance client.

We would sign the contract (sometimes), shake hands, and I would immediately open VS Code. I was eager to impress. I wanted to show progress.

Big mistake.

Three days later, I’d be blocked. "Hey, I still need the AWS keys." "Can you invite me to the GitHub repo?" "Wait, you wanted this in React Native or Flutter?"

I was losing billable hours chasing administrative details. It felt unprofessional, and worse, it delayed my payments.

So, I stopped coding on Day 1. Instead, I built an Onboarding Protocol.

Here is the system I use now to go from "Signed" to "Shipping" without the headache.

Phase 1: The Handshake (Administrative)
Never write a line of code until the relationship is secure. My rule is simple: No deposit, no repo.

Signed Contract: Emails are not contracts. Use a proper e-signature tool.

Deposit Cleared: Don't trust the screenshot of the transfer. Trust the notification from your own bank.

Communication Policy: Establish boundaries now. If you don't want WhatsApp messages at 10 PM on a Sunday, tell them now.

Phase 2: The Keys (Access)
The "Access Dance" is the biggest time-killer in freelancing. I send a single email requesting everything at once.

Repo Access: Ensure you have 'Write' or 'Admin' access. 'Read' access is useless for a developer.

Design Files: Ask for 'Edit' access in Figma so you can actually export the assets you need.

Environment Variables: Ask for the .env file immediately. If they don't have one, offer to set it up (as a billable task).

Phase 3: The Alignment (Technical)
This saves you from the "It works on my machine" nightmare.

Node/PHP Versions: Agree on the exact version (e.g., Node 20, PHP 8.2).

Package Manager: Are we using npm, yarn, or pnpm? Mixing these causes lockfile chaos.

Linter Rules: Agree on a standard (ESLint/Prettier) before you push your first commit.

Why this matters
Since I started using a strict checklist, I look more professional. Clients respect a developer who leads the process. Instead of asking "What do I do now?", I say "Here is what I need to start."

Want the full list?
I turned my personal protocol into a digital product called The Ironclad Onboarding Checklist.

It includes the full 3-Phase breakdown, printable PDF, and a Notion template you can duplicate for every new client.

I'm selling it for $1 (basically free) because I want to help other devs professionalize their business.

👉 Grab the Ironclad Checklist here

DEV Community: Hamza El haissouf

Stop Coding on Day 1: A Freelancer's Guide to "Ironclad" Onboarding