Rolling out Brandflux to your studio.

You are an agency principal or studio owner. You have decided to subscribe to Brandflux. You need a plan to bring designers, account managers, and clients along without it feeling like a tool migration.

Two weeks is the right window. Week one is internal. Week two introduces clients. After week two, the team is either using Brandflux for live pitches or you have a clear list of reasons it did not fit. Either outcome is useful.

Before any rollout meeting, run a 90-minute pilot yourself. Not a designer. You. The point is to land on a sentence you can say at the team kickoff: here is what this tool does for one of our clients. The kickoff goes badly when the principal walks in with a vendor pitch and a signup link.

1. 1
   Pick one retainer client.

   A brand you know cold. The point is to test fit, not to pioneer a new account. The DNA needs to look right to someone who has lived it.

2. 2
   Run three briefs back to back.

   Safe, bold, and one in between. A safe brief mimics what the client signed off on last quarter. A bold brief tests something a designer would normally hesitate to send. The hybrid lives between the two.

3. 3
   Time the pitch versus last month.

   Look at last month's pitch deck for the same client. How many designer-hours went into it? Track the same number on the Brandflux pilot. The first comparison sets your baseline; subsequent rollouts get measured against it.

Write the comparison down. Not a spreadsheet. Three lines: hours then, hours now, what looked off. That note is the pitch you will use for the rest of the rollout.

The 45-second URL extract is fast enough that the team will be tempted to run it once and ship. Resist that. Each new client gets a 15-minute review pass before the first campaign runs. The eight-item checklist below is the minimum bar.

• Palette pulled correctly (primary, secondary, accents) and published.
• Headline type matches the live site, including the italic serif if there is one.
• Body type renders at the right weight for legibility at 4K.
• Voice samples capture both the formal and informal registers.
• Imagery references include three good and three bad examples.
• Do-not-use list documents the wrong logo, off-palette colors, banned phrases.
• Reviewer (designer or account lead) signed off on the DNA before any campaign runs.
• A second client extraction does not bleed into this one when both are open.

The last item is the one most teams forget. Open two client DNAs in separate tabs and run a quick variation in each. If a swatch from client A shows up in client B, raise it before going live; that is a brand-bleed failure mode and we want to see the report.

Reframe the role from translate the brief into pixels to curate output against the brief. The first day or two will feel demotivating to designers who take pride in the manual variation work. Name that out loud at the kickoff. Most designers settle into the curation role within a week once they see the volume.

Record a 30-minute Loom yourself walking through one full brief. Show the brief in, variations out, the moment you reject a generation, and the moment you nudge a DNA field instead of nudging a single asset. Designers learn the tool faster from a principal walkthrough than from any onboarding video we could ship.

Account managers get the biggest workflow change: review chains move from email PDFs to guest reviewer magic links. Fewer attachments, fewer "v3 final final" file names, and the version history lives with the work. Walk one AM through a full review cycle on a mock campaign before any live client sees a link.

Three things to flag at the AM kickoff: guest reviewer seats are free and do not count against your seat ceiling; reviewer comments thread on the variation, not the email; and the AM, not the designer, owns the link revoke when a campaign closes.

Do not announce a tool change. Clients do not buy tools. Send the first variation set for review without explaining the mechanics. If they ask about the link, the AM script is two sentences: this lets you comment in-line on each variation, no login. Reply here if you want a different review flow.

Save the introduction email for the second campaign. By then you have a real story: we shipped your campaign in half the rounds, here is the new review flow if you like it.

Map your existing RACI to Brandflux roles before the first live campaign. Designer generates and curates. Account manager owns the brief and the client-facing review link. Principal or creative director gets the approval ping when a campaign hits ready-to-ship.

On Professional, you can set required-approver roles per workspace. Use it. The default (anyone with seat access can approve) works for solo creators; agencies need the guardrail.

Branded client surfaces apply only to Studio-tier workspaces. Every paid plan exports clean files (no Brandflux watermark) regardless of tier; the watermark only appears on exports during the money-back guarantee window. On Studio, the review page, delivery page, and tokenized share links run on your own domain (CNAME + auto SSL) with your agency’s mark replacing Brandflux’s.

Set the branded-surfaces default at the workspace level, not per user. Designers should not be deciding, per surface, whether the client sees your brand or ours.

Three metrics, tracked weekly through month one. Comparable to the case-study numbers on the customers page so you can benchmark against shops further along.

• Designer-hours per pitch

  Track this weekly during the rollout. Brooklyn studio reduced this 62%; treat that as a ceiling, not a floor. A 30% reduction in month one is already material.

• On-brand approval rate

  Of variations sent to client review, what fraction comes back without "make this more on-brand" notes. Coffee D2C team hit 94%; agencies typically run lower because client preferences vary.

• Pitches shipped per week

  The agency principal's leading indicator. If pitch hours dropped but pitches did not increase, the team is reclaiming time elsewhere. Both outcomes are good.

At month one, if all three metrics moved in the right direction, the rollout is done. If two of three moved, you are mid-rollout; address the laggard before adding clients. If one or zero moved, file feedback with us. We want the report.