Set Boundaries Before the Project Starts

"Can we make one small change."

If you've been an independent professional for more than six months, those five words still make your jaw tighten. That "small change" becomes a new deliverable. Then another. Before you know it, you've done forty percent more work for the same price.

This isn't about difficult clients. It's about a missing conversation the one that happens before the project starts, not during it.

Define the Deliverable, Not the Time

Most independent professionals scope projects in hours. "I think this will take about forty hours, so I'll quote $4,000." That's a trap. Hours measure input, not outcome. The client doesn't care how many hours you work. They care what they get.

Scope by deliverable instead. Name the thing you will hand over. Be specific.

When you define the deliverable specifically, you give yourself a test. When the client asks for "one more page," you can point to the agreement and say, "That's outside scope." Not defensive. Just factual.

The number that matters: independents who scope by deliverable rather than hours report project sizes averaging $10k+ compared to $3k for those who sell time. The work isn't different. The framing is.

Set Revision Limits Up Front

The second biggest scope leak is unlimited revisions. "I want to make sure you're happy" sounds generous. In practice, it means the client can request changes indefinitely while you keep working for free.

Revision limits aren't adversarial. They're a forcing function for decision-making. When a client knows they get three revision rounds, they consolidate feedback. They prioritize.

The transformation: professionals who set explicit revision limits see 60% of projects close on the first revision round. The ones who don't average four to seven rounds. That's weeks of unpaid work.

Write the Scope Like a Contract

Your proposal's scope section isn't marketing copy. It's the document you'll both refer to when things get fuzzy. Three sentences that belong in every scope of work:

• The inclusion sentence: "This project includes [specific list]."
• The exclusion sentence: "This project does not include [specific list]."
• The drift sentence: "Any work outside the items above will be scoped as a separate engagement."

Let Salt Watch the Edges

Here's the hard truth: even with perfect boundaries, scope drift happens. You miss it because you're heads-down doing the work. The client sends a Slack message. You reply yes. You forget you just agreed to something outside scope.

Salt surfaces that for you. When your project scope is defined in Salt, Salt tracks every request against that scope. When a client asks for something outside the agreement, Salt flags it. Not as a confrontation. As a data point.

The professionals who use Salt's scope tracking catch drift an average of two weeks earlier than those who don't. Two weeks of work they don't give away for free. Over a year of projects, that's real money.