Caretaker — rescue and maintenance for orphaned AI automations

1. The idea

A 493-upvote r/automation post describes the pattern from the inside: the app "works" but it's "built in a way that only the original dev can maintain — and even that won't last long. And guess what happens next? The original dev disappears." On the buyer side the same story runs quieter: a Zapier operator whose business-critical flow "stopped triggering around 0700 this morning for no apparent reason" while "the zap history does not show any holds or errors." Thousands of SMBs bought automations from the 2024–26 agency wave; the churn pattern is documented — builds fail "when the client's actual workflow gets messy," the client leaves at month three, and the founder moves on. What's left is an orphan: a black box wired into the client's revenue.

Caretaker adopts orphans. Intake: a read-only health check of whatever exists (n8n, Make, Zapier). Rescue: stabilize, add error handling and monitoring, and produce a plain-English handbook of what the system actually does (HandoverKit output). Then a monthly care plan — monitoring with real alerts, fixes when APIs change, small changes on request, a quarterly review. Flat $750 rescue, $99–$249/mo care, and a white-label tier where agencies hand Caretaker their maintenance backlog.

2. Fact strip

3. The numbers

4. Why now

The orphan supply is a lagging function of the 2024–26 build wave, and the wave is aging right now. Our own trend data (Google Trends, Aug 2026) shows the tooling term "n8n" cooling at −42% YoY while "ai automation agency" runs +170% — a market where first-generation builds outlive first-generation builders. The failure mechanics are documented as of July 2026: course-taught founders "can't deliver when the client's actual workflow gets messy. Client churns at month three. Founder blames the niche. Repeat." Every one of those churns mints a Caretaker prospect.

Two softer accelerants. The EU AI Act's deployer obligations — including ongoing monitoring of AI system operation — became enforceable August 2, 2026 (DLA Piper), giving EU-exposed clients a compliance reason to have someone accountable for their AI systems. And the maintenance-plan category has a proven playbook next door: WordPress care plans matured into a whole ecosystem at $79–$447/mo (WP Buffs, 2026) — automations are where WordPress sites were a decade ago.

Honest caveat: there is no single dated forcing function that makes an SMB owner wake up needing rescue — the trigger is their own breakage, which arrives one client at a time. That caps timing at 7.

5. The receipts

"Sure, the app 'works' but it's built in a way that only the original dev can maintain - and even that won't last long. And guess what happens next? The original dev disappears…" — r/automation · AutomationLikeCrazy · May 2025 · 493↑, 121 comments · thread

"I'm curious how people running business-critical Zaps handle monitoring. Error notifications are one thing, but what about: Zap runs but output is wrong · trigger stops arriving · API behavior changes · Zap hasn't run when it normally should" — r/zapier · kumarshikhardeep1 · Aug 2026 · thread

"It stopped triggering around 0700 this morning for no apparent reason. The triggering spreadsheet has not changed. […] The zap history does not show any holds or errors." — r/zapier · CucumberParty3388 · Aug 2023 · thread

"This was working fine for about a month until today, without any changes to the zap." — r/zapier · Defiant_Brain_9219 · Aug 2023 · thread

"…lands two clients at 1.5k each, then can't deliver when the client's actual workflow gets messy. Client churns at month three. Founder blames the niche. Repeat." — r/Entrepreneurship · Seblewongel12 · Jul 2026 · thread

6. Whitespace

The gap: a targeted search for services that take over automations "built by another agency" returns only DIY monitoring guides and tools — no player markets adoption of orphaned builds. Agencies sell retainers for their own builds ($500–3,500/mo norms); freelancers sell hours; monitoring tools sell dashboards to technical operators. Nobody sells "we take responsibility for the thing someone else built."

The wedge: adoption, not construction. The intake health check + stabilization + handbook is a productized on-ramp no hourly freelancer offers, and the ongoing accountability ("call us when anything breaks") is what the burned buyer actually wants. Incumbent freelancers can't respond without becoming a different business — recurring responsibility is precisely what hourly workers avoid.

7. Proof & signals

• Ongoing automation retainers already run $500–$3,500/mo, with agencies spending 3–4 hrs/client/mo on maintenance at ~$1,500/mo average (The Crunch, 2026; Zaps Studio).
• Zapier consultants charge $40–$150/hr (specialists $200+); fixed troubleshooting projects run $300–$3,000 (GolmTech, 2026).
• The WordPress maintenance market validates the category shape: WP Buffs alone runs plans from $79 to $447/mo with a whole ecosystem of alternatives (G2 pricing, 2026; comparison).
• A cottage industry of n8n monitoring guides appeared in 2026 (API Status Check, Speedrun Ventures) — demand for reliability exists, but every solution assumes a technical operator, not an SMB owner.

8. Who you're up against

• Another freelancer + hope — INCUMBENT. Upwork/Zapier Experts at $40–200/hr. Transactional: fixes the symptom, adds no monitoring, leaves the same orphan behind.
• The original builder — when reachable. The whole premise is that increasingly they aren't.
• Automation agencies' own retainers ($500–3,500/mo) — maintain what they built; taking over strangers' spaghetti is exactly the work they refuse.
• Monitoring tools / n8n Error Trigger — DIY dashboards for technical operators; an SMB owner can't act on an alert.
• Platform AI assistants — n8n/Zapier ship AI debugging help; erodes the simple-fix layer over time, not the accountability layer.
• flospect — documents flows for builders; adjacent, not a maintainer.
• Do nothing until it hurts — the true default; most orphans run unmonitored until a silent failure costs real money.

9. The verdict

Reasons to build

• The failure receipts are abundant and cross-platform: silent failures with clean logs (r/zapier, twice), builds only the vanished original dev could maintain (493↑), and a documented churn-at-month-three pattern minting orphans continuously.
• The money is already flowing at the right shape: $500–3,500/mo retainer norms and $300–3K fix projects mean Caretaker prices under existing behavior, not against a free alternative — unlike HandoverKit.
• The category playbook exists next door: WordPress care plans proved SMBs pay $79–447/mo indefinitely for "someone is responsible" — automations are earlier on the same curve, with no WP Buffs yet.
• Recurring responsibility is a moat a prompt can't replicate: unlike documentation, "we answer when it breaks at 7am" can't be DIY'd by the client's ChatGPT, and switching maintainers is high-friction once trust and monitoring are in place.
• Portfolio synergy: every rescue produces a HandoverKit-style handbook, and every HandoverKit agency is a referral source for maintenance overflow.

Reasons to not build

• Nobody searches for this: rescue-shaped queries returned no measurable search volume anywhere in this research; demand surfaces one breakage at a time, so acquisition is referral-and-content grind with no paid shortcut.
• Channel mismatch on the buyer: Rui's pipeline reaches agency founders, not SMB owners. The white-label/referral route depends on agencies cooperating with someone their clients could see as their replacement.
• Adverse selection is structural: orphaned builds are disproportionately the worst builds. A $750 flat rescue on unknown spaghetti will sometimes eat 20+ hours; misprice the intake and the core offer loses money.
• Liability is real: adopting a workflow that pushes numbers into an ERP means owning the next "one wrong number" (the trust dynamic documented here) — E&O insurance and careful SLAs are needed before client ten, not after.
• The services treadmill fights the profile: at 3–4 hrs/client/mo industry norms, 100 clients is 300+ hours/month — the business only stays solo-sized if tooling crushes that number, otherwise it becomes hiring.
• Platform self-healing compresses the bottom of the market: n8n and Zapier are shipping AI-assisted debugging; the simple-fix revenue layer shrinks over time, leaving only judgment-heavy work.

10. Founder fit

The idea demands: distribution 6/10 · domain 8/10 · sales 7/10 · technical 8/10 · capital 2/10

Best for: a technically deep operator who can read anyone's spaghetti, productize intake ruthlessly, and build the monitoring tooling that keeps per-client hours near zero — with a referral network into the agency world.

Wrong for: anyone who needs scale fast (this compounds slowly, client by client) or who can't stomach being on the hook when someone else's build fails.

The Rui check: strong. Recurring revenue in a specialized vertical with high switching costs is the Innovator's stated sweet spot, and technical 9 vs. demand 8 means the hardest part of the job — adopting unknown systems and tooling away the maintenance hours — is his surplus. Distribution demand (6) is the mildest of any channel-dependent idea yet researched because the motion is referrals from a network he already works daily, not audience building. Two constraint checks (profile updated 2026-08-29): budget is under $1K per bet, so E&O insurance (~$500–1K/yr) waits until the first paying care clients fund it — acceptable for warm-network calibration rescues, not for scale. And the goal is $5K MRR in 12 months, while the conservative napkin exits year one at roughly a $2K/mo run rate — hitting goal needs ~25–30 care clients plus 2–3 white-label desks by month 12, above napkin but inside the ceiling math. BUILD stands; the goal-gap is the number the calibration rescues must inform.

11. Value ladder

12. The plan

Days 1–30: build the intake instrument first — a scripted read-only audit (n8n/Make/Zapier export → risk map) so the $750 rescue can be scoped and capped before committing; adopt 2–3 orphans from the warm network at cost to calibrate hours-per-rescue. Days 30–60: pitch the white-label desk to 20 agency founders already in the Aether pipeline ("keep the client, hand us the maintenance"); answer the standing r/zapier monitoring threads with the health check. Days 60–90: standardize the monitoring stack (error triggers + heartbeat + weekly plain-English report — the report is the retention device), publish two rescue case studies. Hardest part: pricing the rescue on unknown spaghetti — solved by the audit-first sequence and a scope cap with an hourly fallback beyond it.

13. Napkin math — year one

Weakest assumption: the 75% rescue→care conversion. Cheapest test: the first three warm-network rescues — if stabilized clients don't buy monitoring at $149/mo, the model is a fix shop, not a care business.

14. The ceiling

$500K–$1M ARR: ~200–350 care clients at $150–250/mo blended plus 10–20 white-label desks — if monitoring tooling holds per-client time under one hour/month. Past that it's a hiring business, which caps it as a solo asset. The upside surprise would be the tooling itself becoming the product (a "WP Buffs for automations" platform) — but that's a later decision, not this one.

15. Playbook prompts

• Build plan: "Read reports/2026-08-29-caretaker.md. Scope the intake instrument from section 12 (workflow export → risk map): stack, what ships in week one, and how the $750 scope cap is enforced mechanically."
• Roast: "Read reports/2026-08-29-caretaker.md and roast it as (a) an agency founder who'd rather keep the retainer, (b) an SMB owner burned twice who trusts nobody, (c) an insurer pricing my E&O. No mercy."
• Money model: "Read reports/2026-08-29-caretaker.md. Pressure-test $99/$149/$249 care tiers against the 3–4 hrs/client/mo industry norm and find the tooling threshold where margin survives 100 clients."

16. Verdict & next move

BUILD · medium confidence

This is the strongest fit yet scored: recurring revenue, specialized vertical, high switching costs, technical surplus, and — unlike HandoverKit — it prices under money already moving ($500–3,500/mo retainers, $300–3K fixes) rather than against a free habit. The two honest risks are acquisition (nobody searches for rescue; it's a referral business) and the services treadmill (solved only by tooling). Both are testable cheap: the next move is adopting 2–3 orphans from the warm network at cost this month to calibrate real hours-per-rescue and test the rescue→care conversion — before building anything. Cost: ~3 evenings, $0. Medium confidence rather than high solely because every conversion number past the pitch count is still an assumption.