Cardiff runs Wales: government, public services, and a media sector that punches far above its weight. We automate the service delivery behind all three — with bilingual Welsh-English workflows built in from the start, not bolted on.
Every AI vendor pitching in Cardiff will tell you their models "support Welsh." Technically true, practically misleading. Large language models handle Welsh at a usable-but-imperfect level — noticeably weaker than English on nuance, terminology and formal register. For a public body with Welsh Language Standards obligations, "mostly right" is not good enough, and a vendor who glosses over this has never had their output reviewed by a Welsh speaker with a red pen.
Our approach is bilingual by design, not by hope. AI drafts and triages in both languages; Welsh-language outputs pass through native-speaker review before publication; translation memories and terminology databases ground the model's vocabulary in your approved terms. The automation still saves enormous time — triage, summarisation and first drafts work well in Welsh — but the language standard is protected by humans, as it should be.
Beyond language, Cardiff's automation market has two clear shapes. Public sector and arm's-length bodies process citizen enquiries, applications, grants and casework at volume, under procurement rules and audit requirements. The media cluster — production companies, broadcasters, post-production — drowns in the unglamorous side of content: transcription, subtitling, metadata, versioning, compliance paperwork. Both are high-volume, rules-based, and measurable. Both are where AI is genuinely good.
Cardiff's compactness is an advantage buyers underestimate. Government, media and the universities sit within a few square miles, which means discovery workshops can put every stakeholder in one room — and automation projects live or die on whether the people doing the work were in the room when it was designed. We insist on it.
Cardiff's public sector buyers need procurement-friendly delivery: fixed phases, go/no-go gates, evidence packs, and costs that survive audit. That is how we scope — you are never committed beyond the current phase, and every phase ends with written evidence of what was built, what it cost, and what it measured. If a pilot does not prove out, stopping is a legitimate outcome and we will say so.
Build versus buy gets an extra honest answer here: public-sector SaaS and G-Cloud-listed tools cover a lot of standard ground, and we will point you at them where they fit. Our custom work targets the genuinely Welsh-specific problems — bilingual workflows, devolved-policy processes, the integrations nobody else has built. That is where an agency earns its fee.
Delivery is remote-first from our Manchester studio, with in-person discovery and reviews in Cardiff. No fake Cardiff office — but a team that understands Welsh Language Standards are a legal duty, not a nice-to-have. See our AI automation practice and our Cardiff AR work.
Cardiff indicative ranges — labelled, not quoted:
Bilingual review capacity is a real project cost — we scope native-speaker QA explicitly rather than pretending the model does it alone.
Straight answers to what Cardiff teams ask us most.
Honestly: worse than English, and anyone who says otherwise has not tested it. Major models handle Welsh at a usable-but-imperfect level — fine for drafts and summarisation, not for publish-ready copy without native-speaker review. We build bilingual workflows with human Welsh review designed in, never as an afterthought.
Citizen enquiry triage, grant and application processing, media production workflows (transcription, subtitling, metadata), and bilingual content drafting. High-volume service work where consistency and auditability matter.
Phased delivery with go/no-go gates, the smallest pilot that proves the case, and honest build-vs-buy calls — we would rather you buy a £200/month tool than pay us to rebuild it. Every phase ends with an evidence pack your finance team can audit.
No — Google warns against guarantees and we agree with Google. We guarantee senior delivery, honest timelines in writing, and reporting tied to cases processed and cost per transaction.
We build the bilingual workflow — parallel English/Welsh content pipelines, Welsh-language triage, translation-memory integration. Final Welsh copy is always reviewed by native speakers, because the language deserves better than unchecked machine output.
Dig deeper into the services and locations that pair with Cardiff automation.
Bilingual automation built properly: AI does the volume work, native speakers protect the standard. Let's scope your first workflow.
Talk to Visuosofts