問題 › 自社の本当の価値は? › 製造業
企業価値の評価は、主に機械時間あたりの貢献度の質に関わるものであり、売上規模ではありません。 製造業者にとってこれを難しくしているのは構造的な問題です。$45Mの自動化案件は、利益率の問題を引き起こしている顧客に依存しています。したがって、信頼できる回答は、機械時間あたりの貢献度と設備稼働率を同じ視点で捉える必要があります。これはほとんどの内部分析が止まるところです。2つが異なるシステムに存在するためです。
企業価値の評価は、主に機械時間あたりの貢献度の質に関わるものであり、売上規模ではありません。 製造業者にとってこれを難しくしているのは構造的な問題です。$45Mの自動化案件は、利益率の問題を引き起こしている顧客に依存しています。したがって、信頼できる回答は、機械時間あたりの貢献度と設備稼働率を同じ視点で捉える必要があります。これはほとんどの内部分析が止まるところです。2つが異なるシステムに存在するためです。
工場長は企業価値を利益に対する倍率として考えがちです。買い手は、その貢献が自らの所有下でどれだけ残るかの判断として見ます。同じ利益を出していても、2社の製造業者が異なる金額で売却される理由です。
要因は一貫しています。売上の集中度、工場全体での設備稼働率の維持、機械時間あたりの貢献度が工場長に依存している度合い、スクラップ率と段取り替えを考慮した際の利益率の防御力です。これらの各要素は、利益の1ポイント増より倍率に大きく影響します。
つまり、実務的な問いは通常「価値はいくらか」ではなく「倍率を押し下げているのはどれか、売却までの時間で修正できるか」です。
この3つが揃うと特徴的です。1つだけでは別のことを示すことが多いです。
✓ 取引まで数年以内で、機械時間あたりの貢献度をタクトとスクラップで正規化したことがない。
✓ 利益の多くがCEOまたは工場長の持つ関係性に依存している。
✓ 売上の大半が非継続的かつ集中しており、設備稼働率の大きな変動で確認できる。
通常、事態を悪化させる対応です。 売却前年に機械時間あたりの貢献度を最適化しつつ、顧客集中と自動化依存はそのままにする。いずれかを修正するより価値向上に寄与しないことが多い。
It is for you if you run or finance a manufacturer and you are within a few years of a transaction and have never had the earnings normalised. 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 Kessler Industrial Components, a sample company profile used for testing rather than a customer — $310M revenue, three plants.
Excerpt from a real Percision run · Competitive Positioning · sample company profile
The move. Automate Cedar Falls to lock in Customer A manifold volumes at 19% lower cost before Mexican alternates scale.
The leak it closes. Scrap rate reduced from 3.8% to 2.1%; 78-minute changeover reduced toward world-class 25 minutes
The assumption it rests on. Customer A does not activate dual-sourcing before automation payback (3.8 years) — the engine put the probability at 0.65.
| Investment required | $45M total |
| Expected return | 24% IRR on $45M investment over 7-year Customer A programme life |
| Revenue, year 1 | $340M (no incremental revenue; cost protection only) |
| Revenue, year 2 | $351M (3% price-down offset by automation savings) |
| Revenue, year 3 | $362M (Customer A volume stability plus new Mexican OEM programmes) |
| Exit criteria | If Customer A dual-source volume migration exceeds 25% by Month 18, cease further automation spend and redirect remaining capex to Querétaro expansion and aftermarket channel build-out. |
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 contribution per machine hour, capacity utilisation, customer concentration and scrap, 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〜3年です。継続収益と経営者依存度の低減が数字に表れるまでそれだけの時間がかかるためです。
買い手によります。財務的買い手は持続的なキャッシュフローに支払い、戦略的買い手は自社の立場への寄与に支払います。どちらを想定するかで修正すべき点が変わります。
Materially, yes. The $45M automation case depends on the very customer that causes the margin problem — which changes both the diagnosis and the order of the fixes. The metrics that decide it here are contribution per machine hour, capacity utilisation, customer concentration, 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 contribution per machine hour and capacity utilisation. 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 · ไทย · हिन्दी · עברית