Skip to content

Flagship case study

The website, the front desk
and the app that does the job.

Cornwall Play Safety inspect and repair playgrounds across Cornwall for parish councils, holiday parks and schools. I built all three parts of how that business runs online and in the field — and because one person built them, they actually fit together.

Kernow.ai built the complete operating system for Cornwall Play Safety, an RPII-accredited playground inspection firm: their website, the Foredesk AI assistant answering enquiries on it, and InspectVoice, the voice-driven app the inspector uses on site to produce BS EN 1176 inspection reports.

The business

Cornwall Play Safety carry out routine and operational playground inspections to BS EN 1176 and 1177, repair equipment, and lay and repair safety surfacing. Their customers are parish and town councils, holiday and caravan parks, schools and academies, right across the county.

It is a business where the paperwork is not admin — it is the product. When a play area is inspected, the photographed, risk-rated report is the evidence that a duty of care was met. If something goes wrong on that site, that document is what gets examined. So the software cannot be approximately right.

What was built

Three parts, one system

Most small firms end up with a web designer, a chatbot vendor and an off-the-shelf app that was built for somebody else's industry. Three suppliers, three invoices, and nothing quite joining up.

01

The website

Built to explain a technical service to a parish clerk. Every inspection tier set out plainly, the accreditation and insurance visible, and an honest section addressing the obvious question — if the same firm finds the fault and fixes it, who checks the finding?

Fast, accessible, structured so search engines understand it, and built to the same standard as anything else I ship.

02

Foredesk — "Piran"

The assistant on the front of the site. It answers questions about inspection tiers, report turnaround and what to send for a quote — from the firm's own information, not a general model's guesswork.

Anything about a specific site goes to the inspector, and Piran takes a number for the callback. It says it is an assistant up front, and it hands over rather than inventing an answer about somebody's playground.

Try it ↗

03

InspectVoice

The voice-driven inspection platform the work actually runs on. Built for UK parks, playgrounds and outdoor recreation assets, around BS EN 1176.

The inspector speaks the inspection while stood in front of the equipment, rather than writing it up that evening from memory and a page of notes. That is the difference between a report written while you are looking at the thing and one reconstructed four hours later.

Why this is different

The joins are where systems fail

Anyone can build one of these three things. The reason this works is that the same person built all of them, so nothing is lost in translation between suppliers.

The assistant knows what the website says, because both were written from the same understanding of the business. The reporting reflects what an inspection actually captures, because whoever built the app understood the standard rather than being handed a spec. And when something needs changing — a price, a service, a tier — there is one person to tell, not three who each need convincing it is their job.

That is the argument for a single builder at this scale. Not that it is cheaper, although it usually is. That the seams do not show.

Built to a standard the work deserves

An inspection record is what a council relies on if a child is hurt on their play area. Software that produces that record is not a convenience app, and it was not built like one.

Security by design and UK GDPR compliance from the start rather than bolted on afterwards: proper access controls, secrets kept out of the browser where anyone can read them, every input validated, dependencies scanned automatically for known vulnerabilities. The same engineering standard a large organisation would insist on, applied to a Cornish firm that cannot afford a failure.

No shortcuts, because there is no version of this where a shortcut is worth what it costs.That's how everything here gets built.

Straight answers

What did you build for Cornwall Play Safety?
Three things that work as one system: the website, the Foredesk assistant that answers enquiries on it, and InspectVoice, the voice-driven app the inspector uses on site. Most firms have to buy those from three different suppliers and hope they fit together.
What is InspectVoice?
A voice-driven inspection platform for UK parks, playgrounds and outdoor recreation assets, built around BS EN 1176. The inspector speaks the inspection on site rather than writing it up in the evening, and the report comes out the other end.
Why does one person building all three matter?
Because the joins are where systems fail. When the website, the assistant and the field app are built by the same person, the assistant knows what the website says and the reporting matches what the inspection actually captured. Nothing gets lost translating between three suppliers.
Can I get the same thing?
The pattern, yes. The specifics are built around the business. InspectVoice is available to other inspectors, councils and inspection firms, and Foredesk works for any business that loses enquiries outside working hours.
How is the data handled?
Security by design and UK GDPR compliance as standard: proper access controls, secrets kept out of the browser, inputs validated, dependencies scanned automatically. Inspection records are the evidence a duty of care was met, so they are treated as records that matter rather than as app data.

Want the same for your business?

It doesn't have to be all three at once. Most start with the piece that's costing them most — usually the enquiries slipping away outside working hours. Tell me how your business actually runs and I'll tell you straight where the win is.

Get in touch