LoginSign Up
← Back to Analytics
Weekly · Analytics · Week of May 18, 2026

Analytics tools are dropping SQL-first authoring — prompt-as-authoring and AI agents are now first-class.

prompt-as-authoringagents-as-platform-usersworkspace-expansionai-content-governancevertical-pivots
Y
By Yahya Tür
LinkedIn ↗
Generated 4h agoDrawn from 7 products

The week in analytics

The sector spent the week loosening the grip of SQL as the universal authoring interface. Hex reorganized its product around an agent the user steers with prompts and grounds with context — repos, projects, semantic models, memory, guides. Lightdash shipped natural-language table calculations, treating analyst authoring as something an AI can co-pilot rather than something only SQL editors can do. Neo4j went further and called out "AX" alongside DX/UX when announcing neo4j-cli — explicitly framing AI agents as first-class platform users. The directional move is consistent: the analyst surface is becoming a prompt surface, and the system underneath is being rebuilt to support it.

The parallel motion is workspace expansion. NocoDB is repositioning from an Airtable alternative to a database-plus-workspace — docs adjacent to data, geospatial views, deeper Postgres fidelity, tightening paid-tier wedges. Fulcrum is widening from field-data capture into the analyze-and-share layer above it. Analytics tools are growing in two directions at once: up the stack into authoring-by-prompt and out the side into adjacent surfaces.

Leaders

Hex (v6.3) made the most directional bet of the week — data apps are now one sentence away. The product is being reorganized around an agent that grounds itself in repos, semantic models, and memory. Each release either adds context channels or places the agent can act.

Lightdash (v6.3) shipped the natural-language formula feature as its directional signal: analyst authoring as AI co-piloted, not SQL-only. Surrounding work (hierarchical theming, YAML-as-code verified content, metric trees) prepares the supporting governance.

Neo4j (v6.3) shipped neo4j-cli explicitly for AI agents. Calling out "AX" alongside DX/UX is unusual — most database vendors are still adding MCP servers or chat assistants. The GenAI token functions and Cypher 25 work line up with the same posture: agents as users, not integrations.

NocoDB (v6.3) shipped dense — docs, maps, forms, Postgres enums in five weeks, with a regression tail to match. The Enterprise/Plus paywall is tightening (multi-column forms, custom linked-record displays paid-only).

Fulcrum (v6.3) grew a BI layer above its field-data captures while mobile coasted on fixes. Bulk-action ergonomics, BI tooling integration, and a growing Insights surface mark the directional move.

Wildcards

Feedly (v5.0) is steadily rebuilding itself as an AI threat-intelligence platform — the primary verbs are "analyze" and "enrich" rather than "read." Third-party enrichment partnerships (GreyNoise, VirusTotal, Analyst1) anchor the directional pivot away from RSS-era aggregation.

Themes that compounded

  • Prompt-as-authoring became the analyst surface — Hex's agent-driven app generation and Lightdash's natural-language table calculations both replaced SQL-first authoring with NL-first.
  • "Agents as platform users" became explicit framing — Neo4j named AX, Hex named the agent, and Lightdash positioned authoring as AI-co-piloted; the shift from "AI feature" to "AI persona" is now in product language.
  • Analytics tools grew into adjacent workspace surfaces — NocoDB shipped docs-with-data; Fulcrum grew BI above field capture; the standalone dashboard tool is fading.
  • Governance primitives shipped alongside AI authoring — Lightdash's verified content YAML and hierarchical theming, and Hex's context grounding, both pair AI generation with content trust.
  • Vertical analytics pivots accelerated — Feedly into threat intel, Fulcrum into field BI, Neo4j into agent-callable graphs — horizontal analytics keeps losing share to domain-specific positioning.

Watch this week

The near-term test is whether Hex's agent-driven app generation translates into measurable replacement of dashboard tools at the analyst persona — that is the wedge that would shift the category, not another AI feature on an existing dashboard. Watch NocoDB's regression tail: shipping that dense without quality slips for five weeks straight is unusual, and how the team handles the inevitable rollback will signal whether the cadence is sustainable. On the Neo4j side, AX as a stance is interesting on its own — if it gets adopted by another vendor's roadmap language in the next month, it becomes a category posture rather than a marketing line.