Perigon Partners · November 2026 · Live

The tool worked. That was the problem.

Perigon's ESG compliance checker was producing good reports and nobody had complained. I rebuilt it anyway. A report that used to arrive by email an hour later now appears in about 30 seconds, and the rules behind it live in one place instead of four.

ResultReport in 30 seconds, down from an hour
RoleHead of Growth and Operations. Perigon's CEO and a senior consultant own the regulatory content and the calls on how it applies
See it The ESG Compliance Checker

Nobody had complained about the ESG Compliance Checker. The reports were good, our CEO was happy with them, and leads were coming in. If you’d asked me in October whether it needed rebuilding, I’d have said no, and I’d have meant it.

It was one of the first things I built at Perigon. A visitor answers about nine questions about their company: what kind of company it is, staff, revenue, assets, whether they’re FCA regulated, whether they plan to list, whether they hold government contracts, and what ESG work they’ve already started. They get back a personalised briefing. First a compliance map of which UK ESG reporting rules apply to them, each labelled Required, On the Horizon or Monitor. Then three sections of strategic advice written by Claude, grounded in a regulation reference document Perigon maintains.

The ESG Compliance Checker start screen: Take the guesswork out of ESG compliance. Right now. Nine questions, UK regulations only, personalised to your profile

Gender Pay Gap, Modern Slavery, SECR, ESOS, Carbon Reduction Plans, climate disclosures under the Companies Act, FCA TCFD, UK Sustainability Reporting Standards, FCA SDR. When our CEO first mentioned the idea I’d been in the job for a day and didn’t know what ESG stood for.

I still couldn’t tell you which of those rules catch a mid-sized insurer. That isn’t my job. Our CEO knows, and so does the consultant who brings our regulatory expertise. My job is to make what they know available to a stranger at eleven o’clock at night, with neither of them in the room.

Working is not the same as fine

When I went back to it in November, two things bothered me. Neither was visible to anyone filling in the form.

The first was the wait. You answered the questions, and about an hour later an email arrived with a link to your report. An hour is a long time. By then the person who was curious enough to answer nine questions about their company is in a meeting, or on the school run, or has forgotten why they were curious. Speed to value is a growth number. I’ve run enough funnels to know that a result in seconds and a result in an hour are not the same product.

The second was where the rules lived. The regulations, and the judgement about who they apply to, sat in four places: a Google Doc, a Google Sheet, the hover notes in the report, and the prompt Claude worked from. Four copies of the same expertise, kept in step by hand, by people with day jobs. They had started to drift apart, which is what copies do.

None of this was broken. It was just quietly expensive, and it was going to get more expensive every time a regulation changed.

Thirty seconds, not an hour

Now the site stores your answers, Claude writes the report in the background, and you go straight to your results page. The compliance map appears in about ten seconds. The full briefing is there in about thirty, each section appearing as it’s written, so you have something to read while the rest arrives.

Results sit behind the same email check as Perigon’s other tools, and links expire after 60 days. Zapier still does what Zapier is good at, updating the lead sheet and sending the emails, and nothing else. I dropped the nine-day follow-up email and rewrote the two-day one.

The quality bar was one line, and I set it before anything was touched: the output is very good, keep it that way. Every change got measured against it.

One copy of the rules

The reference document now lives in the website’s CMS. The build refuses to deploy if someone breaks its structure, and the hover notes in the report are pulled straight from it, so they can’t drift again. A check built into the system beats asking careful people to be careful.

While I was in there, the FCA published its September 2026 rules. UK SRS replaces TCFD for listed companies from 2027, and listed companies now have to say whether they have a climate transition plan. The reference document was updated, and so was Perigon’s public article on UK ESG requirements, keeping the CEO’s original wording and changing only the facts.

That second rule caught my eye for a commercial reason. Since October, climate transition planning for banks and private equity is what Perigon leads with. A rule that makes listed companies say out loud whether they have a transition plan is not just another row in the table for us.

I’m not the expert. I didn’t need to be.

I didn’t write the code. Claude Code did. I didn’t write the regulatory content either. What I did was notice that a tool everyone was happy with had costs nobody could see, then get the expertise out of my colleagues’ brains and four drifting documents and into one place a system can run.

It runs without me now. Nobody has to press anything for a report to go out, and nobody needs me at my desk. The one job still mine is keeping the reference document up to date, which is now one document, in one place, with a build that tells me if I’ve broken it. And it doesn’t just wait for strangers to find it. We send it to the people we most want to work with, so the first thing they get from us is a briefing on their own company, in their own browser, in the time it takes to make a coffee.

What I don’t know yet is whether a report in thirty seconds turns more people into conversations than a report in an hour. I’d bet on it. I’ll get back to you once there are a few months of leads to compare.

Under the bonnet

  • Built: 9 to 13 November 2026, with Claude Code, in the Perigon website repo (Astro on Netlify). The original was built in my first weeks at Perigon as an add-on to the old Webflow site.
  • Before: form to a 21-step Zapier chain, report emailed about an hour later.
  • After: answers stored by the site, report written by Claude in a background function. Compliance map in about 10 seconds, full briefing in about 30, sections appear as they are written. Results behind an email check, links expire after 60 days.
  • Rules: one regulation reference document, in Keystatic. The build fails if its structure breaks. Report hover notes generated from it.
  • Zapier: lead sheet and emails only. Nine-day email dropped. Two-day email rewritten with an unsubscribe link and self-hosted images. Duplicate lead rows caught.
  • Regulatory update: FCA September 2026 rules (UK SRS replacing TCFD for listed companies from 2027, transition plan disclosure).
  • In use: runs without me. I keep the reference document up to date. Perigon sends the tool to prospects in its ideal client profile as well as leaving it on the site.