Databricks as an AI workbench for knowledge work

Databricks became an end-to-end AI workbench for knowledge work. More than 100 knowledge workers now use coding-class agents on it against challenges of HR, Finance, Commercial, and Marketing.

Finance reconciliations leave private spreadsheets and remain as jobs. Commercial challenges start to find a way out of one-off decks to become repeatable jobs and autonomous agentic flows.

HRs start to productize solutions that would require lots of vendors, time, and spend, while also automating the routine.

This spring I was looking for a way to bring the power of coding agents to knowledge workers. After months on Claude Code I knew the capability was real. I did not yet have a way to give it to people inside the company without pointing a laptop at production. I went in cautiously and found the solution in Databricks, which was not the place I expected to look.

The platform is sold as a lakehouse - pipelines, SQL, dashboards. Genie Code sat on top of that stack just freshly released in March this year. The lake sits beside the work. The sandbox holds the guardrails. Specs, context, jobs, and apps live in the same environment, so a useful sequence does not die as a chat transcript. That is why wide adoption was possible.

The surprise showed up after people were on the surface.

They picked up business problems that used to wait for a specialist. Capability grew because the workbench could execute. Appetite grew with it. The first use case did not close the need. They brought the next one, then the one after that.

I went looking for a way to transfer a tool.

What scaled was the appetite for the next problem.