What Scaling to 180 Employees Taught Me About Accountability

When Penebaker Enterprises had 12 employees, accountability was simple. I knew everyone. I knew what they were working on. I could walk a job site and see whether the work met our standards. If something was off, I had the conversation that day. There were no layers between me and the work. That directness was one of our biggest strengths, and it was the first thing I had to let go of as we grew.

By the time Roofed Right America hit 180 employees, the accountability system that worked at 12 people was not just ineffective. It was harmful. Trying to personally oversee every project, every crew, every customer interaction was creating bottlenecks. My team leads were not developing because I was not giving them room to lead. And the things I was not personally watching were slipping through the cracks because there was no system to catch them.

The breaking point

The breaking point came around 60 employees. We had a project in 2009 where the crew installed the wrong membrane on a 40,000-square-foot commercial roof. The crew lead had ordered the materials, the supplier had sent the wrong product, and nobody caught it until the building owner’s engineer flagged it during an inspection. The rework cost us over $80,000 and three weeks of schedule.

When I investigated, the root cause was not incompetence. It was a lack of verification systems. The crew lead assumed the supplier sent what was ordered. The supplier assumed the crew lead would verify. Nobody had a checklist or sign-off process for material verification. That gap existed because at 12 people, I was the verification system. I checked everything. At 60 people across multiple active projects, that was impossible.

That $80,000 mistake was the most expensive lesson I have ever received on the difference between personal accountability and systematic accountability. Personal accountability depends on one person paying attention. Systematic accountability builds verification into the process itself so that the right things happen regardless of who is working that day.

At Penebaker Enterprises, I hit that wall at about 35 employees. I was still trying to approve every material order, review every job estimate, and personally check on every active project. The business was growing but I was becoming the bottleneck. We missed a deadline on a hospital project because my approval was needed for a change order and I was tied up on another site for two days. That was the moment I realized my hands-on approach, which had built the company, was now the thing holding it back. The shift from doing to overseeing is one of the hardest transitions a founder makes.

Building the system

After that incident, we spent three months building an accountability framework that could scale. It had four components. First, clear metrics for every role. Not vague goals. Specific, measurable numbers that everyone could see. Revenue per rep, close rates, installation quality scores, customer satisfaction ratings. If you could not measure it, it was not a standard.

Second, weekly visibility. Every team lead reviewed their numbers weekly with their direct manager. Not monthly, not quarterly. Weekly. The shorter the feedback loop, the faster problems get addressed. A salesperson who is off pace in week two of the quarter has time to adjust. A salesperson who does not find out until week ten does not.

Third, documented processes for the work that mattered most. Material verification, quality inspections, customer communication protocols. Written down, trained on, and audited. Not because we did not trust our people, but because even good people make mistakes when there is no process to catch them.

Fourth, consequences that were predictable and consistent. Same standard for every crew, every market, every team lead. When accountability is applied unevenly, it breeds resentment. The top performer who gets a pass on quality standards teaches everyone else that the standards are optional.

What most leaders get wrong about accountability

Most leaders think accountability is about catching people doing things wrong. It is not. Accountability is about creating an environment where the right behaviors happen naturally because the systems support them and the expectations are clear. If you are constantly catching problems, your systems are broken. Good accountability is mostly invisible because it prevents issues rather than punishing them.

The other mistake I see is leaders who confuse activity with accountability. They track hours worked, emails sent, meetings attended. Those are inputs, not outcomes. I do not care how many hours someone works if their close rate is below standard. I do not care how many emails they send if their customer satisfaction scores are declining. Track the outcomes that matter and give people the autonomy to achieve them in whatever way works best for them.

At Roofed Right America, we had a sales rep who worked fewer hours than anyone on the team. He also had the highest close rate and the best customer reviews. Under an activity-based accountability system, he would have been flagged as underperforming. Under an outcome-based system, he was our best performer. The distinction matters.

I have seen managers who track every minute of their team’s time and still cannot figure out why productivity is declining. The answer is usually that people perform differently when they feel watched versus when they feel trusted. At Great Day Improvements, I made a deliberate choice to measure outcomes rather than activity. I do not care if a design consultant spends two hours on a presentation instead of one, as long as the close rate reflects the effort. When you shift accountability from inputs to outcomes, people start thinking like owners rather than employees.

Accountability across multiple markets

At Great Day Improvements, accountability gets more complex because I am managing four markets that I cannot be physically present in every day. The temptation is to over-rely on the metrics and manage by spreadsheet. That does not work either. Numbers tell you what is happening but not why. A dip in close rates could mean the sales team needs coaching, the lead quality dropped, or the competitive environment changed. Without context, you make the wrong diagnosis.

My approach is to combine the data with regular presence. I visit each market often enough that the teams know I am paying attention and engaged, not just monitoring from a distance. During those visits, I sit in on sales appointments, ride along on installations, and talk to customers. The things I learn in those interactions fill the gaps that the data cannot capture.

I also make sure each market has a leader who owns accountability locally. Not someone who just reports numbers up the chain, but someone who has the authority and willingness to have the hard conversations in real time. Accountability delayed is accountability denied. If a quality issue happens on Monday and nobody addresses it until I visit on Thursday, that is three days of reinforcing the wrong behavior.

The other piece that matters in multi-market accountability is consistency of standards. What is acceptable in the Milwaukee branch has to be acceptable in Chicago, Madison, and Minneapolis. The moment you allow different standards in different locations, you create a two-tier system where people feel the rules depend on geography rather than values. I hold the same calibration meetings across all four markets and share performance data openly so that every team can see where they stand relative to their peers. Healthy competition requires transparent and fair rules.

The human side of accountability

Systems and metrics are necessary, but accountability is ultimately a human interaction. The way you deliver feedback matters as much as the feedback itself. I have seen managers who have the right message but deliver it in a way that makes people defensive rather than motivated. Public criticism, sarcasm, comparing people to their peers in front of the team. All of those destroy the thing you are trying to build.

The best accountability conversations I have had followed a simple structure. Start with the data. “Your close rate this month is 18 percent. Our standard is 25 percent.” Then ask what is going on. Listen. Then work together on a plan. “What do you need from me to get back on track?” That approach preserves the person’s dignity while being completely clear about the gap.

The hardest part is when someone is consistently below standard despite coaching, support, and clear expectations. At that point, accountability means having an honest conversation about whether the role is the right fit. Not in a punitive way. In a way that respects the person enough to be straight with them. Keeping someone in a role they cannot succeed in is not compassion. It is avoidance dressed up as kindness.

Scaling accountability from 12 people to 180 taught me that the leader’s job changes at every stage. At the beginning, you are the accountability system. In the middle, you are building the accountability system. At scale, you are maintaining and improving the system while trusting the people inside it to do their jobs. Each transition requires letting go of the previous version of leadership. The leaders who cannot let go are the ones whose companies stop growing.

Last updated: March 9, 2026