The New Agency Pitch Deck: Proving UX ROI with Performance Budgets (Not Pretty Mockups) | Blanche

A beautiful homepage doesn’t fail because it’s ugly—it fails because it’s slow, inaccessible, and hard to use.

And clients are catching on.

In 2026, the best agency pitch decks don’t start with “our design system.” They start with a scorecard: what will improve, how it will be measured, and what the business gets in return.

The new competitive advantage isn’t taste. It’s proof—and a plan to deliver it.

This article lays out a pragmatic, outcomes-first pitch framework: UX + performance + accessibility, anchored by a performance budget and a repeatable before/after measurement model you can productize.

Why the Pitch Is Changing (and Why Clients Are Smarter Now)

A decade ago, a slick prototype could close a deal. Today, decision-makers have been burned by:

Replatforms that shipped late and didn’t move revenue
“Modern” sites that tanked SEO due to JavaScript bloat
Accessibility complaints that became legal headaches
Brand refreshes that looked great but didn’t improve conversion

Meanwhile, the market got more transparent. Clients can now:

Pull Core Web Vitals from PageSpeed Insights or CrUX
Audit accessibility with Lighthouse, axe, or WAVE
Track funnel performance in GA4, Mixpanel, Amplitude, or HubSpot
Compare competitors instantly

So the pitch has to evolve from “we’ll redesign your site” to:

Here’s the baseline.
Here’s what we’ll change and why.
Here’s how we’ll measure impact.
Here’s the budget (performance + scope) that keeps us honest.

Concrete takeaway

Build your pitch around measurable deltas, not deliverables. Deliverables are inputs. Clients buy outputs.

The Outcomes-First Scorecard: UX, Performance, Accessibility

A modern pitch needs a single page that aligns creative, engineering, and growth. Call it the Outcomes-First Scorecard.

1) UX outcomes (what users can do faster/easier)

UX is only “subjective” when you don’t define success.

Tie UX decisions to metrics that growth teams already report:

CVR (conversion rate): reduce friction in key flows (signup, checkout, lead form)
AOV (average order value): improve merchandising, bundling, trust signals
Retention: reduce time-to-value, improve onboarding clarity
Support deflection: clearer IA, better self-serve content

Practical UX KPIs to include:

Funnel step completion rate (e.g., PDP → cart → checkout)
Form completion rate and error rate
Task success rate (from moderated tests)
Time on task (for key journeys)

UX ROI becomes obvious when you stop measuring “engagement” and start measuring completed intent.

2) Performance outcomes (what loads faster and responds instantly)

Performance is not a developer preference. It’s a conversion lever and an acquisition lever.

Performance connects to business metrics like:

CVR: faster pages reduce drop-off, especially on mobile
CAC: better SEO and lower paid bounce waste
Retention: perceived quality increases trust and repeat usage

Use the language clients already understand:

“We’ll reduce bounce by improving load speed on top landing pages.”
“We’ll protect paid spend by ensuring campaign pages hit performance targets.”

3) Accessibility outcomes (what becomes usable—and less risky)

Accessibility is where many agencies still under-sell.

Position it as:

Market expansion: more users can complete tasks (including aging users, temporary impairments, low-vision, motor limitations)
Brand trust: inclusive experiences signal quality
Legal risk reduction: fewer demand letters and compliance fire drills

Accessibility also improves UX for everyone:

Better focus states help keyboard users and power users
Clearer labels reduce form errors
Proper headings improve scanning and SEO

Concrete takeaway

Your scorecard should fit on one slide and include:

3–5 business KPIs (CVR, CAC efficiency, retention, leads)
3–5 experience KPIs (CWV, a11y score, task success)
A measurement plan and timeframe

Building a Performance Budget into Discovery and Design

A performance budget is the missing piece that turns “we care about speed” into “we will ship fast.” It’s also a powerful pitching tool because it creates constraints—like any good creative brief.

What a practical performance budget includes

You’re not budgeting “speed.” You’re budgeting the components that create speed.

Include targets for:

Core Web Vitals (field-oriented targets)
- LCP (Largest Contentful Paint): target ≤ 2.5s on mobile (field)
- INP (Interaction to Next Paint): target ≤ 200ms
- CLS (Cumulative Layout Shift): target ≤ 0.1
Page weight and JavaScript constraints (lab-oriented guardrails)
- Total JS payload (e.g., ≤ 170KB gz on key landing pages)
- Total page weight (e.g., ≤ 1.0–1.5MB on mobile for top pages)
- Third-party script budget (e.g., max 2 marketing tags at launch; others phased)
Fonts and imagery
- Font families: 1–2 max; variable fonts preferred
- Font loading strategy: font-display: swap; preload only what’s critical
- Images: AVIF/WebP, responsive sizing, explicit dimensions to prevent CLS
Rendering strategy and framework constraints
- SSR/SSG where it matters (content and landing pages)
- Limit client-side hydration; ship less JS by default
- Component-level performance acceptance criteria

Tools to reference (to build credibility):

PageSpeed Insights + CrUX for field data
Lighthouse and WebPageTest for lab diagnostics
RUM via Vercel Analytics, SpeedCurve, Datadog RUM, or New Relic
Bundle analysis (Next.js bundle analyzer, source-map-explorer)

Where the budget lives in your process

Performance budgets fail when they’re introduced after design.

Bake them into:

Discovery: define targets per template type (homepage, PDP, blog, checkout)
Design: performance-aware patterns (no giant carousels, avoid heavy video backgrounds by default)
Build: CI checks for Lighthouse thresholds, bundle size, and regressions
Launch: RUM dashboards, alerting, and a 30-day tuning window

How to talk about tradeoffs without sounding defensive

Clients fear constraints because they think it means “less creative.” Reframe it as “more intentional.”

Examples of persuasive tradeoff language:

“We can do the cinematic hero, but we’ll implement it as progressive enhancement so the page still hits LCP.”
“We’ll prioritize motion where it supports comprehension—not as decoration that costs performance.”
“We’ll phase in third-party tools after we establish a baseline, so we don’t mask regressions.”

Concrete takeaway

Add a slide titled Performance Budget with:

CWV targets (LCP/INP/CLS)
JS/page-weight/font constraints
How you’ll enforce it (CI + RUM)
The tradeoff policy (what gets cut first when budget is threatened)

Accessibility as a Competitive Differentiator (and Legal Risk Reducer)

Most pitches treat accessibility as a checklist item. That’s a missed opportunity.

How to position accessibility in a pitch

Anchor it in outcomes the buyer cares about:

More completed conversions: fewer users blocked by forms, modals, navigation
Lower churn: better readability, clearer interactions
Faster QA cycles: consistent components reduce regressions
Reduced legal exposure: documented practices and remediation plan

What to include in a practical accessibility scope

Keep it concrete and testable:

WCAG 2.2 AA target (or a defined subset if the client needs a phased approach)
Component library with accessible defaults:
- Buttons, inputs, selects
- Modals and drawers
- Navigation menus
- Toasts/alerts
Testing plan:
- Automated checks (axe, Lighthouse)
- Manual keyboard testing
- Screen reader spot checks (NVDA/JAWS/VoiceOver)

The pitch-winning move: show how accessibility becomes a design system advantage, not a one-time audit.

Concrete takeaway

Offer accessibility in three tiers:

Baseline: audits + quick wins on top templates
Systemic: accessible component library + governance
Operational: ongoing monitoring + regression prevention

Case Study Template: Baseline → Changes → Business Impact

If you want clients to buy outcomes, you need a repeatable way to show outcomes.

Here’s a case study template you can reuse across industries—even when you can’t disclose exact revenue.

1) Baseline (what’s true today)

Collect evidence from:

CrUX/CWV snapshots for top pages
Analytics funnel drop-off
Qualitative UX findings (5–8 user interviews or session replays)
Accessibility audit summary

Baseline slide format:

Performance: LCP/INP/CLS + top offenders (images, JS, third-party)
UX: top 3 friction points in the funnel
Accessibility: top 3 blockers (labels, focus management, contrast)

2) Changes (what you actually did)

Make changes legible and attributable:

“Replaced carousel with a single prioritized value prop + supporting modules”
“Moved personalization logic server-side; reduced client JS by 40%”
“Standardized form fields with clear error states and labels”
“Implemented image CDN and responsive sizing; preloaded LCP image”

Also include what you didn’t do:

“Deferred chat widget until after user intent signal”
“Removed redundant tag manager scripts”

3) Business impact (what moved)

Tie improvements to metrics with a believable timeframe:

Conversion: uplift on key landing pages or funnel steps
Acquisition: organic traffic improvements, reduced paid bounce
Efficiency: lower support tickets, fewer QA cycles, faster content publishing

If you can’t share exact numbers, use ranges or indexed results:

“Checkout completion improved 8–12%”
“LCP reduced from 3.8s → 2.2s on mobile”
“Form completion increased from index 100 → 118”

Measurement integrity: avoid the “agency math” trap

Clients are skeptical of attribution—and they should be.

Use a lightweight but credible approach:

Pre/post comparisons with seasonality notes
Template-level metrics (not just site-wide averages)
A/B tests where feasible (even simple split tests on landing pages)
RUM monitoring to confirm field improvements

Concrete takeaway

Turn this into a one-page PDF you attach to every proposal:

Baseline snapshot
Target scorecard
Measurement plan (30/60/90 days)

How to Scope Deliverables Around Outcomes (Without Overpromising)

Outcomes-first pitching can backfire if you promise metrics you don’t control.

The trick is to commit to targets and practices, not guaranteed revenue.

What you can safely commit to

Commit to:

Performance budgets and enforcement
Accessibility conformance targets and testing
Instrumentation and measurement setup
UX improvements tied to known friction points
A defined optimization window post-launch

Avoid guaranteeing:

“We will increase revenue by 30%”
“We will rank #1 on Google”

Instead say:

“We will ship within a performance budget designed to improve CWV and reduce speed-related drop-off.”
“We will implement and validate WCAG 2.2 AA across agreed templates and components.”
“We will set up analytics events to measure funnel impact and iterate for 30 days post-launch.”

Use “outcome-based scope” language

Structure scope around:

Templates that matter (highest traffic, highest intent)
Critical user journeys (signup, checkout, lead)
System upgrades (design system, CMS model, component library)

This prevents the classic failure mode: spending 60% of the budget on low-impact pages.

Concrete takeaway

Add a “Scope Boundaries” slide:

Included templates and journeys
Excluded items (or phase 2)
Assumptions (traffic levels, content readiness, stakeholder availability)

How to Package This as an Agency Offer (and Price It)

If you want this approach to scale, productize it into offers with clear artifacts.

Offer 1: The Outcomes-First Audit (2–3 weeks)

Best for: new relationships, skeptical stakeholders, pre-redesign clarity.

Deliverables:

Baseline scorecard (CWV, a11y, funnel)
Performance budget proposal (by template)
Accessibility remediation plan (prioritized)
Measurement plan + dashboard spec
Quick-win backlog (effort vs impact)

Pricing model:

Fixed fee (fast procurement), typically positioned as a credit toward build.

Offer 2: Performance-Budgeted Redesign (8–16 weeks)

Best for: teams ready to ship.

Deliverables:

Outcome-based scope (templates + journeys)
Component library with accessibility baked in
Performance budget enforced in CI
RUM monitoring + post-launch tuning window

Pricing model:

Project fee with milestone payments
Optional performance/a11y maintenance retainer

Offer 3: Continuous Optimization Retainer (monthly)

Best for: growth teams that iterate.

Deliverables:

Monthly CWV + a11y reporting
Experiment roadmap (UX + performance)
Regression prevention (budgets, monitoring)
Quarterly accessibility reviews

Pricing model:

Retainer tied to throughput (e.g., 2–4 experiments/month) and monitoring stack

Agencies that win long-term aren’t “done” at launch. They sell operational excellence.

Concrete takeaway

In your pitch deck, include a pricing slide that maps investment to outcomes:

What you’ll improve (scorecard)
How you’ll enforce it (budget + governance)
When results can be measured (30/60/90)

Conclusion: Sell the Budget, Sell the Proof, Sell the Plan

The era of pitching “pretty” is over—not because aesthetics don’t matter, but because aesthetics alone don’t survive scrutiny.

The agencies that will dominate the next wave are the ones that can say:

Here’s your baseline.
Here are the constraints that protect the outcome (performance budgets + accessibility standards).
Here’s the measurement framework we’ll run before and after.
Here’s what we’ll ship first to move the metrics that matter.

If you want your next pitch to land with CEOs, CMOs, and product leaders, rebuild your deck around an Outcomes-First Scorecard—and treat performance and accessibility as first-class creative constraints.

Call to action

If you’re an agency owner or creative director, audit your last three proposals:

Did you include a baseline?
Did you define a performance budget?
Did you specify accessibility conformance and testing?
Did you outline a 30/60/90 measurement plan?

If the answer is “no,” your next pitch is an opportunity to stop selling vibes—and start selling results.