Compare · Fixed price vs retainer
A retainer buys you availability every month. A fixed-price engagement buys you one finished outcome. They are different purchases and they fail in different ways: a retainer can quietly become a subscription nobody reviews, and a fixed price can be the wrong instrument for work that never stops. This page sets out which is which.
Summary
A fixed price and a retainer allocate commitment differently. Under a fixed price the supplier commits to a scope, a timeline and a number, the engagement has a defined end, and the buyer knows what they are getting before they say yes. Under a retainer the buyer commits to a recurring amount and the supplier commits to availability, which is the honest purchase when the work is continuous and nobody can name a finishing line. The failure mode of a fixed price is that it needs a definable scope, and work that is still being decided does not have one. The failure mode of a retainer is quieter and more common: it becomes a line item nobody reviews, the monthly output drifts, and because there is no acceptance criterion there is nothing to hold it against. J Labs prices every build as a fixed scope, timeline and price, from the Spec at €5,000 through to multi-phase builds above €200,000, with a change order for anything beyond scope that you are free to decline. Ongoing support exists where a client wants it, and it is a separate decision rather than a condition of the build.
Side by side
| Fixed price per engagement (how J Labs works) | A monthly retainer | |
|---|---|---|
| What you are buying | One defined outcome, with acceptance criteria written down and agreed before anything is built. | Availability: a number of hours or days a month, directed by you as priorities arrive. |
| When it ends | At handover, against the criteria. Anything after that is a separate decision. | When somebody cancels it, which is a decision nobody is scheduled to make. |
| Who carries the estimate risk | The supplier. If the work takes longer than we thought, the price does not move. | Neither party explicitly, which in practice means the buyer absorbs a slow month. |
| How it is reviewed | Against the written acceptance criteria, which is a yes or no rather than an impression. | Against a monthly report, unless a scope was agreed, in which case it is half a fixed price. |
| Cost model | One price per engagement, from €5,000 to €200,000+, with change orders beyond scope. | A recurring monthly amount that continues whether or not there was work that month. |
| What a change costs | A change order with its own scope, timeline and price, which you decide whether to commission. | Nothing visible, because a change is just what gets worked on next. That is the appeal and the risk. |
| Who ends up owning the knowledge | Your team, by design: weekly check-ins with them in the room and documentation written as we go. | The supplier, cumulatively, which is why a long retainer is hard to leave. |
| Best for | A workflow you can describe in a paragraph, with an owner and a budget holder who needs the number first. | Work that genuinely never stops: running an operating system, a queue, or a platform that keeps moving. |
The honest call
Choose fixed price per engagement (how j labs works) when
You want something finished rather than something ongoing. A defined outcome, built, tested against criteria you agreed, handed over, with the accounts and licences in your name. The Spec at €5,000 is the smallest version of that: one outcome, specified, built and tested, delivered within fifteen working days of the scope being agreed.
The budget holder needs a number and an end date. A fixed price is a decision a finance director can actually make, and it has a finishing line in it. A retainer is a decision to keep spending, which is a harder one to approve and a much harder one to review a year later.
You do not want to be hard to leave. Fixed scope, documentation written as we go, your team learning it as it is built, and nothing after handover that is a condition of anything. If you want ongoing support afterwards, that is a separate conversation we are happy to not have.
Choose a monthly retainer when
The work is genuinely continuous. Somebody has to run the thing: watch the failures, tune the rules, handle the exceptions, keep up with a platform that changes underneath you. That is an operating cost, not a project, and pretending otherwise produces a series of small fixed prices with gaps between them.
You want capacity on tap rather than a deliverable. Priorities that change monthly, a backlog you want someone chipping at, a person who already knows your systems and can start on Monday. A retainer buys exactly that, and a fixed price would add a scoping conversation to every small thing.
The relationship is the point. Some companies want a supplier in the room who knows the history and can be asked. That is real value and it is not shaped like a deliverable. J Labs does this for one client as a weekly commercial review cadence, and it sits outside the build pricing deliberately.
Frequently asked
Or start with our brief templateWe reply within one business day.