Superhuman
Superhuman bets on agent-operable email: a Codex plugin now drives the inbox.
A side-by-side editorial comparison of Spike and WATI — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Spike | WATI |
|---|---|---|
| Sector | Comms | Comms |
| Velocity score | 0.0 | 7.5 |
| Sparks · 30d | 0 | 0 |
| Top themes | incident management, on-call, alerting, integrations | content-marketing, whatsapp-business, ai-agents, mcp |
| Last editorial update | 1mo ago | 2d ago |
| Website | — | Visit → |
Spike grinds out incident-management ergonomics — number-comparison alerts, more integrations, broader AWS auto-resolution.
Spike is an incident management and on-call platform competing in PagerDuty's category. The recent quarter's releases are uniformly incremental — numeric comparison operators in Alert Rules, broader AWS auto-resolution coverage (now including SNS), Jenkins and NinjaOne integrations, an inbound Jira trigger, day-of-week alert routing, admin-managed Out of Office. Each release shaves friction from a specific operator workflow without changing what Spike fundamentally is.
WATI's feed is WhatsApp-commerce SEO content; its AI agent and MCP are referenced, not shipped here.
WATI's crawled feed is its marketing blog — WhatsApp-for-Shopify guides, seasonal message templates, competitive explainers (Meta Business Agent), and agent how-tos. Product capabilities surface only as topics: the Wati MCP server (build and audit agents from Claude), the "Astra" AI agent, and native WhatsApp voice calling. None are release notes.
Spike is an incident management and on-call platform competing in PagerDuty's category. The recent quarter's releases are uniformly incremental — numeric comparison operators in Alert Rules, broader AWS auto-resolution coverage (now including SNS), Jenkins and NinjaOne integrations, an inbound Jira trigger, day-of-week alert routing, admin-managed Out of Office. Each release shaves friction from a specific operator workflow without changing what Spike fundamentally is.
Spike's competitive strategy reads as 'be more methodical about the long tail of operator paper-cuts.' The integration cadence is high — Jenkins, NinjaOne, Jira inbound, calendar links — the alert rule grammar keeps expanding (comparison operators, day-of-week conditions), and the on-call surface keeps gaining flexibility (gaps, scheduled layers, admin-managed OOO). No directional moves, but very consistent incremental velocity.
Expect more integration additions in the same vein (CI/CD tools, IT monitoring vendors), continued alert rule grammar expansion (time-of-day conditions and frequency-based thresholds are the obvious next axes), and more team-management features around on-call rotations.
WATI's crawled feed is its marketing blog — WhatsApp-for-Shopify guides, seasonal message templates, competitive explainers (Meta Business Agent), and agent how-tos. Product capabilities surface only as topics: the Wati MCP server (build and audit agents from Claude), the "Astra" AI agent, and native WhatsApp voice calling. None are release notes.
The content bet is squarely on AI agents over WhatsApp — building and auditing agents from Claude via MCP, CRM-connected agent pipelines, and native voice. WATI is marketing itself as the WhatsApp-API layer beneath AI assistants, but because this feed is SEO, it tracks content cadence rather than shipped features.
Expect more agent- and MCP-centric content; confirming actual Astra, MCP, or voice releases will need WATI's product changelog instead of this blog.
Other Comms products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Spike or WATI.
Superhuman bets on agent-operable email: a Codex plugin now drives the inbox.
Pumble's feed is SEO comparison content, not a changelog — no shipped product changes to read here.
Twilio fills out EU data residency, RBAC, and unified messaging APIs
MirrorFly's feed is comparison-SEO listicles, not a product changelog
Telnyx is racing to be the voice-AI layer for autonomous agents, model by model
Mux pushes deeper into AI video workflows and engagement analytics as Robots starts billing.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. WATI is currently shipping more aggressively (velocity 7.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. WATI is currently shipping more aggressively (velocity 7.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Comms products to evaluate alongside.
Top Spike alternatives in Comms are ranked by recent ship velocity. Browse the "Spike alternatives" section above for the current picks, or visit /alternatives/spike-sh for the full list with editorial commentary on each.
Top WATI alternatives in Comms are ranked by recent ship velocity. Browse the "WATI alternatives" section above for the current picks, or visit /alternatives/wati for the full list with editorial commentary on each.