Somebody has to answer the phone when a workflow nobody owns stops running at 7am — and right now nobody does

§ 01Thesis

Caretaker sells recurring accountability for automations whose builders have vanished — the one thing in this category that a burned buyer cannot get from a freelancer, a monitoring dashboard, or their own ChatGPT.

What it is

A productised maintenance service for existing n8n, Make and Zapier workflows that the original builder no longer supports. Three motions, in order: a free read-only health check that produces a risk map; a $750 flat rescue that stabilises the workflow, adds error handling and monitoring, and delivers a plain-English handbook; and a $99–$249/mo care plan that monitors, alerts, fixes, and reports weekly. A fourth motion — a $500+/mo white-label desk where an agency hands Caretaker its maintenance backlog and keeps the client relationship — is where the money actually is, for reasons § 09 computes.

Who it is for

Two buyers, one of whom signs. The agency founder with a backlog of past-client automations they no longer want to maintain, and the SMB operator whose revenue-critical flow is a black box. The report is explicit that the founder's pipeline reaches the first and not the second. This plan builds the whole go-to-market around that fact rather than wishing it away.

Why now

• The orphan supply is a lagging function of the 2024–26 build wave, and the wave is aging now verified
• Tooling interest is cooling (n8n −42% YoY) while agency formation runs hot (ai automation agency +170%) — first-generation builds are outliving first-generation builders verified · Google Trends, Aug 2026
• The churn-at-month-three pattern is documented as of July 2026 and mints a prospect every time it fires verified
• EU AI Act deployer obligations, including ongoing monitoring of AI system operation, became enforceable 2 August 2026 — a compliance reason for EU-exposed clients to have someone accountable verified · DLA Piper

"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

The one reason it survived

Every other idea in this space competes with a free habit. Caretaker does not. Automation retainers already run $500–$3,500/mo and fixed troubleshooting projects already run $300–$3,000 verified. The money is moving; Caretaker prices under it. That is the single structural advantage, and it is why the verdict is BUILD rather than a polite pass.

Build · 7.3/10 · medium confidence

---

§ 02The buyer

The agency founder signs the cheque; the SMB operator supplies the pain — and the founder's only warm channel reaches the first one, so the first one is the primary ICP.

Primary ICP — the agency founder (the signer)

• RoleOwner-operator or technical co-founder of an AI automation, marketing-ops or workflow agency verified — this is the population the founder's LinkedIn pipeline already targets
• Company shape1–10 people, service revenue, a portfolio of past-client builds still running in the wild, no dedicated support function assumed
• The pain they ownMaintenance requests from clients they no longer bill, or clients they billed and lost. Industry norm is 3–4 hrs/client/mo of maintenance against a ~$1,500/mo average retainer verified, so a lapsed client is pure cost or pure guilt
• The triggerA past client emails "the thing you built stopped working." The agency either does it free, quotes awkwardly, or ignores it
• What they buyA desk: hand Caretaker the backlog, keep the client relationship, keep the logo, stop doing unpaid triage
• How they are reachedDirect LinkedIn outreach on the founder's existing AgentForge pipeline. Verified volume: 20 agency founders currently pitched verified. Per the founder profile, these are pitched directly as buyers, not asked for referrals

Secondary ICP — the orphaned operator (the one who bleeds)

• RoleOwner-operator or the single ops person at a 5–50 employee business; the individual who personally notices when the flow dies assumed
• What they runOne to five Zapier/Make/n8n workflows sitting on a revenue path: lead routing, invoicing, order sync, client onboarding
• What makes them a prospectThe builder is gone or unresponsive, and they cannot read the workflow themselves
• How they are reachedNot by search. The report is unambiguous: rescue-shaped queries return no measurable volume anywhere verified. They are reached by answering the standing monitoring threads on r/zapier and r/n8n, and by inheritance through an agency desk

"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

How many of them exist

The report does not size this population and neither will this plan. What is verifiable is the door count: 20 agency founders in the current pipeline verified, each holding an unknown backlog of past-client builds. The number of workflows behind each door is the single most valuable unknown in the business, and § 13 makes measuring it part of the first test. If the median agency backlog is two workflows, the desk is a $150/mo product and the thesis is weaker than the report thinks. If it is ten, one desk is a $1,250/mo product and the goal is easy.

---

§ 03The job today

The status quo is not a competitor product — it is a client discovering a dead workflow after the damage, paying $300–3,000 to a stranger to make the symptom stop, and being left with the same orphan.

The default path, step by step

1. The workflow fails silently. Not with an error — with nothing. The r/zapier receipts show this twice: "stopped triggering around 0700 this morning for no apparent reason… the zap history does not show any holds or errors" verified and "this was working fine for about a month until today, without any changes to the zap" verified

2. Nobody notices for hours or days, because detection is a human noticing an absence

3. Someone does the work by hand in the meantime — the true spreadsheet competitor here is a person re-keying data

4. The owner tries to reach the original builder. Increasingly they cannot; that absence is the entire premise verified

5. They hire a freelancer at $40–150/hr, $200+ for specialists, or commission a fixed troubleshooting project at $300–$3,000 verified

6. The freelancer fixes the symptom, adds no monitoring, and leaves. The orphan is now an orphan with a patch verified

Where the cost actually lands

The part that makes this sellable

The cost does not land in a budget line. It lands in the owner's evening, in a missed invoice, in a customer who never got their confirmation email. That is why the buyer cannot compare Caretaker to a number they already track — and also why the anchor in § 08 has to be the $1,500/mo the agency would have charged, not the diffuse cost of the outage itself. People buy against a price they have seen quoted, not against a loss they have absorbed.

---

§ 04Market

The goal is fourteen customers: roughly nine SMBs on care plans and five agencies on desks. That is the entire market this business needs to find in year one.

The bottom-up arithmetic to $5,000 MRR

Start from the goal and work backwards, testing each shape against the founder's hour ceiling (5–10 hrs/week = 21.7–43.3 hrs/month, midpoint 32.5) verified · founder profile.

Mixed shape, shown row by row:

Why the pure-care path is arithmetically closed

This is the finding that reorganises the plan. Care clients arrive by converting rescues, and rescues cost hours. At 0.75 conversions/month (one rescue a month at 75% conversion) and 8%/month churn assumed, the steady-state client count is 0.75 ÷ 0.08 = 9.4 clients. Care revenue plateaus at roughly $1,400/mo and stays there forever, no matter how long you run. To reach 25 care clients you need 2 net adds/month, which needs ~2.7 rescues/month at 8 hrs each = 21.6 hrs of rescue delivery, plus 25 × 0.9 = 22.5 hrs of care delivery = 44.1 hrs/month. That is above the 43.3-hour absolute ceiling, before a single hour of selling.

What is not claimed here

No TAM figure. The report supplies none that would survive contact with this business, and a "$X billion automation market" number would be decoration. The only honest market statements available: retainer norms are $500–3,500/mo, fix projects are $300–3,000, WordPress care plans sustain $79–447/mo indefinitely as a category precedent [all v:verified], and the founder can reach 20 agency doors today verified.

---

§ 05The product

The product is a computed risk map with a generated narration on top — the LLM never asserts a fact about a workflow it did not parse, because the whole business is trust and one hallucinated claim about a client's system ends it.

The core mechanic

Three components, in build order.

• The intake instrumentIngests a workflow export (n8n JSON, Make blueprint JSON) and emits a deterministic risk map: node graph, trigger type and expected cadence, external API dependency list, credential inventory, error-path coverage as a percentage of nodes, retry configuration, hard-coded IDs and magic values, unversioned code nodes, and every path that can fail without raising. This is parsing, not inference. It produces the free health check and the scoped, capped quote for the rescue
• The monitoring stackThree detectors matching the three failure modes the receipts name. Error-trigger webhooks catch loud failures. A heartbeat against declared expected cadence catches "hasn't run when it normally should." Output assertions — row count non-zero, required field non-empty, schema unchanged — catch "runs but output is wrong." All three are the exact list from the r/zapier monitoring thread verified
• The narration layerAn LLM writes the plain-English handbook, the incident explanation, and the weekly report, strictly over the computed map and the observed event log. The report calls the weekly report "the retention device" and that is right: it is the artefact that makes an invisible service visible every seven days

Computed versus generated

Where the data comes from

Client workflow exports supplied under read-only access; platform error-trigger webhooks pointed at a Caretaker endpoint; run history where the platform API exposes it; and a client-declared expected cadence captured at intake because no platform reliably tells you what "should" have happened.

The one technically hard part

Detecting absence. A failure that raises an error is trivial; the receipts are all about failures that raise nothing. Heartbeat detection requires knowing the expected cadence, and cadence is only partly inferable from history — a workflow that fires on inbound leads has no schedule, so absence detection has to be statistical (an inter-arrival window learned from history) with a tolerance the client can tune. Get this wrong in the noisy direction and clients ignore alerts; get it wrong in the quiet direction and a silent failure gets through, which is the one failure that cannot happen. Second hard part, less interesting but more annoying: Zapier has no clean workflow export, so Zapier coverage in v1 is a manual walkthrough under read-only account access, not a parse.

Stack

Next.js on Vercel, Supabase for the event log and client records, an LLM API for the narration layer — all of it stack the founder already runs at production quality verified · founder profile, technical 9. No new infrastructure spend.

---

§ 06Scope

Nothing that requires a client-facing interface ships in v1, because the deliverable is an email and a person who answers, and every pixel spent before client twenty is a pixel stolen from the hour budget.

Cut, with the condition that reverses the cut

• Zapier deep-parseZapier lacks a clean export. v1 handles Zapier by manual walkthrough. Earns back when five paying clients are Zapier-primary, or when Zapier ships an export API
• Client-facing dashboardThe weekly plain-English email is the interface. Earns back at 25 monitored workflows or when three separate clients ask unprompted
• Self-serve signup and billing portalStripe payment links and manual onboarding. Earns back at 20 care clients, when manual invoicing exceeds an hour a month
• Auto-remediation / self-healingEvery fix is human-approved in v1. Adopting a workflow means owning its output; an auto-fix that pushes a wrong number into a client's ERP is the liability event described in the report verified. Earns back when the same failure class recurs five or more times across clients and the fix is provably idempotent
• White-label branded portal for agenciesDesk v1 is unbranded PDFs and an email alias. Earns back at desk #3
• 24/7 responsev1 SLA is next business day, 09:00–18:00 Europe, on the $149 tier. The report's own promise of "we answer when it breaks at 7am" is aspirational for a solo founder on 5–10 hrs/week and must not be written into a contract. Earns back when a tier prices it explicitly and there is a second pair of hands
• New automation buildsCaretaker never builds. This is not a hours-saving cut, it is a positioning cut; see § 11. Never earns back
• SOC 2 / formal security programmeEarns back at the first procurement questionnaire
• E&O insurance$500–1,000/yr, deferred until the first paying care clients fund it, per the report's explicit constraint check verified. Earns back the moment there is $1,000 of accumulated net revenue, which the § 09 model reaches in month 7. This is a cut with a live risk attached, not a free one — see § 14
• Hiring or subcontractingOff the table until measured per-client hours are verified under 1.0/month. The report is blunt that hiring caps this as a solo asset

---

§ 07Unit economics

At a target 0.75 hours per client per month the contribution margin is 56%; at the documented industry norm of 3.5 hours it is minus $123 — the entire business is a bet on one number, and that number is measurable in month three.

Cost to serve one $149/mo care client, one month

The tooling threshold, computed

At the verified industry norm of 3.5 hrs/client/mo, a $149 client costs $271.92 to serve and loses $122.92 every month. The report's warning that "the business only stays solo-sized if tooling crushes that number" is not rhetoric — it is the difference between a 56% margin and a negative one, and the crossover is at 1.86 hours.

Rescue economics, separately

Break-even is 9.68 hours. The flat $750 is therefore only viable behind a mechanically enforced cap: the intake instrument produces the risk map, the risk map produces the quote, the quote states 8 hours included with $125/hr assumed beyond, and anything the audit scores above a complexity threshold is quoted hourly from the start and never flat. The report names adverse selection as structural — orphaned builds are disproportionately the worst builds verified — so the cap is not a nicety, it is the thing that stops the frontend offer from funding client losses.

---

§ 08Pricing

The tiers separate on response time and change work, never on monitoring — monitoring is in every tier because it costs almost nothing and it is the only part the buyer can feel weekly.

The ladder

What separates the tiers

• Watch → CareBreak-fix moves from metered to unlimited. This is where the buyer stops calculating and starts trusting, which is the whole point of the category
• Care → Care+A response-time commitment and an hour of change work. Care+ is for the client whose workflow sits directly on revenue and who will pay for a shorter window
• Desk pricingThe report's floor is $500/mo. § 04 shows the goal shape needs $750, which the +$75/workflow structure reaches at four workflows. Price the desk per backlog size from day one; a flat $500 for an unbounded backlog is the adverse-selection problem again, wearing a different hat

The ROI sentence

$149 a month is a tenth of the ~$1,500 a month the agency that built this would charge to keep maintaining it, and less than the $800 you will spend on the next emergency fix — except you find out before your customer does.

Both anchors are verified: ~$1,500/mo average agency retainer and $300–3,000 per fixed troubleshooting project verified. This is the pricing advantage the report identified as the reason to build — Caretaker sits under money already moving rather than against a free habit, unlike a documentation product.

Blended care ARPU, stated

Assumed tier mix 30% Watch / 50% Care / 20% Care+ assumed gives (0.30 × 99) + (0.50 × 149) + (0.20 × 249) = $154.00. The model in § 09 uses $149 rather than $154, a deliberate 3% haircut for launch discounts and the first-three calibration clients who will be grandfathered.

---

§ 09Financial plan

Twelve months of this plan on 5–10 hours a week lands at $1,974 MRR — 39% of the $5,000 goal — and the honest reason is that the hour ceiling caps rescue throughput, which caps care clients at a steady state of nine.

Model inputs, all stated

Month by month

Cash costs exclude founder time; this is a service business and the founder's hours are the real cost, budgeted in § 15. E&O premium enters at month 7 (~$85/mo) once accumulated net revenue exceeds $1,000, per the report's constraint. Year-one revenue of $22,704 sits inside the report's $15K–$35K band, slightly below its ~$25K mid-case, because this model nets out churn where the napkin did not.

Blended ARPU across all recurring customers at month 12: $1,974 ÷ 8.5 customers = $232/customer/month [computed].

Hour reconciliation

The plan requires 412 hours, which is roughly 8 hours a week sustained for twelve months with no slack for holidays, AgentForge crunch, or a rescue that goes badly. At 5 hours a week it does not run at all; the tooling gets built and about four rescues get delivered.

The goal gap, stated plainly

The founder's goal is $5,000 MRR at month 12. This plan reaches $1,974. The gap is $3,026/month and it is not a motivation problem, it is arithmetic:

• Care revenue plateaus. One rescue a month at 75% conversion against 8% churn settles at 9.4 clients and about $1,400/mo, permanently
• Adding care clients means adding rescues, and rescues cost 8 hours each — the throughput limit is the hour ceiling, not demand
• Reaching 25–30 care clients, as the report's goal-gap note requires, needs 44 hours a month of delivery against a 43-hour absolute ceiling

Three ways the gap could close, honestly assessed:

---

§ 10Competition

Nobody in this market sells responsibility for a system they did not build, and the reason is that responsibility is unpleasant — which is exactly why it is defensible.

The field

• Do nothing until it hurtsTRUE DEFAULT. Most orphans run unmonitored until a silent failure costs real money verified. Gets right: it is free, and for non-critical workflows it is correct. The gap: it has no answer for the revenue-path workflow, and the buyer only discovers this after the incident. Caretaker's entire acquisition problem is that this competitor wins until it catastrophically doesn't
• The manual re-dothe human spreadsheet. When the flow dies, someone does it by hand. Gets right: instant, no procurement. The gap: it scales with volume and it hides the failure from anyone who could fix it
• Another freelancer and hopeINCUMBENT. Upwork and Zapier Experts at $40–200/hr verified. Gets right: cheap, available, genuinely competent at the fix. The gap: transactional by design. Fixes the symptom, adds no monitoring, leaves the same orphan behind. The report is right that recurring responsibility is precisely what hourly workers avoid — they cannot respond to Caretaker without becoming a different business
• The original builderGets right: knows the system. The gap: increasingly unreachable, which is the premise. When reachable, Caretaker loses and should lose
• Automation agencies' own retainers$500–3,500/mo verified. Gets right: full accountability, deep context, established relationship. The gap: only for what they built. Taking over a stranger's spaghetti is the work they explicitly refuse — and that refusal is the white-label desk's entire product-market fit
• Monitoring tools and n8n Error TriggerGets right: real detection, often free, technically excellent. The gap: they sell dashboards to technical operators. An SMB owner cannot act on an alert, and the whole cottage industry of 2026 n8n monitoring guides assumes a technical reader verified
• Platform AI assistantsn8n and Zapier are shipping AI debugging help. Gets right: zero marginal cost, always available, improving. The gap: it erodes the simple-fix layer, not the accountability layer. Nobody's ChatGPT notices that a workflow did not run
• flospectDocuments flows for builders. Adjacent, not a maintainer. Gets right: the documentation artefact. The gap: documentation is not a promise to answer

The gap Caretaker walks into: a targeted search for services taking over automations "built by another agency" returns only DIY monitoring guides and tools — no player markets adoption of orphaned builds verified.

The precedent that makes this a category and not a job

WordPress maintenance. WP Buffs alone runs plans from $79 to $447/mo with an entire ecosystem of alternatives verified. SMBs demonstrably pay indefinitely for "someone is responsible." Automations are a decade behind on the same curve with no WP Buffs yet. That is a precedent, not a proof — but it is the right shape.

---

§ 11Positioning

"They're a maintenance plan for the automations somebody else built — they watch them, and they fix them when they break."

That is the sentence a client repeats to a colleague. It contains no technology, no AI, and no verb the buyer does not already understand from their WordPress plan or their boiler service contract.

For the agency founder, a different sentence

"Keep the client. Hand us the maintenance."

Five words of it are reassurance. The agency's fear is that Caretaker becomes the client's new vendor, and the report flags this as a live structural risk. Everything about the desk is built to disarm it: unbranded reports, no direct client relationship without the agency's introduction, and a written non-solicit on new build work. The desk is deliberately the less profitable-looking product so that it is obviously not a land grab.

What this is explicitly not

• Not an automation agencyCaretaker never builds a new workflow. Not as a favour, not as an upsell. The moment it builds, it competes with the agencies that are its channel, and the channel closes
• Not a monitoring toolThere is no dashboard to log into and no product to evaluate. The deliverable is an email every week and a human who replies
• Not documentationThe handbook is an artefact of the rescue, not the offer. Documentation is a thing a client's ChatGPT can approximate; being awake at 7am is not
• Not a staffing solutionNot fractional ops, not a retained developer, not hours in a bucket. The unit is a workflow under care, not a person under contract

Why the wedge must stay this narrow

The founder profile warns of drift toward over-systemising and the report warns of the services treadmill. Both failure modes start the same way: a client asks for something adjacent, it is said yes to, and the offer stops being productisable. The scope of Caretaker is defined by a single question — is this workflow currently under care? If yes, fix it. If no, it is a rescue quote or a decline.

---

§ 12Go to market

The first channel is direct LinkedIn outreach to agency founders on the existing AgentForge pipeline, pitched as buyers of a desk — not asked for referrals — because that is the only warm access the founder verifiably has.

The channel, and why it and not another

The report is explicit that nobody searches for rescue: rescue-shaped queries returned no measurable volume anywhere in the research verified. There is no SEO play, no paid play (budget under $1,000 rules it out anyway verified), and no audience play (distribution 5/10, no large audience verified). What exists is 20 agency founders already being pitched through active outreach verified, and a founder who sits inside the agency world daily verified.

The ask, verbatim

"You've got past clients still running builds you don't get paid to maintain. Send me one export. I'll audit it free and tell you what's fragile. If it's worth fixing, I'll quote it flat — you keep the client, you keep the invoice if you want to mark it up, and you stop doing unpaid triage at 7am."

The ask is one workflow export, not a contract, not a call. It is the smallest possible commitment and it produces the artefact — the risk map — that does the selling.

Conversion assumptions, stated as assumptions

Every one of these except the pipeline count is invented. The § 13 test measures the first three within six weeks.

How the first ten are found, by name

1. The AgentForge LinkedIn pipeline — 20 named agency founders, pitched directly as desk buyers. Expected: 3–5 of the first ten

2. r/zapier standing monitoring threads — Two are named in the report and remain live discussion surfaces for silent-failure complaints. The move is to answer them properly, with the actual three-detector approach, and offer the free health check at the end. Not a content strategy — replying to specific threads where a specific person has described this specific problem. Expected: 2–3 of the first ten

3. r/n8n and r/automation orphan threads — Same motion. The 493-upvote thread's comment section is a list of people describing this problem in their own words

4. HandoverKit-adjacent agencies — Every agency that would buy a handover product has the same backlog. Portfolio synergy, as the report names it. Expected: 1–2 of the first ten

5. Rescue clients' own networks — Not a referral ask, an artefact play: the handbook is a shareable object with Caretaker's name on it

What is deliberately not done

No newsletter, no LinkedIn content calendar, no cold email at volume, no paid anything. The founder profile penalises content-treadmill demands and heavy synchronous sales time, and the 40 hours/year budgeted for sales in § 09 permits about 45 minutes a week. That budget only works because the outreach rides on an existing motion.

---

§ 13The first test

The cheapest falsifying experiment is hand-running five free audits and three at-cost rescues with a checklist and a text editor — because if agency founders will not hand over a workflow export, nothing built afterwards matters.

The report's own next move is "adopt 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." This makes it concrete and puts one cheaper gate in front of it: access. Getting a client's workflow export requires trust that has never been tested.

The sequence

What it produces

• A measured median hours-per-rescue — the input that determines whether $750 flat is a price or a donation (§ 07 shows break-even at 9.68 hours)
• A measured rescue → care conversion rate against the assumed 75%
• A measured access rate: what fraction of warm agency contacts will actually hand over a client's workflow
• The median agency backlog size, which prices the desk (§ 02's most valuable unknown)
• The audit checklist, which becomes the specification for the intake instrument — the test is not throwaway work, it is the requirements document

Cost

Approximately $0 in cash. Three evenings of setup plus the rescue delivery, on the founder's existing tooling. Well inside the under-$1,000 constraint with nothing at risk but hours.

---

§ 14Risk

The report listed six reasons not to build; none of them have been solved by writing a plan, so they are reproduced here as the mechanisms by which this fails.

Risk 1 — Acquisition has no shortcut

• MechanismNobody searches for rescue verified. Demand surfaces one breakage at a time. With no paid channel (budget) and no audience (distribution 5/10), growth is entirely referral-and-content grind at 45 minutes a week
• Early warningFewer than 5 exports from the first 8 asks in § 13. Or: rescues arriving only from the founder's direct pitches, never inbound, past month 6
• MitigationThe desk channel converts one relationship into N workflows, which is the only lever that beats one-at-a-time acquisition. If the desk fails, there is no second mitigation and the honest answer is that this becomes a slow lifestyle service

Risk 2 — Channel mismatch: the agency sees a replacement, not a partner

• MechanismThe founder's pipeline reaches agency founders; the pain lives with SMB owners. The desk depends on agencies cooperating with someone their clients could reasonably hire instead of them verified
• Early warningAgencies engaging warmly on the audit and then going quiet at the desk conversation. Or requesting that Caretaker not contact the client at all, then not making the introduction
• MitigationWritten non-solicit on new build work, unbranded deliverables, agency-fronted pricing. Structural, not promissory: Caretaker never builds, so the agency's core revenue is untouchable
• ResidualReal. Some agencies will simply not risk it, and that is a rate, not a fixable objection

Risk 3 — Adverse selection on the flat rescue

• MechanismOrphaned builds are disproportionately the worst builds verified. A $750 flat on unknown spaghetti sometimes eats 20+ hours, at which point the frontend loses $774 (§ 07)
• Early warningAny single rescue over 15 hours in the § 13 calibration set. Or a widening gap between audit-estimated and actual hours
• MitigationAudit-first, always. Mechanical scope cap at 8 hours with $125/hr beyond, stated in the quote. A complexity score above threshold means hourly-only, never flat

Risk 4 — Liability without insurance

• MechanismAdopting a workflow that pushes numbers into an ERP means owning the next wrong number verified. Months 1–6 run uninsured because E&O is $500–1,000/yr and the budget is under $1,000 per bet verified
• Early warningAny adoption request involving payments, accounting or inventory before month 7
• MitigationSelection, written into the intake checklist: no read-write adoption of financial systems until cover is in force. Explicit liability cap at fees paid in the last 3 months, in every engagement letter from client one
• ResidualA serious incident in months 1–6 is uninsured and personally borne. This is a real, accepted exposure, not a managed one

Risk 5 — The services treadmill

• MechanismAt the documented 3–4 hrs/client/mo norm, 25 clients is 75–100 hours a month against a 43-hour ceiling. The business becomes hiring, which caps it as a solo asset verified
• Early warningMeasured per-client time above 1.5 hrs/mo at month 6, or a rising trend rather than a falling one as tooling ships
• MitigationThe entire § 15 build order exists to push this number down. § 07 gives the exact threshold: 1.86 hrs at $149

Risk 6 — Platform self-healing compresses the bottom

• Mechanismn8n and Zapier are shipping AI-assisted debugging. The simple-fix revenue layer shrinks, leaving only judgment-heavy work verified
• Early warningClients resolving their own alerts before Caretaker responds. Falling fix volume per client without falling incident volume
• MitigationPartial. Position on accountability and detection, not repair — a platform assistant does not notice absence, and does not answer at 7am. But the report is right that this erodes the bottom of the market over time and there is no defence against that, only a migration upward

Risk 7 — Single point of failure

• MechanismOne person, 5–10 hours a week, alongside a primary business. An incident during AgentForge crunch either damages the primary business or breaches the care promise assumed, derived from the profile's stated constraints
• Early warningAny missed response window in the first ten clients
• MitigationThe v1 SLA is next-business-day, business hours, deliberately (§ 06). Do not sell a promise the calendar cannot keep

Kill criteria

Criteria 1, 2 and 6 stop the project outright. Criteria 3 and 5 trigger a decision between continuing as a low-ceiling fix shop and stopping. Criterion 4 triggers a price rise to $249 across the base; if the base will not hold at $249, it becomes a stop.

---

§ 15Sequence

Nothing gets built until the § 13 test returns three numbers, and after that the build order is strictly whichever phase removes the most hours per hour spent.

Reconciliation

412 hours against a midpoint availability of 390 means this plan runs at roughly 8 hours a week for twelve months with zero slack. At the bottom of the range (5 hrs/wk, 260 hrs) it does not fit: Phases 0–3 ship, about four rescues get delivered, and month 12 MRR lands nearer $900. At the top (10 hrs/wk, 520 hrs) there are 108 spare hours, which buys either the second agency cohort earlier or three more rescues.

Ordering logic

Phase 1 before Phase 2 because pricing risk kills faster than margin risk — a rescue that eats 20 hours costs $774 today, while a client costing 2 hrs/mo costs $8 today. Phase 3 before Phase 4 because the desk pitch is much stronger with a weekly report artefact to show an agency than without one. Phase 5 last only in build order, not in importance: the engagement letter with its liability cap is written before client one, as a document, in Phase 0's 46 hours; what waits for Phase 5 is the insurance and the runbook.

The gate between Phase 0 and Phase 1

Do not start Phase 1 until the § 13 gates clear. If 2 of 3 do not buy care, the parser is 40 hours spent building the intake for a business that does not exist. The report's next move and this plan's first phase are the same thing, and that is deliberate — the report earned its BUILD by proposing a test, not a launch.