{"slug": "the-retainer-ladder-from-one-off-ai-builds-to-income-that-repeats", "title": "The retainer ladder: from one-off AI builds to income that repeats", "summary": "AI freelancers are shifting from one-off project builds to retainer-based income models, charging $100–200 per user per month or €300–500 for small automation retainers, following playbooks from the managed service provider industry. Retainers provide recurring revenue by selling availability and accountability rather than prepaid hours, with maintenance plans typically underused but priced to cover quiet months.", "body_md": "The Ledger · Freelancing\n\n# The retainer ladder: from one-off AI builds to income that repeats\n\n- MSP per-user norm\n- $100–200 per user per month\n- Small automation retainer\n- €300–500 per month\n- Maintenance package sizing\n- 2–5 hours per month\n- Actual use of a 3 hr/mo plan\n- 4–5 hours per year\n- MSP monthly minimum\n- $1,000\n- One retainer, paid vs worked\n- 10 hours paid, ~5 worked\n- Web maintenance formula\n- 0.5% of build cost per month\n- Recurring revenue at exit\n- 4–6x EBITDA vs less for project shops\n\nA one-off build starts every month at zero. Retainers are how automation and AI freelancers make the income repeat: what working builders really charge, what the maintenance actually costs, the month the client asks why they are paying, and the playbook an older industry wrote decades ago.\n\nA one-off build has a cruel property: the better you do the job, the sooner the income stops. You [land the client](/ledger/first-ai-client/), [price the work](/ledger/pricing-ai-work/), deliver something that runs, and on the first of next month your revenue is zero again. The builders who get off that treadmill all make the same move, and it is not a secret, because an older industry wrote the playbook decades ago and publishes its numbers. Keep one line in your head before you quote your next project: after delivery, you are not selling hours anymore, you are selling insurance. This piece is the retainer math, with receipts: what working automation builders actually charge, what the maintenance really costs you, and what to say in the month nothing breaks.\n\nThe short version, if you are pricing one this week:\n\n**A retainer is availability plus accountability, not prepaid hours.** The client pays for a promise: it stays alive, and when it breaks, you exist.**The believable numbers are modest and they stack:** a few hundred a month per client for maintenance, four figures for management, with the[MSP industry’s](https://www.datto.com/wp-content/uploads/dlm_uploads/DAT-2024-State-of-the-MSP-Report-1.pdf)$100 to $200 per user per month as the mature reference point.**Price for the quiet months and cap the loud ones.** Small plans get used a few hours a year; the margin is the underuse. The contract’s job is making sure an ugly month cannot eat the year.**The churn moment is predictable.** It arrives the month everything works. Your defense is written into the retainer on day one, not improvised on the renewal call.\n\n## What a retainer actually is\n\nThe cleanest definition on record is from patio11, selling maintenance contracts on custom software [years before the AI wave](https://news.ycombinator.com/item?id=7083948): the client pays monthly for you “to maintain internal expertise about your project and the staffing flexibility to promise you development services in a timely fashion,” up to a capped amount of work. And the part to tattoo somewhere: “What does a $5,000 a month maintenance contract cost if you don’t require any work in a given month? $5,000. It’s like health insurance: just because you don’t have your appendix burst doesn’t mean we give you a rebate.”\n\nThat is the product. Not hours, a standing promise. Consultants who live on retainers structure it the same way: Jonathan Stark’s version is [explicitly “not prepayment for a block of hours”](https://jonathanstark.com/how-my-retainers-work) but paid access with a response-time promise, and he notes five-figure-a-month clients who go months without calling. In practice the market sells three shapes, and you should know which one you are quoting:\n\n**The hours bank.** X hours a month, use them or lose them, overflow billed or queued. Easiest to sell, easiest to abuse, and it quietly reframes you as inventory.**Availability plus SLA.** The insurance model: a response-time promise, monitoring, and a cap. The client buys certainty, not labor.**The managed service.** You run the thing end to end: hosting, monitoring, fixes, improvements. Highest price, most obligation, and the model the entire MSP industry is built on.\n\n## The numbers, from people actually charging them\n\nStart with the mature market, because it anchors everything. Managed service providers, the people who have run business IT on retainers for twenty years, cluster hard around [$100 to $200 per user per month](https://www.reddit.com/r/msp/comments/1iosuqc/looking_for_msp_pricing/) all-inclusive, enforce [monthly minimums around $1,000](https://www.reddit.com/r/msp/comments/1ew5y5r/switching_to_per_seat_pricing_good_pricing_for/) so small clients cannot be unprofitable, and treat recurring revenue as [the backbone of the model](https://www.datto.com/wp-content/uploads/dlm_uploads/DAT-2024-State-of-the-MSP-Report-1.pdf). One MSP posted the unit economics of his [$50-per-user entry tier](https://www.reddit.com/r/msp/comments/1hcptr9/msp_model_but_without_the_price/): tooling costs around $11, the price leaves room for about 20 minutes of support per user per month, and actual usage runs about 3. That gap between what is paid for and what is used is not a scam, it is the entire economics of insurance, and it prices the AI version too.\n\nThe automation and AI numbers, one rung down the maturity ladder, rhyme. The quiet, believable receipts from [builders comparing rates](https://www.reddit.com/r/n8n/comments/1izrlrr/what_the_heck_are_you_guys_charging_clients/): maintenance retainers of €300 to €500 a month, priced, in one builder’s words, “low enough for a company to not scrutinize the bill, but high enough for me to be interesting if I stack a handful of retainers with barely any work needed.” Web freelancers publish the same structure at [$50, $100, and $250 tiers](https://www.reddit.com/r/webdev/comments/1i874z9/how_did_you_get_your_first_few_clients_as_a_web/), or as [a formula: half a percent of the build cost per month](https://www.reddit.com/r/webdev/comments/1f5nlgo/freelancersagency_owners_would_you_charge_monthly/). Above that sits management: the [work-in-progress-slots model](https://www.reddit.com/r/automation/comments/1jhf39o/advice_for_starting_an_ai_agency/), where the client buys a number of active automation requests at a time, and the [$2,500-a-month “AI management as a service”](https://www.reddit.com/r/n8n/comments/1kki6u5/i_just_hit_25000mrr_in_4_months_with_n8n/) tier, which we quote with the caveat that the poster’s headline MRR is his claim, not a verified number. At the top the retainer stops being a retainer: $5,000 a month for 20 hours a week is a fractional hire wearing a retainer’s name tag.\n\nTwo structural receipts worth more than any single price. A builder with [45 to 50 maintenance clients](https://www.reddit.com/r/webdev/comments/1g3f8sj/looking_for_an_alternative_to_wordpress_after_the/) spanning €265 to €3,000 a month calls one-off projects “bonus money on top of my monthly income,” a complete inversion of how most freelancers think. And an agency selling [$0-down, $175-a-month website subscriptions](https://www.reddit.com/r/smallbusiness/comments/1kjfwnu/how_profitable_is_we_design_agency/) reports $23K a month recurring, his argument being arithmetic: selling $500 one-offs means finding 46 new buyers every month forever. The punchline for anyone thinking of an exit someday: recurring books [sell for 4 to 6 times earnings](https://www.reddit.com/r/msp/comments/1ggshwz/ballpark_valuation_of_an_msp/), and the multiple rises with the share of revenue that repeats.\n\nAlso worth knowing: [only about 13% of consultants](https://www.consultingsuccess.com/consulting-retainer) run monthly retainers at all (a stat from a coaching outfit, so season accordingly). The model is underused, not saturated.\n\n## What it costs you: the other side of the meter\n\nThe reason retainers are not free money is that automations rot. The line practitioners repeat about AI systems is that [building the agent is only 30% of the battle](https://www.reddit.com/r/AI_Agents/comments/1k3t3ga/ai_agents_truth_no_one_talks_about/); the rest is deployment, drift, and API changes. The n8n community’s [working definition of a maintenance package](https://community.n8n.io/t/support-pakage-after-workflow-delivery/300786) is the concrete version: 2 to 5 hours a month covering credential rotation, checking execution logs for silent failures, and fixing the node some vendor’s API update just broke. That list is your scope. Note what it does not include, and note the advice attached to it: “draw a massive, explicit line between maintenance (keeping the existing workflow alive) and new features.” Every retainer that turned into a nightmare crossed that line without a change order.\n\nBudget with open eyes on both sides. Most months, most clients use far less than they pay for: one web freelancer’s clients on a 3-hour monthly plan [use 4 to 5 hours a year](https://www.reddit.com/r/webdev/comments/13yhsom/questions_for_the_freelancers_how_long_do_you/); a consultant on retainer [averages 5 hours of work and 10 hours of pay](https://news.ycombinator.com/item?id=27366228). But the tail months are real, and unbounded. The contract needs three protections written in before you sign: a cap or slow-lane for overflow work, the maintenance-versus-new-features line, and payment up front. That last one is not paranoia; it is the [builder who delivered an AI agent and watched $5,800 walk away](https://www.reddit.com/r/AI_Agents/comments/1j1kpsx/lost_5800_building_an_ai_agent_for_a_client/), and the reply that should be your policy: “For retainers, I always ask for payment before doing the work.”\n\nThere is also a load ceiling, and the MSPs have measured theirs: a support tech carries roughly 250 to 300 endpoints before quality slides. Your translation depends on what you sold, but the shape holds. A solo builder maintaining well-built, monitored automations can carry a dozen small retainers in a few days a month; the same builder who skipped error handling on the builds is on call for all twelve at once. The retainer’s profitability is decided when you build the thing, which is exactly the argument for [scoping the build properly](/ledger/scoping-ai-projects/) in the first place.\n\n## The month nothing breaks\n\nSometime around month four, everything works, and the client asks the question a commenter [put to the $25K MRR poster](https://www.reddit.com/r/n8n/comments/1kki6u5/i_just_hit_25000mrr_in_4_months_with_n8n/): how do you justify the fee “in months where you might not actively touch the account?” If your answer improvises, you churn. The defenses, all from the receipts:\n\n**Send the report.** A monthly one-pager: what ran, what broke, what was fixed, what it saved. The n8n forum’s framing is right: it “moves the conversation from fixing broken things to proactive health monitoring.” Invisible work is unpaid work; the report makes it visible.**Own the plumbing, carefully.** Bundling hosting and monitoring makes leaving harder and the value concrete, and it is exactly what mid-ladder freelancers do to fight churn. Two cautions: some tools’ licenses restrict hosting client automations on your own infrastructure (check before you build your model on it), and there is a line between healthy stickiness and hostage-taking. Which is the next point.**Make leaving safe, and staying rational.** The strongest retainer pitch in the receipts is the walk-away clause: the automations are yours if you leave; what you lose is me maintaining them. Paired with the queue rule (retainer clients get the front of the line, everyone else waits), it sells continuity without threats.**Price below the scrutiny line.** The €300-500 stackers are doing churn prevention with the price itself: cheap enough that no CFO opens the invoice, valuable enough that nobody wants to find out what breaks without it.**Start with a warranty, not a retainer.** Thirty days of included support after delivery, then the paid package. It converts better than selling insurance on day one, and it gives the client a month of seeing what “maintained” feels like.\n\nOne thing the receipts refuse to support: the tidy “$500 paid audit converts into the retainer” ladder that automation coaches sell. We looked. Working practitioners run free consultations or discounted paid discovery, fold the auditing into the retainer itself, and close on outcomes. Nobody credible posted the paid-audit funnel actually working, which does not mean it never does, but you should know that the people teaching it are selling the course, not running the ladder. The variance is wide and unglamorous: the same practitioner who described the slots model has “seen well-seasoned business people hit 40-50k MRR in 4 months” and “people flounder around 1-3k per month for over a year.” The difference was the business behind the builder, not the template.\n\n## The ladder, assembled\n\nPut the pieces in order and the ladder has four rungs: a free consultation that finds the automatable pain, a scoped one-off build with payment up front and a 30-day warranty, the maintenance package at delivery (2 to 5 hours, the report, the cap, the line between maintenance and new work), and, for the clients with appetite, the management tier where you audit, build, and improve continuously against a slot limit. Each rung is sold at the top of the previous one, when trust is highest and the memory of the working demo is fresh. Six clients on the maintenance rung at $400 is $2,400 a month that arrives before you sell anything, which is the whole point: [the one-person AI business](/ledger/economics-of-a-one-person-ai-business/) does not die from small revenue, it dies from revenue that starts at zero every month.\n\nSell the insurance, send the report, cap the tail, and keep the line between keeping-it-alive and building-more. The build ends. The retainer is the part of the business that repeats.\n\nOne email, when there's something worth sending\n\n## Get the receipts in your inbox.\n\nNo fixed schedule, no filler. You get an email when we've tested something, run the numbers, or found a tool worth your time.\n\nFree. Double opt-in, unsubscribe in one click.\n\nStacking retainers? [Compare notes in the forum ↗](https://community.okaneland.com)\n\n## Sources\n\n| Source | Link |\n|---|---|\n| patio11 on maintenance contracts (Hacker News) |\n|\n\n[news.ycombinator.com ↗](https://news.ycombinator.com/item?id=33924123)[news.ycombinator.com ↗](https://news.ycombinator.com/item?id=27366228)[jonathanstark.com ↗](https://jonathanstark.com/how-my-retainers-work)[datto.com ↗](https://www.datto.com/wp-content/uploads/dlm_uploads/DAT-2024-State-of-the-MSP-Report-1.pdf)[mspsuccess.com ↗](https://mspsuccess.com/2025/01/cracking-the-code-what-survey-results-reveal-about-msp-pricing-and-profitability/)[reddit.com ↗](https://www.reddit.com/r/msp/comments/1iosuqc/looking_for_msp_pricing/)[reddit.com ↗](https://www.reddit.com/r/msp/comments/1ew5y5r/switching_to_per_seat_pricing_good_pricing_for/)[reddit.com ↗](https://www.reddit.com/r/msp/comments/1hcptr9/msp_model_but_without_the_price/)[reddit.com ↗](https://www.reddit.com/r/msp/comments/1e89hmg/we_dont_like_recurring_services/)[reddit.com ↗](https://www.reddit.com/r/msp/comments/1ggshwz/ballpark_valuation_of_an_msp/)[reddit.com ↗](https://www.reddit.com/r/webdev/comments/1i874z9/how_did_you_get_your_first_few_clients_as_a_web/)[reddit.com ↗](https://www.reddit.com/r/webdev/comments/13yhsom/questions_for_the_freelancers_how_long_do_you/)[reddit.com ↗](https://www.reddit.com/r/webdev/comments/1f5nlgo/freelancersagency_owners_would_you_charge_monthly/)[reddit.com ↗](https://www.reddit.com/r/web_design/comments/1jejc0w/how_much_do_yall_charge_for_a_35_page_basic/)[reddit.com ↗](https://www.reddit.com/r/smallbusiness/comments/1kjfwnu/how_profitable_is_we_design_agency/)[reddit.com ↗](https://www.reddit.com/r/webdev/comments/1g3f8sj/looking_for_an_alternative_to_wordpress_after_the/)[reddit.com ↗](https://www.reddit.com/r/n8n/comments/1izrlrr/what_the_heck_are_you_guys_charging_clients/)[reddit.com ↗](https://www.reddit.com/r/n8n/comments/1kki6u5/i_just_hit_25000mrr_in_4_months_with_n8n/)[reddit.com ↗](https://www.reddit.com/r/automation/comments/1jhf39o/advice_for_starting_an_ai_agency/)[community.n8n.io ↗](https://community.n8n.io/t/support-pakage-after-workflow-delivery/300786)[reddit.com ↗](https://www.reddit.com/r/AI_Agents/comments/1k3t3ga/ai_agents_truth_no_one_talks_about/)[reddit.com ↗](https://www.reddit.com/r/AI_Agents/comments/1j1kpsx/lost_5800_building_an_ai_agent_for_a_client/)[consultingsuccess.com ↗](https://www.consultingsuccess.com/consulting-retainer)Show your work: if a number can't be shown, we don't print it.", "url": "https://wpnews.pro/news/the-retainer-ladder-from-one-off-ai-builds-to-income-that-repeats", "canonical_source": "https://okaneland.com/ledger/retainers-for-ai-work/", "published_at": "2026-07-03 13:00:00+00:00", "updated_at": "2026-07-03 22:00:37.628110+00:00", "lang": "en", "topics": ["ai-tools", "ai-startups", "ai-products", "ai-agents", "developer-tools"], "entities": ["patio11", "Jonathan Stark", "Datto"], "alternates": {"html": "https://wpnews.pro/news/the-retainer-ladder-from-one-off-ai-builds-to-income-that-repeats", "markdown": "https://wpnews.pro/news/the-retainer-ladder-from-one-off-ai-builds-to-income-that-repeats.md", "text": "https://wpnews.pro/news/the-retainer-ladder-from-one-off-ai-builds-to-income-that-repeats.txt", "jsonld": "https://wpnews.pro/news/the-retainer-ladder-from-one-off-ai-builds-to-income-that-repeats.jsonld"}}