Choosing a project or a retainer is not a discount question. A project is work whose written scope closes and whose handover is done. A retainer is responsibility that still produces decisions after launch. The wrong model is either a project that never ends or a monthly invoice with nothing in it.
When a project is enough
If the pages, the languages, the form and the delivery date are known, a project is enough. A first application, one integration, or setting up accounts in the company’s name can be a project too. The finish line is written. “Until we like it” is not a line. When the work closes, code ownership stays with the company and the list is handed over. Account ownership is named in that same list.
When a retainer is the right instrument
If, after launch, the page, the campaign and the software use each other’s data, responsibility continues. Each month a small item arrives, measurement drifts, access needs a check. Without that tempo a retainer is rent for an empty seat. With that tempo the queue is written. An hour pot is not.
Do not sell both in one sentence
Folding the project into the retainer hides the finish. Selling the retainer as unlimited small jobs hides the sequence. The written scope either carries a date and a delivery, or it carries the month’s items. If you need both, the project ends first. A separate monthly scope opens after that. The passage is not an automatic renewal.
The decision is three questions
Does the work close this quarter. If it does not, who approves the sequence each month. When you leave, who holds the accounts. If those answers are missing, choosing a model is early. HED Creative is the accountable partner in Berlin and Ankara and writes both models with the same handover rule: access stays with the company, and the partnership is not a hostage arrangement.
To see the decision in writing, the IT partner brief is enough. The queue shape of the monthly model: retainer scope.