First-class self-hosted calendar (conversion lever for the self-hoster persona)

[ClaydeCode]

From a pilot feedback interview (3-month check-in, 2026-07-06).

A pilot user's explicit condition for switching to a paid plan is a genuinely good self-hosted calendar. They already run their own instance where calendar/mail integration is the priority — it is why they self-host at all. Without it they will not pay; with it they would seriously consider signing up. Max committed on the call to prioritize calendar.

Evidence

[0:15:12] „...die Kalender insbesondere auch bei mir die Priorität genießen. Ansonsten wäre das nämlich ein Punkt, wo ich tatsächlich darüber nachdenken würde, da mit einzusteigen.“
[0:15:31] (Max) „Also dann priorisiere ich die Kalender mal.“

Source: internal pilot interview, 2026-07-06.

[ClaydeCode]

From 2026-07-06 weekly: Aaron taking on a prototype.

Plan: keep Radicale as the CalDAV backend and vibe-code a CalDAV client frontend so the user never sees CalDAV/Radicale — 'just a calendar', UI+backend bundled. Calendar-only first (contacts/tasks later). Must-haves: sharing, subscribing to others' calendars, import/export. He'll prototype against a fresh test user on his own Nextcloud/Radicale instance.

Caveat: calendars are hard (time/timezones/DST) — treated as a fire-and-forget attempt.

Validated demand: both a pilot user and Aaron independently name calendar as a top wanted feature.