Some founders focus primarily on strategy – setting direction, identifying markets, making high-level decisions – and delegate the operational work to specialists. Justin Fulcher has never operated that way.
He built RingMD from a solo prototype into a telehealth platform serving more than fifty countries. That required strategic decisions in terms of which markets to enter, which clients to pursue, and when to pivot. It also required him to understand, in practical terms, how each of those markets actually worked – how regulators moved, what it took to convince a hospital system to adopt new technology, how to build a product that performed in places with unreliable internet access. The two tracks ran together.
His career across RingMD and the public sector work that followed reflects a consistent approach: strategy and operations as a single discipline, rather than a sequence.
Fulcher started coding at seven. At thirteen, he founded Carolina Software Solutions in Charleston, South Carolina – a niche web development firm that built websites for local businesses. That early work had nothing to do with vision or strategy. It was client briefs, deadlines, and functional code that either worked or didn't.
By the time he left Clemson at nineteen and bought a ticket to Southeast Asia, he had been running a small business for the better part of five years. When he saw the gap between smartphone penetration and healthcare access in rural Indonesia, his immediate response was to start building. Not planning, not fundraising – building. He coded the RingMD prototype himself, without a company name or a pitch deck, until investors approached him and the project took formal shape.
"I've always thought of strategy and operations as the same conversation," Fulcher has said on the topic. "When you're running a business at thirteen, you don't have the luxury of separating them. You have a client, a deadline, and a problem to solve. That early experience of being directly accountable for outcomes shaped how I've approached every company I've built since."
Strategic thinking is useful for setting direction but limited for identifying what will actually prevent a company from getting there. The obstacles that stall growth in regulated industries are rarely the ones that appear in a market analysis.
Telehealth is a clear example. The strategic case for remote healthcare delivery was evident years before the sector reached meaningful scale. The demand was documented, the technology worked, and the cost arguments were sound. What the strategic picture didn't fully capture was the institutional drag inside the organizations that would have to adopt it: clinical workflows built around in-person attendance, procurement processes that predated remote care as a concept, and professional cultures that viewed the technology with genuine skepticism.
"The strategic case for telehealth services was clear long before the sector moved," Fulcher has said. "What it couldn't account for was the institutional drag inside the organizations that would have to adopt it – the workflows, the procurement assumptions, the professional resistance. That's not something you can see clearly from the outside. You have to be inside the operation to understand it."
The shift, when it came, was organizational before it was technical. It required operational work – convincing healthcare providers market by market, adapting to each regulatory environment, earning trust that didn't transfer between jurisdictions. The strategic argument alone couldn't produce that outcome.
The decision to engineer RingMD for low-bandwidth environments from the outset illustrates how strategic and operational thinking ran together in practice. The strategic logic was to serve markets with the greatest unmet need – rural India, remote Indonesia, communities where qualified medical care was effectively out of reach. That logic had an immediate operational implication: the platform had to perform under severely constrained connectivity conditions as a core design requirement, not as a later adaptation.
"That decision wasn't purely strategic," Fulcher has said of the low-bandwidth approach. "It came from understanding, at an operational level, what our hardest markets actually required. When you're deploying in places where infrastructure is limited, you have to make design decisions that a more comfortable environment would never force you to make. Those decisions made us better at serving every environment that came after."
The platform's artificial intelligence capabilities for clinical decision support and screening were built to meet federal privacy and security requirements from the ground up. FedRAMP authorization, as well as FISMA and HIPAA compliance, were built into the platform's core from the early days – not added for any single client, but because operating across regulated environments simultaneously required that foundation to already be in place.
The Digital India partnership, through which RingMD built a healthcare access gateway reaching 883 million rural residents, required the platform to perform under exactly those constrained conditions. When RingMD later deployed across US federal health systems (including an Indian Health Service contract serving approximately 2.6 million American Indian and Alaska Native individuals across 37 states), the architecture had already been tested in harder environments than any American clinical setting would present.
When Justin Fulcher moved into public service in Washington, first at the Department of Veterans Affairs and then at the Pentagon, the problems he encountered were structurally familiar. Core systems operating on outdated processes, a gap between what was technically possible and what existing infrastructure would allow – it was the same institutional drag he had spent years navigating in healthcare.
As senior adviser to Defense Secretary Pete Hegseth at the Defense Department, Fulcher focused on acquisition reform and IT modernization. His approach followed the same pattern it had at RingMD: understand the operational reality before redesigning the system. At the VA, he took a methodical approach; he was interviewing staff, reviewing programs, and building an accurate picture of how the institution actually functioned before drawing conclusions.
"When I joined the Defense Department, the underlying problem was familiar," Fulcher has said. "Core systems were operating on outdated processes, and there was a gap between what the technology could deliver and what the institution would allow. The work I'd done in regulated environments in healthcare had prepared me to read that pattern quickly. The domain was different, but the structure of the problem was the same."
During his tenure, Fulcher contributed to initiatives that streamlined software procurement timelines, thus compressing processes that had previously taken years into months. He has spoken of the experience with clear respect for the institution and the people inside it. "Working alongside the dedicated men and women of the Defense Department was incredibly inspiring," he has said. "Secretary Hegseth's decisive leadership created the conditions for real progress. What was accomplished during that period was just the beginning."
He departed in July 2025 after completing a planned period of public service. He's said that his future endeavors will remain focused on national security and defense modernization.
Fulcher's operating principles – execution over narrative, accountability over optics, durability over speed – have held across contexts that look very different on the surface. The thread connecting a web development firm in Charleston, a telehealth platform across fifty countries, and a term of service at the Defense Department is less about domain than about discipline.
"Durability is what I'm most interested in studying now," the technology founder has said – "in the companies I advise, in the systems I've worked to reform. The outcomes that last are the ones built on genuine operational understanding, not just on a clear strategic vision. Those things aren't in conflict, but one without the other rarely holds."
For Justin Fulcher, who started building at seven and has not stopped since, that observation reads less like a conclusion than a working principle – still being tested, still being refined.
