The $3M Logistics Build We Didn't Do

I knew the answer in week two.

Not with the clarity I have now — I did not have the framework then, and clarity is always easier looking back. But I knew enough to ask the right questions. What I did not have was a structure that forced me to answer them honestly.

The venture was a logistics analytics platform. The host was Intel — a hardware company with a salesforce built to move silicon on quarterly quota cycles. The venture needed multi-year, relationship-intensive service contracts. Not as an aspiration. As a structural requirement: the revenue model only worked if customers stayed on multi-year agreements, and multi-year agreements required a sales motion, a compensation structure, and a deal-cycle cadence that Intel's salesforce was not built to execute.

The salesforce was not the problem. They were excellent at what they did. What they did was sell silicon. The analytics platform was asking them to do something structurally different — and the math of how they were paid, how their quota was structured, and how their performance was measured made that different thing essentially impossible, regardless of how compelling the product was.

What I Told Myself

I told myself the salesforce would adapt. I told myself that executive sponsorship at the right level would create enough air cover to restructure the go-to-market motion. I told myself that the organizational gaps would close with enough momentum behind the product.

I spent six months telling myself those things.

The salesforce did not adapt. Not because they were unwilling — several of them were genuinely interested in the product — but because the compensation system did not reward the behavior the venture needed. Compensation systems are more powerful than enthusiasm. The executive sponsorship helped with budget and visibility. It did not restructure how the salesforce was evaluated and paid.

The gaps did not close. They could not close. What I was experiencing was not a culture problem or a leadership problem or a product-market fit problem. It was a structural host mismatch — the kind of mismatch the RPP framework now identifies in days rather than months.

What the Structural Read Would Have Shown

Running the RPP rubric retrospectively against this venture produces a score of 4 out of 8 — Danger Zone. Not obvious misalignment. The kind that looks survivable on paper and is not.

The two questions that would have scored zero: Is the salesforce compensated to sell what this venture will produce? Does the organization have a track record of commercializing ventures of this go-to-market complexity?

Both of those questions were answerable with evidence in week two. Intel's salesforce compensation structure was not proprietary information. The organization's track record in services-based go-to-market was a matter of internal history, accessible to anyone who asked.

I asked. I rationalized the answers.

RPP 4/8

The Verdict Was WRONG COMPANY

The eventual outcome confirmed the structural read. The venture was restructured — not as an internal Intel product, but as a partnership with an established logistics analytics provider. Intel captured data access and ecosystem positioning without taking on the organizational cost of building a services sales motion from zero.

The idea was right. The host was wrong. Restructuring around a partnership rather than internal incubation was the correct call — and it would have been the correct call six months earlier, before the political capital and organizational patience had been spent.

A WRONG COMPANY verdict is not the end of the idea. It is the beginning of finding the right structure for it.

The Test You Can Run Right Now

If you are inside a venture today and the answer to "is the salesforce compensated to sell what we are building" is anything other than a clean yes — that is the whole story. Everything else is rationalization waiting to happen.

The methodology the firm uses today exists because that question was answerable in week two and went unanswered for six months. The RPP rubric forces a 0-or-1 answer to it. The discipline is intentional.