A Dangerous Phrase in Business: “We Should Be Fine”
Many business owners look at their bank balance, see money there, and say: “We should be fine.” This phrase replaces a calculation with a feeling — and cash does not care how you feel about it.
It feels like a reasonable thing to say. Revenue has been good. No big problems are visible. The team is busy. Things feel stable.
But this phrase is dangerous. Not because it is always wrong. Because it replaces a calculation with a feeling — and cash does not care how you feel about it.
What the phrase really means
When a business owner says “we should be fine,” they usually mean something like this:
- Customers will probably pay on time.
- Sales will probably stay at the same level.
- No big unexpected cost will appear.
- Next month will probably look like last month.
These are not bad observations. But they are assumptions about the future — not facts about it.
A business can run successfully for years while those assumptions stay true. The problem starts when two or three of them fail at the same time.
A customer pays three weeks late. A supplier asks for payment earlier than usual. A tax bill and payroll fall in the same week. None of these events is a disaster on its own. Together, they can create a cash gap that nobody saw coming.
Why “should” is not a financial plan
The word “should” contains no numbers. It contains no dates. It cannot be tested.
There is a difference between these two statements:
Statement A feels reassuring. Statement B may feel less comfortable. But only Statement B is based on something you can check and act on.
Some businesses operate closer to Statement A than Statement B. The phrase “we should be fine” is a sign of this.
The gap between profit and cash
Here is the fact that surprises many owners: a business can be profitable and still run out of cash.
Profit is a summary. It tells you that more money came in than went out over a period of time. Cash flow is about timing. It tells you whether the money in your account is enough — on a specific date — to cover what is due.
You invoice a client in March. They pay in May. Your payroll is in April. Your profit looks fine. Your cash does not.
You win a large new contract. To fulfill it, you spend money now. Payment comes later. Revenue is growing. The bank balance is shrinking.
The income statement does not warn you about this gap. The bank balance does not warn you until it is too late. “We should be fine” looks at neither.
Why experienced owners fall into this trap
Experience is supposed to protect you. In most areas of business, it does.
But cash flow is different. The danger does not come from things going wrong. It comes from things going slightly differently than expected.
An owner who has run a business for seven years has survived hard moments before. The brain records this as evidence: I know how to handle this. We’ve been through worse. That confidence is real and earned.
The problem is that past survival does not mean future immunity. And if the business has grown, the stakes are higher now. A cash gap that was a €5,000 problem three years ago may now be a €50,000 problem. But the level of concern stays the same — because nothing catastrophic happened before.
There is also a natural tendency to plan around the most likely outcome. You think about the deals that will probably close, the customers who usually pay, the costs that normally stay stable. This is how human planning works.
If the payment does not arrive, the obligations still land on the exact date they were due.
What this may look like in a real business
This is a fictional example, but it reflects a very common pattern.
A construction fit-out company. Eight employees. Seven years in business. The owner had built it steadily and knew his industry well. The previous two years had been the best in the company’s history.
A larger contract came in — a commercial office renovation worth €180,000 over four months. The client was a known local company. Payment terms were 30 days from each invoice. The owner did the mental calculation: three invoices, money coming in regularly, no trouble.
He hired two additional workers. He ordered materials from his supplier on 60-day terms. He also accepted a second, smaller job running alongside the main one.
Everything looked positive.
The first invoice went out on time. Payment did not arrive in 30 days. The client’s accounts department said they were processing it. It arrived on day 52.
That 22-day delay was annoying — but manageable on its own. Except that by then, several other things had also landed at the same time:
- The materials supplier’s 60-day terms were up.
- The two additional workers had received their first month’s wages.
- The second job had generated its own costs — fuel, materials, a subcontractor — before any income from it arrived.
Each of these items was fine on its own. The client would pay. The supplier was patient. The second job would make money. But all of them landed in the same three-week window, and the business did not have enough cash to cover them all while waiting for the client’s payment.
The owner moved money from his personal account to cover payroll. He called the supplier and asked for two more weeks. The second job’s subcontractor had to wait. For about three weeks, a profitable, growing business could not comfortably meet its basic obligations.
When did the owner realize there was a problem?
The Friday before payroll. He looked at the account, looked at what was due in the next four days, and understood that the numbers did not add up as he had assumed.
Were the warning signs visible earlier?
Yes. All of them.
Payment terms of 30 days in construction routinely become 45 or 50 days in practice. That was predictable. The decision to hire two workers before the first payment had arrived was a commitment made against money that had not yet appeared. The supplier’s 60-day terms would fall due at almost exactly the same time as the other obligations — a simple written schedule would have shown this immediately.
None of the individual decisions were mistakes. The problem was that nobody looked at all of them together, on a timeline, against actual available cash. The owner had done the calculation in his head, and in his head everything balanced. On paper, with dates attached, it did not.
What should replace “we should be fine”?
A specific answer to a specific question: how much cash will we have, on which date, after everything due out has gone out — and only the payments that will realistically arrive have arrived?
This means tracking three things, updated regularly:
1. What is actually in the bank today
Not what is invoiced. Not what is owed. What is physically available.
2. What is going out and when
Every payment due in the next 8–13 weeks. Payroll, rent, suppliers, loan repayments, taxes. With dates, not approximate months.
3. What is coming in and when — honestly
Not all outstanding invoices. Only the ones where payment is genuinely expected in that window. And for each one: when does this client actually pay, based on their history, not their invoice terms?
Lay these out week by week. After each week, calculate the running balance. The vulnerable weeks become visible immediately — weeks where a large payment goes out but nothing significant is expected in, or weeks where the balance only stays positive if one specific client pays on time.
Knowing this 8–10 weeks in advance means you can do something about it. Ask a client to pay slightly earlier. Arrange a short-term credit facility before you need it. Delay a non-essential cost by two weeks. None of these options exist if you only discover the problem when it arrives.
The most important shift: replace optimistic assumptions with honest ones
A cash flow forecast will always contain assumptions. Everything in it is an estimate about the future. That is not a flaw — that is what a forecast is.
The question is not how to remove assumptions. The question is: are your assumptions based on what you hope will happen, or on what has actually happened before?
Your forecast says a client will pay in 30 days. Look back at the last six payments from that client. When did they actually pay? If the answer is consistently 45–50 days, your assumption is wrong — not because you invented it, but because you used the invoice terms instead of the client’s real behaviour.
Your forecast includes a deal closing this month. How many deals at this same stage have actually closed on time in the past year? If the honest answer is about half, putting the full value in this month’s forecast is optimistic. Half the value, or moving it a month forward, is more accurate.
This is what moving from assumptions to evidence means. Not eliminating assumptions. Replacing assumptions based on what you hope will happen with assumptions based on what has actually happened in similar situations before.
Your own records are the evidence. Payment patterns, how often deals close on schedule, when costs tend to arrive earlier than expected — all of this is in your data. A forecast built on real history will still be wrong sometimes. But it will be wrong by small amounts, not large ones. And it will not consistently flatter you in the same direction every month.
Knowing you are fine is not the same as assuming you are
“We should be fine” is not always wrong. Said by someone who has just reviewed a 13-week forecast and can see clearly that obligations are covered and no dangerous weeks are ahead — it is a perfectly accurate statement.
Said by someone going on general feeling, recent good performance, and a comfortable bank balance today — it is a guess.
The goal is not to stop feeling confident. Confidence is useful. The goal is to have a number to check that confidence against — a specific balance, on a specific date, based on honest assumptions about how your customers actually behave.
That is the difference between a business that is probably fine and a business that knows it is.
Business mindset diagnostic: Are you operating on hope? Answer five questions to find out.
Business health diagnostic
"We should be fine" — are you actually sure?