DEV Community: Michael Pilgram

Selling Outcomes, Not Services: A Guide for UK Agencies

Michael Pilgram — Wed, 29 Oct 2025 10:22:47 +0000

There's a pattern I keep seeing in web development: agencies compete on price, clients choose the cheapest option, and six months later everyone's disappointed. The client got a functioning website but their business hasn't improved. The agency delivered exactly what was spec'd but the client still has problems.

The disconnect isn't about quality of execution. It's about what's being sold.

Most agencies sell services: "We'll build you a responsive website with modern design and good performance." The client buys it, gets exactly that, and wonders why their conversion rate is still terrible.

They bought a service. What they actually needed was an outcome: more customers, better conversion, business growth.

Clients don't care what you do. They care what they achieve.

Author's Note: I've spent over fifteen years building websites and running Numen Technology, a UK web development company. The insights in this article come from working with dozens of agencies, freelancers, and in-house teams who've made this transition from service-based to outcome-focused selling—and the measurable results they've achieved.

The Fundamental Misalignment

Most web agencies and freelancers sell the same way: "We build responsive websites using modern frameworks. We follow best practices for accessibility and performance. We deliver on time and on budget."

All true. All important. Completely missing the point.

Clients don't wake up thinking "I need a Next.js website with excellent Lighthouse scores." They wake up thinking "I need more customers," or "I'm losing business to competitors," or "My site is costing me sales and I don't know why."

The service you provide (website, audit, consulting) is the mechanism. The outcome they achieve (growth, competitive advantage, risk reduction) is what they're actually buying.

This distinction isn't semantic. It fundamentally changes how you position yourself, price your work, and build client relationships.

Key Takeaways

What you'll learn in this guide:

Why clients pay premium rates for outcomes over services (research shows 3-5x higher fees)
The difference between outputs (what you deliver) and outcomes (what clients achieve)
A practical 5-step framework for implementing outcome-based selling
How to price based on value rather than time
Real examples of repositioning services as measurable business outcomes

Reading time: 12 minutes | Implementation difficulty: Medium | Potential impact: High (pricing power, client retention, sustainable differentiation)

Outputs vs Outcomes: What's the Difference?

An output is what you deliver. An outcome is what your client achieves.

Output thinking:

"We'll build a responsive website with modern design"
"We'll audit your site and provide a comprehensive report"
"We provide ongoing technical support"

Outcome thinking:

"We'll build a site that converts 25% better through optimised UX and performance—tracked against your current baseline"
"We'll identify which performance and accessibility issues are costing you conversions, with prioritised fixes that deliver measurable business impact"
"We'll maintain 99.9% uptime for customer-facing systems and patch security vulnerabilities within 24 hours—protecting your reputation and revenue"

Notice the shift? Same services, completely different value proposition. The outcome version connects directly to what clients actually care about: revenue, customers, growth, trust.

UK IT consultancy MDB Service Consulting puts it bluntly: "Great IT organisations are designing services to deliver business value focused outcomes. Mediocre IT organisations are stuck on making IT services available based on outputs."

Which one are you?

Why This Matters Now

The market is shifting beneath our feet. Research from 2024 shows 67% of organisations now prioritise business outcomes over cost savings in outsourcing decisions. They're not shopping for the cheapest provider—they're evaluating who delivers measurable results.

Additionally, 87% of business buyers expect sales reps to act as trusted advisors, not vendors, according to Salesforce's State of Sales research. The relationship has changed. Clients want partners who understand their business and drive outcomes, not order-takers who deliver specifications.

For UK web agencies and freelancers, this creates both threat and opportunity. The threat: if you're selling generic services based on features and hourly rates, you're competing on price in a race to the bottom. The opportunity: if you reposition around outcomes, you differentiate based on value and escape the time-for-money trap.

The "People Buy People" Principle

There's an old sales maxim: people buy from people they know, like, and trust. It sounds trite, but the psychology is sound—especially for outcome-focused work.

Here's why trust matters more than likeability: a buyer will pay a premium to someone they trust over someone they merely like. And outcome-based selling requires trust in a way that service-based selling doesn't.

When you're selling services, the evaluation is straightforward: Can you build a website? Do you have relevant experience? What's your hourly rate? The client can verify your capability through portfolio, references, and technical assessment.

When you're selling outcomes, you're asking clients to believe you'll deliver business results. That requires a different kind of confidence. They need to trust that:

You understand their business context
You'll identify the right problems to solve
You'll deliver measurable impact, not just completed tasks
You'll stay accountable beyond initial delivery

This trust isn't built through likeability—it's built through demonstrated expertise, honest communication, and genuine investment in their success.

Every conversation builds what sales psychology calls "value points"—incremental trust that translates directly to pricing power. When you've proven you deliver outcomes, clients pay premium rates because they're not buying your time; they're buying certainty of results.

The Pricing Model Connection

Outcome-focused selling naturally connects to how you price work. Traditional time-and-materials (T&M) billing creates misaligned incentives: you're rewarded for taking longer; the client wants speed and results.

Time & materials model:

Client pays for hours spent
Flexible when scope is uncertain
Risk of budget overruns
Your incentive: maximise billable hours
Client incentive: minimise time spent

Outcome-based model:

Client pays for results achieved
Requires clear success metrics
Risk shifts to you (must deliver despite challenges)
Your incentive: work efficiently and innovatively
Client incentive: ensure outcomes are measurable and achieved

The outcome-based model aligns both parties toward the same goal. You're motivated to deliver results quickly and effectively because that's how you demonstrate value. The client gets predictable costs tied to business impact.

This doesn't mean abandoning hourly billing entirely. Some work genuinely suits T&M—exploratory projects, uncertain scope, maintenance contracts. But wherever possible, pricing based on outcomes creates better relationships and higher margins.

Practical Framework: How to Sell Outcomes

Based on research from HubSpot and Salesforce, here's how to implement outcome-based selling:

1. Do Your Homework

Before engaging a prospect, research thoroughly:

Their industry, competitors, and market position
Their current web presence and obvious issues
Their business model and revenue drivers
Recent news, growth indicators, strategic priorities

Research finding: 90% of prospects research your company before engaging you. They expect equivalent effort from you.

Don't walk into discovery calls blind. If you're pitching an e-commerce business, understand their conversion funnel. If it's a service business, understand their lead generation challenges. Demonstrate you've invested time in understanding their context.

2. Ask Better Questions

Move beyond "what's broken?" to "what does success look like?"

Weak questions:

"Is your website slow?"
"Do you have accessibility issues?"
"When was your site last redesigned?"

Better questions:

"What's preventing you from converting visitors into customers?"
"What competitive advantages are you trying to communicate that your current site doesn't convey?"
"If we could change one thing about your web presence that would meaningfully impact your business, what would it be?"

The second set reveals outcomes—conversion growth, competitive positioning, business impact—rather than just symptoms.

One executive quoted in the research recommends using SWOT analysis: understand their strengths, weaknesses, opportunities, and threats. Position your work as exploiting opportunities or mitigating threats, not just fixing technical issues.

3. Frame Solutions Around Outcomes

Connect your services directly to business results with transparency about what you control.

Traditional pitch:
"We'll rebuild your site using Next.js with comprehensive accessibility testing and performance optimisation."

Outcome-focused pitch:
"We'll build a site that converts 30% better through optimised user experience, reaches 15% more potential customers through WCAG 2.2 compliance, and positions you for AI search traffic growth—tracked against baseline metrics. We'll provide monthly reporting showing exactly how the site impacts your business."

Notice what changed:

Specific, measurable business results (30% conversion improvement)
Timeframe for measurement (monthly reporting)
Direct connection to what client cares about (customers, revenue, growth)
Transparency about tracking and accountability

4. Back Claims with Evidence

Don't make promises you can't substantiate. When you have real results, document them with precision.

Vague approach:
"We've helped lots of clients improve their site performance."

Evidence-backed approach:
"Reduced LCP from 4.1s to 2.3s, cut bundle size from 287KB to 134KB, conversion rate improved 18% within 90 days—tracked through analytics before and after."

The difference is specificity. Concrete numbers, measurable timeframes, business impact. If you've delivered outcomes, prove it with data. If you haven't tracked outcomes yet, start now—your next project is your first case study.

Specificity builds trust. Vague claims destroy it.

5. Maintain Ongoing Partnership

Outcome-based work doesn't end at launch. You must:

Stay connected during implementation
Monitor progress against agreed metrics
Communicate results transparently
Adjust approach if variables change
Own the relationship beyond initial delivery

This positions you as trusted advisor invested in long-term success, not vendor focused on project completion.

Real-World Application for Web Agencies

How this specifically applies to common agency work:

Website Builds

Output approach: "We'll build a responsive site with modern design, fast performance, and accessibility compliance."

Outcome approach: "We'll build a site that converts 25% better by optimising the user journey for your specific customer personas, loads in under 2 seconds on mobile to reduce bounce rate, and reaches your full addressable market through WCAG 2.2 compliance—with conversion tracking proving impact against your current 2.3% baseline."

Site Audits

Output approach: "We'll audit your site across performance, accessibility, SEO, and security, providing a comprehensive report."

Outcome approach: "We'll identify exactly which issues are costing you customers and revenue—prioritised by business impact—with specific fixes that improve conversion rate, search visibility, and customer trust. You'll know precisely where to invest for maximum ROI."

Ongoing Support

Output approach: "We provide technical maintenance, security updates, and support tickets."

Outcome approach: "We'll protect your revenue by maintaining 99.9% uptime, respond to critical issues within 2 hours, and proactively identify problems before they impact customers—with monthly reporting on incidents prevented and business continuity maintained."

The pattern: every outcome version includes measurable business results, specific metrics, and direct connection to what the client values.

The Challenges (And Why They're Worth It)

Outcome-based selling isn't easier than service-based selling. It requires more upfront work, deeper client understanding, and ongoing accountability. Here are the honest challenges:

Extended sales cycles: Higher stakes mean more stakeholders and longer decisions. Accept this. Rushing undermines the trust required.

Measurement requirements: You need baseline data, tracking systems, and agreed metrics. If clients can't or won't measure properly, outcome-based pricing fails.

Uncontrollable variables: Market shifts, client internal decisions, and economic changes can derail outcomes despite excellent work. Clearly define what you control versus what requires client action.

Higher expectations: You're promising results. Clients hold you accountable. Contract disputes increase if outcomes aren't achieved or measurement wasn't defined clearly.

Defining success: Different businesses define success differently. Alignment requires extensive discovery and clear communication.

But here's why it's worth the effort:

Higher margins: When you price based on value delivered rather than hours spent, profitability increases substantially. Research shows consultants implementing value-based pricing often charge 3-5x more than hourly equivalents.

Better client relationships: Deep understanding of client businesses builds trust and positions you as strategic partner, not replaceable vendor.

Sustainable differentiation: Generic services get commoditised. Outcome delivery based on business expertise remains differentiated.

More satisfying work: Solving real business problems is more engaging than simply executing specifications.

What This Means for Your Practice

Three immediate changes you can implement:

1. Reframe Your Positioning

Audit your website, proposals, and pitch decks. Wherever you're leading with services or technologies, reframe around outcomes.

Before: "We build fast, accessible websites using modern frameworks"

After: "We help businesses convert more visitors into customers through sites that load instantly, work for everyone, and communicate value clearly"

Same capability, completely different value proposition.

2. Change Your Discovery Process

Stop treating discovery as requirements gathering. Treat it as business strategy consulting.

Understand:

Strategic business goals (not just website requirements)
How they measure success (revenue, customers, market share)
What's preventing achievement of goals
How your work directly contributes to those measures

Only then propose solutions—framed explicitly around outcomes.

3. Restructure Your Pricing (Where Possible)

Not every project suits outcome-based pricing. Maintenance contracts, exploratory work, and uncertain scope often work better with T&M.

But for website builds, redesigns, optimisation projects, and other defined work, experiment with value-based pricing:

Define success metrics with client (conversion rate, load time, accessibility score, search rankings)
Set baseline measurements
Propose pricing tied to achievement of specific improvements
Build in measurement and reporting

You'll lose some price-sensitive prospects. That's fine—they weren't your ideal clients anyway. The clients who engage based on outcomes pay better, trust more, and build longer-term relationships.

The Uncomfortable Truth

Most agencies resist outcome-based selling because it's harder. It requires:

Deeper business understanding than pure technical execution
Accountability beyond "we delivered what you spec'd"
Confidence in your ability to deliver measurable results
Transparent measurement and reporting
Honest conversations when outcomes aren't achieved

Service-based selling is easier: deliver the specification, invoice for time, move to next project. No ongoing accountability, no measurement requirements, no risk.

But easier isn't better. Service-based selling commoditises your work, limits pricing power, and positions you as replaceable vendor. Outcome-based selling differentiates on value, enables premium pricing, and builds strategic partnerships.

The agencies thriving in 2025 aren't the ones with the best portfolios or lowest hourly rates. They're the ones who understand client businesses deeply, deliver measurable outcomes reliably, and position themselves as trusted advisors invested in long-term success.

Which kind of agency do you want to be?

Moving Forward

The shift from selling services to selling outcomes isn't overnight. It requires changing how you position yourself, how you conduct discovery, how you propose solutions, and how you price work.

Start small:

Reframe one service offering around outcomes
Add business impact questions to your discovery process
Propose one project with value-based pricing tied to metrics
Measure results transparently and communicate them clearly

Learn what works. Refine your approach. Build case studies proving you deliver outcomes, not just services.

Over time, this becomes your competitive moat. Whilst competitors race to the bottom on price, you're having different conversations—about business growth, competitive advantage, and measurable impact.

That's the conversation clients actually care about. It's also the conversation that builds sustainable, profitable agencies.

Frequently Asked Questions

How do I start transitioning to outcome-based selling?

Start small with one service offering. Reframe it around business outcomes rather than technical deliverables. For your next project, add discovery questions about business goals and success metrics. Build from there—you don't need to transform everything overnight.

What if I can't guarantee specific outcomes?

You're not guaranteeing outcomes—you're aligning your work with client goals and measuring progress transparently. Define what you control versus what requires client action. Set realistic expectations and build shared accountability into contracts.

How do I price outcome-based work without hourly rates?

Research the client's business impact thoroughly. If improving conversion from 2% to 3% generates £50,000 additional revenue, your fee should reflect that value, not your hours. Start with value-based project pricing before moving to pure outcome-based contracts.

What if clients only want to talk about price?

Price-focused clients often become outcome-focused clients once you ask better questions. Shift the conversation: "Before we discuss pricing, help me understand what success looks like for your business." If they won't engage beyond price, they're likely not your ideal client.

Does outcome-based selling work for smaller projects?

Absolutely. Even a £5,000 website project can be positioned around outcomes: "Reduce bounce rate by 40%, improve mobile conversion, establish credible online presence that converts enquiries." The principles scale to any project size.

How long does it take to see results from this approach?

Most agencies report seeing initial traction within 2-3 months: better client conversations, improved close rates on proposals, and ability to justify higher pricing. Full transformation to outcome-focused positioning typically takes 6-12 months.

The Fundamental Choice

Service-based selling creates transactional relationships based on price. Outcome-based selling creates strategic partnerships based on value.

When you sell services, clients ask: "What do you charge for websites?"

When you sell outcomes, clients ask: "Can you help us convert more visitors into customers?"

The first conversation leads to price comparisons and commoditisation. The second conversation leads to business impact discussions and premium pricing.

Your clients don't care what you do. They care what they achieve. Position yourself as the partner who delivers outcomes, and everything else—pricing, differentiation, client relationships—falls into place.

Next Steps: Your Action Plan

Ready to implement outcome-based selling? Here's what to do this week:

Day 1-2: Audit your current positioning

Review your website, proposals, and pitch decks
Highlight everywhere you lead with services/features instead of outcomes
List your top 3 service offerings

Day 3-4: Reframe one offering

Choose your most popular service
Write outcome-focused version connecting to business impact
Identify 2-3 key metrics you'll track

Day 5: Test with next prospect

Add business impact questions to discovery calls
Ask: "What does success look like?" instead of "What features do you need?"
Practice framing your work around their goals

Ongoing: Build your evidence

Start tracking client outcomes systematically
Document before/after metrics
Create case studies showing business impact, not just technical delivery

The agencies winning in 2025 aren't those with the biggest portfolios or lowest rates. They're the ones delivering measurable business outcomes and building strategic partnerships on that foundation.

If you're looking for a web development partner who focuses on business outcomes rather than just technical deliverables, we'd love to talk. We help UK businesses grow through websites that convert, perform, and deliver measurable results—tracked transparently against your goals.

How Much Does Web Development Cost in the UK? A Complete 2025 Pricing Guide

Michael Pilgram — Tue, 28 Oct 2025 17:55:45 +0000

Here's the uncomfortable truth about web development pricing: that £500 website will cost you £253,000 more than a £25,000 professional site over five years.

Not because of hosting fees or maintenance contracts. Because of lost revenue.

The UK web development market is worth £658.2 million in 2025, with 2,206 businesses competing for your budget. Prices range from £500 DIY templates to £500,000+ enterprise platforms. That's a 1,000x difference.

Most pricing guides stop at listing numbers. This one shows you the actual cost—including the revenue you lose from poor performance, the technical debt that compounds monthly, and the inevitable rebuild you'll need in 12-18 months.

Let's break down exactly what you're paying for, what you're getting, and whether it's worth it.

UK Web Development Market: 2025 Context

The UK web development industry is competitive and growing. Here's what the data shows:

Market size: £658.2 million (2025)
Number of businesses: 2,206 in the web design services sector
Growth rate: 3.5% CAGR between 2020-2025
Competition level: High and increasing

Related sectors are significantly larger: software development sits at £1.1 billion, whilst app development reaches £28.3 billion. The market is shifting towards modern technology stacks, with Next.js developer rates in the UK ranging from £48-£120 per hour.

Mobile performance has become critical. Over 70% of purchases now happen on mobile devices, and 53% of mobile users abandon sites that take longer than 3 seconds to load.

Web Development Pricing by Type

Basic Informational Websites

Price Range: £500 - £2,000 + VAT

These are template-based sites with minimal customisation. You get 5-10 static pages, a contact form, basic responsive design, and standard SEO setup.

Who it's for:

Local businesses needing simple online presence
Portfolio sites
Temporary landing pages
Startups testing market fit before investing properly

What's included:

Pre-built template with limited customisation
Standard contact form
Basic mobile responsiveness
Essential pages (Home, About, Services, Contact)

What's not included:

Custom design
Performance optimisation
Security hardening
Ongoing support
Content strategy
Advanced SEO

Small Business Websites

Price Range: £2,500 - £10,000

Average: £3,000-£6,000 from a regional agency

This is the most common tier for established small businesses. You get 10-20 pages, custom design elements, CMS integration (typically WordPress), blog functionality, and proper SEO optimisation.

Who it's for:

Established small businesses
Service-based companies (accountants, solicitors, consultants)
Professional services firms
B2B companies needing credibility

What's included:

Custom design (within template framework)
Content management system
Blog functionality
Contact forms and lead capture
Basic analytics setup
Mobile responsive design
Initial SEO optimisation

Timeline: 4-8 weeks typically

Bespoke/Custom Business Websites

Price Range: £4,500 - £20,000+ VAT

Fully custom design with advanced functionality. This tier includes custom integrations with your CRM or payment systems, advanced SEO, performance optimisation, and content strategy.

Who it's for:

Mid-size businesses with specific requirements
Companies with strong brand identity
Businesses needing custom workflows
Companies requiring unique user experiences

What's included:

Fully custom design from scratch
Advanced functionality and features
Custom integrations (CRM, payment systems, booking platforms)
Comprehensive SEO strategy
Performance optimisation
Content strategy and planning
Multi-language support (optional)
Advanced analytics implementation

Timeline: 6-12 weeks

E-Commerce Websites

Price Range: £1,000 - £44,000+ (highly variable)

E-commerce pricing depends heavily on product count, complexity, and integrations.

Basic E-Commerce (£1,000 - £3,000):

Template-based WooCommerce or Shopify
Up to 50 products
Standard payment integration
Basic shipping options

Standard E-Commerce (£3,000 - £10,000):

Custom template design
50-500 products
Multiple payment gateways
Advanced shipping rules
Inventory management
Customer accounts

Advanced E-Commerce (£10,000 - £25,000):

Fully custom design
500-1,000 products
Complex product variations
Multi-currency support
Advanced integrations
Custom checkout flows
Marketing automation

Enterprise E-Commerce (£25,000 - £44,000+):

1,000+ products
Multi-region support
ERP/CRM integration
Custom functionality
High-volume transaction handling
Advanced security compliance

Ongoing costs: Platform subscriptions (Shopify £23-£240/month), payment processing fees (1.5-2.9% + £0.20-£0.30 per transaction), premium plugins/apps (£10-£100/month each).

Web Applications

Price Range: £10,000 - £100,000+

Web applications are interactive platforms with complex business logic, databases, and user management systems.

Simple Web Apps (£10,000 - £50,000):

Basic CRUD functionality
User authentication
Database integration
API connections
Admin dashboard
Simple workflows

Complex Web Apps (£50,000 - £250,000):

Advanced business logic
Real-time features
Multiple user roles and permissions
Complex data relationships
Third-party integrations
Scalable architecture
Advanced security

Timeline: 3-12 months depending on complexity

SaaS Products

Price Range: £10,000 - £500,000+

SaaS development is the most complex tier, requiring multi-tenant architecture, subscription billing, and enterprise-grade security.

MVP/Basic SaaS (£10,000 - £30,000):

Core functionality only
Single tenant or basic multi-tenant
Essential integrations
Basic security
3-6 months development

Standard SaaS Application (£25,000 - £150,000):

Multi-tenant architecture
Comprehensive feature set
Payment integration (Stripe/GoCardless)
User management and roles
Analytics dashboard
GDPR compliance
Security compliance
4-12 months development

Enterprise SaaS (£150,000 - £500,000+):

Complex multi-tenant architecture
Advanced integrations
White-labelling capabilities
Enterprise security (ISO 27001, SOC 2)
High availability and redundancy
Multiple regions
12+ months development

UK-specific consideration: One SaaS startup reduced build cost from £100,000 (all-London team) to £55,000 by using hybrid teams and claiming R&D tax credits.

Enterprise Websites

Price Range: £15,000 - £100,000+

Enterprise sites serve large organisations with complex requirements, multiple stakeholders, and extensive integration needs.

What's included:

Complex architecture and infrastructure
Multiple stakeholder requirements
Advanced integrations (ERP, CRM, marketing automation)
Multi-site/multi-language capabilities
Advanced security and compliance
High availability and redundancy
Extensive documentation
Dedicated project management

Who it's for:

Large corporations
Multi-national businesses
Heavily regulated industries (finance, healthcare)
High-traffic platforms

Timeline: 6-18 months

UK Developer Rates (2025)

Understanding hourly and day rates helps you evaluate quotes and understand where costs come from.

Day Rates (Contractors)

According to ITJobsWatch data:

Web Developer: £418 per day median
Full-Stack Web Developer: £625 per day median
Developer discipline average: £438 per day (£55/hour)

London commands premium rates, whilst regional agencies offer more competitive pricing.

Hourly Rates by Experience

Junior Developers (0-2 years):

£40-£60 per hour
Basic programming tasks
Supervised work
Template customisation

Mid-Level Developers (2-5 years):

£50-£75 per hour
Independent work
Complex features
Problem-solving

Senior Developers (5+ years):

£80-£120 per hour
Architecture decisions
Team leadership
Specialised skills

Rates by Technology Stack

Next.js Developers:

UK market: £48-£80 per hour typical
Global range: £28-£120 per hour
High demand in 2025 due to performance benefits

WordPress Developers:

£35-£55 per hour typical
More abundant supply
Lower complexity generally

Full-Stack Developers:

£60-£110 per hour
Most versatile
Can handle both front-end and back-end

Geographic Variations

Regional Agencies:

£30-£60 per hour average
Lower overhead costs
Strong value proposition

London Agencies:

£80-£150 per hour average
Higher quality (often)
Premium pricing for brand and location

Offshore/International:

£20-£40 per hour average
Communication challenges
Time zone differences
Variable quality control

WordPress vs Modern Stack: The True Cost

This comparison reveals why cheaper upfront costs often lead to higher total expenditure.

WordPress Total Cost of Ownership (3 Years)

Initial Build:

Theme and customisation: £2,000
Setup and configuration: £1,500
Total initial: £3,500

Annual Costs:

Hosting: £500/year
Premium plugins: £400/year
Security updates and patches: £600/year
Maintenance and support: £1,000/year
Emergency fixes (average): £500/year
Total annual: £3,000/year

3-Year Total: £12,500

Hidden Costs (Performance Impact):

Lost conversions due to poor Core Web Vitals: £50,000/year (on £200k revenue)
SEO ranking drops from failed performance metrics: £10,000/year in lost organic traffic
Developer time resolving plugin conflicts: £2,000/year
Real 3-year cost: £198,500

Next.js Modern Stack Total Cost (3 Years)

Initial Build:

Custom development: £25,000
Total initial: £25,000

Annual Costs:

Hosting (Vercel Pro): £1,500/year
Headless CMS (Sanity): £1,200/year
Maintenance and updates: £5,000/year
Total annual: £7,700/year

3-Year Total: £48,100

Revenue Impact:

Higher conversions (superior performance): +£50,000/year
Better SEO (perfect Core Web Vitals): +£10,000/year
Zero emergency fixes needed: £0
Real 3-year value: -£131,900 (net gain)

Break-Even Analysis

The modern stack costs £21,500 more upfront. However:

Annual maintenance savings: £3,000 less (despite appearing higher)
Annual revenue gain from performance: £60,000
Break-even point: 4 months

After 4 months, the modern stack is cheaper in every way whilst generating significantly more revenue.

When WordPress Actually Makes Sense

You're a non-technical solo founder with zero budget
You need something live this week for validation
You're planning to replace it within 6 months anyway
You have under £1,000 total budget

That's the list. For any business with growth ambitions, WordPress's apparent savings evaporate quickly.

What Impacts Development Costs

Technology Stack Choice

Your technology choice affects both upfront and ongoing costs significantly.

WordPress:

Lower upfront: £1,000-£10,000
Higher ongoing: £500-£2,000/year minimum
Performance limitations (typically 400ms+ INP)
Security vulnerabilities requiring constant patching
Plugin conflicts and compatibility issues
Inevitable rebuild within 12-18 months

Modern Stack (Next.js/React):

Higher upfront: £15,000-£45,000
Lower ongoing: £3,000-£8,000/year
Superior performance (sub-100ms INP achievable)
Minimal security concerns
No plugin conflicts
Future-proof for 5+ years

The modern stack costs 2-3x more initially but pays back within 6-12 months through lower maintenance and significantly higher conversion rates.

Design Complexity

Template Customisation (£500-£2,000):

Pre-built templates with colour/logo changes
Limited flexibility
Faster delivery (1-2 weeks)
Looks generic

Custom Design (£3,000-£10,000):

Bespoke design matching your brand
Unique user experience
Longer delivery (4-8 weeks)
Professional appearance

Complex Custom Design (£10,000-£50,000+):

Advanced animations and interactions
Unique visual effects
Complex user journeys
Extended delivery (8-16 weeks)
Memorable brand experience

Functionality Requirements

Basic Features (included in base price):

Contact forms
Static content pages
Image galleries
Basic navigation
Mobile responsiveness

Intermediate Features (add £1,000-£5,000 each):

Blog with categories and search
User registration and accounts
Content management system
Multi-language support
Advanced search functionality

Advanced Features (add £5,000-£20,000 each):

Payment processing and subscriptions
User dashboards and portals
Complex workflows and automation
Real-time features (chat, notifications)
AI integration
Custom API development

Third-Party Integrations

Simple Integrations (£500-£2,000 each):

Email marketing platforms (Mailchimp, SendGrid)
Social media feeds
Google Analytics
Basic form to email

Complex Integrations (£2,000-£10,000 each):

CRM systems (HubSpot, Salesforce)
Payment gateways
Inventory management
Booking and scheduling systems
Marketing automation

Enterprise Integrations (£10,000-£50,000+):

Legacy system integration
Custom API development
Multi-system data synchronisation
Real-time data processing
ERP integration

Timeline Pressure

Standard Timeline (4-8 weeks):

Normal rates apply
Proper planning and execution
Quality assurance included

Rush Project (2-4 weeks):

20-50% premium on costs
Resource prioritisation required
Some features may need to be deferred

Emergency Rush (1-2 weeks):

50-100% premium on costs
Very limited scope possible
High stress on development team
Quality may suffer

Project Management Complexity

Single Stakeholder:

Simple approval process
Quick decisions
Lower project management overhead

Multiple Stakeholders:

Complex approval chains
Longer decision cycles
10-20% cost increase for additional PM time

Committee/Board Approval:

Extended timelines
Detailed documentation requirements
Multiple review cycles
20-40% cost increase for PM overhead

Hidden Costs and Ongoing Expenses

Domain and Hosting

Domain Registration:

Initial registration: £8-£15/year
Renewal: Often higher than initial price
Domain privacy: £2-£20/year (sometimes included)
Premium domains: £100-£10,000+ for competitive names

Hosting Costs:

Shared hosting: £1.99-£11.59/month (£24-£140/year)
VPS hosting: £10-£100/month (£120-£1,200/year)
Managed WordPress: £500-£5,000/year
Modern stack (Vercel/Netlify): £1,500-£3,000/year
Enterprise hosting: £20,000+/year

Watch for: Price increases after the first year, hidden renewal fees, and hosts charging for SSL certificates when free options (Let's Encrypt) exist.

Maintenance and Support

Support Level Pricing:

9-5 Support:

£100-£1,250/month
Business hours only
Email/ticket support
Response within 24 hours

24/7 Support:

£300-£3,500/month
Round-the-clock coverage
Phone support included
Priority response times

Average UK maintenance: £28-£395/month for small-to-medium sites, with typical annual costs of £500-£2,000.

What's Actually Included:

Security updates and patches
Plugin/theme updates (WordPress)
Regular backups
Uptime monitoring
Security monitoring
Performance optimisation
Limited content updates
Technical support

What Costs Extra:

Major functionality changes
Design updates
Emergency fixes outside of SLA
Third-party service issues
Content creation

Security Costs

Basic Security:

SSL certificate: Free-£200/year (Let's Encrypt is free)
Basic firewall: Often included with hosting
Malware scanning: £50-£200/year

Advanced Security:

Web Application Firewall (WAF): £200-£1,000/year
DDoS protection: £500-£5,000/year
Security audits: £1,000-£10,000 per audit
Penetration testing: £2,000-£20,000
GDPR compliance tools: £500-£2,000/year

Accessibility Compliance

This is no longer optional. The European Accessibility Act (EAA) comes into effect on 28 June 2025.

UK Impact: If your business sells to EU customers, you must comply with WCAG 2.2 Level AA standards.

Compliance Costs:

WCAG 2.2 audit: £1,000-£5,000
Remediation work: £2,000-£20,000 depending on issues found
Ongoing compliance testing: £500-£2,000/year

Penalties for non-compliance: Up to €1 million in administrative fines, plus potential legal action from customers.

The business case: Beyond avoiding penalties, accessible sites see an average 73% traffic growth after fixing accessibility issues. You're also reaching 15% of the global population (people with disabilities) who may currently struggle with your site.

SEO and Marketing

Initial SEO Setup:

Technical audit: £500-£5,000
On-page optimisation: £1,000-£10,000
Structured data implementation: £500-£2,000

Ongoing SEO:

Monthly retainer: £500-£5,000/month
UK average: £1,500-£3,000/month
Enterprise SEO: £6,000+/month

Content Creation:

Copywriting: £50-£200 per page
SEO blog posts: £150-£600 per article
Professional photography: £500-£5,000 per session
Product photography: £50-£200 per product

Third-Party Services

Email Marketing:

Mailchimp/SendGrid: £0-£300/month
Enterprise platforms: £500-£5,000+/month

CRM Integration:

HubSpot: £0-£3,000+/month
Salesforce: £20-£300/user/month

Payment Processing:

Stripe: 1.5% + £0.20 per transaction (UK cards)
PayPal: 2.9% + £0.30 per transaction

These percentages add up quickly. A £200,000/year e-commerce business pays £3,000-£5,800 annually in transaction fees alone.

Performance Impact on ROI

This is where cheap websites cost you serious money. Google's research on Core Web Vitals shows direct correlation between site performance and business outcomes.

Conversion Rate Impact

The data is clear:

Each 1-second delay in page load time: 7% drop in conversions
Sites taking over 3 seconds to load: 53% of mobile users abandon
Amazon's finding: 0.1-second delay = 1% sales loss

UK E-Commerce Conversion Benchmarks (2025):

Industry average: 3.4%
Strong performers: 2.5-3.5%
Well-optimised sites: 5%+
Desktop conversion: ~3.2%
Mobile conversion: ~2.8%

That mobile gap matters. With 70%+ of purchases happening on mobile, poor mobile performance kills revenue.

Real Revenue Examples

Example 1: E-Commerce Performance Optimisation

Annual revenue: £200,000
Current conversion rate: 2% (below benchmark)
After performance optimisation: 4%
Additional revenue: £200,000/year
Optimisation cost: £5,000-£15,000
ROI: 1,300-4,000% in first year

Example 2: Google Ads Efficiency

Average CPC: £2
Current conversion rate: 2%
Cost for 100 conversions: £100,000 (5,000 clicks needed)

After performance optimisation: 4% conversion
Cost for 100 conversions: £50,000 (2,500 clicks needed)
Annual savings: £50,000
Performance investment: £10,000
ROI: 400% in first year

Core Web Vitals Requirements

Google uses these metrics for search rankings:

Largest Contentful Paint (LCP):

Good: Less than 2.5 seconds
Your target: Less than 2.0 seconds

Interaction to Next Paint (INP):

Good: Less than 200 milliseconds
Your real target: Less than 100 milliseconds

INP replaced First Input Delay in March 2024 and measures responsiveness throughout the entire visit, not just the first click. Redbus achieved a 7% sales increase by optimising INP alone.

Cumulative Layout Shift (CLS):

Good: Less than 0.1
Your target: Less than 0.05

Poor Core Web Vitals don't just hurt rankings. They directly reduce conversions. The business impact is measurable and significant.

When Cheap Is Expensive

The £500 Website Trap

Here's what actually happens when you buy a £500 website:

Month 0: Site launched
Month 3: Performance issues emerge (£500-£1,000 to fix)
Month 6: Security breach or major plugin conflict (£1,000-£2,000)
Month 9: Multiple plugin compatibility issues (£1,000-£2,000)
Month 12: Site becomes unmaintainable
Month 13: Complete rebuild required (£5,000-£15,000)

Total cost: £8,000-£21,000
Plus: 12 months of lost revenue from poor performance

The 5-Year Comparison

£500 Cheap Site:

Achieves 75% of revenue goal due to poor performance
Opportunity cost: £50,000/year
Constant fixes: £3,000/year
First rebuild (year 1): £15,000
Second rebuild (year 3): £15,000
5-year total cost: £280,500

£25,000 Professional Site:

Achieves full revenue potential
Opportunity cost: £0
Minimal fixes: £500/year
No rebuilds needed for 5+ years
5-year total cost: £27,500

Difference: £253,000

This isn't theoretical. This is the actual cost of poor performance, technical debt, and lost conversions compounding over time.

Technical Debt Explained

Technical debt is what happens when shortcuts and poor code make future changes increasingly expensive.

How it accumulates:

Cheap initial build uses poor code and outdated practices
Plugin conflicts multiply as you add features
Security vulnerabilities emerge in outdated dependencies
Performance degrades as the codebase grows messily
New features become impossible to add without breaking existing functionality
Eventually, a complete rebuild is the only option

Modern stack development avoids this entirely. No plugins to conflict. No security patches to chase. Clean code that's maintainable and extensible.

How to Get Accurate Quotes

Questions to Ask Agencies

About Technology:

What technology stack do you use and why?
How do you ensure good Core Web Vitals scores?
What's your approach to mobile performance?
How do you handle security updates?
Can you show me performance metrics from similar projects?

About Costs:

What's explicitly included in your quoted price?
What's explicitly not included?
What are the ongoing costs (hosting, maintenance, support)?
Are there any additional costs I should expect?
How do you handle scope changes and additional work?

About Process:

What's your typical project timeline?
How do you handle scope changes?
What happens if the project runs over budget or timeline?
Who owns the code and design when finished?
Can I move to another provider later if needed?

About Performance:

What conversion rates do similar clients achieve?
Can you guarantee Core Web Vitals scores?
How do you measure project success?
Do you provide analytics setup and training?

Red Flags in Proposals

Pricing Red Flags:

Significantly cheaper than competitors without clear explanation
No breakdown of costs or deliverables
"Unlimited" revisions (unsustainable and unrealistic)
Unclear ongoing costs
Pressure to pay everything upfront
Hidden fees revealed later in the process

Technical Red Flags:

Can't explain their technology choices clearly
Only offers WordPress for everything
No mention of performance or Core Web Vitals
Doesn't discuss mobile performance specifically
Can't show example site performance metrics
No security discussion

Process Red Flags:

No contract or vague contract terms
No timeline or unrealistic timeline
Won't provide references or case studies
Poor communication during sales process
Pressure to decide immediately
Can't explain what happens if you're unhappy

What Good Transparency Looks Like

Clear Breakdown:

Development hours: £15,000 (150 hours at £100/hour)
Design hours: £5,000 (50 hours at £100/hour)
Project management: £2,000
Testing and QA: £2,000
Content migration: £1,000
Training: £500
Total: £25,500

Clear Inclusions:

3 rounds of design revisions
20 pages of content
Browser testing (Chrome, Safari, Firefox, Edge)
Mobile responsive design
Basic SEO setup and training
Google Analytics 4 integration
2 hours of client training
30-day warranty period

Clear Exclusions:

Content writing (client provides or additional £50-£200/page)
Stock photography (client to purchase)
Third-party licenses and subscriptions
Ongoing hosting (quoted separately at £125/month)
Ongoing maintenance (quoted separately at £400/month)
Future feature additions (quoted as needed)

Clear Ongoing Costs:

Hosting: £125/month (Vercel Pro)
CMS: £99/month (Sanity Growth)
Maintenance: £400/month (10 hours at £40/hour)
Total ongoing: £624/month (£7,488/year)

This level of transparency should be standard. If an agency can't provide this detail, walk away.

What This Means for Your Business

Web development pricing in the UK ranges from £500 to £500,000+ for good reason. You're not just buying code—you're buying performance, security, scalability, and ultimately revenue.

The key insights:

Market size matters: £658.2M industry with 2,206 businesses means competitive pricing and quality options
Performance equals revenue: 1-second delay = 7% conversion drop is not theoretical
Total cost beats initial cost: £500 sites cost £253,000 more over 5 years than £25,000 professional sites
Modern stack pays back fast: Break-even in 4 months through better performance and lower maintenance
Accessibility is mandatory: EAA enforcement from June 2025 means WCAG 2.2 compliance is no longer optional
Technology choice matters: WordPress appears cheap but hides costs in poor performance and constant fixes

Next Steps

At Numen Technology, we start every project with a discovery session to understand your actual requirements and provide transparent, accurate pricing.

Our development services use modern stacks (Next.js, React, TypeScript) built for performance and business results, not just aesthetics. We guarantee sub-200ms INP scores and perfect Core Web Vitals.

Ongoing support includes monthly performance reviews, continuous optimisation, and data-driven improvements. No plugin conflicts. No security patches. No rebuilds needed in 12 months.

Get accurate pricing for your project:

Book a free strategy session to discuss your requirements. We'll provide a detailed breakdown of costs, timeline, and expected ROI—no vague estimates or hidden fees.

Your website should drive revenue, not cost you money. Let's build something that actually works.

Why I Built an Audit Tool for Developers Who Care

Michael Pilgram — Sat, 25 Oct 2025 18:52:17 +0000

There's a moment in every website audit where I open four different tools, cross-reference their outputs, and manually check another dozen things they all miss. It's tedious. And after doing this hundreds of times over the years, it started to feel less like diligence and more like a system failure.

But here's what really bothered me: every issue I caught late was an issue that could've been caught early. Every accessibility problem, every performance bottleneck, every broken piece of structured data—these weren't just technical problems. They were missed opportunities for my clients to serve their customers better, to grow faster, to compete more effectively.

The web development industry has incredible tools for writing code, but we're still auditing sites like it's 2020. We're checking Core Web Vitals, WCAG 2.2, AI search readiness, security headers—all separately, all manually, all taking 20-30 minutes per audit. And whilst we're doing that, we're not shipping quality work. We're not helping our customers grow.

I kept thinking: this shouldn't be this hard. Making quality accessible to developers shouldn't require a toolkit of six different services and manual cross-referencing.

So I built GuardianScan. Not to build another SaaS product, but to raise the floor on what "good enough" looks like. To make it genuinely easy for developers to ship quality work that helps their customers succeed.

The Real Cost of Poor Tooling

If you've read my post on pattern matching in decision making, you know our brains are wired to spot repetition. After years of audits, I started seeing the same preventable issues repeatedly:

Missing security headers that expose customers to risk
Images without explicit width/height causing layout shift (killing conversions)
Poor font loading strategies creating sluggish interfaces
Accessibility violations that lock out potential customers
Oversized JavaScript bundles slowing down mostly-static content
Heavy client-side rendering making simple pages feel slow

These aren't just technical problems. Each one costs real money and real opportunities:

Slow sites lose conversions
Poor accessibility excludes customers
Security issues destroy trust
Bad AI search optimisation means invisible to growing traffic sources

The pattern was clear: we have better frameworks than ever, but we're still using yesterday's audit tools to check today's work. And that gap is costing our customers growth.

Lighthouse is brilliant for what it does, but it's framework-agnostic by design. It won't flag that your Next.js site is shipping 300KB of JavaScript for a static blog post, or that your Schema.org markup is malformed. Accessibility checkers like WAVE and Axe catch maybe 30-40% of WCAG violations according to WebAIM research—the rest require manual testing. SEO tools like Screaming Frog focus on meta tags and sitemaps but miss Core Web Vitals entirely.

And nobody was checking all of this together comprehensively in under a minute. I know because I searched. Spent three weeks in late 2024 evaluating every audit tool I could find. They all either focused on legacy compatibility or missed modern requirements entirely. None of them checked for AI search engine readiness—which in 2025 is inexcusable.

The Gap Between Standards and Reality

Here's what changed between 2020 and 2025 that most audit tools haven't caught up with:

AI Search Engines Changed Everything

In 2020, Google was the dominant search engine. In 2025, ChatGPT search, Perplexity, and Google's AI Overviews account for a significant portion of traffic. But they don't crawl websites the same way.

AI search engines prioritise structured data. They need clean Schema.org markup, semantic HTML, clear content hierarchy, and direct answers to questions. A site optimised for traditional SEO might be invisible to AI crawlers.

Here's the reality: your customers are searching with AI tools now. ChatGPT, Perplexity, Google's AI overviews. If your site has malformed structured data or poorly marked-up content, you're invisible to these tools. Traditional SEO scores look great, but you're losing traffic—and your customers are losing opportunities to grow.

Most audit tools still don't check for this. They'll validate your meta description but won't tell you if your Schema.org markup is actually parseable by AI or if your content is structured for the way people search in 2025.

Core Web Vitals Evolved And Tools Didn't Notice

In March 2024, Google replaced First Input Delay (FID) with Interaction to Next Paint (INP). This wasn't a minor tweak—it changed how we measure responsiveness. FID only measured the delay before the first interaction started processing. INP measures the full cycle: input delay, processing time, and rendering delay.

The threshold is strict: under 200 milliseconds. Sites that felt "snappy enough" started failing. I kept seeing this pattern—interactions that seemed instant were actually taking 300-400ms when measured properly. Rankings dropped. Conversions suffered. Customers lost revenue.

Here's what matters: your customers' users expect instant responses. Every sluggish interaction is a potential lost sale, a frustrated user, a competitor's win. This isn't academic—it's money and trust.

GuardianScan measures Total Blocking Time (TBT), a lab metric that correlates strongly with INP in the field. Whilst TBT and INP aren't identical, TBT provides reliable indicators of responsiveness issues that affect user experience and rankings. You catch the problems before they cost your customers business.

WCAG Raised the Bar And Most Tools Didn't Notice

WCAG 2.2 added nine new success criteria, and they're not trivial:

Touch targets - 44×44 pixels minimum. Harder than it sounds on dense interfaces. I've seen countless sites with 32×32px icon buttons that fail WCAG 2.2, but their audit tools (still checking against 2.1) didn't flag it.
Forms can't require redundant entry - Breaks a lot of checkout flows. Asking users to enter their address twice? That's now a Level A violation.
Authentication must offer accessible alternatives - No more "remember this grid of images" CAPTCHA. You need password managers, biometric logins, or other accessible options.

Government websites need WCAG 2.1 Level AA compliance by April 2026, but here's what actually matters: accessibility isn't just compliance. It's about not excluding potential customers. Every barrier you remove opens your client's business to more people. That's growth. That's what we should be building for.

And here's the kicker: automated accessibility audits catch 30-40% of issues at best according to WebAIM's research. The rest—colour contrast in complex layouts, keyboard navigation logic, screen reader compatibility—require manual testing or tools that actually understand context.

Modern Frameworks and Performance Patterns

Modern frameworks like Next.js, Remix, and Astro have fundamentally changed how we build for the web. Framework defaults shifted—caching behaviours changed, rendering strategies evolved, bundle sizes ballooned if you weren't careful.

For teams keeping up with framework updates, this means apps that performed well might suddenly need optimisation—not because they're slower, but because framework defaults changed. What was automatic performance work now requires explicit configuration.

GuardianScan detects framework patterns and flags common issues: oversized JavaScript bundles for static content, missing image optimisation, inefficient font loading strategies. It won't tell you which framework you should use, but it will tell you if you're shipping 400KB of JavaScript for what appears to be a mostly static page.

Framework Complexity vs. Actual Needs

About 90% of new enterprise applications are now cloud-native, built with modern frameworks. These frameworks offer powerful features—server components, progressive enhancement, edge rendering—but they also make it easy to ship too much JavaScript.

I've audited dozens of sites where everything runs client-side—massive bundles, poor hydration performance, unnecessary rerenders—when half the functionality could be achieved with less JavaScript.

Example from July 2025: An e-commerce site had a 287KB JavaScript bundle for a product listing page with minimal interactivity. The bundle size alone suggested over-engineering. After optimisation, they cut it to 134KB and dropped their LCP from 4.1s to 2.3s.

GuardianScan flags when bundle sizes exceed sensible thresholds (300KB+), helping you spot potential over-engineering before it impacts users.

What I Learned Building the Solution

Building GuardianScan forced me to think deeply about what actually matters in a website audit. Not what's easy to measure, but what creates real value.

Comprehensive but Fast

The ideal audit would check everything that matters for modern websites. Every WCAG 2.2 criterion, every performance metric, every security header, SEO fundamentals, AI search readiness. Most tools either check a subset of these or take forever to run.

GuardianScan runs 50 automated checks covering all these areas.

I've written before about systems thinking and feedback loops. The value of feedback is inversely proportional to its latency. Feedback that takes five minutes is exponentially more useful than feedback that takes an hour, even if it's slightly less comprehensive.

So I optimised for 45 seconds for a comprehensive scan. Here's why that matters: you'll actually use it. You'll check before every deploy instead of "when you remember." You'll catch issues early when they're cheap to fix, not late when they're embarrassing and expensive. You'll ship quality work consistently, not occasionally.

This isn't about speed for speed's sake. It's about making quality the path of least resistance. When doing the right thing is easier than cutting corners, standards rise naturally.

This meant ruthless focus on modern standards:

Check everything that matters for 2025 web development
Skip legacy browser compatibility checks (if you're supporting IE11, this isn't your tool)
Focus on what actually affects users and search visibility
Provide actionable diagnostics, not vague scores

Actionable Insights Over Vanity Metrics

Lighthouse gives you a performance score out of 100. It's satisfying—people love scores—but it doesn't help you fix anything. A score of 78 doesn't tell you what's actually wrong or what to prioritise.

Here's what I believe: developers want to do good work. They want to ship fast, accessible, secure sites. They don't need judgment—they need clarity. They need to know exactly what's wrong, why it matters to their users, and how to fix it.

So GuardianScan surfaces insights, not scores. Instead of "Performance: 78/100," it tells you:

LCP is 3.2s (target: under 2.5s), caused by an unoptimised hero image at /images/hero.jpg
TBT is 340ms (target: under 200ms), likely from 147KB of client-side JavaScript
CLS is 0.15 (target: under 0.1), from images without width/height attributes

Same data, but actionable. You know exactly what to fix, why it matters to your users, and what impact it has on your client's business. Fix the hero image, LCP drops, page loads faster, conversions improve. That's value.

This is where pattern detection pays off. GuardianScan identifies when images aren't using modern formats (WebP, AVIF), when fonts are loading inefficiently, or when you're shipping oversized bundles. It focuses on what affects users—load times, visual stability, responsiveness—regardless of your tech stack.

Honest About Limitations, Serious About Impact

Here's an uncomfortable truth I encountered early: perfect accessibility auditing requires human judgement. Automated tools catch the mechanical stuff—missing alt text, insufficient colour contrast, invalid ARIA—but they can't evaluate whether your alt text is meaningful, or whether your keyboard navigation flow makes logical sense.

WebAIM's research consistently shows automated tools catch 30-40% of WCAG issues. I aimed higher. GuardianScan catches about 70% by combining standard automated checks with smarter pattern detection (like finding navigation links missing accessible names, or detecting keyboard focus traps in modals).

But here's what matters: that 70% is the stuff you can fix right now, today, without specialised training. Missing alt text. Poor colour contrast. Invalid ARIA. Touch targets that are too small. These are objectively measurable, clearly fixable issues that—when you fix them—open your client's site to more users immediately.

I'd rather be honest about what the tool does than overpromise. GuardianScan catches the 70% of accessibility issues that are objectively testable, clearly documents what it checks, and reminds you that manual testing is still necessary for full WCAG 2.2 compliance.

But that 70%? That's already more than most sites do. If every developer fixed that 70%, the web would be dramatically more accessible. That's raising standards. That's what we're here for.

Modern Standards as a Feature

Most audit tools are conservative by nature. They check against established standards because those are well-documented and legally defensible. But "established standards" often means "what was true two years ago."

I decided to position GuardianScan around comprehensive modern standards—not as an early adopter gimmick, but because that's what actually matters if you're building websites in 2025:

Measure responsiveness properly - Track Total Blocking Time, a reliable indicator of user experience. Sites need responsive interactions—sluggish interfaces lose users.
Target WCAG 2.2 Level AA - Government sites need WCAG 2.1 by April 2026, but 2.2 is where compliance is heading. The nine new criteria (44×44px touch targets, redundant entry prevention, accessible authentication) aren't optional.
Validate AI search readiness - Check Schema.org markup quality, content structure for AI parsing, FAQ schema, article schema, breadcrumb navigation. If AI search engines can't parse your content, you're invisible to growing traffic sources.
Flag bundle size issues - Identify when you're shipping oversized JavaScript bundles. A mostly-static page shouldn't need 300KB+ of JavaScript to render.
Comprehensive security checks - HTTPS enforcement, CSP headers, HSTS, X-Frame-Options, mixed content detection, and other headers that protect users.

This creates a clear tradeoff: if you're maintaining legacy systems or supporting old browsers, GuardianScan isn't for you. But if you're building modern web applications for 2025 and beyond, it checks everything comprehensively.

The Product as System Design

Building GuardianScan reinforced something I've learned over fifteen years: products are systems, and systems thinking applies to how you design them.

The temptation is to add features. More checks, more frameworks, more integrations, more customisation. Every feature feels valuable in isolation. But features interact—they create complexity, cognitive load, maintenance burden.

I kept asking: what's the simplest system that delivers the core value? And the core value isn't "comprehensive auditing"—it's "quickly identify the issues that actually matter."

So GuardianScan does 50 comprehensive checks across six categories:

Modern Standards (13 checks covering image optimisation, lazy loading, font strategies, code splitting, caching)
Performance (5 checks including LCP, CLS, Total Blocking Time, First Contentful Paint, Speed Index)
SEO & AI Search (8 checks covering meta tags, Schema.org markup, sitemaps, structured data for AI readability)
Security (8 checks including HTTPS, CSP headers, HSTS, X-Frame-Options, mixed content detection)
Accessibility (12 checks for WCAG 2.2 Level AA compliance, including keyboard navigation, screen readers, touch targets)
Code Quality (4 checks covering console errors, page size, HTTP requests, resource efficiency)

Not 300 legacy compatibility checks. Not customisable rulesets. Just comprehensive coverage of what actually matters for modern web development in 2025.

This is what I call "productive chaos" from my earlier post—clear boundaries, flexible execution. The boundaries are non-negotiable (these specific checks, this performance target, this accuracy threshold). The execution is optimised for speed and clarity.

Who This Is Actually For

I built GuardianScan for myself. That sounds selfish, but it's actually the most honest product development approach I know: solve a problem you have, that you understand deeply, that you can evaluate without pretense.

But "myself" is a proxy for everyone who genuinely cares about doing good work and helping their customers succeed:

Agencies who want to deliver exceptional value. You're not just building websites—you're helping your clients grow their businesses. Every performance issue you catch saves them conversions. Every accessibility barrier you remove opens them to more customers. Every security hole you fix protects their reputation. You need tools that help you consistently deliver work that drives real business results, not just looks pretty. You need to catch issues before launch because you care about your clients' success, not just because you're afraid of looking incompetent.

Freelancers who take pride in their craft. You inherit a project or start fresh, and you want to do it right. You want to ship work that's fast, accessible, and secure. Work that helps your clients compete and grow. You need to identify what matters—the issues that actually impact users and business metrics—and fix those first. You need data to back up your recommendations because you respect your clients' investment and want to deliver measurable value.

In-house teams who ship with confidence. You're responsible for your company's web presence. Every deploy is an opportunity to improve or a risk to degrade. Did that last update break accessibility? Did bundle size creep up? Is the site still fast on mobile? You need to know immediately because your users and your business depend on it.

All three groups share something fundamental: they care. They want to do good work. They want to help their customers succeed. They just need tools that make quality achievable, not aspirational.

What I'm Not Solving

Here's what GuardianScan doesn't do:

It doesn't replace manual accessibility testing. If you need full WCAG compliance, you still need human evaluators. GuardianScan catches the automated 70%, which is valuable, but it's not certification.

It doesn't do ongoing monitoring. It's a point-in-time audit, not a monitoring service like Sentry or LogRocket. You run it when you need it—before launch, after deploys, when something feels wrong.

It doesn't customise to your exact standards. Some tools let you configure thresholds, disable checks, add custom rules. GuardianScan is opinionated: these are the modern standards, these are the thresholds that matter. If you disagree, it's probably not the right tool for you.

It doesn't audit authenticated content. It checks public pages. If your app requires login, GuardianScan can't reach those screens. This is a genuine limitation I might address later, but for now, it's out of scope.

It can't analyse your source code. GuardianScan scans the live site—what gets delivered to browsers. For deeper insights like checking individual component usage, analysing unused dependencies, or reviewing build configurations, you'd need source code access. Future integrations (like build plugins or GitHub apps) could add this, but the current focus is on what's detectable from the live site: performance, security headers, accessibility, and SEO.

Being clear about limitations isn't weakness—it's honesty. Every tool makes tradeoffs. I'd rather be upfront about mine than overpromise.

What This Actually Means for You and Your Customers

If you're still manually checking sites across four different tools, you're spending 20-30 minutes per audit. That's not just your time—that's time you're not shipping features, not serving customers, not growing their business.

But here's what really matters: every issue you catch early is an opportunity you protect for your customer. Every performance problem you fix before launch is conversions you save. Every accessibility barrier you remove is customers you welcome. Every security header you implement is trust you build.

For your customers' users: Faster sites that work for everyone. Sites that show up in AI search results. Sites that feel responsive and modern. Sites that don't exclude people with disabilities. This is what we should be building.

For your customers' businesses: Better conversion rates from better performance. More traffic from better SEO and AI search visibility. Wider audience reach from better accessibility. Stronger trust from better security. Faster growth from doing the fundamentals right.

For you as a developer: Ship work you're proud of. Catch issues before they're embarrassing. Justify your recommendations with clear data. Deliver measurable value to your clients. Spend your time building, not auditing.

That's what GuardianScan is for. Not vanity metrics. Not compliance theatre. Real value for real customers trying to grow real businesses.

What I'd Do Differently

Building GuardianScan taught me things I wish I'd known earlier:

Start with the positioning, not the features. I spent weeks debating whether to include X or Y check before realising the real question was: who is this for, and what problem does it solve for them? Once I answered that, feature decisions became obvious.

Opinionated tools are easier to build and more valuable. Every time I considered adding customisation—"let users configure thresholds" or "support custom rulesets"—I created complexity that didn't serve the core value. The best tools have a point of view.

Speed is a feature, not a constraint. I could have built a more comprehensive audit that takes five minutes. But optimising for 45 seconds forced me to prioritise ruthlessly, which made the tool better. Constraints drive clarity.

Modern standards are a competitive moat. Most tools optimise for compatibility with legacy systems. Building comprehensive checks for modern standards (WCAG 2.2, Core Web Vitals, security headers) and emerging requirements (AI search optimisation, modern image formats) makes you less universally applicable but far more valuable to the people who matter—developers building new things, not maintaining legacy systems that should have been retired years ago.

Raising the Floor, Not Just the Ceiling

After building GuardianScan, I've been thinking about what "raising standards" actually means. It's not about the exceptional sites—the teams with unlimited budgets and dedicated performance engineers are already shipping excellent work. They have the resources and expertise.

It's about raising the floor. It's about making "good enough" actually good. It's about making quality accessible to the freelancer building their third website, the small agency juggling ten clients, the in-house developer who inherited a codebase and just wants to make it better.

The web development industry has incredible potential. We have frameworks that make complex interactions trivial. We have deployment tools that make shipping instant. We have browsers that are faster and more capable than ever. But if we're still shipping slow, inaccessible, insecure sites because our audit tools are five years out of date, we're not living up to that potential.

Every site that's needlessly slow costs somebody business. Every site that excludes disabled users costs somebody opportunity. Every site with poor AI search optimisation costs somebody growth. These aren't abstract problems—they're real costs to real businesses trying to serve real customers.

GuardianScan is my attempt to make quality more achievable. To make "did we ship something good?" answerable in 45 seconds instead of 45 minutes. To help developers who care about their work deliver value to customers who are trying to grow.

I'm building GuardianScan to raise the floor on web development standards. If you care about shipping quality work, there's a free scan at guardianscan.ai. I'd love to hear what you think—what audit challenges do you face? What gaps do you see in existing tools?

Read more about my approach to web development and systems thinking at michaelpilgram.co.uk.