Your Ops Are Your Product (Whether You Like It or Not)
- May 6
- 3 min read
By Jeffrey Frese
Every founder I know has a moment where their business breaks. Not from bad marketing. Not from bad product. From the thing nobody wants to talk about at founder dinners: their ops.
I'm Jeff Frese, founder of Eat My Face — a bootstrapped tallow skincare brand selling across Amazon, Shopify, and direct channels. I've rearchitected my infrastructure twice. Both times it cost me months of productivity and made me wish I had a time machine.
Here's the truth nobody told me: infrastructure decisions ARE product decisions.
When I chose centralized manufacturing over regional suppliers, I didn't just pick a logistics option. I chose the kind of brand I could be. When I picked just-in-time inventory over safety stock, I chose my margin structure — and my ability to sleep at night during a viral TikTok. When I went multi-channel, I didn't just add revenue — I added 4x the ops complexity and my weekends disappeared.
The three questions most founders skip
Most founders obsess over the product and ignore the ops until it hurts. Or they over-build systems way before they need them and get punished when reality forces a pivot. Both mistakes cost the same thing: time.
1. What does failure look like at 10x volume? Your scrappy founder workflow — the spreadsheet, the personal inbox, the Thursday night warehouse run — will collapse the moment your demand doubles. Don't ask "what works now?" Ask "what breaks when this works?"
2. What am I willing to outsource, and what will I regret outsourcing? Everything you outsource saves time but costs control. Everything you keep in-house builds expertise but caps your speed. The right answer depends on your unit economics, your cash position, and your personal risk tolerance. There's no correct default.
3. Which decisions are reversible, and which ones compound? A bad Shopify theme is easily fixed. A bad co-manufacturer contract, a bad fulfillment integration, or a bad ERP choice? Those compound for years. Know which category every decision lives in, and pay for expert advice on the compounding ones.
The brutal math of rebuilding
Here's what nobody tells you about the "let's just rebuild it later" plan: it always costs more than you think.
When I rearchitected our order management, I lost six weeks of growth. Customer service friction spiked. Returns piled up. Amazon flagged us. I fixed it, but the real cost wasn't the six weeks of lost revenue — it was six weeks of broken momentum. That's brutal for a bootstrapped company running on its own cash.
The founders I know who scaled gracefully didn't skip the ops conversation early. They leaned into it. They over-engineered just enough to absorb a 10x shock without collapsing. And they did it before they had the money to do it comfortably.
The ops you build is the brand you become
The truth nobody wants to post on LinkedIn: infrastructure creates culture. Your fulfillment decisions show up in your reviews. Your inventory decisions show up in your customer service threads. Your supplier decisions show up in your margin reports.
Your ops isn't backroom work. It's the quiet version of your brand strategy.
Build it like you mean it. Or rebuild it twice — and pay me the therapy bills in five years.
Connect With Jeffrey
Comments