Fractional COO for pest control

I run the operations.
Then I build the fix.

I'm Tyler Hermann, an operator and the COO of a multi-location pest control company. I help other owners run a tighter operation as a fractional COO, with the software I built for my own team and hands-on FieldRoutes help.

87%
lower cancellation rate in a region I ran at Fox Pest Control
+42%
productivity in that same region
25→65%
retention save rate I built at my current company
$1,200
a month in outside software, replaced by a tool I built
Consulting

Consulting from someone who still runs operations

Most of what I fix doesn't need software. It needs someone who has run the operation to sit with your team and find where the money and customers are going. I've led customer service, managed districts and analyzed fleet and operations data, and today I sit on an executive team.

Customer service & retention

Call center standards, callbacks and cancellation saves.

Field operations & fleet

Scheduling, missed stops and re-services, and what your trucks and GPS data are telling you.

Pay plans & payroll

Technician production pay and door-to-door commission that techs can check themselves and payroll doesn't dread.

KPIs & scorecards

Picking five or six numbers to watch, and a weekly meeting where someone owns each one.

FieldRoutes consulting

Setup, cleanup and getting more out of what you already pay for: workflows, reports, automations and connections to your other tools.

Hiring & training

Standards, onboarding and coaching for office and field teams.

Ways to work together

I only take on a few companies at a time.

Start here

Operations review

I dig into your calls, scheduling, pay and reports and hand you a ranked list of what to fix first. It's yours whether we keep working together or not.

Ongoing

Fractional COO

A set number of hours each month. I join your leadership meetings and own results alongside your team.

One problem

As-needed

One job, scoped and priced up front, like rebuilding your payroll or cleaning up FieldRoutes.

Software

Software I built for my own company

Each one started with something that kept going wrong at the company where I'm COO. The screens below use made-up data so you can see how each one works.

Command

Daily operations board

Office managers start the day digging through the CRM to find what slipped yesterday.

Command reads your CRM overnight, finds the callbacks and missed stops that got dropped, and gives each person a short list before they get in. Managers see every office on one board.

  • Each person sees only their own items
  • Managers see all offices on one screen
  • Tech scorecards go out on their own each morning

Production payroll

Technician pay takes hours to work out every pay period.

Pulls each technician's completed work from the CRM and calculates production pay on your pay plan, with totals ready for payroll instead of a spreadsheet rebuilt every two weeks.

Door-to-door payroll

Upfront now, backends months later, and usually a spreadsheet the reps argue with.

Connects to FieldRoutes and handles reps' pay from the first summer paycheck through the last backend check: upfront commission, end-of-season backends, monthly checks with leader overrides, and a plain-English statement with every check.

See everything it does

Daily KPI report

Leadership finds out about yesterday's numbers in next week's meeting.

Yesterday's stops, callbacks, saves and late clock-ins are in leadership's inbox by morning, each against its goal. Same report every day, and no one spends Monday building it.

Time & GPS check

A tech's timesheet and the truck's GPS don't always agree, and checking by hand eats a manager's morning.

Lines up each technician's clock-in and clock-out against when their truck actually started and parked. Real gaps land on the next morning's list, before they turn into a habit.

Rolling out to other companies now

Inventory

You find out a truck is out of bait when the tech calls from a customer's driveway.

Tracks product and equipment in the warehouse and on every truck, flags what's running low, and builds the reorder list so techs aren't caught short.

Coming soon

Training

A new tech learns the job however the person who trained them happens to do it.

Courses, quizzes and sign-offs for techs and office staff in one place. New hires train the same way every time, and managers see who's done, who's behind and who's ready to work on their own.

CRM add-ons

Your CSRs repeat the same clicks all day because the CRM has no shortcut for them.

Small add-ons that appear right on the CRM screens your office already uses: an account summary at a glance and one-click actions for the things they do by hand all day.

Running into something that isn't here?

Every tool above started as one annoying problem at one company. If yours isn't on the list, send it to me anyway.

Get in touch

Tyler Hermann

  1. Started in door-to-door sales
    Before moving into operations
  2. District management
  3. Operations analysis
    Including a 500-vehicle fleet
  4. Customer experience
    Built a customer experience division from scratch, then led customer service as director
  5. Chief Operating Officer
    Executive team, eight-figure multi-location company

I'm an operator, not a salesperson. I started in pest control selling door to door, then moved to the operations side. I managed districts, analyzed fleet and operations data, and built a customer experience division from scratch. Part of that was at Fox Pest Control, one of the largest companies in the industry.

Today I'm the COO of an eight-figure, multi-location pest control company. My company knows about this work and supports it, and every tool on this page started as a problem I had to solve there.

Hermann 37 is how I bring those tools, and that hands-on operating experience, to other pest control companies. I hold an undergraduate degree in human resources and I'm based in Utah.

Why 37

Small fixes, every day.

Get 1% better every day and a year later you’re about 37 times better. Slip 1% a day and there’s almost nothing left. Same small number, opposite directions.

That’s how I work with an operation. Not a big overhaul on day one, but a steady run of small fixes: a schedule that holds, a callback that actually gets made, a report someone reads every morning. Each one is small. Together they compound.

That’s the 37 in Hermann 37.

Questions owners ask

You have a full-time job. Does your employer know, and do you have time?

Yes to both. My employer knows and supports it, and I don't work with companies that compete with them in their markets. I keep the number of companies I take on small, and the software already exists, so setting it up for you doesn't start from zero.

Do I have to buy software to work with you?

No. Consulting stands on its own, and so does each tool. Plenty of problems get fixed with a process change and no software at all.

We're not on FieldRoutes. Does that matter?

The tools that work with your CRM were built on FieldRoutes. On another CRM it's a short conversation about what connects, and the add-on approach often works even where a full connection doesn't.

Do you work for FieldRoutes?

No. I run operations on FieldRoutes every day, so I know what it does well and where my office works around it. I’m not affiliated with FieldRoutes.

How fast can something be running?

For tools that already exist, the goal is a few weeks from the first call. Consulting can start with the first conversation.

What does it cost?

It depends on what's broken. After a first conversation you get a plain number: a fixed price for setup or a project, and a monthly rate for ongoing tools or fractional COO time.

What does the 37 in Hermann 37 mean?

It’s 1% better every day. Multiply 1.01 by itself 365 times and you get about 37.8, so a year of small daily improvements adds up to roughly 37 times better. It’s how I approach every operation I work with.

Tell me what's broken.

Send a couple of sentences about the problem: what it's costing you and what you've already tried. I'll write back and tell you if I can help and roughly what it would take.