How to Price Strategic Value in a CAS Model

Hourly billing in client accounting services (CAS) engagements creates a set of conditions that most firms recognize but rarely examine: The client watches the clock, the team tracks increments, and the conversations that would build a deeper relationship shorten or disappear altogether. Every interaction carries an implicit cost, and both sides (the firm and the client) behave accordingly.

Under this pricing model, scope becomes the central governing mechanism. The engagement is defined not by what the firm owns but by what’s been authorized in measurable units. For instance, when a client calls with a question outside the original estimate, the firm must decide whether to absorb the time, bill for it, or avoid the conversation. Of course, each of these decisions shape the relationship differently, and none of them build toward embedded trust.

Also with hourly billing, the financial behavior is predictable—revenue fluctuates with volume, and margin compresses as complexity increases without proportional rate adjustment. Realization rates decline when experienced professionals spend time on work that doesn’t bill cleanly. The firm earns more only when it works more—a structure that rewards activity, not positioning.

What hourly billing produces most reliably is distance. The firm remains external, the client remains guarded, and the engagement operates inside a transactional frame regardless of the advisory intent behind it.

WHY THE HOURLY MODEL PERSISTS

Most firm leaders recognize the limitations of hourly billing in CAS. Yet the model persists because it solves problems that matter inside the firm, even as it creates problems within the engagement itself.

Hourly billing offers predictable scoping. It provides a defensible basis for fees when clients question cost. It fits the infrastructure most firms already operate under: timekeeping systems, utilization targets, and realization benchmarks. Abandoning it means abandoning the management architecture built around it, and that architecture governs compensation, performance evaluation, and partner economics.

There’s also less risk involved with hourly billing. Fixed-fee models expose the firm to scope variability. If the engagement requires more hours than anticipated, the firm absorbs the cost. Under hourly billing, however, that risk transfers to the client. For firms that haven’t defined how scope is governed before the engagement begins, that transfer feels like protection.

Overall, the result in maintaining the hourly billing model is that it serves internal operations while constraining external positioning. Both sides operate rationally inside a structure that limits what the relationship can become. The firm organizes around measurability and risk transfer, and the client receives reporting without access to the reasoning behind it.

WHEN PRICING REFLECTS POSITIONING

A CAS engagement that’s priced by the hour compensates the firm for activity. However, a monthly fixed-fee engagement tied to process ownership compensates the firm for its position inside the client’s operation.

Under hourly pricing, the client decides how much access to purchase. Under monthly fixed-fee pricing, access is embedded in the structure. In this case, neither side weighs whether a conversation justifies the cost, and communication becomes operational rather than transactional.

Scope governance also changes under a monthly fix-fee structure. In an hourly model, scope is managed through authorization and estimates. In a monthly fixed-fee model tied to defined process ownership, scope is managed through boundaries. The conversation shifts from “Is this billable?” to “Is this ours?”

Additionally, client expectations shift in parallel. When a firm prices for embedded positioning, the client begins treating the team as an internal function rather than an outside provider. Meetings include the finance team by default, decisions wait for financial interpretation, and the relationship operates inside the client’s structure rather than alongside it.

WHERE EACH MODEL WORKS

The professional debate over hourly billing versus fixed-fee billing often frames the question as preference. In practice, the question is really about application.

Monthly fixed-fee billing works well in process-centric, function-specific engagements—accounting, accounts payable, payroll, and HR administration—where the time spent on work and communication is predictable. The firm knows what it owns, the client knows what to expect, and both sides operate inside a defined rhythm.

Hourly billing works well in complex, issue-driven engagements involving external actors—tax controversies, regulatory responses, and transaction-related diligence—where time spent on work can’t be reasonably estimated. These engagements resist the assumptions that monthly fixed-fee structures depend on.

Notably, a firm that relies solely on either model exposes itself to risks on both sides. For instance, the firm takes on financial risk when it applies monthly fixed-fee pricing to engagements that lack predictable scope. When hourly billing governs an engagement that would function better under a defined operating relationship, the client absorbs unnecessary costs.

At my firm, the majority of billings come from monthly fixed-fee engagements. Every client engagement is also accompanied by a separate hourly billing statement of work—with explicit client consent—for matters that fall outside the scope of monthly fixedfee services. The two structures operate in parallel because the conditions they serve are different.

CAS PACKAGING AND PRICING IN PRACTICE

At my firm, every monthly fixed-fee engagement is structured around process ownership. There are no time entries governing what the client receives. The fee reflects what the firm owns inside the client’s operation.

Our baseline is controllership—month-end close, financial reporting, and the accounting infrastructure that supports both. My firm treats that ownership as a prerequisite. If the firm doesn’t control the close process, it can’t govern the reliability of anything built on top of it.

Beyond controllership, my firm’s engagements are also scoped by function. Some clients require us to manage payroll administration, accounts payable, or cash management. Others require participation in executive planning, board reporting, or departmental budgeting. Each function carries a defined scope boundary. What the firm owns is specified and what falls outside that ownership is equally specified and governed by the separate hourly statement of work.

Additionally, our fees are set based on three factors: the complexity of the client’s operations, the number of functions the firm owns, and the level of access required. A client with a single-entity structure and straightforward reporting pays less than a client with multi-entity consolidation, intercompany transactions, and boardlevel reporting requirements. The fee isn’t renegotiated monthly— it’s reviewed periodically as the scope of ownership changes. That review is the mechanism that protects our margin—it ensures the fee reflects what the firm actually owns, not what it owned when the engagement began.

WHAT PRICING ARCHITECTURE PRODUCES

When packaging is built around process ownership and fees are tied to defined scope, three conditions emerge that hourly billing doesn’t reliably produce:

• Margin becomes governable. The firm knows what it owns, what that ownership costs to deliver, and where the boundary sits. Profitability depends not on utilization rates or realization percentages but on how accurately the scope of ownership reflects the operational complexity underneath it. When scope changes, the fee is renegotiated—not absorbed.
• Scope discipline becomes structural rather than conversational. Under monthly fixed-fee pricing with a parallel hourly statement of work, the boundary between what’s included and what’s not is defined before the engagement begins. When a client request falls outside the defined scope, both sides already know where it lands.
• Executive trust follows from both. When a client’s leadership team sees a firm that owns processes, governs its own scope, and prices with transparency, the relationship moves from vendor oversight to operational reliance. The firm earns a seat in the room where decisions are made because its pricing structure already communicates that it operates as an internal function—they’re not an outside service provider billing for time.

Overall, what determines the CAS engagement isn’t the billing method but the architecture underneath—what the firm owns, how scope is governed, and how the fee reflects that ownership—and that’s the foundation for packaging CAS in a way that delivers real strategic value.