Activity
Mon
Wed
Fri
Sun
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
What is this?
Less
More

Owned by Jason

A relaxed place to learn AI at your own pace, with real prompts and step-by-step walkthroughs. No jargon required.

1790 contributions to AI Automation Society
#AISChallenge Day 6: an overnight scheduled Claude Code job
Scheduled task, not a loop: Windows Task Scheduler starts Claude Code at 02:00, it reads a queue file, picks a model per job, logs tokens per job to a CSV and writes a morning report. It reads its own previous status file first, so it skips what failed last night. Surprise: the boring part (permissions and a missing Chrome flag) took longer than the jobs. #AISChallenge
0 likes • 12m
That permissions and Chrome flag detour sounds familiar. How does the job tell a permanent failure from a temporary hiccup before it skips it on later nights?
How I turn "I build custom automations" into one offer a business owner can say yes to
A lot of automation pitches in groups like this say some version of "I build custom automations for your business." The owner reading that has to figure out what they'd get, what it costs and how long it takes. Most of them don't bother. This is the order I go through when I package a single service: 1. Write the outcome the way the buyer would say it, with a number and a deadline. "More booked jobs" becomes "20 more booked jobs a month within 60 days." 2. List everything that stops them from getting that outcome. I aim for 15 or more. Each item becomes a deliverable or a bonus. 3. Fix the scope, price and timeline, and name the offer after what it does and how long it takes, something like "14-Day Missed-Call Recovery." 4. Add a few bonuses, each one aimed at a specific objection: setup done for them, templates, a short training video, 30 days of support. 5. Tie the guarantee to something the client controls. If they do their part and still don't get the result, you keep working at no extra cost until they do. 6. Only use urgency that's real, like an actual cap on how many clients you onboard a month. 7. Set a ladder: a free audit, then a $500 to $1.5k setup, then a $1k to $3k monthly retainer. What I end up with is one page: who it's for and who it isn't for, deliverables, bonuses, guarantee, price, timeline, a few headline options, and the five objections I'm most likely to hear with an answer for each. Step 2 is the one people skip. Writing out 15 problems is tedious, but that list ends up being most of your sales page and most of what you say on the call. What front-end offer are you selling right now, and what does it cost?
0 likes • 15m
The guarantee is where a clear offer gets tricky if you don't know the owner's starting point yet. A paid workflow audit can set the baseline, like how many calls are missed and how many of those callers become booked jobs, before you commit to a result. It also lets you check whether the data exists and what the owner can realistically control. Then you can agree on a measurable outcome and scope the implementation around what you actually found.
I tried to send one alert to a dead webhook 28 times. Here's what the last one said.
I broke my own alert on purpose. The webhook it sends to answered "500" and stayed down. Here's what happened over 6 hours (simulated): 30 sec → retry 1 min → retry 2 min → retry 5 min → retry 10 min → retry then every 15 min… 28 attempts. 5 hours 48 minutes. Zero delivered. Then it stopped on purpose, because an alert that late isn't news anymore. Then the workflow came back to life. And this is the message that arrived: "It is producing again: the latest run produced 40. You did not hear that it broke: that alert never got through (28 attempts, the webhook last answered 500)." I did not expect to care this much about one sentence. It tells you what you missed instead of pretending nothing happened. Genuine question: if your alert can't get through, would your tool tell you afterwards? Or would you never know?
1 like • 43m
That recovery message matters, because a working system can hide the fact that an alert was missed. I'd record failed alerts somewhere independent of the webhook delivery path, then include the missed incident and last delivery error in the recovery message. For time-critical failures, I'd use a separate escalation channel too, so nobody has to wait for the original webhook to recover.
Advice for Nobody Follow
What is the ONE advice which nobody should follows in agentic AI journey?
0 likes • 1h
I'd be wary of anyone telling you to automate everything at once. It's tempting when you see what agents can do, but a workflow you don't understand is hard to improve when something goes wrong. Pick one workflow you know well, decide what success looks like, and keep a person reviewing the output before it leads to action. Once it's reliable, use what you learned on the next one.
How I would automate a new website lead for a service business, step by step
Most service businesses do not lose leads because of traffic. They lose them in the first five minutes, when a new enquiry sits in an inbox and nobody replies. Here is the simple setup I use to fix that: 1. The website form sends the lead to n8n through a webhook. 2. n8n cleans the data, checks for duplicates, and creates the contact in GoHighLevel. 3. The business owner gets an instant notification with the lead's name, number and message. 4. The lead gets an automatic reply within a minute, so they know they were heard. 5. If nobody follows up within a set time, a reminder task is created automatically. The part that usually breaks is step 2. If the fields from the form do not match the CRM fields exactly, leads arrive with missing phone numbers and the follow-up fails. Nothing here needs expensive tools. It needs the boring parts connected properly. How are you handling the first five minutes after a new lead comes in?
0 likes • 2h
Missing phone numbers are easy to overlook when the workflow looks like it ran fine. I'd validate the required contact fields before creating the GoHighLevel record, then alert the owner with the submitted details if validation fails so the lead doesn't disappear. I'd also track each lead until a person has followed up, with a reminder if it stays untouched. How are you tracking whether that human follow-up actually happened?
1-10 of 1,790
Jason Elam
7
1,032 points to level up
@jason-elam-2821
AI Strategist & Consultant. I help SMB owners build custom AI Powered Solutions to help them empower their employees, NOT replace them.

Active 7m ago
Joined Feb 16, 2026
Powered by