The Number Looks Clear. The Next Move Doesn’t.

A client can understand the report and still leave the meeting without a clear next move.

Consider a service company with steady sales and a cash balance that keeps tightening. The financial statements show the pressure. They do not tell the owner whether the first move should be raising prices, collecting faster, changing payment terms, delaying a hire, or cutting spending.

That is the moment when the conversation moves beyond reporting. The advisor has to help the client choose an action and say what that action is expected to change.

This second part is easy to skip.

An advisor might recommend that the company invoice completed work within one business day instead of waiting until the end of the week. The recommendation sounds practical. It may even be the right move. But without an expectation, the client and advisor have no fair benchmark for the review meeting.

What should change first? How long should that take? What financial response should follow? What result would show that the intervention is not working as intended?

Those questions are the point of Milan’s Third Law of Financial Improvement:

Say what should happen before you see what happens.

A recommendation needs two expectations

Most financial recommendations affect the business in stages. The operating condition changes first. The financial statement changes later.

In the invoicing example, the first expectation might be:

• The average delay between completed work and an issued invoice falls from eight days to one day within the first month.

The downstream financial expectation might be:

• Days sales outstanding moves below 55 within 90 days, assuming customer payment behavior and sales mix remain reasonably stable.

The first expectation tests whether the company changed the process. The second tests whether that process change produced the financial response the advisor and client expected.

Keeping those two ideas separate matters. If invoices go out faster but DSO does not improve, the team has learned something useful. Perhaps customers are paying more slowly. Perhaps the largest accounts have unusual terms. Perhaps disputes are delaying payment after invoicing. The original explanation may need to change.

Without the operating expectation, the advisor may blame the intervention before knowing whether it was implemented. Without the financial expectation, the team may celebrate process improvement without checking whether it affected cash.

An expectation is not a promise

Stating an expectation does not mean pretending the future is certain.

The expectation can be directional. It can use a threshold, a range, or a review date. It can name the assumptions that must remain true. A cash forecast does not become more credible because every number has two decimal places.

A useful expectation sounds like this:

If completed-work invoices go out within one business day, we expect invoice delay to fall during the first month. If customer payment patterns stay near the recent range, DSO should begin moving toward 55 over the following 90 days.

That is specific enough to review without pretending the advisor controls the customer, the economy, or every operating condition.

A weak expectation sounds like this:

Cash flow should improve.

The second statement gives the client nothing to manage. It has no first response, no time frame, no guardrail, and no review point.

Put the expectation into the client conversation

The advisor does not need a long speech. A few direct questions can finish the recommendation:

1. What should change first if we execute this well?
2. What financial result should follow?
3. When will we review it?
4. What assumption or trigger would make us adjust or investigate further?

Those questions also protect the relationship. When the result arrives, the advisor and client can compare it with the decision they actually made, not a cleaner version reconstructed after the fact.

This is where FIX and Milan’s Four Laws work together.

FIX helps the advisor find the burning issue, identify what is creating the pressure, and execute a focused next step. The Third Law gives that next step an expected result. It does not replace FIX. It makes the intervention reviewable.

How Clear Path To Cash supports the work

Clear Path To Cash can keep the burning issue, chosen action, owner, due date, expected operating response, expected financial response, and review date connected in the client record.

The software does not decide what the client should do. The advisor still has to investigate the number, explain the tradeoff, and help the client choose. The system preserves the decision so the next meeting can begin with what was expected rather than what everyone vaguely remembers.

That distinction matters. A dashboard can display the result. An advisor has to prepare the client for what the result will mean.

Practice the conversation before the client is waiting

At the November Clear Path To Cash Advisor App Bootcamp, participants will use a company case, practice the advisor-client conversation, and work through an anonymized situation from their own practice.

On the second day, the expectation has to be stated before the outcome is known. Participants will name the operating response, the financial response, the owner, the review date, and the guardrails that would change the decision.

That is different from watching a software tour. It is practice for the moment when the client understands the report and asks, “What should we do next?”

The core Bootcamp runs November 20-21, 2026, in San Antonio with live virtual attendance available.

See the November Advisor App Bootcamp details

Record the decision while the assumptions are still visible, then review it against what actually happened.