The Deal Too Small for a Contract Is the Deal That Needs One Most
There is a category of engagement that operators consistently leave undocumented.
Not the big ones — the multi-month retainers, the high-value productions, the enterprise client projects. Those get agreements. The stakes are obvious, the formality feels appropriate, the client expects it.
The undocumented category is smaller: the favor-adjacent project for a friend who's also a client. The subsidized engagement with a nonprofit or early-stage company you want to support. The quick scope that 'shouldn't take long.' The relationship-based deal where pulling out a contract feels like an overreaction to something that both parties intend to be simple.
These are the engagements that generate the most disproportionate scope disputes. Not because the people involved are difficult, but because the instinct to skip formality is strongest precisely where the conditions for scope creep are most favorable.
Why Small Deals Drift Fastest
Scope creep requires two conditions: an undefined boundary and a relationship that makes enforcing it feel awkward.
Large, formal engagements tend to have defined boundaries — if only because the contract negotiation forced the conversation. Both parties know what's in scope because someone had to write it down.
Small, informal engagements skip that conversation. The scope is understood between the parties — which means each party understands it differently, in ways that don't become visible until a request arrives that one party considers included and the other considers additional.
The relationship dynamic compounds the problem. In a large formal engagement, a scope boundary conversation is a business conversation. In a small relationship-based one, it feels personal. The operator who wants to push back on an out-of-scope request has to do it in a context where the relationship itself feels like it's at stake — which means many operators don't push back at all. They absorb.
Informal engagements are where scope drifts fastest because nothing was ever written down to drift from. The boundary doesn't exist until you create it — and the time to create it is before the project starts, not when the first expansion request arrives.
The 'It's Too Small to Formalize' Instinct Is Precisely Backwards
The logic behind skipping documentation on small deals seems reasonable on the surface: the overhead of a formal agreement isn't proportionate to the value of the engagement. The time to draft, review, and execute a contract costs more than the deal is worth.
This reasoning contains a structural error.
The cost of a formal agreement is fixed and upfront. The cost of an undefined scope is variable and deferred — and it scales with how much the engagement expands, not with how much it was originally worth. A small deal with no scope boundary can drift into a large amount of uncompensated work. The original value of the engagement becomes irrelevant once the scope has expanded past it.
The operators who've been burned by this — who've delivered three times what they priced because the scope drifted and the relationship made it hard to say no — uniformly describe the same realization: the documentation overhead they avoided upfront cost a fraction of what the undocumented scope expansion eventually cost them.
Subsidized and Reduced-Rate Engagements Are Higher Risk, Not Lower
The risk calculus is even more skewed in subsidized engagements — work done at a reduced rate, as a favor, in exchange for visibility or sponsorship, or for a client whose mission you want to support.
These engagements carry an additional dynamic: the client who is receiving a discount or subsidy often — not always, but often — conflates the reduced fee with an expanded claim on the operator's effort. The discount gets reinterpreted, consciously or not, as a credit toward additional work rather than a reduction in the agreed scope.
This reinterpretation is rarely malicious. It emerges from a genuine misunderstanding of what a subsidized rate means. The client believes the operator is invested in their success and will go the extra mile. The operator believes they've defined a scope and reduced the fee as a gesture of support. These two beliefs are compatible until the first out-of-scope request arrives — at which point the client is surprised that 'going the extra mile' apparently has limits, and the operator is surprised that the discount is being used as leverage.
The provision that prevents this is not complicated. It is explicit.
What a Scope Boundary Clause Actually Needs to Say
A scope boundary clause doesn't require legal sophistication. It requires specificity on three points:
1. What is included
The positive scope: what you are delivering, defined specifically enough that completion is unambiguous. Not 'strategic support' or 'marketing assistance' — the actual deliverables. Three campaign concepts. One governance framework. Two rounds of revised copy. Whatever the specific outputs are, they need to be named.
2. What is not included
The negative scope: what falls outside this engagement. This is the clause most operators omit and most disputes trace back to. A simple formulation: 'Work not described in this agreement, including but not limited to [specific adjacent services], is outside the scope of this engagement and subject to a separate agreement or change order.'
The negative scope doesn't have to be exhaustive. It has to be clear enough that when a request arrives that wasn't in the positive scope, both parties have a shared reference point for the conversation.
3. What happens when the scope expands
The change order process: how additional work is requested, documented, and priced before it begins. 'Any work outside the defined scope requires a written change order signed by both parties before work commences' is sufficient. The key word is before — not after the work is done, not after the relationship has been strained by an undocumented expansion, but before.
For subsidized or reduced-rate engagements, add one more provision: 'The reduced rate in this agreement applies to the defined scope only. Work outside the defined scope is priced at the operator's standard rate.'
That single sentence converts a discount from an open-ended commitment into a specific, bounded gesture. It makes the structure of the arrangement explicit rather than assumed.
Applying This to Relationship-Based Deals
The objection that comes up most often in relationship-based deals is that pulling out a formal agreement signals distrust — that it changes the tone of an arrangement that was supposed to be collegial.
The operators who've worked through this consistently find the opposite. Presenting a clear, simple scope document — not a 40-page contract, just a defined scope, a change order process, and a payment schedule — communicates professionalism, not suspicion. It tells the client that you take the engagement seriously enough to structure it properly.
The clients who respond poorly to basic documentation are, again, providing information worth having before the project starts.
And for the clients who respond well — which is most of them — the scope document becomes the reference point that keeps the relationship clean. When an expansion request arrives, neither party has to have an uncomfortable conversation about whether it was included. The document answers the question. The relationship stays intact because the business structure underneath it is clear.
The Standard Should Be Consistent
The most practical shift an operator can make is to apply the same documentation standard to every engagement regardless of size, rate, or relationship closeness.
Not the same level of complexity — a small engagement doesn't need a 20-page master services agreement. But the same structural elements: a defined scope, a negative scope, a change order process, and a payment schedule. Those four things take less time to document than the average scope dispute takes to resolve.
Oblige provides agreement templates that include scope boundaries as a standard field — not an optional addition, but a core component of every engagement document. When scope is defined in the same place as milestones and payment terms, the structure of the engagement is visible from the start. The small deal gets the same infrastructure as the large one, with proportionate complexity and the same protection.
The deal that feels too small to formalize is rarely too small to go wrong.
Join Oblige → Scope boundaries built into every agreement, every engagement.
