Jordan: I'm looking at a Slack message from three weeks ago. "Hey, quick favor — can you add a dashboard to track conversion rates? Should be simple." I said yes. Didn't send a change order. Didn't track the hours. That "quick favor" took fourteen hours across two weeks. At my rate, that's forty-two hundred dollars of uncompensated work. And here's the thing — the client doesn't even know they asked for something out of scope. To them, it was just a message in Slack. To me, it was two days of margin I'll never get back.
This happens to every solo operator. A client asks for something. You want to be helpful. You say yes. Three months later you realize you've given away thirty percent of your profit to scope creep that entered through Slack DMs and email threads. So I built something. An automation that catches every client request, classifies it as in or out of scope, generates a change order with pricing, and — this is the important part — blocks the work from starting until both signature and payment clear. No project manager needed. No awkward conversations. Just a system that protects your margins while you sleep.
Jordan: If you're running a book of three or more active clients and you don't have a structured change order system, you are hemorrhaging profit through informal requests. Every "can you just" in Slack, every "small tweak" in email — that's unbilled work eating your margins. Today's build changes that. A complete automation that flags scope creep, prices it, documents it, and gates the work until payment clears.
Jordan: Let me show you exactly how this works in production. The entire flow runs through four tools — Slack for the approval, Notion for the data layer, PandaDoc for the document, and Stripe for the payment gate. You can build this in Zapier or Make. I'll show you both.
First, the capture layer. Every client request needs to flow through a single point. I use a dedicated Slack channel — hashtag client-requests. You could also use a Fillout form that dumps into Notion. The point is — no more scattered requests across DMs, emails, and random channels. Everything goes through one gate.
Here's the Notion structure. Three databases. "Requests" — that's where everything lands. "Change Order SKUs" — your pricing table for common add-ons. And "Change Orders" — the actual documents you've sent with their payment status. Simple schema. The Requests database has a Select field for scope status, a Relation to the client, and a number field for the quoted price.
Now here's where it gets interesting. When a request comes in, we run it through an AI classification step. This is just a ChatGPT module in Make or an AI step in Zapier. You feed it the request text and your original scope document. It returns two things — whether this is in or out of scope, and if it's out, which SKU from your pricing table applies.
Let me show you the actual prompt that makes this work. "You are a scope classifier. Here is the signed statement of work for this client." Then you pass the SOW text. "Here is a new request from the client." Pass the request. "Determine if this request is within the original scope. If out of scope, identify which change order SKU best matches from this list." And you pass your SKUs. "Return a JSON object with scopestatus and suggestedsku." That's it. Twelve-second classification that would take you fifteen minutes to think through manually.
If it's in scope, the automation creates the task and notifies you. Normal workflow. But if it's out of scope — this is where the magic happens.
The automation looks up the price from your SKUs table. Let's say it's a dashboard request — that's fifteen hundred dollars in my book. It creates a draft change order record in Notion, then fires a Slack DM to you with two buttons. Approve or Reject. And here's the key — if you need to adjust the price, you click Approve and a modal pops up with the suggested price pre-filled. Change it if needed, submit, and the automation continues.
Now we generate the document. PandaDoc has a "Create from template" action in both Zapier and Make. You need a template with merge fields for client name, scope delta, price, delivery window, and — this is important — a clause reference field that ties back to your master agreement. The AIA defines change orders as written instruments that modify the original contract. This isn't just a new task. It's a contract amendment. Treat it like one.
Quick note on PandaDoc plans. If you're on Enterprise, you get native webhooks. If not, you'll use Zapier or Make's "document completed" trigger. Both work. I've run this on the Business plan for eight months without issues.
Once the document generates, here's the critical step — we attach a Stripe Payment Link. The Payment Link includes the change order amount as a line item. But here's what most people miss — in the paymentintentdata.metadata field, you store the PandaDoc document ID. That's how we correlate payment success back to the specific change order. Without that metadata, you're manually matching Stripe payments to PandaDoc documents. Ask me how I know.
The email goes out with the document link and this exact language: "Work begins when signature and payment clear." Not "please sign at your convenience." Not "we'll start while you review." Work is blocked until both conditions are met.
And I mean actually blocked. In your task management system — Asana, Jira, Trello, whatever you use — the task gets created with a "Blocked — Awaiting CO" status. In Asana, that's a dependency. In Jira, it's a flag. In Trello, you need the Card Dependencies Power-Up. The task exists but cannot move forward.
Here's where most automations would stop. Document sent, task created, hope for the best. But hope doesn't protect margins. We need two webhooks to fire before any work starts.
First webhook — PandaDoc document completed. That's your signature. Second webhook — Stripe payment succeeded. That's your money. Only when both webhooks have fired does the automation unblock the task, notify you in Slack, and log the revenue in your Change Orders database.
Let me show you this in Make. The scenario uses a router after the Slack approval. One path for approved, one for rejected. The approved path has two parallel branches — one creates the PandaDoc document, the other creates the Stripe Payment Link. They converge at an aggregator that waits for both to complete before sending the email.
The webhook listeners are separate scenarios. One listens for PandaDoc completion, one for Stripe payment. Both update the same Notion record. When both status fields show complete, a third scenario triggers that unblocks the task and sends the "all clear" notification.
In Zapier, it's a similar structure but you use Paths instead of routers. The key difference — Zapier's built-in PandaDoc trigger handles the completion webhook for you. In Make, you might need to set up a custom webhook if you're not on Enterprise. Both work. Zapier's slightly easier here, Make gives you more control over the webhook payload.
Now let's talk about what happens when things go wrong. Because they will. Client approves the change order but doesn't pay immediately. Your automation needs to handle partial completion. That's why we track both statuses separately in Notion. Document signed but not paid? Send a payment reminder after forty-eight hours. Paid but not signed? That's unusual but it happens — send a signature reminder.
Client wants to negotiate the price? That's fine. The Reject button in Slack kills the automation and creates a note in Notion to follow up manually. Not everything needs to be automated. Sometimes a five-minute call saves a client relationship.
Oh, and here's something I learned the hard way — always include a delivery window in your change order template. "Additional scope will be delivered within X business days of payment clearance." Without that, clients assume the add-on happens immediately, even if you're booked for two weeks.
The legal side matters here. The AIA — that's the American Institute of Architects — defines change orders as signed amendments to the original contract. Your template needs to reference the master agreement. Mine has a field that says "This Change Order modifies the Service Agreement dated between ." Get your lawyer to review your template once. Use it forever.
Let me show you the reporting layer because this is where you see the real impact. Every paid change order rolls up in Notion. Monthly summary shows total change order revenue, average order value, and most requested add-ons. Last month I had eight change orders totaling twelve thousand dollars. That's twelve thousand dollars that would have been free work without this system.
And here's the beautiful thing — it trains clients to respect scope. After the second or third change order, they start asking "Is this in scope?" before making requests. The system teaches them boundaries without you having to be the bad guy.
Jordan: So that's the build. Slack or Fillout for intake. AI classification against your scope document. Automated pricing from your SKUs table. One-click approval with price override. PandaDoc document generation with proper contract language. Stripe Payment Link with metadata correlation. And the critical piece — work stays blocked until both signature and payment clear. No exceptions.
This isn't about being difficult with clients. It's about running a sustainable business. Every untracked scope change is money you're leaving on the table. Every "quick favor" that takes a day is a day you're not building something billable.
Here's your homework. Set up the three Notion databases — takes about twenty minutes. Create your change order template in PandaDoc with the merge fields I showed you. Build your first five SKUs — the add-ons you see most often. Then pick either Zapier or Make and build the first half — just the classification and approval flow. You can add the document generation and payment gate once the foundation works.
All the templates are in the show notes. The Notion database schemas, the PandaDoc template structure, the Slack Block Kit JSON for the approval buttons, and both the Zapier and Make blueprints. Plus that pricing worksheet that helps you figure out what to charge for common add-ons.
Next week we're diving into async client updates — how to keep clients informed without meetings. Same format, different problem. I'm Jordan. This is Headcount Zero. Go protect your margins.