WeMAIde← All cases
← All cases
● LIVE PRODUCTCASE / 07

AI Telegram product · 2026

Unf*cking Horoscope

Daily horoscopes with profanity, memes and affection — delivered at each user’s exact local time.

PRODUCT SYSTEM● LIVE
01 / GENERATENight pool12 signs · 5 reactions
02 / STOREPostgreSQLVariants · schedule · logs
03 / DELIVERExact local timeRU / UK · 8 time zones
04 / RETAINReaction loopShare gate · smart pause
Market & languagesCIS audience · RU / UK
Year2026
DurationProduction product
Full scopeProduct logic, prompt engineering, backend, database, automation, DevOps
01 / PROBLEM

The challenge

The product needed a recognisable voice, personal delivery and reactive dialogue without turning every user action into a paid LLM request. It also had to run continuously on an inexpensive VPS and remain manageable without server access.

02 / RESPONSE

The solution

A nightly content pool generates variants for all twelve signs and five reaction types. During the day, users receive instant responses from PostgreSQL, so API cost depends on the selected ECONOMY or SCALE mode — not audience size. Personal time zones, viral unlocks, smart pauses, three-layer throttling, backups and admin commands complete the operating system.

03 / SYSTEM

Product architecture

The core operating flow connecting the product idea, code and a measurable outcome.
PRODUCT SYSTEM● LIVE
01 / GENERATENight pool12 signs · 5 reactions
02 / STOREPostgreSQLVariants · schedule · logs
03 / DELIVERExact local timeRU / UK · 8 time zones
04 / RETAINReaction loopShare gate · smart pause

04 / MODULES

Inside the system

01Exact-time delivery across personal time zones↗
02GPT-4o tone system with few-shot examples↗
03Nightly content pool and two cost modes↗
04Viral tomorrow-unlock, smart pauses and admin tools↗

05 / OUTPUT

A bold content product with fixed AI economics

Verified outcomes
OUTPUT_011000+

registered users after Telegram-channel acquisition

OUTPUT_0217

LLM requests per day in ECONOMY mode

OUTPUT_03≈€4

monthly production infrastructure

Project principle
“API cost follows a chosen operating mode — not the number of people pressing buttons.”

System principle — WeMAIde

Explore the related work

Services and practical material connected to the system in this case.

SERVICETelegram bot developmentSERVICEAI automation developmentPRACTICAL GUIDEHow to schedule Telegram bot messages in each user’s time zone
Next case / 08Pi Mainnet Export↗