Rollout, enablement, retainer
Launch and growth
A brand that never ships is not a brand. We plan the rollout, arm your team, and stay on through the first months of iteration.
The most common way a rebrand fails is not a bad design. It is a good design that reached the website and stopped — while the invoices, the van, the email signatures and the way the phone is answered all carried on as before, so customers experienced two companies at once.
So the rollout gets planned like the rest of the work. What changes on day one, what can wait a quarter, what is expensive enough to replace only when it wears out, and in what order, so that at no point does the new brand look like a coat of paint over the old one.
Your team is the other half. The people who will use this every week get shown how, in a session about the decisions rather than the file formats, so that someone making a social post at half past four on a Friday makes something that still looks like you.
Then we stay for the part most projects skip. The first months after launch are when the real questions arrive — the case the guidelines did not cover, the page that needs to exist now, the thing customers keep asking. We would rather be there for those than hand over a folder and disappear.
Questions we get asked
What happens after launch?
We stay for the first months, which is the part most projects skip. That is when the real questions arrive: the case the guidelines did not cover, the page that needs to exist now, the thing customers keep asking about.
Do we have to change everything at once?
No, and you probably should not. The plan says what changes on day one, what can wait a quarter, and what is expensive enough to replace only when it wears out — in an order where the new brand never looks like paint over the old one.
Is a retainer required?
No. It exists because for some companies the work genuinely keeps arriving, and paying for it in a predictable way beats a quote every fortnight. If that is not you, the handover is complete on its own.