Transformations / conversational analytics

Ask Anything. Trust Every Answer.

Your data stays where it is. Anyone can ask in plain English — and every answer stays live and shows each person only what they’re allowed to see.

[ the difference ]

AI on Your Data, Before and After

today
  • AI answers pulled into files, then forwarded anywhere
  • Whoever gets the file sees every row in it
  • Each chat decides what revenue means
  • A chart that was right on Monday, wrong by Friday
with textql
  • Ask from Slack, Teams or your AI assistant — data never moves
  • Every answer filtered by who is asking
  • Every metric read from one governed definition
  • Every query logged, every number traceable
[ 01 govern ]

Everyone Asks. Everyone Sees Only Theirs.

The same question means different answers for different people — and it should. Every answer runs under the access rules in your ontology, so sales in EMEA sees EMEA, finance sees everything, and a contractor sees nothing they shouldn’t.

  1. Row- and column-level rules defined once, in your repository
  2. Enforced on every question, from every surface people ask from
  3. Every answer logged with who asked and what they could see
one question · three people 2 of 6 rows visible
/ asked What did we book last quarter?
  • amer
  • emea New logos $3.1M
  • apac
  • emea Enterprise renewals $4.2M
  • amer
  • apac
answer for Maria $7.3M
ontology/access.tql · region = user.region same question · same definition
[ 02 stay live ]

Answers That Stay True

An answer pasted into a doc is a picture of the data on the day it was drawn. Ask TextQL and the answer is a dashboard: it re-queries on schedule, so the number people act on is today’s, not last Monday’s.

  1. Any answer saved as a dashboard with one click
  2. Refreshed on the schedule you set, in your own cloud
  3. The questions asked every Monday answered every Monday
the same answer, a week later mon
/ asked on mon Bookings this week, by day?
Chat export bookings.html
$3.0M made mon
Your dashboard dashboards/bookings.tsx
$3.0M refreshed hourly · mon
[ customer story ]
client
PlayOn Sports
profile
software services · charlotte, nc
file
snowflake → ana, in slack
status
live · default analytics layer
2–3 days every question through the data team
4–5 hrs asked ana in slack
asked+1 day+2 days+3 days
Snowflake CortexSecoda Ana ai tools tried on their data · replaced
PlayOn Sports

Every executive asks Ana first.

Every new executive spends their first two weeks talking to Ana. They get going without using our data resources — they just ask her questions in Slack and get detailed feedback about what’s happening.

Chris Morgan, Head of Data and AI, PlayOn Sports
10×
faster analytics turnaround
7,000
datasets joinable by non-technical users
0
analysts needed on-call during peak season
[ getting started ]

Three Steps, on the Warehouse You Already Connected

No new BI tool and no migration project. The same warehouse, the same questions — answered in a form that lasts.

  1. 01 / connect Read What’s There Point TextQL at the warehouse your AI already queries. It reads the schema, the joins and the metrics people keep asking about. no data copied
  2. 02 / define Agree the Numbers The metrics everyone asks for are defined once, in your repository, and signed off by the people who own them. one definition each
  3. 03 / ask Answers That Last People keep asking in plain English — in Slack, Teams or their AI assistant. What comes back refreshes, shares safely and is logged. live, governed

See It on Your Warehouse

Bring the questions your team already asks AI. We connect to the warehouse you use, define the metrics behind them, and turn the answers into dashboards you own.

  1. 01A 30-minute call to pick the questions and the warehouse
  2. 02We define the metrics behind them, inside your cloud
  3. 03Your team asks away — and every answer stays live
[ use cases ]

Where It Starts

  • 01 AI on Snowflake, governed

    Keep the AI your team already uses on the warehouse, and make what it produces refresh and respect access.

  • 02 Retire the HTML dashboards

    Find the AI-made dashboards people actually reuse and turn them into live ones; let the one-offs go.

  • 03 Ask from Slack and Teams

    Plain-English questions where people already work, answered from the same governed definitions.

  • 04 Board-ready numbers

    Every figure traced to its query and definition, so the number in a chat is the one finance signs off.

  • 05 Scheduled answers

    The questions people ask every Monday, answered every Monday — as playbooks, not a pasted chart.

  • 06 Row-level security by default

    Every answer inherits the warehouse’s own permissions, so a forwarded dashboard never shows more than it should.

[ faq ]

What Teams Ask Before They Start

Keep it. The gap is what happens after the answer: a static file that doesn’t refresh, doesn’t carry your permissions and defines revenue however that chat decided to. TextQL makes the answer live, governed and consistent.

[ try textql ]

Bring Us Your Hardest Problem