# Software development 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/custom-software-development-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

Your product was built by a founding team moving fast, and now every change breaks something and the people who know why are busy selling. Our senior engineers join your team and make the platform safe to change, with tests, a deploy you can roll back and documentation your next hire can read. Along the Wasatch Front that's a founder-run software company on Silicon Slopes, or a Salt Lake distributor whose ordering system grew up with it.

## Dynamics 365 consultants in Salt Lake City

Utah's direct-selling companies, many of them in Provo, Orem and Lehi, pay distributor commissions out of several entities at once, and Dynamics 365 Business Central keeps that beside finance and inventory, as it does for Salt Lake City's fintech lenders and Ogden's outdoor gear makers. We implement it with Dynamics 365 CRM and automate month-end with Power Automate.

[Dynamics 365 consulting in Phoenix](https://www.techfabric.com/dynamics-365-consulting-phoenix) · [Power BI consulting in Phoenix](https://www.techfabric.com/power-bi-consulting-phoenix)

## 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

### 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.

### Do you have an office in Salt Lake City?

The office is in Gilbert, Arizona, with teams in Amsterdam, Dnipro and Hyderabad. Delivery is remote or hybrid, and we travel for discovery, workshops and the opening weeks of a build.

## What software development covers

### Web applications

Applications built to be changed safely years after the original team has moved on. That means tests that mean something, seams where the business logic can move, and a deployment nobody is afraid of.

### Mobile applications

iOS and Android, built as products rather than as ports. The maintenance story is decided at the start, while it is still cheap.

### APIs and integration

The seams between systems, done once and properly. Most of the expensive failures we are called into are integration failures wearing another name.

### Data platforms

The layer underneath the application, on Databricks, Azure, AWS or Google Cloud. If the reporting and the application disagree, the platform is the reason.

### Modernisation of what exists

Often the work arrives as something already built that has become hard to change. We would rather read it and tell you honestly whether it is worth keeping than sell a rewrite you may not need.

### Durable, auditable workflows

Processes that take days, call several systems and must never half-complete. Getting that right is a different discipline from getting a request handler right, and it is where we spend most of our time.

## 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.