問題 › 売上は安定しているのに資金が厳しい › 建設・工事業
利益と資金繰りは予測可能な箇所で乖離します。ほぼ常に、着手から最終入金までの工事サイクルです。 建設・工事業者では、この問題が特定の場所に現れます。答えを運ぶ数字は工事粗利益率とバックログカバーです。この業種特有の複雑さは、サービス工事の粗利益率がプロジェクトの2倍である一方、工期遅延条項との人員配置争いに毎回負ける点です。一般的な問題と実際に直面している問題では、最初の対応が異なります。
利益と資金繰りは予測可能な箇所で乖離します。ほぼ常に、着手から最終入金までの工事サイクルです。 建設・工事業者では、この問題が特定の場所に現れます。答えを運ぶ数字は工事粗利益率とバックログカバーです。この業種特有の複雑さは、サービス工事の粗利益率がプロジェクトの2倍である一方、工期遅延条項との人員配置争いに毎回負ける点です。一般的な問題と実際に直面している問題では、最初の対応が異なります。
粗利益率が出ていても、現場人件費と資材費が出来高請求の入金前に支払われ、変更指示書が未価格のまま残り、工期遅延条項で支出が先に来る場合、工事は資金を吸い上げます。これらはいずれも通常の流れであり、まとまるとバックログ内の追加工事1件あたりが消費する資金量を決めます。
重要な結果は、この状況では成長が問題を悪化させることです。バックログに新しいプロジェクトを加えるたびに、着手時と初期人件費の支出が最初の検収入金より先に来るため、売上が伸びている機械設備業者でも資金不足に直面します。
レバーは地味ですが即効性があります。追加工事着手前の変更指示書捕捉の厳格化、工事完了時ではなくマイルストーン連動の段階払い、プロジェクトの資金タイミングを埋めるサービス工事の計画的投入です。これらは通常、融資交渉より早く多くの資金を解放します。
この3つが揃うと特徴的です。1つだけでは別のことを示すことが多いです。
✓ 工事別粗利益率は健全に見えるのに、銀行残高が次回の人件費や仕入支払いに足りない。
✓ バックログ期間が長くなりながら、変更指示書の捕捉が遅れ、承認済みバラエティへの入金が滞っている。
✓ プロジェクト着手増加やバックログ拡大の時期に、報告上は粗利益率が維持されているのに資金繰りが逼迫する。
通常、事態を悪化させる対応です。 ギャップを埋めるために融資を入れることです。工事サイクルのタイミング問題を金利負担に置き換え、仕組みをそのまま残します。
It is for you if you run or finance a contractor and the P&L looks healthy and the bank balance does not. It is the situation where the numbers are available but nobody has put them in an order that produces a decision.
It is not for you if Percision is the wrong tool if you already know the answer and only need execution capacity, or if the business is pre-revenue — then the constraint is evidence about the market, not analysis of your own figures. Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library. Also wrong if you need facilitation, politics, or someone to sit with a lender or buyer. Those are human jobs.
Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library.
Below is an excerpt from a real run of this analysis on 請負業者. It is a sample profile rather than a customer, and it is engine output translated from English — this is the format you get, on your own numbers.
The subject is Halloway Mechanical, a sample company profile used for testing rather than a customer — $180M revenue, mechanical contracting.
Excerpt from a real Percision run · Pricing Strategy · sample company profile
The move. Deploy 12 existing journeymen to lock in 40 new hospital service contracts, converting construction relationships into recurring 32% GM revenue.
The leak it closes. Reduces $4.2M overtime drag by re-allocating 12 journeymen from construction backlog to service fleet.
The assumption it rests on. Hospital procurement will accept 12–18% premium pricing for single-source mechanical partner — the engine put the probability at 0.75.
| Investment required | $2M cash (Phase 1); funded by existing $6.4M cash balance. |
| Expected return | 128% gross-profit ROI on $2M investment in Year 1; payback <12 months. |
| Revenue, year 1 | $8M incremental service revenue |
| Revenue, year 2 | $12M cumulative incremental |
| Revenue, year 3 | $18M cumulative incremental |
| Exit criteria | Terminate move if fewer than 15 hospital SLAs signed by Month 9 OR construction backlog falls below 6 months. |
This is one move out of a full analysis. Read a complete report — every page, no email required.
This question routes to 独自のEFF Methodology, one of 29 engagements the platform runs. For 建設・工事業者 it works through job gross margin, backlog cover, change-order capture and service attach rate, then produces the sequence rather than a list of options — which move first, what it funds, and the observation that would say the sequence is wrong.
You watch the analysis get built before paying anything. 完全なレポートはこちらをご覧ください if you would rather see the depth first.
利益は請求時に計上され、資金は入金時に動くためです。この2つの間の乖離に成長を掛け合わせたものが、成長が消費する資金量です。
通常は請求ラグと着手金です。どちらも自社で制御可能で即効性があります。売掛金回収は効果がありますが遅く、仕入先条件の再交渉はさらに遅いです。
ギャップを同時に閉じる場合のみです。構造的な運転資金サイクルをそのままに融資を受けると、次の成長段階でより不利な条件で再び借り入れることになります。
Materially, yes. Service work earns double the margin of projects and loses every staffing argument to liquidated-damages clauses — which changes both the diagnosis and the order of the fixes. The metrics that decide it here are job gross margin, backlog cover, change-order capture, and an answer built on industry-general benchmarks will usually point at the wrong one first.
Less than most people expect. Your last twelve months of revenue and cost split the way you already split it, plus whatever you hold on job gross margin and backlog cover. The analysis is explicit about what it is assuming where your data stops, which is more useful than waiting for numbers you may never have.
Percision is the wrong tool if you already know the answer and only need execution capacity, or if the business is pre-revenue — then the constraint is evidence about the market, not analysis of your own figures. Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library. Also wrong if you need facilitation, politics, or someone to sit with a lender or buyer. Those are human jobs.
Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library.
Describe the situation in your own words and we will tell you which analysis answers it — before you sign up for anything.
Describe my situation →Prefer to skip ahead? Go straight to the free diagnostic.
English · Español · Deutsch · Português · Français · Italiano · Nederlands · 日本語 · 한국어 · 中文 · Polski · Svenska · Türkçe · العربية · Tiếng Việt · ไทย · हिन्दी · עברית