Smartsheet deploys Claude across customer-facing AI, engineering, and company-wide surfaces in early 2026
Smartsheet customers faced fragmented data across multiple systems, data warehouses, and project repositories, making a unified view of work difficult to achieve. Inside engineering, existing AI coding tools only supported line-level code completion and could not bridge data silos across Snowflake, service databases, and internal APIs.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · User submits request via Claude
Smartsheet customers view, create, and manage their work directly from a Claude conversation.
The Smartsheet MCP Connector reached 1,400+ organizations within 30 days of launch, with 48% of usage going beyond queries into active work creation. Claude Code users ship 3x more code and merge 31% more pull requests, with cycle time dropping 28%. Helpdesk volume fell 30%, prompt caching cut operational costs by 60%, and 49% of employees were actively using Claude within 2.5 weeks.
What failed first
Existing AI coding tools were limited to line-level code completion and could not work across the data boundaries Smartsheet's engineering team needed.