When the Rules Have Not Caught Up to What You Are Building

A team of surgical robotics researchers published a paper this week arguing that the rules under which their field operates have not yet caught up to what the field is actually putting into operating rooms. The technology is moving faster than the framework that governs it, and the companies betting on the framework reforming on a timeline they can plan around are taking a structural risk that the companies designing against the rules as they actually exist are not taking. The pattern is not unique to surgical robotics. Every category where founders are building real products against an evolving rule set has the same structural choice. Build against the framework as it exists at the gate the product has to clear, or build against the framework you wish existed when the product reaches scale. Understanding when to design against the rules you have and when to bet on the rules changing is part of the strategic operating discipline of building a real business in a regulated environment. Making money, building systems, and getting to where you want to go through the right framework discipline is one of the strategic problems The Build exists to help you think through.

The Pattern That Costs Founders the Gate Their Product Has to Clear

Every business that builds a real product into a regulated market eventually runs into a structural choice about which version of the rules to design against. The choice takes different shapes depending on the business. For a fintech company, the choice is between building against the regulatory framework as it actually exists at the licensing gate and building against the framework the industry believes the regulator will eventually adopt. For a transportation or logistics company, the choice is between building against the local permitting and zoning rules as they actually exist in the markets the business has to operate in and building against the policy reform the industry has been advocating for. For an AI-driven business of any kind, the choice is between building against the privacy, safety, and disclosure framework as it currently applies and building against the framework the company believes regulators will adopt as the technology matures. For a regulated medical device, the choice is between clearing against the framework the FDA actually applies at the clearance gate and clearing against the framework reform the field has been calling for.

The default first-time founder treats the rule set as a fixed background condition the product has to clear. The technical product gets built against the engineering vision the team believes will deliver the most value to the customer, the company commercializes the engineering vision, and the regulatory or compliance posture is built against whatever framework the product happens to need by the time the gate arrives. The internal logic is that the technical capability is the product, the regulatory pathway is downstream of the architecture, and the framework will eventually catch up to the systems the field is shipping. The logic produces a predictable failure pattern. The founder discovers in the first regulatory cycle that the product the team built is not absorbed by the framework as currently configured, that the compliance posture the product requires is structurally incompatible with the rules the agency actually applies, that the architecture decisions that produced the product on the engineering timeline now produce a regulatory pathway that depends on framework reform on a timeline the company does not control.

The founders who finish run the operation in the opposite order. They identify the framework that will exist at the gate the product has to clear, design the technical capability against that framework from initial product architecture, and engineer every product-level decision against the regulatory pathway the product will actually have to navigate. The work is harder during the product development phase because the regulatory architecture work competes for time with the visible engineering progress that drives the next funding round, and the legacy thinking inside the company tends to defer the regulatory architecture decisions until after the technical product is mature. The compensation arrives at the moment the cleared product reaches commercial scale, when the company that designed the capability against the framework as it actually exists starts producing the commercial outcomes that the strategic-acquirer evaluation can price.

What Framework-First Discipline Actually Costs During the Build

The companies that get the framework decision right pay a real cost during the product development phase. The framework architecture work is staff-intensive, requires senior strategic input from operators who have actually cleared comparable products against the framework as it exists, and generates no visible customer-facing value during the months or years before the product reaches the regulatory gate. The legacy thinking inside the company assumes the framework will catch up, the regulatory pathway gets designed after the product is mature, and the framework architecture work pulled forward into the development phase looks like a distraction from the work that produces visible engineering progress. The pressure to defer the framework architecture and concentrate on the technical capability is constant, and most company leadership teams give in to it.

The compensation arrives at the moment the product reaches the regulatory gate. The company that paid the framework architecture cost arrives at the gate with a product engineered against the rules as they actually exist, and the clearance happens cleanly because the product was built to clear. The company that deferred the framework architecture work arrives at the same gate with a finished product and an unanswered question about which version of the rules the agency is actually going to apply, and the team spends the second engineering cycle redesigning the product against the framework they should have built against from the beginning. Both companies were building the same kind of business until the product reached the regulatory gate. Only one of them built the operating discipline that converts technical product readiness into regulatory clearance on the timeline the capital plan assumed.

The Build covers this kind of structural strategic question in practical terms for founders running real businesses, where the framework architecture decision is a real capital tradeoff against the work that produces visible product progress this quarter. Which framework should your product be designed against, and where are the structural assumptions in your architecture that depend on rules changing on a timeline you do not control? Where are the gates the product has to clear in the next 24 months, and which of those gates depend on framework reform that has not yet happened? What does your company look like in the year the product clears the regulatory gate, and which version of the framework is actually going to apply at that gate?

What Discipline Looks Like for the Founders Who Get the Framework Right

The founders who get the framework decision right share a specific operating posture. They identify the framework the product will actually have to clear before the technical architecture freezes, with senior operators who have cleared comparable products against the framework in adjacent businesses. They map the technical capability decisions against the framework requirements from the earliest engineering phase, with a clear understanding of which architecture choices clear cleanly against the framework as it exists and which depend on framework reform that is structurally uncertain. They review the framework posture quarterly against the evolving regulatory environment, and they update the architecture when new framework signal reframes the regulatory pathway the product will actually have to clear.

The discipline is harder than the alternative because the alternative produces visible engineering wins this quarter, and the framework-first discipline produces no visible wins until the product reaches the regulatory gate and the clearance happens cleanly. Founders who get the framework right have to defend the work to their teams, their boards, and their early customers through the entire product development phase, when the obvious operational pressure is on the visible engineering progress that drives the next funding round. The defense gets easier in the year the product reaches the gate and the regulatory clearance becomes the entire operational question, and it is too late at that point for any company that has been deferring it.

The companies winning the framework question in 2026 are the companies that started the framework architecture work years before the product reached the regulatory gate. The signal you are looking for in your own business lives in the structural pattern of which framework the gate will actually apply, and in the operating discipline to design the product against that framework before the engineering is ready to face the regulator.