Cover
B2B SaaS for the supply side. Consumer marketplace for the demand side. AI-native, on the same surface.
Telegram is the focus. Deepest distribution, native economy (Stars · TON · Gifts · partner programs), and the wave is right now — Durov back to TON, Functions / agentic-dev launch, AI-coding tools delivering builders.
The framing «messenger / superapp ecosystem with native mini-apps» is structural — same builder problems exist anywhere this category exists. We expand through the creators we already onboard, not by re-pitching new platforms (slide 09).
Audience
Each creator ships an app for the few hundred who think like them. Multiplied — bottom-up scale that no top-down platform can reach.
The instinct is to imagine a Telegram-app builder as a vibe-coder or a crypto founder. That's outdated. The wave underneath is any expert who serves a niche community — small-business operator, teacher, vet, fitness coach, hobbyist, niche professional. Each of them carries authority and pull within their circle.
The math is bottom-up: 1 creator × 100-1K followers × 100K-1M creators ≈ tens of millions of end-users. Top-down platforms can't reach these niches — by definition, the niches are too small individually. We don't try to reach them; we equip the creators who already serve them.
«We don't go find the housewives. We give the one housewife who already runs that community the tools to ship her app — and her community follows.»
Status quo
Tools eat the budget. Marketing has nothing left. Without traction, no resources to iterate. Without iteration, no traction. The cycle starves itself.
Six stages, six chances to fail. The drop-off isn't only about technical skill — most happens at marketing (50 → 15 — services consumed the budget) and at iteration to PMF (15 → 3 — exhaustion + zero feedback signal kills the loop).
Hidden cost: TIME. Most builders are part-time. Weeks of stitching → can't afford another quarter to iterate. The system rewards capital + technical skill + idle time, not insight.
«The 100K-1M niche creators from slide 02 don't fail because their ideas are wrong. They never reach the cycle.»
Insight
The deeper play isn't $200 → $30 savings — it's where the saved $170 lands. Builders who consolidate onto Apps Pro keep an active marketing budget. We make that budget land on @appss-native channels: our influencer marketplace, App Store featured slots, partner programs, bounty pools.
This is why slide 05 has 5 revenue streams instead of 1. The SaaS subscription is the floor; the redirected marketing spend is what compounds. And the more apps shipped through us (slide 04 flywheel), the more marketing-budget volume runs through these channels.
«You're not paying for tools. You're paying for the app you create — and growing it through us.»
Product
$19-34/mo
App Store — Mini App in Telegram. ~5K apps in catalog, 6 languages, 5 regions. Native earn loop (Stars staking, partner programs, bounty pools) keeps users coming back daily.
Apps Pro — credit-based SaaS. Each block replaces a Western-stack equivalent (Mixpanel, Figma, Customer.io, Intercom, etc.). Market Research AI is the hero entry use-case driving current revenue.
The two share one backbone (platform-service · SDK · builder-api · TON · Stars) — which is why the next slide is the flywheel, not just «two products».
Compounding
Three loops compose: (1) Supply / Demand — more builders → more apps → more users → more demand. (2) Distribution exchange — founders amplify via our referral / vote tools and trade a share of their existing audience for new traffic. (3) Data network effect — more apps → richer market data → Market Research becomes the obvious entry tool → more builders.
Why founders accept the trade. Net-positive: more new users than they give up, plus they get $200-400/mo of tools bundled at ~$30/mo. Asymmetric in their favour.
«A pure SaaS doesn't have the App Store. A pure marketplace doesn't have Apps Pro. We have both — and they feed each other.»
Comparable
If one slice (vibe-code web apps) became a generational success, the whole cycle in a 1B-user ecosystem is structurally bigger.
Why Lovable matters as a yardstick: they hit massive ARR by automating one step (vibe-code → working web app). They didn't help with hosting, branding, marketing, support, iteration. The market still rewarded them generously — that's what one slice is worth.
Apps Pro covers all those slices — for Telegram, where the stack is more isolated AND has native monetisation primitives (Stars, TON, partner programs) that web doesn't. Lovable saved founders weeks of build-time. We save them months of build + the whole post-launch cycle.
«Lovable closed one slice. We close the cycle. Same wave, larger surface, native monetisation.»
Expansion
Influencers don't live on one platform. As messenger / superapp ecosystems mature mini-apps, we follow the creators we've already attracted. Not a re-launch — an extension.
Two structural reasons this expansion mechanism works without a big-bang launch:
The cost of expansion is roughly «add a monetisation adapter + onboard creators already in our pipeline», not «build a new growth stack from scratch».
«Lovable is web-only and that's their TAM. Apps Pro starts in Telegram, and the same creators take us elsewhere when those ecosystems are ready.»
Money
Two live. Two ready, awaiting volume. One structurally uncapped.
| # | Stream | State | Mechanic |
|---|---|---|---|
| 1 | Pro subscriptions | Live | Apps Pro credit-based SaaS, $19-34/mo |
| 2 | Partner-program commission | Live | Cut on CPA payouts in catalog apps |
| 3 | App Store traffic sales | Ready | Featured / promoted slots; awaits DAU |
| 4 | Influencer marketplace fee | In-flight | Productising ~50 onboarded influencers |
| 5 | Portfolio apps | ∞ Uncapped | Notspy / Cover Food / VPN — owned directly |
Streams 1-2 underwrite the floor. Streams 3-4 unlock as App Store DAU and the in-Apps-Pro influencer marketplace ship. Stream 5 (portfolio) is what makes the upside uncapped — see slide 06.
Source: raw/business-model.md · decisions/2026-05-08-blogger-ops-model.md
Upside profile
SaaS floor. Marketplace compound. Portfolio ceiling.
| Model | Floor | Ceiling |
|---|---|---|
| Pure SaaS | Strong | Capped |
| Pure marketplace | Weak | High |
| Pure portfolio | Weak | Very high · variance |
| @appss | SaaS recurring | Uncapped via portfolio |
If a portfolio app does what Notspy did and goes 10x, we ride 10x — no commission ceiling. If two of them do it, we ride both. Meanwhile, Apps Pro recurring revenue protects the downside regardless.
Source: raw/business-model.md «asymmetric upside» section
Traction · Apps Pro
Off two viral Reels. Pre-funnel optimisation. Pre-marketplace productisation.
| Metric | Value |
|---|---|
| Visits (recent ~30d) | ~1 500 |
| Sign-ups | ~370 |
| Pro purchases | ~13 |
| Daily Pro purchases | ~3 / day baseline |
| ASP per purchase | $6-17 |
| Hero use-case | Market Research AI |
| Pricing model | Credit-based, shipped 2026-05-08 |
Numbers reflect the funnel before the credit-based pricing shipped. The next viral push hits a different funnel and is expected to convert better. Validation here is trajectory + the new pricing match.
Traction · Notspy proof point
Telegram premium-only limit lifted on 2026-05-08. Whole user base can now configure → expecting 2-3× revenue.
The 2026-05-08 Telegram update lifting Notspy's premium-only constraint is a structural unlock, not a marketing event. The bottleneck (only Premium users could configure → only ~5% of registered) just disappeared.
Validation arc: if Apps Pro can power Notspy through this transition, it can power any portfolio company's app through similar structural shifts.
Traction · Inbound flywheel
The 50 onboarded names are relationship capital — defensible. Standardised terms create switching cost. The marketplace, once shipped, becomes the network-effect lock.
Why now
Investor read: «institutional belief in TON came back; marketing budgets unfreeze; we're early on the curve».
Why now
init_data, Stars, channel distribution.Narratives align without competing — Telegram amplifies the platform, Apps Pro captures the gap.
Why now
Russia · China · Iran. Three different displacement attempts. Telegram retained dominance in all three. Closes the «what if a region blocks Telegram» objection in one slide.
The right framing is resilience as a moat: in regions where Telegram has dominance, alternative messengers and government-backed displacements have repeatedly failed to capture share. This is not just «Russia is fine» — it's the structural durability of the audience layer we sit on.
If Russia escalates to full infrastructure block, exposure increases. Other regions (CIS-non-RU, India, SEA, Africa, global English) absorb risk.
Team
Hiring philosophy: cut fast when revenue/spend is tight; avoid «monkey-job» roles that don't surface founder-level pain; promote direct-mandate ownership.
Ask
| Item | Value |
|---|---|
| Stage | Early seed |
| Round size | [TBD — Mark] |
| Valuation | [TBD] |
| Lead targets | [TBD] |
Use of funds
Looking for investors who get Telegram-native, the asymmetric-upside structure, and want to be early on the macro curve.