--- title: "Dot" type: "AI Tool" url: "https://aidemos.com/tools/dot" description: "We tested Dot on live-database questions in plain English, with SQL shown beside each answer. It keeps follow-up context, but insight and recency handling slip." category: "business-marketing" website: "https://app.getdot.ai" published: "2026-08-09T10:50:49.281347+00:00" updated: "2026-08-09T10:50:49.281347+00:00" evidenceCount: 22 verifiedCount: 16 coverage: "dense" --- # Dot Plain-English database querying with strong SQL transparency and follow-up context, but uneven insight and data-recency handling. ## TL;DR Verdict **Good self-serve analytics, best for users who will verify and interpret** **Where it wins:** - You want non-technical users to ask plain-English questions against a live database and verify the answer with generated SQL. - You value follow-up context and want the tool to ask for clarification when a prompt is ambiguous. - You are comfortable with a result that may be a chart, a table, or text depending on the query shape. **Main limitation:** You need the tool to proactively interpret the business meaning of every answer rather than just report the numbers. **Pricing:** Free Free · Pro $180/month · Team $720/month · Enterprise Custom `Live PostgreSQL` · `SQL tab visibility` · `Follow-up context` · `Auto charts` **Website:** [Visit Dot](https://app.getdot.ai) ## Evidence (first-party, tested) *22 tested cells · 16/22 artifact-verified. Cite a cell by its Evidence ID, e.g. `ev:dot·best-customers-with-unpaid-order-and-payment-method-follow-ups·ambiguity-handling`.* | Criterion | Scenario | Verdict | Proof | Evidence ID | | --- | --- | --- | --- | --- | | Ambiguity Handling | Best customers with unpaid-order and payment-method follow-ups | ✓ worked | 🧾 [proof](https://cdn.futuresmart.ai/public/aidemos/c126c58ac82e4d899b11a7006a73d94d.png?v=1) | `ev:dot·best-customers-with-unpaid-order-and-payment-method-follow-ups·ambiguity-handling` | | Ambiguity Handling | Order pipeline breakdown with paid-pending edge case and last-month comparison | ✓ worked | 🧾 [proof](https://cdn.futuresmart.ai/public/aidemos/f4a355dee7cc4264abda5070118c15f6.png?v=1) | `ev:dot·order-pipeline-breakdown-with-paid-pending-edge-case-and-last-month-comparison·ambiguity-handling` | | Ambiguity Handling | cross-scenario | ✓ worked | 👁 observed | `ev:dot·cross·ambiguity-handling` | | Business Insight | Order pipeline breakdown with paid-pending edge case and last-month comparison | ✓ worked | 🧾 [proof](https://cdn.futuresmart.ai/public/aidemos/f66e88efc06343bdb64af3c00e3d1003.png?v=1) | `ev:dot·order-pipeline-breakdown-with-paid-pending-edge-case-and-last-month-comparison·business-insight` | | Business Insight | Best customers with unpaid-order and payment-method follow-ups | ✓ worked | 🧾 [proof](https://cdn.futuresmart.ai/public/aidemos/c126c58ac82e4d899b11a7006a73d94d.png?v=1) | `ev:dot·best-customers-with-unpaid-order-and-payment-method-follow-ups·business-insight` | | Business Insight | Customer acquisition in the last 90 days vs previous 90 days | ⚠ struggled | 🧾 [proof](https://cdn.futuresmart.ai/public/aidemos/8ce008eac9564d3cb0a6a0cf9a6cb5b4.png?v=1) | `ev:dot·customer-acquisition-in-the-last-90-days-vs-previous-90-days·business-insight` | | Chart / Visualization Support | cross-scenario | ◐ mixed | 👁 observed | `ev:dot·cross·chart-visualization-support` | | Dashboard Workflow | cross-scenario | ◐ mixed | 🧾 [proof](https://cdn.futuresmart.ai/public/aidemos/45ef8c30f8f14b8bbb2d43aecc8efa53.mp4?v=1) | `ev:dot·cross·dashboard-workflow` | | Export / Reuse | cross-scenario | ✓ worked | 🧾 [proof](https://cdn.futuresmart.ai/public/aidemos/45ef8c30f8f14b8bbb2d43aecc8efa53.mp4?v=1) | `ev:dot·cross·export-reuse` | | Follow-Up Context | Best customers with unpaid-order and payment-method follow-ups | ✓ worked | 🧾 [proof](https://cdn.futuresmart.ai/public/aidemos/e94fab739e414924b69bd67beb632d2f.png?v=1) | `ev:dot·best-customers-with-unpaid-order-and-payment-method-follow-ups·follow-up-context` | | FS Learning Value | cross-scenario | ✓ worked | 🧾 [proof](https://cdn.futuresmart.ai/public/aidemos/83c5f85ec0d44671817d813dda770ef7.png?v=1) | `ev:dot·cross·fs-learning-value` | | Plain English Query Handling | Customer acquisition in the last 90 days vs previous 90 days | ✓ worked | 🧾 [proof](https://cdn.futuresmart.ai/public/aidemos/8ce008eac9564d3cb0a6a0cf9a6cb5b4.png?v=1) | `ev:dot·customer-acquisition-in-the-last-90-days-vs-previous-90-days·plain-english-query-handling` | | Plain English Query Handling | Order pipeline breakdown with paid-pending edge case and last-month comparison | ✓ worked | 🧾 [proof](https://cdn.futuresmart.ai/public/aidemos/ef5af24b11994f87b7003541bb6a49b2.png?v=1) | `ev:dot·order-pipeline-breakdown-with-paid-pending-edge-case-and-last-month-comparison·plain-english-query-handling` | | Plain English Query Handling | cross-scenario | ✓ worked | 👁 observed | `ev:dot·cross·plain-english-query-handling` | | Result Readability | Customer acquisition in the last 90 days vs previous 90 days | ✓ worked | 🧾 [proof](https://cdn.futuresmart.ai/public/aidemos/8ce008eac9564d3cb0a6a0cf9a6cb5b4.png?v=1) | `ev:dot·customer-acquisition-in-the-last-90-days-vs-previous-90-days·result-readability` | | Result Readability | Best customers with unpaid-order and payment-method follow-ups | ◐ mixed | 🧾 [proof](https://cdn.futuresmart.ai/public/aidemos/e94fab739e414924b69bd67beb632d2f.png?v=1) | `ev:dot·best-customers-with-unpaid-order-and-payment-method-follow-ups·result-readability` | | Result Readability | cross-scenario | ◐ mixed | 👁 observed | `ev:dot·cross·result-readability` | | SQL Generation | Order pipeline breakdown with paid-pending edge case and last-month comparison | ✓ worked | 🧾 [proof](https://cdn.futuresmart.ai/public/aidemos/de47c420c7294041881ce9083c43523b.png?v=1) | `ev:dot·order-pipeline-breakdown-with-paid-pending-edge-case-and-last-month-comparison·sql-generation` | | SQL Generation | Best customers with unpaid-order and payment-method follow-ups | ✓ worked | 🧾 [proof](https://cdn.futuresmart.ai/public/aidemos/660535357d404e5ea29b115bbc94f21f.png?v=1) | `ev:dot·best-customers-with-unpaid-order-and-payment-method-follow-ups·sql-generation` | | SQL Generation | Customer acquisition in the last 90 days vs previous 90 days | ✓ worked | 🧾 [proof](https://cdn.futuresmart.ai/public/aidemos/2245ba6d917b4b0dba2fd4233ee6ca0a.png?v=1) | `ev:dot·customer-acquisition-in-the-last-90-days-vs-previous-90-days·sql-generation` | | SQL Generation | cross-scenario | ✓ worked | 👁 observed | `ev:dot·cross·sql-generation` | | SQL Visibility | cross-scenario | ✓ worked | 👁 observed | `ev:dot·cross·sql-visibility` | > 🧾 = artifact-verified (proof captured) · 👁 = observed (noted, no artifact) · verdicts: worked / mixed / struggled / failed. > **Good self-serve analytics, best for users who will verify and interpret** > > Dot is strong at answering live-database questions in plain English, showing the SQL, and preserving context across follow-ups. It is less reliable when the answer depends on proactive interpretation or on refusing comparisons that span data gaps, so it works best for users who are comfortable checking the result themselves. ## Demo Recording [Video: Dot demo recording (download MP4)](https://cdn.futuresmart.ai/public/aidemos/a7ee9f5329ad47f7b3888f571e7371c3.mp4?v=1) [▶️ Watch (streaming)](https://stream.futuresmart.ai/embed/47a035d3-7dbc-405d-a511-d1839c352e03) - [0:00 Introduction to Qeasol](https://stream.futuresmart.ai/embed/47a035d3-7dbc-405d-a511-d1839c352e03?t=0) - [0:40 Account Setup and Dashboard Overview](https://stream.futuresmart.ai/embed/47a035d3-7dbc-405d-a511-d1839c352e03?t=40) - [2:05 Connecting Data Sources](https://stream.futuresmart.ai/embed/47a035d3-7dbc-405d-a511-d1839c352e03?t=125) - [4:45 Natural Language Query Execution](https://stream.futuresmart.ai/embed/47a035d3-7dbc-405d-a511-d1839c352e03?t=285) - [8:50 Visualization and Advanced Features](https://stream.futuresmart.ai/embed/47a035d3-7dbc-405d-a511-d1839c352e03?t=530) - [11:38 Final Overview and Conclusion](https://stream.futuresmart.ai/embed/47a035d3-7dbc-405d-a511-d1839c352e03?t=698) *Video — Demo walkthrough of Dot’s database-chat workflow.* ## Feature-by-Feature Breakdown ### Natural-Language Database Querying **Verdict:** Strong Dot answers business questions against a live PostgreSQL database without requiring the user to write SQL, and returns a natural-language summary with an auto-generated chart or table. The tested inputs included a 90-day customer-acquisition comparison, a customer-value ranking, and an order-status query. **Input:** ``` Show all customers created in the last 90 days. How does new customer acquisition compare to the previous 90 days? ``` **Output:** **Input:** ``` Who are my best customers — the ones who order the most and spend the most? ``` **Output:** **Input:** ``` How many orders do we have at each stage right now? ``` **Output:** **Bottom line:** Strong for direct self-serve queries: the answers were readable, accurate, and formatted with charts or tables, but the tool generally reports the number before adding business interpretation. ### SQL Transparency and Query Assumptions **Verdict:** Strong Dot shows the generated SQL behind a result in a separate Query tab and includes filter notes that explain date windows and ranking assumptions. In testing, this covered the 90-day acquisition comparison and the best-customers ranking queries. **Input:** ``` Show all customers created in the last 90 days. How does new customer acquisition compare to the previous 90 days? ``` **Output:** **Input:** ``` Who are my best customers — the ones who order the most and spend the most? ``` **Output:** **Bottom line:** Very good transparency: the generated SQL and assumptions are inspectable, but they are one click away rather than embedded inline in the chat answer. ### Conversational Follow-Up Handling **Verdict:** Strong Dot keeps context across turns so follow-up questions can build on the previous result instead of starting over, and it asks clarifying questions when a reference is ambiguous. The tested follow-ups carried forward a top-three customer list into unpaid-order and payment-method questions. **Input:** ``` For the top 3 from that list — do any of them have unpaid orders? ``` **Output:** **Input:** ``` What payment methods do these top 3 usually use? ``` **Output:** **Input:** ``` Compare that to last month — same breakdown. I want to see if things have improved or got worse. ``` **Output:** **Bottom line:** Standout capability: it preserves context well and will ask before guessing when a reference is ambiguous. The weakness is that some follow-up answers become very terse, with supporting detail buried in logs. ### Time-Based Comparison and Historical Snapshot Analysis **Verdict:** Mixed Dot can compare time windows and reconstruct prior snapshots from order history. The tested cases included last-90-days versus previous-90-days comparisons, delivered versus cancelled share, and a current-versus-prior-month view of paid-but-pending orders. **Input:** ``` What percentage of our orders were successfully delivered vs cancelled? ``` **Output:** **Input:** ``` Compare that to last month — same breakdown, I want to see if things have improved or got worse. ``` **Input:** ``` What is the most recent month of order data you actually have? ``` **Output:** **Input:** ``` wht is most recent order month and show everything o g that ``` **Output:** **Bottom line:** It can reconstruct useful time-based views and even answer recency checks correctly, but the final month-over-month comparison was misleading because it compared July/August dates even though the tool’s own data cutoff was in May. That makes this capability useful but risky when the date window may be empty. ## Free tier plus credit-based paid plans Testing used the free 300-credit tier; paid plans are metered by credits. | Plan | Price | Notes | | --- | --- | --- | | Free ★ (tested) | Free | 300 one-time credits, no card, full Pro feature access. | | Pro | $180/month | 150 credits/month, unlimited users, $1.80 per overage credit. | | Team | $720/month | 800 credits, SSO, row-level security, embedded Dot. | | Enterprise | Custom | Self-hosted, audit logs, SLA. | *A 10% annual discount was mentioned in the report.* ## Is It Right For You? **Use it if** - You want non-technical users to ask plain-English questions against a live database and verify the answer with generated SQL. - You value follow-up context and want the tool to ask for clarification when a prompt is ambiguous. - You are comfortable with a result that may be a chart, a table, or text depending on the query shape. **Skip it if** - You need the tool to proactively interpret the business meaning of every answer rather than just report the numbers. - You need a guarantee that every result will render as a chart; some queries return tables or text only. - You need the tool to refuse or clearly block comparisons that fall outside the available data window without manual checking. ## Classification - **Category:** business-marketing - **Subcategory:** other-business-marketing - **Type:** text - **Built for:** Other ## Frequently Asked Questions **Q: Does Dot work with a live database, or only uploaded files?** In this test, Dot was connected to a live PostgreSQL database through its hosted cloud product. The report does note broader connector support, but this benchmark specifically used a live Postgres source, not CSV-only input. **Q: Does Dot show the SQL it used?** Yes. Dot exposes the generated SQL in a separate Query tab, and it also shows plain-English filter notes. The SQL is not embedded directly in the chat bubble. **Q: Can Dot handle follow-up questions in the same conversation?** Yes. It retained context across the customer-ranking follow-ups and the order-pipeline follow-ups. It also asked a clarification question when a follow-up phrase like "same breakdown" could refer to more than one prior result. **Q: Does every answer come with a chart?** No. Dot is adaptive. Some questions produced charts, some produced tables, and some follow-ups were text-only with supporting data buried in logs. **Q: How reliable is Dot with date comparisons?** It handled several comparisons correctly, including the 90-day customer-acquisition comparison and a month-over-month snapshot query. But it also produced a plausible-looking comparison over a period after the database’s last real data, so date-recency checks still need caution. **Q: What plans and pricing were observed in the report?** The report states a free tier with 300 one-time credits and no card, plus paid Pro ($180/month), Team ($720/month), and custom Enterprise plans. ## Similar Tools AI tools similar to Dot: - [Draxlr](https://aidemos.com/tools/draxlr) — AI Data Analyst · NL2SQL · Data Visualization · June 2026 - [AskYourDatabase](https://aidemos.com/tools/askyourdatabase) — AskYourDatabase Review: NL2SQL AI Database Chatbot Tested (2026) - [Basedash](https://aidemos.com/tools/basedash) — AI-Native BI · NL2SQL · Data Analyst Chat · June 2026 - [Definite](https://aidemos.com/tools/definite) — AI Data Platform · NL2SQL · AI Analyst · Dashboard Builder · June 2026 - [Querio](https://aidemos.com/tools/querio) — AI Data Analyst · NL2SQL · Data Visualization · June 2026 ## Need a custom AI solution for this use case? If you are looking to build a custom natural language SQL querying, database analytics assistant, data exploration tool for your business or internal workflow, email us at [contact@futuresmart.ai](mailto:contact@futuresmart.ai). ### Found something inaccurate or missing? We try to keep our AI research accurate and useful. If you found outdated information, an issue, or have a suggestion, email us at [collaborate@aidemos.com](mailto:collaborate@aidemos.com).