The Unscrupulousness Protocol: Nothing to See Here

Fort Lauderdale International Boat Show, Day One: Questionable engineering, unreasonable leverage, expensive boats, and the occupational hazards of being helpful.

I think I may have a problem.

Actually, several.

The first is that I can't go anywhere without turning an ordinary conversation into a technology project. The second is that I can't recognize when I've already accomplished enough for one day. And the third, which became especially relevant on Day One, is that I have no idea how to balance caffeine and bourbon when both are apparently essential components of my professional development strategy.

Welcome to the 2026 Fort Lauderdale International Boat Show.

Or, as I've decided to call it, The Unscrupulousness Protocol.

Nothing to see here.

The Official Assignment

I arrived with an actual job to do. A legitimate technology assignment involving custom-built hardware, software, and some real-world experimentation in the marine industry. Some of this technology was developed through a "highly sophisticated" engineering process involving a soldering iron, a 3D printer, artificial intelligence, caffeine, and an unreasonable belief that I can probably figure things out.

Not the sort of development methodology typically featured in corporate annual reports.

But the difference between an experimental piece of technology and a commercially useful product is often just whether someone is willing to put it in the real world and see what happens.

So that's what we did.

Without getting into the details, because I'm not interested in giving away the recipe yet, something interesting happened. It worked.

Not just technically. It produced an actual business opportunity that moved beyond an initial interaction into a real sales conversation. That's an important distinction. Engineers love proving that things work. Entrepreneurs love proving that things matter. When both happen at once, things get interesting.

Watching something you built with a few inexpensive components potentially influence a transaction involving a multimillion-dollar asset is a uniquely entertaining experience. No sale has been made, and there's plenty left to validate. But the first meaningful waypoint has been reached.

I may have celebrated internally. Violently. All anatomical systems remain in their factory-default configuration. For now.

Unreasonable Leverage

There's a phrase I keep coming back to: unreasonable leverage.

We usually think about business investment in linear terms. Spend more, hire more, buy more equipment, build more infrastructure, hopefully generate more revenue.

Technology has a funny way of making that relationship absurd. A relatively small investment of time, creativity, and resources can produce an outcome wildly disproportionate to the effort, especially when you combine inexpensive computing hardware, AI-assisted development, automation, and a willingness to experiment.

The technology itself isn't necessarily remarkable. The leverage comes from recognizing where to apply it.

We're entering an era where individuals and small teams can build capabilities that used to require entire departments. That doesn't guarantee commercial success. It changes what's possible. And frankly, that's ridiculously exciting.

Three Meetings That Didn't Exist When I Arrived

Here's where my inability to behave like a normal person becomes a problem.

I had a perfectly reasonable plan. Show up. Complete the technical assignment. Meet a few people. Enjoy the Boat Show. Except I'm surrounded by entrepreneurs, yacht brokers, business owners, engineers, and people who've spent years dealing with problems that might benefit from emerging technology.

So conversations happen. I ask questions. People explain how their businesses work. And somewhere along the way, someone says something that makes me think, "Wait a minute. We can probably do something about that."

By late afternoon, I'd scheduled three additional meetings for Saturday, October 31, involving artificial intelligence, superintelligence, and potential business applications.

Three. None of them existed when I arrived.

This is why I shouldn't be allowed to socialize professionally without adult supervision. I came here with a job. Now I have more jobs. I'm beginning to suspect this is how work reproduces.

And Then I Accidentally Built Another Application

For months I've been exploring opportunities in the marine technology space, where artificial intelligence, information management, professional networking, and business processes intersect. I've already been developing YachtRecon and Mooring Club, both addressing different aspects of the industry's increasingly connected ecosystem.

Then a conversation introduced another problem. The kind where an entire industry still relies on disconnected services, directories, spreadsheets, phone calls, and personal relationships to accomplish something technology should simplify.

Someone described what they needed. I started thinking. And because the distance between an idea and functional software has become astonishingly small, I did what any reasonable person would do.

I started building.

Between conversations. At the Boat Show. Sitting in a waterfront hospitality area surrounded by expensive yachts. By the afternoon, I had an initial working version of another application, along with a project overview covering the concept, workflows, intended users, and potential business model.

The new project, currently called YachtWorks, explores how yacht owners, captains, marine service professionals, and management companies might connect through a more intelligent service marketplace. Service discovery, maintenance requests, competitive quotes, provider coordination, documented service histories.

It's early. The MVP needs end-to-end validation, and plenty of operational and commercial questions remain. But the larger question is getting interesting: what happens when marine-industry relationships, technical intelligence, and service operations work together instead of sitting in disconnected silos?

I'm not announcing a product. I'm documenting the moment another idea crossed the blurry boundary between conversation and software.

A few years ago, this might have required weeks of planning before development even began. Apparently now you can make meaningful progress between cocktails.

The Four Roses Problem

I should address the beverage situation.

Caffeine says, "Let's solve problems." Bourbon says, "Let's discuss opportunities." My brain interprets both as authorization to start another project.

Four Roses entered the equation. There were also, I'm reasonably certain, delicious mezzes. I say reasonably certain because somewhere between conversations, engineering, networking, and software development, lunch became less of a scheduled activity and more of a supporting character.

I'm not proposing bourbon as a formal software development methodology. My attorney, if I had consulted one, would appreciate that clarification.

Still, the day's results raise some deeply troubling questions about the relationship between waterfront hospitality and entrepreneurial productivity. I'm going to need more data. Under properly controlled conditions. With snacks.

The Difference Between Networking and Actually Connecting

I've always found it strange how much effort people put into collecting contacts. Business cards. LinkedIn connections. Follow-up emails.

Nothing wrong with any of it. I've just never been particularly interested in collecting people. I'm interested in connecting ideas. Someone has a problem. Someone has expertise. Someone knows someone else. Someone has technology that solves something nobody thought to apply it to. Occasionally you end up standing at one of those intersections.

The best conversations weren't pitches. They were ordinary conversations with people who knew their businesses and were willing to say what they needed.

AI doesn't eliminate the need to understand an industry. It makes that understanding more valuable. The code is getting cheaper. Context, judgment, relationships, and trust are not.

In an industry like yachting, where relationships still drive so much of the business, that's an interesting opportunity.

The Unscrupulousness Protocol

So why the title? Because I have a suspicious habit of helping people, building things, and discovering opportunities in situations where I was supposedly doing something else.

A favor becomes a friendship. A conversation becomes a collaboration. A small experiment becomes commercially interesting. And sometimes you look up from your drink and realize you've added three meetings and built the foundation of another software application.

None of this was part of an elaborate master plan. Not entirely.

There's something deeply satisfying about recognizing an opportunity and acting on it immediately. Not six months from now. Not after a dozen planning meetings. Not after someone approves a development budget.

Now.

Most ideas still need testing, refinement, market validation, and the occasional confrontation with reality. But being able to explore them quickly is itself an extraordinary advantage, especially when you're surrounded by people who understand the industry you're trying to serve.

Day One, Mission Accomplished. Sort Of.

Several hours at Pier 66. Technology now being tested in a live commercial environment, with an encouraging early result. Fascinating conversations. Three meetings on Saturday's calendar. An initial version of another marine application. And a reasonably thorough, if scientifically questionable, evaluation of waterfront hospitality.

I'm going to call it a day.

Which is a strange thing to say, considering I somehow ended up with more to do on Saturday than I had when I arrived. I came with one official assignment and a few ideas. I'm leaving Day One with progress on the assignment, a new software concept, several promising conversations, and three additional meetings.

No grand announcement. No victory lap. No claim that any of this becomes the next big thing. Just a reminder that a single person with curiosity, technical experience, access to AI, and the willingness to get their hands dirty can accomplish some genuinely surprising things.

Unreasonable leverage isn't about having unlimited resources. It's about recognizing that the right application of surprisingly modest resources can create disproportionately interesting opportunities.

Sometimes those opportunities begin in a laboratory. Sometimes in a boardroom. And sometimes at a waterfront bar during the Fort Lauderdale International Boat Show.

Saturday, apparently, we do it again.

The crosses I bear.

The Unscrupulousness Protocol: Nothing to See Here.

P.S. If any of these experiments eventually turn into something spectacular, I'd like to remind everyone that I documented the suspicious circumstances in advance.

P.P.S. Four Roses has not sponsored this article, although I'm willing to entertain discussions regarding a strategic research partnership.

---

Rich Washburn is a technologist, strategist, and Founder & Chief AI Architect of ARIA AI Labs, working at the intersection of AI, infrastructure, communications, and capital. He also serves as Managing Partner and Chief AI Officer at Eliakim Capital.