AI disclosure is a design problem
Since 2 August 2026 the EU AI Act requires you to tell people when they are dealing with a machine. Most teams will answer that with a footer, which is the one place nobody looks.
Sectors / Compliance and regulated software
Website Design for compliance software
We put the proof where buyers look first.
We design compliance software and websites for teams whose buyers need proof before they trust a single screen
Trusted where compliance matters
subcontractors onboarded through Wise.280,000+
Why compliance
The buyer is cautious. The interface should not be.
Compliance products sell on trust. We design compliance, payments and regulated software so a cautious buyer can see it is safe above the fold, and the person using it every day can get the job done without a manual. Compliance software is sold to people whose job is to avoid a problem: an audit, a fine, a worker paid wrong, a sign that does not meet the regulations. Feature lists matter less to them than two questions: will this product hold up when the regulator asks, and will their team actually use it? Most compliance products are written as if they were feature lists anyway. The site leads with what the software does and barely mentions what it protects against. The product shows every field and every setting because the engineers who built it know what each one is for. Trust signals sit in the footer. So the whole category looks complicated and feels risky, when safety is the thing it is selling. We design the other way round. Proof first: the volume handled, the checks done, the security, a named customer. Then the structure, so a cautious buyer can find the one claim that matters to them without a demo. Then the product itself, organised around the task people came to do (the pay run, the check, the lookup).
What we have built
Built to be audited
600 pages of UK law made searchable. Search comes first, and one screen replaces three tabs, with the regulation text, the diagram and the project side by side. 440 hours saved per team, per year.
See TSRGDWhat we already know
You will not be teaching us what an audit trail is
We arrive fluent. Why reversibility, human sign-off and refusal states are design work for us to solve early. Where a security claim belongs on a page and how to make it something a buyer can check. What a deadline does to a buyer (Wise's construction page was designed first because every construction firm was reacting to the 1 October 2026 Right to Work change) and how to use one only when it is real. How to show the regulation, the data and the decision on one screen so the person using the product can defend what they did. If your product needs a glossary and a statute before a designer is any use, that is our normal starting position.
Numbers you can check
- 440 hrs
- saved per team, per year, on TSRGD's platform.
- 600 pages
- of traffic signs law made searchable for TSRGD.
- 200+
- projects since 2023, across products, websites and brands.
Testimonials
Not our words, theirs
As someone who had never managed a website project before, I couldn’t have asked for a better company to work with. … Highly recommend for anyone looking to work with a company that knows their stuff.
I highly recommend Grid Design. Sy and his team are brilliant at what they do. Fast, highly skilled, and extremely efficient. They are a rare diamond.
I’d be creating new projects with you guys all year if I had the time!
Ash MiriFounder, Air Landline & TSRGDFAQs
Questions compliance companies ask us
Yes, and it is a growing share of what we do. Statutory regulations (TSRGD), workforce compliance and payments (Wise), and the hosting platforms where abuse and compliance load is designed in or out at onboarding. The thread is products where trust is the thing being sold.
That is where we are most useful. Audit trails, reversibility, human sign-off, refusal states and plain-language explanations are all design decisions, and designing them early is how a product gets through legal on the first pass. We would rather have legal in the first workshop than the last review.
We design with realistic but invented data, never your customers'. Where research needs real users, it runs under your NDA and your data rules, and nothing leaves your systems. We will sign what you need before the kickoff.
A full engagement, from discovery through research, architecture, prototypes, interface and design system, is a twelve-week project priced as a fixed scope. We give you the number at proposal stage, before you commit to anything.
Yes, and for a regulated product it is usually the only sensible route. We rebuild the architecture underneath the screens so your team ships the new version in stages, each one checkable, rather than switching everything off for a big-bang launch that nobody can audit.
Yes, if the interface shows the working. What the model did, how confident it is, and how a person checks or overrides it. Reliability sets what the system may do alone; it does not decide whether you can ship. We design the human-in-the-loop steps first.
Related reading
Worth reading before you call
Your cancel button retains customers
From January, UK subscription rules mean a reminder before every renewal and an exit as easy as the sign-up was. Most hosting companies will send that to Legal, when it belongs to whoever owns the billing screens.
Your website should rule buyers out
Most of your buyers decide before they fill anything in. So the useful question is what they go looking for on your site and cannot find.