Pinnacle logo

Pinnacle

API & SDK for RCS (the next-generation of texting)

Summer 2024active2024Website
Developer ToolsB2BSalesE-commerceSMS
Sponsored
Documenso logo

Documenso

Open source e-signing

The open source DocuSign alternative. Beautiful, modern, and built for developers.

Learn more →
?

Your Company Here

Sponsor slot available

Want to be listed as a sponsor? Reach thousands of founders and developers.

Report from 10 months ago

What do they actually do

Pinnacle provides an API and SDKs (Python, TypeScript, Ruby) that let developers send interactive RCS messages with automatic fallback to SMS/MMS. Teams use REST endpoints to compose messages (cards, buttons, quick replies for RCS; text/media for SMS/MMS) and can test on a free sandbox agent before going live Docs introduction, RCS quickstart.

It also handles the carrier and compliance steps needed for production: brand and campaign registration (10DLC/toll‑free), number purchasing and attaching numbers to campaigns, plus webhooks and status endpoints for delivery and replies 10DLC campaigns, Messaging overview. Public pricing lists per‑message rates (e.g., RCS text ~$0.02) and the site highlights faster RCS agent provisioning as a selling point Pinnacle homepage.

Who are their target customer(s)

  • Product and backend developers replacing or augmenting SMS with richer flows: They need an easy way to build, test, and ship RCS without re‑architecting their backend and want SMS/MMS fallback when RCS isn’t available.
  • Growth/marketing teams running high‑volume campaigns: They deal with carrier paperwork, approvals, and deliverability risk; they want better engagement than plain SMS without operational overhead.
  • Customer support and operations teams: They need reliable delivery status and a single place to capture replies; failures and siloed replies make it hard to support users.
  • Regulated or appointment‑driven businesses (e.g., healthcare, finance): They must meet compliance rules and ensure time‑sensitive messages are approved and delivered; carrier approvals and sender identity setup are bottlenecks.
  • Small engineering teams at startups: They lack in‑house telecom expertise and are slowed by complex carrier setups; they want quick prototypes and automated onboarding.

How would they acquire their first 10, 50, and 100 customers

  • First 10: Run targeted pilots via founder networks (e.g., YC alumni already sending SMS), offering a free sandbox agent and hands‑on help with brand/campaign submission to prove out RCS quickly.
  • First 50: Drive self‑serve adoption with SDKs, quickstarts, and sample apps; seed developer communities and GitHub/VSCode tooling to funnel signups to the sandbox and simple API keys.
  • First 100: Package compliance+deliverability as a service for specific verticals; add agency/CRM/support integrations and use early case studies plus transparent per‑message pricing to speed procurement.

What is the rough total addressable market

Top-down context:

Business (A2P) messaging is a tens‑of‑billions market globally, with estimates around ~$50B+ and higher depending on scope Juniper, Grand View Research. RCS is a smaller but fast‑growing slice, currently low billions and projected to become a material share of operator business‑messaging revenue GMI, Juniper.

Bottom-up calculation:

Illustratively, if 10,000 businesses adopt an RCS‑capable API over the next few years and each sends ~1M messages/year at a ~$0.02 blended API price, that implies ~$200M/year in programmable RCS messaging revenue, before counting SMS fallback and compliance services. This scales with adoption rates, message volumes, and blended pricing Pinnacle pricing.

Assumptions:

  • ~10,000 addressable API‑using businesses adopt RCS messaging in 3–5 years.
  • Average 1M outbound messages per account per year across RCS/SMS fallback.
  • Blended per‑message API revenue of ~$0.02, consistent with listed unit pricing.

Who are some of their notable competitors

  • Twilio: Broad communications API with RCS, SMS/MMS, and analytics; strong global reach and multi‑channel tooling for enterprises and developers.
  • Sinch: Telecom‑scale CPaaS offering RCS via APIs and managed agent/registration; focuses on enterprise compliance and global operator relationships.
  • Infobip: Omnichannel platform with RCS, campaign tools, and contact‑center integrations; suited to large marketing and support teams.
  • Vonage (Nexmo): Messages API supporting RCS alongside SMS/WhatsApp; familiar developer docs and webhook flows for multi‑channel messaging.
  • MessageBird (Bird): Omnichannel tooling with visual campaign builders and Google RCS support; targets marketers with low‑code workflows and templates.