Product websites that let UK buyers approve an AI that records their meetings.

A dedicated section covering your role as processor, the data processing agreement, the sub-processor register, retention defaults and how deletion requests are handled. Each document carries a version date and a short change log, so a data protection officer at a council or a bank can see what changed since their last review.

A plain page, with screenshots, showing what attendees see when your assistant joins: the join message, the on-screen indicator, the wording added to calendar invites and how someone asks for recording to stop. UK GDPR expects people to be told, and buyers want to read the exact words before they roll the product out to staff.

Where audio, transcripts and summaries are processed and stored, which hosting regions customers can choose, and which safeguards cover any transfer outside the UK, such as the International Data Transfer Agreement or the UK extension to the EU and US Data Privacy Framework. We write it with your engineers so it matches the real infrastructure.

The Digital Markets, Competition and Consumers Act 2024 treats drip pricing as an unfair practice where consumers are involved. Your plans page shows what each tier includes, whether prices exclude VAT, how seat and usage charges work and what renewal looks like, so nothing new appears late in the sign-up flow.

Keyboard navigation, visible focus, captions on product videos, sufficient contrast, labelled forms and target sizes that meet WCAG 2.2. Many UK public bodies must meet accessibility regulations themselves and look for suppliers who take the subject seriously, and the Equality Act 2010 covers services offered to the public.

A section for councils, NHS bodies, universities and central government: the frameworks you are listed on, your accessibility statement, security documentation and a contact route for procurement officers. If you sell through G-Cloud on the Digital Marketplace, the site mirrors the wording of that listing so buyers see one consistent story.

One page per integration, such as Microsoft Teams, Zoom, Google Meet, Outlook and Google calendars, Slack and the CRMs your customers file notes into. Each page states what the connection does, which permissions it requests and who must approve it, built from structured CMS entries so the next one takes minutes to add.

Landing pages for the cities and nations you target, with real local substance rather than swapped place names. That can include a Welsh language route where you sell to Welsh public bodies bound by the Welsh Language Standards, and copy for Scottish buyers that reflects their separate legal system and their own procurement portal.

A cookie banner that meets PECR, with analytics and advertising tags held back until a visitor agrees, plus demo and sign-up forms that pass company size, sector and region to your CRM. Enquiries reach the right account executive, and marketing can still measure which pages produce pipeline.