The Execution Marketplace: A Three-Sided Order Book for Small Business

It started, like most of our good ideas, in a Slack thread at lunch.

Daksh confirmed we still had the Stripe integration wired up — an ecommerce template where you swap in your own keys and it just works, with an API that sends every order upstream into our CMS admin panel so the shop can either pipe it to a shipping service or just see who bought what. So I did the thing I always do. I went looking for someone to sell it to.

I found Rune and Board — a family-friendly game shop out in Hillsboro. The name is a play on "Room and Board," which I love. The site is rough. But it's already doing a ton under the hood — real inventory, real commerce, the works; it just looks like it was assembled between shifts. I looked at it and thought, I can make these people something badass.

That's the entire FootTraffic instinct in one browser tab. Project FootTraffic is the bigger swing — treat overlooked local plazas like real estate, raise the value of the place, and fund a compounding platform one small business at a time. Chris asked the right question in the thread: these shops reach for free stuff like WordPress, so will they actually pay us? Yes. They pull roughly five grand a day through the register. They have the money. What they don't have is a dev.

Which is exactly the opening. But this post isn't the pitch for FootTraffic — that one's already written. This is the pitch for the thing that sits on top of it, and I want the eng team to build it.

The Thread Was the Whole Strategy

Re-read what the team said in twenty minutes. Daksh: one person can maintain five or six websites — point an MCP at the CMS and mass-create the blocks. Chris: small businesses don't have devs, so the subscription has to include a dev who builds the template and the first wave of content; after that, updates are a piece of cake. And Chris reached for a word he and edibles had already been kicking around — skills. Named, reusable procedures that make the AI faster and less likely to misshape a build.

Nobody in that thread was describing a website. They were describing an assembly line. And an assembly line with idle capacity is just a market nobody has opened yet.

A Standing Inventory of Demand

Here's the part most agencies never get to stand on.

Once we own a portfolio of these businesses across Portland, LA, Austin, Detroit — dozens today, hundreds as we grow — every one of them is a faucet of recurring work. A booking flow that needs wiring. A menu redesign. "Can someone fix our Google listing this week." A new-release Friday that really should have been a pre-order drop.

Each of those is a unit of work attached to a real business that already trusts us and already pays. That's not a backlog. That's demand we already own — and demand you already own is the single hardest thing for any marketplace to manufacture.

It's a marketplace waiting to clear.

Three Sides, One Board

The model I keep drawing on the whiteboard looks like rentahuman.ai — but pointed inward, at our own real estate. Three sides.

Side one — the businesses. We build the most ergonomic tooling we possibly can so an owner can self-serve the easy stuff: the booking widget, the loyalty loop, the post-visit text, the discount code and gift card Daksh would otherwise have to go figure out by hand. Push-button. No human required.

Side two — the open network. When an owner hits something they don't want to touch, they don't file a ticket and wait on an account manager. They vibe-submit it in plain English, it drops onto a board, and it's first come, first serve. Any operator — or AI-assisted human — in the network can claim it and ship it.

Side three — us, the house. This is the part that makes it ours and not just another freelancer site. We're not neutral plumbing sitting between a buyer and a freelancer. We're a participant on our own board. We claim the brand-defining, high-margin work ourselves, we set the quality floor the whole network has to clear, and we capture every reusable module that falls out of a job — which feeds straight back into the FootTraffic platform layer.

What the Owner Touches

For the owner, none of that machinery should show. They get a console. The easy things are buttons. The hard things are a text box.

That text box is the whole UX bet. The owner shouldn't have to know whether "pre-order Friday" is a tool toggle, a template tweak, or a two-day build. They describe the outcome they want; the system figures out who clears it.

The Board

Behind the text box is the board. This is where supply meets demand.

First come, first serve, with a lock so two operators never grab the same job. A business chip so whoever claims it has the context. A tag for the kind of work. An SLA so "this week" actually means something. And the house, sitting quietly in the same feed, claiming the jobs worth doing ourselves.

Routing Is the Whole Game

Everything I just showed you is window dressing on one hard problem: when a request comes in, where does it go? That decision — tool, open network, or house — is the core IP. Get it right and one person really can run a territory of a hundred businesses. Get it wrong and we're a worse agency with extra steps.

The classifier asks three things in order. Can a tool already do this? Is it commodity work the network should clear? Or is it brand-defining enough that the house should take it and turn it into a module the next hundred shops inherit? That router is the thing I most want us to get obsessive about.

Why We're the House — and Why It Compounds

Trading on our own board is what turns regional ownership into a liquidity engine.

Every job the house claims should leave the company more capable than it was before. The discount-code flow Daksh has to figure out once becomes a button every shop gets forever. The MCP-driven block creation and the skills Chris and edibles keep pushing for aren't side quests — they are the supply side's productivity, and ours. The better they get, the cheaper execution gets; the cheaper execution gets, the more businesses we can hold; the more businesses we hold, the deeper the board.

This is the Uber model fused to the agency model — which, after twenty years, is honestly all I've ever worked inside, so it's all I know how to build. I can't help myself but try to mimic it. The one difference that matters: we're not starting cold. We don't have to beg for either side. The real estate hands us the demand on day one, and we've already proven one person plus AI can stand up a real store on the supply side.

What I Want Us to Build

So, team — here's the brick I'm asking us to lay next. Roughly in order:

• Intake parser — vibe-submit text into a structured, routable job. This is where the magic has to feel like magic.
• The board — post, claim, lock, SLA, status. Boring, load-bearing, has to be bulletproof.
• The router — the classifier that sends a job to a tool, the network, or the house. The IP.
• Self-serve tiles — booking, loyalty, post-visit, discounts and gift cards. Chris, Daksh — this is the assembly line you two already sketched.
• Module capture — every house job ends by promoting its reusable part up into the platform.
• Billing — subscriptions on top of the Stripe wiring we already have. We don't beat Shopify's margin, and we're not trying to.

We have the CMS. We have Stripe. We have a game shop in Hillsboro that deserves better than what it's running. That's enough to lay the first brick.