What nobody tells you about your first freelance data client
When I landed my first consulting project, I thought the hardest part would be the technical work — building the data warehouse, designing ETL pipelines, getting SSRS reports right.
It wasn't.
The hardest part was the conversation before the work even started. The client didn't know what they needed. They just knew they had "a data problem." They wanted "dashboards" but couldn't articulate what decisions those dashboards would drive.
Here's what those early projects taught me:
Start with the decision, not the data. Ask: "What decision would you make differently if you had this information?" That single question has saved me hours of building reports nobody uses.
Scope creep starts at kick-off. Every vague requirement you let slide in the first conversation will haunt you in week 6. I now walk into every engagement with a written SOW — non-negotiable.
Charge for discovery. I used to do it free to "win" the project. Now I know: discovery IS the work. If they won't pay for it, they won't value the output either.
These lessons are now baked into how I run my entire practice. I packaged the framework — from pricing to proposals to SOW templates — in my Freelancer Starter Kit: https://growthwithshehroz.gumroad.com/l/cpfja
What's the one thing you wish someone had told you before your first consulting or freelance gig?
The gap between "I can do the technical work" and "I know how to navigate a client relationship" is something almost no one talks about before you land that first project.
What I've found talking to freelancers: the hardest invisible skill is managing expectations at the start, not delivering the work at the end. The client who goes quiet, moves goalposts, or forgets what they agreed to — those situations don't get covered in any tutorial.
One thing that helps: getting everything in writing as early as possible, including what "done" looks like. Scope creep and payment issues almost always trace back to a fuzzy kickoff conversation.
What was the thing that surprised you most — was it the client communication side, the scoping, or something else entirely?
Honestly, scoping — but not in the way I expected. It wasn't that clients asked for too much. It was that they had no idea what they actually wanted. They'd say "we need better reporting" but couldn't tell me what decision they were trying to make with that reporting.
Your point about getting everything in writing is exactly right. I now run a discovery call before any engagement where I refuse to talk about deliverables until the client can answer: "What would you do differently if you had this data?" That single question filters out so much ambiguity.
The going-quiet thing is real too. I've learned that silence from a client usually means confusion, not disinterest. Following up with "is anything unclear about what we agreed?" has saved me from more scope disasters than I can count.
I put my full freelancing framework together here if useful → https://growthwithshehroz.gumroad.com/l/cpfja — covers the discovery call structure, SOW templates, and pricing approach I've built over time.