The Peanut Portco

It's early morning in New York City.

Beep. Beep, beep. My alarm goes off. It's 5 a.m.

Beep. Beep.

I hit snooze.

BEEP. BEEP.

It's six, seven. I'm late for my commute. I jump out of bed, brush my teeth, take a quick shower, and open my massive walk-in closet to a row of identical white and blue shirts. I pick the one I always wear (it's either blue or white), then throw on my trousers, my suit jacket, and my sneakers, because the sidewalks of New York are one giant petri dish.

I walk to the PATH, same as every single day. I love the smell of the train in the morning: coffee, warm garbage, and a mystery note that I've stopped trying to identify.

My phone rings. I forgot to check my email. I'm on the train, and suddenly it's a fire drill.

My VP starts yelling at me. I need to put a deck together in two hours for the MD to review. One of our senior operating partners has a buddy who owns a pickle jar manufacturer. Just the jars. No pickles. The operating partner wants us to buy it as the platform for a pickle jar roll-up. The investment thesis is that brine is a commodity, but glass is a moat. The deal is priced at 12x EBITDA, and half the EBITDA is add-backs. Financing is a unitranche from a private credit fund with a PIK toggle, and the seller wants his rollover as pref equity. Management justifies the valuation with a TAM slide that counts every refrigerator in North America, and they swear revenue is 100% recurring, assuming each customer reorders one pallet per quarter.

I build the returns model, build a DCF out of habit from my banking days, delete it before anyone sees, and send the deck to my VP. He sends it back: "Please fix." It's a stray number in my sources and uses. "Damn it," I say under my breath. I delete the number and send it back. The VP sends it to the MD.

The MD just forwards the email back to the VP.

The VP messages me: "We need to tighten this." I lose my mind. I have no idea what he wants me to correct. I go through the whole presentation again, hunting for every error and making sure all the numbers tie. Finally, I change a few formatting things and send it back.

My VP, now satisfied, sends it to the MD. The MD screams at the VP: "I don't want this color in the title. Change the color." My VP sends the deck back to me, I change the title, and it goes back up to the MD.

The MD, now satisfied, walks the presentation over to the operating partner.

The operating partner never uses it.

I eat lunch at my desk. It's the best part of the job. I look up and remember the Equinox membership I never use.

My girlfriend starts calling. I can't pick up. I'm deep in a scenario analysis for one of our portfolio companies, a peanut-counting operation, and this is the project that's going to define my career.

I look at my model. If we buy 20 machines, the peanut count goes up marginally. If we buy 10, the peanut count also goes up marginally, but the capex is lower. Airtight. Elegant. I've basically found free EBITDA. I confidently walk over to my VP and present my findings.

He gives me a long, tired look and says, "Do you even know how peanuts are counted?"

He walks me to a conference room, sits me down, and says, "Listen. I've been in the game for almost four years post MBA. You have no idea what you're talking about."

Then he starts assigning. He wants a full operational deep-dive on the portfolio company by morning. He wants me to rebuild the model bottom-up, peanut by peanut, no more lazy top-down counting. He wants a 20-page deck with a recommendation on whether we hold or exit the peanut business at the top of the cycle. He wants a shell-adjusted EBITDA bridge. He wants sensitivities on the price of a single peanut. He wants a comps set, but there are no comparable public peanut companies, so I'm told to "be creative." He wants channel checks with the actual peanut counters on the factory floor. He wants a management quality assessment of the head peanut counter.

Then he tells me he wants me to expense a bag of peanuts, eat every one, and write a paragraph on the "lived experience of the product" so my analysis finally has some credibility.

He tells me if the numbers don't tie by 6 a.m., I shouldn't bother coming back.

I look at him. His receding hairline glistens under the fluorescent lights, and his dry red eyes look deep into my soul, daring me to challenge the instruction. I'm afraid, but deep down, I know I have to do this. This is my life's work. I love creating value. So I take the assignment, roll up my sleeves, and get back to the grind.

I reluctantly pick up my phone, check my fantasy football team, and start crying.

Then an MD walks up and asks me why we use subscription lines. I nod thoughtfully, buying time, then give him the honest answer: "So we can call capital later and the IRR looks better."

He stares at me. "Never say that in front of an LP." He walks away.

I carry on. I clean up a few Excel sheets, have Claude fix a circular reference I'll take full credit for in my year-end review, rebuild three returns models nobody asked for, and save the deck as "FINAL_v7_ACTUALFINAL_USE_THIS." Around 9 p.m., I finally board the train home.

On the ride home, a homeless guy hucks an egg at me. It explodes at my feet, all over my sneakers. Thank God I didn't wear the loafers. I briefly consider being upset, then remember bonus season is coming. I'm fine.

I get home, exhausted. My girlfriend is pissed. But there's no sleep tonight. I stay up until 1 a.m. tying all the peanut comps together, and slowly, somewhere around the fourth returns case, I stop seeing numbers. I'm seeing peanuts. Every cell in the model is a little shell. My bull case is a world at peace, drowning in peanuts. My bear case is a single, cracked, lonely peanut rolling across an empty warehouse floor.

Finally, the numbers tie. I flop, completely naked, into bed and set my alarm for the next day.

Six, seven. Six, seven.

My alarm rings.

The endless cycle.