Sunsama vs Rize
Side-by-side trajectory, velocity, and editorial themes.
Sunsama ships Task Priority + Auto-Sort and starts wiring Sunny into MCP — daily planning gets opinionated.
Sunsama is in steady weekly-release cadence, with the bulk of recent work concentrated in two places: the Task Priority + Auto-Sort system, which has just graduated from beta into a documented core feature, and the Sunny AI assistant, which is gaining persistent memory and MCP-callable primitives like get_task_by_id. The integration surface continues to deepen — Linear, Todoist, Jira, Asana imports now carry priority signal through into Sunsama's own model.
The product is moving from 'manual daily planner' toward 'opinionated planner that can be driven by Sunny or external agents.' Auto-Sort is the most telling move: Sunsama is now willing to reorder the user's day on its own based on priority and scheduled time, which is a philosophical step away from the manual drag-and-drop heritage. The MCP work signals they want Sunsama to be addressable by other AI tools — not just consumed via the Sunny UI.
Expect the next few weekly drops to expand Sunny's MCP toolset (write actions, not just reads) and to roll priority rollover into more of the integration importers. A 'Sunny plans your day' end-to-end flow that leans on the new priority + auto-sort plumbing is the natural next milestone.
Rize pivots from passive tracker to live, AI-queryable work data substrate.
Rize landed two directional moves in the last 30 days: live time-entry creation that replaces the previous batched-after-the-fact model, and a Beta MCP server that exposes time tracking data to Claude and ChatGPT for natural-language analysis. Around those, the team rebuilt the time-entry review panel and added an alternative Work Hours calculation that excludes break time the way most teams actually want. Cadence is high and the releases are coherent, not scattered.
The product is repositioning itself from 'passive tracker that classifies activity later' to 'live work-data platform other AI tools can read.' MCP integration signals Rize wants to be the data layer external assistants reach into, not a self-contained reporting app. The live-entries shift is the user-experience counterpart: data is current and editable in the moment instead of reconstructed later.
Expect the next moves to lean into the new substrate: manager-facing project-overrun alerts, budget-vs-actual dashboards, or richer outbound webhooks. A natural follow-on is broader MCP exposure (write-side actions, not just read), or a chat surface inside Rize itself.
See more alternatives to Sunsama →
See more alternatives to Rize →