build of the week · you decide
one build, open to the crowd.
Each week one idea waiting in the build queue goes public. Vote it up or down. The owner keeps the final say, but the crowd shapes the call.
AsyncOath — binding 'I will respond by Friday EOD' receipts for distributed teams
voting openAdd a ⏰ emoji to any Slack message; bot DMs the recipient: 'sign an oath by when you'll reply.' Recipient picks Friday EOD, oath is posted publicly to thread, bot enforces and updates the recipient's public 'oath kept' streak.
the problem
Distributed teams send async asks (Slack, Linear, GitHub) and 30-50% never get a clear response by the implicit deadline. The asker either nudges (creating noise) or escalates (creating conflict). Slack reminders are private; Linear due dates are individual; neither creates a public commitment artifact.
who it serves
Engineer, PM, or designer on an async-first distributed team of 8-50 people
the model
$7/mo individual; $19/mo team-of-10, freemium
the wedge
- Slack app: emoji-triggered oath flow + public team streak page
- Linear webhook: every issue assignment auto-prompts an oath
- Stripe at $7/mo individual after 5 oaths/mo free
would we build this?
Cast a vote. It is crowdsourced signal, not the final call.