Maintenance pricing trips up most custom software development shops because they treat it like a flat fee when it's really a variable cost model. The wrong pricing strategy bleeds margins, frustrates clients, and tanks your predictability. Get this right, and you'll build recurring revenue that makes your business genuinely scalable.
Why Maintenance Pricing Matters More Than You Think
Your maintenance contract is where relationships either strengthen or snap. A client who paid $50K for build-out expects clear, fair pricing for ongoing support—not surprise invoices or vague hourly rates that feel punitive. The right maintenance model funds your team's capacity, keeps your pipeline stable, and gives clients confidence they won't face unexpected bills when a critical bug hits production.
Common Maintenance Pricing Models
Most custom software shops use one of these frameworks:
- Retainer-based pricing: Fixed monthly fee (typically $1,500–$8,000+) for a set number of support hours, monitoring, and minor updates. Best for clients who want predictability and you want recurring revenue.
- Hourly support billing: Charge $85–$200/hour for work beyond the retainer. Works if you clearly define what's included and track time obsessively, but creates friction.
- Subscription tiers: Bronze ($1,200/month, 10 hours), Silver ($3,500/month, 30 hours), Platinum ($7,000/month, unlimited). Lets clients self-select based on risk tolerance.
- Per-incident pricing: Charge $500–$2,500 per bug fix, update, or feature request. Risky because clients hold off on requests to avoid costs, and you lose predictability.
- Hybrid models: Retainer covers routine monitoring and critical fixes; hourly rates apply to feature requests or major refactoring.
How to Set Your Maintenance Price Range
Start by calculating your actual costs. Factor in:
- Team capacity: If one developer costs you $6,500/month fully loaded (salary, benefits, tools), and they can handle 4 maintenance clients at 10 hours/month each, your retainer floor is roughly $1,625 per client minimum.
- Stack complexity: A straightforward REST API needs less maintenance than a real-time trading platform. Adjust pricing 20–40% higher for high-criticality systems.
- Client industry and revenue: A B2B SaaS client generating $500K/year in revenue from your software can absorb a $5,000/month retainer; a nonprofit can't.
- Severity levels and response time SLAs: If you're committing to 4-hour response times for production outages, that's worth $3,000+/month. Standard 24-hour response for non-critical issues is cheaper.
Building a Maintenance Pricing Menu Clients Understand
Transparency beats complexity every time. Present three tiers with real specifics:
Standard Tier ($2,000/month): 15 hours of support, business-hours response, up to 2 minor updates/month, security patches included, $75/hour overages.
Professional Tier ($4,500/month): 40 hours of support, 8-hour response time for critical issues, unlimited minor updates, quarterly performance reviews, $60/hour overages.
Enterprise Tier ($8,000+/month): Dedicated contact, 2-hour critical response, unlimited updates, infrastructure optimization, monthly reporting.
Each tier should include what's not covered (major refactoring, third-party integrations, custom feature development) so clients don't expect free work.
Red Flags That Signal Pricing Problems
If you're constantly working overages without billing them, your rates are too low. If clients balk at every invoice, you haven't justified value—add quarterly impact reports showing uptime %, bugs resolved, and cost savings from preventive maintenance. If you can't predict team capacity month-to-month, your retainer size is misaligned with actual workload.
Getting Contracts Right
Spell out maintenance clearly in writing. Include response time SLAs, what counts as "support" versus "new work," renewal terms (annual is better than monthly), and how you handle scope creep. A simple one-pager beats legal jargon; clients need to know they're covered.
If you're struggling to land clients willing to commit to maintenance packages, listing your maintenance services on Mercoly helps you get discovered, win qualified leads, and sell those predictable ongoing contracts to businesses actively seeking support agreements.
Frequently Asked Questions
Q: Should I charge differently for bug fixes versus feature requests in maintenance? Yes—bug fixes are typically included; feature requests should either consume retainer hours or be billed separately as custom development at your standard development rate (often 20–40% higher than support rates).
Q: How do I handle a client requesting 60 hours of work in a month when their retainer covers 30? Track and invoice the 30-hour overage at your agreed rate, then discuss next month's tier in a calm, data-driven conversation—don't spring surprise bills.
Q: What's a reasonable maintenance percentage of original project cost annually? Most shops charge 10–20% of the original build cost per year; a $100K project gets a $10K–$20K annual maintenance budget, ideally split into monthly retainers.
Ready to formalize your maintenance pricing? Start with your cost structure, pick a model that matches your team's capacity, and get it in writing.