Justin Smith

I rebuild messy service businesses.

The product first, then the demand, then the pricing, then the software that holds it together. I do all four myself. Right now I run operations, marketing, and sales for a multi-site outdoor recreation company in Idaho, and I wrote the platform it runs on.

A large whiteboard covered in hand-written names, dates, and colored lines: the operations schedule for a multi-base rafting company before it was replaced by software.
This ran the company. Every trip, guide, driver, vehicle, and shuttle for the season, in dry-erase marker, held together by whoever remembered what the colors meant. It worked until it was the ceiling. Replacing it is most of what I do.

What I actually do

Most operators are either a systems person or a growth person. The work I do needs both, because a demand engine pointed at an inconsistent product just manufactures bad reviews, and a beautifully run operation nobody can find doesn't survive either.

So the sequence matters. Standardize the product so it's the same every time. Build demand where there wasn't any. Price for the demand once it exists. Then build the operating system so growth doesn't turn into chaos, and so the business stops depending on whoever happens to remember everything.

Selected work

A raft full of teenagers and guides dropping through a whitewater rapid, paddles raised, water breaking over the bow.

Where I'm useful

Experiential and outdoor hospitality, multi-unit service businesses, and vertical software serving them. The problems repeat: seasonal labor in places nobody wants to commute to, capacity that's gated by permits or physical constraints, inventory that perishes nightly, and an operation that lives in one person's head. All four are solvable.

More about me · Get in touch