Atlas AI - Sell Project

Asking price: USD 2,500 — negotiable Stage: live beta / early software asset Website: https://atlas-ai-agent.site Bot: https://t.me/Atlas7AIbot I built Atlas as a solo developer, without outside investment. Atlas is a proactive Telegram assistant built around saved context, scheduled reminders and relevant follow-ups. Its purpose is to help people follow through across their day: remember an upcoming task, deliver a requested reminder, log a meal, or bring connected information into a configured briefing. The product focus is continuity. Configured reminders, briefings and context-based follow-ups can reach the user without them starting a new conversation each time. Follow-ups depend on saved context, enabled settings and connected services. Proactivity is an existing part of the implementation, not a claim of perfect autonomous judgment or proven retention. I have decided to sell the project and move on. I am looking for a technical buyer who wants to take over the existing product and focus its next stage. What is built • Natural-language reminders and scheduled delivery. • Saved memory and profile preferences. • Meal logging, estimated calories/macros and correction workflows. • Gmail connection, email reading and configurable alerts/digests. • Calendar connections and planning features. • Briefings and context-based follow-up systems. • English and Arabic support, voice input, photo/document analysis, and additional power-user features. • Website, admin tools, analytics, Telegram Stars payment integration and Free/Plus/Pro access logic. It is still beta software. Voice transcription can mishear dense food notes; meal nutrition is estimated; complex follow-ups and integrations should be evaluated in the buyer demonstration. This is not a claim that every feature works perfectly. Current traction At the 30 October 2026 activity cutoff: • 256 recorded account rows, including owner/testing accounts; 253 remain after excluding known classified internal accounts and nonpositive IDs. • 52 eligible accounts messaged in 30 days, 20 in seven days, and six in 24 hours. These count user-triggered incoming-message activity and exclude owner/known test traffic. • One historical 500-Star payment record; zero Stars in the last 30 days. Gifted or trial access is not counted as paid traction. Recurring revenue and paid retention are not established. This is an opportunity to acquire working software and continue developing it, not an established passive-income business. What the proposed sale includes The Atlas application code and seller-owned product assets, website, database schema/migrations, bot implementation, existing brand/domain and Telegram bot ownership, subject to ownership and transfer checks. Third-party components retain their licenses. A defined handover can be agreed. My personal accounts, API credits and keys are not included. Existing customer data and connected inboxes are not offered as a downloadable dataset; any service transition needs a separate, appropriate process. Technology and costs Next.js, React, TypeScript, Prisma/PostgreSQL, Supabase and Vercel, with Telegram and external AI/search services. A technical buyer will need their own service accounts, provider credentials and scheduler setup. Operating costs depend on hosting choices, AI usage and connected features. Application estimates and known gaps are described in the buyer brief; a complete monthly expense figure and profit have not yet been verified. A product walkthrough, aggregate usage figures, known limitations and handover scope are available for review. 1 November 2026 update: A staged usage-allowance pilot is implemented, with a Telegram /usage readout, dashboard allowance meter, per-quarter usage notices and transaction-based provider-budget reservations. Isolated Telegram testing verified the readout, ordinary conversation, quarter notices without repetition and the exhaustion message. Paid extra-usage purchases and public enforcement are not enabled; existing customer prices and access are unchanged. Multimodal cost coverage and commercial policy validation remain necessary before public activation.