Friend codes as the on-ramp, not the party (remote workers)
Kim's coworking Slack is loud; her brunch graph is six people who know her kitchen. Codes pulled college friends into the app; pings pull her body into sunlight. Remote work brunch is calendar geography, not mood.
Kim uses friend-code brunch invites when stepping out of the home office into sunlight with a human is the goal—not a group chat performance, not a stranger queue. Six characters link someone you already trust into the graph; the ping is the readable ask that follows redemption. Affinity without a calendar object is the drift pattern for remote workers: weeks blending together because every meal happens over the same laptop. The fix is mechanical: code if needed, then place plus time or Let's Decide, audience on the ping, published end.
Hand codes like spare keys—to humans you can picture over eggs—not like coupons on a public board. One code per person, no reset theater. Redeeming is instant friendship; only then does brunch belong on the feed.
For remote workers, the code solves graph gaps; the ping solves Saturday. Skipping either step is how brunch friend code invites stay folklore in chat while calendars stay empty.
On Let's Join, remote workers brunch starts in a graph you already trust: redeem a six-character friend code for instant friendship—no reset theater, no public stranger radius. The feed opens after your first friend; phone verifies once for safety while Cognito email handles login. Your ping is place plus time, or Let's Decide while the hour is still negotiable; audience lives on that object—all friends, the undeletable Close friends list, or a named list—with friends-of-friends toggled only when this meal should widen. RSVP yes, no, or maybe; open plans that never lock time cancel after seven days so the feed does not hoard guilt.




