It started with a simple request.
“Can you build us a website Nothing fancy. Just a clean design, maybe 5 pages. Two weeks, tops.”
I said yes. No contract. No written agreement. Just an email thread with some bullet points and a handshake over Zoom.
You probably know where this is going.
How It Fell Apart
Week one was fine. I designed the homepage, got approval, moved on to the inner pages. Week two is when things started to shift.
“Actually, can you also write the copy for the About page? Just a few paragraphs.”
Sure. That’s not a big deal.
“And can you integrate our booking system? It should be simple — just embed a calendar widget.”
Okay. A bit more work but manageable.
“Oh and the logo doesn’t really match the new site. Can you tweak it a bit?”
I’m a developer, not a designer. But fine.
“One more thing — can you set up basic SEO? Just the meta tags and stuff.”
By week four I was still working on a project that was supposed to be done in two weeks. The client wasn’t being malicious. They genuinely thought all of this was included. And I had nothing — nothing — written down that said it wasn’t.
That project cost me roughly 6 extra weeks of work. Unpaid.
The Real Problem Wasn’t the Client
Here’s the thing I had to admit to myself afterward: it wasn’t the client’s fault.
Clients don’t know what they don’t know. When they hire someone to “build a website,” they imagine a complete, finished, everything-works product. They don’t think in terms of scope. They don’t know that logo design is a separate service, that copywriting is a separate service, that SEO setup is a separate service.
That’s not ignorance — that’s just not being in the industry.
It was my job to define the boundaries. And I didn’t.
The moment I agreed to start work without a clear written document saying exactly what was and wasn’t included, I handed the client a blank check.
What a Statement of Work Actually Does
After that project, I started using a proper Statement of Work for every engagement. Not a general contract — those are about
legal terms and payment conditions. A SOW is project-specific. It answers one question: what exactly are we building together?
A good SOW has a few critical sections:
Scope of Work — what you will do. Specific, detailed, no vague language. Not “design the website” but “design up to 5 pages including Home, About, Services, Portfolio, and Contact.”
What’s Not Included — this is the section that actually changes everything.
Most freelancers write what they will do. Almost nobody writes what they won’t do. But clients fill that gap with assumptions. They assume copywriting is included. They assume revisions are unlimited. They assume the logo is part of the deal.
When you explicitly write “copywriting not included — client
provides all text” and “logo design not included” and “revisions beyond 2 rounds billed at standard hourly rate” — the conversation changes completely.
Not because clients are trying to cheat you. But because now everyone is working from the same page.
Client Responsibilities — what you need from them and when. Content, assets, feedback deadlines. If they’re late providing content, the project timeline shifts. This section protects you from delays that look like your fault.
Kill Fee — if the client cancels after work has started, they owe you a percentage of the total fee. 25% is standard. This protects you from investing weeks into a project that disappears.
Late Payment Clause — unpaid invoices accrue interest. 1.5% per month is standard. Most clients never trigger this — but having it written down means invoices get paid on time.
The Problem With Writing SOWs
Here’s the honest problem: writing a proper SOW from scratch takes 30-60 minutes. Every time. For every project.
You copy the last one, update the client name, try to remember what needs to change, inevitably miss something, send it, have to fix it.
After the scope creep nightmare I described above, I started taking SOWs seriously. But I also got tired of writing them from scratch for every project.
So I built a tool to generate them.
stecya.com — you fill in your project details and AI writes the complete SOW in about 30 seconds. Scope, deliverables, timeline, payment terms, what’s not included, client responsibilities, kill fee — all of it, tailored to your project type.
It’s free to generate and read. I built it because I needed it myself.
What Changed After I Started Using SOWs
The first time I sent a proper SOW to a client, they pushed back a little. “What do you mean copywriting isn’t included?”
I explained. They understood. We added copywriting to the scope, adjusted the price and timeline accordingly. Everyone was happy.
That conversation — which used to happen week three when I was already deep in the project and had no leverage — now happened before a single line of code was written.
That’s the real value of a Statement of Work. It’s not about being difficult or legalistic. It’s about having a real conversation about what you’re building before you build it.
Clients who understand the scope upfront are better clients. Projects with clear boundaries run smoother. And when something outside the scope comes up — and it always does — you have something to point to.
The One Section That Matters Most
If you take nothing else from this article, take this:
Write down what you won’t do.
It feels awkward. It feels negative. But it is the single most effective thing you can add to any freelance agreement.
“SEO optimization beyond basic meta tags — not included.”
“Photography and video production — not included.”
“Ongoing maintenance after 30-day post-launch period — not included.”
“Any pages beyond the 5 listed above — not included.”
Every item on that list is a conversation you won’t have to
have at 11pm on a Tuesday when you’re already three weeks into
a two-week project.
Start Simple
You don’t need a lawyer. You don’t need a complex legal document.
Start with a simple one-page document that answers:
- What am I building?
- What am I NOT building?
- When will it be done?
- How much does it cost?
- When do I get paid?
Get that signed — even just an email reply saying “I agree to
these terms” — before you start any work.
That one habit will save you more money and stress than almost
anything else you do as a freelancer.
Built stecya.com after this experience — free AI SOW generator for freelancers. Takes 30 seconds. No credit card required.
This article was originally published by DEV Community and written by Roy Sukro.
Read original article on DEV Community