問題 › 次の四半期、何をすべきか › 建設・工事業
四半期計画の多くは、優先順位の選択ではなく、要員と資金の算術で破綻します。 建設・工事業の請負業者にとって特に難しいのは構造的な理由です。サービス工事の粗利益率はプロジェクトの二倍ですが、工期遅延条項のあるプロジェクトに要員が取られます。現実的な計画は、案件ごとの粗利益と手持ち工事の状況を同時に見なければなりません。多くの社内資料がここで止まるのは、二つの数字が別々のシステムにあるためです。
四半期計画の多くは、優先順位の選択ではなく、要員と資金の算術で破綻します。 建設・工事業の請負業者にとって特に難しいのは構造的な理由です。サービス工事の粗利益率はプロジェクトの二倍ですが、工期遅延条項のあるプロジェクトに要員が取られます。現実的な計画は、案件ごとの粗利益と手持ち工事の状況を同時に見なければなりません。多くの社内資料がここで止まるのは、二つの数字が別々のシステムにあるためです。
四半期には、既存の手持ち工事から生まれる要員と資金の総量が決まっています。多くの計画は、新規プロジェクトにこの総量を超える要員と資金を振り向けます。工期遅延条項が発動した時点で、粗利益で支えきれなくなります。結果は計画の失敗ではなく、静かな取捨選択です。サービス工事の付帯率や変更指示の獲得で、どの部分を切り捨てたかは記録に残りません。
計画が実行段階で残るためには、候補となる手を案件粗利益に対するリターンで並べ直し、現在の要員拘束を差し引いた残りの要員で実現可能かを確認し、最初に手持ち工事の状況を改善するか、次の手を可能にする順に並べる必要があります。三つの優先事項が、十二の並列表記より確実に機能します。
ほぼ常に欠けているのは停止条件です。案件粗利益や手持ち工事の状況について、着手前に決めておく数値基準がなければ、後で結果をめぐって議論が始まります。
この3つが揃うと特徴的です。1つだけでは別のことを示すことが多いです。
✓ 前四半期にサービス工事の付帯率が低下し、進行中のプロジェクトに要員がすべて取られ、正式に中止された項目がなかった。
✓ 経営者またはCFOが新規プロジェクトの入札とサービス拡大目標の両方を挙げながら、要員をどちらに優先的に充てるかを順位付けしていない。
✓ どの案件または施策にも、変更指示の獲得率や案件粗利益について、事前に決めた停止基準が書かれていない。
通常、事態を悪化させる対応です。 粗利益の基準を満たすプロジェクトにすべて着手すること。これでは、工期遅延条項が先に到着した順に組織が選ぶことになります。
It is for you if you run or finance a contractor and last quarter's plan was partly done and nobody formally dropped anything. 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. Recover $2.7M of lost change-order revenue in 12 months by digitizing the 44% late-submission process that currently leaks 146% of net income.
The leak it closes. Eliminates the 44% of submissions occurring >30 days post-event that currently result in zero collection
The assumption it rests on. Field technicians will adopt the mobile app at ≥85% compliance within 90 days — the engine put the probability at 0.75.
| Investment required | $180K total |
| Expected return | 1,500% over 12 months |
| Revenue, year 1 | $1.35M incremental service revenue (50% realization ramp) |
| Revenue, year 2 | $2.7M incremental service revenue (full realization) |
| Revenue, year 3 | $3.0M incremental service revenue (pricing uplift + volume growth) |
| Exit criteria | Kill the move if, by Month 6, adoption <70% OR realization <65%; otherwise continue through Month 24 and reassess at Durability half-life. |
This is one move out of a full analysis. Read a complete report — every page, no email required.
This question routes to Growth Portfolio Framework, 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.
実際に使える要員と資金で回る件数です。大半の中堅・中小企業では二つか三つです。この数は算術であって、考え方の問題ではありません。
消費する要員に対するリターンで並べ、次に撤回しやすさで並べます。二つが近い場合は、止めやすい方から着手します。
そのために停止条件を用意します。事前に失敗の基準を決めておけば、議論ではなく事実に基づいて計画を修正できます。適応と漂流の違いです。
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 · ไทย · हिन्दी · עברית