Every automation I've built started with the same question: where does the work actually enter the system? For a landlord client it was lease PDFs sitting in a shared drive. For a small shop it was WhatsApp messages. For another team it was one inbox nobody checked. Not the tool. Not the workflow diagram. The file or message that starts everything. Once you know that entry point, the automation almost writes itself: something watches that spot, reads what lands there, and puts the important bits where people actually look. Skip this question and you end up with a clever workflow that still needs a human to feed it by hand. That's the part that breaks. Quick check for your own work: what file, message or email starts the task you're trying to automate? Start there.

Welcome to the 15 new faces who joined this week — good to have you here. So here's the thing I keep coming back to. The ideas you have aren't the problem. It's where they land. A thought hits you in the shower, in the car, mid-meeting — and then it's gone, because it had nowhere to go. Most of us never had a system for catching the thing, we just hoped we'd remember it later. We didn't. Quick one for the new people first, then everyone — where do your ideas actually go right now? 1) all in my head 2) notes app on my phone 3) notebook/paper 4) honestly it's scattered everywhere Vote below, then drop a comment with why that's your setup. No judgment — scattered everywhere is most of us. Tell me where yours lands and I'll point you at the best place to start tidying it up 👇

I've seen this happen a lot: someone takes a messy manual process and bolts AI onto it. Now the mess just happens faster. Before you automate anything, write the steps on paper first. If you can't explain the process to a friend in plain words, the automation will be a mess too. Simple example: following up with leads. The messy version is "check my notes, maybe text them, maybe email them, depends on my mood." The clean version is "every new lead gets a text in 5 minutes, an email in 1 day, and a call reminder in 3 days if no reply." Once the steps are that clear, the automation is almost easy to build. My rule now: automate the second version of a process, never the first. The first version is where you learn what the process actually is.

Alright… this one's for everyone who'd rather eat the loss than send the "just following up on invoice #0412" email. The chasing is boring, it feels rude, and so it slips. So you build it once and it does the asking for you. Here's what it does, in plain english. You keep your unpaid invoices in a Google Sheet — client, amount, due date, email, a Status column. Every day the automation looks at that sheet. Any row where the due date has passed and the status isn't "Paid", it hands to ChatGPT, which writes a reminder matched to how late it is. A day over gets a gentle nudge. Three weeks over gets firmer. Gmail sends it, and the row gets marked "Chased" so the same client doesn't get pinged twice. The services it touches, three of them: 👉 Make.com — https://www.make.com 👉 Google Sheets — https://sheets.google.com 👉 ChatGPT via the OpenAI API — https://platform.openai.com The build, start to finish: 1. Set up the sheet. Columns for Client, Email, Amount, Due Date and Status. Put a drop-down on Status with Unpaid, Chased and Paid. Add conditional formatting on Due Date so anything past today turns red — that way the sheet is readable even without the automation. 2. In Make.com, create a new scenario. First module is Google Sheets, action Search Rows. Point it at your sheet and tab. 3. In that module's filter, set Due Date "earlier than" now, and Status "not equal to" Paid. That's the "overdue and still owed" list. 4. Add a module to work out how overdue each one is. A Set Variable with a formula on the due date gives you a days-late number. You feed that into the next step. 5. Add the OpenAI module, action Create a Chat Completion. The prompt is where the tone lives. Something like: "Write a short, polite payment reminder to {{Client}} about invoice for {{Amount}}, now {{days late}} days overdue. Friendly if under a week, firmer if over three. Keep it human, no threats." 6. Add the Gmail module, Send an Email. Map the client's email into To, and the ChatGPT output into the body. 7. Add a Google Sheets Update a Row at the end. Set Status to Chased on that row so it drops off tomorrow's list. 8. Set the scenario to run once a day and turn it on.