What Revenue Operations Looks Like Inside a 50-200 Person Accounting Firm

Revenue Operations, at a 50 to 200 person accounting firm, is not a department with its own floor - it is usually one person, one small team, or an external partner who owns the systems and data connecting business development, engagement delivery, and billing, so those three functions stop operating as disconnected silos that only reconcile with each other by hand at month end.

Why accounting firms hit this wall at a specific size

Below roughly 50 people, informal coordination works. Partners know which prospects are in the pipeline, staff know which engagements are active, and billing questions get resolved in a hallway conversation. Past that point, the number of active engagements, staff, and referral relationships outgrows what anyone can track by memory, and the same functions that ran fine informally start producing real friction: leads that go unfollowed, engagements that get staffed late, invoices that go out weeks after the work is actually done.

Most firms in this range already run several systems - a CRM or lead-tracking spreadsheet for business development, a practice or engagement management platform for client work, and a separate accounting or billing system - built and adopted at different times, by different people, for different immediate needs. None of them were designed with each other in mind, and by the time a firm notices the gaps between them, meaningful revenue is usually already leaking through the seams.

The three functions RevOps has to connect

Business development and pipeline. Referral sources, inbound inquiries, and proposal tracking need a consistent home and a consistent definition of where each prospect stands. Without it, partners run their own informal pipelines in their heads or inboxes, and the firm has no aggregate view of what is coming - which makes staffing and capacity planning a guessing game.

Engagement delivery. Once a client signs, the engagement needs to be staffed, scoped, and tracked against budget - this is engagement or matter management. The handoff from "signed" to "staffed and started" is one of the most common places delivery stalls in a growing firm, because nobody owns making sure it happens on a defined timeline.

Billing and collections. Time recorded against an engagement has to become an invoice on a predictable cycle, and that invoice has to get collected. This is where work in progress (WIP) either converts to cash promptly or ages into a cash flow and realization problem.

RevOps in an accounting firm this size is the function that makes sure information moves cleanly across all three - a signed engagement flows into staffing without manual re-entry, staffing and time data flow into billing without reconciliation, and none of the three functions is operating on a different version of the truth than the others.

Why accounting firms feel this differently than other professional services

Accounting has a structural wrinkle most other professional services do not: seasonality. Tax season concentrates an enormous share of annual engagement volume into a few months, which means the staffing and delivery function has to flex hard on a predictable annual cycle, while business development and billing continue at a steadier pace the rest of the year. A RevOps function built for a firm with even, year-round demand will not fit an accounting firm's actual rhythm - capacity planning here has to explicitly model the seasonal peak, not just track a rolling average that smooths right past it.

That seasonality also raises the cost of a broken handoff. A staffing delay that costs a consulting firm a few days of engagement momentum can cost an accounting firm a missed filing deadline during peak season, with real client and regulatory consequences attached. The margin for a slow or manual handoff between systems is simply smaller during the months that matter most.

What the first 90 days of a RevOps build usually looks like

Audit before building. The starting point is almost always a data and process audit: where does a lead currently get tracked, how does a signed engagement get staffed today, how long does time sit as unbilled WIP before an invoice goes out. Most firms are surprised by what the audit finds - not because anyone did anything wrong, but because nobody had looked at the full chain end to end before.

Fix data quality before connecting systems. Integrating a CRM with a practice management system, or a practice management system with the accounting platform, only compounds a mess if the underlying data going in is inconsistent - duplicate client records, unclear engagement scopes, mismatched naming conventions. Data cleanup is unglamorous and usually happens first, because a two-way sync on bad data just copies the mess into more places, faster.

Define one system of record per data type. Decide, explicitly, which system owns the authoritative version of client data, engagement status, and billing data, so when two systems disagree, there is a clear rule for which one wins instead of a silent, arbitrary overwrite. This is the core of CRM-ERP integration done properly.

Instrument the handoffs, not just the systems. The highest-leverage fixes are usually at the handoff points - sales to delivery, delivery to billing - not inside any single system. A CRM that is perfectly clean and a billing system that is perfectly accurate can still leak revenue if the handoff between them depends on someone remembering to do something manually.

Who actually owns this at a firm this size

Very few 50-200 person accounting firms have budget for a dedicated, full-time Chief Revenue Officer or a multi-person operations team, which is part of why RevOps at this scale so often lands on a managing partner's plate alongside client work, or gets outsourced to an external partner who can dedicate real, focused attention to it. Neither path is inherently wrong, but the failure mode to watch for is the same in both: RevOps treated as a side project that only gets attention when something breaks, rather than an ongoing function with clear ownership and a standing cadence for reviewing the numbers it produces. A managing partner who owns RevOps in name but has no protected time for it tends to produce the same disconnected-systems outcome the function was meant to solve.

What good looks like once it is running

The tell is quiet, not dramatic. Partners can see a real-time view of pipeline instead of piecing it together before a partner meeting. A signed engagement gets staffed and kicked off on a predictable timeline instead of sitting in someone's inbox. Time recorded against an engagement becomes an invoice on a defined cadence instead of accumulating as aging WIP. And when leadership asks which clients or practice areas are actually most profitable, the firm can answer from data instead of instinct - see engagement profitability for how that calculation actually works.

What this means for a firm at this size

The reflex at 50 to 200 people is often to hire a dedicated ops leader inside each function - a business development coordinator, a delivery manager, a billing specialist - which adds headcount without necessarily connecting anything. The more durable fix is usually a single accountable Revenue Operations function (in-house or an external partner) that owns the systems and data spanning all three, because the value is almost entirely in the connections between functions, not inside any one of them.

If you want to see where your own firm's business development, delivery, and billing are disconnected, the free AI Opportunity Assessment maps it in about a minute. For a deeper look at the accounting-specific playbook, see the accounting firms industry page, or book a strategy call to walk through your firm's systems directly.