Engineering brief
Why Can't Anyone Answer Questions About the Business? — Garrett Galow, WorkOS
The Brief
WorkOS’s Studio turns ad‑hoc business questions into durable, self‑serve widgets over internal data sources.
Decision relevance
Read this for workflow impact, implementation trade-offs, and the claims that need technical scrutiny before they reach team planning.

Summary
WorkOS built an internal agentic workspace (“Studio”) that lets non‑engineers ask business questions and have the system generate reusable widgets (code-backed UIs) that query Snowflake, Linear, Notion, etc. Crucially, the LLM is used once to design the widget; ongoing usage directly hits data sources without invoking the model. This shifts many BI/support tickets to self‑serve tools.
The technical pattern is notable: no RAG. Instead, constrained agents, strict sequencing (preflight checks), and contextual tool hints at call time (e.g., how to join messy Snowflake tables) drive reliability. They layer prompts (base + org + tool-specific rules), explicitly distrust the model’s product knowledge, and validate queries return data before codifying them.
Impact: GTM and support teams reduce Slack/Snowflake dependency on engineers; data/platform teams stop building endless one‑off dashboards. The “widgetization” makes outputs governable artifacts, not ephemeral chats. It also controls LLM spend by front‑loading generation cost and eliminating per‑use inference.
Tradeoffs: Governance is immature. Permissioning is currently user-based with org connectors “in progress.” There’s a real “query-as-truth” risk unless you add review, status filters, and lineage. Data semantics live in prompt context, not a canonical model—maintain these or drift will bite. Costs are hand‑waved as acceptable; Snowflake compute and Opus prompts still add up.
What most will miss: the winning move isn’t cleaner data or bigger dashboards; it’s precise runtime context injection and validation to make agents trustworthy, plus converting agent output into code you can review, version, and reuse.
Why It Matters
Turns business Q&A from ticket-driven to self‑serve, reducing data/engineering load while enforcing reliability through context and validation.
Editorial analysis
Key claims
- Treat agent outputs as code. Constrain tools, inject context at runtime, and validate before shipping widgets.
Practical use cases
- Use this as input for tooling evaluation, workflow planning, and technical due diligence.
Risks / caveats
- “Answer any question” claims, anecdotal hit rates, vague cost posture, unfinished org-wide permissioning.
Who should care
- Engineering managers, tech leads, and CTOs evaluating AI or developer tooling decisions.
Related topics
Bottom Line
Treat agent outputs as code. Constrain tools, inject context at runtime, and validate before shipping widgets.
Watch
This video is blocked due to your privacy settings. To watch this video, please accept YouTube marketing cookies.
Related breakdowns
How to Keep Shipping When You Walk Away from Your Desk — Zack Proser, WorkOS
A short briefing on the practical engineering implications, trade-offs, and claims worth ignoring.
PI AGENT FULL COURSE: Master Pi Agent in 30 Minutes
A short briefing on the practical engineering implications, trade-offs, and claims worth ignoring.
Shopify Staff Engineer: Why Your Multi-Agent AI Architecture Will Fail
A short briefing on the practical engineering implications, trade-offs, and claims worth ignoring.
Get TL;DW
Too Long; Didn't Watch.
A concise breakdowns of the AI and devtools videos that actually matter for engineering leaders.
Free. Weekly. No hype.
Video and thumbnails remain the property of their respective creators. tldw.news provides editorial analysis, commentary, and discovery links to original content.