Scheduling & Coordination
LiveShare one link, everyone marks when they're free, and the best slot rises to the top.
The problem
Finding one hour that works across a dozen calendars is a problem email is actively bad at. Every reply-all adds a constraint and removes none, the organiser ends up tallying availability by hand, and the answer arrives two days after it mattered. Existing tools mostly solve it by making everyone sign up first, which loses the half of the group who were never going to.
Anonymous participation on every tier
For in-person meetings, on paid tiers
Free, Pro, and Org
How it works
Converge solves the coordination problem that email was never built for: finding one hour that works across a dozen calendars and four time zones. Guests open a link, paint the times they are free, and a live heat map resolves the group's best slot without anyone tallying responses by hand. Time zones convert automatically, so nobody does arithmetic to answer a scheduling question.
Either set the window by hand or write a sentence and let the AI compose step turn it into a draft — title, duration, candidate window, invite text. It uses forced tool-calling rather than parsing free text, so the draft comes back as structured fields instead of a paragraph that has to be re-read.
Participants open it and paint the times they are free onto a grid. There is no account step: an anonymous participant is a first-class row in the database with its own identity, not a degraded guest mode bolted on afterwards.
A live heat map ranks candidate slots as responses land, so the best time surfaces on its own rather than being counted out. Every time is rendered in the reader's own zone, so nobody does arithmetic to answer a scheduling question.
Confirming produces an .ics any calendar client will take — including for the guests who never signed in. In-person meetings also get a map and a venue weather forecast.
What it does
Engineering
The part of a build that is worth reading is rarely the feature list. These are the calls that shaped the product, and the reasons they were made.
The whole product depends on people answering without signing up, so the anonymous identity had to be something row-level security could reason about rather than a session trick. It is a first-class column with its own policies, which is what makes a guest's availability as safe to store as a member's.
The API was migrated to a code-first GraphQL schema specifically to be consumable by something other than the web app. The React Native client now speaks to the identical endpoint, and the tier limits, recurrence rules and time-zone helpers live in a shared package both clients import — so a rule cannot be right on the web and wrong on a phone.
Subscriptions can arrive from the web or from a phone's app store, which means two billing systems disagreeing about the same person. The entitlement layer is biased toward keeping access: wrongly retaining a plan costs a little revenue, wrongly revoking one breaks a paying customer.
Limits
Every product page lists what the software can do. This one lists what it cannot, because that is the half you would otherwise find out afterwards.
Questions
Also from the studio
Next step
Tell us what the software has to do and who it is for. We come back with a scope, a first milestone, and a number. Discovery is free and commits you to nothing.