集中が問題になるのは、元請が機械工事の範囲を簡単に他の業者に置き換えられるかどうかに比例します。これはスケジュールの露出と違約金に関する問題で、割合の問題ではありません。 建設・工事業の請負業者では、特定の場所でこの問題が現れます。答えを運ぶ数字は案件粗利益率とバックログカバーであり、この業種特有の複雑さは、サービス業務が案件の2倍の粗利益を生む一方で、違約金条項による人員配置の争いに毎回負ける点です。一般的な問題と実際に直面している問題では、最初の対応が異なります。
集中が問題になるのは、元請が機械工事の範囲を簡単に他の業者に置き換えられるかどうかに比例します。これはスケジュールの露出と違約金に関する問題で、割合の問題ではありません。 建設・工事業の請負業者では、特定の場所でこの問題が現れます。答えを運ぶ数字は案件粗利益率とバックログカバーであり、この業種特有の複雑さは、サービス業務が案件の2倍の粗利益を生む一方で、違約金条項による人員配置の争いに毎回負ける点です。一般的な問題と実際に直面している問題では、最初の対応が異なります。
バックログカバーの大半を占める顧客は、その下の構造次第で危険にも安全にもなります。残りの範囲を別の業者に移せ、再工程なしで済むなら存続に関わる露出です。置き換えに再入札、再許可、違約金を引き起こす遅延の吸収が必要なら、集中に見えても強い立場です。
落とし穴は、集中が通常より悪い経済条件を伴うことです。大口顧客は案件粗利益率で強く交渉し、変更指示への即応を求め、支払いサイトを長くします。リスクと利益の低下が同時に来るのです。追加案件で集中を薄めるのは遅く、依存を再価格設定して現場人件費リスクを反映させる方が早い手段です。
売上集中と貢献集中を分けて考える価値もあります。1件の大規模案件が売上を支配していても、サービス業務が粗利益の大部分を供給している場合、後者こそが実際に痛む部分です。
この3つが揃うと特徴的です。1つだけでは別のことを示すことが多いです。
✓ 1顧客または1案件が現在のバックログカバーの大半を占めている
✓ その顧客の案件は、台帳の他案件より案件粗利益率や変更指示の捕捉率が明らかに低い
✓ 顧客を失うと、他の業務への再配置ではなく、現場人員の即時削減を迫られる
通常、事態を悪化させる対応です。 割合を薄めるために追加案件を追うこと。依存を残したまま現場人員のコミットメントを増やします。
It is for you if you run or finance a contractor and one customer exceeds a quarter of revenue. 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 · Competitive Positioning · 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 · ไทย · हिन्दी · עברית