Writing from the bygild studio
We write about what we learn building for small UK ventures: what a website actually needs to say, what makes an enquiry form convert, how local SEO works for a small business, and what to avoid when briefing a web designer. No jargon, no generalist advice repackaged for clicks.
The earlier posts below come from the studio's education-sector work; the lessons in them hold for any small organisation. Newer writing follows the studio's current focus: data protection, security, and the governance layer under the website.
In May 2026 an automation over-fired and burnt through the studio's monthly email allowance before breakfast. Here is the post-mortem: what broke, the two bugs underneath it, and what a one-person studio does differently afterwards.
Read: The morning a scheduled job spent our month's email quota →Bygild uses AI every working day, so we wrote down what we use, classified it against the EU AI Act's risk tiers, and set rules we can show a client's procurement team. The register matters more than the policy.
Read: We mapped a two-person studio's AI use to the EU AI Act. Here is what that looks like. →Bygild built keyproof.co.uk, a verification product handling ID documents, faces and driving licences. The data protection could not be bolted on afterwards. Here is what designing around the data from day one actually changed.
Read: Compliance decisions are design decisions: what building KeyProof taught us about UK GDPR →