← All templates

Client Delivery

Scope Creep Guard

Scope creep is rarely a single big request; it is fifteen small ones nobody wrote down. This workflow watches your client channel for request language, logs each one to a change-request sheet, and reminds you weekly to convert the list into an invoice or a conversation.

4 stepsRequires Zapier Starter or higher15 minMedium
SlackGoogle SheetsTodoistFilter by Zapier

What you get

Every extra request is written down at the moment it is made.
You can show a client the list instead of arguing from memory.
Small extras become invoiced work rather than unpaid work.

Workflow blueprint

SL
When this happens
SlackNew Message Posted to Channel
1FI
Filter by ZapierOnly continue if
2GS
Google SheetsCreate Spreadsheet Row
3TO
TodoistCreate Task

The full blueprint — every field mapping, example value and the written copy for each message — is included with purchase.

Getting it into Zapier

Build this one from the recipe. The blueprint gives you the exact trigger, action events and field mapping for all 4 steps, so it is a copy-and-paste job rather than a design job.

You need your own Zapier account. Zapier’s Free plan runs single-step Zaps only; multi-step Zaps need a paid plan, and Paths and Webhooks need Professional. How this works →

Not on Zapier?

n8n — import and go

An n8n workflow JSON ships with this template. Import it and all 4 steps arrive on the canvas wired in order, and 3 of the 4 nodes arrive with their fields already filled in — the subject lines, the message copy, the delays, the column names. Every step maps to a native n8n node.

What an import cannot carry is your credentials, and the IDs that only exist inside your own account — which spreadsheet, which channel, which board. Those stay in a sticky note under the node, listing what is already done so you do not retype it, and what is left so you can see it.

Make — build guide

A Make-specific guide ships with this template: every module in order, every field value, and the concept translations that catch people out — filters live on the links between modules, and the schedule lives on the scenario rather than in a trigger module.

Self-hosted n8n has no per-task fee, which is worth knowing if this workflow runs at volume. Platform coverage →

Setup steps

1
Watch the shared client channel

Configure this step using the field mapping in the blueprint.

2
Filter for request language

Configure this step using the field mapping in the blueprint.

3
Log the request as a change request

Configure this step using the field mapping in the blueprint.

4
Create a same-day review task

Configure this step using the field mapping in the blueprint.

Implementation notes

  • Tune the trigger phrases to how your clients actually write. Two weeks of real messages will tell you.
  • Email works as a trigger instead of Slack: use Gmail — New Email Matching Search on the client address.
  • The sheet is the deliverable. Bring it to the monthly call rather than only invoking it during a dispute.