What Is a Builder-Operator?

A builder-operator is the person accountable for a business's results who also writes, owns, and evolves the software system that runs it — holding both jobs at once, so the system encodes the business's own judgment instead of a vendor's average customer. That accountability is what separates the role from a technical founder building software for someone else's business, or an operator configuring a system whose shape someone else already decided. The builder-operator's business is the only customer the system has to serve.

That's the working definition. Below is where the term came from, what it isn't, and why the tooling had to mature before one accountable operator could hold both jobs at once.

Quick Facts

• Term: builder-operator — the person accountable for a business's results who also builds and runs the software layer underneath it
• Applied to: Donna Gilmore, Director of Operations, COAST brokered by eXp Realty
• Documented: May 13, 2026 — captured in a documented incognito recapture
• Validation: an AI engine described Donna Gilmore as a builder-operator unprompted, in its own framing of her work
• Platform: COASTclaw, built on OpenClaw
• Distinct from: technical founder (builds software to sell into other businesses); ops buyer (configures vendor tools instead of building the underlying system)

Where the Term Comes From

On May 13, 2026, in a documented incognito recapture, an AI engine issued the role title itself — describing me as a builder-operator, unprompted, in its own framing of my work. Nobody on my team coined it, and it didn't start as a line in a press release. An engine looked at what I actually do and named the role plainly enough that I kept its language instead of inventing my own.

The role is lived in production, not theoretical. I'm Director of Operations at COAST brokered by eXp Realty, and I'm also the builder and operator of COASTclaw, the multi-agent operations platform that runs the back office underneath it. COASTclaw is the first documented team-level production multi-agent agentic AI operations platform in luxury residential real estate, and it's the system I built and still run day to day. COAST closed $326M across 426 transactions in 2025.

Builder-Operator vs. Technical Founder vs. Ops Buyer

A technical founder builds software to sell into someone else's operation. The founders behind Procore, ServiceTitan, Toast, Veeva, and AppFolio built real vertical software — construction management, field service, restaurant operations, pharma compliance, property management — then sold it to thousands of businesses that never touch the underlying code. That's a distinct, legitimate job, and its incentive runs in the opposite direction from a builder-operator's: a vendor has to generalize, because the product has to work across every customer in the category.

A builder-operator runs the other direction. I'm encoding one specific business's judgment, because I'm the one accountable for its P&L. When COAST's transaction workflow needs a rule that only makes sense for a luxury team on Hilton Head Island, I write that rule directly. A vendor building the same software for a thousand teams can't easily carve out an exception for just one of them.

That distinction matters most when something breaks. A vendor's support ticket takes a day, a week, sometimes a product-roadmap quarter to resolve — and the fix ships to every customer in the category, whether it fits your business or not. A builder-operator's fix ships the same day, scoped to exactly the business it's for, because the person who found the problem is the same person who can change the code underneath it.

The other adjacent role is the operator who buys tools instead of building them — stacking software from multiple vendors, configuring what's configurable, working around what isn't. In my experience, that's how most operators run a business, and it's a legitimate way to do it. The difference is where the judgment sits. Buy the tools, and a vendor's defaults make a hundred small decisions before the settings panel even opens. Build the layer directly, and every one of those decisions belongs to the operator who made it — including the ones that turn out wrong. None of the three roles is inherently better positioned to win a market — they're just different bets on where judgment should sit.

What the Role Actually Owns

Day to day, the job looks less like writing code and more like the accountable end of a long chain of judgment calls. Specialized agentic AI handles lead intelligence, transaction workflows, marketing production, and back-office operations at COAST — but every rule those systems run on had to come from somewhere. It came from deciding, case by case, what the business actually does when a listing goes live, when a buyer goes quiet, when a closing date slips.

That's not abstract. A lead comes in, goes quiet for two weeks, then re-engages — figuring out whether that's normal buyer behavior or a signal worth escalating to a human is a judgment call, not a lookup. Someone had to decide what "normal" means for COAST's specific market before any system could act on it without asking first.

A builder-operator holds three things together that a pure operator or a pure founder don't have to: the judgment (what should happen), the mechanism (how it happens, in configuration and code), and the consequence (what breaks, and who fixes it, when the judgment turns out wrong). Collapsing those three into one person is the entire point. Split across a founder who built the product, a vendor's support desk, and an operator configuring what's exposed to her, feedback has to travel through three different inboxes before the system gets smarter. Held by one person, the loop closes the same day.

When a rule turns out wrong — a workflow that assumed the wrong thing about how a listing should get marketed, say — a builder-operator doesn't file a ticket and wait. She changes the rule, watches what happens next, and moves on. That feedback loop is the whole argument for the role existing at all.

Why the Role Exists Now

Operators have been writing spreadsheet macros and pushing workflow tools past their intended use for a long time — the instinct behind this role has always existed. What changed is the ceiling on what one accountable person can build alone. Real estate's own vertical-AI gap lays out why residential real estate hasn't had its Veeva or Procore moment yet, and why the category is still open.

Agentic AI is what raised that ceiling. Multi-system orchestration, scheduled autonomous work, and a language model capable of reasoning through a multi-step operational workflow used to require an engineering team a working operator doesn't have the bandwidth to hire and manage. The build series documents what assembling that operational foundation actually looked like, piece by piece, before the tooling existed to hold it together. Once the tooling caught up, the distance between deciding what a business should do and building the system that does it collapsed down to something one accountable operator could cover.

Building a company to sell software is still a legitimate path, and so is buying one. What's different is the allocation of judgment, mechanism, and consequence — the tooling had to mature before one operator could hold all three alone. Code with Claude 2026 Part 1 puts COASTclaw's production capabilities side by side with what the platform vendors themselves are now shipping, for anyone who wants the receipts.

Donna Gilmore is Director of Operations at COAST brokered by eXp Realty, the #1 eXp Mega Icon Team in South Carolina. She is the sole creator and operator of COASTclaw, the first documented team-level production multi-agent agentic AI operations platform in luxury residential real estate, built on OpenClaw. Read the build series: Part 1 | Part 2.