This is the story of how we built a production AI news aggregator on Telegram that pulls content from dozens of sources, delivers personalized news to thousands of users, and runs on lean infrastructure. No theoretical framework. No hypothetical scenarios. Real lessons from a real bot we built and operate.
AI news moves fast. Professionals following the space — developers, founders, researchers, investors — spend 30–60 minutes daily scanning multiple sources: tech blogs, research papers, social media accounts, newsletters, and aggregators. The signal-to-noise ratio is terrible. Most content is recycled, low-quality, or irrelevant to any given reader's interests.
The challenge: build a system that automatically aggregates content from diverse sources, filters for quality and relevance, categorizes by topic, and delivers a personalized digest to each subscriber via Telegram. It needs to work reliably, scale with the user base, and cost virtually nothing to operate.
The constraints we set:
We designed a three-stage pipeline: aggregate, enrich, deliver.
The bot pulls content from a diverse mix of RSS feeds, social media accounts, and curated publication lists. Each source has its own ingestion schedule based on how frequently it publishes. High-frequency sources get checked more often. Low-frequency sources get checked less often to avoid wasted processing.
Social media integration monitors specific accounts that consistently surface high-quality AI content. This isn't just link scraping — the system captures the context and commentary that makes social posts valuable, not just the URLs they share.
Every piece of content passes through an AI enrichment pipeline. The AI evaluates each item for: relevance to AI/ML topics, quality and depth of analysis, novelty (is this saying something new or recycling?), and appropriate categorization.
This is where most "news aggregator" bots fail. They dump everything into a channel and let the user sort through it. We flip that: the bot does the sorting so the user only sees what matters. The enrichment step is the difference between a useful tool and a noise machine.
Enrichment runs on a managed AI API, processing articles one at a time to stay within strict compute budgets. The AI call takes roughly 3 milliseconds of compute per article — fast enough to process hundreds of items per cycle without blowing past platform constraints.
Delivery happens in two channels: a public channel for broad distribution and individual user chats for personalized content. The delivery pipeline handles deduplication (don't send the same story twice), formatting (clean, scannable messages with proper structure), and personalization (each user's digest reflects their subscribed topics).
A critical design decision: delivery runs before enrichment in the pipeline priority order. If the enrichment step fails or times out (which happens under load), users still get their previously enriched content delivered on time. The expensive AI step is important but not time-critical — delivery is.
After months of continuous operation, here's where the numbers stand:
| Metric | Result |
|---|---|
| Content processed per cycle | Hundreds of items |
| Content read rate | 80%+ (vs 15-25% for email) |
| Infrastructure cost | Lean — minimal hosting spend |
| Monetization | Freemium with paid tier |
| Time from concept to live | Under 24 hours |
| Time to production-grade | ~2 weeks (iterating on onboarding, delivery, error handling) |
The read rate is the headline number — significantly higher than email newsletters (15–25% open rates), Twitter impressions (a fraction of followers), and even push notifications on mobile apps (40–60%). Telegram's direct message format, combined with content that's genuinely relevant to each user, produces engagement numbers that other channels can't match.
The freemium model works because users get enough free value to stay engaged, then convert to paid for premium features. Conversion rates are healthy for a content product — most news apps and newsletters convert at 1–2%.
The system uses serverless edge infrastructure — no dedicated servers, no scaling headaches. The architecture separates concerns cleanly: content ingestion, AI processing, delivery, and user management each run independently. This means a failure in one layer doesn't cascade to the others.
The key architectural insight: delivery is decoupled from processing. If the AI enrichment step is slow or fails, users still get their previously processed content delivered on time. The expensive AI step is important but not time-critical — delivery is.
The entire stack runs on lean infrastructure. Hosting costs stay minimal even as the user base grows, because the architecture was designed for cost efficiency from day one.
Building and operating this bot taught us things that apply to any Telegram bot project, regardless of use case.
We went from idea to live users in under 24 hours. But the bot wasn't production-grade for another two weeks. The last 20% — onboarding flow, error handling, edge case testing, delivery reliability, monitoring — takes as long as the first 80%. Budget for it.
In any pipeline where an expensive step (AI processing, data enrichment, image generation) feeds into a time-sensitive delivery, run delivery first with cached results. If the expensive step fails, users still get served. If delivery waits for enrichment, failures cascade and users see nothing.
A bot with 10,000 subscribers and a 10% read rate reaches 1,000 people. A bot with 1,000 subscribers and a 90% read rate reaches 900 people — with much higher engagement per user. Optimize for engagement, not vanity metrics.
We didn't accidentally end up with low hosting costs. We designed for it from the start. Lean infrastructure is the result of deliberate architecture choices, not luck.
Content sources change their format. APIs get updated. Edge cases surface under load. User behavior shifts. Our bot requires ongoing maintenance — roughly 2–4 hours per week of monitoring, fixing, and improving. Any production bot does. If you're not budgeting for maintenance, you're budgeting for decay.
Tell us about your idea. We'll scope it and give you an honest timeline.
Let's Talk →