Fixed price vs hourly vs retainer: how to read a Laravel quote
A fixed price is a bet on a written scope. An hourly rate is a bet on the relationship. What the quote structure tells you about the project.
Quotes are not just numbers; they encode who carries the risk. Reading the structure tells you how well the vendor understands your project and where the arguments will happen later.
Fixed price: buy certainty, pay a premium
The vendor adds a contingency of 15–30% for unknowns. It works when the scope is written down and unlikely to change. It fails when "one more feature" becomes a change request negotiation every week.
Hourly: pay for the truth
You see the real cost and can stop at any time. It requires trust and a regular status report. For maintenance and exploratory work it is usually the fairest model on both sides.
Monthly retainer
A block of hours or a dedicated person at a fixed monthly cost. Best value for ongoing product work, but check the rollover policy and the notice period.
What a good quote contains
Scope in numbered deliverables, assumptions, exclusions, the rate and hours by phase, the payment schedule, the acceptance criteria and what happens after launch. A one-line quote is not a quote; it is an opening position.
Frequently asked questions
Should I ask for a discount on a fixed price?
You can, but you are mostly negotiating the contingency down. That increases the chance the vendor cuts testing or walks away when the scope grows.
What is a reasonable deposit?
30–50% up front for a new client is normal. Milestone payments after that, with a final payment on acceptance rather than on "deployment".
More on this topic: Business & pricing articles.
Admin
Related articles
Rescuing a half-finished Laravel project: what it costs and where to start
The first week is diagnosis, not code. Budget a fixed audit fee, then decide between finishing, rewriting and restarting the parts...
What does it cost to build a marketplace app in 2026?
Marketplaces are two products plus the hard part in the middle: payments, disputes and trust. Budget double a normal SaaS before y...
Is Laravel still worth it in 2026? An honest answer
Yes for most web products, with three caveats: yearly upgrades, fewer AI/ML libraries than Python, and a hiring pool that skews to...