@appss · papers

← Back to papers

Positioning

Growth stack for Telegram builders

Investor / advisor · 2026-05-10

@appss is two products on one stack, a B2B SaaS for Telegram creators (supply) and a consumer marketplace where their apps live (demand). Each side feeds the other. The flywheel, not either product alone, is the moat.

@appss is the growth stack for Telegram builders. Externally, that's two products: Apps Pro, the paid creator toolkit (analytics, design, build, push, referral, market research), and @appss, the consumer Mini App where users discover and use creator-built apps. Internally, both products run on one shared stack of twelve horizontal capabilities. Investors don't have to pick which side they're betting on; the bet is the loop.

The two-product framing

Product Side What it is State
Apps Pro Supply (B2B SaaS) Creator dashboard. Replaces 5–7 separate tools. Live, paid
@appss Mini App Demand (consumer marketplace) Discovery, reviews, earn loop, ~5K apps in catalog Live, 6 languages, 5 regions

Both ship today. Both have paying users / active engagement. See Traction for the full surface and Products for the capabilities they share.

Why the loop is the moat

        more apps shipped via Apps Pro
                       ↓
          more apps in the @appss catalog
                       ↓
           more users using @appss
                       ↓
          more demand for Apps Pro
                       ↓
                    (loop)

Every creator who ships through Apps Pro adds inventory to the @appss catalog. Every new @appss user adds demand-side gravity for new creators. Either product alone is replicable. The two-sided loop, with twelve capabilities engineered together to feed it, is not.

Four insights outsiders miss

These are why a generic «analytics for Telegram» or «Telegram app store» pitch fails on first principles, and why we've built differently.

1. Telegram has its own economy

Stars, Gifts, NFTs, Telegram Premium, partner programs, bounty pools, in-bot subscriptions, Stars staking, Telegram is a self-contained value layer that interacts natively with TON. Not Western-style ad monetisation. Not App Store IAP. Not Stripe-style billing. A parallel economy with its own primitives. Most outsiders see «messenger with chats» and miss the substrate.

2. Existing analytics and growth tools don't speak Telegram

Mixpanel, Amplitude, AppsFlyer, Adjust, Mailchimp, Customer.io, OneSignal, none of them have native concepts for Stars, partner-program payouts, Mini App init_data, channel-driven distribution, bot-mediated UX. Founders building inside Telegram have to bend tools that weren't designed for the surface. Apps Pro was built native to Telegram primitives. We don't translate; we speak the language.

3. Telegram creators are missing one half

A creator inside Telegram is usually either technical (vibe-coder, ex-engineer) or distribution-heavy (channel-owner, influencer), rarely both. Technical creators don't know channel mechanics, gifts, or bounty loops. Distribution-heavy creators can't ship code. Neither has analytics that fit Telegram's metrics. Apps Pro closes this by being a stack, research, build, distribute, monetise, not a single tool.

4. Distribution doesn't work like Play Store

There is no ranked search, no platform-curated featured-app list, no SEO. Distribution in Telegram is bot- and channel-driven, influencer-amplified, gift- and bounty-incentivised, and Mini-App-portal-driven. A pitch that assumes App Store / Play Store mental models for Telegram is wrong on first principles.

See social graph fragmentation for the deeper structural reason this constrains everyone, and why our cross-ecosystem-as-default doctrine follows from it.

What @appss is not

  • Not a no-code platform, we serve vibe-coders and traditional engineers alongside no-code creators.
  • Not another analytics tool, analytics is one of twelve capabilities, not the product.
  • Not «Telegram's app store», singular, that's the demand-side half. The supply-side toolkit is the other half, and the combination is the bet.
  • Not a crypto / Web3 platform, TON and Stars are primitives we use; the audience is the wider creator class, not the crypto bubble.
  • Not an education company, Apps Pro Academy is a consequence of the stack, not the product itself.

Read next

  • Business model, the five revenue streams across both sides of the loop.
  • Why now, Telegram macro: Durov back in TON, Russia-block defanged, AI-coding wave, Mini Apps 2.0.
  • Social graph fragmentation, the structural constraint that forces our cross-ecosystem strategy.

For the underlying source documents, the formal positioning decision file, or the live Apps Pro / @appss product walkthroughs, email mark@engagelabs.org.