That's the ceiling nobody prices in. The AI reads your data, writes a beautiful summary of the problem, and then a human copies the customer list into another tab and starts the actual work by hand.
So we built the part after the insight. Basedash Actions writes and runs the SQL to find the answer, then reaches into the tools where the work actually lives (Stripe, HubSpot, and anything else with an MCP server) and does the follow-through. Find the accounts, update the CRM, chain the steps into a workflow that runs on its own.
The obvious objection: nobody sane wants an AI acting on production data unsupervised. Agreed, which is why every action runs through a human approval gate. You see exactly what it's about to do, in plain terms, before it does it.
The gates add friction, and that's deliberate. Trust in agents gets earned one approved action at a time, and I'd rather ship the training wheels than ship the incident report.
We just launched yesterday on Product Hunt. Would you trust this?
https://www.producthunt.com/prod...
Basedash: AI data analyst
Tabstack by Mozilla
@maxmusing S/O for this new launch! keep up the great work, and keep launching
Basedash: AI data analyst
Thank you @fmerian! Means a lot coming from you 🙏
An LLM writing and running mutating SQL against a real database is exactly the part I'd want the guardrails on. When it says 'update the state of a hundred items', does it show me the statement and the affected-row count before it runs, and does it wrap the write in a transaction I can roll back? The classic failure is a dropped WHERE turning a 100-row update into 100k, and the model sounds equally confident either way. Preview plus row-count plus rollback is what would get me to flip 'allow edits' on in prod.
Basedash: AI data analyst
@dipankar_sarkar yes exactly, you can preview the exact query and see what would be affected before deciding whether you want to approve or reject the action. Reliability and trust are super important for a feature like this.
Love that the natural language input sits front and center instead of burying it behind a SQL editor or settings panel. The "describe what you want" framing makes it feel like a creative tool rather than another BI dashboard.
Basedash: AI data analyst
@mzeyyenrdjx yes exactly, that was super important to us. We market ourselves as AI-native because we really designed and built this product around AI from the start. In many ways, we're much closer to Lovable or v0 than Tableau or Looker.
How does it handle really messy or unstructured data sources, like pulling from a NoSQL database or a third-party API that doesn't return clean tables?
Basedash: AI data analyst
@duran_ml51620 we have an ETL pipeline built in that syncs third-party API data into structured tables. It can also work well with NoSQL databases like MongoDB.
Our AI harness is specifically built to handle these kinds of messy datasets well. It learns the shape of the data over time and improves its own context.
Basedash: AI data analyst
Kris from @Basedash: AI data analyst here! Super excited about this launch. We built this because we realized that we often wanted to act on all the insights we were getting from our own product. But carrying out these write tasks is still pretty tedious for a non-technical user, whereas technical teams need guardrails in place before non-coders like me can update the database. So we built both :)
Now the agent writes the fix, shows you exactly what it's about to run, and waits for your approval. One click. All with tons of controls. Admins enable edits per connection. Every tool gets its own permission level. Routine operations run automatically, sensitive ones pause for a human, dangerous ones stay blocked. Your rules, enforced every time.
We've run this internally for weeks and it has already changed how our own team operates. The person closest to the customer fixes the issue.
Happy to answer anything!
Preview plus approve/reject covers the intent check nicely. The one that's bitten me: the affected-row count you show at preview is a separate query from the write, so under any concurrent traffic the number I approved and the number that actually changes can drift. Do you run the count and the update inside one transaction, or is that preview count more of an estimate?
The natural language to chart flow feels really polished, like the team actually thought through what happens when a query doesn't quite match the data. That's rare in AI BI tools.
Basedash: AI data analyst
Thanks @sakin8461, those kinds of details are very important to us!