About the project
A long-term client came to us—a large online school (Airat Shakurov’s Yellow Club) that regularly runs education launches. Every cohort means many members, separate Telegram chats, clubs and a motivation system.
Infrastructure grew over time, different developers owned pieces of the stack—and critical access and automation failures started stacking up.
Client pain
Main problems:
- manual Telegram chat creation and setup per launch;
- unstable GetCourse + SaleBot + custom Python backend glue;
- lost paid purchases and broken access grants;
- people landed in the wrong communities—or got no access after payment;
- no state control—some users got stuck between automation steps;
- no community activity analytics;
- no VK support at all.
Support drowned, and member experience broke before any content.
The solution
We fully rebuilt access grants and community management. Instead of scattered processes—one system that automatically:
- creates Telegram chats for new launches;
- sets branding, topics and permissions;
- routes users into the right communities;
- controls access duration;
- syncs Telegram, VK, GetCourse and the internal backend.
Architecture
At the core—a Python backend and PostgreSQL stitching external services:
- GetCourse;
- SaleBot;
- Telegram User API and Bot API;
- VK API;
- admin panel;
- analytics.
All member actions go through one processing logic—cross-platform routing errors go away.
User journey
After payment the system knows the purchased product. Then the member:
- gets access to chats and materials for their plan;
- is auto-added to Telegram or VK depending on format;
- gets access without an admin;
- is auto-removed from private communities when the subscription ends.
The whole path runs without manual staff actions.
Key mechanics
We shipped:
- auto-create Telegram chats per launch;
- auto-setup of topics, branding and permissions;
- internal points for submitted videos;
- assignment moderation in admin;
- auto grant and revoke of access;
- subscription end control;
- fixes for legacy routing bugs;
- Telegram, VK, GetCourse and SaleBot sync;
- member activity analytics.
Telegram infrastructure and Mini App
The main focus is Telegram infrastructure automation. The system creates chats, configures them for the launch, routes members, tracks activity, manages access and subscription windows. Manual team work on every new launch nearly disappears.
On top—a product layer for members and operators: Mini App and marathon/club ops (captain chats, video intake, KPIs, “bought → assigned → joined” funnel).
Admin
For leadership and the team—a control panel to:
- read member activity;
- read chat stats;
- control point grants;
- see user distribution;
- analyze club renewals;
- find access problems fast.
Instead of constant manual checks—one monitoring surface.
Results and growth
After launch we achieved:
- fully automate Telegram chat creation;
- kill access-grant errors;
- remove Telegram / VK mix-ups;
- ship full VK support;
- automate subscription control and removals after access ends;
- cut support load significantly;
- give leadership clear club and activity analytics.
The product stays live: we add features, evolve the architecture and support the system for the school’s next products and processes.
