Value-Based Pricing for Custom Software: How to Price MVPs, Full Products, and Retainers
Software development companies that price on hours are forever competing on rate. Shops that price on value — what the software is worth to the client's business — earn 2–3x more for the same quality of work. The shift from hourly rate billing to value-based pricing is the most significant financial lever available to a growing dev shop, and it starts with understanding how to quantify what you're actually delivering.
READY TO TAKE ACTION?
Use the free LaunchAdvisor checklist to track every step in this guide.
The Foundation: Value-Based vs. Cost-Plus Pricing
Cost-plus pricing works like this: calculate your fully-loaded hourly cost ($85–$125/hour for a mid-level developer), multiply by estimated hours, add a margin, and quote the client. This is transparent, simple, and consistently leaves money on the table.
Value-based pricing works like this: determine what this software is worth to the client's business, then price your engagement as a fraction of that value. A client building a customer portal that will reduce their support ticket volume by 40% — saving $200,000/year in support staff costs — is building something worth $600,000+ in 3-year NPV. A $75,000 fixed-price engagement to build that portal is excellent value for them and excellent margin for you.
The critical insight: clients don't buy software development hours. They buy business outcomes. Your pricing should reflect the outcome, not the input.
Pricing the Discovery Phase
The discovery phase (also called a scoping project, technical discovery, or product definition sprint) is a paid 2–4 week engagement where your team works with the client to define requirements, assess technical complexity, audit existing systems, and produce a scoped project proposal.
Why charge for discovery? It filters serious buyers from window-shoppers, compensates you for real work (discovery requires senior developer and PM time), and creates a higher-quality project brief that reduces scope creep in the actual build phase.
Discovery pricing: $5,000–$15,000 depending on complexity. A simple 2-week discovery for a mobile app MVP is $5,000–$7,500. A 4-week discovery for an enterprise system replacement involving stakeholder interviews, architecture review, and detailed technical specification is $10,000–$15,000. Offer to credit the full discovery fee against the build project if the client proceeds — this removes the financial risk objection while preserving the filter function.
Deliverable from discovery: a detailed Scope of Work (SOW) with user stories, technical architecture recommendations, technology stack rationale, development timeline, milestone schedule, and a fixed-price or retainer quote for the build phase. Clients who see a well-structured SOW deliverable immediately understand why they paid for discovery.
MVP Pricing: $15K–$50K Range
An MVP (Minimum Viable Product) for a software development context is the smallest functional version of a product that can be tested with real users. Pricing depends on scope, complexity, and the client's sophistication.
Typical MVP project types and price ranges:
Simple mobile app MVP (basic CRUD, user auth, 3–5 screens): $15,000–$25,000. Typical timeline: 6–10 weeks. Stack: React Native or Flutter, simple REST API, PostgreSQL or Firebase.
SaaS web application MVP (user management, core feature set, payment integration, basic admin dashboard): $25,000–$50,000. Typical timeline: 10–16 weeks. Stack: Next.js, Node.js/FastAPI, PostgreSQL, Stripe.
Integration-heavy MVP (connecting 2–3 existing enterprise systems via APIs, data transformation, basic reporting): $30,000–$60,000 depending on API complexity. Timeline: 8–14 weeks.
When quoting an MVP, define 'MVP' explicitly in your SOW. What's in scope and out of scope? Clients often expand MVP definitions without realizing it — 'can you add a reporting dashboard?' is a $10,000 addition, not an afterthought. Your SOW should list specific deliverables, not general categories.
Full Product Pricing: $50K–$200K Range
A full product build goes beyond MVP to include the complete feature set, production infrastructure, security hardening, performance optimization, and launch readiness. Projects in this range typically involve 16–40 weeks of development.
$50,000–$100,000: production-ready SaaS application with complete user authentication, multi-tier permissions, core feature set, payment processing, email notifications, basic analytics dashboard, mobile-responsive design, and staging/production environment setup. Typical team: 1 senior dev + 1 mid-level dev + part-time design.
$100,000–$200,000: complex multi-stakeholder applications — enterprise portals, healthcare platforms, fintech tools, marketplace applications with buyer and seller flows, or applications requiring significant data processing. Includes performance testing, security audit, documentation, and post-launch support window. Typical team: 2 senior devs + 1–2 mid-level devs + dedicated design + PM oversight.
Fixing scope is critical at this price range. Require all client stakeholders to sign off on the SOW before work begins. Include a formal change order process (any scope addition outside the SOW requires written approval and pricing update) in your MSA. Scope creep on a $150,000 project that isn't managed can easily add $40,000–$60,000 in unbilled hours.
Retainer Pricing: $3K–$10K/Month
Monthly retainers are the holy grail of software agency pricing: predictable revenue, lower sales overhead than project-by-project acquisition, and the ability to staff consistently without bench time.
$3,000–$5,000/month: 20–30 hours of mixed development support (bug fixes, minor feature additions, technical debt, code reviews, deployment management). Suitable for clients with an existing application who need ongoing maintenance and light development. Often sold as a 'fractional CTO + development' retainer for clients without in-house tech leadership.
$5,000–$8,000/month: 30–50 hours of active development — a steady feature delivery cadence. Suitable for post-launch SaaS companies that need continuous product development but aren't ready to hire in-house. Your team delivers one sprint's worth of features per month.
$8,000–$15,000/month: 50–80 hours — effectively a fractional senior developer plus PM overhead. Suitable for growth-stage startups using your team as their entire engineering function.
Retainer vs. project pros and cons: Retainers provide revenue predictability but require ongoing relationship management. Projects provide clear endpoints and margin control but create feast-or-famine revenue cycles. The optimal dev shop revenue mix for stability: 50–60% retainer revenue, 40–50% project revenue. This provides predictable base revenue with upside from project work.
Presenting Pricing in Your SOW and Proposals
How you present pricing is as important as the numbers themselves. Client-facing pricing should always include: a scope summary (exactly what's included), a milestone payment schedule, assumptions that affect the price (e.g., 'client will provide design mockups by week 2; delay beyond 5 business days may affect timeline'), and explicitly named exclusions (e.g., third-party API fees, App Store submission fees, server costs).
Present three options whenever possible (Good/Better/Best or Bronze/Silver/Gold). A $50,000 MVP quote feels expensive. The same $50,000 quote presented as the middle option between a $30,000 'core feature MVP' and a $75,000 'full launch-ready product' anchors it differently — and some clients will choose the $75,000 option.
Use Proposify (proposify.com — $49/month) to send professional, trackable proposals. Proposify shows you when the client viewed the proposal, which sections they spent time on, and allows e-signature. The psychological close rate difference between a clean Proposify proposal and a PDF is real — close rates on Proposify proposals run 15–25% higher for many agencies.
RECOMMENDED TOOLS
Some links above are affiliate links. We may earn a commission if you sign up — at no extra cost to you.
FREQUENTLY ASKED QUESTIONS
Should I always quote a fixed price or is time-and-materials sometimes better?
Fixed price is better for you (forces scoping discipline and protects margin if you're efficient) and often preferred by clients (eliminates their budget uncertainty). Time and materials is better when requirements are genuinely undefined and scoping would take 4+ weeks — typically for legacy system modernization, complex integrations, or exploratory product development. Never do time-and-materials without a not-to-exceed (NTE) cap in the contract.
How do I handle a client who thinks my MVP quote is too high?
First, identify whether they're comparing to offshore shops or DIY tools — both are irrelevant comparisons to a U.S.-quality dev shop. Second, offer a reduced scope option: 'I can deliver a $25,000 version that covers the core three features and drops the analytics dashboard to a future phase.' Third, connect your pricing to their business outcome: 'If this MVP generates $150,000 in year one, a $40,000 build investment is a 3.75x return.'
When should I transition a project client to a retainer?
The ideal retainer conversion moment is 4–6 weeks before a project ends — when you can demonstrate specific ongoing needs: 'You'll need ongoing feature development for Phase 2, and post-launch support as user feedback comes in. A $6,000/month retainer secures our team through Q3.' Convert projects to retainers before the project ends, not after.