©WebNovelPub
How I Became Ultra Rich Using a Reconstruction System-Chapter 234: Medical Enterprise Part 2
Hana did not open a browser first. She opened a notebook.
She sat at her dining table that evening with her laptop closed, pen in hand, and wrote what Timothy had actually asked for, stripped of intent and tone.
Structure.
Risk separation.
Compliance reality.
Failure points.
Then she wrote the real question underneath.
How do you build a medical technology company in the Philippines without turning it into a permanent legal and reputational hazard.
She left it there until the sentence stopped sounding theoretical and started sounding operational.
The next morning, she made calls.
Not to people who liked her. Not to people who owed favors. She reached out to people who would answer honestly and quickly, and who would not care who the parent company was if the idea was flawed.
A corporate lawyer whose practice revolved around regulated industries. A former Department of Health policy staffer now consulting for hospitals. A regulatory affairs head from a local medical device distributor. Two biomedical engineers she remembered from foundation site visits—people who fixed machines when budgets ran out and paperwork lagged behind reality.
By noon, her calendar was full of short calls stacked tightly together. She kept the meeting titles vague. No one questioned it. Hana rarely wasted time, and people had learned not to ask what she was doing unless they wanted to be involved.
The lawyer came first.
"You want to set up a medical device company," he said, voice flat, efficient.
"A medtech subsidiary," Hana replied. "Under a holding company."
"That distinction matters to investors," he said. "Not to regulators."
Hana wrote that down.
"What’s the first thing that breaks," she asked.
"Classification," the lawyer said without hesitation. "If you don’t know exactly what kind of medical device you’re producing, you don’t know which laws apply. And if you guess wrong, everything downstream collapses."
"So regulatory strategy before factory planning," Hana said.
"Yes," he replied. "And keep your scope narrow. The fastest way to get buried is trying to touch too many device categories at once."
They talked structure. Separate subsidiary. Separate compliance function. Clean governance lines. Not too defensive, not too loose.
"If it looks like you’re insulating to avoid responsibility," the lawyer warned, "you invite scrutiny. You want separation for focus, not for escape."
Hana ended the call with a request for a short written brief: entity setup considerations, baseline licensing requirements, and the most common legal failure patterns he’d seen.
The second call was with the former DOH staffer.
Hana framed it as a scenario.
"Hypothetically," she said, "an industrial group wants to enter medtech manufacturing. Devices, diagnostics, service. No hospitals. No care delivery. Where does it get killed first."
The consultant laughed, tired and sharp. "By overpromising. Especially publicly."
"Second," Hana prompted.
"Procurement politics," the consultant said. "Hospitals don’t buy the best machine. They buy what fits bidding rules, budget cycles, and what they can keep alive with the staff they already have."
"And distributors," Hana said. 𝑓𝘳𝑒𝑒𝓌𝘦𝘣𝘯ℴ𝑣𝘦𝑙.𝘤𝑜𝑚
"Yes," the consultant replied. "They don’t like being bypassed. Even if bypassing them fixes problems."
"So resistance is guaranteed," Hana said.
"Absolutely," the consultant replied. "They’ll call it safety. They’ll call it compliance. It won’t be about either."
They talked about regulation as practice rather than theory. Where approvals slowed. Which documents were always questioned. How long "temporary" delays tended to become permanent.
"What about pilots," Hana asked. "Partnering with hospitals early."
"Don’t start with doctors," the consultant said. "Start with biomedical engineers. They’ll tell you if your machine survives real conditions. Doctors care about outcomes. Engineers care about whether it works tomorrow."
That aligned cleanly with what Timothy had already heard.
One more note went down.
Avoid AI-heavy branding. Frame everything as tools, not replacements.
The third call was with the regulatory affairs head from a distributor. This one pushed back immediately.
"You think we enjoy delays," he said when Hana raised lead times. "You think customs is fun."
"I think delays have become normal," Hana replied. "And normal problems stop getting fixed."
Silence, then a slower reply.
"If you manufacture locally," he said, "your biggest challenge isn’t machines. It’s parts, calibration tools, technician certification, and service logistics. Devices don’t fail alone. Systems fail."
"What happens if someone builds a real service network," Hana asked.
"You’ll gain trust faster than with any feature list," he said. "But you’ll burn money doing it. For years."
"That’s acceptable," Hana said.
He exhaled, not quite a laugh. "Then pick devices that break often and matter when they do. Monitoring systems. Power modules. Imaging components. Things that trigger emergency calls."
"And incumbents," Hana said. "How do they respond."
"They lobby. They whisper. They question compliance. They warn hospitals you’re risky," he said. "You’ll need to be cleaner than clean."
By late afternoon, Hana had pages of notes and a clear shape emerging. Not a plan. A constraint map.
That night, she organized everything into a single document for Timothy. No filler. No background education. Just verified realities grouped the way he thought.
Structure came first.
Separate subsidiary under TG Holdings. Independent compliance and risk teams. Clear governance lines. Early board oversight, not delayed. Walls built for accountability, not avoidance.
Regulatory reality followed.
Device classification defines the path. Product scope before factory spend. Documentation treated as baseline operations. Any drift toward invasive or autonomous clinical decision-making spikes scrutiny immediately.
Market reality came next.
Procurement rules shape adoption more than performance. Distribution incumbents will resist if margins or relevance are threatened. Public hospitals value uptime and service more than features.
Trust strategy followed.
Service infrastructure precedes product scaling. Biomedical engineers before marketing teams. Avoid narratives that suggest replacing clinicians. Tools support judgment, they do not override it.
Then starting scope.
Diagnostics and monitoring systems. Failure-prone, mission-critical components. Power, sensors, ruggedized imaging subassemblies. Devices that reduce downtime immediately and can be serviced locally.
She ended with a short list.
Known pressure points. Compliance complaints. Procurement influence. Media narratives. Lawsuits as leverage.
She saved the file and closed her laptop.
The next day, she brought it to Timothy in person.
She placed the folder on his desk and sat down without ceremony.
"I mapped the reality," she said.
Timothy opened it and scanned quickly, eyes moving straight to the parts where friction lived.
"Summarize," he said.
"It’s viable," Hana said. "But only if we stay narrow, quiet, and service-first. Regulation comes before capex. Trust comes before scale. Resistance is guaranteed."
He paused on the final section.
"You believe this," he said.
"I expect it," Hana replied.
Timothy closed the folder and leaned back.
"What does ’quietly’ actually mean," he asked.
"Entity formation first," Hana said. "Regulatory hires first. Service planning first. No product announcements. No internal hype. We build the skeleton while everyone assumes you’re busy elsewhere."
Timothy nodded once.
"And after," he said.
Hana met his gaze. "After, we decide what we’re willing to be responsible for. Not what we can build. What we can own."







