Case Study | Commercial HVAC company | Ohio
A connected foundation for commercial HVAC sales.
Foundari helped an Ohio commercial HVAC company shape Zoho CRM around its sales workflow and connect field-service data from one regional operation—giving sales a clearer view of prospects and customer activity.
industry
Commercial HVAC
company size
Multi-location business
systems used
Zoho CRM, BuildOps, Zoho Voice
engagement type
Systems, Integration & Automation
location
Ohio Regional Markets
The Challenge
what was getting in the way
The original setup was cumbersome to work with. The business wanted relevant BuildOps information in its CRM, but the CRM first needed customization to receive and organize that data. Business development representatives also needed a more workable process for prospect calls.
Customer visibility was another gap. Sales reps had to ask dispatch or search the dispatch board to find out about their customers’ jobs. Useful operational information existed, but it was not reaching sales in the flow of their work.
The company brought a business problem, not a finished technical specification. It needed help deciding what would work as it developed its sales operation. The challenge was to create a foundation the team could build on—not simply add another tool.
challenges
- Disconnected CRM and field-service information.
- A CRM that needed to fit prospecting and customer follow-up.
- Manual checking to understand customer-job activity.
Our Approach
Foundari worked with the team through brainstorming sessions, meetings, and ongoing discussions to understand how the CRM should support the business. The starting point was the work: what information sales needed, how prospects differed from customers, and where field-service information belonged.
That discovery informed the design of the CRM workflow and the BuildOps connection. Leads would support prospecting, while accounts would represent customers. Relevant operational data and job notifications would give sales reps more context without requiring them to search a separate dispatch workflow.
Implementation involved customization, integration, and iteration. It took longer than the client expected, and a BuildOps API change interrupted integrations during the engagement. The experience reinforced the importance of realistic timelines and continued refinement as systems and team needs evolve.
“We kind of came with a blank slate saying, help us figure it out. So it's not like we came to you guys with a specific plan.”
— Client representative, commercial HVAC company
What We Did
what foundari changed
A clearer CRM structure. Leads were used for prospects and accounts for customers. The lead workflow gave business development representatives a more useful basis for identifying whom to call and collecting information during those calls.
A working BuildOps connection. Information from one regional operation was reaching Zoho CRM at the September 2026 review. Credentials had been provisioned for additional operations, but those connections were not yet live. The completed work was an initial deployment, not a company-wide rollout.
Customer-job notifications. Sales reps were receiving notifications when their customers had jobs. This reduced their need to ask dispatch or search the dispatch board and gave them more visibility at the start of the day.
Calling tools in early use. The team was using Zoho Voice and beginning to use a power dialer for first-contact prospecting. Follow-up calls still needed refinement because the dialer view did not show all the prior notes the team wanted. Adoption remained early.
solutions
- CRM structure: leads for prospects; accounts for customers.
- Integration: one regional BuildOps operation connected to Zoho CRM.
- Notifications: customer-job activity reaching sales reps.
- Calling: Zoho Voice in use; power-dialer adoption underway.
The Outcome
The company had moved from disconnected systems toward a more usable sales foundation. Prospect and customer records had defined roles, field-service information was reaching the CRM for the initial operation, and sales reps were receiving customer-job notifications.
The practical change was access to information in the sales workflow. Reps could see customer activity without relying entirely on dispatch inquiries, and business development had a clearer structure for prospecting and recording call information.
These were client-reported capabilities, not measured productivity or revenue gains. Duplicate records and other punch-list items still needed attention, and reporting had not yet been meaningfully adopted. The foundation was working, with further refinement ahead.
One regional operation connected
BuildOps information was reaching Zoho CRM for the initial operation. Wider rollout remained ahead.
Customer-job visibility for sales
Job notifications reached sales reps, reducing the need to ask dispatch or search the dispatch board.
Clearer prospecting workflow
Leads and accounts had distinct roles, supporting prospect calls and better call information.
“we couldn't build off of it, and now we can.”
— Client representative, commercial HVAC company
What Came Next
The next stage was to extend the connection to additional regional operations, complete the remaining punch list, and develop reporting. Another operation was still entering quotes manually into its CRM, making that handoff a candidate for future improvement.
Expansion would build on the initial connection rather than assume every operation was already integrated. Calling workflows also needed further adoption and refinement, particularly access to prior notes during follow-up.
For the business, the engagement created something it had previously lacked: a connected foundation it could develop further. The next opportunity was to broaden that foundation and establish evidence of its effect on day-to-day work.
the operational shift
Area of Focus
Before
After
Timeframe
Sales workflow
CRM needed customization to support prospecting and customer records.
Leads for prospects; accounts for customers, with clearer call information.
In use at Sept. 29, 2026 review.
BuildOps connection
Zoho CRM and BuildOps were disconnected.
One regional BuildOps operation connected to Zoho CRM; additional operations not yet live.
Initial operation live at the September 2026 review.
Customer job visibility
Sales reps asked dispatch or searched the dispatch board for customer jobs.
Customer job notifications reaching sales reps.
In use at Sept. 29, 2026 review.
Prospect calling
Working through prospect calls was difficult in the original setup.
Zoho Voice in use; power dialer adoption early, with follow-up note visibility still limited.
Early adoption at Sept. 29, 2026 review.
Need clarity in your operating system?
Are disconnected systems, manual handoffs, or gaps in visibility making work harder than it needs to be? Find out what to fix, connect, or automate first.