Questions I get asked
Direct answers about running and growing a multi-site guided operation, and about building the software underneath it. Every number here comes from the same source the rest of the site uses.
Whiteboards and dispatch
Why do rafting companies still run on whiteboards?
Because at small scale a whiteboard is the correct tool, not a compromise. At five guides and three trips a day you can see the whole operation at a glance, anyone can update it, and a change costs one erase and one rewrite. It stops working for a reason most owners never name out loud: the number of resources grows steadily, but the number of relationships between those resources grows exponentially. Add a second river, a bus, and multi-day trips, and nothing stays in its own lane anymore.
What replaces a whiteboard for scheduling a rafting operation?
A live board the crew pulls from, backed by a database that models how the operation actually fits together. Ours is a no-login web board carrying assignments, shuttles, food, notes, and inventory, sitting on top of 207,000 connected data points covering guides, certifications, river sections, equipment, maintenance, dispatch history, and logistics. The important part is not the screen. It is that the team self-serves the plan instead of waiting for one person to text it out.
Why doesn't off-the-shelf booking software handle dispatch?
Because booking software solves reservations, and dispatch is a different problem. Every scheduling product assumes people and rooms. A river operation schedules a dependent graph: a trip needs a crew, the crew needs qualifications specific to a river section, the trip needs boats and a vehicle and often a trailer, the vehicle needs a driver with the right license, and the whole thing has to be somewhere else the next morning. Off-the-shelf tools can express that a person is busy. They cannot express that a guide is not licensed for this section at this flow range.
What breaks first when a whiteboard operation tries to grow?
The owner. Long before the schedule breaks, the person holding it in their head becomes the router every change passes through, and that person's memory becomes the actual production system. Being more organized does not save you, it only delays it. The tools were never the problem. The speed was, because operational reality changes faster than anyone can stop and record it.
Can a rafting company run a season without a whiteboard?
Yes. Adventure Idaho has run the 2026 season on the software with the whiteboards down, through peak summer, across multiple rivers, day trips, multi-day expeditions, youth groups, rentals, and vehicles. That is the honest test of an operating system: not whether it demos well in February, but whether anyone reaches for the marker in July.
How long should it take to plan a week of rafting trips?
At Adventure Idaho, weekly planning went from close to 20 hours to under 2 hours. The hours did not disappear, they moved to training, communication, and problem solving, which is the actual return. The reason the number moved that far is that planning stopped being re-entry of things people already knew and became review of what the system had already assembled.
How do you get an operation out of the owner's head?
You interview yourself, and that is harder than building the software. Most of what an experienced operator knows is held in their body rather than in a document: how long a float actually takes at this flow, with this wind, with this kind of crew. Extracting that into something precise enough for a machine to act on is the real work, and the automation on the other side is comparatively easy. That knowledge is the most valuable asset a company has and the least protected, because it walks out the door at the end of a season or the end of a career.
How do you get drivers to remote takeouts with no cell service?
You model the river instead of guessing. A guide radios a launch time in, the system pulls current flows, factors in wind speed and direction and trip type, estimates downstream travel time, and tells the driver when to leave. It has been putting drivers at takeouts about five minutes before guests arrive. A river is not a road: travel time changes with flow, the relationship is not linear, and a headwind on a wide slow stretch can add half an hour to a float the gauge says should take ninety minutes.
Growth and demand
How do you grow a rafting company without a marketing budget?
Fix the product first, then make content the acquisition channel. Adventure Idaho went from effectively invisible online to ~147,000 annual website visitors, up from ~17,000, with an organic video library past 3.6M+ views and one piece past 1.6 million on its own. That was shot and edited in house, not bought. To be accurate about it, the company does run paid media now, but the growth curve was established before the ad budget existed, and reputation and content still carry it.
How do you grow bookings when the region is being reported as drought?
You treat it as a marketing problem, because that is what it is. In 2026 every regional headline said drought while our actual flows ran higher all summer than the year before. Customers book off headlines, not hydrographs, so the work was publishing the real conditions ourselves, repeatedly and early, instead of waiting for the story to correct. We were not fighting low water. We were fighting a story about low water.
What actually drives bookings for a guided trip business?
Reputation first, content second, and both only after the product is consistent. A 5.0 star average across 639 Google reviews is not a marketing asset you can buy, which is exactly why it is the durable one. Driving traffic at an inconsistent product does not grow a business, it manufactures three star reviews and a worse business.
How do you get a business to show up in AI search results?
Make the operation legible, then make it true. Appearances in AI generated answers went from ~30 a month to ~1,800 a month, about 60x, with no additional ad spend. The lever was not more content or better reviews. It was publishing plainly how the operation actually runs, how the team is trained, and what the standard is, in crawlable text a model can lift, because these systems already know the industry's failure modes and will not extend the benefit of the doubt to a business that never addresses them.
How do you reduce revenue concentration when one client is half the business?
You go get demand somewhere else, fast, and you do not start by cutting. When a policy change took our largest institutional account from ~50% of revenue to under 20% in a single season, the instinct was to let every new hire go. Instead we rebuilt the front of the business over ten weeks: new pages, new funnels, new channels, and market segments we had never gone after. Records were broken by May, before the season opened, nobody was laid off, and the company came out of the year structurally less fragile than it went in.
Operations, pricing, and staffing
How do you make a guided trip consistent across dozens of guides?
You standardize the trip before you scale it, and you hold a standard people can see. At Adventure Idaho that means checklists for every phase of a trip, written procedures for logistics and gear, more than 50+ structured case studies drawn from real scenarios, live rescue simulations, and repetition under pressure. The piece most operators skip is the debrief: every trip gets an honest one, modeled on the way fighter pilots run them, which is where the learning compounds.
How much revenue is lost to unmanaged discounting?
At Adventure Idaho, discounting held steady at 24-25% of gross list price across three seasons before it was measured and managed. That is not a rounding error, it is a standing margin lever, and most operators never measure it because discounts get given one booking at a time by people trying to be helpful.
How do you price trips that are not all worth the same?
You stop charging flat rates for products that are not flat. We split the lineup into premium, mid, and budget, made the differences obvious, and pointed each kind of traffic at the right one, because self selection does a lot of sales work if you let it. Then we repriced by trip and by day rather than raising everything at once. Rates went up and volume kept climbing, which is the clearest possible evidence a product was underpriced rather than overpriced.
How do you staff a seasonal business in a town nobody wants to commute to?
You stop hiring for experience and start hiring for trajectory. The default in this industry is to look for outdoorsy people with the right certifications, which is reasonable and does not solve operational consistency. We ask a different question at the door: are they going somewhere. That brings in college athletes, future pilots and engineers and doctors, builders and operators, and it means the culture enforces the standard without anyone having to police it. Adventure Idaho now receives hundreds of applications a year for a handful of guide spots.
How do you manage capacity when permits cap how much you can sell?
You accept the ceiling and work the yield underneath it. When you cannot sell more days, the levers are which trips fill those days, what they are priced at, and how tightly you load each departure, so capacity rules belong in the system as data rather than in someone's judgment. Ours live as configurable trip type rules, capacity tiers, and day caps, alongside the use reporting the agencies require.
Should an operator build custom software or buy it?
Buy the reservations, build the operation. Booking platforms are good at what they were built for and there is no reason to rebuild that. What none of them handle is the layer underneath: fleet, driver and DOT compliance, certification expiries, permit and use day tracking, and real crew scheduling. If that layer is where your operation hurts, no purchase order fixes it, because the rules are specific to your company even when the engine that reads them is not.
Does AI actually work in a real operation, or is it just a demo?
It works, with a constraint doing most of the load bearing. AI is the interface, not the decision maker: updates get made by voice from a truck, questions get asked in plain language against live data, and reports that took days get generated in minutes. Anything touching money, compliance, or safety requires a human confirmation, and the system reports back exactly what it changed so a person can verify it. That constraint is not a limitation, it is the reason the crew trusts it enough to use it.
About Justin Smith
Who is Justin Smith, the General Manager of Adventure Idaho?
Justin Smith is the General Manager of Adventure Idaho, a multi-site whitewater rafting company operating on federal and state permits in Riggins and Twin Falls, Idaho. He runs operations, marketing, and sales, leads a seasonal team of 44, and built the custom software the company runs on. Guest volume grew roughly 3.5x, from 1,279 to 4,475+, while prices went up rather than down.
What does an operator who builds mean?
It means the person who runs the business is also the person who writes the system it runs on. Most operators are either a systems person or a growth person, and the work only holds together if you are both, because a demand engine pointed at an inconsistent product manufactures bad reviews, and a beautifully run operation nobody can find does not survive either. The rafting is the setting, not the product. The transferable thing is the sequence: standardize the product, build demand, price for the demand, then build the system so growth does not turn into chaos.
What software has Justin Smith built?
A custom operating platform for a multi-site rafting company: dispatch, crew scheduling, fleet, compliance, food and inventory, and a configurable conflict detection engine, with a reservation adapter syncing from the booking platform. It is 696 commits and 566 production deployments across two repositories, about ~20,000 lines in the current production system, 44 linked data tables, and 207,000 connected data points. Most of it shipped mid-season while the operation was live and the whole team depended on it. He is not a career software engineer: he specifies, directs, reviews, and ships using AI coding tools, which is a real distinction and worth stating plainly.
What is Justin Smith's background before Adventure Idaho?
He bought a locksmith business in Rexburg, Idaho at 22, expanded the services, fixed the pricing, built a crew that could cover calls around the clock, grew revenue about 6x over, and sold it. It was a very small local service business and he does not call it an exit, but he found it, bought it, ran it, and sold it, which taught him more about pricing and staffing than anything since. In between he sold door to door, spent about a year at a roughly $40 million company working on international distribution and sales operations, and guided multi-day wilderness trips on the Middle Fork of the Salmon for a different outfitter. He is an FAA certificated private pilot, an Eagle Scout, and holds an Idaho guide license.
What does a general manager of a rafting company actually do?
At a small operator, all of it. Operations, marketing, sales, hiring, pricing, fleet, compliance, and whatever broke that morning. The job description that matters is narrower: get the operation out of your own head and into a system the whole team can run from, so the business stops depending on one person remembering everything. A business that only works when one person remembers everything is not a business yet, it is a job with employees.