Senja vs Lytics
Side-by-side trajectory, velocity, and editorial themes.
Testimonial platform consolidates its surface and extends it to AI agents via MCP.
Senja is a small (3-person) testimonial collection and presentation tool serving 3,000+ paying customers. Recent work moves across two themes: stitching the product surface into a single coherent flow — Forms 2.0 unification, native Slack notifications replacing Zapier — and exposing the entire testimonial database to AI agents via a first-party MCP server.
The big bet is becoming part of the AI-native marketing stack — letting Claude and any MCP client search, filter, and create testimonials and grab embed codes for any Senja asset. Alongside, the team is consolidating accumulated dual-track product surfaces and pulling third-party glue into native integrations. Both moves point at scale: one unlocks new distribution, the other reduces support load before growth.
Expect deeper MCP capabilities — generating sizzle reels or case studies from a Claude prompt — and continued migration of features that previously lived in Zapier or Make into native integrations. The hiring of a Customer Success Lead suggests a near-term push from 3K to 10K paying customers, so feature work will likely tilt toward retention and team-collaboration polish.
Lytics retires the legacy audience builder, ships zero-copy Salesforce Data Cloud sync, and pushes integrations weekly.
Lytics is a CDP shipping at a steady weekly cadence. Recent work cuts across three vectors: a forced migration off the legacy audience builder (sunset May 4, 2026) toward a redesigned builder with geolocation rules; heavy expansion of cloud-warehouse and ad-platform integrations (Salesforce Data Cloud, The Trade Desk, Microsoft UET, Pushly, Algolia, GCS); and admin-side governance — naming conventions, metric threshold alerts, easier OAuth recovery.
Two arcs are visible. First, the integration catalog is being deepened toward server-side conversion APIs and zero-copy data movement — Salesforce Data Cloud's bidirectional sync with zero-copy bulk via GCS is the architecturally interesting move and likely a template for what's next. Second, the platform itself is being made more legible to large operators: naming conventions, threshold alerts, and reconnect-in-place auth all target customers running Lytics at scale rather than acquiring net-new ones.
Expect the next quarter to bring more zero-copy/streaming export jobs patterned after the Salesforce Data Cloud blueprint (Snowflake or Databricks are the obvious next targets), plus additional governance features — likely per-team audience permissions or audit-log enhancements — as the natural follow-on to naming conventions.
See more alternatives to Senja →
See more alternatives to Lytics →