--- title: "The architecture behind creative operations at enterprise scale" description: "How one internal platform gives creative teams their pace and gives the enterprise approvals, access control, and an audit trail." canonical: "https://stackdrop.co/blog/governed-creative-operations-architecture" published: "2026-04-01T09:00:00.000Z" updated: "2026-04-01T09:00:00.000Z" authors: ["John Miniadis"] topics: ["Workflow automation", "Production"] readers: ["builders", "operators", "leaders"] --- # The architecture behind creative operations at enterprise scale A banner for a new market starts as a request in a chat thread. It is reviewed over email, checked against brand guidelines in a shared document, and tracked in a separate task tool. Nobody can say where it is waiting, and the campaign date moves. Enterprise creative teams produce more formats, in more languages, for more markets every year. When delivery slows and brand mistakes creep in, the first assumption is a shortage of designers. Usually the people are there. The constraint sits in how the work is coordinated between tools. This piece covers where that breaks, what the platform underneath needs, and how it worked at Saxo Bank. ## Where creative operations break The pattern repeats across industries: a bank running campaigns in several markets, a retailer coordinating regional agencies with an in-house team, a software company producing marketing for several business units. The details vary. The breakdown is the same. Work starts in one tool, gets reviewed in another, approved somewhere else, and tracked separately. Brand compliance, legal sign-off, and localization rules sit outside the workflow and depend on someone remembering to check. As volume grows, coordinating the work starts to take longer than doing it. Three failure modes show up most often: - **Copied instead of shared.** Asset IDs, files, and tasks are copied between systems, and the copies drift. - **Checks after the fact.** Brand and legal review happen downstream, as a separate step, so mistakes are found late. - **Rebuilt every time.** Each campaign rebuilds its own workflow, so nothing gets faster with repetition. Output keeps rising. Quality and consistency get harder to hold. ## Why fewer tools is not enough The usual response is to consolidate tools. Fewer platforms do mean fewer handoffs. They do not change how work moves from request to launch. One platform with no structure still leaves the team bridging the gap between the tool and the way the work actually happens. Brand checks stay manual, and the delay simply moves somewhere else. What makes the difference is how the tools are connected, and whether the lifecycle of the work is built into that connection. ## What the platform layer needs ### Built around the lifecycle of the work The data model follows the work: a request, its brief, the market and language, each format, each review, each approval, the launch. Every record has an owner and a status, and the interface shows both in real time. The existing tools stay. Asset management, task tracking, previewing, and publishing keep doing their jobs. The platform coordinates how work moves between them, through integrations, so nobody copies a file or an ID by hand. ### Controls inside the workflow Brand and legal rules become part of the flow. Role-based permissions decide who can submit, review, and approve each kind of asset. Approval steps are defined once and applied to every request, so work moves forward only when its conditions are met. Every action is logged with who did it and when. That gives legal and compliance a traceable record without anyone assembling it before an audit, which matters in regulated sectors such as banking. ### Room to grow New markets, channels, and formats arrive every year. The data model should take a new workflow or dataset without a rework. Analytics belong inside the platform, so the team can see where work slows without a separate report. Alerts should flag a stalled review before it costs a launch date. ## The architecture in practice: Saxo Bank [Saxo Bank](https://stackdrop.co/customer-stories/saxo-bank) serves over 1.5 million clients. Its creative operations team localizes, brand-checks, and publishes assets across 13 offices, 19 languages, and every key channel. Output was high, and the bank's compliance requirements were strict. The constraint was coordination across that footprint. Requests, briefs, approvals, and assets were spread across disconnected tools. Brand rules were enforced outside the workflow, by hand. As volume grew, the overhead showed up as delayed launches. We built Launchpad, an internal platform on Retool that brings the creative lifecycle into one interface. The approach was integration rather than replacement: - **Zuuvi** handles asset previews. - **Bynder** provides access to the digital asset library. - **Podio** keeps tasks and deadlines in sync. Brand and approval rules were defined once and applied to every workflow through role-based logic. Analytics were built into the platform, so the team could see where work slowed down. When Saxo later introduced a new creative tool, the integration layer took it on without disturbing the existing workflows. ## What changed Saxo's own analysis measured the result: - **Median time to market fell 78.3%,** from 310 hours to 67. - **Time to review fell 86.1%,** from 8.1 days to 1.1. - **Within a year,** the platform processed 970 submissions and supported more than 5,800 creative formats, which generated 1.74 billion impressions. Speed and control improved together, because the checks moved into the workflow instead of sitting on top of it. ## Where to start Map one campaign from request to launch with the people who run it. Note every tool it touches, every manual check, and every place it waits. That map shows which integrations the platform needs, and which rules can move into the workflow. For the controls in more detail, see [four controls that make an internal tool safe to rely on](https://stackdrop.co/blog/governed-internal-tools-reduce-risk). For why mapping comes first, see [why your internal tools behave the way they do](https://stackdrop.co/blog/systems-logic-internal-tools). ## Our view We recommend building the platform layer around the lifecycle of the work and keeping the tools the team already uses. Replacing them adds a migration to a coordination problem. Brand and legal checks belong inside the workflow, because a check that sits outside it is the first thing skipped under deadline pressure. The creative operations lead stays the product owner and decides which rules are enforced, and where. We bring the architecture, the integrations, and the running of it.