Risks › Scope creep

Scope creep.
The risk that pays nothing extra.

Extra work the client asks for casually. Extra work that wasn't in the contract. Extra work that gets done because saying no is awkward.

Draft an agreement that prevents it

Free. No registration. No card. No catch.

What it means

In plain English.

Scope creep is what happens when the deliverables the client expects keep expanding beyond what's written in the contract — without an increase in the price, the timeline, or the agreed boundaries.

What it looks like

"Can you just add one more page?" "Quick logo tweak — five minutes?" "We need a Spanish version too." "Just one more revision." Each ask is small. The cumulative cost is not.

Why it's so common

Clients don't usually mean to do it. They're working out what they want as the project progresses. The contract was written before they knew. By the end, the agreement and the actual work don't match.

Why it's expensive

You absorb the cost. The deal stays at the original price, but the hours behind it go up. Profitable projects become break-even. Break-even projects become losses.

Why it's missed

It sounds harmless. It looks normal. It hides in vague wording.

Why missed

It feels rude to say no

The client asks casually. You want them to be happy. Saying "that's out of scope" feels confrontational without a contract to point at.

Why missed

Each ask is small

Any one tweak is a few minutes. The threshold for "this should be a change order" never gets crossed by any single request.

Why missed

The contract is silent

If the contract doesn't define scope precisely, you have no anchor. You can't point to what's in vs out because the document doesn't say.

What can go wrong

The downstream consequences.

Extra work

Hours you didn't quote. Days you didn't budget. The 20-hour project becomes 35 hours at the same price.

Delayed payment

When "done" keeps moving, "send the final invoice" keeps moving with it. Cash flow stalls.

Ownership conflict

Extra work, but is it covered by the original IP-transfer clause? Often unclear, often disputed later.

Burned relationship

Eventually you push back. By then it's a confrontation, not a contract discussion. The relationship sours.

Red-flag wording

If your contract says any of this, scope creep has already found a door.

These phrases sound reasonable. They're the legal version of a wide-open question. Avoid each.

Red flag

"as needed"

Who decides what's needed? Usually the client. Open-ended by definition.

Red flag

"until satisfied"

Subjective standard. Could mean anything. There's no finish line.

Red flag

"reasonable changes"

Whose reasonable? Almost always the client's. No upper bound.

Red flag

"all rights"

In context of revisions or changes, "all rights to request" = unlimited revisions.

Red flag

"at client discretion"

Whatever follows this phrase is one-sided. The client gets to decide. You absorb.

Safer pattern

The clause that writes scope creep out.

The fix isn't one clause — it's three working together: a precise scope-of-work clause, a revision-limit clause, and a change-order clause. Each is short. Together they put scope creep on the client's side of the cost line.

BizDraft's defaults already include all three, calibrated to the engagement you describe.

The pattern

Define scope concretely. Not "a website" but "a five-page marketing site with brand-aligned typography, sourced stock imagery, and a contact form. Excludes blog setup, e-commerce, third-party integrations."
Cap revisions. "Two rounds of feedback are included per deliverable. Each round must be consolidated and submitted within five business days."
Define change orders. "Work outside the defined scope, or beyond the included revision rounds, requires a written change order specifying additional fee and timeline."
Make change orders normal, not adversarial. "We expect change orders — clients often want to add scope as the project clarifies. The change order is the mechanism, not a flag of trouble."

Most affected