Justin Fulcher has scaled a company across nearly fifty countries, navigated federal procurement systems, and served as senior advisor inside two of America's most complex government agencies. His account of what scaling in regulated environments actually demands from the people doing it is notably different from how the subject is usually discussed.
Most scaling advice is written for founders who control the key variables: timing, go-to-market strategy, and product iteration cycles. In regulated industries such as healthcare, defense, and government, those variables aren't yours to control. The market has its own cadence, its own approval chains, and its own tolerance for the pace of change. What that requires, both intellectually and personally, isn't a slower version of the startup playbook. It's a structurally different discipline.
The first thing regulated environments ask of a founder is a change in how they read resistance.
In conventional startup scaling, institutional resistance is an obstacle – something to route around or push through. In regulated markets, it is usually information. A hospital system that won't adopt a new platform, a government procurement office that won't accelerate its timeline, a regulatory body organized around assumptions that predate the technology being introduced – none of these are simply inertia. They are signals about how the system understands risk, and the founder who reads them as such is better positioned than one who treats them as friction.
"The instinct is to move through resistance as fast as possible," Justin Fulcher has said. "In regulated environments, that instinct will cost you. The resistance is telling you something about the institution – about what it's protecting, what it's been burned by, and what it needs before it will move. That's not a reason to slow down your ambition. It's a reason to sharpen your analysis before you accelerate your execution."
That intellectual posture – curiosity before urgency – shaped how Fulcher built RingMD across Southeast Asia and later into US federal health systems. The medical community's skepticism of telehealth services in the early years wasn't irrational. Clinical workflows, liability frameworks, and billing systems had all been organized around in-person attendance for decades. Understanding that architecture – why it existed, what it was doing for the people inside it – was what allowed RingMD to position itself as an extension of existing capability rather than a disruption to it. Founders who skip that step tend to build things the institution can't absorb, regardless of how good the product is.
The most common structural error technology founders make when entering regulated markets is treating compliance as a later-stage problem – something to address once the product has proven itself and a contract is within reach.
In regulated environments, that sequence doesn't work. Compliance isn't a feature you add. It's the infrastructure the product sits on. Institutional clients in government and healthcare can't adopt a platform that doesn't meet their security and regulatory requirements, regardless of what else it can do. Building where the stakes are real means building compliance in from the start – not because any single client demands it, but because the architecture has to be in place before the conversation can begin.
RingMD's FedRAMP Moderate authorization, FISMA compliance, and HIPAA infrastructure weren't built in response to a specific contract requirement. They were built because operating across regulated environments simultaneously required that foundation to already exist. When the Indian Health Service awarded RingMD its first dedicated telehealth platform in 2021 (serving approximately 2.6 million American Indian and Alaska Native individuals across 24 hospitals and 51 clinics in 37 states), the architecture had already been in place and tested.
The contract was possible because the compliance work had been done long before the contract was on the table. That sequencing is not accidental. It is the discipline that separates companies that can serve institutional clients at scale from those that can only pursue them.
Of all the differences between scaling in regulated markets and scaling in conventional ones, this is the one that surprises founders most consistently: the trust earned in one jurisdiction tells the next one almost nothing about you.
A government contract in India doesn't signal anything to a US federal procurement office. A FedRAMP authorization doesn't open the door in Southeast Asia. Every institution – every regulator, every hospital system, every government agency – operates its own internal logic about risk, and credibility has to be established within that logic before anything else can move. There is no accumulated reputation that transfers automatically. You earn it each time, or you don't scale.
Justin Fulcher encountered this across every market RingMD entered. The evolution of telehealth as a viable clinical tool wasn't a single argument won once. It was a case made and remade across different countries, different regulatory frameworks, and different professional cultures. "This is not a replacement for in-person care," he told skeptical clinicians in each new market. "This is an augmentation to what you're currently doing." That reframing worked – but only through repetition, and only by starting from the institution's own concerns rather than from RingMD's value proposition.
"Institutional trust doesn't compound the way market reputation does," Fulcher has said. "You don't get credit for what you've already earned somewhere else. Every new environment is a new negotiation. The founders who understand that build differently – they treat trust as a running operational cost, not a milestone you clear and move past."
Startup culture is built, in no small part, around fast validation. You ship, you get a signal, you correct. The feedback loop is tight enough that confidence and direction can be maintained through the data the product generates.
Regulated environments don't offer that mechanism. Procurement cycles run for months or years. Regulatory approvals move on institutional schedules that don't respond to urgency. Progress is slow, often opaque, and rarely announced in any way that feels proportional to the effort it took to produce it.
That reflects on a founder emotionally in specific ways. The absence of market feedback as a confidence mechanism requires a different internal resource: a conviction about the underlying problem that can sustain momentum through periods where nothing visible is moving.
Fulcher has written about what that sustained pressure costs, and his language is not abstract: "Victory is rare. Survival is achievable." It is the language of someone who spent seven years living inside a problem in Southeast Asia, who stayed long enough to see a three-month trip become a decade of work, and who understands what that kind of commitment demands of a person, not just of a company.
The lifestyle implications compound over time. Operating across jurisdictions with competing regulatory timelines and procurement calendars means accepting that your schedule is not your own. The question of when a contract closes, when a government will partner, when an institution will move – those timelines are set by forces outside your control, and the founder who can't make peace with that tends to either burn out or make decisions driven by exhaustion rather than judgment. The ones who sustain it tend to share a specific quality: they find the problem itself sufficiently interesting to remain curious about it long after the initial motivation has been spent.
When Fulcher moved into government as a senior advisor – first at the Department of Veterans Affairs, then at the Defense Department – the problems he encountered were structurally familiar. Core systems operate on outdated processes, creating institutional drag at every level. The gap between what technology could deliver and what existing systems would allow wasn't a function of bad intent. It was accumulated weight that no one had been required to revisit.
That pattern was identical to what RingMD had navigated in healthcare. The difference was the stakes. In a regulated market, a wrong call costs a client or a market position. Inside a federal agency, the consequences land on the people the institution exists to serve – veterans, service members, and communities with no alternative. That distinction recalibrates how a founder thinks about judgment under uncertainty, and it doesn't leave when the tenure ends.
His work at the Defense Department contributed to initiatives that reduced software procurement timelines previously measured in years – outcomes that required acting on incomplete information and committing to a direction before the results were visible. It's the same kind of discipline that scaling a regulated business demands.
"Secretary Hegseth's decisive leadership created the conditions for that work to move forward," Fulcher has said of his time there. His future endeavors remain focused on national security and defense modernization – work that, by his own account, is just the beginning.
Scaling a regulated business is not scaling with additional friction. It is a different kind of work, requiring a different relationship to time, to trust, and to the personal resources a founder draws on when external validation is slow and institutional resistance is the daily condition.
The intellectual shift is real: regulated environments reward curiosity over urgency, and founders who read institutional resistance as information tend to build more durably than those who treat it as an obstacle.
The personal cost is real: the long feedback loop requires a conviction about the underlying problem that doesn't depend on the market confirming it quickly.
And the trust requirement is real: every institution, every jurisdiction, every regulatory environment is a new negotiation. No prior record substitutes for earning it again.
For Justin Fulcher, that work began at nineteen with a prototype built in Southeast Asia and has continued across every regulated environment since. The context changes, but the discipline doesn't.
