Overview
Save up to 95% on real-time experiences. Community-powered
AutomateSleeping Giant
dTelecom
Save up to 95% on real-time experiences. Community-powered
Paid
Compare Alternatives
dTelecom
Paid
Enjoying this? Get one like it in your inbox each morning.
one email a day · unsubscribe in two clicks · no third-party tracking
Stork Quadrant
Sleeping Giant· 39/100
Has a real moat but invisible to agents. Add an MCP and you'd climb.
“dTelecom owns real infrastructure moats: physical nodes in a peer-to-peer network, regulatory compliance for telecom services, and coordination across distributed participants. An LLM can't replace the actual network that routes calls or the legal framework that lets them operate as a telecom. The defensibility is high because the core value is the network itself, not advice about networks.”
Defensibility · 66/100
- Physical-world coupling
- Regulatory moat
- Network liquidity
- Proprietary refreshing data
- High-trust catastrophic workflows
- Multi-party coordination
- Brand / community / taste
An LLM alone could replace
- Generate pricing comparisons between telecom providers
- Create documentation or guides on VoIP/WebRTC setup
- Explain telecom cost optimization strategies
- Draft marketing copy about communication savings
Agent-Readiness · 5/100
- Verified MCP
- Listed on agent surfaces
- Usage-based pricing
- Headless agent auth
- Public OpenAPI
- Active changelog
- llms.txt— https://dtelecom.org/llms.txt
How to defend
Double down on network effects — make it easier for developers to plug in as nodes and for end-users to join. Expand into adjacent regulated services (SMS, video) where the network becomes stickier and regulatory moats compound.
- Ship an MCP server and list it on Stork — biggest single point gain (+25).
- Get listed in the Anthropic MCP registry, Cursor, or Claude Desktop (+20).
- Add a usage-based or per-call tier; per-seat-only pricing dies when agents replace seats (+15).
- Expose API-key auth with a self-serve sandbox tier; remove sales-call gates (+15).
- Publish an OpenAPI spec at /openapi.json or /.well-known/openapi (+10).