SQL barrier
Non-technical team members couldn't query their own data without involving a developer. Every simple question caused a delay.
Slow turnaround
Waiting for a developer to run a report meant decisions were made on stale data or gut feel rather than real numbers.
No self-serve reporting
There was no way for the team to pull formatted reports or charts without custom dashboard work. Those took weeks to build.
User Asks
Team member sends a plain-English question on Telegram, email, or the web interface.
LLM Converts
Multiple LLM calls convert the question into a safe, executable SQL query.
Query Runs
SQL executes against Supabase. On error, it's retried automatically with error context.
Answer Returned
Formatted answer with data visualizations and downloadable Excel report sent back.
Database Layer
Hosts the PostgreSQL database. Provides a secure API for querying live business data on demand with user-level access control.
- PostgreSQL database
- Row-level security
- Real-time data
NL → SQL Engine
Multiple LLM calls handle intent extraction, schema matching, SQL generation, and error recovery, producing reliable queries from free-form questions.
- Multi-step LLM calls
- Error retry logic
- Schema-aware generation
Multi-Platform Interface
The same pipeline runs across Telegram, email, and a web interface. Users pick whichever channel fits their workflow. The backend is shared.
- Telegram bot
- Email interface
- Web chatbot
What just happened?
Plain English Queries
Anyone on the team can ask data questions in natural language — no SQL knowledge required.
Excel Report Output
Every successful query generates a downloadable, formatted Excel report alongside the text answer.
Auto Error Recovery
On a SQL error, the query is retried with error context. If still unresolved, the user is prompted to clarify.
Multi-Platform
Works on Telegram, email, and the web — same intelligence, whichever channel the team prefers.
Stored Query History
Every query and its result is stored, creating a searchable history of what was asked and when.
Secure by Design
Queries run through Supabase row-level security — users only see data they're permitted to access.
Your team deserves
self-serve data.
Works with any PostgreSQL or Supabase database. Custom to your schema, live in days.
- Any SQL database
- Custom to your schema
- Live in days, not months