The mass adoption of personal software

Apps are becoming user generated content. AI now writes most of the code, so one person can ship a working app in a weekend, the way the phone camera once turned everyone into a video producer. The hard part has moved from building the app to everything after it.

We build that missing layer: tools to create, distribute, manage and monetize apps at the speed people produce TikToks and Reels. Creators build native and mini apps in each platform's own stack, deploy on our managed cloud, and reach users through @appss, a store driven by a social graph rather than search.

We are an ex-Telegram team, and we hit these problems building apps ourselves. Notspy, a portfolio app on our own stack, runs profitably with 115K real users. The tooling started as what we needed to operate; we packaged it so any creator can run the same playbook.

Structure follows what investors ask for: the pain of a concrete person and how they cope today (Sequoia), which of Kevin Hale's attributes make it worth solving (popular, growing, expensive for the first; mandatory, frequent, expensive for the second), and proof instead of opinion. On the slide the proof is real X posts from builders, shown as cards; the attributes are spoken.

Problem 1, spoken: popular and growing (anyone can start now, and most do; 291 build requests from 248 people on appss.pro in ten days, 17-27 Sep 2026), expensive (the remainder still costs a team). Posts: @HashamBuilds 25 Sep 2026 "every tiny feature has a database, a login flow, a bug, three edge cases and a documentation page"; @basedlayer 25 Aug 2026 "building good software is incredibly hard… maintenance, databases, server infrastructure, security"; @akarshjha03 3 Sep 2026 "Building it wasn't the hard part. Power, storage, backups, updates, database history…"; @leojrr 17 Mar 2025, 6K likes, "maxed out usage on api keys, people bypassing the subscription… I'm not technical".

Problem 2, spoken: mandatory and frequent (every app, every launch), expensive (attention is bought and stops with the spend). Posts: @caelum0x42 15 Sep 2026 "The products are done. Distribution is not. Zero users."; @WillLovesNoCode 25 Sep 2026 "Month nine… fifth vibecoded SaaS. Still stuck at zero users. Every launch drives a spike in traffic, then dies off fast"; @XTeamPal 27 Sep 2026 "Day 10: (zero users). Launched on product hunt, hacker news, indie hackers…"; @shivamkumarlogs 22 Sep 2026 "build → ship → 0 users → build a completely different app to avoid doing sales → repeat"; @Jadu100x 22 Sep 2026 "Harder than building an app: get noticed. Paid ads, SEO, socials, events." Source data: public/deck/assets/x-posts/posts.json (fetched 28 Sep 2026).

This slide answers problem 1: making a product people pay for is hard. A product is a chain of five parts: compute, data and operations, actions (what the app does for you: book, pay, map, translate, scrape), the interface, the people. Today one company has to own every part before anyone pays; everyone else picks between being a developer or making a toy.

With @appss the creator does only the last two: the interface and their people. Everything before it already exists (85K+ MCPs, connectors, data sources) and plugs in as actions. Every paid use is settled along the chain, so nobody has to build the whole chain to get paid for their part. The logic a creator writes becomes an action too, and the next person builds on it.

Spoken line: YouTube made the unit a video, Uber a ride, Airbnb a room. Software's unit was still the company. Naming note (Mark, 2026-09-28): the third box is "small jobs to be done"; not "skills". Chosen: actions (Mark, 2026-09-28). Rejected: skills, capabilities.

2026-09-30 (Mark): six steps, two lines each, no "Step N" labels. Heights 104/140/176/212/248 and Verify identity 340 (first step doubled, last one clearly taller).

Answers problem 2: it's hard to get users. The ladder is what an app asks of a person before it does anything for them. Step 0: nothing, it opens in the chat they are already in, already signed in. Step 1: open a link. Step 2: create an account. Step 3: install. Step 4: verify identity. Every step loses most of the people who reached it.

Content has lived at step 0 since 2010: a video, a post, a clip. Software almost never has. Forms, link-in-bio and web builders live at step 1. SaaS and marketplaces at step 2. Native apps and extensions at step 3. Fintech at step 4. The logos on the slide are examples of who lives on each step today, not competitors.

Spoken, not written: with @appss the same app exists at every step and opens at the bottom (iMessage, WhatsApp, Telegram, ChatGPT, Reddit, Playables), climbs to web, then to iOS, Android, Mac, widgets and push only after use; payouts sit at step 4 through @appss Pro.

Rebuilt 2026-09-30 (Mark): title at the common size, lead about the perks of living inside a platform (signed in, push channel, one-tap sharing, no install), perk chips, five phones (iMessage, WhatsApp, TikTok, YouTube, Reddit) and the "where mini apps already live" list. The iMessage phone is a real screenshot (GamePigeon in iMessage, 2026-09-30); the other four are frames from our own promo videos.

Nine of the world's ten largest apps now host an app surface: Instant Games on Facebook, Flows in WhatsApp, Playables on YouTube, Minis on TikTok, Mini Programs in WeChat, Mini Apps in Telegram, Devvit apps on Reddit. Only X has none. Distribution is moving inside the apps people already open.

We checked the ceiling ourselves, on real devices in China this August: ten platforms, hands on. The top four apps there, WeChat, Alipay, Taobao and Douyin, are all mini-app platforms; WeChat's mini-programs alone reach 962M monthly users. Where a claimed host failed our check, like Amap or Meituan, we cut it.

The second table has a pattern: almost every significant 2026 update is about AI agents driving mini-apps. WeChat opened its mini-programs to agents in June. Alipay converted 10,000+ services into agent skills by August. Meta shipped Business Agent, UnionPay an agentic payments protocol. Mini-apps are becoming the tools agents call.

Rebuilt 2026-09-30 (Mark): one horizontal composition instead of three squares. Left column (Mark, 2026-09-30): caption on top with "@appss · connectors", one wrapped row of chips: link icon "500+", Gmail, Calendar, Drive, Maps, Notion, then the MCP chip with ChatGPT / Claude / Grok / Gemini icons; no arrows; then the ChatGPT phone. Center: the mobile app in an iPhone frame, caption on top. Right: @appss Pro caption and a smaller laptop with a real screenshot (Cloud page, Snake Game, 28 Sep 2026, file pro-cloud-2026-09-28.jpg?v=0930f) bleeding off the right and bottom edges.

Center (2026-09-30): two thin-bezel iPhone frames, the native app in front (lower) and the same screen in mobile Chrome behind it (higher) with an iOS-style address bar (our icon + appss.com) and the status bar taken from the app screenshot, the app phone covering most of it; iOS / Android / web icons sit next to the @appss logo in the column caption; hero screen from the Claude Design concept mockup (file app-hero-screen-2026-09-30.jpg?v=0930c), shown in full; caption above it. The ChatGPT screen is an HTML mock of the iOS ChatGPT app (Mark, 2026-09-30: Jira cards in ChatGPT did not render, so the real screenshot was impossible; the card design follows the Claude/Atlassian card): request "Is there any app ideas from my context?", @appss MCP app answers with three app ideas from calendar, mail and chats. Ideas are illustrative examples, not real user data.

@appss Pro is for the ones who want to run it as a business: code access on our own runtime, analytics and push chains, credits and payouts, market research and keywords. Same app, professional tooling. Own runtime, iMessage and MCP are also roadmap items to show on the roadmap slide.

Added 2026-10-01 (Mark): after the product slide, before the four stages, a slide that lists every source of actions we maintain (MCP servers, connectors, data sources, payments and identity, creators' own actions published on @appss Pro) and every platform we ship to (the same list as the app-stores slide plus web, iOS, Android and Mac). Counts 85K+ and 500+ are the ones already used on the hero and product slides. Generator: scripts/deck_v3_slide_actions.py.

2026-09-30 (Mark): Yourself column is a single iOS-style push card drawn in HTML (no phone, no wallpaper, per Mark), with a second card peeking below as the stack; six source circles above with threads ending just above the card. Push text is illustrative.

The combined solution to both problems, told as the life of one app. Stage 1, yourself: the person makes the app for their own use case and uses it daily in the @appss app on their phone. Stage 2, their people: they share it to involve friends or let them use it, for example sending a friend the contact in Telegram or iMessage so the friend enters their part; it opens inside the chat, no install, no sign-up. Stage 3, it spreads: a friend who saw it working recommends it to others; the app was shared only to get some data in, and now it travels chat to chat and group to group. Stage 4, keep them: once there is a crowd, the person builds native apps on top of it for retention and monetization: web, iOS, Android, Mac, widgets, push.

The context block on the left (Mark, 2026-09-30): via MCP we sit in the person's mail, calendar and the assistants they already use (ChatGPT, Claude, Grok), see what they actually do, and suggest which real use cases are worth packaging into an app. So stage 1 usually starts from a suggestion, not a blank page.

Building an app is now the cheap part. A coding agent gets you a working mini-app in days; that is the five percent. What stops creators is everything after: knowing what to build, getting installs, keeping users, taking payments. The build step is a commodity. The rest is the product.

@appss Pro packages that rest as one workflow: 16 tools across Research, Build, Distribute and Monetize, from Market Research and App Remix through to Channel Attribution and Push Management, under one subscription. Creators do not have the budget to glue ten standalone tools together, so we sell the workflow, not the parts.

Every capability is also an AI action surface. Plug Claude or ChatGPT in and drive any tool from chat: track a competitor, send a push to a churned cohort, generate a referral landing. Work front-loads in research and build, then drops, while users and revenue keep compounding on the same stack.

Native app stores reward consolidation. A ranked chart pushes each category toward one winner: one booking app takes the downloads and the other 200 fade. UGC platforms reward the opposite. YouTube does not have one cooking channel, it has millions, each personal to its creator. App supply is starting to behave the same way.

The atomic unit is the niche, not the category. A manicurist builds the booking app she actually wants, charges her clients five dollars a month, and is profitable at 100 to 1,000 users. Multiply that across masters, shops, and communities and you get 20,000 apps where a native store allows one.

So we built our store as a long-tail catalog, not a top-50 chart. Telegram alone already carries 8,000-plus of these apps, each with a small, committed audience. We do not need one app to win a category; we need tens of thousands, each good for its own people.

We size the market from the buyer out. Creators spend from a $480B economy: Goldman Sachs put creator-economy spend at $250B in 2024, roughly doubling to $480B by 2027. That spend comes from 200-300M creators worldwide, per Linktree and Adobe, about 50M of them professional.

Our serviceable market is the creator tools budget, summed from named analyst segments: AI and no-code app platforms at $45B growing to $102B by 2030 (Grand View Research), social-media management at $36B (Grand View), monetization platforms at $14B and creator infrastructure at $25-38B (The Business Research Company). The sum is $120-133B; segments overlap, so we quote $100B+.

We target $1B+ a year: 1% of that budget top-down, cross-checked bottom-up at roughly 500K paying creators worth ~$2K each, which is 0.2% of the creator base. China already proves the model monetizes: WeChat mini-programs move over $1T a year (Tencent, Q3 2024).

2026-10-01 (Mark): rebuilt as four loose columns in the style of the reworked slides: group title, logo chips with names, one plain text. Order per Mark: personal agents (Muse, Grok Bot, ChatGPT Dots), coding agents (Codex, Claude Code, Cursor), web and mobile builders (Lovable, Replit, v0, Rork, Newly), single-purpose tools; the Wabi row sits under the lead. All texts (lead, Wabi row, four columns) were written on 2026-10-01 through a council: research agents (Wabi facts, X narratives, single-purpose tools, VC critique), then per-text tests by tone, investor and fact agents plus Grok over the xAI API with live X search; see planning/competitors-slide-copy-2026-10-01.md. Facts on the slide: Meta transaction fee (Zuckerberg, Connect, 23 Sep 2026; Meta president, 30 Sep 2026); Wabi 2.0 messenger, invite-only (28 Sep 2026); Google Forms is free, the other three charge. No bold in captions. Generator: scripts/deck_v3_slide_competitors.py.

Wabi took the words "personal software" but only inside their own app: their surface, their runtime, vendor lock. We look at it from the market: the app has to open where the person's people already are.

Lovable, Bolt, v0, Rork are built for someone who already knows they want a web app or a mobile app, and their money went into onboarding that professional user. Our person does not know yet and does not need to; they sell a combination of actions plus an interface. To copy us these builders would have to change their end user, and by then we are the default.

ChatGPT, Claude and Gemini app tools keep the app inside their own chat. None of them will ship to a rival surface, so cross-platform is a lane they leave empty. We stay one step ahead on every new host and run on their tools as actions.

Linktree, Calendly, Typeform, Luma and similar single-purpose tools: a static function on their domain with their data. With @appss the same thing is the person's own software, opens where their people are, and earns among them. Needs a separate workshop for the full list.

The request is real: "создай приложение Делим расходы в поездке", typed into the appss.pro builder on 27 September 2026 (source: builder_idea_submitted events of the @appss Pro app, pulled via MCP on 28 September; 291 requests from 248 people between 17 and 27 September). Other recurring requests in the same ten days: booking for nail and hair salons and detailing studios, habit and expense trackers, "everyone marks whether they come to the court and when", anonymous compliments to friends, daily tarot with friends.

The ideal path for this person: an agent in their own trip chat on WhatsApp or iMessage, made for their own trip first; a fuller Telegram mini app with receipts, currencies and settlement; a Reddit interactive post that runs inside r/travel threads where trip money is already discussed, which is where it spreads; then a native app with widget and push for the ones who come back, with a paid tier for organizers.

The numbers (150 people, 20 paying $19 a month, $380 a month) are the target scenario Mark set for this case, not actuals. Every paid use is split per use across the actions the app calls (FX rates, receipt OCR, payments), @appss keeps 15%, the maker keeps the rest. The next slide shows real cases on Telegram.

Source: builder_message_sent and builder_idea_submitted events of the appssprobot analytics app (text recorded from 2026-09-17). Clustering and verbatim prompts: planning/builder-ideas-2026-10-07/builder_prompts_clusters.md. Chips paraphrase the prompt in English; the city is the creator's time zone city where it is known. Per Mark (2026-10-07) Russia and Iran are not shown; Russian-origin prompts are attributed to Ukraine, Kazakhstan, Uzbekistan or Poland. The map is an illustration, labelled as such on the slide.

NotSpy recovers deleted and edited Telegram messages. Over the last three months it reached 715K users and $9.5K in MRR, with 2.4M views a month. It is the largest app on the platform, and it grew inside Telegram, where the audience already was.

KAVA Food serves recipes with calories and macros per portion. Last month it counted 11.8K users, $540 in MRR, and 940K views. A small, focused utility that a creator could not have justified as a native app; as a mini-app the economics work.

abcdVPN sells one-tap VPN subscriptions inside Telegram. Last month, 300 users produced $1,200 in MRR. Three hundred users is not a big number, and that is the point: with payments native to the surface, an app this small is already a business.

We brought the platform online piece by piece. The Analytics SDK shipped in April and has since counted 882K end-users served across creators' apps. Market Research followed in May. In total, the AI tools have handled 11.2K actions across 2,181 creator accounts, and 850 apps built elsewhere came in to list with us.

The AI Builder was the last piece. It launched on July 31 and closed the loop: a creator can now build, publish, measure, and monetize in one place. The response was immediate. In under four weeks, creators built 394 apps from scratch in the Builder.

Monetization switched on last. 123 users now pay, at about $115 average spend. The base is small and recent, and we treat these numbers as groundwork: each metric started at zero when its tool shipped, and August is the first month the complete loop has been running.

We do not rent distribution. We run 44 owned influencer accounts across Instagram, TikTok, YouTube and Telegram, with 78K followers and 46.7M views all time. The largest single account has done 15.6M views. Every one of them was grown in house, by our own team, on our own content.

These accounts already work as a channel. They route audience into our own apps and monetize them, so the engine pays for itself while it proves the loop. Track Socials, Influencer Market, Referral System and Channel Attribution inside @appss Pro are the same tooling we use ourselves.

The next step is the market. The same accounts, plus the community around them, will push creators' apps built on our platform. Ad budgets buy reach once. Owned accounts compound, and they pump the market we take a cut of.

The base is the subscription. Each plan includes a monthly credit budget of around 3,000 credits, and every tool draws it down: research queries, builds, remixes, pushes. AI tools are priced at cost times two, infra and ops tools at three to five, so revenue tracks real usage and margin grows with scale.

The second stream is aggregated traffic. Apps built on the platform funnel their audience through the @appss store, and that Store MAU becomes inventory we sell per impression and per outcome, to Pro creators and external advertisers. More apps means more traffic to sell; the first stream feeds the second.

The third is partner flows. When creators and influencers make deals through the platform, we take a cut of each one: a fee per Influencer Market order, a percentage of referral-program budgets. Each stream raises the others, so a marketing dollar spent acquiring one subscriber ends up working across all three.

Twelve of the sixteen tools are live today. APIs & LLMs and the Influencer Market ship in September; Designer Studio and Support close the set in October. From that point the product surface is complete, and the work shifts entirely to distribution. That is the whole game for the next two quarters.

Distribution runs platform by platform. Reddit and WhatsApp in September; YouTube, TikTok and Discord in October; Instagram, Messenger, Facebook and iMessage in November. WeChat, LINE and Zalo follow in December, with Alipay, Douyin and Weibo through the first quarter. The West first, then China, in the order access opens.

The numbers are outputs of a loop, not a forecast. Each platform adds creators, each app becomes a template others remix, and remixes carry into the next platform. Run at this cadence, that loop is built to produce one million mini-apps by year-end and three million by March. Targets, not promises.

We are operators, not observers. Before building the platform we shipped our own apps on the Telegram substrate; Notspy alone runs at 115K users. The stack we sell is the stack we use daily, so every tool exists because one of our own apps needed it first.

The team fits the problem three ways. Mark, ex-Telegram team and TON Foundation, runs product and positioning as an operator-founder. Anton has generated billions of organic views on Instagram, TikTok and YouTube and recruits creators in their own language. Max built at Telegram Mini Apps depth and owns the platform.

This market is won from inside the ecosystems, and our 15+ teammates already work there: UGC operators, growth engineers and mini-app developers embedded in Instagram, Telegram, TikTok and Meta. @loomdart, co-founder and early backer, has been on this thesis since day one.