ThoughtSpot expands into code-first analytics

The Mode deal matters because it turns ThoughtSpot from a search box for business users into a wider analytics workspace that can also keep technical analysts inside the product. Before the acquisition, a common pattern was to ask questions in ThoughtSpot, then move into a separate tool to write SQL, build custom charts, or run Python. Mode fills that gap with notebooks and richer report building on top of the same governed data.

• Mode brought a code first workflow built around SQL, then Python or R notebooks, with charts and dashboards in the same report. That is the exact shape of product used by teams that would otherwise choose Hex or Metabase for deeper analysis after the dashboard or search layer.
  2 thoughtspot 3 mode 4 sacra
• ThoughtSpot framed the acquisition as a way to cover the full range from ad hoc code first analysis to natural language exploration, and said the combined company would pass $150M ARR with a doubled customer base. That shows the deal was not just feature fill in, it was a bid to expand both persona coverage and distribution.
  1 thoughtspot
• The hard part is product coherence. ThoughtSpot now has business users clicking through Liveboards and asking questions in plain English, while analysts expect an IDE like workflow with cells, queries, and reusable code. Unifying those modes without making either one feel compromised is the main execution task behind the strategy.
  4 sacra 5 sacra

The direction is toward one analytics stack where an executive starts with a natural language question, an analyst opens the same dataset in a notebook, and both share one governed output. If ThoughtSpot makes that handoff feel seamless, it can compete higher in the market against both self service BI and analyst first tools.