Working with an agency
Fixed price, retainer or dedicated team: which one fits your project
How fixed-price, monthly retainer and dedicated team engagements work, where each one goes wrong, and how to choose the right one for your project.
The short answer: choose fixed price when you can write down exactly what you want and it won’t change much. Choose a monthly retainer when you need steady, smaller pieces of work over time. Choose a dedicated team when you are building a product that will keep evolving for six months or more and you want people who know it inside out.
Most problems between businesses and agencies aren’t about skill. They come from a mismatch between how the work was priced and how the work actually behaved. Here is how each model works, and where each one tends to go wrong.
Fixed price
You agree a defined scope, a price and a timeline. The agency carries the risk of its own estimate: if the work takes longer than they thought, that is their cost, not yours.
It suits a marketing website, a store on a known platform, a clearly specified internal tool, or a first version with a firm feature list. Where it goes wrong:
- Scope that wasn’t really defined. “User management” can mean a login page or a full roles-and-permissions system. Fixed price only protects you if the scope document is detailed.
- Every change becomes a negotiation. New ideas need a change request. That is fair, but it feels slow if you are still discovering what you need.
- You pay for certainty. Because the agency carries the risk, a sensible one adds a buffer to its estimate.
- Corners get cut late. If the estimate was too low, testing and polish are what get squeezed in the final weeks.
Monthly retainer
You pay a fixed amount each month for an agreed block of time or set of outcomes. It is built for ongoing work: maintenance, small features, SEO, content, ad management and design support.
It suits a live product that needs regular improvements, growth work that builds over months, or a business that wants a team on call without hiring one. Where it goes wrong:
- Paying for hours you don’t use. Agree what happens to unused time, and review usage together every month.
- No clear priorities. Without a shared list, a retainer drifts into reacting to whatever came up this week.
- Unclear deliverables. An SEO or ads retainer should come with a written monthly plan and a report, not just an invoice.
Dedicated team
The agency assigns specific people, for example two developers, a part-time designer and a project lead, who work mainly on your product for a set period, usually six months or longer. You pay monthly for the team, and you set the priorities week by week.
It suits a SaaS product or platform under active development, a business that would otherwise hire an in-house team, or a roadmap that will change as users respond. Where it goes wrong:
- Nobody owns the product on your side. Someone has to decide what gets built next. Without that person, a dedicated team will be busy without being useful.
- The total cost is open-ended. You are paying for time, not a defined result, so track what actually ships every sprint.
- People change. Ask how the agency handles leave and replacements, and how much notice you will get.
Side by side
| Fixed price | Monthly retainer | Dedicated team | |
|---|---|---|---|
| Best for | Defined projects | Ongoing, smaller work | Evolving products, 6+ months |
| You pay for | An agreed scope | A monthly block of time or outcomes | Named people’s time, monthly |
| Who carries estimate risk | Mostly the agency | Shared | Mostly you |
| Room to change direction | Low, through change requests | Medium | High |
| What you need to bring | A clear brief and quick feedback | A prioritised list each month | A product owner who decides weekly |
| Budget predictability | High | High per month | Predictable per month, open-ended overall |
| Main risk | Scope gaps and change disputes | Unused hours and drift | Paying for activity, not progress |
Combining models
Many projects use more than one. A common pattern: a short paid discovery phase to define scope, a fixed-price build for version one, then a retainer for maintenance and small features once real users arrive. If the product takes off, it may move to a dedicated team.
Mixing is fine as long as each phase has its own clear terms. Trouble starts when a fixed-price contract is stretched to cover open-ended work, or a retainer is used to sneak in a large new build without a proper plan.
Five questions to help you decide
- Can you write down, screen by screen, what version one does? If yes, fixed price is realistic.
- Will the work continue for months in small pieces? Consider a retainer.
- Is the software your product, and will it change based on what users do? Consider a dedicated team.
- Who on your side has time to make decisions every week? If nobody does, hold off on a dedicated team until someone can.
- How fixed is your budget? If the number can’t move, fit the scope to the number, not the other way round.
What to put in writing, whichever you choose
- What is being delivered, or what the monthly time covers.
- How changes are requested, estimated and approved.
- How and when you will see progress.
- Who owns the code, designs and accounts.
- How either side can end the arrangement, and what you receive if they do.
What we’d do
At Yakooha we work in all three ways: fixed price for a defined scope, a monthly retainer for ongoing work, and a dedicated team for engagements of six months or more. When a scope is still fuzzy, we would rather help you define it first than put a fixed number on guesswork. Whichever model you choose, you own the code, the repository and every account from day one, and every project includes 30 days of support after launch.
If you’re weighing this for your own project, send us a WhatsApp. A person replies within one working day.