問題 › 自社雇用かアウトソースか › 物流・サプライチェーン
判断基準は1マイルあたりのコストではありません。機能の所有が積載マイルあたりの収益やドライバーの離職率を動かし、オペレーティングレシオを変えるかどうかです。 物流・輸送会社の場合、専用輸送は利益率を圧迫しますが、ドライバーの離職率を改善する唯一の手段でもあります。これを価格に織り込まない限り、積載マイルあたりの収益は原因不明のまま動き続け、総コストをめぐる議論は意見のぶつかり合いにとどまります。
判断基準は1マイルあたりのコストではありません。機能の所有が積載マイルあたりの収益やドライバーの離職率を動かし、オペレーティングレシオを変えるかどうかです。 物流・輸送会社の場合、専用輸送は利益率を圧迫しますが、ドライバーの離職率を改善する唯一の手段でもあります。これを価格に織り込まない限り、積載マイルあたりの収益は原因不明のまま動き続け、総コストをめぐる議論は意見のぶつかり合いにとどまります。
自社雇用かアウトソースかの議論は通常、1マイルあたりのコストで行われますが、これは最も影響の小さい要素です。スポット輸送は稼働率が低いときは安く、高いときは高くなります。したがって正しい比較は、予測しなければならない専用輸送とスポット輸送の比率次第です。
本質的な問いは、販売しているものとの近さです。顧客が支払う輸送の体験に触れる機能、または積載マイルあたりの収益を高めるレーン知識を蓄積する機能は、割高でも自社で持つ価値があります。それ以外は購買判断です。
三つ目の要素は変動です。自社で持てばタイミングとドライバー定着の制御が得られ、アウトソースすれば柔軟性が得られます。どちらが重要かは、変動がデッドヘッド率に現れるか、または次回の専用契約に影響する顧客苦情に現れるかで決まります。
この3つが揃うと特徴的です。1つだけでは別のことを示すことが多いです。
✓ 議論が1マイルあたりのコストに終始し、ドライバーの離職率やデッドヘッド率に触れない。
✓ 提案する人員の稼働率や積載率が、専用輸送とスポット輸送のボリューム予測を行わずに決められている。
✓ 機能がスポットブローカーではなく、専用契約の実行やドライバー配置の中にある。
通常、事態を悪化させる対応です。 レーン知識と顧客知識を蓄積する機能をアウトソースすること。これにより毎年コストは下がる一方で、デッドヘッドと離職率は毎年上がります。
It is for you if you run or finance a freight company and the debate is being conducted entirely on hourly rates. 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 Ridgeway Freight Systems, a sample company profile used for testing rather than a customer — $240M revenue, 900 drivers.
Excerpt from a real Percision run · Pricing Strategy · sample company profile
The move. Convert 3-year dedicated customers into hybrid LTL lanes that stack 52-month durability and deliver $22M incremental operating income.
The leak it closes. Plugs $2.9M annual empty-mile cost drag by converting 5.5 percentage points of empty miles into loaded hybrid revenue
The assumption it rests on. Dedicated customers accept hybrid LTL lanes at 70% probability — the engine put the probability at 0.7.
| Investment required | $1.4–1.8M total ($450K software + $350K training + $600–1M salesperson SPIFFs) |
| Expected return | 12.2–15.7× on $1.6M base investment ($22M upside / $1.6M cost) |
| Revenue, year 1 | $4.2M incremental operating income (10 hybrid lanes × $420K avg contribution) |
| Revenue, year 2 | $11.0M incremental (25 lanes) |
| Revenue, year 3 | $22.0M incremental (40 lanes) |
| Exit criteria | Terminate hybrid program if <40% dedicated customer conversion by Month 12 or if hybrid lanes show negative operating income contribution by Month 18 |
This is one move out of a full analysis. Read a complete report — every page, no email required.
This question routes to Organizational Alignment Model, one of 29 engagements the platform runs. For 物流・輸送会社 it works through revenue per loaded mile, driver turnover, deadhead percentage and operating ratio, 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. Dedicated freight dilutes margin and is also the only thing that fixes driver turnover — which changes both the diagnosis and the order of the fixes. The metrics that decide it here are revenue per loaded mile, driver turnover, deadhead percentage, 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 revenue per loaded mile and driver turnover. 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 · ไทย · हिन्दी · עברית