Chapter 35: Breakfast and balances

Damian was halfway through breakfast when his phone vibrated.

He glanced at the screen, expecting another message from Emily.

Instead, a notification from Westbridge Solutions appeared.

[WESTBRIDGE INVESTMENT UPDATE]

Current estimated company valuation: $6,940,000

Estimated increase since last update: +$240,000

Investment performance: Positive

Damian stopped chewing.

He read the notification twice.

Then he slowly placed his spoon on the table.

"Not bad."

The update wasn’t an official payment.

He hadn’t received any money directly.

The increase represented the estimated value of the company—and, by extension, the value of his stake.

Still, seeing the number climb had a different effect than watching his bank balance increase.

Cash was immediate.

Company value was potential.

It could grow.

It could disappear.

It could become something much larger than he initially expected.

Damian opened the report.

The figures were based on recent pilot activity, new interest from the second university, and projected revenue from future institutional contracts.

The company was still far from being a major player.

But it was no longer just a small software team testing an idea with fifty students.

Things were moving.

And the more they moved, the more complicated his position became.

If the company grows, my investment grows.

He leaned back slightly.

But if the company makes a bad decision, I lose more than money.

That thought lingered longer than he expected.

His phone vibrated again.

Emily: Morning, babe. Are you on campus yet?

Damian smiled.

Damian: Not yet. Leaving soon.

Emily: Good. Don’t forget your breakfast this time.

He looked down at the half-finished meal.

Damian: I’m literally eating.

Emily: You say that now.

Damian: You’re becoming very demanding.

Emily: And you’re becoming very dramatic, my love.

Damian shook his head, smiling at the screen.

The system, investment reports, and business decisions could wait for a few minutes.

For now, he finished his breakfast.

⸻

"You’re late."

Ethan was standing outside the lecture hall with his backpack hanging from one shoulder.

Damian checked the time.

"I’m three minutes early."

"By your standards, that’s late."

"Since when do I have standards?"

"Since you started wearing shoes that don’t look like they survived a natural disaster."

Damian glanced down at his sneakers.

"They’re clean."

"Exactly. Suspicious."

Damian pushed past him.

"Good morning to you too."

Ethan followed.

"How’s married life?"

"We’ve been dating for less than twenty-four hours."

"That’s what they all say."

"Who are they?"

"People who are secretly planning weddings."

Damian gave him a flat look.

Ethan grinned.

"So, did Emily call you babe yet?"

Damian paused for half a second.

Ethan’s grin widened.

"She did."

"That’s not important."

"She called you babe."

"People use words."

"And she called you my love?"

Damian turned toward him.

"How do you know that?"

Ethan pointed at his face.

"Your expression."

"My expression doesn’t reveal anything."

"Your expression is currently screaming, ’Emily called me my love and I have no idea how to behave.’"

Damian opened his mouth.

Then closed it.

Ethan laughed.

"Thought so."

They entered the hall just as the lecturer began arranging his notes.

Ethan lowered his voice.

"Relax. You’re allowed to be happy."

Damian looked at him.

The teasing had disappeared from Ethan’s voice.

For a moment, he sounded serious.

Damian nodded.

"I know."

"Good."

Ethan sat down.

Then added,

"But if you start writing her name in your notebook, I’m transferring seats."

Damian shoved his shoulder.

⸻

The day passed in the usual rhythm of lectures, notes, assignments, and Ethan complaining about a quiz neither of them had prepared for properly.

At lunch, Emily joined them.

She dropped into the seat beside Damian rather than across from him.

Ethan noticed.

Of course he noticed. 𝘧𝓇ℯℯ𝑤ℯ𝘣𝓃ℴ

He slowly looked from Emily to Damian.

Then he smiled.

"Interesting."

Emily opened her food.

"What?"

"Nothing."

"That was definitely not a nothing smile."

Ethan raised both hands.

"I’m simply observing."

Damian sighed.

"Can you eat without making this weird?"

"I’m not making anything weird. You two are the ones sitting like—"

"Ethan."

"Fine."

He took a bite of his food.

Three seconds later, Emily reached over and stole one of Damian’s fries.

Damian looked at her.

"You have your own."

"I wanted yours."

"Why?"

"Because yours tastes better."

Ethan pointed at them with his fork.

"That. That’s exactly what I’m talking about."

Emily laughed.

Damian shook his head and pushed the rest of his fries toward her.

Ethan stared at the gesture.

"Unbelievable."

"What now?" Damian asked.

"Nothing. I’m just witnessing the gradual destruction of your independence."

Emily smiled.

"He’s always been dramatic."

"Thank you," Ethan said. "Finally, someone understands me."

Damian’s phone vibrated on the table.

This time, the message was from Sarah.

Sarah: Reminder: 2 PM meeting at the Westbridge office. Daniel wants to review the next stage of the pilot.

Damian read it and locked his phone.

Emily noticed.

"Business?"

"Westbridge meeting."

"Today?"

"Yeah. They’re reviewing the next stage of the pilot."

Ethan leaned back.

"Look at you. Busy businessman."

"I’m still attending the same classes as you."

"That doesn’t mean anything. Criminals attend classes too."

Damian stared at him.

"How did you even get there?"

"I don’t know. It felt right."

Emily laughed.

Damian looked at the time.

He still had another lecture before the meeting.

The day was becoming crowded.

But the Westbridge meeting mattered.

The investment update from that morning had reminded him of something he hadn’t fully considered before.

The company was growing.

And growth always came with problems.

⸻

The Westbridge office looked almost exactly the same as Damian remembered.

Third floor.

Plain hallway.

A modest reception area.

A few desks visible through the glass partition.

No expensive furniture.

No dramatic signs of success.

Yet the atmosphere had changed.

There were more people moving around.

Two employees stood near a whiteboard, discussing a list of technical issues.

Someone was on a phone call near the entrance.

A stack of printed reports sat on the reception desk.

The office was busier.

Not chaotic.

Just active.

Sarah spotted Damian first.

"You’re right on time."

"I try."

She gave him an amused look.

"That’s not what Daniel says."

"Daniel has unrealistic expectations."

Sarah smiled and led him toward the meeting room.

Daniel was already inside with his laptop open.

A large spreadsheet filled the screen.

"Damian," he said, standing briefly. "Good to see you."

"Good to see you too."

Damian took a seat.

Sarah sat beside Daniel and opened a folder.

For a few seconds, nobody spoke.

Then Daniel turned the laptop toward them.

"The two-hundred-student pilot is progressing well."

That sounded positive.

But Daniel didn’t smile.

Damian noticed.

"There’s a ’but’ coming."

Daniel gave a small laugh.

"Several, actually."

Sarah slid a report across the table.

"We’ve had strong engagement during the first stage. The number of students completing the onboarding process is higher than expected, and the second university is satisfied with the early results."

"That’s good," Damian said.

"It is," Daniel replied. "But the larger pilot has exposed some weaknesses."

Damian picked up the report.

The first page contained user feedback.

The second showed support requests.

The third displayed implementation costs.

He scanned the figures.

There were more support tickets than during the original fifty-student pilot.

That part made sense.

Four times as many users meant more questions.

But the pattern was more important than the total.

Most complaints appeared to fall into a few categories.

Confusion during onboarding.

Difficulty understanding certain features.

Problems connecting existing business records.

Repeated questions about the same functions.

Damian looked up.

"How many people are handling support?"

"Two employees directly," Sarah said. "The development team helps when the issue is technical."

"Which means they’re being pulled away from development."

"Exactly."

Daniel leaned back.

"We can manage two hundred students. The problem is what happens if the next institution wants five hundred. Or a thousand."

Damian returned his attention to the report.

The original pilot had been small enough for the team to handle problems manually.

At two hundred users, the cracks were becoming visible.

At a thousand, those cracks could turn into structural damage.

The product isn’t failing.

It’s growing faster than the process around it.

That distinction mattered.

A bad product needed to be fixed.

A growing product needed systems.

Damian tapped the report.

"Have you separated the support requests by issue?"

"We’ve categorized them," Sarah said.

"Broadly?"

"Mostly."

"Can I see the breakdown?"

Sarah turned her laptop around.

A chart appeared on the screen.

Damian studied it.

A large portion of the complaints came from the same three areas.

The onboarding instructions were unclear.

Students didn’t understand the purpose of the first guided challenge.

And many users couldn’t tell whether a problem was caused by their own input or by the software.

Damian leaned forward.

"How much of the support workload comes from these three issues?"

Sarah checked the figures.

"Roughly sixty percent."

"Then that’s where you start."

Daniel folded his arms.

"We’ve already discussed improving the tutorials."

"Improving them isn’t enough if users don’t know what they’re supposed to accomplish."

Damian pointed toward the chart.

"The guided challenge is supposed to show them how the product works. But if they don’t understand why they’re doing it, they’ll treat it like another task they have to complete."

Sarah nodded slowly.

"So you think the challenge needs more context."

"Context, and a clear result. Before they begin, they should know what they’re trying to achieve. After they finish, they should see what they actually accomplished."

Daniel looked thoughtful.

"That would mean changing the onboarding flow."

"Probably. But I wouldn’t rebuild everything."

Damian scanned the report again.

"Test a smaller change first. Add a short explanation before the first challenge. Something that tells users what problem they’re solving and what they’ll get from completing it. Then track whether the number of related questions drops."

Sarah made a note.

Daniel watched him.

"You’ve become more comfortable with this."

Damian glanced up.

"With what?"

"Looking at a problem without immediately trying to solve the entire company."

Damian smiled faintly.

"I’m learning."

That was the honest answer.

He wasn’t a business expert.

He didn’t have years of experience managing teams or scaling software.

But he could recognize patterns.

He could ask questions.

He could avoid pretending that every problem needed a dramatic solution.

Daniel nodded.

"That’s useful."

Sarah flipped to another page.

"There is one more thing."

The tone in her voice changed slightly.

Damian noticed.

"What is it?"

"We received an inquiry from another university yesterday."

"That’s good, isn’t it?"

"It could be."

Sarah exchanged a glance with Daniel.

"The university didn’t just ask about our pilot. They mentioned that another software company had already approached them with a similar offer."

Damian’s eyes narrowed.

"Similar how?"

"Student access. Trial period. Business-management tools. A guided onboarding process."

Daniel leaned forward.

"They haven’t signed anything with the other company. But they made it clear that they’re comparing options."

Damian looked at the report again.

The numbers suddenly felt different.

Until now, Westbridge had been trying to prove that its product worked.

Now someone else was paying attention.

That wasn’t necessarily bad.

Competition could validate a market.

It could also expose weaknesses.

"Do we know who the company is?" Damian asked.

Sarah opened another file.

"Yes."

She turned the laptop toward him.

A logo appeared at the top of the document.

NEXORA SOLUTIONS

Beneath it was a short company profile.

Established software provider specializing in small-business management platforms, institutional partnerships, and scalable digital services.

Damian read the description carefully.

Unlike Westbridge, Nexora already had:

An established customer base.A larger technical team.More extensive institutional connections.A mature product.Considerably more capital.

Westbridge had something Nexora probably didn’t.

A small, flexible team.

A product still being shaped around user feedback.

And a pilot that had begun producing useful results.

But flexibility only mattered if they could survive long enough to use it.

Damian leaned back.

"How long have they been operating?"

"Almost six years," Daniel said.

"How long have they been interested in universities?"

"We don’t know yet."

"Have they contacted us directly?"

"No."

Damian looked at the Nexora logo.

The company wasn’t attacking Westbridge.

Not yet.

They had simply noticed an opportunity and entered the same space.

That was normal business.

Still, something about the timing bothered him.

The second university had only recently shown interest.

Now another company was offering a similar arrangement.

Maybe they were already watching this market.

Or maybe Westbridge’s results had finally made them pay attention.

Either way, the situation had changed.

Daniel closed the file.

"We’re not going to panic over one competitor."

"Good," Damian said.

"We also aren’t going to ignore them."

"Better."

Sarah smiled slightly.

Daniel turned toward Damian.

"I want you to look into their product before our next meeting. Not just their features. Their pricing, target customers, onboarding process, and the kind of institutions they usually work with."

Damian nodded.

"I can do that."

"We’re not asking you to compete with them alone," Daniel added. "But you have a habit of noticing things other people overlook."

Damian almost laughed.

"That’s a generous way of saying I ask too many questions."

"It can be both."

The meeting continued for another thirty minutes.

They discussed support systems, onboarding experiments, pilot feedback, and the possibility of bringing in student ambassadors to help new users.

By the time Damian left the office, the sun had begun to sink behind the buildings.

His phone vibrated as he reached the pavement.

A new message from Emily.

Emily: Are you done, babe?

Damian smiled.

Damian: Just finished.

Emily: How did it go?

He glanced back at the office.

Then at the Nexora report open on his phone.

Damian: Good. Westbridge has a few things to fix.

He paused before adding:

Damian: And there’s a competitor.

The reply came quickly.

Emily: Already?

Damian: Apparently.

Emily: Are you worried, my love?

Damian considered the question.

Was he worried?

Not exactly.

But he could feel something changing.

The system had made him wealthy.

Westbridge had given that wealth direction.

Now, for the first time, he was beginning to understand that money could create opportunities without guaranteeing success.

He typed his response.

Damian: Not worried. Just paying attention.

Emily replied with a heart.

Damian slipped the phone into his pocket.

Then the familiar golden screen appeared in front of him.

Only he could see it.

[SYSTEM NOTICE]

[NEW FINANCIAL PRESSURE DETECTED.]

Damian stopped walking.

A second line appeared.

[EXTERNAL MARKET COMPETITION MAY AFFECT EXISTING INVESTMENT VALUE.]

His expression sharpened.

The system had never mentioned Westbridge’s competitors before.

He read the message again.

Then another line appeared.

[MONITORING RECOMMENDED.]

Damian stared at the screen.

"That’s new."

The golden interface remained in place.

No instructions.

No reward.

No clear explanation of what would happen next.

Just a warning.

Then it vanished.

Damian looked down the street.

Somewhere in the city, Nexora Solutions was continuing its business as usual.

Its employees were working.

Its executives were making plans.

Its investors were expecting growth.

And now, whether they knew it or not, their decisions could affect something Damian owned.

He pulled out his phone again and opened the report.

NEXORA SOLUTIONS

He studied the logo for a moment.

Then he began searching.

Not because he wanted to destroy them.

Not because he believed Westbridge was guaranteed to win.

But because he had learned one thing about money.

If you wanted to keep it—

You had to understand what could take it away.