18-vehicle private hire firm: off Wix, onto a booking machine.

Case study, anonymised

18-vehicle Warrington PHV firm. Wix out, WordPress in.

The firm ran 18 saloons and 2 MPVs out of a licensing office in Warrington. Every web booking arrived by email, the controller re-keyed it into Autocab, and roughly one in six had a wrong postcode. The brief was simple: kill the re-keying and lift the share of daily jobs coming through the widget.

Before

• Web share of daily jobs: 9% (roughly 14 jobs / day out of 155)
• Postcode re-key error rate: 1 in 6 web bookings
• Average controller time per web booking: 32 seconds
• Mobile PageSpeed: 38 (Wix free theme, 4G test)

What we built

Standard £1,995 pack. 12-page WordPress build, Autocab integration, fare calculator, PHV plate footer, one council-district service page. Full URL preservation from the Wix site, 27 redirects mapped. Live in 19 days from brief.

After (5 months post-launch)

• Web share of daily jobs: 27% (42 jobs / day out of 156)
• Postcode re-key error rate: zero (Google Places validates before submit)
• Controller time per web booking: 3 seconds (auto-drop into Autocab)
• Mobile PageSpeed: 94
• Estimated dispatcher hours saved per week: 3.4

Case anonymised at operator request; numbers verified from Autocab console exports and GA4. For an ongoing SEO retainer, our sister brand Marketing The Change is the fit. For non-taxi web builds, Liverpool Web Designers.

Related

• Private hire vertical
• Rebrand service
• Brighton Yellow Cabs (named case study)

Representative build · 18 vehicles · WordPress + dispatch

The firm

An 18-vehicle private hire firm is a council-town private hire operator running roughly 18 vehicles on WordPress + dispatch. A firm at this size lives and dies on the phone: peak-time call volume, account clients, and a booking site that has to earn its place next to the console.

The problem

• A Wix site that looked fine but could not quote a fare or take a real booking.
• Every online enquiry landed as an email a controller had to chase.
• No presence for the council-district searches the firm depends on.

What we built

• A WordPress rebuild with a fare-quoting booking widget wired to dispatch.
• Council-district pages for each area the firm covers.
• A mobile-first booking flow built for evening and weekend demand.

What changes

• Enquiries arrive already-quoted instead of as raw emails.
• The firm starts showing up for ‘taxi near me’ across its districts.
• Controllers spend less time re-keying and chasing web enquiries.

Timeline and stack

Live in 14 to 21 days from signed brief. Built on WordPress, wired to WordPress + dispatch, WCAG 2.2 AA on every template, and the operator owns the domain, the code, and the content.

Representative example. Figures describe the kind of change a firm of this size and setup typically sees after the rebuild, not a single audited client result.