top of page

Salad and Go Didn't Have a Bad Idea. It Just Got Tossed One Too Many times. Why Did It Go Bankrupt?

Aug 28
4 min read

Salad and Go looked like somebody had finally cracked the salad problem.

Healthy food. Drive-thru convenience. Tiny restaurants. Affordable pricing. No giant dining room to staff or heat. Fast service. Basically, a salad concept designed by someone who'd actually looked at a restaurant P&L instead of just a menu board.

I've spent a good chunk of my career building health-conscious concepts myself, DIG's vegetable-forward menu, By Chloe's plant-based platform, so I watched Salad and Go's model with real interest. On paper, it solved problems I've personally wrestled with: how do you keep a produce-heavy menu profitable at volume without either raising prices past what people will pay or cutting corners on quality until the whole point of the concept disappears.

Then it went bankrupt. Salad and Go filed for Chapter 11 on August 4, 2026, and closed all 70 remaining restaurants the very next day.

The interesting question isn't whether Americans like salad. They clearly do. The better question is why salad is so much harder to scale than it looks.


We've Seen This Movie Before

Salad concepts have been trying to solve this equation for decades. Tossed was an early player, launching in New York in the late 1990s with big ambitions around customizable salads. Chopt followed with a far more disciplined regional footprint, concentrating heavily where it could build real density and brand recognition. Then came Sweetgreen, arguably the strongest brand the category has produced, proof that salad could be culturally relevant, digitally sophisticated, and genuinely scalable.

But even Sweetgreen shows that scale doesn't automatically make restaurant economics easy. Which is what makes Salad and Go so interesting. It tried attacking the problem from a completely different direction.

Salad and Go the company that got tossed to much. Salad and Go Tried to Fix the Economics

Instead of expensive urban restaurants, Salad and Go went small, roughly 750-square-foot drive-thrus, centralized food production, limited front-of-house labor, fast throughput, affordable salads and wraps. The model worked well enough to grow aggressively, eventually reaching 146 restaurants at its peak.

Then growth itself became part of the problem. The company expanded hard into Texas and Oklahoma while simultaneously building out centralized production infrastructure ahead of proven demand. That Texas commissary alone represented more than $70 million of total investment, carrying real fixed overhead. Some of the newer stores struggled with visibility and access, and the entire Central Region turned significantly cash-flow negative. That's the moment a clever operating model quietly becomes a dangerous financial one.

Then Lettuce Became the Headline

As if salad concepts needed another challenge, 2026 brought one of the largest reported Cyclospora outbreaks in U.S. history. By late August, more than 11,000 illnesses had been reported across 20 states, linked to iceberg lettuce from a Taylor Farms operation in central Mexico.

This wasn't just a Salad and Go problem. It became a perception problem for the entire fresh-food category. Consumers don't always distinguish between grower, distributor, supplier, and restaurant brand, they just hear "lettuce is making people sick." For a burger concept, that's an inconvenience. For a salad concept, that hits the hero ingredient directly. Even Cava reported a short-term sales impact despite saying it never sourced from the implicated suppliers.

Cyclospora didn't create Salad and Go's problems. The company itself said as much, the outbreak wasn't the root cause. But it compounded an already difficult financial situation and further weakened consumer confidence at exactly the wrong moment. When traffic's already soft and the balance sheet's already under pressure, a national lettuce scare is not the side salad anyone was hoping for.

Chicken Has One Advantage Lettuce Doesn't

There's a structural issue here too. Salad has a narrower occasion than most proteins. Chicken can be lunch, dinner, a kids' meal, family dinner, drive-thru, delivery, comfort food, and healthy-ish food if everyone politely ignores the fries next to it. Salad usually starts with a direct question: "do you want salad?" One "no" ends the transaction right there.

That means salad concepts need exceptional location strategy, frequency, convenience, and brand loyalty just to survive, let alone scale. The category can absolutely work, Sweetgreen proves it, Chopt proves it, but it may demand more discipline than the industry likes to admit.

The Real Lesson Isn't About Salad

Restaurant companies love the word "scalable." But scalability was never about how quickly you can build the next restaurant. It's about how reliably that next restaurant produces attractive economics, and there's a huge difference between the two.

Tossed showed that being early isn't enough. Chopt shows the value of disciplined market development. Sweetgreen shows that even a genuinely powerful brand has to keep fighting for traffic and margin. And Salad and Go showed exactly what happens when infrastructure and expansion get ahead of proven demand.

I built DIG's systems the opposite way, prove one location cold before touching a second one, and it's the rule I've carried into every concept since: don't scale the concept, scale the proof. Prove the restaurant. Prove the market. Prove the cluster. Then, and only then, build the infrastructure underneath it.

Because 150 restaurants on a presentation deck look fantastic. Seventy restaurants in bankruptcy court look considerably less impressive, and nobody's framing that slide for the office wall.

Salad and Go may have genuinely had the right idea. It just tried to scale the future before the economics were actually ready for it.

Thinking about how fast to scale your own concept? That's usually the most important conversation to have before the infrastructure gets built, not after.


 
 
 

Comments


© 2026 Daniel Angerer

  • LinkedIn
bottom of page