Integrations & automation

Scope control for integration and automation projects

Integration scope is about named systems, directions, frequencies and failure handling. Automation scope is about named workflows. Clients ask for a new connector, a faster sync or “one more” workflow, and each sounds small until you build it. Agreeably checks it against what you signed.

Where the boundary moves

The edges clients push on.

  • Named systems

    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.

  • Direction and frequency

    One-way nightly sync and two-way real-time sync are different projects. Agreeably finds the clause that set direction and frequency.

  • Workflows and error handling

    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

How a few of them might come back.

Illustrative examples. The label always depends on what your own agreement says.

  • “Could the sync run every five minutes instead of nightly?”

    Potentially additional

    The SOW specifies a nightly one-way sync.

  • “Our finance team wants Xero connected too.”

    Unclear

    The accounting integration is “to be confirmed during discovery”.

  • “Can failed syncs email the ops team?”

    Included

    Error handling includes “email notification to a nominated address”.

Write it down

Clauses that make these easy to answer.

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 →
  1. Systems to integrate, by name
  2. Direction, frequency and volume of each sync
  3. Error handling, retries and alerting
  4. Number of automated workflows, named
  5. Who owns API credentials and third-party costs
  6. Monitoring and support after go-live

FAQ

Integrations & automation: questions

Does Agreeably connect to our integration platform?

No. It reads the agreement and the client requests, nothing else. It never calls your clients’ systems.

Can instructions in a forwarded email make it do something?

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.

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