What has shipped, and when

BusyWait is now open: sign up, connect two calendars free and upgrade to Pro or Team from the billing page. No access request.

A pass over what this site says the product does. Sync speed is now stated in general terms: changes usually show up within minutes, depending on the provider. A booking link checks the calendars selected for it. A guest list, where switched on, is copied as text and nobody is invited.

The site named calendar providers BusyWait does not connect. It connects Google, Outlook and iCloud, and the list now says exactly that. It also said every calendar syncs within seconds, which is not true of every provider, and that claim came out.

The payload comparison and the feature grid each appeared on three pages; they are down to two and one. Section headings that were epigrams now say what the section is about, with the epigram demoted to a sub-line. The pricing page argues for the price of Pro instead of only stating it.

/about used to redirect to ak.dev, which pushed anyone evaluating BusyWait onto a different brand halfway through deciding. It is now a page on this site: why the thing exists, why busy-only is the floor rather than a setting, who publishes it, and what happens if it breaks or is wound down.

Head-to-head pages against Calendly, OneCal and Reclaim.ai, a page for people reconsidering Cal.com, and a buyer’s guide setting out the six questions worth asking of any calendar sync tool. Each one names where the other product is the better answer, because a comparison nobody could lose is not a comparison.

A dated record of what has shipped. It exists because a small product with nothing visible happening reads as an abandoned one, and because the claim that this is maintained should be checkable rather than asserted.

A new reliability page sets out what happens when a provider errors, a token expires or the service itself is down, how you are told, and what happens to your data if BusyWait is ever wound down.

The publisher (AKdev Ltd, with its Companies House number), the BusyWait brand and the product are now three distinct nodes emitted on every page, with the plan prices as offers and breadcrumbs on inner pages. The FAQPage markup came out — Google deprecated FAQ rich results in May 2026, so it earned nothing — while the answers themselves stay exactly where they were. A full favicon set and an installable web manifest went in at the same time.

Links shared into Slack, LinkedIn or iMessage used to show the home page regardless of which page was sent. Each page now carries its own title, description, canonical URL and social card.

The first public version of the site: what the product does, what it stores field by field, what it will never do, and what it costs. Alongside it a machine-readable layer — a robots.txt carrying Content Signals, an llms.txt overview, and every page available as markdown — so answer engines describe the product from its own words rather than a competitor’s framing.