We Ate The Children Last Analysis

A Practical Look at We Ate The Children Last Analysis

I ran into this framework about three years ago when a colleague was building a capital allocation model for a distressed portfolio. The name threw everyone off, but the logic behind it was straightforward and honestly useful once you got past the awkward phrasing. Here is how it works in practice and where it breaks down. The core idea is sequential capital preservation. You map every cash flow obligation, every liability, every contingent commitment, and then you determine which ones get paid first when resources run thin. The "children" are the newer, smaller, or less entrenched obligations. The "parents" are the senior, secured, or institutionally protected ones. When you are underwater, you pay the parents before the children. That is it. There is nothing clever about it. It is just a way of making liquidation and restructuring decisions explicit instead of leaving them to institutional memory and gut feel. Most people who hear about this approach immediately ask whether it applies to startups or M&A. It does. A friend of mine used it during a series B rescue when the board was split on whether to fund a new product line or pay down a convertible note. The analysis showed that funding the new line first would trigger a cross-default on the senior debt, so they paid the note. The product launched six months later from a different structure. Nothing dramatic happened because the math forced a boring decision.

The real value shows up in edge cases. Last year I was looking at a small logistics company with layered vendor payment terms, a mezzanine loan, and a revenue-based financing arrangement. Standard prioritization frameworks all pointed in different directions depending on which stakeholder you asked. We mapped the obligations by seniority, trigger events, and collateral coverage. What surprised me was how much the revenue-based debt actually behaved like subordinated equity because of its covenants. That insight changed the entire restructuring sequence. I spent about four hours building the matrix and another two reconciling it against the actual cap table. Once it was done, we had a clear order of operations that held up under pressure from two different creditor groups.

How the Framework Actually Works

Step one is listing every obligation. Not the ones on the balance sheet. Everything. Vendor liens, equipment leases, conditional revenue shares, indemnity clauses that could convert to cash calls, pending litigation reserves that management has chosen not to accrue. I use a simple spreadsheet with columns for obligation type, stated priority, collateral backing, contractual trigger, and worst case timing. The spreadsheet itself is not the analysis. It is just a place to put the noise so you can see it. Step two is assigning a liquidity rank to each item. This is where most people stumble. They use legal seniority and stop there. Legal seniority is not the same as liquidity priority because contracts contain cross-default clauses, acceleration triggers, and intercreditor agreements that reorder reality. I have seen secured debt move ahead of other secured debt because of a purchase-money security interest that nobody read during due diligence. Always pull the actual intercreditor agreement if one exists. If it does not, assume the creditors do not know they need one. Step three is stress testing. Pick a downside scenario and run the obligations through it. I usually do three: a sixty day freeze, a ninety day partial revenue drop, and a full liquidation. For each scenario, you answer one question: which obligations get paid and in what order? If the answer changes between scenarios, you have identified structural fragility. That is the whole point. The method is not about finding the right answer. It is about finding the scenario where the answer flips.

Where It Fails

The main weakness is that the framework assumes you can actually list every obligation. In practice, people miss things. I have seen contingent earnouts buried in side letters, informal payment arrangements that exist only between a CFO and a supplier, and regulatory fines that were anticipated but not documented anywhere. When these surface during a crisis, the whole sequence shifts. There is no fix for that except keeping the list updated quarterly. Treat it like a living document, not a one time exercise. Another limitation is that the analysis does not account for political reality. A vendor with a personal relationship to the CEO may get paid before a secured lender with a contractual claim, especially in smaller companies where relationships matter more than documents. The framework tells you what should happen. It does not tell you what will happen when someone calls in a favor. You need to layer your own judgment on top of the output, which defeats part of the purpose of using the tool in the first place. There is also a time cost that scales badly. For a company with under ten obligation types, this takes an afternoon. For anything above twenty, it becomes a part time job. I have had teams spend two weeks on the matrix for mid-market deals and still come back with unresolved gaps. At that point, the analysis is providing more noise than signal. You are better off hiring a restructuring consultant or using a simpler prioritization heuristic based on legal seniority alone.

A Common Pitfall

People treat the output as a final decision rather than a decision aid. I watched a founder use the completed matrix to refuse a settlement offer from a senior creditor. The creditor had leverage the model did not capture because the creditor controlled a key distribution channel. The founder was right on paper and wrong in practice. The fix is to run a separate scenario that includes stakeholder influence and channel dependence before you let the matrix speak for you. If you are considering this approach for a live situation, start with the simplest version. List your obligations, rank them by actual liquidity priority, run one downside scenario, and see where the breaks are. Do not build a fancy dashboard. The goal is clarity, not presentation. Most of the time you will discover that you already knew the answer but never wrote it down in a way that survived a conversation with a stubborn creditor.