About CrowdDuty
Why we built this
Why we built this
We read the statute, not the summary

Ben Liger
Founder, CrowdDuty
I’ve spent the last fourteen years as a full-stack developer, building production software for companies including the Financial Times, Diageo, and Betfair. That work has included building compliance software from the ground up, so CrowdDuty isn’t my first time turning a regulation into something operators can actually use. Before that, I started out in marketing — which is part of why this site doesn’t read like it was written by an engineer alone. I’ve also built and exited a company before, so this isn’t the first time I’ve bet on an idea from nothing.
When I started building CrowdDuty, I read the actual statutory guidance for Martyn’s Law — all of it, not the summaries — because I didn’t want to guess at what the Act actually requires. What I found is that the tools already out there handle the straightforward case well, and go quiet the moment things get complicated: shared sites with more than one responsible party, one-off events rather than permanent premises, the enhanced-tier document that’s supposed to explain your reasoning, not just tick a box. CrowdDuty exists to cover what everyone else left out.
Want to chat about how CrowdDuty could help your business?