What has shipped, and when

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 why Pro is £7 rather than only stating it, and says out loud that Team is £4.80 a head. And the domain gets acknowledged once, on the home page, under the list of things this product will never do.

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 same material now appears in short on the home page and on the sync page, because "what happens when it breaks" is a fair question to ask before connecting anything.

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.