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
CRM implementations
Where the boundary moves
Pipeline stages, custom objects, page layouts, reports, dashboards and user roles are usually capped. A request for “just one more” is checked against the cap and what has already been agreed.
An extra sandbox, a partial-copy refresh or a second production org can be a day of work. Agreeably cites the environment clause rather than leaving it to memory.
Another training round, a recorded session for a new team, two more weeks of support after go-live. Each is assessed against the sessions and support period you signed.
Typical requests
Illustrative examples. The label always depends on what your own agreement says.
“Can we add a “Negotiation” stage to the pipeline?”
IncludedThe SOW allows up to seven stages and five are configured.
“We need a separate pipeline for renewals.”
Potentially additionalConfiguration covers “one sales pipeline”.
“Can the sales team get another training session?”
UnclearTraining is “two sessions for the sales team”, and the client counts the cancelled one differently.
Write it down
The more specific the statement of work, the more requests come back included or potentially additional instead of unclear. Worth having in yours:
Read the guide to SOW clauses →FAQ
No. It works from the agreement and the requests you paste or forward. Nothing is read from or written to your client’s CRM.
Any. Agreeably reads the statement of work, not the platform, so it works the same for Salesforce, HubSpot, Dynamics 365, Zoho or anything else your SOW describes.
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