The Microsite Graveyard: What Running Promotions One Build at a Time Really Costs

Most brands don't have a promotions framework. They have a pile of one off builds.

It doesn't feel that way at the start. The first promotion goes out, it works, everyone's happy. Then the next brief lands, and it gets its own microsite, its own domain, its own supplier, its own compliance review. Same again for the one after that.

Run five or ten promotions a year across a couple of brands and it adds up fast. Three years later you're sitting on dozens of dead URLs, a folder of logins you've half forgotten, and a setup process that costs you the same pain on promo number twenty that it cost you on promo number one.

That's the microsite graveyard. And most brands are living in it without ever calling it what it is.

The cost nobody puts on the invoice

Here's what actually happens every time a promotion gets built from scratch.

Someone rebuilds the entry form. Someone rebuilds the unique code handling. Someone rebuilds the instant win logic, the receipt validation, the SMS and email flows, the wallet passes, the fraud checks, the reconciliation, the reporting. Then someone tests all of it again, because none of it carried over from the last campaign.

Every one of those is a line item. Every one gets quoted again, rebuilt and retested. Not because the work is new, but because there was never anything underneath to build on.

That's the tax. It doesn't show up as a single number on a quote, which is exactly why it's so easy to keep paying. It hides across a dozen briefs and a dozen invoices, campaign after campaign.

And it isn't only money. It's the compliance review you run from zero every time. It's the domain you register, point and eventually let die. It's the reporting that lives in a different place for every promotion, so you can never see the whole picture across a year.

Custom is not the problem

Here's where a lot of brands get the fix wrong.

They assume the only way off the treadmill is to reuse the same promotion. Same mechanic, same look, rinsed and repeated. Cheaper, sure. But now every campaign feels like the last one, and your customers notice.

That's the wrong trade. Custom is not the problem. Rebuilding the engine underneath every single time is the problem.

The promotion should be bespoke. Built for the brand, for the audience, for the moment. The infrastructure underneath it should not be. You should never pay to reinvent code reservation or fraud checks or wallet delivery just because the creative changed.

Get that distinction right and the whole equation flips. You keep everything that makes a promotion feel custom. You stop paying for everything that shouldn't have to be rebuilt.

What a framework actually looks like

A framework is the layer that stays, so every campaign starts ahead instead of starting over.

One platform hosts every promotion, across every brand in your portfolio. Live promos and archived promos, all in one place, instead of scattered across suppliers and forgotten logins.

Any campaign embeds directly onto the brand's own website, so the domain problem disappears. No new URLs. No graveyard. The promotion lives where your customers already are.

The hard parts are built in, not bolted on. Unique codes, instant win, receipt validation, gift card fulfilment, wallet passes, SMS and email, fraud protection. Not rebuilt for each brief. Ready, tested and waiting.

And because every promotion runs on the same framework, they compound. The data doesn't vanish when the campaign ends. It stacks. Every promotion you run makes the next one smarter, faster and cheaper to launch.

That's the difference between a pile of builds and a framework. One costs you the same setup pain forever. The other gets better every time you use it.

The test

Here's the simplest way to know which one you've got.

If promotion number ten still costs you the same setup pain as promotion number one, you don't have a framework. You have a graveyard with better landscaping.

You should have a framework. And you shouldn't have to give up custom to get one.

That's what we built Fronterly to be.