Insights · 5 min read
A billboard design platform is a production system, not an ad server. Where the real work sits: the artwork pipeline, approval loops, and print-ready exports.
By GGP Editorial
We built a billboard design platform for a Brazilian client, alooz.com.br, and the part everyone underestimates is not the ad serving. It is the artwork pipeline. Getting a design from a client's brand folder to a print-ready file, through approvals, and out to a physical billboard is where the real work sits.
Most people think an advertising platform is a media-buying tool. For the businesses we talk to, it is a production system. Ads have to be made, checked, and delivered before any impression is ever counted.
A billboard design platform takes a client's logo, a size, and some copy, and hands back a file the printer can use. Between upload and download there are a dozen steps nobody puts on a slide.
The file has to land in the right color space, at the right resolution, with the right bleed and safe margins. A design that looks fine on a laptop screen can be useless on a ten-meter board. Our platform handles the conversion and validation automatically, so a designer does not need to know the difference between CMYK and RGB, or which DPI a given printer expects.
Asset quality is the other silent killer. Clients send a logo pulled from a website, which is fine for a screen and useless for a print at twenty meters. The platform has to catch that at upload time, flag the low resolution, and either upscale cleanly or ask for a better file, before it reaches the proof stage. Catching it early is what stops a campaign from being printed wrong.
Here is what that pipeline looks like in practice:
| Stage | What happens | Where it goes wrong |
|---|---|---|
| Upload | Client sends logo and copy | Wrong format, low-res logo |
| Layout | Template applies size and margins | Text overflow, wrong ratio |
| Proof | Client approves a preview | Misunderstanding about final size |
| Export | Print-ready file is generated | Color space or DPI mismatch |
| Delivery | File goes to the printer | Late changes after approval |
Most of the bugs we fix sit in the gap between proof and export. What the client approves is not always what the printer receives, and closing that gap is where a platform earns its keep.
A design that has to be approved by a brand manager, a client, and a printer spends most of its life waiting. Every revision is an email, a wait, and a version number.
We build the approval into the platform instead of leaving it in email threads. Each version is tracked, the approver sees exactly what changed, and the final sign-off locks the file. It sounds small, but it removes the "which PDF was the final one?" problem that haunts every campaign.
The Brazilian market made this concrete. Our client runs campaigns across cities with different sizes and formats, and the whole team works in Portuguese. We support the platform in English and Portuguese, and our engineers overlap working hours with the São Paulo team, so a production question does not wait a full day for an answer. That kind of cross-border delivery matters more than any feature list.
The temptation is to build the dashboard first: impressions, spend, charts. Resist it. A dashboard with nothing real behind it is a demo. The production path, from upload to print-ready file to delivery, is the part that has to be solid before anything else.
Multi-format is the hidden multiplier. A campaign that runs on a roadside billboard, a bus shelter, and an in-store screen is three different aspect ratios, three different DPI targets, and three different files. A designer doing this by hand redoes the layout each time. A platform that treats each format as a template reuses the same artwork and re-renders it, which turns an hour of fiddling into a click.
We use the same stack across these builds: Java and Spring Boot on the backend, Vue or React on the front, Redis for the fast path, and object storage for the artwork files. Rendering and file conversion run in background jobs so a large upload does not freeze the interface. The stack is not the story. The workflow is.
Once production works, the reporting layer pays for itself quickly. A client who can see which formats are used most, which campaigns are running, and where the approval queue is stuck will make better decisions than one chasing files by email.
A simple design-and-download platform starts in the tens of thousands of US dollars. The cost climbs with the number of formats, the integration with real printers or ad networks, and the depth of the approval workflow. Billing, multi-tenant workspaces, and real-time campaign reporting are a separate phase, and they should come after the production path works.
My advice to anyone planning an advertising platform is to write down the ten most common jobs your team does by hand today. The platform that automates those ten jobs is worth building. The one that only reports on them is not.
If you are planning an advertising or billboard platform, tell us the sizes and formats you actually produce. That list tells us more about the build than a feature wishlist.
Tell us what you are building and where you are today. We typically reply within 24 hours.
