Building ClubFriends from zero
Notes on starting a consumer social product alone — the constraints I picked, what I am avoiding, and the small loops I run every week.
I started ClubFriends with one constraint: I had to be able to ship a usable version every Friday. Not a pretty version. Not a complete version. Just something I would tap through on the bus and not be embarrassed by.
That single rule changed everything about how I work.
The week-shaped loop
A week is the largest unit I can hold in my head without losing the plot. I plan on Monday, prototype Tuesday and Wednesday, harden Thursday, and ship something to TestFlight before I leave my desk on Friday. It is not novel, but the consistency is the point.
When I drift from this rhythm, the product drifts too. The features I add get fancier. The decisions I delay get harder. The honest signal from a human tapping through the app gets quieter. So I treat the cadence as non-negotiable, and the surface area of any single week as small.
Choosing what not to build
The harder discipline is what not to ship. ClubFriends will never have a public feed, recommendations, or a content algorithm. Not because those things are wrong, but because they would pull the product away from the small group of people I am building it for.
Every founder has a list of features they keep almost-deciding to add. The useful version of that list is the one you keep deleting from.