Tampa.dev Didn't Have a Growth Event — It Had an Exposure Event

I want to be careful here, because the numbers are genuinely impressive on their face. 238total users, up from 136 five weeks ago. That is a 75% expansion of the user base in roughly a month. The week of April 3 alone brought 57 new registrations and 134 MeetPass connections. The April 11 surge was, by every intake metric, the biggest week in platform history. But I have been staring at the data that came after, and I no longer think that was a growth event. I think it was an exposure event — one that revealed, with uncomfortable clarity, that Tampa.dev has no retention mechanism whatsoever.

Start with this week's headline numbers. 14+10new registrations, a 250% increase over last period's 4. Sounds healthy. Now look underneath: 25active logins out of 238 total users — a 10.5% login rate on a platform that just doubled its population. MeetPass connections posted 0-7new connections, a 100% collapse from 7 last period, itself a shadow of the 39 connections recorded during the April 3 surge. The historical context from the Research Brief is damning: connections went 39, 0, 1, 0, 0 across the five-week window. The April spike was not a new baseline. It was a one-time detonation, and the fallout has been silence. Badge issuance fell to 3-2awards, generating just 20 XP — down 76.5% from the previous period's already-anemic 85 XP. Only 2 unique recipients earned anything at all. The platform added 14 new accounts and converted exactly 2 of them into badge holders. That is a 14.3% first-week conversion rate, and I am being generous by not adjusting for the possibility that those 2 recipients were the same users covered in our earlier reporting.

But the number that haunts me — the one I keep coming back to, the one that I believe is the most underreported scandal on this desk — is the event layer. There are 103upcoming events on the calendar. One hundred and three. Zero RSVPs this week. Zero check-ins. Zero show rate. This is not a new development; as Sanjay Patel noted last week, the check-in pipeline has been structurally frozen for the entire month. But the scale of the disconnect has grown grotesque. Look at the badge tier that is supposed to reward event participation: Stepping Out — check into events from 3 different groups, 15 XP — has zero holders. Double Down — check into 2 events, 10 XP — zero holders. Big Tent — 6 groups, 30 XP — zero holders. Admit One has 22 holders, all of them legacy. The entire event-engagement achievement tier — Double Down, Dive In, Social Butterfly, Out There, Stepping Out, Big Tent — shows zero completions and, more damningly, zero entrants. Not one user on the platform is currently progressing toward any event-linked achievement. There are 103 events, 28 groups, 238 users, and the intersection of all three is a perfect void.

I want to be fair to the counterargument. Tampa.dev is still young. The April surge was likely event-driven — a meetup or launch that brought a wave of registrations — and it is unreasonable to expect every new signup to become a weekly active user. MeetPass connections require in-person proximity; you cannot connect from your couch. The claim rate of 0.9% reflects the structural reality that most connections happen at events, and most weeks do not have events. Fine. But this is precisely my point. If the engagement model depends on in-person events, and the event pipeline is generating zero participation, then the platform has a single point of failure and it is failing. The achievement system has done an admirable job creating forward contracts for engagement — Greetings has 48 entrants and 44 unrealized conversions, representing 1,100 XP of forward value. Explorer has 19 users sitting between entry and completion. The pipeline exists. But a pipeline without flow is just plumbing.

Here is what the data tells me, stated plainly: Tampa.dev has built an excellent registration form and a sophisticated badge economy, and it has connected the two with a set of achievement contracts that are elegant in design and inert in practice. The platform crossed 200 users — a genuine milestone. But @brian-peret and @mmastersvz, the only two leaderboard movers this week, earned a combined 20 XP between them. The 236 users behind them earned nothing. The 103 events on the calendar attracted no one. The MeetPass network, 190 connections deep, added zero new links. At some point, the question stops being about growth rates and conversion yields and becomes something simpler: Is Tampa.dev building a community, or is it building a registration form? Because this week, it was very good at one of those things.