Justin Smith

AI Can Write the Code. You Still Have to Engineer the System.

Before anybody gets splashed going through a wave, a surprising amount of work has to happen.

I’m Justin Smith, General Manager at Adventure Idaho. I’m preparing to speak at the Idaho Outfitters and Guides Association conference about that work: what I built to help run it, what took longer than I expected, and what another operator can use even if their business looks very different from ours.

At peak, our crew of 44 worked across multiple locations in Idaho.

These are the ideas I’m bringing to the talk. The dispatch case study shows the tools. This is about the decisions behind them.

The levels of integrating AI into a business

Before the rafting story, here’s the map I use. There’s a difference between asking AI a question and building it into the way a business runs.

A seven-level chart titled "Levels of integrating AI into your business." From level 1 to level 7: Ask it. Give it context. Connect your tools. Model your operation. Let it act, with approval. Let it run workflows. Let it pursue a goal. The levels are grouped as Use it, Connect it and Delegate work. Closing line: "Anyone can buy the AI. Building it into your business is the work." A helpful framework, not a formal standard.
Levels of integrating AI into your business. A helpful framework, not a formal standard. View full size

At the bottom, I bring the assistant a question. Then I give it useful context: our procedures, policies and examples. That means supplying information, not retraining a model. Connecting it to authorized tools lets it look up information instead of asking me to paste it in.

The fourth level is modeling the operation: linked records, relationships and operating rules an assistant can work from. The next three levels give it different responsibilities:

People still set the goals, permissions, approval points and stop conditions. Logs and oversight matter more as the system takes on more responsibility. These are useful distinctions, not a formal standard or a sequence every business has to follow. A proposed plan is not an executed change or a guarantee of the best possible answer.

This isn’t a requirement to write all your own software. Buying, configuring, integrating and custom-building are all options. I choose based on the job, access to the data, permissions, reliability, cost and who will maintain it. More integration is useful only when it solves a real problem.

My experience at Adventure Idaho has been working through those decisions: what the system needs to know, which rules belong in code, where AI helps, and what still needs a person. The whiteboard story is where that became concrete.

A reservation is the beginning of the plan

A group wants to move its trip to tomorrow. Another group grows enough that the vans no longer work. Now we need a bus, which means checking for an available CDL driver. A multi-day crew gets back that afternoon, but those guides need time to unload, clean and rig before their next assignment. Rentals draw on some of the same equipment.

Each decision changes another decision. A name in a guide field doesn’t tell me whether that guide is available, qualified, rested, already promised somewhere else or able to reach the next assignment on time.

Booking software is crucial. Taking reservations and payments well is a substantial job. Broadly useful software also has to serve many kinds of businesses. Trying to fit a particular operation into its scheduling fields can feel like pushing a round peg into a square hole.

Our software setup also assumed one job per day. On the river, a guide can drive a morning shuttle and then guide an afternoon trip, if they’re qualified and the timing works. One van can drop off a full-day group, pick up a half-day group and bring another group back from the take-out. When I stacked those jobs, the software flagged them: this guide can’t drive, this van is already assigned, this trailer is already in use. I had to check the qualifications and timing, then work through the errors and update the records by hand while the day kept changing.

A one-day timeline titled "One job per day? Not on the river." Guide B is away on a multi-day trip. Guide D drives a morning drop and then guides the 2:00 half day. Guide E guides two half-day waves. Van 2 covers the full day plus half-day pickups. A short trailer has five jobs. Three numbered software errors read: "Guide D is a guide. Can't be assigned as a driver." "Van 2 is already assigned to the full day." "Trailer already assigned today." The reply says they are qualified, the van can cover both and the trailer is back by 1:30. The software assumed one job per day, but guides, vans and trailers worked in waves. An illustrative day showing our software setup, not any specific platform.
The software assumed one job per day. Our guides, vans and trailers worked in waves. An illustrative day. View full size

Our whiteboard worked because it was fast. I could erase something, move a name and see the whole day. The problem was how much knowledge had to stay beside it.

The booking software held the reservations. The whiteboard held the assignments. I held the connections between them.

Diagram titled "Five places. One plan." A change card reads "Guide D can't drive Saturday." Below it are five boxes: Reservations in booking software Availability in texts and a crew app Certifications in a spreadsheet Assignments on the whiteboard Instructions in the dispatch message Three boxes are highlighted as places to find, check and fix. Closing line: "The problem wasn't entering the information. It was keeping every version of the plan true."
The problem wasn't entering the information. It was keeping every version of the plan true. View full size

Then I had to translate the board into dispatch messages: which group, what time, which vehicle, which trailer, where to go next. Updating the plan meant updating the explanation too. A guide looking at the board and a guide reading yesterday’s message could be looking at different plans.

A recreated nightly dispatch message for a Saturday in Riggins, listing trips, guides, bus and van assignments, trailers, put-ins, pickups, rentals, food and photo timing. Below it are three crew replies, each forcing a rework: A guide asks how they are on a multi-day and a day trip at the same time. A driver says the van is still staged at another take-out. A guide says the trailer is needed for her own pickup.
A recreation of the kind of message we sent every night, with placeholder names. Every reply sent me back through the plan. View full size

The part AI could not guess

I was already using AI. But it couldn’t coordinate an operation whose reservations, availability, qualifications, assignments and instructions lived in separate places.

During the summer of 2025, I tried giving ChatGPT a photograph of the whiteboard and asking it to help untangle the schedule. One suggestion was to take guides partway through a Main Salmon trip, have them cover a day trip, then finish their multi-day trip.

It could read names. It didn’t understand what those assignments meant in the real world.

Slide titled "AI couldn't use knowledge we hadn't given it." It shows the request, "help me cover tomorrow's half day" with a whiteboard photo, and the paraphrased suggestion to take two guides off day 3 of a Main Salmon trip, run the half day, then send them back. A five-day timeline marks day 3 as the middle of a wilderness trip. Line: "Apparently we'd added teleportation to the shuttle plan."
Paraphrased from memory, summer 2025. View full size

That experience is still useful to me. A convincing answer can be impossible. The missing work was to make the operation understandable: the people, equipment, trips, locations, timing and rules connecting them. I’ve written more about that first attempt and getting off the whiteboard.

I started building the connected records and tools around those relationships. That became what I call the company brain: our operating records, the relationships between them and the rules for using them.

The booking software still owns the reservation and payment records. The company brain connects a reservation to the people, equipment, timing and rules needed to deliver the trip. Email, calendar and payroll still do their own jobs. Not every tool runs on our database; the useful parts connect to it.

That gave me a foundation I could build different ways of working around: the crew board, a phone view or a spoken request. The operating knowledge doesn’t have to live only in the screen I happen to be using.

A return time and a ready-to-work time aren’t the same fact. A guide may be back at the shop but still need to unload and rig. A vehicle can handle several movements in a day if the times and places line up. I had to represent those relationships, including the exceptions and the time window each rule applies to.

That is where my operating experience mattered. I knew which questions to ask because I had been the person answering them. For each connection, I had to work through:

I also decided where the operating system stops. Payments stay in the booking software. Sensitive payroll details and bank information stay with the payroll company. Deleting records and changing access stay with a person.

A connector can move information. Those decisions determine whether the information is useful and trustworthy in the operation. AI helped write the software around them.

AI can write the code. You still have to engineer the system.

Two columns. "What I did": decided what mattered, chose the stories and the order, knew how our trips actually work, reviewed every draft. "What AI did": built the slides, laid out the diagrams, wrote and revised the code, did the clicking and dragging. Closing line: "AI can do the computer work. You still have to know what you're building and why."
True of the operation, and true of the talk itself. View full size

In 2026, I took down the whiteboard. We didn’t use it all season. The change was possible because the records, rules and connections behind the board were finally in place.

One board is only the visible part

The crew board is the easiest thing to show. Behind it are guide availability and qualifications, assignments, vehicles, trailers, equipment, food planning, issue tracking and reporting.

The board is one window into the company brain. The same records support:

Replacing the whiteboard came fast once the base existed. The base was the hard part. More of what it runs.

I didn’t replace the booking system with a board. I kept the specialist tools and built the operating relationships around them. Once that base was in place, another view or workflow could use the same records rather than start with another disconnected copy of the plan. That’s how I designed ours, not a requirement for every business to build a custom database.

A layered diagram titled "Build the base once. Everything stacks on it." The company brain is the foundation: the data, its structure, what connects to what, and where AI, code and routing fit. It is labeled "Months. The hard part." The crew board replaced the whiteboard: "Not easy, but it came fast." Above it are ten capabilities: changes by voice, conflict checks, booking feed, morning digest, field texts, guest details, balances and payroll, credentials, food that scales and crew phone apps. A spotlight describes photographer reminders with timing adjusted for river level, wind and group size.
Build the base once. Everything stacks on it. View full size

The crew can see assignments and trip details on their phones. The office can check conflicts against connected records rather than reconstruct the whole operation from memory. The same information supports food preparation, maintenance tracking and payroll preparation. Permit and usage reports are another reason to keep the underlying trip records useful.

Adventure Idaho's former whiteboard alongside the connected crew scheduling board
The old whiteboard and the connected crew board show different planning periods. The improvement came from the records, rules and workflows behind the screen.

My estimate is that weekly planning dropped from roughly 20–40 hours to 2–4. That’s an estimate of planning work, not my entire job or an audited productivity study. It gave me more room for guide training, driving, photography and improving other parts of the operation.

The useful result was breathing room to manage the business better.

Voice gets interesting when something is connected

Dictation alone saves typing. A connected assistant can work with the records and tools behind the words, within the access it has been given.

Four ways AI can work with tools: copy and paste, browser use, API and MCP connector. Browser use clicks through a website like a person, is slow, uses a lot of AI and can misclick or misread. It is the last resort when no other door exists. APIs support direct program connections; MCP provides a standard interface for an assistant with configured tool permissions.
Use the most connected door the app offers. Browser use is the slow, last-resort door. View full size

I can describe a change, ask what it affects and review a proposed response. That is a very different workflow from opening several apps, finding the same information in each and typing it again. My spoken production-fix example shows one way I use that speed.

One guide’s message said they’d take another guide’s driving the next day: the full-day drop-off, the pickup and the 3 o’clock half-day pickup. The system matched that message to three driving movements, checked them against the board and staged the change. I reviewed and approved it before the schedule updated in the crew’s apps. The first time I saw it was about two hours later. Before, a message like that could mean 30 minutes to an hour of checking the board, texting people and waiting for replies. The useful part was understanding what “that driving” referred to in our operation. It wasn’t just transcribing a sentence.

A phone screenshot of a dictated request to review guide river miles, training opportunities and vehicle maintenance timing, find recent scheduling messages, and return an overview for a person to verify.
A real dictated request from the operating-system case study. View full size

Buying an AI subscription for everyone doesn’t create this workflow by itself. The useful work is deciding what connects, who can change it, what needs approval and how the team knows a change actually happened.

That’s why the levels at the beginning matter. Connecting an app is one step. Making its information usable in a decision, and giving a person a clear way to check the result, is the integration work.

Speed needs checks

A database can be wrong. A sync can stop. An assistant can misunderstand. A person can miss an assignment that was correctly recorded.

I want the system to make those problems visible. Hard conflicts block an assignment that breaks a rule. Soft conflicts flag something that needs judgment or confirmation. An override needs an explanation. A change log tells us what happened. Important changes need a person to review them, and important assignments need acknowledgment from the person doing the work.

A crew-board screenshot with a red, yellow and green status legend, an AI Plan week button, cleared trip cards, open items and changed headcounts.
The real crew-board interface, with status flags and an AI Plan week control. View full size

The crew board also has an “AI Plan week” control. In the workflow I describe in the talk, it proposes crew for the week’s trips. I review and adjust the draft, and nothing is written until I click Apply. In the version I reviewed, the proposals come from coded rules, not an AI model. It is a reviewed planning step, not a full goal-directed system running on its own or a guarantee of the best possible plan.

Three circles distinguish assigned on the board, acknowledged by the driver, and verified ready by someone who confirmed in time to act. A good system still needs management and leadership.
Assigned, acknowledged and verified ready are separate steps. View full size

A good system still needs management and leadership.

Before giving an assistant another permission, I ask what could happen if it gets the task wrong. Reading a schedule, proposing a change and changing a customer’s booking are different levels of responsibility. External booking records remain read-only in the operating system described here; that is different from letting an agent change reservations or payments.

An illustrative blast-radius diagram titled "If it goes wrong, how much can it affect?" Concentric rings expand from Draft to Booking, Payment and Bulk update. Examples compare a proposed change, a trip move that affects customers, payments kept in booking software and bulk updates kept off limits to the assistant. Side panels distinguish reading from writing, human approval and overrides from non-negotiable qualifications and capacity limits. A change log records what changed and what it was before. Closing line: "Read. Propose. Commit. Three different permissions." This illustrates permission design, not the capabilities granted to this system.
The larger the potential impact, the tighter the permissions and review. An illustrative comparison, not permissions granted to this system. View full size

The benefit of tracking an issue is also practical. Someone reports it, someone owns the next step, and someone verifies the work is complete. A longer task list on its own doesn’t make an operation safer.

Some things should stay simple

I could try to model propane use from trip length, group size, stove type and weather. I could build a dashboard to track every paddle.

An overbuilt code snippet that calculates propane from trip days, group size, stove efficiency, wind, cold mornings, coffee drinkers, hot chocolate and Dutch-oven nights, crossed out with a red X. It resolves to "a notification when it's running low." Beside it: a pre-trip check, a simple reserve and reorder rule, and a named owner.
Just because we can model it doesn't mean we should. A teaching sketch, not a safety SOP. View full size

But the model is only useful if the inputs stay reliable and the result changes a decision. A straightforward equipment check, spare supply and clear restocking responsibility may solve the propane problem better. A paddle count that nobody can maintain is another thing to fix.

Build the system people can keep accurate.

The same judgment applies to AI itself. Building the tool and running it are different jobs:

I don’t need a fresh model call to do arithmetic every time the headcount changes. A model call is a request to an AI model for a response; it isn’t every piece of software running behind the board.

The graphic below compares ten selected jobs from our system. As far as I’ve confirmed, nine run as code; voice changes use a model call. That is a count of examples, not a percentage of the system’s AI use. Other activities, including questions across Google and Slack, also use models. The curves illustrate a design choice, not measured requests, cost or environmental savings.

A slide titled "How much AI does this use?" distinguishes code that follows written rules from a model call that asks an AI model to interpret or propose. Ten selected jobs are listed. Conflict checks, Plan the Week proposals, booking feed sync, field texts to every manager, credential tracking, guest details, food scaling, balance and payroll checks, and photographer timing are labeled Code. Changes by voice is labeled Model call. Two curves contrast building with AI then running known rules as code with repeatedly asking AI to sort out each problem. The chart is labeled "Illustrative pattern, not measured usage." The footer says this is a count of jobs, not measured usage.
Ten selected jobs, not a complete inventory or a percentage of AI use. Other activities also use models. The curves are illustrative, not measured usage or savings. View full size

That is the distinction behind using AI to build the system. It still takes maintenance, hosting, testing and attention. It also has environmental costs. I don’t have a defensible water-use figure for this project, and I won’t turn it into a shower comparison. I want useful tools that reduce repeated work, not more processing for its own sake.

Adoption is another engineering decision. If checking the board on a phone is harder than asking someone, people will keep asking. I want the useful information close to the work, and a clear person responsible when something is missing or wrong. A system people don’t keep current won’t stay useful, however much code we can generate.

When evaluating software, I also want to know whether I can access the underlying records, receive change notifications and use supported write actions where appropriate. My Exhibit Hall Test is a starting point for those conversations. Access still needs permissions, checks and someone responsible for maintaining it. These questions help me keep options open and connect useful tools around the booking system we already value. They aren’t an argument for replacing it.

What I think comes next

I expect more business work to start with a conversation instead of a sequence of clicks. That’s a prediction, not a timetable. It won’t remove the need for good records or for people who understand the operation. In my experience it makes that knowledge more valuable.

Three-stage timeline labeled as opinion. Today: connected operations, where agents propose and people approve. Next: agent-ready software with APIs, webhooks and MCP connectors. Coming: customers send their own AI to find and book trips. Closing line: "When a customer's AI checks your availability, it should find the truth."
My opinion, not a forecast. View full size

For a high-trust business, I still want a capable person talking with customers. I’m more interested in taking repetitive coordination off that person’s plate than putting a robot between them and a guest.

I love Idaho’s rivers and the people who work on them. Better preparation, fewer avoidable trips back for something forgotten, clearer responsibilities and more time for training are worth working toward. That’s why I want to share what I’ve learned with other outfitters.

If you’re coming to IOGA, I’d enjoy comparing notes. Bring a process that keeps pulling you away from the work you actually want to do. We may not need to build very much to make it better. Get in touch.

← All writing