Billionaire Cashback System: I Can't Go Broke!-Chapter 45: Thursday

If audio player doesn't work, press Reset or reload the page.
Chapter 45: Thursday

The boardroom on the forty-seventh floor was long and glass-walled, the city visible on two sides, a table that sat twelve with chairs that cost more than most people’s rent.

Diana had it set with water, coffee, and nothing else. Just a room and enough chairs.

Ryan arrived first with the team at 9:50, ten minutes early.

They settled around one end of the table — Danny and Iralis beside each other, laptops open, the technical overview printed and stacked in front of them.

Liam across from them with his competitor analysis. Mike at the near end, the only one without a laptop, which was deliberate. Sophie at Ryan’s right with the design mockups loaded and ready on her screen.

Ryan looked at them.

"Same as the presentation Saturday," he said. "Except she’s going to push harder than I did."

"How much harder," Mike asked.

"Enough it’ll matters greatly how you respond, not just what you say."

Iralis adjusted her printed notes by a small degree and said nothing.

At 10:02 the boardroom door opened.

Diana came in first. Dark suit, hair back, the same composed authority as Monday. Behind her was a woman Ryan didn’t recognize — late thirties, natural hair cut close, glasses, a leather portfolio under one arm. She had the energy of someone brought to a meeting for a defined purpose. 𝙛𝒓𝓮𝙚𝔀𝒆𝒃𝓷𝒐𝓿𝙚𝓵.𝙘𝒐𝒎

"This is Dr. Amara Cole," Diana said, taking her seat at the head of the table. "She advises my firm on technical acquisitions. I’ve asked her to join us."

Dr. Cole sat beside Diana, opened the portfolio, and looked at the team with assessing eyes that had been in many rooms like this and had developed efficient ways of determining what was worth her time.

"Thank you for coming," Ryan said.

Diana looked at the team. "Who’s presenting."

"All of us," Ryan said. "Different sections."

Diana nodded once. "Start."

---

Danny went first, same as Saturday, the technical framework. He was cleaner than he’d been with the team — tighter, no digressions, a presentation that came from having given it once already and knowing where it worked and where it didn’t.

Dr. Cole waited until he was four minutes in before she said anything.

"The adaptive layer," she said. "How does it learn the team’s workflow without significant manual input from the user."

Danny looked at her. "Passive observation initially. The platform runs in the background for the first two weeks, mapping how the team moves between their existing tools — what they open in sequence, what they copy between platforms, where the gaps in their current automation are. It builds a behavioral map before it suggests anything."

"What’s the data retention model."

"On-premise option for enterprise clients who have compliance requirements. Cloud default for the mid-market we’re targeting, with full encryption at rest and in transit. The behavioral data never leaves the client’s instance."

"GDPR."

"Compliant by architecture, not by policy addition. We built the data model around it rather than adding compliance on top."

Dr. Cole wrote something in the portfolio.

Diana watched her write without expression.

---

Liam presented the market case, and Dr. Cole let him get through most of it before she stopped him.

"Your churn assumption for year two," she said. "Twelve percent. That’s optimistic for a new entrant in enterprise software."

"It’s below the segment average," Liam said. "The mid-market segment average for SaaS tools in the productivity category runs between eighteen and twenty-two percent annually. We’re projecting twelve because our integration model creates switching costs that didn’t exist with previous tools — once Bridge has mapped a team’s workflow, replacing it means rebuilding that map from scratch. That’s not nothing."

"You’re assuming your retention mechanism works as designed."

"I’m assuming the product does what it’s designed to do," Liam said. "If it doesn’t, twelve percent is the least of our problems."

Dr. Cole looked at him for a second. Wrote something.

---

Sophie presented the design and Dr. Cole largely left her alone, which Ryan took as either approval or disinterest and couldn’t immediately determine which. Diana, however, stopped Sophie twice — once to ask about the onboarding flow and once to ask about accessibility compliance, both of which Sophie answered without hesitation and in enough detail that Ryan could see Diana processing the answers carefully.

When Sophie finished, Diana looked at Iralis.

"You annotated the technical overview," she said.

Iralis looked at her. "Yes."

"I read your notes." Diana paused. "The scaling concern on page seven. You proposed a solution in the margin. Walk me through it."

Iralis walked her through it.

She spoke for four minutes without stopping, clearly and without any performance of clarity — just the information in the order it needed to be in. Dr. Cole’s pen moved twice.

Danny listened, hearing a colleague explain something they’d discussed together but presented better than they’d managed themselves.

When Iralis finished, Dr. Cole looked up from her portfolio.

"How long have you been working in systems architecture," she asked.

"Four years professionally. Before that academically."

"Where."

Iralis told her.

Dr. Cole wrote something longer this time.

Diana looked at Ryan.

"Questions for your team," she said. "From me. Not technical."

"Go ahead."

Diana looked at them one by one, unhurried. "Why this company. You’re all qualified enough to be somewhere else. Some of you were somewhere else. Why here."

A brief silence.

Mike spoke first, which Ryan hadn’t expected. "Because my last company was spending time building something nobody needed for people who didn’t care, and I watched it happen and stayed anyway because the salary was fine." He shrugged. "This one has a reason to exist. That’s not as common as it sounds."

Liam said, "The problem is a real one. I’ve worked inside companies that were drowning in exactly what we’re describing. I know what the solution is worth to the people who need it."

Danny said, "Ryan called me after years of not talking and told me we were going to build what we said we’d build in college. That’s the reason."

Sophie’s answer was more straightforward.