A Campaign is the unit of work in Brandflux. It replaces the generic “Project” terminology because the work it represents is closer to a marketing campaign than to a software project: a defined goal, a defined audience, a defined deadline, a defined set of deliverables, and a closing handoff.
One campaign, one brand
Every Campaign belongs to exactly one Brand. The Brand DNA is the rendering anchor for everything the campaign produces. A creative-ops team working across four brands runs four parallel campaign tracks, not one shared campaign with four sub-folders.
The campaign arc
A Campaign runs through three macro phases, plan, make, and ship, each composed of several stages:
- Plan. Brief, references, named Directions. Signed off as a single unit, not stage by stage.
- Make. Variations rendered against the published DNA. Comment-first concept review on named directions. Production renders of the chosen direction.
- Ship. Final approval, locked masters into the DAM, delivery to the channel queue or direct download.
The phases are sequential, the stages inside each phase have an explicit ordering, and the boundary between phases is an approval moment, not a state machine flag.
Why campaign and not project
“Project” carries software-engineering connotations (open-ended, iterative, never quite done). A Campaign has an end state by definition: locked masters delivered, performance tracked, archive closed. Naming the unit “Campaign” sets the right expectations for everyone in the workflow, including clients who don’t know what a Brandflux is yet but do know what a campaign is.
Related on this site
- /glossary/brief, /glossary/direction, /glossary/variation are the artifacts inside a campaign.
- /glossary/plan-make-ship is the macro arc.
- /product walks through the campaign workflow end to end.