Johnson & Johnson cleared a surgical instrument in Europe this week that was designed to run on a robot Europe has not yet cleared. The strategic logic is one of the cleanest examples in recent medtech of a much more general business idea: the work that determines whether a launch lands is mostly the work you finish before the launch is the visible event. Understanding that pattern in surgical robotics is part of the job. Making money, building the systems, and getting to where you want to go in your own business when the visible milestones are not the ones that matter, those are the problems The Build exists to help you think through.
The Quiet Work That Determines Whether a Launch Lands
Most founders, asked what their next milestone is, will name a visible event. Product launch. Funding close. Major client signing. The visible event becomes the planning anchor, and the team works backwards from it. This is intuitive and useful right up until the moment you notice that the businesses that win are usually built on the unglamorous work that happens before the visible event, not the event itself.
J&J’s clearance this week is a clean example. The visible event for J&J’s surgical robotics business is the eventual launch of the Ottava robot in Europe. Most companies in that position would treat the years before launch as platform development, with everything else, instruments, training, hospital relationships, evidence base, deferred until the platform clears. J&J ran a different play. The instrument that sits on the future robot is shipping today, on procedures the robot does not yet support, in hospitals the robot has not yet entered. By the time the robot arrives, the instrument is not new. The hospital is not new. The surgeon is not new. The procurement contract is not new. The visible event is therefore much smaller than it appears, because most of the work that would have been required for it has already been done.
Every business has its own version of this dynamic. The visible event in your business might be a product release, a market expansion, a price change, a hire that opens a new line. The structure is the same. The question is what work you can finish before the visible event, so that when the event happens, the conditions for it to land are already in place. Founders who consistently ship things that work spend their time on the invisible side of the calendar. Founders whose launches consistently fall flat spend their time on the visible side, then wonder why the event was not enough.
Why Most Businesses Underinvest in the Pre-Work
The reason most businesses underinvest in pre-launch ecosystem work is that the work does not produce the kind of progress that internal stakeholders, boards, and investors find legible. A milestone that says “the platform cleared regulatory” is something a board can read in a deck. A milestone that says “we trained 80 surgeons on a precursor instrument so the launch lands” is harder to convert into a chart. The work that compounds the most is often the work that reads as the least progress.
The compounding effect is real, though. By the time the visible event happens, the company that did the pre-work is operating from a position the company that skipped it cannot reproduce in the time the market gives them. The two companies look identical on the day of the launch. They do not look identical six months later, because the customer relationships, training infrastructure, evidence base, and procurement readiness on one side did not exist on the other side and cannot be built fast enough.
The Build covers this kind of operational dynamic in practical terms for founders. Not at multinational scale, but at the scale of the businesses subscribers actually run. What does the pre-work look like in your business? What is the equivalent of the Ethicon-stapler-before-Ottava move that builds the conditions for your next launch to land? What is the visible milestone you have been planning around that is actually the back half of the work, not the front?
Building Systems That Make the Pre-Work Possible
The reason most companies cannot run the pre-launch playbook is not that the founders do not see it. It is that their operating systems do not support it. The team is structured around the visible milestone. The budget is allocated to the visible milestone. The reporting cadence tracks the visible milestone. The work that needs to happen on the invisible side of the calendar has no owner, no budget, and no reporting line, so it does not happen.
The systems problem is the more interesting one to work on, because solving it changes the company’s default behavior. Once the operating model has owners for ecosystem work, budget that survives reallocation when the visible milestone is in flight, and reporting that surfaces invisible-side progress, the team starts treating pre-work as a normal mode of operation. That is the difference between a company that occasionally executes the pre-launch play because the founder pushed it through and a company that runs it as the standard play, on every launch, by default.
The Build is a monthly, physical newsletter. It arrives printed and mailed to subscribers every month. The format is not what most founders expect from a business publication in 2026, and the format is part of the point. The problems that determine whether a business wins, how money moves, how systems scale, how to build a team that holds together under pressure, are not problems that change week to week. They benefit from a reading environment that is not competing with feeds and notifications. They benefit from being annotated in the margins, kept on a shelf, and returned to when the problem becomes the problem you are facing this quarter.
From a recent issue
The Cash Flow Gap That Kills Profitable Businesses
Most founders who run out of money are not running unprofitable businesses. They are running businesses where the timing between when money goes out and when money comes in creates a gap that compounds faster than revenue growth closes it. The issue walks through the mechanics of the gap and the specific operational changes that close it without requiring outside capital.
From a recent issue
Why Your Hiring Process Is Producing the Wrong Results
The standard founder approach to hiring is to find the best available person for the role as it currently exists. That approach works until the company is under stress, at which point most of those hires reveal themselves as optimized for the stable environment, not for the volatile one you are actually operating in. The issue covers a different hiring framework designed for businesses that expect significant change.
From a recent issue
Building Systems That Work Without You in the Room
The operational bottleneck for most founder-led businesses is not capital or product or market. It is that the founder is the system. Every decision that matters routes through one person. The issue covers how to build operating systems that produce consistent results when you are not directly involved, which is the prerequisite for every meaningful growth move the business will eventually need to make.
Why physical and monthly
The format is part of the point
The Build arrives printed and mailed once a month. Not weekly. Not digital. The problems that determine whether a business survives are not problems that change week to week. They are durable. They benefit from a reading environment that is not competing with notifications, feeds, and the ambient pressure to respond to everything immediately. Subscribers annotate their issues, keep them, and return to them when the problem they covered becomes the problem they are facing. That does not happen with a digital newsletter that scrolls past on a Tuesday morning.
The Build
The best newsletter for making money, building systems, and getting to where you want to go
Monthly. Physical. Mailed to subscribers. Built for founders who are serious about the operational problems that actually determine whether a business makes it.
30-day trial period
$14.95 — then $79/month