Project-Based Design vs a Design Retainer: Which Model Fits Your Company?

Short answer: choose a project when you need one defined outcome, such as a new brand identity or a website redesign, with a clear start and end. Choose ongoing design support when design needs come back every month and someone has to keep everything consistent. Most companies need both, in that order: a project to build the foundation, then continuity to protect it.

The question usually comes up at a precise moment. A rebrand is finished, the new website is live, and three months later marketing needs campaign visuals, sales wants a new deck and the product team is adding features. Do you go back to a quote for every request, or do you set up something ongoing? This article compares the two models honestly, including where each one goes wrong..

What is project-based design?

Project-based design is a fixed engagement with a defined scope, a timeline and an agreed price. You know what you are buying before it starts: a brand identity, a set of brand guidelines, a website, a product interface. When the deliverables are handed over, the engagement ends.

Its strength is clarity. The budget is approved once, the result is easy to evaluate, and it suits work that genuinely has an end, like building a foundation that does not exist yet. Its weakness shows up after delivery: nobody is responsible for what happens next.

What is a design retainer?

A design retainer is an ongoing agreement where a company pays a recurring fee, usually monthly, for continuous access to a design team. Instead of scoping each request separately, work is handled as it comes, within an agreed scope or capacity.

Its strength is continuity: no briefing from zero, no quote for every landing page, a team that already knows your brand. Its weakness depends entirely on how it is set up. A retainer that only buys hours turns design into a queue of tasks. A retainer built around ownership of your brand and product systems keeps them coherent as they grow. The billing format is the same. The value is not.

Project vs retainer: a side-by-side comparison

When does a project make more sense?

• You do not have a solid foundation yet: no clear identity, no guidelines, no consistent interface. Continuity cannot protect something that was never defined.
• The need is genuinely one-time: a rebrand, a website redesign, a new product launch.
• Your budget works per initiative and has to be approved project by project.
• You have an internal team ready to take ownership of the result once it is delivered.

In these cases, a well-scoped project is the right move, whether it is a brand identity built with a branding agency in Luxembourg or an interface redesign with a UX/UI design agency. Paying monthly before the foundation exists usually means paying to produce inconsistency faster.

When does ongoing design support make more sense?

• Design requests arrive every week, from different teams: marketing, sales, HR, product.
• You keep re-briefing different providers, and each one starts from zero.
• Your brand looks slightly different on the website, in presentations and on social media, and nobody can say exactly when it started.
• Your website or product keeps adding pages and features, and each one is designed a little differently.
• Nobody internally owns design decisions, so they are made by whoever is closest to the deadline.

If several of these sound familiar, the problem is not a lack of design work. It is a lack of continuity. It is the pattern we describe in why brands lose consistency as they grow: systems rarely break in one moment, they drift with every unconnected decision.

What does choosing the wrong model cost?

Projects only, no continuity. The rebrand is delivered with clean guidelines. Six months later, new pages, posts and documents have been produced by different people, each interpreting the rules in their own way. The company eventually pays for another redesign to fix a drift it could have prevented. Even a complete brand guidelines document needs someone to apply it and keep it up to date.

Retainer only, no foundation. A monthly agreement starts before the brand or the interface has been structured. Every request is handled quickly, but each one is a local decision. After a year, there is a lot of output and no system. On a website, it shows up as an interface that looks fine screen by screen and still feels confusing as a whole.

A retainer buys time. A partnership buys ownership.

Why we usually start with a project

At LostWoods, we rarely start with an ongoing agreement. We start with a structuring project, a Brand Foundation or a UI/UX Design engagement, because that is where the system gets defined: the identity, the rules, the components and the logic behind each decision. Once that system exists and works, continuity becomes worth paying for, because there is something real to protect and evolve.

That is what our ongoing design support is built for. Not a bank of hours, but continuous responsibility for your brand and product systems: design direction, recurring execution within the system, and governance as the organization grows. It is also why we do not take on purely reactive requests. Isolated tasks with no context do not need a partner.

How to decide: five questions to ask internally

1. Do we have a clear, documented foundation (identity, guidelines, interface logic)? If not, start with a project.
2. How often do new design needs appear: once a year, or every week?
3. Who owns design decisions today, and do they have the time and the authority to enforce them?
4. How much of our current effort goes into re-briefing, fixing and redoing work?
5. In twelve months, will our brand and product be bigger and more complex than they are today?

If the answers point in different directions, start by locating the problem. The Compass, our free brand and design diagnostic (6 questions, about 2 minutes), shows where consistency is breaking before you choose a model.

The takeaway

Project-based design and ongoing support are not competitors. A project builds the system. Continuity keeps it coherent. The real mistake is asking one to do the other’s job: expecting a one-off project to stay consistent on its own, or paying a monthly fee to produce work without a foundation. Choose based on where your company is today, not on the billing format.

FAQ

Is a design retainer cheaper than paying per project?

Not necessarily per hour, but often over time. The savings come from what you stop paying for: re-briefing new providers, quoting every small request, and redoing work that drifted away from the brand. If your design needs are occasional, projects will usually cost less.

Can we start with a retainer without a prior project?

You can, but it only works if a solid foundation already exists, built internally or by a previous agency. Without it, a retainer produces output faster without making it more coherent. In that case, a short structuring project first is the safer path.

What is the difference between a design retainer and a long-term design partnership?

A retainer describes how the work is paid for: a recurring fee. A long-term design partnership describes what the team is responsible for: the ongoing coherence of your brand and product systems, including direction and governance, not only execution. Some retainers work like partnerships. Many are simply blocks of hours.

How do we know it is time to move from projects to ongoing support?

When design needs become continuous rather than occasional, when several teams produce brand material, or when inconsistency starts creeping into your website, documents or product. Those are signs that the foundation now needs an owner, not another project.