Check your next request against the agreement.
Upload one agreement and paste the last request that made you wince. See what it says in a few minutes.
No card needed · Cancel any time · A$ pricing
Guides
Field notes on scope.
Practical writing for delivery leads at implementation consultancies: how scope leaks,
how to decide what to do about it, and how to write agreements that make those
decisions easy.
-
Scope creep in fixed-price software implementations: how to spot it early
Why fixed-price CRM, integration and migration projects leak margin through small requests, the five shapes scope creep usually takes, and a routine for catching it before work starts.
Read -
Charge, absorb, clarify or decline: deciding what to do with an out-of-scope request
A decision framework for delivery leads: when to charge for a client request, when absorbing it is the right call, when to ask first, and how to record the decision so it holds up later.
Read -
How to write a change request a client can approve quickly
What a software change request needs to contain, the order to put it in, and a plain template you can copy, with the mistakes that slow approval down.
Read -
Statement of work clauses that make scope questions easy to answer
The deliverable, exclusion, limit, dependency and change-procedure clauses that let you answer “is this in scope?” in seconds, with examples for CRM, migration and integration work.
Read