Branded QR codes for agency clients — what they're worth

A generic black-and-white QR code on a client's flyer looks like you ran out of time. A branded one — the client's accent colour on the modules, their mark in the centre, a custom subdomain handling the redirect — looks like you actually finished the work. Most clients can't articulate the difference, but they notice it, and the scan numbers reflect it.

This is what branded QR codes are actually worth to an agency: what changes in the scan-through rate, how to price them as a deliverable, the static-versus-dynamic decision that ruins campaigns when it goes the wrong way, and why the short-link domain that handles the redirect matters as much as the design printed on the asset.

Why a branded QR reads differently than a generic one#

Three things change when you put real design effort into the QR rather than dropping the default output of a free generator.

The first is the asset itself. A black QR on a magazine ad reads as "we did the bare minimum". The same ad with a QR matched to the client's accent colour, with rounded modules, with a frame that says "Scan to RSVP" — that one reads as the same designer drew the whole thing. Clients don't have words for this, but they know which version their boss prefers when you put them side by side.

The second is the URL preview. Every modern phone camera shows the destination URL in a banner above the scan before opening it. A QR that resolves to qr.client.com/spring reads as legitimate. The same QR pointing at unmemorable-shortener.io/aH7k2X reads as someone phishing the user. The preview is the trust gate, and most agencies skip it entirely because they don't realise their generator is using its own domain. The DNS-to-scan setup that closes this gate for every client domain at once lives in the custom domains for QR codes walkthrough.

The third is the destination. A branded QR landing on a generic platform landing page wastes the trust the design just bought. Branded codes that end at a properly designed landing or a campaign-specific page convert at a different rate to ones that dump the user on the client's homepage. Pricing the engine into your client deliverable is the last piece — the lifetime tier on Linked.Codes is one upfront cost the agency absorbs once and bills against forever, instead of a per-client SaaS fee that erodes your retainer margin every month.

The encoding underneath is identical. The decoder doesn't know which version is "branded". Every uplift is downstream — in human attention, in trust at the URL preview, in the integrated experience that follows. None of it requires changing how the QR works. All of it requires a designer making three or four real decisions.

What the scan-rate data actually says#

The marketing literature loves the number "30% higher scan rate for branded QRs". You can find it on every QR vendor's landing page, usually traced back to Beaconstac's QR Trends report and a smaller study Scanova published a couple of years back. The number is real in the sense that someone measured it, and not totally fake in the sense that the methodology was sound. But it's also lazy, because the actual mechanism is more interesting than the headline.

Branded QRs don't win because of colour. They win because of context. The codes that score better are almost always the ones that have a frame, a call-to-action above the modules ("Scan to enter"), a recognisable brand sitting next to them, and a custom short URL underneath. The colour change matters less than the package. A black-and-white QR inside a well-designed frame with a clear CTA usually beats a coloured QR floating in the corner of an ad with no context at all.

The branded QR doesn't win because the code is prettier. It wins because the whole package signals that someone designed it on purpose. The colour is just the cheapest part of that signal.

That's the version of the claim that survives scrutiny. If you tell a client "branded QRs get 30% more scans", you've sold them a number that depends on placement, on print size, on the surrounding asset, and on whether the destination is any good. Sell them the package instead. The number follows.

What "branded" actually means in practice#

Four design decisions move the needle. None of them are technically hard. Most agencies do one and call it branded.

Module colour. The QR's dark modules can be any brand colour as long as the contrast ratio stays above roughly 4:1 against the background. Anything mid-saturation works: navy, deep red, the client's primary, the client's accent. Light colours fail — pastel yellow on white, mid-grey on white, anything below the contrast threshold won't survive a phone camera in mediocre lighting. Test the contrast in your generator before exporting. Better yet, check the scanability score on the asset at print-size before the file leaves your machine.

Centre logo. A logo in the middle of the QR is the single biggest brand signal. The risk is that you block too much of the encoded data and break scanning. The fix is mechanical: render the QR at error-correction level H (30% redundancy), keep the logo to under 25% of the total area, and leave a small white "clear-space" ring around the mark so the decoder doesn't confuse logo strokes with modules. Walk through error-correction levels for the full table, and logo placement in QR codes — how big can it actually be for the off-centre placement trick that buys a few extra percentage points of safe coverage.

Frame and call-to-action. A box around the QR with a short instruction — "Scan to reserve", "Scan for menu", "Scan to RSVP" — adds the affordance the QR doesn't have on its own. People know what to do with a hyperlink. They don't always know what to do with a square. The frame solves that, and adds the brand voice in the process.

Custom subdomain on the short link. The URL that previews above the scan, before the browser opens, is the trust signal most generators ignore. If your QR resolves through lnks.work/xY12, the preview reads as a random shortener. If it resolves through qr.client.com/spring, it reads as the client. The walkthrough is in setting up a custom short-link domain, the impact is covered in why your domain beats bit.ly, and the platform side is in the custom-domain docs.

Those four. Get those four right and the result reads as designed. Skip any of them and a client with a sharp eye will spot what's missing.

The static-versus-dynamic decision that ruins campaigns#

Every QR is either static or dynamic. A static QR has the destination URL baked directly into the modules — when the printer presses it onto 10,000 flyers, the destination is locked forever. A dynamic QR encodes a short URL the platform owns, and the platform redirects that short URL to whatever destination you set today, tomorrow, and a year from now.

For agency work, the answer is dynamic. Always dynamic. The reasons are operational, not aesthetic.

You will get the destination URL wrong. Maybe not on the first campaign, but eventually. A typo in a landing page slug, a marketing manager who changes the page after the print run starts, a destination domain that gets retired during a rebrand. With a static QR, that's 10,000 useless flyers and a furious client. With a dynamic QR, you log in, change the destination, and the existing print run keeps working.

You will run sequels. The poster from this season's promo doesn't get thrown away — it gets repurposed for the next campaign. A static QR is dead at the end of the campaign. A dynamic QR is reusable inventory.

You will want analytics. Static QRs are invisible to you after print. Dynamic ones produce per-scan logs with location, device, referrer, time-of-day. That data is the deliverable that justifies the next retainer.

The only place a static QR makes sense is on something you'll never reuse and never need to track — disposable event signage, a single-use ticket, a temporary table card. Even there, the marginal cost of going dynamic is zero. Default to dynamic. The full breakdown is in the static-versus-dynamic primer and the every-type-dynamic case.

Pricing branded QRs as an agency deliverable#

The most common mistake is folding the QR into the design package as if it were a small graphic element. A branded QR with a custom subdomain, error-correction at H, a logo overlay, and a hosted dashboard isn't a small graphic element. It's a piece of campaign infrastructure that you'll be operating for the client for the next twelve months. Price it that way.

Three patterns work, and you can stack them.

Per-QR line item. Charge a flat fee for each branded QR variant. Reasonable range for an agency-quality output: $150 to $500 per QR, depending on complexity. A single QR with the client's colour, logo and frame is at the low end. A set of five regionally targeted variants with per-region analytics — the same per-rep, per-day split that runs QR codes for tradeshow booths — is at the high end.

Campaign bundle. For a multi-asset campaign — flyer plus poster plus social plus billboard with the same QR or co-ordinated variants — bundle the QRs into a campaign package. Reasonable range: $1,500 to $5,000 for the campaign component covering design, hosting, analytics setup, and the first month of management. The package signals you're not selling pixels — you're selling the infrastructure behind the campaign.

Ongoing management retainer. This is the recurring revenue most agencies leave on the table. After the campaign launches, the client benefits from someone who'll re-point QRs if a destination changes, refresh designs seasonally, send monthly scan reports, and flag underperforming placements. Reasonable range: $99 to $299 per month per active campaign, depending on volume and reporting depth. Charge it. The work is real, the value is obvious to the client, and it locks in the platform relationship.

The honest version of these numbers is that the floor depends on your local market and the ceiling depends on how much value the client believes you're providing. The agencies that run dynamic QRs through their own dashboard, present white-label analytics under their own brand, and bundle the work into the campaign retainer charge multiples of the agencies who treat the QR as a free deliverable. The cost of the platform underneath is roughly the same. The story you can tell the client is not.

The agency workflow that scales past two clients#

The first branded QR is a craft project. The tenth is a process. The hundredth is software, or you've got a real problem.

Most agencies that scale this work follow the same pattern. One parent platform account. Per-client folders or sub-accounts that hold templates pre-configured with the client's accent colour, logo, frame text and short-link domain. Each new QR for that client starts from the template and inherits the brand automatically. You're not redesigning the QR — you're picking a destination and a placement.

The destination side splits cleanly by client category. B2B clients — SaaS, professional services, recruiting firms — almost always want the scan landing on a company page, a hiring post, or a newsletter on LinkedIn; the LinkedIn QR generator covers Profile, Company, Post, and Newsletter modes and the Paste-URL escape hatch for anything that doesn't fit one of those buckets, which is the right starting template for the conference-badge / executive-handout work most B2B campaigns ship. The four-mode breakdown and the matching print placements (badges, business cards, step-and-repeats, sales-collateral PDFs) sit in the LinkedIn QR codes deep-dive — useful to forward to a client who keeps asking why their booth backdrop should not point at the CEO's personal profile. Clients with a video pillar — fitness studios, course creators, anyone running a content channel as their lead magnet — want the same template pointed at a YouTube destination; the YouTube QR generator handles Channel, Video, Playlist, and Short modes so a print campaign for "Scan to watch the studio tour" lands on the exact asset instead of the channel homepage.

Pre-flight testing happens at print size, not on a 1200-pixel preview in the editor. Print a draft of the asset, scan it from the distance the real viewer will, in light comparable to where it'll be placed. The two QRs that look identical at 1200px don't always behave identically when printed at 30mm on uncoated stock. Most scan failures in the wild come from skipping this step, not from a flaw in the encoding.

Handover comes in three flavours. Some clients want a read-only dashboard so they can see scan totals without breaking anything. Some want full access so their marketing team can re-point QRs without paging you. A few prefer you keep ownership entirely and bill the maintenance. The fee structure changes with each option, but the platform setup is the same. Spell it out in the proposal so nobody is surprised six months in.

When NOT to brand the QR#

There are cases where branding the QR is wasted effort. Disposable event signage that gets recycled at the end of the night. Internal tools that only the client's staff ever touch. Assets where the QR is microscopic compared to the surrounding artwork — billboard ads where the QR is one element among twenty, magazine ads where it sits in a tiny corner. In all of those, the branding gets lost in the chaos and the marginal cost of doing it right doesn't pay back.

Use the round-QR scan-rules and the error-correction levels to make the QR survive instead. Save the branding effort for the assets where someone will actually look at it long enough to register the colour. For agency clients in single-property categories — most obviously real estate brokerages, where every yard sign and listing flyer carries the brokerage brand — the brokerage-side framing in QR codes for real estate listings covers what changes when one branded domain has to cover dozens of agents and hundreds of listings at once. Fitness-franchise clients sit in the same shape — one parent brand, many studios, a per-location destination behind every scan — and the gym and fitness studio WiFi piece shows how the per-studio template runs once the network and welcome page are set up.

The FAQ#

Sourcesshow citations

• ISO/IEC 18004:2015 — QR Code bar code symbology specification. https://www.iso.org/standard/62021.html
• Wikipedia — QR code (Reed-Solomon error correction, module structure, finder patterns). https://en.wikipedia.org/wiki/QR_code
• Apple — About URL previews in iOS Camera and Safari (developer documentation). https://developer.apple.com/documentation/safariservices
• W3C — Contrast ratio guidance, WCAG 2.1 (relevant for QR foreground/background ratios). https://www.w3.org/TR/WCAG21/#contrast-minimum
• Statista — QR code usage and adoption statistics (industry context for scan growth). https://www.statista.com/topics/9963/qr-codes/
• Mozilla Developer Network — image/svg+xml rendering and accessibility. https://developer.mozilla.org/en-US/docs/Web/SVG