
Practical guides for running your weekly kickabout — plus the engineering story behind Capo.
15 years. 718 matches. 4,959 goals. What the data from one obsessively tracked weekly kickabout reveals about amateur football, ageing, and why men never stop.
Everything you need to organise a weekly five-a-side — from finding players and booking a pitch to managing RSVPs, collecting money and picking fair teams.
Practical strategies for handling five-a-side dropouts and no-shows — from waitlists and deadlines to pre-payment and attendance tracking.
WhatsApp is great for banter but terrible for running a five-a-side. Here is why your group chat is making the organiser’s life harder — and what to use instead.
Practical methods for balancing five-a-side teams fairly — from captains picking to stats-based balancing and AI team generators.
Honest comparison of the best five-a-side organiser apps in 2026 — from Capo and Spond to WhatsApp and spreadsheets. Find the right tool for your weekly kickabout.
Your five-a-side attendance is dropping and the game feels like it is dying. Here is how to bring it back — from tracking stats and growing your squad to fixing the admin bottleneck.
Turn your weekly kickabout into a proper league with stats, points and tables. Here is what to track, how to set up a points system and why it changes everything.
Practical guide to collecting match fees for five-a-side — from cash and bank transfers to in-app payments. Stop being a debt collector.
Every five-a-side group has the same cast of characters — the goal hanger, the bruiser, the moaner. After 15 years of organising, here’s what actually determines who’s best.
Most five-a-side groups have core players, regulars, and last-minute fillers. Here’s how to manage tiers, handle dropouts, and stop the admin from taking over your week.
Spond is built for clubs. Capo is built for mates’ football. An honest look at which app fits a casual 5-a-side group — and how to choose between them.
9-Part Series
The engineering decisions behind a 125,000-line platform built entirely with AI. Real problems, real solutions, real lessons.
View seriesThe high cost of getting exactly what you want
What happens when the distance between wanting something and getting it disappears - and what that does to the way you treat other people.
Why judgment and specs matter more than prompts when building with AI—and where the real work happens.
Why 45,000 lines of specifications matter more than prompts when building with AI.
How connection pooling broke the RLS policies and what I built instead.
Adding tenant_id to 33 tables and 70+ API routes without breaking production.
How fail-fast patterns prevent silent cross-tenant data leaks.
What happens when five players click Book for the last spot at the same time.
From 45-second blocking requests to instant responses with background processing.
Why 300+ duplicate requests became 30, and what that did to load times.
The hardest feature to build with AI, and the 15 iterations it took to get right.
Why static JSON exports beat live tenant switching for demo modes.