Compare · For brands
Build or buy a retail partner platform: the Retail Activation cost structure
Last updated
Building a partner platform with an agency is a real option, and for some brands the right one. The trap is that the build quote is the visible cost and the smallest one. What follows is a relationship where every change is a billable request: a new market, a new campaign template, a field the buying team wants, a design tweak before a launch. With many agency builds, even publishing content is a request rather than something your own team does. Before comparing a build quote to a subscription, price the second year rather than the first, and count who has to be paid before a campaign can go live.
The cost structure, so you can price it yourself
Three lines, and only the first one appears in the quote.
1. Build. Scoping, design, development, integration, launch. This is the number on the proposal and the one everyone compares against a subscription. The build is also the only cost line that ends.
2. Change. Every subsequent alteration. A new market. A new language. A new campaign format. A field the commercial team needs. A fix after a browser update. Each is scoped, quoted and invoiced, and each carries the agency’s lead time as well as its rate. Ask your agency what a typical change request costs and how long it takes, then multiply by how often your retail programme actually changes. For most brands that is monthly, not annually.
3. Publishing. The line most people forget. With many agency builds, getting content live is a ticket to the agency rather than a task for your own team. If that is the arrangement, you are paying per campaign to use the thing you already paid to build, and your launch date depends on someone else’s queue.
Then add the two things that are not invoiced at all: the internal time spent briefing, checking and chasing, and the cost of the changes you do not make because each one needs a quote. That last one is the real damage. A platform your team cannot change is a platform that slowly stops matching the programme.
An agency build and Atobi compared
Agency build | Atobi | |
|---|---|---|
Visible cost | A build quote, then change requests | A subscription |
Publishing a campaign | Often a billable request with a lead time | Your team, same day |
Making a change | Scoped, quoted, queued | Configuration |
New market or language | A project | Automated localisation, text through to video |
Who maintains it | You pay for maintenance, and for keeping up | Included |
Ownership | Yours outright | Subscription |
Reaching store staff without a login | Has to be built | Link or iframe, no login |
Retailer approval of what its staff see | Has to be built | Built in |
Proof a store is ready before launch | Has to be built | Built in |
Improvements from other customers | None. You fund every one | Arrive with the platform |
Where building is the better choice
Build when the requirement is genuinely unusual and central to how you compete, when you have the in-house capability to run the platform after launch, or when owning the asset outright matters more than the running cost. Those are good reasons and they are not rare.
A build also gives you something a subscription cannot: the platform is yours. No vendor risk, no renewal, no roadmap you do not control. For some brands that settles it, and it should.
Where Atobi is stronger
The honest comparison is not build cost against subscription cost. The honest comparison is the second year against the second year. A platform absorbs change as configuration; a build absorbs change as invoices. A retail programme changes constantly, so the gap widens rather than closes.
The other difference is what you would have to build to match the starting point: reaching store staff without an account, an approval step the retailer controls, proof of readiness per store before a launch, and localisation across text, subtitles, images and video. Each of those is a project on its own, and none of them appears in a first build quote, because nobody thinks of them until the programme is live.
Frequently asked questions
Should we build our own retail partner platform or buy one?
Build if the requirement is genuinely unusual and central to how you compete, and you have in-house capability to run the platform afterwards. Otherwise the arithmetic usually favours buying, and not for the reason people expect. The build quote is rarely the problem; the change costs are. A retail programme changes monthly, and with an agency build each change is scoped, quoted and queued. Compare the second year, not the first.
What does an agency-built partner portal really cost?
Three lines, and only the first is quoted: the build, every subsequent change, and in many arrangements the publishing of content itself. Ask your agency what a typical change request costs and how long it takes, then multiply by how often your retail programme changes. Add the internal time spent briefing and chasing, and the improvements you quietly skip because each one needs a quote.
Can we not just get the agency to maintain it?
You can, and that is the normal arrangement. The thing to check is what counts as maintenance and what counts as a change, because a change is billed separately and the boundary is usually the agency’s to draw. Also ask whether publishing a campaign is something your own team can do, or a request you submit.
