Request a demo

Ask your operation anything.

Ask answers plain-English questions from your own systems (TMS, ELDs, spreadsheets) and shows the query behind every answer.

Request a demo
Ask · thread Read-only
Which lanes pay us the least per mile?
Ask
Inspected columns of dbo.orderheader
Revenue per mile by lane, July deliveries 41 rows · 388ms

WITH orders AS (

SELECT DISTINCT ord_hdrnumber, ord_originpoint, ord_destpoint, ord_totalcharge, ord_totalmiles

FROM dbo.orderheader WHERE ord_completiondate >= @start_date AND ord_status = 'CMP')

SELECT TOP (50) …, SUM(ord_totalcharge) / NULLIF(SUM(ord_totalmiles), 0) AS rev_per_mile

BIS → FSD is your weakest lane — $0.38 under the $2.24 fleet average.

Revenue per mile vs fleet average — July Saved · Ops dashboard
BIS → FSD −$0.38/mi AMA → OKC −$0.26/mi GRR → CLE −$0.12/mi DAL → MEM +$0.15/mi ATL → CLT +$0.33/mi
read orderheader · legheader filters completed deliveries · July 41 rows fresh 6m ago View SQL refreshes every 5m
AI-generated query. Verify before acting on it.
How are those lanes doing on time?
Ask Thinking…
On-time delivery by lane, July 412 rows · 241ms

BIS → FSD runs 71% on time, 23 points under fleet average.

On-time vs appointment — July Save to dashboard Saved · Ops dashboard
71% BIS → FSD 94% fleet average 1h 48m median lateness
read stops · orderheader derived arrival vs appointment, ±15 min 412 rows fresh 6m ago View SQL
How are those lanes doing on time? Ask a follow-up…
A looping sequence of the Ask thread over a read-only bridge to the fleet's own systems. The thread already holds a delivered answer: asked which lanes pay the least per mile, Ask read orderheader and legheader across 41 completed July deliveries and charted five lanes as bars against the $2.24 fleet average, BIS to FSD lowest at $0.38 below it. That answer is saved to the Ops dashboard as a live tile. A follow-up then types into the composer — “How are those lanes doing on time?” — and Ask writes and runs a single T-SQL statement over dbo.stops joined to dbo.orderheader, comparing each arrival against its appointment window and returning 412 rows in 241 milliseconds: BIS to FSD runs 71% on time against a 94% fleet average, with median lateness of one hour 48 minutes. Each answer carries its own receipts row, and the second is saved to the dashboard in turn.

How Ask answers a question.

  1. Ask in plain English

    Ask writes the query and runs it against your systems through a read-only bridge.

  2. Read the receipts

    Every answer shows the tables it read, the filters it applied, the row count, and freshness. Raw SQL is one click away.

  3. Set up a monitor

    A monitor is a question that re-runs on a schedule. It posts findings to Slack, Teams, or email, with receipts.

  4. Run Deep Research

    Deep Research runs agents across your operation and reports back: idle-fuel burn, unbilled detention, lanes whose rate per mile has slipped.

  5. When Ask can't answer

    If your data can't support an answer, Ask says so instead of guessing. No cost data in the TMS, no margin number.

The freight ontology, pre-built.

Ask already knows loads, lanes, stops, detention, deadhead, margin, and how they connect, whatever your TMS calls the fields.

TMS TMW Suite · McLeod
  • orders & rates
  • customers & stops
  • dispatch legs
  • drivers & trucks
ELD Samsara · Motive
  • GPS pings & miles
  • hours of service
  • duty status
  • arrivals & departures
Accounting QuickBooks
  • invoices & payments
  • fuel spend
  • driver settlements
  • receivables aging
Spreadsheets Excel · Google Sheets
  • rate sheets
  • fuel surcharge tables
  • driver pay rules
  • accessorial charges
What Ask knows
Read
  • Loads
  • Lanes
  • Stops
  • Drivers
  • Trucks
  • Revenue
Derived
  • Deadhead
  • Detention
  • On-time
  • Margin

No source stores a deadhead, detention, on-time, or margin column. Those numbers exist only where the systems join.

FAQ

How do we know the answers are right?

Check any answer against the query that produced it and the tables it read. If the data can't support one, Ask says so.

What if nobody on our team writes SQL?

Nobody has to. You ask in plain English and Ask writes and runs the query. A dispatcher or billing clerk gets the answer an analyst would.

Does it work with our systems?

Ask reads the systems you already run (TMS, ELDs, spreadsheets) through a read-only bridge. It's tuned for heavily customized TMS installs and messy data.