Pro Sound Studio
The old site asked you to trust a studio while publishing a fictional street address and a 555 phone number. This one publishes only what can be proved — and prices every single thing it sells.
What was actually wrong
What I shipped
An evidence rule
Every claim classified: verified, client-confirmation-required, or removed. The fake address, the unsourced testimonials, the 5,000-tracks figure and the celebrity credits all came out. The real phone number was recovered from the live booking system and corroborated against three directories.
Accessibility, measured not asserted
axe-core across all 39 routes found 353 failing elements in 19 colour combinations — every page failed. Fixed by splitting one overloaded red token into a background red and a text red, and consolidating seven ad-hoc greys into one accessible token. Now zero violations in two engines.
A pricing architecture
Mined 135 rows from the live booking system and found Spark/Pro/Elite were pure multipliers with no stated difference — customers were asked for 124% more with no reason given. Surfaced the tier definitions, then priced the five service lines that had no price anywhere.
The site as the desk
A Supabase backend holds the catalogue, tier definitions and orders. Row-level security is deny-by-default on anything holding a name, email or phone. Quotes snapshot their prices, so a later catalogue edit can never change a number already given to a customer.
Memberships that show their working
Five monthly plans, each priced below the à-la-carte value of what it contains, with the saving printed next to the price so the customer can check the maths.
Infrastructure parity
29 legacy URLs redirect 308 with query strings intact, and the payment permission is delegated only to the verified booking origin — generated from one source of truth with a test that fails if the two ever drift.
The result
◉ Proof: every number here was measured, not estimated — axe-core and Lighthouse against the deployed build, and all 29 redirects checked live. The site is deployed and public; the client’s domain has not been pointed at it yet, because contact details, policies and photography still need owner sign-off. That gate is deliberate and documented, not an oversight.
Deliverables & build
Why it matters
The interesting work here was not design. It was deciding what a business is allowed to say about itself. A studio taking card payments was publishing a fictional address, borrowed credibility and prices nobody could explain — and the fix for each was the same: find the source, or do not print it.
What is left is not code. It is six questions only the owner can answer — refund terms, file retention, photography rights. They are written up and waiting, because shipping a guess on any of them would have put a real business at risk.