Monthly Recap and Q1 Review

A quarter in the books

Three months ago, manyCalendars was a browser extension with a landing page and a handful of early users. Today, we have a growing community of contractors, consultants, and fractional executives who rely on it daily. This recap covers what happened, what we learned, and where we are heading.

Top posts this quarter

The content that resonated most tells us something about what our audience cares about:

1. "How to Never Double-Book Yourself Again" remains the most-read post on the blog. Practical, tactical, and directly tied to the pain point that brings people to manyCalendars in the first place.

2. "The Hidden Risks of OAuth Calendar Access" surprised us with its engagement. Turns out, people are more privacy-conscious about their calendar data than we expected. The post resonated particularly with consultants managing competing client relationships.

3. "Running a Consultancy Where Client Confidentiality Is Everything" generated the most direct responses. Several readers reached out to share their own near-miss stories about calendar data exposure. The fictional persona clearly hit close to home.

Feature highlights from Q1

Conflict count in the topbar. A small change that users love. The red badge showing the number of active conflicts means you never need to scan the entire week view to know if there is a problem.

One-click busy blocks. Blocking time across calendars went from a multi-step process to a single click. The block defaults to "Busy" with no details, which is the only sane default for cross-calendar blocking.

Improved ICS feed parsing. We fixed edge cases with recurring events, timezone handling, and Apple iCloud's occasionally creative interpretation of the ICS specification. Feeds from iCloud, Google, and Outlook now parse reliably.

Availability export. Generate a plain-text summary of your open time slots and paste it into Slack or email. This feature came directly from user feedback about the back-and-forth of scheduling across clients.

What we heard from readers

Three themes emerged consistently in feedback this quarter:

"I did not realize my calendar data was going to a server." Many users came to manyCalendars after learning that their previous calendar tool was syncing data through a cloud backend. The local-first pitch resonates because the alternative is scarier than people initially realize.

"Can you add support for [specific calendar platform]?" We got requests for Zoho Calendar, Fastmail, and several niche project management tools with built-in calendars. We are prioritizing based on request volume. Keep them coming.

"The extension just works. I forget it is there." This is the best compliment a tool like ours can receive. Calendar management should be invisible. If you are thinking about your calendar tool, it is not doing its job well enough.

What is coming in Q2

We do not do big roadmap reveals because plans change. But here is what we are actively working on:

Additional calendar platform support. The most-requested platforms from Q1 feedback are being built now. We will announce each one as it ships.

Improved conflict resolution workflows. Detecting conflicts is step one. Helping you resolve them faster is step two. We are exploring what that looks like without adding server-side components.

Better onboarding for new users. The setup process works, but it could be smoother. First impressions matter, and we want new users to reach their unified calendar view in under 60 seconds.

Thank you to everyone who used manyCalendars this quarter, reported bugs, requested features, or shared the tool with a colleague. Building in public means building with feedback, and yours has been invaluable. If you have not tried manyCalendars yet, there is no better time to start. Q2 is going to be a good one.