AI Automation Toolkit Community

AI automation playbooks, templates, and support for solo founders who want their email, CRM, and admin work running on autopilot.
New Castle, US
•
•Created byProfile pictureMax Sacco
1 joined
Profile picture
Max SaccoProfile picture@saccomax15·1d

I stopped rewriting the same 12 replies by drafting from my own sent folder

A lot of my inbox wasn't new work. It was the same questions in new threads: pricing, timeline, what's included, how onboarding works, can you do X. I kept rewriting answers I had already written well six months ago.


I didn't build a chatbot. I built a first-draft machine that only uses my own past emails.


Here's the setup, Make.com + Gmail + a private Google Doc of "approved answers":


  1. Trigger: new inbound email that isn't from an existing client project (those still get a human read first).

  2. Action: GPT classifies it as one of about 12 question types, or "other." Other skips the rest and just sits in my inbox.

  3. Action: for a known type, it searches my sent folder plus the approved-answers doc and pulls the closest reply I actually sent before.

  4. Action: it drafts a reply in Gmail, in my voice, with a blank where a name or price might need updating. It never sends.

  5. I open the draft, change two lines if needed, hit send. Average time is under a minute.


After about six weeks:

  • Repeat questions went from 15-20 minutes of writing each to a skim and a send.

  • Tone stayed consistent because the source material is emails I already sent, not a generic FAQ page.

  • The classifier used to dump "can we hop on a call?" into pricing. I added an explicit "call request" type that drafts nothing and just labels it. Don't auto-draft meeting asks.


The rule that matters: drafts only, never auto-send, and only from copy I've already stood behind. That's how you get the time back without sounding like a bot.


If you want the 12-type list and the "don't send" prompt rules, people pass that around in the AI Automation Toolkit community.

Profile picture
Max SaccoProfile picture@saccomax15·Oct 6

I stopped doing my books on Sunday night by making every receipt file itself

Sunday night used to mean sitting down with a pile of Gmail receipts, downloading PDFs, renaming them, and typing amounts into a spreadsheet. I'd skip weeks, then spend two hours catching up, then skip again.


The fix was not "be more disciplined." It was taking myself out of the loop.


Here's what I built with Zapier + Gmail + Google Drive + a simple Sheet:


  1. Trigger: new email in Gmail matching from:(receipt OR invoice OR noreply) with an attachment, or any email I star and label "expense."

  2. Action: save the attachment to a Drive folder named by month (2026-10, etc.).

  3. Action: GPT reads the PDF or image and extracts merchant, date, amount, and category (software, ads, travel, contractors, other). If it can't read it, it flags the row instead of guessing.

  4. Action: a new row lands in my expenses Sheet with those fields plus a link to the file.

  5. Every Friday I get a 5-line email: total spent this month, anything uncategorized, and any charge over $100 for a second look.


I still approve the weird ones. I do not retype them.


After three months:

  • Bookkeeping dropped from a Sunday chore to about 8 minutes on Friday.

  • I stopped losing Uber and Stripe receipts that used to vanish into Promotions.

  • The model misread a handwritten parking receipt once. The "flag if unsure" rule caught it. Don't let it invent numbers.


The lesson: expense tracking fails because the work is boring, not because the tools are missing. If the receipt files itself the moment it hits your inbox, you don't need willpower.


If you want the Gmail search filter and the extraction prompt, that's a common swap in the AI Automation Toolkit community.

Profile picture
Max SaccoProfile picture@saccomax15·Sep 29

I stopped getting "any update?" emails by sending a 4-line status note before clients had to ask

The most draining emails I used to get weren't complaints. They were "hey, just checking in, any update on this?" They always arrived on a day I was already behind, and answering them took longer than the actual work because I had to reconstruct where the project stood.


I didn't hire anyone to handle it. I made the update go out before the question could form.


Here's the setup, using n8n + my project board:


  1. Trigger: every Friday at 9am, pull every active client project that isn't marked done.

  2. Action: grab the last three completed tasks, the next two upcoming ones, and the current due date from the board.

  3. Action: GPT turns that into a 4-line email. Hard rules in the prompt: no adjectives, no "hope this finds you well," no filler. Just: what shipped this week, what's next, anything blocked, and the date they should expect the next note.

  4. Action: the draft lands in Gmail as a scheduled send for Friday 10am. I glance at it for 30 seconds. If it's accurate, it goes. If a project is in a weird spot, I rewrite those four lines myself.


Results after about two months:

  • "Any update?" emails dropped from a few a week to almost none. Clients started replying "thanks, this is helpful" instead of chasing me.

  • I spend about 10 minutes on Friday reviewing drafts instead of 20-30 minutes scattered through the week reconstructing status from memory.

  • The first version of the prompt was too cheerful and too long. Cutting it to four lines made people actually read it.


The lesson: most check-in emails aren't clients being impatient. They're clients sitting in the dark. A short, boring, predictable note on a fixed day removes the need for them to ask.


If you want the 4-line prompt, that's the kind of thing people trade in the AI Automation Toolkit community.

Profile picture
Max SaccoProfile picture@saccomax15·Sep 22

I cut proposal writing from two hours to fifteen minutes by generating the first draft from my CRM

I used to dread sending proposals. After a discovery call I'd sit down, open a blank Google Doc, and spend two hours rewriting the same structure: recap of their problem, what I'd do, timeline, price, next step. Most of that information already existed in my CRM notes. I was just retyping it.


The system I built now does the first draft for me:


  1. Trigger: I mark a deal in my CRM as "proposal requested."

  2. Action: Make.com pulls the deal notes, discovery-call summary, budget range, and the services they asked about.

  3. Action: that bundle goes to GPT with a locked template (same headings every time) and a few hard rules: no fluff, no made-up case studies, leave price as a placeholder if it wasn't discussed.

  4. Action: the draft lands in a Google Doc in a "Proposals - Drafts" folder and I get a Slack ping with the link.

  5. I spend 10-15 minutes editing for tone, filling in the actual number, and cutting anything that sounds generic. Then I send it.


The template is doing as much work as the AI. Without a rigid structure, the drafts wandered. With one, they come out 80% usable.


After about six weeks:

  • Time per proposal dropped from roughly two hours to fifteen minutes of actual editing.

  • I send proposals the same day as the call instead of two days later, which noticeably improved close rate on smaller deals.

  • The first version of the prompt kept inventing timelines I hadn't agreed to. Adding "only use dates or durations that appear in the source notes" fixed that.


The point isn't to auto-send proposals. It's to stop treating a document you write every week like a blank-page problem. Automate the structure, keep the judgment.


If you want the prompt and the CRM field list I use, that's the kind of thing people swap in the AI Automation Toolkit community.

Profile picture
Max SaccoProfile picture@saccomax15·Sep 15

My client calls used to end and then just evaporate until I automated the notes-to-action step

For a long time my client calls followed the same pattern: good conversation, a few commitments made out loud, and then nothing written down anywhere except whatever I could remember an hour later. Things slipped. A client would ask "did we ever follow up on X" and I'd have no record.


Here's the chain I built with Fireflies (call recording/transcription) + Make.com + my task manager:


  1. Trigger: Fireflies finishes transcribing a call (it auto-joins my Zoom calls).

  2. Action: the full transcript gets sent to GPT with a prompt that extracts only concrete commitments, in the format "[Who] will [what] by [when]," ignoring small talk and vague statements like "we should probably look into that sometime."

  3. Action: each extracted commitment becomes a task in my task manager, tagged with the client name and due date if one was mentioned, unassigned tasks default to a 3-day follow-up.

  4. Action: a clean summary (not the full transcript, just the extracted commitments) gets emailed to the client within 10 minutes of the call ending, framed as "here's what we agreed on."


The client-facing summary turned out to be the unexpected win. It reads as attentive and organized, and it's created entirely from the transcript with no extra work from me.


Results after about two months:

  • Zero dropped commitments that I'm aware of, versus at least 2-3 a month before.

  • Clients started referencing "the recap email" back to me, which tells me it's actually getting read and valued.

  • The prompt needed tuning early on, it initially pulled in soft language like "I'll think about it" as if it were a real commitment. Tightening the prompt to require explicit action verbs and timeframes fixed most of that.


The broader point: the value wasn't in recording the call, everyone already does that. It was in forcing the raw transcript through a filter that only keeps what's actually actionable, so nothing depends on my memory of a conversation from three days ago.


If you want the extraction prompt, that's the kind of thing people share in the AI Automation Toolkit community.

Profile picture
Max SaccoProfile picture@saccomax15·Sep 8

I went from 3 reviews to 40 in two months by automating the ask, not the writing

I used to ask for reviews the way most solo founders do: remember to do it, feel awkward about it, send a one-off message a week after the project wrapped, and get maybe a 1-in-10 response rate. Over a year I'd collected 3 reviews total.


The fix wasn't a better ask, it was making the ask happen automatically at the right moment instead of whenever I remembered:


  1. Trigger: project status changes to "delivered" in my CRM.

  2. Delay: 3 days (long enough for the client to actually use what they paid for, short enough that the experience is fresh).

  3. Action: personalized email goes out with a direct link to leave a review (I use a simple typeform that posts straight to my testimonials page and, with permission, Google).

  4. If no response after 5 days, one soft follow-up: "No worries if you're busy, here's the link again in case it got buried."

  5. If they submit, a thank-you email fires automatically and I get a Slack ping to review it before it goes live.


The delay is doing more work than the copy. Asking immediately at delivery catches people before they've actually experienced the result. Asking 3 days later catches them right when the value is obvious and easy to describe.


Results over two months:

  • Response rate went from roughly 10% to 42%.

  • Total reviews went from 3 (all year) to 40.

  • Zero extra time spent per client, the whole thing fires on its own after delivery is marked done.


One thing I'd add if starting over: I initially didn't have the "mark as delivered" step wired tightly enough into my actual workflow, so the trigger sometimes fired late or not at all for the first few weeks. The automation is only as good as the trigger event being consistent, so audit that first.


Social proof compounds like everything else, it just needed a system instead of my memory. If you want the Typeform-to-CRM wiring, that's a common ask in the AI Automation Toolkit community.

Profile picture
Max SaccoProfile picture@saccomax15·Sep 1

The automation that saved me the most money had nothing to do with email or CRM

Everyone talks about automating outreach, follow-ups, onboarding. The one that's actually saved me the most hard cash this year was boring: a monthly subscription audit.


I run a lean operation, but between tools I tried once and forgot to cancel, seat-based SaaS I outgrew, and duplicate tools doing the same job, I was bleeding money quietly. Checking every statement manually was tedious enough that I never actually did it.


So I automated the audit instead of the spending decision:


  1. Trigger: scheduled monthly, first of the month.

  2. Action: Make.com pulls the last 30 days of transactions from my business bank account via Plaid.

  3. Action: filters for recurring charges (same merchant, similar amount, monthly cadence) and cross-references them against a master list I keep of tools I actually use.

  4. Action: anything recurring that's NOT on my active-tools list gets flagged and dropped into an email to me with the merchant name, amount, and last charge date.

  5. I spend 5 minutes reading the email and either confirm "cancel" or "keep," and update the master list.


No AI needed to actually decide anything, just AI/automation to surface the decision instead of me remembering to look.


What it caught in the first three months:

  • Two tools I'd trialed and forgotten, totaling $94/month.

  • One tool I'd upgraded to a higher tier for a project that ended, still billing at the higher rate: $60/month.

  • A duplicate transcription tool I was paying for after switching to a different one and not canceling the old one: $29/month.


That's about $2,200/year from a system that takes 5 minutes of my attention monthly. It's not glamorous, but it beat every revenue-generating automation I built this year in pure ROI, because savings compound the same as revenue does and there's no customer acquisition cost attached to it.


The lesson: not every worthwhile automation makes you money directly. Some just stop you from quietly losing it. Worth an hour to set up if you haven't audited your subscriptions in a while.


Small, unglamorous stuff like this gets traded around in the AI Automation Toolkit community if you want the Plaid setup details.

Profile picture
Max SaccoProfile picture@saccomax15·Aug 25

I stopped taking calls with unqualified leads by adding one AI scoring step before my calendar link

For months my "book a call" link was open to anyone who filled out a form, which meant a chunk of my week went to calls with people who couldn't afford my services or weren't a fit. I didn't want a long application form because that kills conversion, but I also couldn't keep giving away 30 minutes to tire-kickers.


The fix ended up being a single AI scoring step wedged between the form and the calendar, built with Make.com + OpenAI's API:


  1. Trigger: form submission (still just 4 fields: name, email, company, "what are you trying to fix").

  2. Action: the free-text answer gets sent to GPT with a prompt that scores it 1-10 on fit, based on a short rubric I wrote once (budget signals, urgency language, whether the problem matches what I actually solve).

  3. Branch: score 7+ gets an immediate email with my Calendly link. Score 4-6 gets a short qualifying email asking one more question before the link unlocks. Score below 4 gets a polite "here are some free resources" email and no call link.

  4. Every submission and its score logs to a sheet so I can sanity-check the AI's judgment weekly and adjust the rubric.


This isn't about gatekeeping, it's about matching effort to fit. Results after about 6 weeks:


  • Calls booked dropped by roughly 30%, but calls that convert to paying clients went up because the ones I'm taking now are pre-filtered.

  • I reclaimed close to 4 hours a week that used to go to calls that were never going to close.

  • The rubric needed two rounds of tweaking in the first month because the AI was initially too generous with vague "urgent" language. Worth checking your first 20-30 scores manually before trusting it.


The bigger lesson: not every lead deserves the same amount of your time, and you can automate the triage without making the form itself longer or more annoying.


If you want to compare scoring rubrics or see the actual prompt, that's the kind of thing that gets traded around in the AI Automation Toolkit community.

Profile picture
Max SaccoProfile picture@saccomax15·Aug 18

No-shows dropped almost in half after I stopped relying on Calendly's default reminders

I run discovery calls for my consulting work and no-shows were quietly killing my week. I'd block 30 minutes, prep notes, and then eat the slot when someone just didn't show. Calendly's built-in reminder (one email, 24 hours out) wasn't cutting it.


Here's what actually moved the number, built with Make.com + Calendly + Twilio:


  1. Trigger: new booking created in Calendly.

  2. Immediately: confirmation email with the call's actual purpose in the subject line (not "Your meeting is scheduled" — something like "Your automation audit call: what to bring").

  3. 24 hours before: automated email reminder, same as before.

  4. 2 hours before: SMS text via Twilio with the Zoom link and a one-line "reply CANCEL if you need to reschedule."

  5. 15 minutes before: a second SMS, just the Zoom link again, nothing else.


The SMS layer is what changed things. Email reminders get buried; a text at the 2-hour mark doesn't. I also added the "reply CANCEL" option because a chunk of my no-shows weren't people ghosting, they were people who wanted to reschedule but didn't want the friction of finding my email or the booking link again.


Results after about two months:

  • No-show rate went from roughly 22% to 12%.

  • Of the people who used to no-show, a good number now reply CANCEL and rebook instead of disappearing, which is a much better outcome than an empty slot.

  • Total build time was under an hour, and Twilio's SMS costs run me about $4/month at my call volume.


The takeaway: reminders fail when they rely on channels people don't check under time pressure. Email is easy to snooze mentally. A text 2 hours out is not.


If you're bleeding time to no-shows on discovery or sales calls, this is a cheap fix. The AI Automation Toolkit community is where I'd point you if you want the exact Twilio setup.

Profile picture
Max SaccoProfile picture@saccomax15·Aug 12

3 AI automations that saved me 8+ hours a week (steal these)

I run a one-person business and for months my biggest bottleneck wasn't strategy — it was admin. Inbox, CRM, meeting notes. Here's what actually moved the needle once I automated it:


  1. Inbox triage — AI classifies incoming email (lead / support / spam / needs-reply) and auto-labels it before I even open my inbox. Cuts my "what needs my attention" scan from 20 min to 2.


  1. Lead capture → CRM sync — Every Calendly booking or Typeform submission auto-creates a CRM record with enriched notes. No more copy-pasting names into Airtable at 11pm.


  1. Meeting notes → action items — Zoom/Fireflies transcript gets summarized and turned into tasks in Notion automatically. I stopped losing follow-ups entirely.


None of this needs custom code — Zapier, Make, or n8n can all do it if you wire the triggers right. The hard part isn't the tool, it's knowing which workflows are actually worth automating first (hint: start with whatever you do manually more than 3x/week).


Happy to answer questions if anyone's stuck setting one of these up. I write these as done-for-you templates over at AI Automation Toolkit if you'd rather skip the wiring — but even if you build it yourself, start with inbox triage. It's the highest ROI for the least effort.