How should a project business think about working capital?
Project businesses should connect the timing of customer receivables with approved contractor and vendor obligations, while preserving job-level margin context. The key operating question is not only how much A/R exists, but whether expected cash and current cash safely cover near-term obligations by job.
- Profitability and liquidity are different
- An unpaid invoice is not settled cash
- Approved payout obligations can create near-term pressure
- Job-level context explains where the pressure comes from
- Cash-control signals are not the same as formal treasury forecasting
A project business can be profitable on paper and still experience cash pressure.
That happens because profitability measures economics, while working capital is heavily affected by timing.
A customer may owe a large milestone that has not yet been paid. At the same time, contractors, guides, production crew, vendors, travel, or other project obligations may be approaching their payment dates.
The operating problem is therefore not solved by looking only at profit or only at total A/R.
Start with settled cash, not expected cash
An open customer invoice can be valuable and highly collectible without being cash in the bank today.
For conservative operating control, distinguish:
- settled cash,
- open receivables,
- overdue receivables,
- promised or expected receipts,
- approved obligations,
- failed or unresolved payouts.
Do not silently treat every open invoice as immediately available funding.
Connect receivables to the jobs that created them
A $50,000 receivables total is much more useful when finance can see which projects, customers, and milestones make up the balance.
The job link helps answer:
- Which project is waiting on cash?
- How old is the receivable?
- What contractor or vendor obligations are connected to the same work?
- Is the job economically healthy?
- What happens if the customer payment is delayed?
That is the foundation of working capital control for project businesses.
Keep payout obligations visible before settlement
Approved contractor or vendor obligations may create real near-term cash demand before the payout actually occurs.
Useful states can include:
- work accepted,
- amount approved,
- funding pending,
- payout processing,
- payout completed,
- payout failed or returned.
The cash-control view should make the supported obligation visible without confusing it with an already settled cash outflow.
Profit margin does not answer cash timing
A project can have an attractive forecast margin and still create temporary funding pressure if customer payment occurs after contractor obligations.
The reverse can also happen: a project can have strong incoming cash but weak economics because delivery cost has increased.
That is why a useful control layer keeps Kelvaro Margin, Kelvaro Collect, and Kelvaro Cash conceptually distinct but connected.
Margin asks whether the job is economically healthy.
Collect asks what customer cash is outstanding and what action is required.
Cash asks how receivables and payout obligations combine into near-term funding pressure and operator actions.
Build a conservative funding-gap signal
A simple operational funding-gap signal can compare supported available resources with supported near-term obligations.
The exact formula depends on the business and data available. The important design principles are:
- do not count uncertain inflows as settled cash,
- show the evidence behind the signal,
- distinguish timing risk from profitability risk,
- route the user to the underlying receivable or payout issue,
- avoid implying guaranteed liquidity.
This is operational decision support, not lending and not a promise that funding will be available.
Rank the next action instead of only displaying balances
A cash dashboard is more useful when it answers what needs attention.
Potential actions include:
- follow up on an overdue customer invoice,
- resolve a failed payout,
- fund an approved obligation,
- review a margin exception,
- investigate an excluded or unsupported record.
The queue should point back to the underlying evidence whenever possible.
Working capital control is not a replacement for treasury forecasting
Near-term cash control and a formal treasury forecast are related but not identical.
A full treasury process may include bank balances across entities, debt facilities, payroll, taxes, capital expenditure, long-range operating forecasts, financing scenarios, and a formal 13-week cash model.
Kelvaro Cash is not positioned as that system. It focuses on project-linked receivables, payout obligations, margin context, conservative funding-gap signals, and operator actions.
Frequently asked questions
What is working capital in a project business?
At a high level, working capital reflects the short-term resources and obligations that support operations. For project businesses, customer receivable timing and project-related payment obligations can materially affect day-to-day liquidity.
Can a profitable job create a cash problem?
Yes. If customer cash arrives after contractor, vendor, travel, or other obligations are due, a profitable project can still create a timing gap.
Is cash-flow visibility the same as a 13-week cash forecast?
No. Cash-flow visibility can surface current and near-term operating pressure. A formal 13-week forecast is a broader treasury planning process with more complete cash sources, uses, assumptions, and scenarios.