Custom software development projects often blow budgets because scope creeps and billing models don't align with how work actually unfolds. Moving to a retainer model can stabilize revenue, deepen client relationships, and let you plan staffing more predictably. Here's how to structure and sell retainer arrangements that work for both you and your clients.
Why Retainers Beat Project-Based Pricing
Project estimates assume you know exactly what a client needs upfront—rarely true in software work. Retainers flip the model: clients pay a fixed monthly fee for a defined scope of work, whether that's feature development, maintenance, bug fixes, or architectural guidance. This removes the constant negotiation cycle, gives clients predictable costs, and gives you predictable revenue.
For custom software shops, retainers typically represent 40–60% of healthy revenue. They act as a financial cushion during slower sales periods and fund your ability to invest in better tooling and team development.
Structuring Your Retainer Tiers
A three-tier retainer model works well for most custom development shops:
- Tier 1 (Essential): 20–40 hours/month. Covers bug fixes, small feature requests, security patches, and dependency updates. Price range: $3,000–$6,000/month depending on geography and team seniority. Good entry point for early-stage clients or those with stable, mature products.
- Tier 2 (Standard): 40–80 hours/month. Includes the above plus larger feature development, quarterly performance audits, and proactive technical debt work. Price range: $6,000–$12,000/month. Attracts growth-stage companies who want continuous improvement without hiring.
- Tier 3 (Premium): 80+ hours/month. Dedicated team or near-dedicated resource, architectural planning, mentorship for client's in-house team, roadmap collaboration, and priority support. Price range: $12,000–$25,000+/month. Suits companies building product as their core business.
Setting Your Hourly Rate Foundation
Your retainer price starts with your effective billable rate. If your team's fully-loaded cost (salary, benefits, overhead) is $80/hour, you'll want to bill $120–$180/hour gross to account for non-billable admin, sales, and margin.
For retainers, apply a 10–20% discount off that hourly rate to reward predictability. A team billing $150/hour on projects might sell retainers as if billing $135/hour—clients save money, you get stable cash flow.
What to Include (and Exclude)
Clear scope prevents disputes. Standard retainer inclusions:
- Code reviews and pull request feedback
- Bug fixes and patches for reported issues
- Updates to third-party libraries and frameworks
- Production monitoring and alerting setup
- Technical documentation updates
Typical exclusions (charged separately):
- Major feature rewrites or redesigns (scope negotiation needed)
- Infrastructure migration or platform changes
- Training on technologies outside your primary stack
- Third-party vendor licensing or SaaS tool subscriptions
Put this in writing. A one-page scope document prevents the "I thought that was included" conversation at month three.
Selling Retainers to Prospects
Retainers sell best to clients who already have a product in market or are committed to building one long-term. Early conversations should surface whether a prospect fits:
- Ask: "What ongoing work do you anticipate in year two—after launch or after the initial build?"
- Listen for: mentions of maintenance burden, planned features, team gaps, or uncertainty about future scope.
- Reframe: "Rather than guess at project scope, many clients start on retainer for three months. We document what comes up, and you'll know your actual needs by month four."
Position retainers as risk reduction for them. They avoid surprise invoices and keep your team warm on their codebase for when bigger work arrives.
Handling Unused Hours
Most retainer agreements include a rollover policy: unused hours roll to the next month, capping at 20–30% of that month's allocation. Beyond that, hours expire. This prevents clients from banking six months of unused hours and discourages you from under-delivering.
Document this in your contract and review utilization monthly. If a client consistently doesn't use their allocation, revisit their tier—they may need Tier 1 instead of Tier 2.
Frequently Asked Questions
Q: Can I switch a client from project-based to retainer mid-relationship? Yes. After a successful project, propose a retainer for the "keep-the-lights-on" work you know is coming. Frame it as simpler billing and faster response times for them.
Q: What if my retainer client needs a big feature that exceeds their monthly hours? Scope it as a separate project with its own timeline and invoice, or increase their retainer temporarily for that quarter. Make the conversation explicit—don't silently eat the overrun.
Q: How do I prevent retainer clients from treating me like a free helpline? Define response time SLAs (e.g., "non-urgent requests within 48 hours"), scope work types clearly, and log time spent. Monthly reporting keeps expectations aligned.
Start a retainer program this quarter—it's one of the fastest ways to stabilize custom software development revenue. List your retainer packages on Mercoly to reach founders and CTOs actively searching for managed development partnerships.