What your clients cannot see between check-ins

Several practitioners we spoke with described a version of this story. A weekly or biweekly check-in ends well. The numbers are fine, the plan is agreed, the client is clear on what happens next. Then, somewhere in the days before the next one, the client pays a supplier early, or brings on two contractors, or takes a distribution. The firm finds out from the books, or from the client mentioning it on the next call, after the money has moved.

The instinct is to read that as a client who should have called first. It is worth resisting, because the practitioners we spoke with described clients who track their own commitments carefully and still end up here. The gap is not carelessness on either side. It is structural, and it opens between check-ins even with a strong cadence.

The short answer

In the pattern practitioners described, the founder knew each commitment individually. What they could not see in a bank balance is the combined timing: payroll, the tax instalment, the insurance renewal and a slipped receivable landing in the same ten days.

The bank shows current cash. The books record what has happened and what is owed. The forecast is what assembles those facts, the commitments the client made on the last call, and the firm’s assumptions about timing into a sequence. The founder reads the bank, because it is current and legible. The firm reads the forecast, because building it is the firm’s work. The client blind spot is the gap between the point the founder can see and the sequence the firm can see.

Between check-ins, the founder is the one deciding, and they are deciding from the point. Asking the firm first has real friction, so they often do not. The fix is on the firm’s side and it is proactive: use the forecast you already build to flag the tight weeks before they arrive, prompt the client on a fixed rhythm, and keep the exchange in a channel where it carries into the next check-in.

This guide draws on qualitative design-partner conversations with CPA and fractional CFO practices. Client behaviour is as practitioners described it; we did not interview clients directly.

The founder is not missing information

It would be easy to write this as a guide about what business owners do not know. That would be wrong, and any owner reading it would know it was wrong.

A founder knows payroll runs every other Friday and roughly what it costs. They know the quarterly tax is coming. They know they told the firm they would hold the hire until the big invoice cleared. Each of these is tracked, usually well, in the founder’s head or their own notes. Practitioners did not describe clients who forget their obligations.

What no one holds in their head is the sequence. Payroll on the tenth is fine. The tax instalment on the fifteenth is fine. The insurance renewal on the twelfth is fine. The receivable that was funding all three arriving on day forty-five instead of day thirty is annoying but survivable. All four in the same window is a balance that crosses the buffer on the fourteenth, and nothing about any single item warned of it.

That sequence exists, but not in any one place the founder looks. It is assembled from the books, the bank activity, the commitments the founder mentioned on the last call, and the firm’s read on when the receivable will actually land. Assembling it is what a cash forecast is, and the firm can see it because the firm builds it. The founder cannot, not because they lack the facts but because the surface they read is structurally unable to show them.

The bank shows a point

The bank balance is often the most immediate and legible number a founder has. It is theirs, it updates overnight, and it is one figure, and for many owners it is the one they check first.

It shows exactly one thing: what is in the account at this moment. It has no way to express what is committed to leave over the next two weeks, when the outstanding invoices will actually land rather than when they say they will, or which of the commitments from the last check-in are still open. Those are forward-looking facts and assumptions. A bank balance cannot show them, and it is not designed to.

So the founder’s view of the business is a point, refreshed daily. The firm’s view is the sequence. Neither is doing anything wrong. The founder is reading the most current, most legible thing available. The firm is reading the thing that actually answers the question. They are looking at the same business through instruments that cannot show each other’s picture.

Why the gap survives good cadence

The obvious response is more check-ins. Practitioners were clear that this does not close the gap, and the reason is that the gap is not a function of interval.

A weekly check-in leaves six days. A twice-weekly one leaves three. The founder’s decisions do not wait for either. They arrive when the supplier emails, when the contractor is available, when the project looks close enough to spend against. The decision lands on a Wednesday because that is when the question came up, and on Wednesday the founder is looking at the bank.

More cadence also has a cost, in the founder’s time and the firm’s, and beyond a point it starts to look like what it is, which is the firm trying to be present for a decision it cannot predict. The problem is not that the firm is absent too often. It is that the founder’s view of the sequence is absent all the time, and only the firm can supply it.

The friction of asking

“Just call your CPA first” sounds free. It is not, and the practitioners who described it were describing the founder’s side fairly.

To ask, the founder has to decide the question is important enough to interrupt someone. Then they have to write it up in a way that makes sense to a person who was not in the room. Then they wait, because the firm has other clients and the partner is in a meeting. The answer comes back in a few hours or the next day, and the supplier or the contractor may not have waited.

So the founder weighs interrupting against deciding. That threshold exists even in a warm, responsive relationship. Every question still depends on the founder deciding to initiate it, the firm reconstructing the relevant financial picture, and the answer arriving before the decision is made. Neither side is at fault. The channel simply depends on human attention to carry information that changes continuously.

The two outcomes practitioners described follow directly. Either the founder decides alone, and the firm learns about it afterwards from the books, which is the subject of the commitment-tracking guide. Or the founder asks, and the question reorganises the firm’s day. Too little contact and too much, from the same cause.

What practitioners asked for

Two of our design partners, a fractional CPA and a fractional CFO in different markets with different client bases, independently asked for the same thing: a view their clients could open themselves. The forecast, the outstanding invoices, the receivables. Not so the client could do the analysis, but so the routine questions had somewhere to go that was not the partner’s inbox.

We put weight on that because it is a practitioner describing the gap from inside the relationship. A firm that wants its client to have the sequence is not complaining about the questions. It is saying the questions have no home.

What exists today, and what it leaves open

Firms have tools for this, and they should use them.

Advisory reporting platforms increasingly offer a client-facing dashboard, so a founder can open the forecast and the aging without asking. A number of firms run a shared messaging channel with each client, in Slack or similar, so a quick question costs a sentence rather than an email chain. Both are real improvements on the balance and the phone call, and a firm that has neither should start with them.

A client-facing reporting view, by itself, waits to be opened. A shared messaging channel, by itself, does not know what the forecast says. Some products combine parts of this workflow. The remaining question is whether a tight week can surface the right conversation, and whether the client’s response carries back into the firm’s record.

That separation is the remaining gap. The firm already has the forecast. It already knows, in most cases, which week is tight and which decisions are coming. What it does not have is a way for that knowledge to reach the founder before the decision, and a way for the founder’s thinking to reach the firm before the money moves.

Closing the loop

The fix is proactive, and it belongs to the firm, because the firm is the party that can see the sequence.

Read the forecast for decisions, not just for cash. The forecast you already build shows the tight windows. Look at each one and ask what the founder is likely to be deciding around it: the supplier payment, the hire, the distribution. Then say so, before the window, in the founder’s terms. “Payroll, the tax instalment and the renewal all land the week of the fourteenth, and the big invoice probably arrives after that, so this is a week to hold rather than spend.” That is analysis the firm is already doing, redirected from reporting what happened to anticipating what is about to be decided.

Invert who initiates. On a fixed day each week, send the client a short prompt. Anything on your mind? Any decision you are weighing? Happy to think it through. It removes the friction entirely, because the founder is no longer interrupting anyone. They are replying. Practitioners who wanted their clients to have the view were, in effect, asking for this: a standing invitation rather than a threshold the founder has to clear.

Keep it in one place. Whatever channel the firm uses, the forecast flags and the founder’s replies should land in the same one, so that by the next check-in the firm can see what the founder was worried about and what was decided, and open from there rather than from “how is the business going.” This is where continuity is actually made. The preparation guide opens with reconstructing decisions from the last two calls. A channel that already holds them means there is nothing to reconstruct.

Run manually, this is a weekly forecast read, a weekly prompt, and a channel. The action is small for one client and becomes real operating work across a full client book, and the forecast has to be current for the flags to be right, which returns to the reconciliation problem that runs through this whole series. But it is a method, and it closes the loop that dashboards and channels each leave open on their own.

Our product

AgentLink (agentlink.finance) runs this loop continuously. The forecast is refreshed daily from bank activity and the latest available books, carrying forward what the client and the firm agreed on the last call. Tight windows and likely decisions are surfaced as prompts to the client under the firm’s brand, the client’s questions and answers land where the firm can see them, and the exchange becomes the opening of the next check-in. When the books are unreconciled or transactions remain uncategorised, that limitation stays visible in the forecast rather than being treated as settled fact. It is sold through CPA and fractional CFO firms. The firm keeps the client, the pricing and the judgement.

Frequently asked questions

Won’t a weekly prompt generate more questions?

Probably, at first. The practitioners who asked for client access expected the routine ones to fall away once the founder could see the sequence, leaving the judgement questions, which are the ones the firm wants. A question that arrives on the firm’s schedule, in a channel, with the forecast already flagged, is a different thing from one that arrives cold on a Wednesday.

Is this the client’s fault for not looking at the books?

No. The books are designed to record financial activity, not to present the forward-looking sequence around a decision. This is a visibility problem, not a financial-literacy problem. The instrument the founder does read cannot show a sequence, and that is not something a founder can fix by trying harder.

We already have a client dashboard. Isn’t that enough?

It is a good start and worth keeping. The limit is that it waits to be opened. The loop described here adds the two things a dashboard cannot do: bring the tight week to the founder before they decide, and bring the founder’s thinking to the firm before the money moves.

What should clients be able to see between advisory calls?

At minimum, current cash, upcoming commitments, expected inflows, the tight weeks, and any unresolved assumptions the forecast rests on. The view should also show how current the underlying books are, so the client knows how much weight the picture will bear.

Does this replace the check-in?

No. It changes what the check-in opens with. Instead of reconstructing the last two weeks, the firm starts from a record of what the founder was weighing and what was decided, and spends the time on judgement.

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. Client behaviour is as described by practitioners; clients were not interviewed directly. Corrections to nilanjan@agentlink.finance.