How I Became Ultra Rich Using a Reconstruction System-Chapter 243: First Product

Elena didn’t let the momentum die in the hallway.

She walked out of the prototype room and didn’t stop until she reached the taped floor plan, where the future assembly area was still bare concrete and chalk marks.

"Here," she said.

Everyone stopped where the tape line cut across the floor like a border.

Jun’s engineers shifted their weight, looking around like they expected equipment to appear. Maria kept her arms crossed, eyes scanning exits and access points. Victor stayed a step behind, already reading the space as an audit diagram. Hana stood near the wall, phone in hand, ready to turn decisions into forms and emails.

Timothy stayed quiet and let Elena own the room.

Elena pointed to the section taped off as receiving and quarantine. "This is where we start acting like a manufacturer. Not an idea."

Jun nodded once. "We need a product definition."

"We need three," Elena said. "But we pick one first."

Maria’s head tilted. "You said power module."

Elena looked at her. "Power module first. Monitoring second. Sensor platform third."

Jun’s engineer asked the obvious question. "Power module for what device."

Jun answered before Elena could. "For ours. The one we build to survive brownouts and ugly grounding."

Victor cut in. "Be careful with language. ’For ours’ implies we already have a registered device family."

Jun’s jaw moved, annoyed.

Elena didn’t let it turn into a fight. "He means our eventual product line. For now, we define it as a regulated power management component intended for use inside diagnostic and monitoring equipment. B2B. Not patient-facing. Not decision-making."

Victor nodded. "That’s defensible. If it stays true."

Hana stepped forward. "Then we need a project code and a paper trail that starts today."

Elena pointed at Hana. "Assign it."

Hana tapped her screen. "TGMS-P1. Power module."

Jun’s engineer looked around the empty floor. "We don’t even have benches."

Elena looked at him like he was new. "Then we build benches before we build boards."

Maria nodded. "And we build service kits before we build volume."

Timothy finally spoke. "What’s the minimum version that’s still honest."

Jun answered. "A module that can handle unstable input, protect downstream boards, log events, and be replaced fast. No fancy."

Victor raised a finger. "If it logs events, it creates data. Data creates obligations. Storage, security, retention policy."

Jun looked like he wanted to throw something.

Elena stepped in again. "We can make logging optional for early versions. Or local-only. No network. No patient data. Just power event codes."

Victor considered. "That helps. But we still treat it like a controlled record."

Hana wrote it down. "Local power event log. No PHI. No network until approved."

Elena looked at everyone. "Good. Now we stop talking like this is a brainstorm."

She walked to the whiteboard and uncapped a marker. The board still had faint stains from old meetings. She didn’t care.

She wrote four headings.

FUNCTION

CONSTRAINTS

TESTS

SERVICE

Then she pointed at Jun. "Function."

Jun stepped up without hesitation and took the marker from her. "Input range. Output stability. Surge protection. Brownout ride-through, but not pretending to be a generator. Safe shutdown."

Maria cut in. "And a visible status indicator. Something a tired tech can read without an app."

Jun wrote it. "Status indicator."

Victor cleared his throat. "Constraints."

Elena gave him the marker back.

Victor wrote slowly, like each word was a legal boundary.

"Non-clinical component."

"No diagnostic claims."

"No patient-facing interface."

"No wireless."

"No cloud."

"No AI."

"Documented performance limits."

"Traceable parts."

He underlined the last one twice.

Jun’s engineers watched, some of them visibly wanting to argue, but Elena didn’t allow the air to turn playful.

Elena pointed at Jun again. "Tests."

Jun took the marker. "Thermal cycling. Vibration. Voltage sag simulation. Surge simulation. Long-run burn-in. Fail-safe behavior."

Maria added from her spot. "Humidity. Real humidity. Not air-conditioned lab humidity."

Jun wrote it. "High humidity test."

Victor added, "EMC planning. If you ignore it now, it destroys you later."

Jun wrote it, annoyed. "EMC pre-check."

Elena pointed to Maria. "Service."

Maria walked up and took the marker. "Replaceable in under ten minutes with basic tools. No special jigs. Clear labels. Torque specs. Simple connectors. Spare parts stocked locally."

She wrote one more line and then underlined it.

"Service manual drafted before pilot units."

Jun’s engineers looked at her like she’d insulted them.

Maria didn’t care. She capped the marker and stepped back.

"Now," Elena said, "we assign owners."

She pointed at Jun. "You own design and test planning. Not just the circuit. The process."

Jun nodded once.

She pointed at Maria. "You own serviceability requirements and field kit design."

Maria nodded.

She pointed at Victor. "You own the compliance posture and language. Anything written goes through you."

Victor nodded.

She pointed at Hana. "You own structure. Procurement paths. Facility readiness. Document control."

Hana nodded and immediately started typing.

Elena turned to Timothy last. "And you keep people from trying to turn this into a press release."

Timothy didn’t smile. "Done."

They didn’t stay in the open floor long after that. Elena moved them into the temporary conference room where the aircon worked and the table had enough space for laptops.

Hana pulled up a simple project tracker on the screen. No fancy dashboard. Just tasks and dates.

"Before we buy anything," she said, "we need internal procurement rules for this entity. Separate from TG Holdings. Clean audit trail."

Victor nodded. "And supplier onboarding."

Jun’s engineer looked tired already. "We can use existing TG suppliers."

Victor’s eyes moved to him. "Not without review. Medical components are not automotive components. Traceability expectations shift."

Jun cut in. "Some suppliers overlap."

Victor didn’t deny it. "Then they pass onboarding. Or they don’t."

Elena sat down and opened a blank document.

"Let’s do the first product spec," she said. "One page. If we can’t write it in one page, we don’t understand it."

Jun leaned forward. "I can write it now."

Elena held up a hand. "You write it with Maria and Victor in the room."

Jun’s engineer muttered, "Here we go."

Elena looked at him. Not angry. Just direct.

"Yes," she said. "Here we go."

They built the one-page spec in real time.

Name: TGMS Power Stabilization Module — P1

Intended use: internal power conditioning for diagnostic/monitoring equipment.

Scope: regulated component, not a complete medical device.

Interface: standard DC outputs, documented connectors, no network.

Logging: local fault codes only, non-patient, non-clinical.

Environmental: high humidity tolerance, heat tolerance, dust exposure assumptions.

Service: swap under ten minutes, standard tools, clear labeling.

Safety: failsafe shutdown, no unsafe output drift.

Victor rewrote three lines immediately.

Jun didn’t like it.

He leaned back and looked at Victor. "You’re making it sound weak."

Victor didn’t look up. "I’m making it sound true."

Elena didn’t let Jun argue.

"This is not a sales sheet," she said. "It’s a spec."

Maria pointed at the line about swap time. "Ten minutes is generous. Make it eight."

Jun’s mouth opened.

Elena cut it off. "Make it eight."

Jun’s engineer rubbed his face. "We haven’t even designed the enclosure."

Maria answered, "Then design the enclosure around service, not the other way around."

Silence for a beat.

Then Jun nodded once. "Fine."

Hana chimed in. "Bench setup next. We need a controlled test bench area. Power input simulation. Surge generator. Load bank."

Jun’s engineer looked at her. "That’s a lot of capital."

Timothy spoke calmly. "We’re not cheaping out on the bench. The bench is the product’s birthplace."

Victor added, "And the bench is evidence."

That settled it.

Elena assigned deadlines that made people uncomfortable, but not impossible.

"One week for bench procurement list," she said. "Two weeks to assemble and validate bench. Four weeks for first board prototype. Six weeks for initial stress test results. No public anything."

Jun’s engineer looked at Jun like he wanted to protest the timeline.

Jun didn’t. He was already building the list in his head.

Maria asked, "Who handles packaging and spares."

Elena answered, "You do. With Hana."

Hana looked up. "We’ll need a warehouse corner. Locked. Tracked."

Victor nodded. "And lot tracking. Even for pilot."

Jun’s engineer sighed. "This is going to be slow."

Elena leaned forward. "If you want fast, go build phone chargers."

The room went quiet again.

Timothy watched them. This was what he wanted. People disagreeing in ways that produced constraints, not slogans.

Hana’s phone buzzed. She glanced at it and grimaced.

"What," Elena asked.

Hana didn’t hide it. "Someone from corporate heard about ’a new medical machine room’ and wants a tour. They’re not supposed to know, but they heard."

Maria’s jaw tightened. "No."

Victor didn’t look surprised. "It starts."

Elena looked at Timothy. "Handle it."

Timothy nodded once. "They don’t tour."

Hana asked, "What do I tell them."

Timothy’s voice stayed flat. "Tell them we’re setting up a regulated manufacturing facility. No prototypes. No demos. If they want to support, they support by not asking."

Hana typed as he spoke.

Elena stood and capped her marker.

"Alright," she said. "We have two rooms now. Prototype room stays locked and boring. Floor room becomes real."

Jun closed his laptop and stood. "I’m going to the automotive lab to pull the surge equipment list."

Maria stood too. "I’m drafting the service manual template today."

Victor gathered his papers. "I’m writing the supplier onboarding checklist and the document control policy. If it’s not controlled, it doesn’t exist."

Hana nodded. "And I’m locking internal comms down. No rumors. No curiosity tours."

They moved out of the conference room in small groups, already splitting tasks without needing more talk.

Timothy stayed behind for a moment with Elena.

She watched the team disperse, then looked at him.

"You understand what happens next," she said.

"People will try to turn this into a story," Timothy replied.

"And if they do," Elena said, "we lose control."

Timothy nodded. "So we don’t let them."

Elena didn’t smile. She grabbed her folder and headed for the floor, following Jun and Maria out into the noise of contractors and bare concrete, where the taped lines waited to become something permanent.