What it sells
iMessage infrastructure for business
Business model breakdown
Buyer: who owns the budget?
UnverifiedProduct, growth or engineering lead at companies that message customers at scale (real estate, delivery, services); developers integrating via API.
Trigger: what makes them buy now?
SMS is carrier-filtered and visibly automated; customers want higher open/reply rates on iMessage (example: Getcho moving delivery notifications from SMS, onboarded in about 15 minutes).
Workflow: what inputs become what output?
Developers send iMessage threads via REST API and webhooks (blue-bubble messages, group threads, attachments, read receipts), with SMS/RCS fallback, then sync events to CRM or AI agents.
Economics: what it saves and how it charges
UnverifiedInfrastructure/API vendor; pricing not published, likely usage or per-sender based.
Distribution: how it reaches customers
Sales-led: "Book a Call" with a 20-minute kickoff; API docs and case studies; Chert handles integration during onboarding.
Funding history and coverage
| Round date | Stage | Amount | Investors | Source |
|---|---|---|---|---|
| — | Y Combinator Spring 2026 | — | Y Combinator | ycombinator.com |
Profiles summarize public reporting and company websites. Business-model notes are MaxBC's reading of that material, not confirmed facts; unknowns are left blank rather than guessed. Updated 2026-10-12.