automation
How to Calculate Hourly Versus Retainer Pricing for Automation Agency Contracts
A client asks "why not just bill hourly?" Here's the math to answer that question and price automation contracts so scope creep doesn't eat your margin.
A client just asked you to quote a Telegram outreach automation build. You throw out an hourly rate, they say "sounds fair," and three weeks later you've burned 40 unbilled hours on "quick tweaks" that were never in the original scope. Now you're doing $18/hour work on a $150/hour contract.
This is the single most common way automation agencies lose money — not from bad clients, but from picking the wrong pricing model for the wrong kind of work. Hourly and retainer aren't interchangeable defaults. They solve different problems, and picking wrong is what turns a profitable engagement into a slow bleed.
What's the break-even point between hourly and retainer pricing?
The break-even point is roughly 15-20 hours of work per month. Below that threshold, hourly billing usually nets you more revenue per hour worked. Above it, a retainer almost always protects your margin better, because clients start requesting more "small favors" once they know you're available — and those favors are unbilled under a flat hourly rate that assumes a fixed scope.
Here's the actual math: if your target rate is $100/hour and a client needs roughly 25 hours/month of ongoing automation maintenance, tweaks, and monitoring, a $2,500/month retainer nets the same $100/hour only if hours stay at 25. The moment scope creeps to 32 hours (which it will — automation contracts almost always creep because "just add one more trigger" feels small to the client and isn't), your effective rate drops to $78/hour. That's the retainer trap. But the inverse is worse: pure hourly billing on ongoing work means you're re-negotiating scope every single week, and clients start nickel-and-diming every invoice line.
When should you bill hourly instead of retainer?
Bill hourly when the engagement has a defined start and end date and the deliverable is clear before you start. Automation agencies should default to hourly for:
One-time builds: setting up a Telegram CRM pipeline, building a single outreach sequence, or migrating a client's contact database into a new system.
Discovery and audits: when you're diagnosing why a client's current automation is broken before you know the fix.
New clients with unknown scope volatility: you don't yet know if this client sends 10 change requests a month or 1.
Fixed integration work: connecting a CRM to a specific API endpoint, where the task has a clear "done" state.
The rule of thumb: if you can scope the deliverable in a single sentence with a clear finish line, bill hourly. If the sentence is "keep this running and improve it," that's retainer territory.
When does a retainer make more financial sense?
Retainers make sense when the value you deliver is ongoing and hard to isolate into discrete billable tasks — think account management, campaign optimization, monthly reporting, and the constant small maintenance that automated outreach systems need to keep running without getting flagged or banned. If you've ever managed Telegram accounts that get shadow restricted during outreach, you know this kind of work never fits neatly into a timesheet — it's reactive, unpredictable, and happens in 20-minute bursts across the week.
A well-structured retainer bundles that unpredictability into a flat, predictable number for both sides. The client gets budget certainty. You get revenue certainty and stop bleeding time on unbilled "quick favors." The catch: you have to actually define the ceiling, or the retainer becomes an unlimited-hours trap that pays worse than hourly.
The retainer scope checklist
Cap the hours. State a maximum monthly hour allotment (e.g., "up to 20 hours") and bill overages hourly.
Define response time, not availability. "24-hour response on business days" beats "available whenever," which invites 11pm messages.
List what's included vs. billable extra. Monitoring and minor tweaks in; net-new automation builds or new integrations out (billed separately).
Set a quarterly review clause. Either side can renegotiate the retainer size based on actual logged hours over the last 90 days.
Track hours even on flat retainers. You need the data to know if you're underpricing before it's too late to fix.
How do you calculate your actual hourly cost before quoting either model?
Most agencies quote a number that "feels right" instead of working backward from their real costs. Start here: take your desired annual income, add overhead (software, contractor pay, your own taxes), and divide by your realistic billable hours per year — not 2,080 (40 hours x 52 weeks), but closer to 1,200-1,400 once you subtract sales calls, admin, and slow weeks.
Example: you want $120,000/year net, plus $30,000 in tools and subcontractor costs. That's $150,000 total, divided by 1,300 realistic billable hours = $115/hour minimum just to hit your target — before profit margin. Most agencies price below this number because they calculate off a fantasy 40-hour billable week that never happens once you factor in scoping calls, revisions, and account management that doesn't get logged.
How do you price a hybrid contract that covers both builds and maintenance?
Most real automation contracts aren't purely one or the other — they're hybrid. The build phase is hourly or fixed-fee, and once the system is live, it rolls into a retainer for maintenance and optimization. This is actually the healthiest structure for both sides:
Quote the initial build as a fixed price, based on your hourly rate times an honest time estimate, with a 15-20% buffer for scope surprises.
Set a "go-live" milestone that triggers the switch from build pricing to retainer pricing.
Price the retainer based on system complexity, not just hours — a system running multiple Telegram outreach accounts across a team needs more monitoring than a single-account setup, so tier your retainer to account count or campaign volume.
Bake in tool costs transparently. If you're managing outreach infrastructure on behalf of the client, their software costs (CRM seats, outreach accounts) should be a visible line item, not absorbed into your margin.
This is also where your own tool stack pricing matters for your margin math. If you're running client outreach through CRMChat, the Team plan's tiered account pricing (accounts get cheaper per-seat as volume scales, from $79/account down to $39/account past the 10-account mark) means your cost-per-client-account drops as you take on more automation clients — which should show up in how you price retainers at scale, not just get pocketed as extra margin.
What should actually go in the contract, regardless of pricing model?
CRMChat is used by agencies like uForce to run automated Telegram outreach across 10 simultaneous B2B client projects — and the lesson from that kind of scale is that the pricing model only works if the scope is written down precisely. Vague contracts are what turn a good retainer into a bad one.
Number of accounts/campaigns covered under the current price.
Response SLA for issues (e.g., account gets flagged, sequence stops sending).
What counts as "maintenance" vs. what triggers a new quote (new client vertical, new integration, new automation logic).
Reporting cadence — weekly, monthly, what metrics.
Termination and hour-rollover terms — do unused retainer hours roll over, or reset monthly?
CRMChat also automates the reporting layer that agencies typically bill hours to produce manually — the platform's built-in analytics and centralized team workspace mean you're not paying an account manager to hand-compile monthly performance decks for every client retainer. That's real hours back on your side of the ledger, which is exactly the kind of hidden margin most agencies never calculate before they price a contract.
Quick answer: which should you choose?
If the engagement has a clear end date and defined deliverable, bill hourly. If it's ongoing maintenance, optimization, or account management with unpredictable but recurring demand, use a capped retainer. Most healthy automation agency contracts use both — hourly or fixed-fee for the build, retainer for everything after go-live. Whichever you choose, log every hour anyway; it's the only way you'll know your pricing is actually working six months from now instead of guessing.
