Footify: Run the Game, Play the Game
The Wednesday night kickabout, out of the group chat. Who is in, who has paid, who is playing where, and who won Player of the Match, all settled before anyone reaches the pitch.
01The challenge
One organiser, fifteen mates, and a chat that loses everything
Every weekly game runs on one person chasing RSVPs, sorting teams, then asking people for a fiver for a fortnight.
Headcount is a guess
Attendance lives in a chat thread, so nobody knows the real number until players arrive.
The organiser is the bank
Fronting the pitch fee and chasing it back is the most common reason casual squads fall apart.
Line-ups scroll away
Teams get posted once, then half the squad asks again on the way to the pitch.
No history worth arguing about
Results, goals and Player of the Match live only in memory.
Drop-outs every week
Reshuffling a reserve list by hand is exactly the admin that burns organisers out.
02What we built
Design the money out of the awkward conversation
Flutter across iOS, Android and web, so a player answers from whatever they have to hand. The product decision is where payment sits.
Squads and games
Squad creation with a shareable invite link, player profiles and recurring weekly fixtures.
RSVP, reserves and payment
Live attendance, a self sorting reserve list, guest invites, and payment taken at confirmation.
Line-ups, reports and stats
Published line-ups, match reports, a timed Player of the Match vote, and squad leaderboards.
Payment is collected when a player confirms, so being on the team sheet and having paid are the same action.
03In the app
One game screen, the whole week's admin
Who is in, who has paid, and what team they are on.
An organiser posts the fixture once. Everything that used to be a message thread, the headcount, the money and the teams, now lives on the game itself.
01Real time RSVPs
Coming, pending and declined at a glance, so the true headcount is known days out.
02Self sorting reserves
When a confirmed player drops out, the next reserve moves up without the organiser touching it.
03Payment at confirmation
Money is collected as a player says yes, so the team sheet and the paid list are one list.
04Published line-ups
The teams live somewhere permanent instead of a message that scrolled away.
05Guest invites
Fill the pitch from outside the regular group without adding anyone permanently.
06Match reports and POTM
The result, plus a timed vote open to the organiser or the players who actually turned up.
07Stats and leaderboards
Goals, assists and Player of the Match counts tracked among the same fifteen people, week after week.
08Web companion
footify.live lets a player respond or check the line-up without reaching for the app.
04The instance
Footify, as it ships
Two screens from the live app: a player's profile and the squad picker an organiser works from before kick off.
No client wordmark to show here, so the screens carry the weight instead. Near black surfaces throughout, one yellow accent held back for the primary action.
Colour otherwise stays functional. A player's role badge, S, RM, LW, is the only thing on the screen that is not white, grey or black.
05Stack
One Flutter codebase across mobile and web
Three platforms, because a player answers on whichever one is open.
06Results
A weekly ritual that runs itself
The admin the organiser used to carry now sits in the app.
Platforms from one Flutter codebase
Payment chasing, money is collected at RSVP
Reserve list that reshuffles itself
Stores live, App Store and Google Play
Footify is for the organiser who sorts the game, the players who show up, and everything that usually gets lost in the chat.
Footify Limited
One codebase covering every way a player responds
Collection moved to the RSVP, so organisers stop fronting the fee
Built around real 5 a side squads, not league management
Let's take the admin out of the thing people enjoy.
Tell us where your users are doing manual work around your product and we'll bring the engineering to design it out.
Start a project