Two companies with identical budgets can hire the same studio under completely different terms, and both can be right. A fixed project and a monthly retainer are not tiers of the same thing; they solve different problems. Choosing the wrong one is how businesses end up paying for availability they do not use, or nickel and diming a partner into indifference.
What a project actually buys
A project is a defined outcome for a defined price: this scope, this timeline, this deliverable. A marketing site, a redesign, an app’s core flows.
It is the right model when the destination is clear. You know roughly what you need, the work has an end, and success looks like a launch. You get a fixed number to take to whoever signs it off, a schedule you can plan around, and a studio motivated to be efficient because their margin depends on it.
The cost of that clarity is rigidity. Scope becomes a boundary that has to be defended by both sides, and every genuinely good idea that arrives in week three has to be negotiated rather than simply built. That is not a studio being difficult; it is the mathematics of a fixed price, and it is why a specific brief is worth the hour it takes to write.
What a retainer actually buys
A retainer buys reserved capacity: an agreed amount of design and development time per month, spent on whatever matters most at the time.
It fits when the work is continuous and the priorities move. A product shipping every sprint, a marketing team publishing landing pages, a company running experiments. There is no scope negotiation for each small thing, which removes an enormous amount of friction: the request goes in the queue, the queue gets ordered, the work ships.
The cost here is different. You are paying for capacity whether or not you fill it, which punishes teams who go quiet for a month. Retainers also need someone on your side to feed them. A studio holding time for you with no direction produces the worst outcome for everyone.
The signals that point one way or the other
Choose a project when you have a launch date, a board or client expecting a specific deliverable, an approval process that needs a fixed number, or when this is your first time working with the studio and both sides need a low risk trial. It is also the honest answer when the work genuinely finishes, which a marketing site build usually does.
Choose a retainer when your requests arrive weekly rather than quarterly, when priorities change faster than a scope document can be amended, when you have a product in active development, or when the real value is response time rather than any single deliverable.
Choose both, in sequence, which is what most of our longest relationships look like: one project to build the thing, then a smaller monthly arrangement to keep it moving.
What a retainer should include, in writing
Retainers go wrong when nobody defines them, so insist on the specifics before signing.
How much time, expressed in a unit you understand (hours, days, or a number of concurrent requests). What response time you can expect. Whether unused time rolls over, and for how long, since indefinite rollover is rare and none at all is harsh. Who decides priority when two things compete. What sits outside the arrangement entirely: usually large new builds, which get quoted as projects.
And a notice period that is short enough to be fair, since a retainer defended by a long lock in is a retainer that stopped earning its place.
The maintenance question is separate
Do not confuse a design retainer with hosting, updates, and security patching. Those are a maintenance arrangement, usually far cheaper, and often better handled separately so the design budget is not quietly consumed by plugin updates.
Similarly, a retainer is not a substitute for a discovery phase on genuinely new work. New builds deserve their own scope, their own estimate, and their own timeline conversation, even if the same team delivers them.
Rough shape of the money
Projects for a serious custom marketing site typically run in the thousands to low tens of thousands depending on page count and complexity, and the honest ranges are worth reading before budgeting.
Retainers usually start at a fraction of that per month, and the useful comparison is not against a project fee but against the cost of the alternative: a full time designer with salary, tools, and management overhead, or the slower compounding cost of a site nobody updates. That trade off is the same one behind hiring in house versus hiring a studio.
Whichever model you pick, judge the studio on the same criteria: evidence they have shipped things like yours, clarity about what happens when something goes wrong, and straight answers to uncomfortable questions.
Not sure which shape fits your next six months? Say what you are trying to get done and we will tell you honestly, including when the answer is a small project rather than a commitment: hello@beconfidency.agency.
If you want a team that can work either way on the same site, that is exactly what our web design service is for.