Retainers vs project work for restaurants
Projects are for the leap: a new site, a live menu, a second location. Retainers are for the Tuesday hours change and the thing that broke at lunch.
Project work fits a destination. Retainers fit a kitchen that keeps changing. Using the wrong shape creates either endless extras or constant re-onboarding.
The common mistake is project-pricing continuous needs. Every hours tweak becomes a negotiation. Small fixes wait. The site drifts.
The opposite mistake is a major rebuild on a vague monthly rhythm with no milestones. Big work needs a visible sequence.
Hybrid is how most of our restaurant relationships run. A project for the leap, a retainer for the runway, Quiteful for the menu so publishing is not a ticket.
Pick the shape that matches service, not a generic agency package.
Common questions
- When is a project the right shape?
- When done is a launch: new site, migration, Quiteful going live, a group template for new rooms.
- When is a retainer the right shape?
- When the work is uneven and ongoing — seasonal menus, landing pages, performance, small integrations.