# Databricks consulting in Salt Lake City, UT > A substantial fintech and software base along the Wasatch Front, a large integrated health system beside it, and an unusually high share of companies still run by their founders. If that's you, you want the AI system in production and its operating cost known, without a transformation programme in front of it. Canonical: https://www.techfabric.com/databricks-consulting-salt-lake-city Serving: Salt Lake City, Provo, Lehi, Ogden, Sandy, Park City Headquarters: 1530 E Williams Field Rd, Ste 201, Gilbert, AZ 85295. No office in Salt Lake City. --- ## Why Salt Lake City work is our work Founder-run fintech and software companies here usually have a Postgres that became the warehouse by accident and a BI tool pointed at it. Lakebase and Lakehouse Federation let that first step be small, with the application's own data federated into Unity Catalog before anything moves, and the SOC 2 evidence comes from the audit tables rather than a project. ## Work a buyer here would recognise If your application database has quietly become your warehouse, read how TotalLoop moved. It started as a cloud-native platform on Azure with its own CRM and a sales dashboard, and later moved off Cosmos DB and SQL Server onto Databricks Lakebase, converted with TechFabric Airlift and cut over in reversible waves. ## The first enterprise deal brings the questionnaire Plenty of software and fintech companies between Salt Lake City and Lehi are still run by their founders, and the first large customer usually arrives with a security questionnaire and a SOC 2 Type II requirement. A fintech partnering with one of Utah's industrial banks, chartered by the state's Department of Financial Institutions, gets a second list on top, because the bank's examiners expect it to oversee its vendors. ## Questions ### What would Databricks look like for a Salt Lake City biotech? Like Recursion's, at a smaller scale, with images and results kept together. Recursion, on Rio Grande Street in Salt Lake City, says it runs up to 2 million experiments a week to build a 50+ petabyte dataset, which shows where a lab's data heads once screening scales. We'd keep the raw image files in a Unity Catalog volume and write each plate's metadata and assay readings to Delta tables that point at those files, so scientists query both under one set of grants. The plate map is where we'd expect disagreement, so we'd fix its schema with your lab lead first. Sources: [Recursion](https://www.recursion.com/) ### How does Utah's privacy law change a Databricks setup in Salt Lake City? If the law covers you, it decides where personal data gets tagged. The state's Consumer Privacy Act applies to companies with at least $25 million in annual revenue that also handle the data of 100,000 consumers a year, or 25,000 if more than half their revenue comes from selling it. Covered consumers can ask for deletion and opt out of targeted advertising. We'd tag personal columns in Unity Catalog as tables land, write masking policies against the tags, and keep a deletion job that finds a person across every table carrying their key. Tags don't follow data into a copy, so three years of untagged copies is slow to clean up. Sources: [Consumer Privacy Act](https://le.utah.gov/~2022/bills/sbillenr/SB0227.htm) ### What would Databricks do for a Salt Lake City distributor's inventory data? Give you one inventory number that warehouse, sales and finance all trust. Trade, transportation and utilities is the largest sector in the Salt Lake City metro, at 163,100 jobs against 155,800 in professional and business services, in September 2026 (preliminary) according to the Bureau of Labor Statistics. We'd bring the warehouse system, ERP and carrier feeds into Delta tables and define on-hand and in-transit once, as metric views in Unity Catalog. Planning models come second, once a pallet counted at the dock shows up as the same pallet in finance's numbers. Sources: [the Bureau of Labor Statistics](https://www.bls.gov/eag/eag.ut_saltlakecity_msa.htm) ### We are founder-run and our first big customer wants SOC 2. Then the useful thing is a platform that already produces the evidence, so the questionnaire becomes a document exercise. We would rather get one system into production with the trail built in than run a compliance programme alongside a build. ## What databricks consulting covers ### Migration off Snowflake, Synapse and Teradata Run through TechFabric Airlift, with executable playbooks for twenty-seven source platforms, signed migration certificates, and a cutover you can reverse at two in the morning. ### Unity Catalog governance Catalogue and schema design, a grant model expressed through groups, row filters and column masks, and lineage that survives a refactor. The boundary your agents and Power BI inherit. ### Lakeflow pipelines Ingestion and Lakeflow jobs with schema evolution handled rather than hoped for, medallion boundaries drawn on purpose, and jobs that recover instead of restarting from zero. ### Databricks Apps and agents Applications that run inside the workspace under their own service principal, and agents on Unity Gateway that inherit catalogue permissions instead of routing around them. ### Genie and AI/BI Metric definitions agreed with the person who owns the number, and a benchmark suite Genie has to keep passing, so the answer holds up when finance checks it. ### Cost that somebody can defend Cluster policies, warehouse sizing, file layout and the queries that actually pay. Instrumented at build time rather than discovered on an invoice. ## Working with us from Arizona Arizona does not observe daylight saving, so from November to March we are on the same clock as you and from March to November we are an hour behind. The working day overlaps almost completely. Most delivery is remote or hybrid. We travel for discovery, workshops and the opening weeks of a build.