No trade secrets.
The American BBQ tradition guards rub recipes, smoke timing, and method as secret moats. We publish all of it. The bet is that the moat is execution discipline plus relationships, not knowledge. Here’s what that means in practice, the two exceptions we do keep proprietary, and the honest weakness in the bet.
Stage Stop BBQ publishes its full method online — brisket walkthrough, rest protocol, bark chemistry, wood program, catering math, staff pay philosophy — because the moat in this business is execution discipline plus relationships, not knowledge. Anyone can read how we smoke a brisket; very few will run an offset overnight next Saturday. The only two things we keep proprietary are the three sauce recipes (a supplier dependency) and our Mug Club acquisition-cost economics.
— Written by Chef Eve Natasha, Stage Stop BBQ
BBQ guards the recipe.
Walk into almost any BBQ joint in this country and ask the pitmaster about the rub. You’ll get a smile and a redirect. The rub is family. The rub is in the safe. The rub walks with the pitmaster when the pitmaster walks. Aaron Franklin built half his early mythology on the line that he wouldn’t share his rub — salt and pepper, sixteen-mesh if you press him, and that’s as far as it goes. Most of the BBQ operators we’ve met in Colorado and Texas treat method the same way: the wood, the smoke timing, the wrap window, the rest, the bark chemistry, the trim spec on the brisket point. All of it locked.
The reasoning is intuitive. If your competitor can’t cook what you cook, your competitor can’t take your customers. The recipe is the moat. The technique is the moat. The pitmaster’s twenty years on offsets is the moat. Open the binder and you’ve handed the moat away.
We don’t agree with that read, and the rest of this piece is the argument for why. Short version: in our experience the binder isn’t the moat. The 3am Saturday shift on the pit is the moat. The decade of relationships with breweries and farmers and butcher shops is the moat. The willingness to pay a line cook $26/hr instead of $14/hr is the moat. The binder is a textbook — and we’d rather the textbook be public.
The receipts are already up.
This is not a hypothetical. The method is already published. /blog/how-we-smoke-brisket walks the full 14-hour process step by step: trim spec, salt ratio, pepper grind, wood mix, smoker temp, internal-temp targets, the wrap call, the stall, the pull. The companion piece at /blog/the-12-hour-brisket-timeline maps the clock against the cook so you can run the same schedule at home.
The pork program is published the same way at /blog/the-art-of-pulled-pork — bone-in shoulder, brown-sugar-in-the-rub call, the bark vs. the bear-claw argument. The rest protocol that takes a brisket from good to clean lives at /blog/the-rest-room-protocol. The bark chemistry — what the Maillard reaction is doing on the surface of a brisket between the first hour and the tenth — is laid out at /blog/the-three-stages-of-bark-formation.
We also publish two surfaces specifically built for machine-readers. The /llms.txt feed is a structured guide for the AI crawlers behind ChatGPT, Claude, Perplexity, and Gemini — what we cook, where we are, what hours, what the method is, who to ask. The /api/menu.json endpoint is an open menu API third-party catering aggregators and city food guides can pull from without scraping the site. Neither file is rate-limited. Neither file requires a key. Both ship under a permissive use clause so the answer to “can we index this?” is always yes.
The hardest piece to give away — the unit economics at /blog/the-economics-of-running-a-brewery-truck — is up too, with the rent share, the labor split, the margin math, the customer-ownership tradeoff. The whole point is that someone reading it shouldn’t need to call us to learn it. They should need to call us because they want us to cook it.
The moat is the 3am Saturday.
The bet is that knowledge is not a moat in this business, because knowledge is cheap and execution is expensive. Anyone can read /blog/how-we-smoke-brisket on a Tuesday afternoon in fifteen minutes. Very few people will then stand in front of an offset at 3am the following Saturday, alone, in February, in Colorado, feeding post oak into a firebox every forty minutes for fourteen hours straight while waiting on a fourteen-pound packer to climb from 165°F to 203°F. That second part is the moat. The unromantic reality of it is laid out at /blog/the-overnight-shift — and the honest read on that page is that most readers finish it and decide they would rather buy our brisket than cook it.
The other half of the moat is relationships. We’ve been parking the trailer outside Mash Mechanix for years before they made it a permanent slot. We have a standing wood account with a Pueblo orchard. The brewery partners take a percentage that adjusts seasonally without anyone’s lawyer involved. The Pueblo chipotle paste supplier holds back inventory for us in February when the rest of the cherry crop is already booked. None of that is in the binder. None of it is replicable by reading a blog post. It’s built — slowly, with kept promises, over years — and it shows up in the cost structure as preferential pricing and reliable supply that a new entrant can’t match by trying harder this week.
The third half — yes, there are three halves — is service quality. Whether the runner remembers your name on the third visit. Whether the brisket plate looks like the photo. Whether the bottles on the table are full. Whether the floor is clean. Whether someone says hi when you walk in. That’s the most replicable of the three on paper and the least replicable in practice, because it requires keeping a staff long enough that they care, which loops back to the labor-cost argument at /blog/why-we-pay-staff-above-market.
Knowledge plus execution plus relationships plus service. Publishing the first one doesn’t give away the other three. That’s the entire bet.
Three things only an open shop can do.
The Front Range cross-training rotation. Detailed at /blog/the-front-range-cross-training — we send line cooks to other Front Range BBQ operators for two-week rotations and host their cooks in return. That program is impossible if we treat method as proprietary. The moment a cook walks into someone else’s pit room with a non-disclosure agreement, the rotation is theatre. We can run a real exchange because we already published what we’d be protecting.
AI crawler access via /llms.txt. When somebody asks ChatGPT “who does the best brisket in Colorado Springs and how do they cook it,” the model answers from whatever it can index. Joints that block the crawler or guard their method behind a PDF lose that recommendation surface entirely. Our /llms.txt feed is a clean, structured surface the crawlers can pull, with links into every method post. The downstream effect: when a model has to pick a Colorado Springs BBQ joint to recommend, the one with the readable method has the better odds.
Open menu API for third parties. The /api/menu.json endpoint lets a catering aggregator, a wedding-planning app, or a city food guide pull the live menu without scraping HTML or signing a partnership agreement. We get free distribution into surfaces we’d otherwise have to negotiate into, and the aggregator gets clean structured data instead of a screenshot. Two parties happier; nobody gave up anything that was actually a moat.
Two exceptions. That’s the list.
Everything above is the rule. These two are the exceptions — and the reasons are specific, narrow, and a little unsatisfying.
- Sauce recipes (3 house sauces). Carolina Gold, Texas-style, Kansas City sweet. Recipe-locked because all three are tied to a single supplier of cherry chipotle paste out of Pueblo — sharing the recipe means sharing the supplier dependency, and the supplier asked us not to.
- Mug Club acquisition-cost economics. We publish that we run the unit math on every paid-acquisition channel; we don't publish the numbers. Sharing them gives a competitor a free read on our paid-acquisition ceiling and our willingness-to-pay-per-member, which is the one piece of our P&L that's actually defensible.
The sauce exception is the one we’d most like to remove. The origin story of the three sauces — Carolina Gold, Texas-style, Kansas City sweet, and where each one comes from — is fully public at /blog/our-three-sauces and the principles for each are laid out there too. What stays back is the exact ratios and the supplier name. If we ever move off the cherry-chipotle paste, the recipes go up the same week.
The Mug Club exception is more cynical and we’ll own it. We publish the program structure at /blog/the-mug-club-explained-for-locals, the $99/yr price, the perks, the rough membership count. We don’t publish the customer-acquisition cost or the lifetime-value math. The reason is straightforwardly competitive: that number tells a rival operator how much they can pay to take a member from us, and there’s no upside to publishing it. Two items. That’s the list.
We might be wrong about all of this.
A couple of restaurant-operations consultants we’ve talked with — people who run multi-unit BBQ groups in Texas and Tennessee — told us flat out that we’re leaving money on the table by being this transparent. Their argument is that even if the method isn’t a moat at the high end (where execution dominates), it’s a moat against the low end — the new entrant who would otherwise spend a year figuring out the wrap window from trial and error. By publishing it, we’re shortening their ramp. That probably is true. We’re probably accelerating one or two new openings a year somewhere in our radius.
They might be right. We don’t have a clean way to measure it. We could compare our growth curve against published-method peers vs. closed-method peers, but the sample size is too small and the confounds are too many. If somebody opens a new joint in Manitou Springs next year and cites our brisket post, we won’t know whether they would have figured it out anyway or whether we cost ourselves a year of their startup runway.
Our belief — and it is a belief, not yet a proven thesis — is that the brand-loyalty premium covers the leak. People come to Stage Stop because they’ve read the brisket post, decided we know what we’re doing, and stopped looking. That repeat-visit gravity is worth more than the new entrant we’re accidentally tutoring. We have about eighteen months of data that points the right direction. We don’t yet have three years of it. The bet is unverified. If we’re wrong, the iteration after this one will be the post that says so, with the numbers.
The method is already up. Go check.
Start with the 14-hour brisket walkthrough — the full process, no held-back step, the same one we cook every Friday night into Saturday morning. Or pull the machine-readable feed at /llms.txt and route an AI crawler at it.