How long client call preparation takes

Practitioners in our design-partner conversations described preparation for a client advisory call as taking roughly two hours for a straightforward client and up to half a day for one with debt, multiple entities or a live decision. That is the total, and it is the number people ask for. It is also the least useful number on this page.

Three things matter more than the total. Where the time goes within the sequence, because it is not spread evenly. Who decides when the time gets spent, because it is usually not the practitioner. And which parts of the time are not the practitioner’s to control at all.

The short answer

In our design-partner conversations, CPAs and fractional CFOs described client-call preparation ranging from roughly two hours for a straightforward engagement to half a day for one involving debt, multiple entities or an active decision. They consistently identified three time-intensive areas: reconstructing prior decisions, verifying outcomes against the books and bank, and preparing answers that connect multiple parts of the business.

Preparation time is also vulnerable to two things the calendar does not show: off-cycle client questions, and books that are not ready when preparation begins.

This guide draws on qualitative design-partner conversations with CPA and fractional CFO practices. Time ranges are as practitioners described them, not measured benchmarks.

Where the time goes

Take the eight-step sequence from the preparation guide and ask which steps are fast and which are slow.

The fast steps are the ones the accounting system already supports. Reading the P&L, balance sheet and cash position is fast. Checking the reconciliation date is fast, once you know to do it. Opening the call with what changed takes no time at all if the rest was done.

The time-intensive steps are the ones least supported by the usual combination of meeting notes, task systems and accounting software:

• Reconstructing decisions from the last two calls. The notes exist, but the commitments are a few sentences inside a page of summary, and someone has to find them.
• Verifying each decision against what actually happened. The bank knows whether the receivable landed. The task list does not. Someone has to look.
• Preparing the cross-domain answer. “Is the marketing spend turning into revenue?” is a lookup on each side and real analytical work in the middle. Running the scenario the client is likely to ask about belongs here too.

Practitioners did not give us minute-by-minute breakdowns, and we are not going to invent one. But the shape they described was consistent: the reporting half of preparation is quick, and the controllership half is where the hours go, because the connecting work has to be reconstructed across several systems. The reporting half has had software built for it for decades. The controllership half is done by hand, which is why it is slow, and being slow is what makes it vulnerable when the window shrinks.

Who actually decides when the time gets spent

This is the finding that changed how we think about the whole subject.

A fractional CPA we work with put it in one line: his day is decided by his inbox. He can plan tomorrow around two client calls and the preparation for them. Then two emails arrive overnight. One client needs an answer on a hire. Another wants to know whether they can take the distribution they were planning. Neither is on the calendar. Both need research: pulling reports, checking the bank, sometimes building a fresh cash forecast. By mid-morning the plan for the day is gone.

Notice what got sacrificed. Not the calls, which were fixed. Not the off-cycle requests, which were already urgent. For this practitioner, preparation was the movable item: work for a meeting that had not happened yet, so it was the thing that gave up the time.

This is why the failure modes keep recurring even in practices that value preparation and know exactly how to do it. The practitioner did not decide to skip it. The inbox decided.

An off-cycle request repeats the preparation work

Look closely at what those two emails required. Reconstructing context. Pulling current numbers. Verifying something against the bank. Running a scenario. That is the preparation sequence, run under time pressure, with no meeting attached and usually no line item for it.

So the practitioner ends up doing preparation twice: once for the calls that are scheduled, and once, unplanned, for the questions that arrive between them. Unless the engagement explicitly scopes or prices that second kind, it becomes invisible in the engagement’s economics. It is also the kind most likely to be answered from memory, or with “I will get back to you,” because it arrived in the middle of work that was already planned.

The time that is not yours to control

Some of the preparation time is not the practitioner’s at all, and an honest account has to say so.

Step three of the sequence is checking when the books were last reconciled. Frequently the answer is “not recently,” and frequently the reason is upstream: the client has not uploaded the receipts, the client’s team has not answered a categorisation question, a bank feed has been disconnected for two weeks. None of that is inside the firm. All of it lands on preparation, because every number downstream of an unreconciled book is provisional, and the practitioner either presents provisional numbers or spends the preparation window chasing the client for what is missing.

We are not going to claim software fixes this. Some preparation depends on information or action outside the firm’s control, and no workflow removes that. What can change is when the dependency is discovered: it should be visible before the window opens, not found inside it. A practitioner reading “two hours to half a day” should know that some of those hours may be spent waiting on someone else, and that the number depends on how current the books were when preparation began.

What this means for capacity

Ask practitioners why they cannot take more clients and the answer we heard was bandwidth. Not a shortage of prospects. A shortage of hours, and the hours are consumed in the two ways above: scheduled preparation that competes with everything else, and unscheduled requests that win.

There is a second constraint on new clients that is larger than either, and it deserves its own guide rather than a paragraph here. Firms told us that a new client typically arrives after the founder has given up managing the finances alone, which means the books often arrive with months or years of reconciliation behind them. Onboarding can take months, and none of it is advisory. It is cleanup before advisory can begin. That cost sits before the preparation cost and is separate from it. We will cover it in a later guide.

What this means for pricing advisory work

It is easy to price advisory around the visible meeting. The client experiences the meeting, so it becomes the natural unit a package is described around.

But the meeting may be the least time-intensive part of delivering it. The expensive part is the two hours to half a day before it, plus the off-cycle requests that recur between meetings and are rarely quoted. A firm pricing off the visible hour is pricing the reporting half and absorbing the controllership half.

We are not going to tell you what to charge. But the honest basis for an advisory fee is the controllership work: the reconstruction, the verification, the cross-domain preparation and the off-cycle answers. That is what the client is buying, whether or not the invoice says so. Making that work visible in scope and pricing also gives the firm a better chance of protecting the preparation time when other requests arrive.

Our product

AgentLink (agentlink.finance) is designed to carry the slow half of preparation continuously rather than in a window the day before: the decisions from the last call held and checked against the books and the bank each day, the reconciliation date stated, the likely cross-domain questions surfaced in advance. Because it runs between calls, it is also what a partner opens when the off-cycle email arrives, so that answer comes from the same prepared context as the scheduled one. It is sold through CPA and fractional CFO firms. The firm keeps the client, the pricing and the judgement.

Frequently asked questions

Should preparation be done by the partner or an associate?

Reconstruction, verification and initial scenario work can all be delegated with a clear review step. Cross-domain analysis usually benefits from senior judgement, especially when the answer bears on a consequential client decision, but that is a review question, not a reason to keep it off the associate’s desk.

How do I stop off-cycle requests eating the preparation window?

The practitioners we spoke to had not fully solved it, and we are not going to pretend there is a clean answer. Two levers help. Scope and price recurring off-cycle support explicitly, so it is visible in the engagement rather than absorbed. And keep the context assembled between calls, so an off-cycle answer costs minutes rather than a morning. Prepared context does not remove the request; it lowers the cost of answering it.

Does preparation time fall as you get to know a client?

Some of it. Familiarity usually reduces interpretation time and some reconstruction. It does not remove the new decisions, outcomes and questions each cycle produces, so preparation gets more efficient without disappearing.

What if the books are not current when I start preparing?

Say so in the call, present the affected numbers as of the reconciliation date, and use part of the window to identify what is missing from the client rather than to analyse numbers that will move. The preparation guide covers this under step three.

About the author

Nilanjan Raychaudhuri is the founder of AgentLink (Tublian LLC, Columbus, Ohio), which builds controller-layer software sold through CPA and fractional CFO firms. He has spent the past year interviewing practitioners at fractional CPA and CFO practices about how advisory work is actually delivered. Team page

The practitioner observations in this guide come from design-partner conversations and are used with permission where attributed. Time ranges are as described by practitioners and are not measured benchmarks. Corrections to nilanjan@agentlink.finance.