Subsplash vs Notion
Side-by-side trajectory, velocity, and editorial themes.
Subsplash wires natural-language AI through People and Analytics — its two highest-leverage surfaces.
Subsplash has spent the last two months putting AI on the busiest parts of its admin. Trends AI consolidated giving, attendance, and events data into AI-buildable dashboards in late March, and People Assistant followed in May with natural-language filtering of congregation lists. Between those, the team shipped a dedicated Events Manager role, a group-attendance analytics dashboard, and smaller workflow-board UX gains.
The bet is clear: ministry staff with no SQL or BI background want to ask questions of their congregation's data in plain language — both for analysis and for action. Trends AI handles the analytical half; People Assistant is the actionable list-building counterpart. The supporting work — RBAC, attendance analytics, faster workflow navigation — is what lets the AI features actually land inside real church-staff workflows.
Expect AI to extend next into Workflows (plain-language routing rules for congregants) and Giving (donor segmentation for stewardship outreach), with a unified AI surface across modules as the natural endpoint. Pricing the AI tier separately, as Trends AI already is, telegraphs how Subsplash will monetize this push.
Notion turns itself into the orchestration layer where other agents run.
Notion has shipped a full developer platform — Workers as a hosted runtime, External Agents API for Claude/Codex/Decagon, a CLI, inbound webhooks, and an Agent SDK. The Custom Agents beta has produced more than a million agents in two months, and the latest releases are about turning that surge into something enterprises will actually deploy: per-agent credit limits, workspace caps, admin dashboards, and a Library directory. Doc editing has become the visible surface; the engine being built underneath is agent and data plumbing.
The trajectory is from doc-and-database app to connective tissue between agents, SaaS APIs, and team workflows. Each recent release pushes in the same direction — agents become more discoverable (Directory), more reviewable before they act (Plan Mode), more governable at scale (admin controls), and more capable of reaching outside Notion (Agent SDK, webhooks). The strategic bet is that whoever owns the orchestration substrate matters more than whoever ships the smartest model.
Expect Workers to convert from free-beta to credit-metered on August 11, 2026, with pricing pressure landing on agent-SaaS startups whose value is mostly API stitching. The External Agents API and Agent SDK should move from waitlist to GA next, alongside deeper Slack/MS Teams surfaces where Notion agents run without users ever opening Notion.
See more alternatives to Subsplash →
See more alternatives to Notion →