Chapter 10
He cast his line again, catching rare fish effortlessly, amassing wealth, and upgrading his gear far beyond what any player could achieve through normal gameplay. Other avatars crowded around him, their chat bubbles filled with awe and confusion.
But Daniel didn’t feel guilty. It was a taste of the freedom he craved — a reminder that the limitations others imposed on him were nothing more than illusions.
He closed the game, his mind buzzing with ideas. The office, the web portals, Leo, Ray — he could outmaneuver them all. He could craft his own destiny, reshape his environment, and when the time came, leave a legacy of chaos they wouldn’t recover from.
As he powered down his laptop, a calm, confident smile settled on his face.
Daniel entered the office the next day, his footsteps echoing through the unusually quiet IT section. He half-expected the usual rush of morning chatter or the clack of keyboards, but the room was empty. He checked the clock on the wall; it was past the official start time. The absence of Ray, Joe, and Graham struck him as odd, but he shrugged it off.
Maybe another meeting or some last-minute scramble, he thought.
Settling into his chair, he powered up his computer and began attending to the pile of emails that had landed in his inbox overnight. Requests poured in from different departments: evaluations for new software, specifications for hardware upgrades, troubleshooting for minor technical glitches. His fingers flew across the keyboard, and within minutes, each task was handled with flawless efficiency.
His inbox, once a chaotic mess, was cleared in record time. He leaned back, a small smile of satisfaction tugging at the corners of his lips. The feeling of productivity, of being in control, never got old.
The door creaked open behind him, and he glanced over his shoulder to see Ray walking in. His eyes were weary, his posture slightly slumped, but his expression was more resigned than hostile.
“Daniel,” Ray said, his voice lacking its usual edge. “Can you attend the induction meeting today? It’s a briefing before the external developers take over the project for the company’s official procurement portal.”
Daniel’s heart gave a small, excited thud. This was it — the moment he’d been waiting for. The chance to demonstrate his true value, to position himself where his skills couldn’t be ignored.
He nodded, keeping his expression neutral. “Sure, no problem.”
Ray gave a tight-lipped nod in return and walked away without further comment. Daniel knew Ray had no idea what was coming — no clue that the person he routinely overlooked was about to change the game entirely.
He glanced at the clock. An hour left until the meeting. The anticipation buzzed beneath his skin, but he didn’t want to burn himself out with nervous energy. He opened his favorite podcast playlist on his office computer, slipped on his headphones, and leaned back in his chair.
The smooth voices of podcast hosts discussing tech innovations and digital revolutions filled his ears. The words flowed like a soothing stream, grounding him. He closed his eyes briefly, letting the calm wash over him. His mind, however, remained sharp, running through the possibilities and strategies for the meeting ahead.
This is my moment, he thought, his fingers drumming lightly on the desk. They’re going to see what I can really do.
The minutes ticked by, each one bringing him closer to the opportunity he had been preparing for. He could feel it — the shift in the air, the inevitable turn of the tide.
As the hour drew near, Daniel straightened up, removed his headphones, and took a steadying breath. The excitement was tempered with cold resolve. He wasn’t just going to participate in this meeting; he was going to own it.
His time had come, and nothing was going to stop him now.
Daniel stepped into the vast conference room, the heavy doors closing softly behind him. The space was illuminated by sleek overhead lighting, reflecting off the polished mahogany table that stretched nearly the length of the room. Potted plants sat in the corners, adding a touch of vibrancy to the otherwise corporate atmosphere.
On one side of the table, the external developers from AnswerQ were seated. Their crisp uniforms bore the company’s name and logo, a sleek design that spoke to professionalism and precision. Each team member had a notepad, laptops open and ready, their faces set in practiced neutrality. At the center of their group was their lead, Zian Oki — a man in his early forties, with sharp eyes and an air of calm authority.
On the opposite side, the procurement section was represented by Director Brian Ortega, a man in his mid-fifties with silver-streaked hair and a gaze that carried the weight of experience. Beside him sat a senior procurement officer, a woman named Elaine Park, who glanced up briefly as Daniel entered, her expression unreadable. Alongside them were two additional procurement officers.
Brian’s eyes immediately settled on Daniel, his brow furrowing slightly. “Where’s Ray?” he asked, his voice clipped but polite.
Daniel met his gaze with a calm confidence. “Ray sent me in his place,” he replied evenly.
Brian’s lips pressed into a thin line, his eyes narrowing as if weighing the situation. After a moment, he nodded silently and gestured for Daniel to take a seat.
Daniel settled in, his hands resting lightly on the table, his eyes scanning the room, taking in every detail — the stiff posture of the developers, the wary glances exchanged by the procurement team, the faint hum of the projector as it warmed up.
Zian Oki cleared his throat, drawing everyone’s attention. He tapped a few keys on his laptop, and the large screen at the front of the room flickered to life. A sleek slide deck appeared, outlining the framework of their proposal. Zian began his presentation, his voice smooth and deliberate.
Unauthorized usage: this narrative is on Amazon without the author's consent. Report any sightings.
“As requested, we’ve designed a comprehensive procurement portal with all the specified features,” Zian began, his laser pointer highlighting bullet points as he spoke. “The portal will feature an intuitive user interface, robust search capabilities, real-time tracking of procurement requests, and a secure backend to handle sensitive data. Our proposed timeline for development is approximately six months, with additional time allocated for testing and deployment.”
Daniel listened intently, his eyes narrowing slightly. The features Zian outlined were standard, functional but uninspired. The timeline, six months, seemed bloated — a buffer typical of external contractors who padded deadlines for safety. He could do better. Much better.
Zian continued, detailing the infrastructure, security measures, and support plans. He spoke with the confident cadence of someone who had given this pitch many times before. The procurement team nodded along, but Daniel could sense the undercurrent of doubt in their expressions — the lingering uncertainty about cost, efficiency, and effectiveness.
As Zian reached the final slide, he clicked off the projector and clasped his hands. “This approach ensures that your company will receive a state-of-the-art portal, tailored to your needs. We’re confident this solution will streamline procurement processes and enhance operational efficiency.”
Silence settled over the room. Director Brian Ortega leaned back in his chair, his fingers steepled under his chin, eyes narrowed in thought. Elaine scribbled a note, her brow furrowed.
Daniel’s heart beat steadily in his chest. He knew what was coming next — the questions, the deliberations. And he was ready. This was his chance to change everything, to show them that they didn’t need to outsource this project, that the solution they were looking for was already in the room.
This is it, he thought, his fingers curling slightly on the table’s edge.
Brian leaned forward, his expression firm and thoughtful. “Mr. Oki,” he began, his tone measured, “we need this portal to be as user-friendly as possible. Other departments will be accessing it, and we can’t afford complications. Would it be possible to add a few adjustments? Specifically, features like automated report generation and digital signing to eliminate the need for printing documents.”
A murmur of agreement rippled through the procurement team. The suggestions were practical, aimed at making daily tasks smoother and reducing paper waste — things that would benefit the company immensely.
Zian Oki’s expression remained calm, but a subtle tightening of his jaw betrayed his thoughts. He adjusted his tie before responding. “While I understand the need for these features, Director Ortega, they fall outside the initial scope we discussed. Implementing report generation and digital signing will require additional development time and resources. We can certainly accommodate these changes, but it will necessitate an increase in cost. I’ll be glad to provide an amended proposal reflecting those adjustments.”
The room fell into a contemplative silence. Brian’s eyes narrowed slightly, his fingers drumming softly on the table. He didn’t like the answer, and Daniel knew it. This was the standard playbook for external developers — upselling at every turn, turning minor tweaks into costly amendments.
Brian turned to Elaine, leaning closer to discuss the issue privately. Their voices dropped to a whisper, but their expressions spoke volumes. Elaine frowned, nodding occasionally, while Brian’s jaw tightened with frustration. They were stuck between a rock and a hard place — either accept the inflated costs or go without the improvements they needed.
Daniel leaned back in his chair, a wave of calm washing over him. He’d seen this scenario unfold countless times. External developers promising a baseline product, only to nickel-and-dime their clients for every modification. It was a frustrating dance, one that drained time, money, and patience.
They’re walking straight into the trap, Daniel thought. He knew the signs too well. The hesitation, the frustration — it was all leading to a breaking point. But he also knew this wasn’t the time to step in. Not yet.
He kept his expression neutral, his fingers tapping lightly on his knee under the table. There was no need to reveal his hand in front of AnswerQ. This wasn’t their moment; it was his. When the time was right, when the procurement team’s frustration reached its peak, he would offer his solution — a streamlined, cost-effective, internally developed portal that wouldn’t drain the company’s resources.
For now, he let the scene play out, his patience unwavering. The cracks were forming, and soon, they would need him more than ever.
Let them come to me, he thought, a quiet confidence settling in his chest. They’ll see soon enough.
The air in the conference room felt heavy as Director Brian Ortega announced the meeting was over. The AnswerQ team gathered their materials and filed out, their lead, Zian Oki, wearing a tight, unsatisfied expression. His eyes flicked toward Brian and Elaine, a hint of irritation in his gaze. The door closed behind them with a muted thud, and the atmosphere grew still.
Everyone else had left the room, leaving just Daniel, Elaine, and Brian seated around the vast conference table. The weight of indecision and frustration settled over the two procurement officials. Brian rubbed his temple, exhaustion etched into his features. Elaine flipped through her notes, her brow furrowed, her lips pressed into a thin line.
“We can’t keep going in circles like this,” Elaine muttered, her voice tinged with frustration. “We’ve been struggling for months now. How do we explain this to Chief Director Michael?”
Brian leaned back in his chair, letting out a long sigh. “I don’t know. We’re running out of options, and these external developers are bleeding us dry.”
Daniel watched them quietly, his fingers steepled together. He could feel the opportunity crackling in the air — this was his moment. The frustration, the desperation, the need for a solution — it was all aligned perfectly.
Clearing his throat gently, he leaned forward. “Director Ortega, Elaine, what if the IT section develops the procurement portal?”
Brian’s head snapped up, a confused expression flashing across his face. He blinked at Daniel, his eyes narrowing slightly. “The IT section? Our IT section can’t handle that kind of development work. We don’t have the capability.”
Daniel met his gaze with calm determination. “We do. At least, I do. Give me a chance. Let me build the portal. If it doesn’t meet your expectations, you can go back to hiring another external company. No harm done.”
Elaine’s eyes widened slightly, surprise flickering across her features. She looked at Brian, who seemed caught between skepticism and curiosity. His lips parted, hesitation clear in his voice. “And how long do you think this would take, Daniel?”
“A day,” Daniel said, his tone firm and confident.
Brian’s eyebrows shot up, disbelief etched across his face. “A day? That’s impossible.”
“It’s not,” Daniel assured him. “Trust me. Just one day. If I don’t deliver, you lose nothing. But if I do, we save time, money, and the headache of dealing with external developers.”
Silence stretched between them, the weight of the proposition hanging in the air. Brian looked at Elaine, his eyes searching for answers. She gave a slight shrug, her voice cautious but hopeful. “What do we have to lose? If he can do it in a day, it’s worth the shot. If not, we’re no worse off than we are now.”
Brian sighed, the gears in his mind turning. Finally, he nodded, his expression firming into resolve. “Alright, Daniel. You’ve got your chance. One day. Impress me.”
A quiet thrill surged through Daniel. He’d done it. The door was open, and he was stepping through. He nodded confidently. “You won’t regret this.”
As Brian and Elaine gathered their things and left the room, Daniel remained seated for a moment, a slow smile spreading across his face. This was it — his opportunity to shine, to show them his true capabilities.