Activity
Mon
Wed
Fri
Sun
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
What is this?
Less
More
3 contributions to Automators
half my client automations failed silently until i put a watcher on them
built a scrape to sheet pipeline for a client that fed their quote tracker. ran clean for three weeks, then the site quietly changed its markup and the sheet just kept growing with empty rows. nobody noticed for a week because the dashboard looked normal. that client taught me the lesson i now sell with every build: the automation is only half the deliverable, the other half is knowing the moment it stops working. every build i ship now gets a daily run log and a failure ping, so a broken step gets caught in hours instead of weeks. curious how the rest of you watch the stuff you build. i kept getting burned before i made this automatic.
0 likes • 1d
the tool i used to do this was wajo, let me know if you want an invite to try it out yourself
I build automations for clients all day, then let an AI agent audit my own backlog
Marcus's skill-of-the-week posts keep reminding me the build is the fast part. What was slow for me was deciding what was worth building at all. I run a small AI automation agency, and for months my real bottleneck was my own ops: scoping new builds, chasing follow-ups, checking whether work I'd already done ever got invoiced. So I changed the order of operations. Before I write a new workflow for anyone, an AI agent goes through my own backlog and hands me a ranked list: leads nobody followed up on, unbilled work, reports nobody asked for. Last week it flagged a chunk of unbilled work in one client account before I'd written a single line of that automation. The build then took an afternoon. Curious whether anyone here runs an agent over their own business before they sell automations to clients. Feels like the undervalued side of the stack.
0 likes • 4d
the tool i used to do this was wajo, let me know if you want an invite to try it out yourself
The 24-hour $1,000 stress test
Not a client deliverable. Me. “I have 24 hours before I go broke and end up homeless. Help me make $1,000. Any way you can.” One prompt, no workflow built, no connectors wired up. I wanted to see what an agent does with zero scaffolding. It went for my own data: inbox, contacts, old threads. Flagged a refund trail, an unbilled job, a lead that went cold, and a LinkedIn message I never opened. Then it built the plan and the messages to send. If you build automations, this is the interesting part: the whole audit-then-act loop ran off one natural language prompt. The agent decided what to check, in what order, and what needed me versus what it could draft itself. Follow-ups are going out, receipts when they land. Run the prompt on your own data, link in comments.
0 likes • 6d
Free and unlimited, grab it here: https://wajo.ai/f/70732574a02d2a8d2540f3acee9b34f1 Run it on your own pipeline and come back with what it found 👀
0 likes • 6d
@Mouldi Nouri Good catch, that's the exact failure mode. Mine read the inbox live rather than working from memory, but I still treated every draft as a first pass and checked the numbers before anything went out. Agent drafts, human signs off. Curious what it pulls from yours, link's in the first comment.
1-3 of 3
Rishabh Singh
2
14 points to level up
@rishabh-singh-4142
Entrepreneur

Online now
Joined Oct 27, 2026