How to Calculate Your Impact on the Business as a Designer - B2B Website Version

As a designer, I have found myself asking this very question a million times. But today is the day I sit down and narrow it down — for myself and for whoever is reading this.

Designers today are drained. Overworked. Burnt out. And it's the result of a few things:

• An overwhelming number of tools and learning opportunities

• Unrealistic deadlines driven by AI (because yeah, AI can do everything in minutes — sarcasm, obviously)

• A lack of documentation of design work in business language

Today, I want to talk about that third point — a detailed rundown on what to document and how to document it, so you can make a case for yourself in front of stakeholders.

I'll be speaking specifically about visual design, because that's my area. But I'd love to collaborate with designers from other disciplines for a Part 2.

For this blog, I'll focus on the website redesign use case, since that's what I'm currently working on the most.

But First — Why Does Any of This Matter?

Before we get into the numbers, here's why having metrics in your back pocket is so important:

Design decisions are business decisions in disguise. Not all, but many choices a designer makes — the placement of a CTA, the length of a form, the number of steps in a checkout flow, the load time of a hero image — have measurable downstream effects on conversion rates, bounce rates, support costs, and revenue. A designer who doesn't know this makes those choices on aesthetic instinct alone. A designer who does makes them with full awareness of what's at stake.

It changes how you prioritise. When you understand that reducing form fields from 8 to 4 can lift conversion, you fight harder for that simplification in a stakeholder meeting. When you know that a 2-second improvement in page load time can recover thousands in monthly revenue, you push back on the request to add another autoplay video above the fold. Impact awareness gives you evidence where you previously only had opinion.

It earns you credibility with non-designers. Most designers struggle to communicate their value to CEOs, CFOs, and product managers because they speak the language of aesthetics — colour, spacing, typography. Business stakeholders speak the language of revenue, cost, and risk.

It protects the project from being cut. Redesigns get descoped, delayed, and cancelled — usually because the business case was never made clearly. A designer who built the impact model owns the most compelling reason to proceed. When budget conversations happen, they have numbers, not just mockups.

It makes you a better designer, not just a more political one. Understanding that a confusing navigation generates hundreds of support tickets a month doesn't just help you justify a redesign — it tells you where to focus. You stop spending equal time on everything and start allocating effort to the flows with the most business consequence.

It creates a feedback loop that improves your craft. When you track what happens after you ship — whether conversion went up, bounce rate dropped, or support tickets fell — you learn which design decisions actually worked. Designers who never measure are flying blind, repeating the same intuitions. Designers who measure develop calibrated judgment over time.

The Numbers That Matter

A B2B website has very different metrics from a B2C one. B2B isn't about volume — it's about the quality of visitors coming in and converting them into high-value customers.

Marketing Metrics

Metric	What It Means
Leads per month	Every visitor who takes a conversion action on your site. Raw volume before any quality filter. A high number only matters if MQL rate is also high.
Marketing Qualified Leads (MQL)	Leads that marketing has assessed as worth passing to sales — based on company size, role, industry, and intent signals.
Opportunities per month	After sales speaks to a lead, they qualify it as an opportunity if it's an active deal in the pipeline.
Deals closed per month	An opportunity becomes a closed deal when the contract is signed.
Customer Acquisition Cost (CAC)	Total sales and marketing spend divided by new customers acquired. Tells you how efficient your go-to-market engine is. A high CAC isn't automatically bad — it's only a problem if LTV doesn't cover it. Target: LTV:CAC of at least 3:1.
Customer Lifetime Value (LTV)	Total revenue expected from a customer before they cancel. Calculated from ACV and churn rate. A $24K ACV customer who stays 5 years is worth $120K — which is why reducing churn by even 2% has enormous compounding value.
LTV:CAC Ratio	How much value you get back for every dollar spent on acquisition. 3:1 is the baseline. Below that, growth starts destroying value. Above 5:1, you're likely under-investing in growth.
ARR (Annual Recurring Revenue)	The annualised value of recurring subscription contracts. The headline number that investors and boards watch — and it compounds every year unless customers churn.
Net Revenue Retention (NRR)	Whether your existing customer base is generating more or less revenue over time, without counting new customers. Above 100% means expansions outpace churn. The best B2B SaaS companies sit at 120–140% NRR — meaning they'd grow even if they stopped acquiring new customers entirely.

Soft Indicators

These are the internal signals that tell you how healthy your design process is — before problems become visible to users.

• Throughput — Volume of work getting done. The key ratio: new work vs. revision work. High revision work means something upstream is broken.
  

• Speed — How long each stage takes and where lag accumulates. The hidden killer: meeting time vs. focus time.
  

• Design system signals — The earliest indicators of long-term technical debt. Component detach rate is the most honest metric — it tells you whether designers actually trust the system enough to use it.
  

• Quality signals — Missing states, missing accessibility considerations, visual drift across pages. Invisible in the design file, very visible to users and engineers.
  

• Dev handoff signals — The friction point between design and engineering. The most revealing signal: how often engineers make design decisions silently in code without flagging it. When that starts happening, it means they've concluded the design process is too slow to wait for.

User Experience Indicators

These tell you what's actually happening when real users interact with your site.

Signal	What It Tells You
Click heatmaps	Density map of every click on a page
Scroll depth maps	How far down a page users actually read
Mouse movement / attention maps	Where users look and hover, not just click
User flow / navigation paths	Actual routes users take vs. expected routes
Funnel drop-off analysis	Where users exit multi-step flows
Rage click detection	Repeated rapid clicking — the clearest frustration signal
Form error frequency	Which fields trigger errors and where users abandon
Time on page vs. task complexity	Whether time on page signals engagement or confusion

Beyond the Figma File

If this blog did anything, I hope it sparked a little curiosity — a nudge to look beyond the artboard and see the fuller picture of what your work actually does in the world. As designers, it's easy to measure our output by what we deliver: the polished screens, the tight components, the handed-off specs. But the real impact of your decisions lives somewhere else entirely — in a conversion rate that climbed, a support queue that shrank, a customer who stayed. The Figma file is where the work lives. The metrics are where the work matters. And the sooner we start fluently moving between both worlds, the harder it becomes for anyone to underestimate what a designer brings to the table. You were never just making things look good. You were shaping how a business grows.