Billionaire Cashback System: I Can't Go Broke!-Chapter 39: Two Minutes

Ryan looked at Diana Lockridge and didn’t touch the deck.

"Every company in the world," he said, "is drowning in tools that were supposed to save them time. Project management software, communication platforms, file systems, scheduling tools — the average mid-size company is paying for eleven different software subscriptions and their teams are spending forty percent of their working week managing the tools instead of doing the work the tools were supposed to enable."

Diana hadn’t moved.

"That problem has a name," Ryan continued. "Tool fragmentation. And every existing solution to it has made the same mistake — they try to replace the tools. Build a bigger, better, all-in-one platform. Convince the company to migrate everything, retrain everyone, absorb the six month productivity dip while people figure out the new system." He paused. "And it almost never works. You know why?"

Diana said nothing. Waiting.

"Because companies don’t have a tools problem. They have a translation problem. The tools work fine in isolation. The problem is they don’t talk to each other, and the people using them have developed their own workflows around the gaps, and nobody has mapped those workflows, and when you rip the tools out and replace them you rip out the institutional knowledge those workarounds represent."

He leaned forward slightly.

"We don’t replace the tools. We sit between them. Bridge learns how your team actually works — not how the software says they should work, how they actually do. It maps the gaps, automates the translation between platforms, and builds a unified layer that reflects the team’s real behavior back to them in a single interface. No migration or retraining. No six month productivity loss. You plug Bridge in on a Tuesday and by Thursday your team is working faster than they were on Monday."

Diana uncrossed and recrossed her legs. The movement was brief and entirely unconscious — she was focused on what he was saying. Ryan kept his eyes on her face.

"That’s the product," he said. "Twelve weeks to MVP. The market is companies between fifty and five hundred employees — too big for spreadsheets, too small for enterprise contracts. It’s the most underserved segment in the B2B software space and it represents a combined addressable market of forty-three billion dollars in the United States alone."

He sat back.

"That’s two minutes," he said.

The office was quiet. Outside the windows the city moved at its usual pace, completely indifferent.

Diana looked at him. She hadn’t written anything down, hadn’t reached for the deck, hadn’t looked away since he started talking.

"How do you acquire customers," she said.

"Bottom up. Free tier that actually works — not a crippled demo, a functional product with actual utility. Teams adopt it without asking their IT department. It spreads inside the company. When it reaches critical mass the company converts to a paid plan because the alternative is removing something people are already depending on."

"Product-led growth."

"Yes."

"Everyone says that."

"Everyone says it because it works when the product is actually good," Ryan said. "It doesn’t work when the free tier is deliberately broken to force conversion. Ours won’t be."

Diana picked up the deck.

She went through it the way she’d read the document when he arrived — focused, fast, turning pages like she who knew exactly what she was looking for and was checking whether it was there.

She stopped on the market analysis page. Read it. Turned to the technical overview. Stopped again.

"Your technical lead," she said, not looking up. "This annotation in the margins."

"That’s our systems architect. Iralis Davids."

Diana looked up. "How old."

"Twenty-six."

Diana looked back at the page. Read the annotation fully. "She identified a scaling problem in the architecture and proposed a solution in the margin of someone else’s document."

"That’s how she operates."

Diana turned another page. The financial projections — conservative on the left, realistic in the middle, optimistic on the right, each one built from actual assumptions that were documented in the footnotes rather than reverse-engineered from a number that sounded good.

She put the deck down.

"What do you need from me," she said.

Ryan had been waiting for that question since he walked in.

"Two things," he said. "The first is capital. Seed round. I’m not here to negotiate the number today — I want to know if you’re interested before we talk terms."

"And the second."

Ryan held her gaze. "I need the investment backdated to six weeks ago. Documented as an initial capital injection into Rebuild Tech LLC at point of formation."

The office was very quiet.

Diana looked at him with the quality of attention that meant she understood exactly what he was asking and why, and was deciding whether to let him explain or address it directly.

"The IRS," she said.

Not a question.

Ryan didn’t flinch. "I’ve had unusual deposit activity that predates the company’s formal revenue. It needs a source that holds up to documentation review."

"You’re asking me to sign paperwork that describes a transaction that didn’t happen."

"I’m asking you to sign paperwork that describes a transaction that will have happened," Ryan said. "The investment is real and so is the money. The company is real and it’s going to be worth considerably more than what you put in. The only thing I’m asking you to adjust is the date."

Diana sat back in her chair.

She looked at him for a long moment — she wasn’t hostile or even alarmed, she had an expression of steady assessment. Again, how she’d looked at the painting at the gallery. Working out what something actually was rather than what it appeared to be.

Ryan waited. He didn’t fill the silence. The silence was hers to fill.

"You walked into my office," she said finally, "on the strength of a two minute phone pitch, asked me to invest in a company with no revenue and a twelve week MVP timeline, and then asked me to backdate the paperwork to help you manage a federal inquiry."

"Yes," Ryan said.

"And you said all of that like you were reading off a menu."

"I find confidence is more useful than apology in most situations."

Diana looked at the deck on her desk. At the window. Back at Ryan.

"The product is authentic," she said.

"Yes."

"And so is the team,"

"Yes."

"And you believe this works."

"I know it works," Ryan said. "The question is how big it gets, not whether it does."

Diana was quiet for a moment.

Then she reached forward and turned the deck back to the market analysis page. She looked at it again, one finger moving along a line of numbers.

"Your total addressable market figure," she said. "Forty-three billion. How did you arrive at that."

"Page nine. The methodology is in the footnote."

She turned to page nine. Read the footnote. Turned back to the market page.

She put the deck face down on the desk.

Ryan watched her think. He could see it happening — the real version of it, not performed consideration but actual processing. She’d done this a long time. She knew what good looked like and she was measuring what was in front of her against that standard.

"I want to meet the team," she said.

"I can arrange that this week."

"The systems architect specifically. I want thirty minutes with her before I commit to anything."

"Done."

"And I want a board seat. Advisory, non-voting, but I want the seat."

"Also done."

Diana picked up her coffee, found it had gone cold, and set it back down with the mild displeasure of someone who’d forgotten about it.

"The backdating," she said. "I’ll have my attorney structure it. The documentation will reflect an initial consultation period beginning six weeks ago and a capital commitment formalized at company registration. That’s defensible."

"That’s all I need."

"If this goes sideways," Diana said, "I want it understood that my involvement is as an investor who did appropriate due diligence on a promising early stage company. Nothing more."

"Understood."

"And Ryan."

He looked at her.

"If the product isn’t what that deck says it is when I meet the team," she said, "this conversation didn’t happen."

"The product is what the deck says it is," Ryan said. "And it’ll be more than that by the time you see it."

Diana looked at him.

Something shifted in her expression —little, barely visible, a shift that happened when someone had decided something and was in the process of accepting the decision.

Her eyes stayed on his a beat longer than the conversation strictly required.

Then she picked up her pen and opened her notebook.

"Have your person contact mine today," she said. "We’ll schedule the team meeting for Thursday."

"I’ll have her call within the hour."

Diana wrote something down. Ryan stood, picked up his briefcase, and buttoned his jacket.

"Mr. Russo," she said without looking up from the notebook.

He stopped.

"Next time you walk into someone’s office and ask them to do something that could expose them to legal risk," she said, "lead with the product. Not the ask."

Ryan considered that.

"The product would have taken longer than two minutes," he said. "And you gave me two minutes."

Diana looked up.

For the first time since he’d walked into the office, something moved at the corner of her mouth.

"Thursday," she said.

Ryan nodded and walked out.