How the Designed Revenue Audit Was Built
The Moment It Clicked
I wasn't trying to build a tool.
I was trying to solve a content problem.
I had a new core belief: the smallest changes in design can lead to massive growth or massive savings. I had 15 years of case studies that proved it. I had a target audience of founders, C-suite executives, and managing partners who needed to hear it.
What I didn't have was a content system that could carry that belief consistently across a year of publishing.
So I started mapping content pillars. The obvious move was to anchor the system around the Flynn Score, my existing performance framework for evaluating designer output. It's weighted, it's structured, it produces a number. It made sense on paper.
Except it didn't work.
The Flynn Score is a management tool. It was built for creative directors and design operations leads. The people running teams and needing a defensible way to measure individual designer performance. That's a real audience with a real problem. But it wasn't the audience I was writing for now.
I was writing for the person who doesn't manage designers. The person who commissions design, funds design, and is ultimately accountable for whether design produces a return. The founder who approved the rebrand budget. The CFO who signed off on the agency retainer. The managing partner who needs to explain to the board why creative spend is justified.
The Flynn Score had nothing to say to them.
And that's when the question surfaced that changed everything.
If the Flynn Score measures designer performance, what measures design's revenue performance?
The Gap Nobody Had Named
I went looking for an existing framework. Something I could adapt, reference, or build on.
I didn't find one.
There are design maturity models. Brand audit frameworks. UX heuristic checklists. Creative operations benchmarks. All of them useful. None of them asking the revenue question directly.
The closest things were conversion rate optimisation frameworks, but those only cover digital performance. They don't touch sales enablement, finance, or operations. They assume the rest of the design function is someone else's problem.
It isn't. It's all connected. And nobody had mapped the connection in a way that produced a number a CFO could act on.
That absence was the opportunity.
I wasn't identifying a gap in the market. I was identifying a gap in the conversation. Designers talk about craft. Business leaders talk about return. Nobody was standing in the middle translating one into the other in a structured, repeatable way.
That translation was exactly what 15 years of engagements had been preparing me to do.
Building the Pillar Structure
The first structural decision was the most important one: what categories of design decision have a direct, demonstrable line to revenue?
I didn't start with categories. I started with outcomes.
I pulled every engagement where a design decision had produced a measurable financial result, positive or negative, and grouped them by the type of decision involved.
The SVG file size fix that produced a 35% sales increase for an e-commerce client. That was a digital performance decision with a revenue consequence that a standard speed audit had completely missed.
The meeting room scheduling wayfinding intervention at an enterprise property firm. Sub-$10,000 implementation cost. Measurable revenue lift through increased utilisation of billable space. That was an operations decision nobody had framed as a revenue opportunity.
The pitch deck that lost a deal not because the strategy was weak but because the document looked like it hadn't been touched since 2011. That was a sales enablement failure. The design was the signal before it was anything else.
The creative team running three different design subscription tools across two departments because nobody had audited the tooling stack. Duplicated spend. Invisible on the P&L. That was a finance failure.
Four categories emerged cleanly from the evidence. Not constructed theoretically. Observed from outcomes.
Sales Enablement. Finance. Digital Performance. Operations.
Assigning the Weights
Having the categories wasn't enough. A framework that treats all four categories as equal weight produces a score that misleads. A business with a perfect Operations score and a broken Sales Enablement function is not performing at 50%. It's losing deals.
The weights needed to reflect revenue impact potential, not categorical fairness.
I used the same logic I applied when building the Flynn Score. Weight toward what moves the needle most. The heavier weights create urgency in the pillars where intervention delivers the fastest and most measurable return.
Sales Enablement landed at 35%. Design's most direct revenue function is enabling the sales process. Every touchpoint a prospect encounters before they buy is a design decision. The consequence of getting it wrong is a lost deal. That's the highest stakes category.
Finance landed at 30%. Design inefficiency has a direct cost that most finance teams never see itemised. Rework cycles. Format conversion spend. Duplicated tooling. Assets recreated from scratch because there's no retrieval system. This is invisible budget. Significant in aggregate. Recoverable with relatively low intervention cost.
Digital Performance landed at 20%. The revenue consequence is real but the connection is less immediately visible to non-technical stakeholders. The SVG story is the proof case. The fix was simple. The impact was significant. But it took someone looking specifically for that category of problem to find it.
Operations landed at 15%. Genuine financial impact through pipeline efficiency, revision cycle length, and briefing quality. Harder to attribute directly to a revenue line in a single quarter, which is why it carries the lowest weight despite being the category with the most day-to-day design activity.
Total: 100%. Every pillar earns its weight. None of them are there for completeness.
Writing the 24 Conditions
Six conditions per pillar. The number wasn't arbitrary.
Five felt thin. It produced scores that were too coarse to be useful. Seven started to feel like a checklist that needed a design background to complete. Six conditions per pillar, 24 total, gave enough resolution to identify where specifically the problem was sitting without requiring the person completing the audit to be a designer.
That constraint mattered enormously. The audit was built for founders and executives. If completing it required design knowledge, it would fail its primary audience before it produced a single result.
Every condition had to meet three criteria.
It had to be observable. Not a rating. Not a matter of opinion. A yes or no question answerable against real evidence.
It had to be answerable without a design background. The language had to be business language. "Do your sales materials visually reflect the quality of the product or service you're selling" is a question a founder can answer. "Is your type hierarchy consistent across collateral" is not.
It had to have a real consequence. Every condition on the final list has a corresponding example from a real engagement where that condition was failing and revenue was affected. Not theoretical. Documented.
Writing the conditions took longer than building the pillar structure. A condition that sounds right but can be argued both ways undermines trust in the output. If the answer depends on who's completing the audit, the condition isn't doing its job.
Several early drafts were cut for exactly this reason. Replaced with conditions that produced consistent answers regardless of the respondent.
The Scoring Model
The output needed to be a number. Not a category. Not a colour. A number a CFO could take into a budget conversation.
The audit produces two outputs.
A percentage score reflecting how many of the 24 conditions are currently working in the business's favour, weighted by pillar. This is the diagnostic number. It shows where the gaps are and how significant they are relative to each other.
A revenue opportunity figure. A calculated estimate of the revenue impact available if the failing conditions were resolved. Conservative by design. The methodology uses observed outcome ranges from real engagements, not theoretical maximums. The number is meant to be credible in a boardroom, not impressive in a marketing document.
The distinction matters. A design audit that outputs a revenue figure needs to survive scrutiny from a CFO. Inflated estimates undermine the tool and the positioning. The number has to be one a finance team can pressure-test and not immediately dismiss.
What the Build Taught Me
Building the audit clarified something I had known practically for 15 years but hadn't articulated cleanly.
The reason design's revenue contribution is invisible in most businesses isn't that the contribution doesn't exist. It's that nobody built the instrument to measure it.
Craft audits measure craft. Performance reviews measure individuals. P&L statements measure outcomes several steps removed from the design decisions that influenced them. None of these instruments were designed to answer the revenue question.
The Designed Revenue Audit isn't an argument for the value of design. It doesn't need to make that case. It measures what's already there.
The SVG fix happened before the audit existed. The JLL intervention happened before the audit existed. The revenue was always a consequence of those design decisions. What didn't exist was a systematic way to find those decisions before their absence became a problem, and before the revenue consequence compounded to the point where it showed up on a P&L as something else entirely.
That's what the audit does. It finds the design decisions that are quietly costing or quietly earning, before they're invisible in a line item nobody connects to a creative brief.
The Framework Is Live
The Designed Revenue Audit is free at flynnfrancisco.com/designed-revenue-audit
24 conditions. Four weighted pillars. One revenue opportunity number.
It takes less time to complete than most businesses spend on a single revision cycle.
Your next revenue increase is by design.