Ficool

Chapter 1068 - Chapter 1178: Raytheon's Intentions

Through the recent military campaign against Turkey, the U.S. Air Force had fully realized the power of Castle's two missile designs: the Jericho and the Ex-Wife. Backed strongly by General Peterson—Deputy Chief of Operations for the Air Force and the second-in-command at NORAD—the Air Force was now seriously planning a full-scale replacement of all currently deployed air-to-air missiles with the Ex-Wife, intending to standardize it across all fighter jets in service.

But there was a problem.

While the improved version of the Ex-Wife missile did offer excellent performance—especially compared to Raytheon's existing AIM-120 AMRAAM—it still wasn't an all-around solution. It performed admirably in certain metrics but lacked effectiveness in others, particularly in close-quarters dogfighting scenarios. As a result, the Air Force concluded that despite the tremendous boost in payload capacity it offered to stealth fighters like the F-22 (which rely on internal weapon bays for maintaining stealth), the Ex-Wife couldn't fulfill all tactical needs.

They needed a new missile—a compact, high-powered close-range dogfighting weapon to complement the Ex-Wife.

Naturally, this discussion within the Air Force quickly reached Raytheon, the long-time provider of nearly all U.S. air-to-air missiles. Eager to get ahead of the curve—and recognizing that their legacy platforms were being pushed aside—they decided it was time to act.

Which was why they had come to Castle directly, hoping to accomplish two things at once: negotiate licensing for the Ex-Wife (a lost cause, as it turned out) and commission him to develop a brand-new missile.

Castle felt somewhat awkward about their request. His deal with Northrop wasn't just a production license for the Ex-Wife—it included the full patent transfer and all rights to further development. Legally, it had nothing to do with him anymore.

He was puzzled. How could Raytheon make such a basic mistake? Hadn't they done their due diligence before coming here?

And more importantly—how did they expect him to just drop everything and design a new missile for them right now?

It wasn't a matter of technical difficulty. He could do it. Easily.

But between Beckett's congressional campaign (which had officially kicked off and required his behind-the-scenes support), and the ongoing fallout with the Indian government—who were still furious at him for profiting off their financial market crash—he had more than enough on his plate.

And now Raytheon wanted a tailor-made missile? Get in line.

But he couldn't outright reject them either. This was Raytheon—one of the U.S.'s Big Four military contractors, standing shoulder to shoulder with Lockheed, Boeing, and Northrop. His fearless attitude toward foreign governments like India came precisely because he had the unwavering support of the U.S. military-industrial complex.

Pissing off Raytheon wasn't exactly in his best interest.

So, after a moment's thought, Castle carefully crafted a diplomatic reply.

"Apologies, gentlemen. I think there might be some confusion. First, the Ex-Wife missile—its production rights and intellectual property have been fully transferred to Northrop Grumman. I have no further involvement with the platform, including its future development.

"Second, at the moment, I truly don't have the time or bandwidth to take on a new project. My girlfriend is currently running for office in New York, and I'm deeply involved in her campaign's logistics and support.

"Lastly… I'm dealing with some lingering issues from a certain South Asian government. You may have heard of it. So unfortunately, I can't commit to anything right now."

Raytheon's vice president offered a knowing smile. "Mr. Castle, we're actually aware of all that. But the reason we're still here is because… we have the means to resolve those issues for you."

He placed special emphasis on the word issues, making it clear that the feud with the Indian government was nothing more than a small matter to a company like Raytheon.

As for the Ex-Wife's licensing? Not a concern.

Beckett's campaign logistics? An afterthought.

It was all within their reach.

By now, both parties had dropped all pretense. Raytheon was openly offering to help Castle clear the deck—remove obstacles, provide political cover, and handle foreign pressure—in exchange for one thing: a new weapon design, tailor-made for their upcoming bid on the next-generation U.S. missile program.

Castle thought carefully.

He didn't say yes. Not immediately. He simply said he needed time to consider it.

Raytheon didn't push. They never expected him to agree on the spot. This visit was just to establish contact, to open the door. They'd made their offer, and he'd heard it. That was enough—for now. After all, the Pentagon hadn't even officially launched the bidding process for new missiles yet. There was still time.

After sending off the two executives, Castle stood at the entrance of his mansion, deep in thought.

I could squeeze in some time to 'develop' (read: plagiarize) a missile from Stark Industries…

After all, thanks to his mysteriously quiet and seemingly dormant system, he had access not just to the Iron Man suits and Arc Reactor tech, but to nearly every single piece of military hardware that Stark had ever developed for the U.S. in the Marvel universe.

That was why, even when he created his first drone and heavily modified it for this world's tech level, it still debuted as a top-tier platform.

For military corporations like Raytheon or Northrop, who had to spend years and millions on R&D with no guarantee of success, Castle's process looked almost magical.

To him, designing a missile was as simple as looking up the blueprints in his head and translating it into reality. No need for prototyping, debugging, or simulation testing. Just plug, play, and profit.

What he really needed to decide was—what do I want out of this deal?

He already had more than enough allies across the U.S. military, politics, and defense industry. He wasn't the vulnerable newcomer he'd been two years ago, fresh from another world. Back then, even showing off a slightly futuristic drone could get him kidnapped or assassinated.

Now, he could say "no" to anyone and walk away untouched.

But Raytheon's proposal was tempting.

Not because he wanted to work with them—but because the VP had all but promised they'd shield him from the Indian government's retaliation. That kind of support was no small offer.

And with his father currently in Mumbai—along with his special ops team and two retired CIA operatives—planning a hit on the same Indian MP who had orchestrated the failed kidnapping attempt, tensions could escalate any time.

So yes, the offer had weight.

Castle had already made up his mind to say yes.

But he didn't want to seem too eager.

He'd wait until things calmed down—until Beckett's campaign settled into its rhythm, and his personal schedule cleared a bit—then he'd give them the green light.

Raytheon, wisely, hadn't pressured him. They'd given him space.

Which, in Castle's opinion, was the smart move.

Just then, John came walking over with his daughter in one arm and Castle's son, little Alex, in the other. He found his friend still staring at the doorway in a daze.

"What's with the deep thoughts?" John asked. "Raytheon gone already? What'd they want?"

Castle turned and explained the situation.

John raised an eyebrow. "They want you to develop a brand-new missile for them? You actually considering it?"

More Chapters