CONSTRUCTION CASH FLOW FEAST OR FAMINE CYCLE 13-WEEK CASH FLOW FORECAST JOB COSTING · WIP · OVERHEAD RATE $1M–$12M SUBCONTRACTORS CONSTRUCTION CASH FLOW FEAST OR FAMINE CYCLE 13-WEEK CASH FLOW FORECAST JOB COSTING · WIP · OVERHEAD RATE $1M–$12M SUBCONTRACTORS
THE CONSTRUCTION CFO
Pricing Results Free Tools About Free Call

The feast or famine cash flow cycle in construction happens because revenue is lumpy — jobs run for months, overhead is constant, and billing timing rarely matches cash inflow. Most subcontractors doing $1M–$12M in revenue don't have a 13-week cash flow forecast, so the dry months always arrive as a surprise. SPM fixes this through job costing aligned to estimates, WIP reporting, and 13-week forecasting built around your actual billing cycles. The Construction CFO, Sulphur Rock AR, serves commercial subcontractors nationwide.

Cash Flow · Construction Subcontractors

Construction Business Cash Flow Problems: Feast or Famine Cycle

The feast or famine cycle is the most predictable financial problem in construction — and almost nobody has a real system to prevent it. Revenue is lumpy by design. Overhead is not. When billing timing doesn't match cash inflow, you spend flush months feeling good and dry months calling your bank. Most subcontractors doing $1M–$12M treat this as a fact of life. It isn't.

Schedule a Free Call → See Pricing
Updated: May 2026By Josh Luebker, The Construction CFO
How It Happens

The Feast or Famine Cycle, Step by Step

The feast or famine cycle in construction is structural — it's built into how jobs are awarded, started, billed, and paid. Most subcontractors experience the same 6-step loop on repeat. Understanding which step is breaking for your company tells you exactly where to fix it.

1

Job Awarded — No Cash Yet

You win a $2M job. Your bank account doesn't change. Mobilization costs hit immediately — equipment moves, crew starts, materials land. You're spending cash before your first pay app even leaves the office.

2

First Pay App — 60 Days Out

Most GC payment cycles run 30–60 days after submission. You submit at the end of the month for work done that month. Best case, you see cash in 45 days. Worst case, 75 days with a dispute. Meanwhile, payroll runs every week.

3

Retainage Held — Cash Locked

5–10% of every pay app gets held as retainage. On a $2M job that's $100K–$200K you won't see until final completion — which could be 12–18 months away. That's real cash that's working for your GC, not you.

4

Jobs Overlap — Cash Gaps Multiply

You're running three jobs. One is mid-cycle (cash flowing), one just started (cash out), one is in closeout (waiting on retainage release). The net position looks fine on paper. The bank balance tells a different story every Friday.

5

Overhead Doesn't Stop

Payroll, insurance, equipment payments, rent — these don't pause between jobs. A slow month in new work doesn't reduce your overhead by a dollar. This is why growing subcontractors sometimes have worse cash flow than smaller ones.

6

The Cycle Repeats

No forecast. No real-time job cost data. No system to see the gap coming. The next dry stretch catches you the same way the last one did. The LOC gets tapped again. And the cycle runs again.

The Numbers

What the Cycle Costs You

The feast or famine cycle isn't just uncomfortable — it has a measurable financial cost. Most subcontractors don't track it because they don't have the systems to see it. Here's what it typically looks like across SPM's client base.

73
Average days between billing and cash received for electrical subcontractors
10%
Of annual revenue held in retainage at any given time on active jobs
60 days
How far ahead you need visibility to prevent a payroll near-miss

The core problem: Most subcontractors make cash flow decisions based on their bank balance. That number tells you what happened 30–60 days ago. By the time you see the problem, you're already in it. A 13-week forecast built around your actual billing cycles tells you what's coming — in time to do something about it.

Root Causes

Why the Cycle Keeps Repeating

The feast or famine cycle persists because most subcontractors are fixing symptoms instead of causes. Pulling on the LOC is a symptom fix. Delaying AP is a symptom fix. The causes are almost always one of three things — and they all have systems-level solutions.

01

Overhead Rate Too Low

Your bids don't cover your real cost of doing business. Every job you win contributes less to overhead than you need. Cash flow feels tight because it is tight — the math doesn't work at the bid level. You need an overhead rate recalculation, not an LOC increase.

02

Billing Timing Mismatches

You're doing the work. You're not billing it when you should. SOV front-loading, aggressive pay app scheduling, and billing at mobilization instead of completion are the difference between 45-day cash cycles and 75-day ones. Every 30 days of billing lag is real money sitting in your GC's account.

03

No Real-Time Job Cost Visibility

You don't know a job is losing money until it closes. By then there's nothing left to fix. Real-time job costing in ControlQore shows you cost-to-complete variances weekly — so you catch the bleed when there's still time to act. Without it, you're managing by feel and hoping.

The Fix

How SPM Breaks The Cycle

SPM builds the three systems that actually fix the feast or famine cycle — not one at a time, but together, because they only work when they're connected. Job costing tells you what's happening. WIP tells you what it means to your billing position. The 13-week forecast tells you what's coming.

13-Week Cash Flow Forecast

Built around your actual billing cycles — not a generic template. Every pay app submission date, every expected receipt, every AP obligation mapped out 90 days. You see the gap before it hits. You make decisions in time to matter.

How it works →

Job Costing in ControlQore

Actual costs tracked against estimated costs by phase — weekly, not at closeout. You know which jobs are making money while they're running. You catch the bleed in week 4, not month 8. That's the difference between a margin adjustment and a loss.

ControlQore setup →

WIP Reporting Monthly

Monthly work-in-progress schedule showing every job's billing position — overbilled, underbilled, or in range. The single most important financial document for a subcontractor. Catches revenue recognition problems before they hit the P&L. Executive tier.

How WIP works →
In Practice

What Changes After 60 Days

SPM clients are fully operational in 60 days — books migrated, ControlQore live, job costing running. Here's what the feast or famine picture typically looks like before and after SPM gets involved.

Before SPM
Making decisions based on bank balance
Finding out jobs lost money at closeout
Calling the bank when cash gets tight
Dry months arriving as a surprise every time
LOC tapped, AP delayed, stress on Friday
After SPM
90-day visibility into cash — gaps seen in advance
Job cost variances caught weekly, not at closeout
LOC used strategically, not reactively
Billing timing optimized — pay apps hitting earlier
Friday afternoon no longer stressful
Common Questions

Straight Answers

The feast or famine cycle in construction happens because revenue is lumpy by nature — jobs start, run for months, and close. But overhead is constant. When billing timing doesn't match cash inflow, you get flush months followed by dry ones. Most subcontractors don't have a 13-week cash flow forecast, so the dry months always come as a surprise. The fix is a forecasting system built around your actual billing cycles — not a generic spreadsheet.

Three things fix it together: a 13-week cash flow forecast built around your billing cycles so you see gaps before they hit; job costing aligned to your estimates so you know which jobs are actually making money; and an overhead rate that reflects your real cost structure. Most subcontractors fix one of the three and wonder why the problem persists. They work together or they don't fully work.

The most common causes: billing timing mismatches with GC pay cycles, overhead rates that are too low, retainage held for 90–180 days, pay-when-paid contract terms, and no real-time job cost visibility. The P&L often shows profitable — the bank account tells a different story. The gap between those two numbers is where the feast or famine cycle lives.

No. A line of credit manages the symptom — it doesn't fix the cause. If your overhead rate is too low, every job you win makes the problem worse, and the LOC just lets you defer the reckoning. If your billing timing is off, you'll tap the LOC every dry month forever. Fix the underlying system first. Use the LOC for strategic investment, not survival.

Josh Luebker — The Construction CFO
Josh Luebker
Fractional CFO · The Construction CFO

Former commercial construction project manager and master electrician. Managed 150+ projects totaling $300M+ including Google data centers, military bases, hospitals, and high-rises. Now fractional CFO for commercial subcontractors doing $1M–$12M through Sulphur Prairie Management. About Josh →  |  LinkedIn →

Related Resources
Guide
13-Week Cash Flow Forecast
How to build a real forecast around your billing cycles
Guide
How to Read a WIP Schedule
The document that connects billing position to cash flow
Fix
Overhead Rate Is Wrong
How to find and fix the overhead rate killing your margins
Working Capital
How Much LOC Do I Need?
Calculate the right credit line for your revenue band
Cash Flow
Retainage Cash Flow Problem
How retainage compounds the feast or famine cycle
Cash Flow
Profitable But No Cash
Why the P&L and bank account tell different stories

STOP FLYING BLIND
ON CASH FLOW.

Schedule a free 30-minute call. We'll tell you straight where your feast or famine cycle is coming from and whether SPM can fix it.

Schedule a Free Call → See Pricing
THE CONSTRUCTION CFO
13-Week Cash Flow Profitable But No Cash Overhead Rate Fix Pricing Schedule a Call Josh@ConstructionCFO.net
© 2026 SULPHUR PRAIRIE MANAGEMENT · SULPHUR ROCK, AR · CONSTRUCTIONCFO.NET
0