How the Missouri River Valley LOOP Outgrew a Spreadsheet I Built

Picture what it takes to run a tourism campaign across eight river towns and 49 local businesses. The directory lives in a spreadsheet, or three. Updates come in by email and phone and get retyped by hand. The public site is maintained separately, so it drifts from the spreadsheet, and sooner or later a visitor sees the version that's wrong. The only person who knows where everything actually lives is whoever set it up.

It works, right up until it doesn't.

I know this state well, and not from a discovery call. The Missouri River Valley LOOP ran a version of it for years. I should know. I built it.

How the LOOP ended up with my duct tape

The LOOP is run by my aunt. Years ago, her WordPress developer walked away mid-relationship and left her with a build she couldn't maintain and couldn't get help with. Her plan B was Squarespace, and I couldn't in good conscience let that happen. Not because Squarespace is evil, but because I'd watched what depending on the wrong setup had already cost her, and renting a template wasn't going to make her more capable. It was going to make her dependent on a different landlord.

So I built her something clever instead: a fast static site, published for free, fed by a Google Spreadsheet. She edited the sheet, an automation rebuilt the site, and the public pages updated. No hosting bill, no developer gatekeeping every edit, and honestly, for what it was, it worked for years.

I'm telling you about the old build because I want you to trust me when I criticize it. The data still lived in a spreadsheet, with all the fragility that implies. Editing meant knowing the sheet's unwritten rules. And anything beyond the spreadsheet's reach, structure, new features, anything real, still needed me. It was better duct tape than most, but it was duct tape, and I'm the one who taped it.

That experience, watching a small organization get abandoned by one developer and then bump against the ceiling of my own clever workaround, is a lot of why Wild Kahuna exists.

What replaced it: one system, one source of truth

Today the LOOP runs on a single platform. The public site, the town pages, the business directory, the events, and the map are all generated from the same data, managed in one admin. There's no spreadsheet to keep in step, because the site is the data. Change it once, in one place, and the public face updates from it.

Just as important: the admin is built for a non-technical owner to run. My aunt manages listings, events, and content directly, and each of the 49 businesses can get its own scoped login to update its own hours, links, and events. That's the change that ended the seasonal phone tag: nobody chases 49 owners for fresh information anymore, because the owners keep their own information fresh. My job is keeping the system healthy, not being the bottleneck every time a business changes its hours. She already lived through one developer who made himself the bottleneck and then vanished. The whole design answers that.

So the pile of spreadsheets, retyping, and phone tag collapses into: one place the data lives, one place it's edited, and a public site that can't fall out of sync because it's drawn from the same source.

Why this was the right founding project

Every business is built on a first real project, and this was mine. I point to it first for a specific reason: line item by line item, the LOOP exercises the entire Operations Platform tier, the most capable thing Wild Kahuna builds. Not a slice of it. The whole thing:

• Structured, multi-user access for an organization, not a single owner.
• A directory of businesses as first-class records, the same shape as a member or customer directory.
• Marketing, campaigns, and an engagement layer (the LOOP's passport and scavenger hunt) running on the same data.
• Automation and data-import workflows behind the scenes so the busywork doesn't land on a person.
• A public experience generated from all of it, kept in sync by design.

When I tell a chamber or an association the platform can carry their whole operation, it isn't theoretical. It's running a real regional campaign right now, operated by a real non-technical owner, and I had to earn every design decision against an operator who will absolutely tell me when something is too complicated. Family is useful that way.

The honest part about results

I'm not going to hand you a chart of visitor numbers. The analytics history isn't long enough to mean anything yet, and I'd rather tell you that than dress up a number.

What I can point to is the operational result, which is the one that mattered from day one: one admin instead of a spreadsheet pipeline, one source of truth instead of data that argues with the website, and an owner who runs the whole thing without calling a developer to change a phone number. The traffic story will be worth telling later. The "the spreadsheet is gone and nobody misses it" story is true now, and you can go click around it today.

What this means if you run something similar

If you're a chamber, a tourism group, an association, or any network coordinating a lot of businesses or members, and you're holding it together with forms and spreadsheets, the LOOP is what the other side looks like. One system that owns the data and generates the public site from it, run by your own people, built to grow as you add towns, members, or programs.

And if a developer has ever left you holding a build you can't maintain, I take that history seriously, because my first client lived it. Shared platforms like this are scoped differently from a single-owner build, because the value is spread across many participants. They're usually structured around sponsor support, chamber or grant funding, or member participation, not one custom-build invoice. And like everything I build, the data and the site are yours to take with you if you ever leave. Nobody should need a nephew in the software business to get treated that way.

FAQ

Can one system really replace Google Forms and spreadsheets? Yes. The LOOP's old setup was literally a spreadsheet publishing to a website, and it was one of the better versions of that pattern. It still hit a ceiling. A single platform keeps the directory, events, sign-ups, and public site drawn from one source, so nothing drifts and nothing needs retyping.

Who updates it day to day? The owner, not the developer. The LOOP's admin is run by a non-technical operator who manages listings, events, and content directly. The developer keeps the system healthy in the background; they don't gatekeep every edit.

Is this only for tourism? No. The same shape fits chambers of commerce, associations, member networks, and any organization coordinating many businesses or participants. Tourism is just where this build lives.

How is a community or tourism platform priced? Differently from a single-business site, because the value is spread across many participants. These are usually structured around sponsor, grant, chamber, or member funding rather than one owner's invoice. We map the model before pricing it. The pricing page has the starting point.

What happens to the data if the organization moves on? It's theirs. The data exports and the site comes with them. That's covered plainly in the exit policy, the same as for every Wild Kahuna client.

The short version

The LOOP went from an abandoned WordPress build, to a clever spreadsheet-powered workaround I built myself, to one system with one source of truth that its owner runs without me in the loop. Each step was better than the last, and I'm only proud of the current one.

You can see it live. And if you're coordinating a community, a chamber, or a member network and you're tired of the forms, get in touch and we'll figure out what one system would replace for you.