Cowee

Where this started

Working alone is hard and shared focus sessions help, but running them by hand does not scale: the schedule, the seats, the room links and the no-shows eat more time than the sessions themselves.

Who we built it for

People who work alone and get more done in a room with others, even a video one.

What fought back

1. 
   01

   Seats that cannot be sold twice

   Two people booking the last seat at the same moment is the normal case, not the edge case. Allocation has to settle it in the database, not in the code that asked.

2. 
   02

   A room link only the booked may hold

   The link is the product. It has to reach exactly the people with a seat, at the right moment, and a permanent ban has to be enforced where access is granted rather than where it was requested.

3. 
   03

   Releasing without dropping anyone

   Sessions are live when you deploy. That is why there are 76 test suites and 26 migrations underneath: both counts are countable, and both exist so a release never lands in the middle of somebody’s hour.

What we actually built

The bot runs the whole loop: onboarding in two languages, booking a slot in the visitor own timezone, seat allocation that cannot double-book, reminders before the session, a video room link issued only to those actually booked, a host flow, post-session feedback, complaints with a permanent ban enforced where access is granted, and an admin panel for slots and attendance.

What came of it

Live in Telegram and running sessions: booking a seat and joining the room never leaves the chat.