// case study · manufacturing & logistics / construction · product development, software engineering

Field Crews Don't Use Software They Don't Trust.
So We Built Some They Do.

We took MAS HVAC from product discovery through MVP - a construction scheduling platform built with React, Hasura, and Azure Functions for real field teams.

// the receipts
MVP
Discovery → build
React
+ Hasura + Azure
Field-first
Adoption focus
HVAC
Scheduling platform

// the challenge

Field crews know bad software within five minutes.

Construction scheduling has a technology adoption problem. Software built for construction is often built by people who've never been on a job site - and field crews know it within five minutes of using it. The result is expensive software nobody actually uses, and foremen who go back to whiteboards and phone calls because at least those work.

MAS HVAC needed a platform that could handle the actual complexity of HVAC contractor scheduling - crews, equipment, job sites, subcontractors, and the constant realities of field work - in a way that field teams would actually adopt. That's not a user interface problem. It's a product understanding problem.

// no whiteboards, no workarounds

Software Field Crews Actually Use.

200+
Products shipped
4.9
Clutch rating
10yr
Shipping since 2016
Start Your Field Build

// the approach

Discovery first, then a product that fit reality.

Discovery Before Build

We started with a structured product discovery to understand the real workflows before we touched a line of code. Who uses this, when, under what conditions, and what makes them stop using it? That work saved significant rebuild time and shaped a product that fit reality.

React for a Fast, Responsive Interface

Field software needs to feel fast - hesitation in a UI leads to users finding workarounds. React gave us the component architecture to build a responsive, snappy experience that could handle complex state without feeling sluggish.

Hasura for a Flexible Data Layer

Hasura's GraphQL API layer let us move quickly during MVP development while building a data architecture that could evolve. Less hand-written API boilerplate, more focus on the actual product logic.

Azure Functions for a Serverless Backend

Event-driven, scalable, and cost-effective for a scheduling platform's usage patterns - peak at job start and end of day, quieter in between. Azure Functions matched the workload profile.

// the outcome

MVP

discovery → validated build

An MVP scheduling platform built through discovery - shaped by how field crews actually work.

Not how someone hoped they would. A React + Hasura + Azure Functions stack, designed for field-crew adoption from day one in a construction scheduling platform built for HVAC.

React + Hasura+ Azure Functions
Field-firstAdoption from day one
ConstructionHVAC scheduling

Built.
Shipped. Adopted.

// technologies used

Built on a stack matched to the workload.

Reactfrontend
Hasuragraphql data layer
Azure Functionsserverless backend
Azurecloud infrastructure

got a project?

Building something for people who have
better things to do than learn your software?

Let's talk about how to build it right - software field teams will actually trust and use.