Sitework contractors run out of cash because of three stacked problems: developer payment cycles that run 30–45 days slower than GC-managed work with no leverage to accelerate them, phase billing that doesn't align with actual cost burn so the contractor funds the gap between phases out of operating cash, and scope creep absorbed without documented change orders because the developer relationship feels too important to push back on. The jobs are real. The margin is there on paper. The cash disappears into timing gaps and undocumented work — and that pattern repeats on every project until a system is built to stop it.
Sitework is not civil work. Civil is production economics — equipment moving material at a cost per unit. Sitework is coordination economics — phased scopes, developer relationships, and scope boundaries that shift. The cash failure patterns are different. The financial system required is the same: C.F.O.S.
This page is for you if: you're running $1M–$12M in commercial sitework, your projects are executing on schedule, and you're still always short on cash. Developer-driven sitework has a different payment structure than GC work — slower pay cycles, phase-based billing, and scope exposure that doesn't exist on traditional subcontracts. You cannot negotiate your way out of the structural gaps. You manage them with a system.
Sitework on developer-driven projects operates on a completely different financial structure than GC-managed commercial work. The developer is not a GC. They don't have a superintendent managing the schedule. They don't have a standard pay app process. They have a budget, a lender, and a timeline — and the contractor's pay app competes with every other draw on that development loan for priority. Understanding that structure is the first step. Building a financial system around it is the only fix.
Developer pay cycles consistently run 30–45 days longer than equivalent GC-managed commercial work. A sitework contractor on a residential or mixed-use development submits a pay app and waits for the developer to process it through their construction loan draw, get lender approval, and release funds. That process takes 45–60 days on a well-run development and 75–90 days on a complicated one. The contractor's cost burn started on day one regardless.
Phase billing compounds the problem. Sitework contracts are typically structured around project phases — clearing and grubbing complete, rough grading complete, utilities roughed in, fine grading complete, paving complete. Each phase is a billing milestone. But the cost doesn't stop between phases. Crew mobilization, equipment standby, and supervision continue across phase transitions. The contractor funds the gap between when one phase ends and the next phase billing event is reachable — sometimes 3–4 weeks of cost with no billing offset.
The math: A $4M sitework contractor on two simultaneous developer projects, each with 45-day pay cycles and two phase transition gaps per project, is carrying a structural cash gap of $300K–$500K at any given time — not from bad jobs, but from the billing structure of developer-driven work and the absence of a system managing it.
These three problems are specific to developer-driven sitework. A sitework contractor doing GC-managed commercial work and developer-driven residential or mixed-use work simultaneously is running two different financial structures at once — and usually only has a system built for one of them.
A commercial GC has an established AP process. They receive pay apps, route them through project management approval, and cut checks on a predictable schedule. A developer is running a construction loan draw process through a lender. Every pay app requires a draw request, lender review, title company involvement in some cases, and fund disbursement from the construction account. That process is slower, less predictable, and harder to push on than a GC relationship.
A sitework contractor who moves from GC-managed commercial work to developer-driven projects without adjusting their cash model is funding a 30–45 day longer payment cycle on every dollar of developer work they take on. On a $1.5M developer sitework contract with a $120K/month cost burn, that extra 30–45 days is $120K–$180K of additional working capital requirement compared to equivalent GC work — just from the payment cycle difference.
The C.F.O.S fix starts at contract review. Developer payment terms reviewed before signing. Construction loan draw schedule mapped into the billing cut-off calendar. 13-week forecast built around developer payment timing, not GC payment timing. The financial model has to match the actual payment structure of who is paying — not a generic billing cycle assumption.
Phase-based billing on sitework contracts creates predictable cash gaps that most contractors fund without ever identifying them as a structural problem. The contract says: bill when rough grading is complete. Rough grading runs weeks three through seven. Fine grading starts week eight. Between the rough grading billing event and the fine grading billing event, two to four weeks of crew cost, equipment cost, and supervision continue with no billing offset.
On a $2.2M sitework contract with five phases and four phase transitions, each gap averaging three weeks of $80K/month cost burn, the contractor funds $60K per transition — $240K total across the project — entirely out of operating cash. That $240K doesn't show up as a loss at closeout. The job closes profitably. But the cash was gone for most of the project duration and the contractor ran on the LOC to cover it.
The fix is SOV restructuring before contract signing. Mobilization and supervision billed as continuous general conditions lines that don't stop between phases. Equipment standby billed as a separate recoverable line during phase transitions. Progress billing provisions that allow partial phase billing at percentage complete instead of only at phase completion. These three changes can recover $120K–$180K of the phase transition gap on a $2M sitework contract.
Developer-driven sitework has a scope creep problem that doesn't exist to the same degree on GC commercial work. Developers make decisions on the fly — grade this area differently, extend the storm drain, add a retention pond, widen the entry drive. Each decision adds scope. Each decision costs money. And in a developer relationship where the contractor wants to stay on the preferred vendor list and keep getting work, pushing back on undocumented scope feels like a relationship risk.
The result is absorbed scope — work done without change orders, costs incurred without billing recovery. A sitework contractor absorbing 8–12% undocumented scope on a $2M developer project is giving away $160K–$240K of work. Not because they agreed to — but because nobody built the process to document and bill it systematically.
This is not a relationship problem. It is a documentation process problem. C.F.O.S builds the change order tracking cadence as part of the monthly review — every scope event documented in real time, every change order submitted within 30 days of the scope event, every unapproved change order tracked as a disputed amount in the WIP schedule. The developer relationship doesn't have to change. The documentation process does.
Sitework cash problems on developer projects get blamed on the developer, the market, and the nature of the work. Those are real factors — but they are not why a $4M sitework contractor is perpetually short on cash despite profitable jobs. Here are the three wrong diagnoses.
Developer payment cycles are slower than GC cycles — that's structurally true. But "slow pay" is not a fixed reality that can't be managed. The construction loan draw schedule is knowable before the project starts. The lender's review timeline is predictable. A billing cut-off calendar built around the developer's actual draw process compresses the cash gap without changing the relationship or the contract terms.
→ Real problem: No billing cut-off calendar built around developer draw timing — pay apps submitted on the contractor's schedule instead of the lender's approval cycle.
Phase gaps are real — but they are manageable with the right SOV structure. Supervision and equipment standby billed as continuous general conditions lines, progress billing provisions allowing partial phase billing at percentage complete, mobilization lines that recover early cost before the first phase milestone — all of these are negotiable at contract review. Contractors who sign phase-based SOVs without negotiating continuous billing provisions fund every phase gap unnecessarily.
→ Real problem: SOV accepted without structuring continuous billing provisions — phase gaps funded by default instead of addressed at contract signing.
Developer relationships are valuable. But undocumented scope doesn't build a relationship — it builds a pattern where the contractor is expected to absorb extras as a cost of doing business. Documenting scope changes and submitting change orders is not adversarial. A professional contractor who tracks and bills all scope changes is more credible with a developer than one who absorbs them silently and then shows up short on cash.
→ Real problem: No change order documentation process — scope creep tracked informally or not at all, absorbed into job cost without billing recovery.
C.F.O.S is the financial operating system built around sitework's specific cash failure patterns — developer payment timing, phase billing gaps, and undocumented scope. Without this system running every month, developer slow pay compounds with phase gaps and absorbed scope until the LOC is carrying a permanent balance that never fully clears. This is C.F.O.S executing inside the civil cluster — every deliverable specific to sitework, monthly, and connected to the other five layers of the system.
Two service tiers priced by trailing twelve-month revenue. Core Financial covers the full C.F.O.S system — ControlQore setup, job costing by phase and work type, bookkeeping, and WIP. Executive Financial adds monthly CFO strategy meetings, controllership, and ongoing advisory. No payroll. 60-day onboarding. No scope gaps.
| Revenue Band | Core Financial | Executive Financial |
|---|---|---|
| Under $1M | $1,900/mo | $2,900/mo |
| $1M–$3M | $2,600/mo | $3,600/mo |
| $4M–$6M | $3,800/mo | $5,500/mo |
| $7M–$9M | $5,100/mo | $6,900/mo |
| $10M–$12M | $6,100/mo | $8,500/mo |
| $13M+ | Quoted | Quoted |
Three stacked problems specific to developer-driven work. Developer payment cycles run 30–45 days longer than GC work — on a $1.5M sitework contract that's $120K–$180K of additional working capital requirement. Phase billing milestones don't align with actual cost burn, creating 3–4 week gaps between phases that the contractor funds from operating cash. And scope creep gets absorbed without change orders because the developer relationship feels more important than the paperwork. All three compound on the same projects without a financial operating system managing them.
Developer payment terms reviewed and billing cut-off calendar built around the construction loan draw cycle before work starts. SOV structured with continuous general conditions, equipment standby, and progress billing provisions. 13-week forecast built around developer timing and phase milestones. Change order documentation process running every month — scope events logged within 7 days, change orders submitted within 30. Cost-to-complete tracked by phase in ControlQore. Retainage tracked with developer-specific release triggers.
Commercial sitework subcontractors doing $1M–$12M. Core Financial starts at $1,900/month. Executive Financial starts at $2,900/month. Both priced by trailing twelve-month revenue. Onboarding takes 60 days — books migrated, ControlQore set up, job costing built around your phases and work types. No payroll. No residential.
Core Financial includes ControlQore setup, job costing aligned to your phases and estimates, full-service bookkeeping, and bank reconciliations. Executive Financial adds monthly CFO strategy meetings, controllership, and strategic accountability. No payroll. No scope gaps.
60 days. We migrate your books to the start of your last taxable year, set up ControlQore, and build your job costing structure from scratch aligned to your phases and work types. Fully operational in two months.
You cannot self-assemble a fix from knowing the problem. The financial system has to be built, run monthly, and connected to the other five layers of C.F.O.S — or developer slow pay, phase gaps, and absorbed scope keep compounding every project. Schedule a free call and we'll show you what that system looks like built around your sitework business.
SCHEDULE A FREE CALL →