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
Integrations & automation
Where the boundary moves
An integration with Mailchimp does not mean an integration with every marketing tool. Requests for a new system are checked against the named list and the change procedure.
One-way nightly sync and two-way real-time sync are different projects. Agreeably finds the clause that set direction and frequency.
Automation counts, retry behaviour, alerting and monitoring are often specified, or left vague. Vague ones come back as unclear, with the gap named.
Typical requests
Illustrative examples. The label always depends on what your own agreement says.
“Could the sync run every five minutes instead of nightly?”
Potentially additionalThe SOW specifies a nightly one-way sync.
“Our finance team wants Xero connected too.”
UnclearThe accounting integration is “to be confirmed during discovery”.
“Can failed syncs email the ops team?”
IncludedError handling includes “email notification to a nominated address”.
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 reads the agreement and the client requests, nothing else. It never calls your clients’ systems.
No. Text in emails and agreements is treated as data to be analysed. The model has no ability to send messages, change billing or alter scope.
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