Reception

reception.sh· Customer Support

Does Reception have a moat?

No.

24/100 · Moatless

“An in-app chat SDK with a shared inbox takes a couple of weeks to build. What protects it is Frederick James's 18k followers among indie iOS devs.”

Code to copy

2 weeks

Moat to cross

3 months

Market

A few rivals

Share on X

Moat depth

MoatlessShallowReal

Verified revenueMRR $742Last 30 days $1,485All time $1.5kFounded 2026TrustMRR

01/The verdict

A native in-app support chat SDK for iOS apps (Swift, React Native, Expo) with an AI auto-reply, review prompts and in-chat plan upsells. Indie iOS app developers pay $25 a month.

Reception is a polished, narrowly focused SDK: native chat UI, one inbox, Telegram relay, AI answers from docs, and RevenueCat, Superwall and Adapty context. A capable builder with coding agents could rebuild all of it in weeks. The only real advantage is distribution. Frederick James has about 18k X followers, builds in public in the indie iOS 'appmaxxing' scene and sells to that same crowd. That is shallow, and with 32 subscriptions and $767 MRR there is no network, data or lock-in yet.

02/3 moats

Founder brand

Shallow

Time won't do it

Frederick James has about 18,082 X followers and posts iOS growth playbooks to indie app makers, the exact buyers. His posts include $1.5k MRR in 34 days, a $25k acquisition offer and work on Clavicular's top-10 app. The launch tweet and the appmaxxing community likely drove most of its first 39 apps.

To cross it: Build an audience among indie iOS devs, or partner with a larger creator in the same scene. A personal following can't be bought on a schedule.

Integrations

Shallow

~2 mo to cross

It reads subscriber context from RevenueCat, Superwall and Adapty, can switch plans inside the chat, and ships Swift and React Native/Expo SDKs. Pushes go through APNs, and replies can come from Telegram.

To cross it: Wire up the same three subscription SDKs and the Telegram bot API. Each is a public API with no approval process.

Switching costs

Shallow

~1 mo to cross

Customers embed the SDK in their app binary, so leaving means a code change plus an App Store update, and they lose their chat history.

To cross it: Offer a one-prompt migration and import of past conversations, so swapping SDKs takes an afternoon.

03/The gap

Easy to copy

The native chat UI, theming and remote config are standard SwiftUI work.
AI replies drawn from the customer's docs are a commodity RAG feature.
Telegram forwarding, a multi-app inbox and auto-detected device language are each a few days of work.
Review prompts and discount offers are deep links to the App Store and to paywall SDKs, with no gatekeeper.

How you'd go after it

Undercut at $9 a month, or offer a free tier up to N conversations. Indie devs are very price sensitive.
Ship Android and Flutter support, since Reception is iOS only.
Partner with RevenueCat, Superwall or Adapty, or with a big indie-app YouTuber, to become the default support add-on in their ecosystem.
Release an open-source, self-hostable version for indie devs who would rather not pay a monthly fee.

04/Build against it?

Only with an edge

The market is small: indie iOS devs paying $25 a month, with big players like Intercom and Crisp above them. Only go after it if you already have reach among indie app makers or a distribution deal with a paywall or subscription platform.

Already selling this:IntercomCrispHelpshiftZendesk Messaging SDKChatwootInstabug

05/Receipts

Checked 1h ago by Claude Opus 5.5 on high effort, with web search. Confidence: medium.