Metricgram dashboard — Telegram community analytics and management SaaS
10 wk Idea to live SaaS
Multi-tenant Architecture from day one
Wk 1 First paying customers
0 Rewrites since launch

The challenge

The founders had a working Telegram bot prototype and a clear product hypothesis: serious community managers running paid groups, paid newsletters and large public channels need analytics, member-management and automation tools that go far beyond what Telegram natively offers. They didn't need another bot — they needed a real multi-tenant SaaS where each customer manages multiple communities with their own team.

The hard parts: getting clean real-time data out of a chat platform, keeping per-tenant data strictly isolated, and shipping fast enough to onboard paying customers within the first month.

What I built

  • Multi-tenant Rails app. Each customer manages multiple Telegram groups with role-based access for their team. Strict data isolation at the Postgres schema level.
  • Real-time bot integration. Telegram Bot API consumed via webhooks, processed in async Sidekiq workers so the request path stays under 100ms.
  • Stripe Billing: tiered plans, metered usage based on group size and message volume, automated dunning for failed payments, EU VAT handled via Stripe Tax.
  • Admin panel with impersonation. Support can debug a customer's setup without leaving the dashboard or asking for credentials.
  • Hotwire / Turbo frontend. Instant page transitions feel like an SPA without the SPA complexity. The whole team works in the same Rails repo.
Un trabajo excepcional. Consiguió lo que muchos equipos no consiguen, una aplicación robusta con muchas funcionalidades complejas, y lo más importante, con un código limpio, centralizado y escalable.
Co-founder — Metricgram

The result

From kickoff to live SaaS with paying customers: 10 weeks. Onboarded the first paying customers in week one of go-live (existing waitlist, but the platform held). The codebase is clean enough that the founders' in-house team could pick up feature work without a rewrite — exactly the handover I aim for in every MVP.

Some screenshots

Stack

Ruby on Rails 7 Ruby 3.2 PostgreSQL Sidekiq Stripe Billing Stripe Tax Hotwire / Turbo Stimulus TailwindCSS Telegram Bot API Heroku GitHub Actions

Have a SaaS hypothesis you want to validate fast?

I build production SaaS MVPs in 6–10 weeks. Fixed scope, fixed price, code in your repo from day one.

Read my SaaS MVP service →

Want to ship a real SaaS in 10 weeks?

30-min discovery call. Written fixed-price quote within 24 hours. No obligation.

Book a free 30-min call