Things that are live and running.
Platforms, websites and apps in production. Where there is a story worth telling about how something was built, it gets a full case study. Where there is not, it is listed plainly.
A month of paid ads, measured by nothing
An account had run for a month with around £149 spent and zero conversions reported. The obvious reading was that the ads did not work. A read-only audit found one conversion action — a generic page-view tracker, inactive, with zero lifetime conversions — and no analytics property linked at all, so no event on the site had any route to the ads platform. The search terms were clean and impression share was lost to ad rank rather than budget, which ruled out targeting. Campaigns were paused rather than optimised, and measurement was rebuilt and verified before another click was paid for.
Instrumental Teachers Hub
Private music teachers run real businesses without any of the infrastructure a business normally gets — policies, invoices and safeguarding documents assembled by hand from whatever a colleague sent years ago. This is one product answering that: a compliance toolkit with eleven UK-ready templates, a members' community, and an AI Professor that marks written work from a photograph. It had to work on a phone, because teachers are between lessons rather than at a desk, and it had to be built in-house on a budget that assumed no funding round.
Recurring billing that actually recurs
The same platform was advertising £15 a month, cancel anytime, on top of a WooCommerce product that charged once and never renewed — with access granted by a member landing on a URL rather than by a payment, and nothing that could take it away again. This is the rebuild onto Stripe Billing: SCA-compliant checkout for UK cards, access driven by signed webhooks, cancellation honoured by Stripe, and deliberately no Stripe secret key stored on a site carrying known plugin vulnerabilities. It covers the two faults end-to-end testing caught that would otherwise have met the first paying member.
Analytics that looked healthy and recorded nothing
Page views arrived normally, so the tag was obviously working — while every form submission, product click and purchase silently never reached the platform. Three assumptions about how the analytics queue behaves, all of which read as correct from the code, and only one of which survived contact with the network panel. The write-up shows which, how each was disproved, and the buffering fix that stopped events racing the tag they depend on.
Selling a file at 2am without being awake
A £39 digital product delivered by hand within 24 hours, which is slow enough to lose an impulse purchase and tethered to somebody reading an inbox. Rebuilt as a signature-verified payment webhook that maps the purchased price to the right files, issues time-limited signed download links, and streams them from private storage that is not reachable at any public path. Includes the error-reporting bug worth more than the automation: a missing configuration value that reported itself as a bad signature and would have sent anyone debugging to the one thing that was not wrong.
Running right now.
Both of these run unattended in production. Neither was built to be shown — they exist because something had to work.
AI Social Media Agent
One line of a spreadsheet becomes three platform-specific captions, a branded graphic and a post on Facebook, Instagram and LinkedIn — written, rendered and published without anyone opening a tab. GPT picks the angle and writes per platform, the model output is validated before anything publishes, and the row is marked done. It runs unattended in production, and is one of the templates on sale.
Automated finance ops
Invoices raised on a schedule from records that already exist, checkout links written back, payments read in by webhook and matched off against what is outstanding. What reconciles is closed automatically; what does not is flagged to a person rather than quietly ignored. AI drafts the customer emails mid-workflow. It runs the billing for a service business with over 300 customers.
Front ends, and one still in the studio.
Premium WordPress website
A school with strong ABRSM results and national scholarship credentials was being let down by a site that did not look like it belonged to them. The rebuild is a hand-written theme rather than a bought one: templates authored for the actual content, responsive from the first breakpoint instead of retrofitted, and content fields that match how the school thinks about its own terms and lessons. Parents deciding where to send a child judge on credibility long before they read a fee.
Richmond Piano School
Seven pages covering lessons, gallery, term dates and enquiries for a school teaching across Richmond and Twickenham. Built on Wix because that is what the client could confidently maintain themselves afterwards — the right answer is sometimes the platform they will actually keep updating, not the one that would impress another developer. Booking forms and search optimisation were wired in around it, and the site is live and taking enquiries.
Miss Melody AI Music Theory Tutor
Music theory for seven to nine year olds, which means the hard part is not the AI at all — it is holding a child's attention and rendering notation they can read. Built in Next.js and TypeScript with abcjs drawing the staves, and a tutoring engine that responds to a wrong answer the way a patient teacher would rather than marking it and moving on. Still in build.
Want yours on this page?
Everything above started as a short email describing a problem. Send yours — what the thing needs to do, who it is for, and roughly when. You will get a straight answer within one working day, and no calls unless you want them.
hello@cbwstudio.studio