Before the Logo

How to Build a Brand With No Money

The first time I walked into the studio, I wasn't the one shooting in it.

By then I'd moved into product development. Marketing had real people in real seats. The brand had a budget. The studio was a building on the property, with lights and backdrops and a clean floor and enough room to pull a mower or a UTV in from the assembly line, shoot it from every angle, and have the images on a hard drive before lunch.

It was the operation we'd needed for years.

I'd just stopped being the one who needed it.

I want to back up, because the studio didn't appear because somebody put it on a wishlist. The studio appeared because of what came before it.

Before it, there was Springfield.

The web devs had asked for proper 360° product spins — the kind where you can click and drag a mower in your browser and see it from every angle. Real spins. Not seven photos stitched in Photoshop. Real, controlled studio shots delivered as a sequence.

We didn't have a place to do that. So we loaded machines onto a trailer and drove them to Springfield, Missouri, to a studio that did. Indoor. Controlled. Cyclorama wall. Lighting rigs that cost more than my truck. A turntable for the spins. A photographer who knew exactly what the web team needed because the web team had told him.

I remember standing in that studio watching the first spin happen and thinking: this is what doing it right looks like.

That was the moment that made the rest of what I was doing impossible to ignore.

Because the rest of what I was doing looked nothing like that.

The rest of what I was doing was a dealer's pasture outside town with a borrowed UTV and whatever light God gave us that afternoon. A treeline that worked from one angle and ruined the shot from the other. A friend-of-a-friend who owned land that looked right but wouldn't let us bring more than two machines because his wife was tired of trucks in the driveway. A photographer working out of his garage who'd quote us a price that fit our budget and then we'd spend a day driving machines to him.

I had a sponsorship deck and a placement network that lived in my head and a contact list of every dealer, rider, event organizer, and land-owner within four hours of Batesville who'd said yes to me at least once. The brand we were building was the product, yes — but it was also the evidence of the product. Photos. Video. A rider on a Spartan at an event. A UTV on a dealer's lot in a real customer's town. A placement at a trade show. A magazine spread we'd traded a machine for.

All of it cost a trip. A trailer. A favor. A week of someone's time.

I did this for years.

By the time Springfield happened, I had filing cabinets full of negotiated agreements, scouted locations, photographer rates, sponsorship terms, event sheets. I had a working operation. It just wasn't a studio. It was a Rolodex and a willingness to drive.

Here's the thing nobody told me at the time.

The Rolodex was the case.

Every favor I called in, every dealer's pasture I shot in, every five-hour haul to somebody else's facility — those weren't the cost of doing the work. Those were the documentation. Every one of them was a data point in a case file I was building without realizing it. A case for what the company was actually doing and what it actually needed to keep doing it.

When somebody eventually said "we should build a studio," there was no argument to have. The case had been built. By years of trips. By the gap between what Springfield gave the web team and what I was still doing for everything else. By the cost — not the budget cost, the opportunity cost — of every week the marketing department couldn't function because the marketing department was on a road trip.

The studio didn't get built because somebody at the company woke up and decided the brand needed better infrastructure. The studio got built because the turmoil of not having one had become more expensive than building one.

That's how real infrastructure gets justified. Not by wishlists. By turmoil.

I want to be careful here, because this is the part that sounds like a humblebrag and isn't meant to be.

I didn't suffer through those years on purpose. I wasn't building a case file for the studio. I was doing the work. The case file built itself. By the time the studio was justified, I'd moved on — into product development, then into a series of roles I'll get into in Season 2 — and the studio became somebody else's tool. Which is fine. That's how it's supposed to work. You build the case by living the problem. Then somebody who didn't live the problem gets to use the solution.

What I want you to take from this is the order of operations.

You don't get to skip the turmoil. The turmoil is what tells you what you actually need.

---

If I'd Had AI…

This is the post where I have to be more honest than usual.

A version of this story that a tool vendor would tell you goes like this: if Matt had had AI back then, he wouldn't have needed Springfield, the dealer pastures, the borrowed land, the photographer-out-of-a-garage years. AI image and video tools can produce a passable mower-in-a-pasture render from a CAD file. AI scheduling can run the sponsorship network. The whole turmoil compresses into an afternoon. No road trips. No favors. No filing cabinet of beg/borrow/steal agreements. You skip straight to the studio-quality output.

That's true. That's literally what those tools do.

It's also exactly the wrong way to deploy them.

Because the turmoil isn't waste. The turmoil is the case. The reason I know what a Spartan looks like in the right light is because I shot it in the wrong light a hundred times. The reason I know which sponsorship investments pay off is because I made the bad ones first. The reason I knew what the studio needed to be — what the workflow had to look like, what kinds of shots had to come out of it, how it had to fit into the rest of the operation — is because I'd spent years not having it.

It's the piece of infrastructure they want before they've earned the right to want it. They've seen what their competitor does with it. They've seen the demos. They've decided they need it. So they buy it and try to deploy it on top of an operation that has no case file under it — no turmoil documented, no problems identified, no judgment built about what the tool is even supposed to do for them.

The companies that win with AI in the next ten years aren't going to be the ones with the most tools. They're going to be the ones who've already lived the version of the work that AI now makes optional. They've earned the right to skip the turmoil because they've already done it.

That's the advantage of doing it the hard way first.

That's what 18 years of doing it the hard way taught me.

That's what I bring to every client engagement now — the discipline of not skipping the turmoil before you've understood it.

---

That's Season 1 of From Burnout to Buyout.

Next week we move into Season 2: Every Hat in the Building. The years when I was doing marketing AND CAD design AND project management at the same time. When the hat count went up faster than the headcount. When the work that built the case file for the studio was running in parallel with three other jobs.

The road to product development started in those years.

It gets real.

What's a piece of infrastructure your business wants right now that it hasn't yet earned the case for?

---