Cohort 2: Results & Reviews

Jess built an invoice-chasing agent to fix a persistent cash flow problem at their charity. The team had been following up on overdue invoices inconsistently, relying on automated chases that contacts routinely ignored.

They set up an agent called Agent Jesse in Claude, connected to Xero via a CSV workflow, drafting personalised chaser emails each week. It checks email history to skip invoices already being resolved and intercompany accounts, producing 19 ready-to-send drafts in a single session.

Since building it, thousands of pounds in long-overdue payments have come into the organisation.

Abbie automated sponsorship prospecting, a process that previously took multiple hours per prospect.

They built a workflow connecting Claude to a Slack channel, Apollo for contact enrichment, and HubSpot as the CRM. Claude runs a weekly check on Slack to spot potential sponsor companies, searches Apollo for relevant contacts by job-title priority, and deduplicates against existing outreach history.

It then creates the contacts, companies, and deals in HubSpot automatically, complete with research notes and a draft outreach message.

Nick automated the triage of data-pipeline failures as the sole member of their data team. Production error emails from their orchestration tool gave no useful detail, so every failure meant manual investigation through multiple authentication steps, including on Christmas Day.

They built a webhook-based workflow using Zapier and Claude Code that intercepts errors, diagnoses the cause, checks their calendar for availability, posts summaries to Slack, and logs tickets in Linear.

It then opens pull requests in GitHub that a second Claude instance reviews.

George cut down account-call prep that was taking the team 30 to 45 minutes per call, manually pulling data from HubSpot, Metabase, Chargebee, Xero, and contract attachments.

They built an agent that runs daily, querying those sources to generate account briefings in a Slack-style workflow. It surfaces ROI figures, payment status, risk factors like break clauses, and contact changes, and account managers can self-serve by typing a slash command with a venue name.

The tool has already reached full adoption across the account management team.

Jen built a supplier cost-analysis dashboard to handle the yearly job of reviewing supplier cost increases across multiple destinations, work that had been spread across Google Sheets with inconsistent assumptions and heavy data-loading issues.

The dashboard pulls raw data from BigQuery into a connected Google Sheet, refreshed hourly, with Google authentication restricting access to internal staff. It can be filtered by destination, departure month, and tour to see where cost targets are or are not being met.

They built it first in Cowork, then migrated to Claude Code, which needed less back-and-forth when making specific changes like adding charts or adjusting formatting.