Waleed Asif · Co-founder and CTO, NexHealth · City College beginnings · Forbes 30 Under 30 · $125M Series C

The repairman's API · Profile

Waleed Asif Learned to Fix What Others Threw Away

Before NexHealth became a billion-dollar company, its technical co-founder paid bills by repairing discarded computers. That instinct - open the box, question the design, make the old machinery useful - became a blueprint for taking on healthcare's locked data systems.

Long before Waleed Asif was taking apart healthcare software, the neighborhood had already found him. Broken bicycles arrived. So did computers, furniture and, eventually, car engines. People left things by his door because Asif had acquired a useful reputation: he was willing to look inside. The habit had roots in childhood trips to Pakistan, where he watched relatives repair objects that Americans might simply replace. Waste, in that world, was often only a failure of curiosity.

The lesson stayed with him. During the leanest stretch of NexHealth, the company he started with his City College classmate Alamin Uddin, Asif bought damaged computers and printers, repaired them and sold them online. The work helped support him and his family. It also made a tidy metaphor for what came next, though metaphors are always tidier than the living. Healthcare's record systems were not literally sitting on a curb. Many were securely installed, widely trusted and highly resistant to outsiders. They also kept information in separate rooms whose doors did not readily open.

Asif would make a career from asking whether those doors were quite as permanent as they looked.

I · The useful nuisanceA front desk problem with a back-room answer

Asif met Uddin while both were undergraduates at the City College of New York. Uddin had worked at a doctor's office in the Bronx and discovered that automating something as ordinary as appointment reminders could turn into an expedition. The patient-facing task was simple. The data it required lived inside electronic record software that did not welcome new applications.

In 2014, the pair joined the Zahn Center's inaugural Social Entrepreneurship bootcamp. They were still students, trying several ideas and learning the unromantic craft of customer discovery. By 2016, they were writing the first lines of NexHealth code. The company formally launched in 2017 with online booking that synchronized with an office's existing record system.

That synchronization was the trick. A handsome booking page is a shop window; the difficult engineering happens in the stockroom. A new appointment must be read correctly, checked against the current schedule and written back without corrupting the system that runs the practice. Multiply that by vendors, versions and local configurations, and the apparent convenience becomes an integration campaign.

“I was always a tinkerer and a problem solver.”Waleed Asif, on the habit that preceded NexHealth

Asif's contribution was not merely an enthusiasm for code. It was the repairer's temperament: assume there is a logic inside the box, however unfriendly; learn it; make the machine do one more useful thing. NexHealth built an integration layer that allowed modern scheduling, messaging, forms and payments to communicate with the older systems already running medical and dental offices. Eventually that layer became a product for other developers too.

Waleed Asif and Alamin Uddin, the co-founders of NexHealth, standing together in an office
Two founders, one less photogenic adversary: the legacy database behind the front desk. Waleed Asif, left, and Alamin Uddin built NexHealth around the connection other products preferred not to make.

II · The unpolished middleFor two years, the machine refused to start

Founder stories tend to glide from dorm-room inspiration to investor applause with the middle sanded smooth. NexHealth's middle was rough enough to catch a sleeve. Asif has said the company did not work for more than two years. Customers left. Money ran out repeatedly, even after an early seed round. Employees departed. The founders sometimes went months without paying themselves.

They began with credit-card debt and the proceeds from selling things on eBay. This is frequently called scrappiness, a charming word for circumstances that are rarely charming while one is inside them. Yet the founders kept the distinction that matters in an uncertain company: the problem was real, but their current answer to it might still be wrong. Their task was to preserve conviction about the former while becoming less precious about the latter.

2+early years Asif says the company struggled to work
$125MSeries C announced in 2022
$1Bvaluation attached to that round

His own summary is characteristically blunt: “Don't give up, but don't be dumb.” Perseverance, in this formulation, is not worshipping yesterday's plan. It is continuing to interrogate it. NexHealth found a core team, improved the product and began gaining customers through word of mouth. The repair finally held.

Recognition arrived early enough to look almost premature. Forbes put Asif and Uddin on its 2018 30 Under 30 healthcare list. The financial milestones followed: additional seed capital in 2019, a $15 million Series A in 2020, a $31 million Series B in 2021, then a $125 million Series C in 2022 at a $1 billion valuation. City College's entrepreneurship network celebrated NexHealth as the first unicorn connected to its training programs.

III · The platform betThe best answer is “I don't know”

Money widened the company's options; it did not change Asif's chosen problem. NexHealth now presented two faces. To practices, it offered tools patients could see: online scheduling, reminders, messaging, forms and payments. To developers, it offered the less visible machinery underneath, a common API that could speak to many record and practice-management systems.

The second face contains the larger ambition. In an essay about healthcare APIs, Asif imagined developers using connected records to improve referrals, automate payment ledgers and create portable patient histories. He argued for a system in which builders could work from a common data layer instead of negotiating every closed database independently.

Asked what those developers will ultimately make, he offered the rare executive answer that improves with uncertainty: “I don't know.” A tool has prescribed uses. A platform becomes interesting when its creator can no longer foresee them all. The builder's job changes from designing every room to making sure the road reaches the property.

The front of the product made appointments easier. The back of it made other products possible.

That distinction explains the scale of Asif's language. He has described an ambition for NexHealth to become a highway for health data and a place where other applications are built. The company's own culture document calls its long-term product a protocol moving information from point A to point B. These are infrastructure metaphors, not feature-list metaphors. They imply patience, standardization and the slightly thankless work of being most successful when nobody notices the plumbing.

By 2026, Asif was publicly promoting a third major version of NexHealth's Synchronizer API, including read-and-write workflows for scheduling, finance and clinical records across 15 practice-management systems. He said the platform was powering more than 10,000 locations for hundreds of developers. At a company hackathon in Seattle, teams used the same infrastructure to prototype new software. The private pipe was becoming a public building material.

There is a neat reversal here. Early NexHealth had to persuade individual practices to let two young founders connect to the server in the office. The company now invites hundreds of developers to treat those connections as dependable infrastructure. Each layer of abstraction hides yesterday's argument. A builder can call one API because another team already endured the peculiarities underneath it. Asif's work, viewed this way, is the conversion of nuisance into normality. The most flattering outcome for an integration is that the next engineer never needs to know how disagreeable the original systems were. Reliability erases the drama of its own construction. It turns a hard-won exception into something that feels obvious, then lets a new generation complain about an entirely more interesting class of problem.

IV · The long repairAgency, with a screwdriver attached

Asif's ideas about building are tied to a larger belief in agency. Childhood travel exposed him to families living by different assumptions. Moving from public school to a private Muslim school made him examine another set. When people told him to return to college after he left to build NexHealth, he interpreted their doubt as evidence that imagined limits often arrive disguised as common sense.

His faith is explicit in the way he tells the story, as is a desire to create infrastructure that benefits the Muslim community rather than merely consuming systems built elsewhere. He speaks of ownership, technical ambition and institutions intended to last. There is little modesty in the scale of that aspiration. There is, however, a practical object lesson beneath it: every grand platform begins as a particular thing that will not work.

For NexHealth, that thing was an appointment trying to enter an old record system. For Asif, the response was familiar. Open the casing. Trace the connections. Refuse the assumption that difficult means sealed forever. The company that emerged is larger, better funded and considerably more complicated than the repair jobs once left at his doorstep. The instinct is recognizably the same.

A valuation can tell you what investors believed on a given day. It cannot explain why someone stayed with a stubborn problem through years when the evidence was impolite. For that, the broken computers are more revealing. Asif saw value where other people saw the end of usefulness. Then he learned how to make that judgment at industrial scale.