Operations

Your Accounting Firm’s Biggest Structural Problem Is Something You Built on Purpose

Earmark Team · May 31, 2026 ·

You built a successful accounting firm, and now you’re trapped inside it. Every client question routes through you. Every tax return needs your eyes before it goes out the door. Your team is talented, but no one knows whose desk the work is on, and your clients couldn’t name their accountant if you asked them to.

Sound familiar?

Unfortunately, you probably built the structure causing all this pain with the best of intentions.

In this episode of Who’s Really the BOSS?, Marcus and Rachel Dillon pull back the curtain on how they restructured their firm, Dillon Business Advisors (DBA), from a bottlenecked, siloed operation into a scalable team-based model. They walk through the exact phased transition that made it work, including the hard conversations, the timing decisions, the mistakes, and the results.

One lesson they learned the hard way, and they keep seeing other firms stumble over it: the biggest mistake accounting firm owners make when restructuring is skipping straight to the end state without working through the messy middle. Building a firm that doesn’t revolve around you requires a phased transition. First, define the roles. Then align the teams and optimize for industry niches. Get the sequence right, and you unlock collaboration, capacity, and career growth for your people. Skip steps, and you’ll create more chaos than you started with.

Let’s break down what that transition actually looks like, starting with the pain points that tell you your current structure is broken, moving through the three phases DBA used to go from chaos to clarity, and ending with what becomes possible on the other side.

The Problem Hiding Behind Good Intentions

Before you can fix your firm’s structure, you have to be honest about what’s broken. What makes this tricky is, the thing that’s broken is probably something you built on purpose.

Marcus describes the symptoms DBA experienced, and they’ll sound painfully familiar to most firm owners. Despite having project management software that technically showed the status of every project, they still didn’t really know where work was. Not in the way that matters, like what a team member was actually waiting on, or why something hadn’t moved in three days. When someone needed time off, or worse, left the firm, there was no reliable way to pick up where they left off without a scramble.

Then there was the silo problem, and this one stings because it started as a smart idea. DBA intentionally created three separate teams: one for individual tax, one for business tax, and one for accounting. On paper, it looked like specialization. In practice, it built unintentional walls.

“The accounting would be done and then passed the baton to the business tax team,” Marcus explains. “The business tax team would do tax returns, and then pass things over to the individual tax team.” The business tax team would be busy at certain times of the year, completely dependent on the accounting team to deliver clean financials, but they had no visibility into what was on that team’s plate. Meanwhile, the individual tax team sat idle, waiting on K-1s, unable to push the process forward or even understand why things were delayed.

Marcus was at the center of it all. Every return needed his review. Every client conversation required his voice. The org chart was a bull’s eye with him in the middle. “I was definitely the bottleneck,” he admits. “I had to have eyes on everything before it went out to a client. It had to be me calling or sitting down with the client.”

The damage wasn’t just internal. Rachel adds the client perspective, and it’s equally sobering. “Clients really didn’t know who their point person was. So when they called, they would ask for Marcus, or they would say, ‘I don’t know who’s working on my tax return’ or ‘I don’t know who’s working on my accounting.'” Things would get lost in translation from person to person. Clients wanted two things the structure simply couldn’t deliver: fast responses and proactive advice.

That’s the real cost of a structure built around one person. It’s not just that the owner burns out. Client experience degrades. Your team knows who they’re working with, but your clients don’t. And when clients feel uncertain about who’s handling their finances, trust erodes until it’s too late.

The Three Phases From Scaffolding to Scale

This is where Marcus and Rachel’s conversation gets practical. They walk through a three-phase approach that DBA used to transition from their old structure to the Team of Three model. Each phase builds on the one before it. Skip ahead, and you’ll pay for it later.

Phase 1: Define the Roles (Build the Scaffolding)

Before you can organize teams, you need to know what roles exist. DBA’s Team of Three consists of three clearly defined positions:

Client Service Manager (CSM). The base of the team. Marcus describes them as “an accountant, a bookkeeper, somebody with experience who doesn’t have to have a degree.” Many of DBA’s CSMs are working parents who want a career that offers flexibility alongside meaningful work. They operate at 85% capacity, with 15% reserved for onboarding new clients and handling the inevitable surprises.
Client Controller. Someone with tax experience who has “seen accounting and done closeouts,” Marcus explains. “Maybe they’ve done the bookkeeping cleanup at year end, and they can produce clean financials.” They can prepare business tax returns and advise on personal and business tax matters. When DBA hires for this role, they post it as “tax manager” because posting “client controller” attracts candidates who misunderstand the position.
Client CFO. This person manages the team and drives the client relationship. “They can have larger business strategy and tax-related conversations with clients as needed or consistently throughout the year,” Marcus notes. Business ownership experience is a big plus here because it gives them risk tolerance and the ability to connect with entrepreneurial clients.

With those three roles defined, DBA assessed its existing team and started mapping people into positions. Some placements were obvious. Others required difficult conversations.

“We didn’t want to force people into a certain role,” Marcus explains. They had direct conversations with team members. “Here are the guidelines of each role, here’s what each one would do. What would you like to do? Where do you feel most comfortable?”

Rachel adds an important nuance about those conversations. “There were team members who had been with us a long time, and they were leaders within our firm. They were experienced, degreed and very good accountants. But if you think about it vertically, they’re the bottom.” It was important to help them understand that CSMs have significant client interaction and hold important relationships. They found other ways for these team members to lead through onboarding, training, mentoring, or becoming subject matter experts.

Marcus admits to a mistake from this phase. “We kept some people on too long. They clearly weren’t fully a client controller. They had a leg in CSM and another in Client Controller for just a little bit too long. And it didn’t work out.”

Phase 2: Align the Teams (Set the Team Structure)

Phase 2 is where the real transformation happens, and where it often breaks down for other firms.

After Phase 1, DBA had people in defined roles. But those people weren’t working in consistent teams. “Even with myself as maybe the only client CFO at that time, we had close to 40 different teams of three within our team of 12 or 10 FTEs,” Marcus reveals.

Rachel paints the picture. “A CSM on our team was working with three different controllers. So three people give her work, ask her questions or request things from her. During tax season, everyone’s busy. Who do I prioritize work for?”

The solution was a deliberate reorganization and locking in which three people would serve which clients. DBA used a straightforward decision framework. If two of the three team members were already working with a client, those two stayed. Swapping out two of three required exceptional justification, such as a team member having a relationship that overrode the numbers.

The timing was strategic. They planned the reorg in March and April, then communicated it to clients after tax season. “After tax season, we actually pushed through the reorg and communicated to clients,” Marcus explains.

Clients reacted well. “They said, ‘Okay, we know you have what’s in our best interest. We trust you. I didn’t lose my person.'”

The internal results were dramatic and fast. “Within a month, efficiencies and budgets improved,” Marcus reports.

Phase 3: Optimize and Refine (Industry Niches and Career Paths)

With teams aligned and running smoothly, DBA could finally build industry specializations. They organized pods around verticals: dental, veterinary, and medical professional services. Construction and real estate were sprinkled across every team, since many clients own real estate.

This created real advisory value. “When I have advisory conversations, that’s what they typically ask me: ‘Well, how’s everybody else doing?” Marcus shares. “Because I want to know, am I the only one who’s going through this difficult time?”

Phase 3 also made career progression visible. “It gives people a clear path to move if they want to do that career ladder,” Marcus explains.

Marcus’s own evolution shows the ultimate success. “I’ve given away clients and team members to other people who are progressing in their careers.” He adds, “After the client meets the team, they forget about me.”

“Sometimes starting at phase three is the problem, or not doing phase one and phase two well,” Marcus warns. “The firms that have success with this start with role definition and then move to defining teams and then optimizing or refining.”

What The Right Sequence Unlocks

Step back and look at what DBA built through this phased approach. Each phase created the foundation for the next breakthrough.

Collaboration over silos. Teams know each other’s workloads and can step in when needed. There’s no single point of failure on any client. “If a team member needs to be out, the client is still going to be fully served and their team is available,” Rachel explains.
Consistency through tax season. Marcus calls out a common industry problem where firms sell clients on recurring advisory work, then stop delivering it from January through April. “You should have the bandwidth and the capacity to serve those clients consistently all year long, including tax season. If you’re signing somebody up for recurring ongoing financial support, which is what most people do in CAS, you have to do that consistently.”
Real capacity for growth. After the Phase 2 reorg, Rachel notes, “Those team members actually had enough capacity to take on clients without being overloaded with work or going above their peak capacity.”
Career development without departure. Team members don’t have to leave to advance. Marcus shares, “Our team members don’t have to go outside of DBA to continue to progress in their careers.”

Marcus and Rachel have seen what happens when firms skip steps. Firms that jump straight to building industry pods without first defining roles end up with confused team members. Firms that try to align teams without clear role definitions create accountability structures with nothing to be accountable to.

The sequence is the architecture that makes everything else work.

Your Move: Define, Align, Then Optimize

The Team of Three model gave DBA a destination. But the phased transition got them there. Most firm owners who struggle with restructuring try to implement the final version on day one.

Whether your firm has five team members or 50, the principles hold: clarity before alignment, alignment before optimization. Your team needs to know their role before they can function as a unit. Units need to gel before you can specialize.

If you’re feeling stuck as the bottleneck in your firm, or you’ve tried restructuring and it created more chaos than clarity, Marcus and Rachel share more details about each phase in this episode of Who’s Really the BOSS?. They discuss the specific mistakes they made and how they coach other firms through the same transition.

Marcus closes with an invitation: “We have a lot of resources. If anybody wants to reach out about any of those resources, job descriptions, benchmarks, scorecards, all that fun stuff. We have those in the Collective community. But if something is sticking out, please reach out.”

Listen to the full episode to hear their complete breakdown of how to build an accounting firm structure that actually works.

Rachel and Marcus Dillon, CPA, own a Texas-based, remote client accounting and advisory services firm, Dillon Business Advisors, with a team of 15 professionals. Their latest organization, Collective by DBA, supports and guides accounting firm owners and leaders with firm resources, education, and operational strategy through community, groups, and one-on-one advisory.

Why Your Team Resists Change and the Simple Framework That Fixes It

Earmark Team · May 19, 2026 ·

A client builds an AI-powered dashboard, gets his CPA to validate it, then turns around and asks, “So what value do you bring that I can’t get from this thing?” The CPA doesn’t have a great answer. Services get scaled back.

Meanwhile, an oral surgery practice with four doctors and $8 million in annual revenue is still running QuickBooks Desktop, booking revenue through monthly adjusting journal entries, and entering its entire American Express bill as a single payment each month. They haven’t updated a single process since they founded the business decades ago. Both of these clients exist right now, and they could both be sitting in your pipeline this week.

That’s the change landscape accounting firm leaders navigate today. And if you think the biggest threat is AI or the private equity money flooding into the profession, Marcus and Rachel Dillon say you’re looking at the wrong problem.

In this episode of Who’s Really the BOSS?, the Dillons, owners of Dillon Business Advisors, make the case that the real risk isn’t the change itself. It’s how you lead your people through it. Drawing on real client stories, their own leadership missteps, and a framework borrowed from Patrick Lencioni, they lay out a practical approach to change management any firm leader can start using immediately.

The Change Landscape: From Silicon Valley to Main Street

Before you can bring your team through change, you need to understand what you’re actually up against. The answer depends on where you’re standing.

Marcus spends time networking with partners at top-20 and top-100 firms with $60 million or more in revenue. What he hears from those conversations tends toward doomsday. These firms serve private equity-backed businesses whose principals all have finance or business backgrounds. Those clients are leaning hard into AI, meaning the professionals serving them have to keep pace or move faster.

One leader at a larger firm told Marcus he no longer opens conversations with “How are the kids?” Instead, the first question he asks clients, prospects, and peers is, “How are you using AI today?”

“If your clients are changing faster than you are,” Marcus explains, “you’re going to be the weakest link in that relationship, and they’re going to move on faster than you can.”

The Big Four are already placing their bets. PwC is doubling down on technology and AI at the entry level, slashing recruiting and campus visits. If that layer of the workforce shrinks, they don’t need to wine and dine as many college students. EY is taking a different approach, doubling its CPA exam pass bonus to $10,000 and investing in the human side.

But while Silicon Valley types are sounding the alarm, Main Street tells a different story.

Remember that oral surgery practice? The lead doctor told Marcus they set up the business nearly 30 years ago and never updated their processes because the same team has been in place the whole time.

DBA’s plan for this client is to set up QuickBooks Online, enable bank feeds, connect them to a service like Ramp, and automate the revenue journal entry. Low-hanging fruit by any modern standard.

“You have to choose how analog you want to exist in this digital world,” Marcus says. The clients who want a human touch continue to pay a premium for it. A purely digital product, he argues, is a race to the bottom.

When Change Communication Goes Wrong

Marcus doesn’t sugarcoat DBA’s early track record on change communication. When the firm merged in another practice nearly a decade ago, Marcus was so excited about the acquisition that he gathered everyone in the conference room and essentially announced it cold. Most team members were hearing about it for the first time.

“That probably didn’t go over as well as I could have hoped,” he admits.

The fallout from moments like this is bad. People disengage. The service atmosphere turns mediocre. Tension builds. Marcus found himself labeled “addicted to change,” which bred resistance rather than readiness.

“If you don’t work on your culture, you still have a culture,” he says. “It’s just unintentional. The same can be said of change.”

Rachel offers the perspective from the other side. When she talks to team members about why they push back on change, the answer is almost always a lack of clarity. They don’t understand why it’s important. They can’t see how it impacts them personally.

“A lot of times it feels like, ‘This is going to take me longer and I’m going to have to work more. And I don’t have any more hours or capacity left to give,'” Rachel explains.

The Dillons evolved toward a three-question framework:

What is changing?
What is staying the same?
How does this impact me?

It was an improvement, but still incomplete. It only addressed the team’s perspective, not clients or other stakeholders.

A peer group introduced Marcus to Patrick Lencioni’s Four Ps framework. The Dillons adopted it as their change-management filter and introduced it to the team at their recent Gather event alongside their rally cry for 2026: “Lead change, create impact.”

The Four Ps: Your Repeatable Framework for Leading Change

The framework gives firm leaders four sequential steps to follow every time they introduce change, whether it’s a new tech stack, a team restructuring, or a client exit strategy.

Purpose: What are we changing?

You need to anchor every change in something bigger than “we found a cool new tool.” At DBA, that anchor is their mission, vision, and values. Their core values spell out the word IMPACT, and Rachel describes how they literally map each proposed change back to specific letters in that acronym.

The trap most leaders fall into here is vagueness. Marcus admits he’s guilty of softening language because he wants to be liked and avoiding directness to dodge conflict.

“Just tell me what you expect. Just tell me what you need me to do,” Rachel says. “People don’t want 20 options. They want one or two.”

Marcus borrows from Andy Stanley: “To be clear is to be kind. To be unclear is to be unkind.”

“If you can’t clearly say what’s changing, the team will default to their comfort level,” Marcus warns. “Which means they’ll do as little as possible.”

Picture: What does success look like?

Leaders often skip this step. They explain what’s changing and how it will happen, but they never describe what winning looks like on the other side.

Marcus uses a family vacation analogy. You decide to take a trip (that’s the purpose). Now tell the kids you’re going to Disneyland and describe the destination so everyone can see it.

In a firm context, that might mean showing the team what life looks like after implementing a team-of-three service model: predictable capacity, no more overtime scrambles, better client satisfaction scores.

The Dillons deploy an exercise called Optimist/Pessimist. Pair people up. One person must articulate at least one or two positives about the proposed change. The other must find negatives. This gives explicit permission to voice concerns that would otherwise get whispered in private channels.

“Once we are sick of saying the same thing over and over again, they’ve actually received it, processed it, and can carry it out,” Rachel says.

Plan: How do we get there?

The plan phase breaks the picture into executable steps. Extending the road trip metaphor, explain whether you’re flying or driving. If driving, are you taking the scenic route? Where do you pull over to celebrate progress?

Rachel emphasizes two non-negotiables for every step: a responsible person and a deadline. Each milestone needs an owner and a date, so there’s no ambiguity about who’s doing what by when.

This is also where you appoint change agents from within your team. Team members who showed energy during the Picture phase are natural candidates to lead portions of the execution.

“A simple plan executed beats a perfect plan that’s been delayed,” Marcus notes.

Part: What’s my role in this?

Every single person needs to understand their role, including those whose role is “nothing changes for you.”

Marcus shares a recent example from DBA’s acquisition work. For some team members, the message was, “Keep serving your current clients well. You’re not getting new clients from this acquisition. You’re not learning a new process or technology.”

Simply telling people “your job stays the same” is just as critical as the detailed instructions given to people at the center of the transition.

When you don’t tell people their part, they default to their worst experience. Maybe a previous boss promised “nothing will change” and then changed everything. You can’t control the baggage people carry, but you can replace old narratives with present-tense clarity.

This step requires a conversation, not an email. People need two-way dialogue where they can ask questions and process in real time.

Leading Through the Messy Middle

Marcus closes with an honest confession. “I’m as guilty as anybody. I want to initiate the change. And I want all the fruit from the success of that change. I don’t want to live through the change. I want to just speed through it or delegate it.”

Successful firms have leaders who bring their people through change intentionally, with clarity, conviction, and care.

The Four Ps give you a repeatable filter for any transition:

Purpose: Anchor the change in your mission and values and say it plainly
Picture: Show people what success looks like, then repeat until you’re sick of it
Plan: Break the vision into steps with owners and deadlines
Part: Tell everyone their role in a live conversation, not an email

Whether you’re navigating a firm acquisition, a technology overhaul, or wondering how fast AI is coming for your services, the same four questions apply. As the Dillons put it, the goal for 2026 is to lead change and create impact.

Listen to the full episode to hear Marcus’s take on how fast AI is really moving, Rachel’s breakdown of the Optimist/Pessimist exercise in action, and why moving homes during busy season might actually make perfect sense for a couple “addicted to change.”

The 90 Days After Closing That Most Firm Buyers Never Talk About

Earmark Team · February 17, 2026 ·

When an accounting firm announces an acquisition, the industry responds with congratulations and LinkedIn likes before quickly moving on. But for the acquiring firm, that’s when the real work begins and when most deals quietly succeed or fail.

In a recent episode of Who’s Really the BOSS?, Marcus and Rachel Dillon sit down with Amy McCarty, MBA, to discuss what actually happens after signing on the dotted line. Having completed two acquisitions in 2025—one in January and another on October 1—the Dillon Business Advisors (DBA) team shares the specific decisions, timelines, and hard-won lessons that transformed signed deals into a unified firm.

When “Growth, Not Comfort” Means More Than You Bargained For

At the start of 2025, Marcus proposed “growth, not comfort” as DBA’s rally cry for the year. Rachel and Amy thought he meant leadership development and personal growth. They discovered later he had something else in mind entirely.

“You totally tricked us,” Rachel tells Marcus during the podcast. “You said it was completely about leadership growth and personal and professional development. You never let on that this was really about revenue, team size, acquisitions.”

Marcus’s real motivation was building the budget to hire director-level talent. The firm brought on Angel Sabino as Director of Technology in January and Arin Neucks, CPA, CFP, as Director of Tax and Financial Planning in August. Supporting these hires required top-line growth, and acquisitions offered the fastest path to it.

“To have the budget to do great things, the top line had to grow a little bit,” Marcus admits with characteristic understatement.

The first acquisition closed in January with a longtime friend from a consulting organization. It was intentionally small, what Marcus calls a “dip your toes in the water acquisition.” They retained most of the revenue and one excellent team member who now has a clear career path at DBA.

After news of the January acquisition spread through their St. Louis market, other firm owners approached them directly, asking to be considered for future acquisitions. By Q2, DBA was in serious discussions about a second acquisition that would be three times the size of the first.

The First 30 Days: Change Nothing (Except Communication)

The October 1 acquisition created an immediate challenge because it closed just two weeks before the October 15 tax deadline. DBA’s response was counterintuitive but crucial: they changed almost nothing.

“The biggest changes for them are the name of the company that they worked for changed, and where they’re getting their paycheck from changed,” Amy explains. “But otherwise, same clients, same daily functions.”

This restraint matters because acquired team members arrive in a fundamentally different situation than new hires. A new employee has time to learn systems and absorb culture. An acquired team member comes with a full client roster and deadlines that can’t wait. DBA’s standard two-week onboarding stretched to four to six weeks for acquired teams, with the timeline threaded between ongoing client work.

The single exception to the “change nothing” rule was communication infrastructure. Getting the acquired team into Microsoft Teams became the only day-one priority, even though the acquired firm ran on Google and Slack. Angel worked his technical magic to make it happen.

“That is where we live from an internal communication standpoint,” Amy notes. Without unified communication, the teams coordinated work via email, creating delays and missed context they couldn’t afford during the integration.

This stability was possible because they laid the groundwork long before closing. In late September, DBA visited the acquired team in person to present job offers and handbooks. Rachel initially thought this pre-close access seemed risky. She learned it’s actually common practice. Some private-equity-backed firms even begin data migration before deals close.

Days 31-60: Methodical Technology Migration

After maintaining stability through the October deadline, DBA began the complex work of technology consolidation. The preparation made all the difference.

When Angel joined as Director of Technology, he knew acquisitions were coming. Within 30 days—while tax season was underway—he built an enterprise-level Azure environment from scratch. This meant when October’s acquisition arrived, DBA had infrastructure ready to absorb new users rather than scrambling to build it during integration.

Similar tech stacks between firms simplified everything. Both acquired firms used Thomson Reuters UltraTax and QuickBooks Online, matching DBA’s setup. This synergy was a factor in acquisition decisions.

Where systems differed, results varied. Intuit’s realm consolidation tool worked beautifully. Marcus migrated all the acquired firm’s QuickBooks accounts from his phone’s hotspot while driving to his child’s swim meet. ADP proved more challenging because they wanted to re-onboard clients with new signatures. Rather than confuse clients, DBA maintained two separate ADP logins and will migrate opportunistically over time.

Client communication platforms required careful handling. Both acquired firms used Liscio, while DBA uses Canopy. For the January acquisition, DBA kept Liscio running through tax season before transitioning. The October firm had already been planning its own Canopy migration.

“We told them, ‘We love that you’re going to be on Canopy. Why don’t you hold off on that migration for now?”‘ Marcus recalls. “Because we’re going to have to migrate everything into DBA anyway.”

For systems they couldn’t immediately eliminate, Amy reduced subscriptions to the minimum level rather than canceling them completely. “It’s like when you clean your closet, and you turn the hanger the other way,” she explains. “If you don’t ever use it, then you need to get rid of it.”

Protecting the Cash Flow You Bought

“From a business owner standpoint, I would much rather talk about getting paid and sales and receipts and deposits over tax returns and general ledgers,” Marcus says bluntly.

The revenue structure of the October acquisition required immediate attention. Two-thirds was monthly recurring revenue with auto-drafted payments. Without intervention, that money would continue to flow into the previous owners’ bank accounts.

Rather than rushing clients onto new systems during integration chaos, DBA kept the acquired firm’s payment processor running for three months. The previous owners were a husband-and-wife team, with the husband joining DBA. They agreed to reconcile deposits and forward funds within days. This required an enormous amount of trust, built during 90 days of pre-close due diligence.

The arrangement had a natural endpoint. Monthly clients’ annual agreements expired with their January payment, creating a perfect transition moment. DBA sent new engagement letters with updated payment information to all DBA clients, using the acquisition as a catalyst for firm-wide standardization.

Alison Sharp, the operations and administrative professional who came over from the acquired firm, proved invaluable during this transition. She handled client communications about payment changes, maintaining continuity for clients who knew and trusted her.

Looking Ahead to Tax Season and Beyond

As 2026 begins, DBA faces its first full tax season serving both acquired client bases. The January-acquisition clients are returning for their second year, while the October clients will experience DBA’s processes for the first time.

“It’s going to be a fun tax season,” Amy says with a laugh that suggests “fun” might be understating the challenge.

The integration work continues, but with infrastructure in place and teams unified in communication and technology, DBA has transformed two separate acquisitions into growth that actually supports their expanded director team, even if that wasn’t quite what Rachel and Amy thought they were signing up for with “growth, not comfort.”

For accounting firms considering acquisitions, the DBA team’s experience shows how crucial it is to invest as much in planning the 90 days after closing as you do in the months before. The deal terms matter, but integration execution determines whether you build something lasting or buy an expensive headache. Listen to the full episode for all the details.

Your Team Actually Wants You Less Involved in Daily Operations—Here’s How to Give Them What They Need

Blake Oliver · November 25, 2025 ·

For an accounting firm owner, days can feel like an endless stream of Slack notifications and “quick questions” from your team. You’ve become your company’s “internal Wikipedia”—the go-to source for every operational decision, client question, and process clarification. Sound familiar?

Chase Damiano, founder of Human at Scale and recent guest on the Earmark Podcast, has a name for this trap: the bottleneck.

Damiano brings a unique perspective to the accounting world. After scaling Commonwealth Joe Coffee Roasters from zero to $5 million in revenue and earning a spot on Forbes’ 30 Under 30 list in 2018, he experienced burnout so severe it drove him to take a 12-week sabbatical that included two weeks of silent meditation. This radical reset transformed his understanding of leadership and delegation. Now, he shares those insights with accounting firm leaders trapped in similar operational quicksand.

In his conversation with host Blake Oliver on the Earmark Podcast, Damiano challenges a fundamental assumption plaguing firm owners: the belief that hiring more people will solve their capacity problems. The reality is far more complex. Breaking free requires a systematic approach to delegation that transforms how you communicate expectations and how you measure success.

Every overwhelmed firm owner needs to understand three critical transformations. First, why the traits that make you successful—perfectionism and desire to serve—become the quicksand that traps you. Second, how a six-part delegation framework frees you from daily firefighting. And third, why building a “team responsibility inventory” provides the roadmap for extracting yourself from workflows while actually increasing your team’s autonomy.

The Psychology of Being Stuck: Why Good Intentions Create Bad Systems

Before you can implement systematic delegation, you need to recognize that the very traits that made you successful now hold your firm hostage.

Damiano knows this pattern intimately. After scaling his coffee company to $5 million in revenue, he found himself addicted to the productivity habit. It took three full weeks of his sabbatical just to stop compulsively “figuring things out.”

“Even the act of ‘figuring out your life’ can now look more like a job,” he explained to Oliver. “Wake up, have breakfast, go to a coffee shop to figure things out. Then it’s time for lunch, more figuring out, dinner—and suddenly another day has vanished.”

This addiction to busyness hits accounting firm owners particularly hard. Your perfectionism, your genuine desire to serve clients, and your technical expertise aren’t character flaws. They’re the foundation of your professional success. But when it comes to scaling a firm, they become quicksand.

Oliver admits he fell into this exact trap with his own firm. “I said yes to everything,” he reflected during the conversation, “and then I’ve got too much to do and I’m busy all the time, working 60 hour weeks.”

The desire to help everyone feels noble in the moment. But it creates a system where your brain becomes the firm’s operating system. Every decision, every quality check, every client question routes through you.

The perfectionism problem runs deeper than just workload. Oliver shared an example from his time at a Big Four firm. The nonprofit team was performing full compilation engagements for clients who didn’t need them. “Most of these nonprofits did not need compilations, but we were doing it anyway with a huge added cost,” he observed. The team could have delivered a simpler service at better margins while still meeting client needs.

Damiano challenges firm owners to examine their “inner data”—not financial metrics, but the intuitive signals about energy and alignment. When he asks bottlenecked CEOs how they feel day-to-day, the answer is always the same: “incredibly draining,” “incredibly stressed,” “I don’t want to do this.”

Yet the pattern continues. They know they’re stuck, they can articulate the problem, but they take no action to change it.

This paralysis stems from a fundamental identity crisis. As Damiano discovered after exiting his coffee company, entrepreneurs often don’t know who they are without their business. “Everyone asked me what I’m going to get into next.” he recalled. “People assume you’re going to go on to an even greater thing, but you might not be clear about that internally, and that’s okay.”

The reality check comes when you realize your team actually wants you less involved. Teams see your pain from being overwhelmed. But more importantly, they experience frustration when you inject yourself into processes and “muck things up,” as Damiano puts it.

Your team craves autonomy over their roles. They want to make decisions without running everything by you. But first, you need to accept that your five-minute solution might be worth sacrificing for their two-hour learning experience.

Damiano’s perspective on one-on-ones captures the mindset shift required: “Your one-on-ones should not be about status updates. It’s an opportunity to develop them as leaders in every role, in every position. They should do 80 plus percent of the talking.”

Understanding these psychological barriers is crucial, but awareness alone won’t free you from the trap. You need a concrete system for transferring responsibilities that addresses both your need for quality and your team’s need for clarity.

The Six-Part Delegation Framework: From Chaos to Clarity

The breakthrough moment in Oliver and Damiano’s conversation came when Oliver realized effective delegation to humans uses the exact same structure as prompt engineering for AI.

“What you just described is a well-written prompt,” Oliver exclaimed as Damiano outlined his delegation system. “It’s the same thing.”

This revelation transforms delegation from an art into a science. The framework emerged from Damiano’s observation of countless delegation failures. One particularly instructive disaster involved a chief operating officer who attempted to delegate a billing process. She wrote just seven words on a piece of paper: “Manage billing process while I’m out on vacation.”

The predictable result? Complete failure. Without context, success criteria, or clear boundaries, the delegation was doomed from the start.

During the podcast, Damiano and Oliver worked through a real example: delegating the management of weekly team meetings. Here’s how the framework transformed this common bottleneck into a clear, delegatable responsibility:

1. Name the responsibility: “Manage and coordinate weekly team sync.” Just two to three sentences that start with action verbs.

2. Define the purpose: As Oliver articulated: “Our weekly team sync is what keeps everyone organized and makes sure nothing falls through the cracks. It helps us prioritize.” Damiano added, “This is our command center for what is happening for the week, but also a place for us to come together as a culture.”

3. Establish success metrics: “Everybody leaves the meeting with their top three to five priorities clearly defined. We’ve addressed any blockers,” Oliver said. Plus the binary metric: Did the meeting happen? Did everyone who could attend actually attend?

4. Document the process: They mapped out everything from sending meeting invites and creating agendas to collecting topics, facilitating discussions, and updating the practice management system.

5. Identify resources: Access to calendars, ability to run reports on upcoming deadlines, time for preparation and follow-up. “In a prompt that would be the tools,” Oliver noted.

6. Clarify decisions: The operations manager can choose meeting times and create agendas autonomously, but needs approval to cancel meetings two weeks in a row.

The elegance of this system lies in its flexibility. “Those first three are perfect delegation opportunities for a more senior individual,” Damiano explains. Junior team members benefit from all six elements as guardrails.

What makes this framework powerful is how it addresses trust issues that sabotage most delegation attempts. When delegation fails using this structure, you can pinpoint exactly what went wrong.

“You can literally look at it and pinpoint exactly where,” Damiano says. “And that is what makes the delegation stick, because you can just fix that one issue.”

The framework also flips the traditional delegation dynamic. Instead of the owner having to document everything, team members can use these six elements as a guide to ask better questions. This transforms delegation from a top-down directive into a collaborative process.

Oliver’s enthusiasm was immediate: “I’m going to start using this. I’m going to do this tomorrow with my team.”

The framework addresses his core challenge: getting his team to take ownership without constantly coming to him for decisions. By clearly defining decision boundaries upfront, team members gain confidence to act autonomously while knowing exactly when to escalate.

But individual delegation is just the beginning. True transformation requires examining every responsibility across the entire firm.

Building Your Delegation Roadmap: The Path to Strategic Leadership

Moving from technician to strategic architect demands a systematic inventory and redistribution of all responsibilities across your firm.

Damiano calls this process building a “Team Responsibility Inventory.” As Oliver discovered with his own 16-person company, you can reach a point where founders are still doing work from when the company was half its size.

“We’re the bottleneck,” he admitted, recognizing how he and his partner had become “functionally critical participants in the workflow” even though they now had a team capable of handling that work.

The Team Responsibility Inventory begins with radical transparency. Every team member completes a seven-day time audit, brain-dumping every task and responsibility they handle. No organization needed, just raw data.

Then comes the revolutionary part: a facilitated session to compile all these responsibilities and review them line by line as a company. For many firms, this marks the first time the team sees exactly what’s on the CEO’s plate.

“Imagine you’re going line by line through these responsibilities and as a team making a decision,” Damiano explains. “Should the CEO still have this responsibility?”

The power of this collective review can’t be overstated. Team members who’ve been frustrated by their CEO’s constant intervention suddenly understand the impossible workload their leader carries. More importantly, they become active participants in solving the problem.

Each responsibility faces one of six possible destinies: hire someone, delegate and train internally, outsource to a service provider, automate through software, consciously eliminate, or keep.

The elimination option deserves special attention. “This is an underused one,” Damiano emphasizes. After years of growth, firms accumulate zombie tasks—reports nobody reads, processes that served a purpose five years ago.

Oliver shared the perfect example: “There’s all these people running weekly, monthly, quarterly reports that were defined five years ago that they’ve been sending out constantly and nobody’s actually reading them.”

The delegation roadmap shows how responsibilities shifts over time. But successful execution requires developing your team’s decision-making capabilities, not just their technical skills.

This is where Damiano’s “Problem-Outcome-Solution Framework” comes in. Instead of bringing problems to leadership, team members learn to present complete proposals. Define the problem and its cost. Articulate the desired outcome. Recommend a solution with clear resource requirements.

Oliver’s current challenge illustrates why this matters: “My team comes to me with a problem and then I have to use my brain space to think about the solution. But it’d be much better if they defined the problem, defined the outcome they want, and gave me a proposed solution.”

This shift transforms every interaction from a drain on the CEO’s cognitive resources into a development opportunity for the team member.

The framework works because it addresses a fundamental misunderstanding about delegation. Firm owners often justify keeping tasks because “I could do this in five minutes. Why delegate something that takes them two hours?”

But this calculation ignores the compound effect. That two-hour learning investment today becomes 90 minutes next week, then 60 minutes, then eventually faster than you could do it yourself—all while freeing you to focus on strategic work only you can do.

Oliver’s ultimate success story proves what’s possible. After five years building his firm with these principles, he achieved the dream: “I was doing no sales, I was doing no client work. We were getting customers. They were getting served. They were happy, they were paying. Money was coming into the bank and I was not involved.”

For anyone trapped in 60-hour weeks, Oliver’s enthusiasm is infectious: “I will tell you that it is the greatest thing in the world to get into that position, because then you’re really just an owner of a business.”

From Bottleneck to Breakthrough: Your Next Strategic Move

The journey from bottleneck to strategic leader is about fundamentally reimagining how knowledge and decision-making flow through your organization.

Damiano’s framework reveals that delegation isn’t a single skill but a system. It requires clear communication, defined success metrics, and the courage to accept “good enough” from others. The same perfectionism that built your reputation can become the cage that limits your growth.

This transformation extends beyond individual firms to the entire accounting profession’s evolution. As AI handles increasingly complex technical work, the firms that thrive will be those where owners have already extracted themselves from technical execution. They’ll focus on strategy, relationships, and innovation instead.

What makes Human at Scale different is, “We don’t just come in as a consultant or advisor or coach,” Damiano explains. “We actually come in and join your team. We are in there, actually running these systems and building that with you.”

Listen to the full conversation between Oliver and Damiano on the Earmark Podcast to discover additional frameworks and tools. Visit Human at Scale to take their operational leadership assessment that can diagnose your firm’s specific bottlenecks.