Portable Playbook · Framework

The Carthage Test

When Outsourcing Crosses Into Structural Dependency

Section X · CROSS-CUTTING PLAYBOOKS: ALEXANDER TO BEZOS · Alexander to Bezos

Convenience means you chose the vendor because they are better. Dependency means you can no longer do the work without them. The symptom is a strange incuriosity about how things work.

How It Works

For every outsourced function, answer: if this supplier disappeared tomorrow, could you perform this function yourself within 90 days? If no, you have made the Carthaginian bet.

Carthage outsourced its military for the same reason companies outsource engineering: citizens preferred commerce to conscription. The arrangement produced some of the finest military forces in the ancient Mediterranean. It collapsed when the mercenaries died at Cannae and replacements had to be recruited from distant provinces, and collapsed again when the pay stopped and the Mercenary War nearly destroyed Carthage from within. The test is not whether you should outsource. You probably should. The test is whether you have lost the internal capability to even evaluate the work.

How to Use This Today

Any company with outsourced engineering, manufacturing, or customer service.

Run the Carthage Test on each outsourced function with one question: if this vendor disappeared tomorrow, could you perform this function yourself within ninety days? If the answer is no, you have made the Carthaginian bet. But the test has a second, harder part: can your team describe *how* the vendor produces the output, or only *what* the vendor delivers? The distinction is the Carthaginian line. When your team can describe the what but not the how, you have lost the internal capability to evaluate the work. And when you cannot evaluate the work, you cannot detect when quality degrades. You will discover the degradation only when a customer complains, an audit fails, or a crisis reveals that the vendor has been cutting corners you could not see. The specific audit: for each outsourced function, ask your internal team to write a one-page description of the vendor's process. If they cannot do it without asking the vendor, you have crossed the line from convenience into dependency. The vendor knows this. It is priced into every contract renewal they send you.

Vendor renegotiations and the information asymmetry of dependency.

The vendor knows you are dependent before you do. They know it because they track how many of your internal people understand their system, how long it has been since you last ran a competitive RFP, and how deeply integrated their tools are into your workflow. That knowledge is priced into every contract renewal. The countermeasure is not to insource (which is often more expensive than outsourcing). The countermeasure is to maintain what the military calls "organic capability": at least one internal person who understands the vendor's process well enough to evaluate quality, estimate costs independently, and manage a transition to an alternative vendor within a defined timeline. Carthage outsourced its military for the same reason companies outsource engineering: citizens preferred commerce to conscription. The arrangement worked beautifully until Cannae, and then Carthage discovered it could not regenerate a capability it had stopped cultivating three generations earlier.

Which of your outsourced functions have you lost the internal capability to even evaluate, let alone perform? The vendor knows this before you do.