Why We Built HoodOps — And Why the Industry Needs Purpose-Built Software

I spent 25 years in enterprise IT before I ever touched a hood. I built systems for organizations that processed millions of transactions, managed complex compliance requirements, and needed their technology to work without excuses. Then I started a hood cleaning company, and I discovered an industry where most businesses run on paper, spreadsheets, and sheer determination.

That contrast — between what I knew technology could do and what this industry was actually using — is why HoodOps exists.

The Origin: Building CPP from Scratch

When I launched Cleaning Pros Plus (CPP), I did what most new hood cleaning owners do: I tried the tools that were available. I tried generic field service management platforms. I tried CRMs built for HVAC companies. I tried scheduling software designed for plumbers. I even tried cobbling together a stack of off-the-shelf tools — one for scheduling, one for invoicing, one for route planning, one for documentation.

None of them worked. Not because they were bad software — some of them were excellent at what they were designed to do. They failed because hood cleaning is not a generic field service trade. We have compliance requirements that plumbers do not have. We have frequency schedules dictated by NFPA 96 that HVAC companies do not deal with. We have before-and-after photo documentation requirements, access panel tracking, grease accumulation assessments, and fire suppression system interactions that no general-purpose FSM tool was built to handle.

So I built my own system. I wrote the workflows, designed the database, created the forms. It was ugly. It was held together with duct tape and determination. But it worked — because it was built around the way hood cleaning actually happens, not the way a software company imagines field service works.

Getting IKECA Certified

Somewhere in the process of building CPP, I got my IKECA certification. For those outside the industry, IKECA — the International Kitchen Exhaust Cleaning Association — is the professional body that sets education and certification standards for kitchen exhaust cleaning. Getting certified meant studying the science behind grease accumulation, understanding ductwork design, learning the fire dynamics that make our work critical to life safety.

That certification changed how I thought about the business. It was not just about cleaning hoods. It was about fire prevention. It was about compliance. It was about being able to look a fire marshal in the eye and show them exactly what was done, when it was done, and why the frequency was appropriate for the cooking type.

And it made the software gap even more glaring. Here was an industry with genuine life-safety implications, governed by a detailed national standard, subject to inspection by fire authorities — and the technology most companies used to manage it was a clipboard and a filing cabinet.

The Gap Between Generic Software and KEC Needs

Let me be specific about what generic field service software gets wrong for hood cleaning:

• Frequency scheduling: Most FSM tools let you schedule recurring jobs — weekly, monthly, quarterly. But they do not tie frequency to cooking type. They do not know that a charbroiler requires monthly service while the steam kettle next to it requires annual. They treat all recurring jobs the same.
• Compliance documentation: Generic tools generate invoices. Hood cleaners need to generate compliance certificates — documents that include before/after photos, system condition assessments, access panel verification, and cleaning method details. An invoice proves you billed for the work. A compliance certificate proves you did the work.
• NFPA 96 awareness: No generic FSM platform knows what NFPA 96 is. It cannot validate that a monthly-frequency client is actually scheduled monthly. It cannot flag when a client's cooking type changes and their frequency should be reassessed. It does not speak the language of this trade.
• Client system profiles: A hood cleaning client is not just a name and an address. They are a system — hoods, fans, ductwork, access panels, fire suppression, cooking equipment, grease containment. Generic CRMs have no concept of this. Every time you visit, you are re-entering information that should persist from job to job.

These are not edge cases. These are the core workflows of kitchen exhaust cleaning. When your software does not support them natively, you end up building workarounds — custom fields, manual processes, spreadsheet supplements — until the workarounds become more work than the software saves.

The Decision to Build

There is a moment in every founder's journey where you decide to stop adapting and start building. For me, it came when I realized that the gap between generic software and KEC needs was not a feature request — it was a fundamental design difference. You cannot bolt hood cleaning onto software designed for a different trade. You have to build from the ground up, with NFPA 96 in the foundation, not as an afterthought.

HoodOps is what came out of that decision. Every screen, every workflow, every data field was designed by someone who has done this work — who has crawled through ductwork at 2 AM, who has stood in front of a fire marshal with a stack of service records, who has tried to schedule 200 clients across four frequency tiers with a spreadsheet and a prayer.

It is not a generic platform with a hood cleaning skin. It is hood cleaning software, built for hood cleaners, by someone who understands the work because he has done the work.

The Vision: An Industry That Shares Instead of Hoards

But HoodOps is not just about better software for individual companies. It is about raising the bar for the entire industry.

Kitchen exhaust cleaning is fragmented. Most companies are small — one to five trucks. Knowledge is siloed. Best practices are guarded. New operators enter the industry and make the same mistakes that veterans made twenty years ago, because there is no shared body of operational knowledge.

I believe that has to change. When one company figures out a better way to price, schedule, document, or deliver hood cleaning services, that knowledge should be available to others. Not because competition does not matter — it does — but because the rising tide of industry professionalism lifts every boat. When customers trust that hood cleaning companies are competent, compliant, and professional, demand grows. When demand grows, there is more work for everyone.

That is the future I am building toward. Software that makes every hood cleaning company more professional, more compliant, and more profitable — and an industry culture that shares knowledge instead of hoarding it.

If that vision resonates with you, I would love to hear from you. Reach out at (855) 384-3591 or visit gethoodops.com. We are building this for the trade, and the trade's input makes it better.