talehub

Chapter 19 - THE NUMBER NOBODY WANTED TO SEE

The first formal request for my consulting proposal arrived the following afternoon.

Denise copied Ben, Patricia, and Dad on the email. The scope was limited to three items: an improved purchase-approval warning, a clearer supplier-return display, and a training session for the department leads.

I prepared the estimate that evening.

It included the work, the deliverables, the payment schedule, and the boundaries of the engagement. The company would own the completed customizations after payment. Existing documentation would remain available to the staff. No one would need my personal login to operate the store.

I also included a provision for future requests.

Any additional work would require written approval.

I sent it on Thursday morning.

Patricia replied that she would review the numbers with the company's accountant. Denise thanked me for making the scope clear. Ben wrote only three words.

This is fair.

Dad did not reply.

I expected that.

What I didn't expect was the phone call from Patricia two days later.

"Luke, do you have a few minutes?"

"Depends. Is this about the proposal?"

"Partly. But I need to ask you something about the transition document."

My stomach tightened.

"What about it?"

"Did your father tell you he intended to list your continued technical support as part of the succession plan?"

"No."

"Did you agree to provide that support after Ben becomes president?"

"No."

She paused.

"That's what I thought."

I sat down at my desk.

"Why are you asking?"

"Because the draft agreement refers to ongoing operational support from you. It doesn't specify compensation, scope, or a termination date. I asked your father whether there was a separate consulting agreement, and he said the arrangement had been discussed with you."

"He told Ben that, too."

Patricia exhaled slowly.

"I was afraid of that."

"What does the company need from me?"

"Nothing yet. I need to clarify the financial assumptions behind the transition plan. Your father has asked me to prepare a report showing whether the business can support the leadership changes and the next stage of growth."

"That sounds like your job."

"It is. But I found something I think you should know."

She asked whether I could come to the store on Monday afternoon to review a set of operational records.

I hesitated.

"Is this a request from the company?"

"Yes. A limited records review. I'm not asking you to do free technical work. I need you to explain the assumptions used in the operating model you built."

"Send me the scope in writing."

"I will."

On Monday, I returned to Dawson Hardware & Supply.

Patricia met me in her office with two folders and a laptop. She was a careful woman, the kind who checked a total twice before presenting it and never used the phrase "probably fine" when she could say "not yet verified."

She opened the first folder.

"The store's reported revenue is healthy enough for its size," she said. "We have loyal customers, good contractor relationships, and manageable operating costs. But our cash position is tighter than the headline numbers suggest."

She showed me the figures.

Supplier payments were becoming more concentrated. Several large orders had been placed before their expected sales cycles. Some contractor accounts paid slowly, and a few had exceeded the credit limits established in the old policy.

None of those issues was new by itself.

Together, they created pressure.

"How long has this been happening?" I asked.

"Some of it has been building for eighteen months. The recent inventory order made it more visible, but it didn't create the underlying pattern."

"Has Dad seen this?"

"He's received the monthly reports."

"Has he understood them?"

Patricia chose her words carefully.

"He understands the individual numbers. I'm not sure he's considered what happens when they move in the same direction."

I looked at the screen.

The business wasn't collapsing. That was important. We weren't dealing with a secret catastrophe that would conveniently turn me into a hero.

We were dealing with a familiar problem: a company that had grown more complex while its decision-making structure remained built around one person's instincts.

Dad could still recognize a good supplier, negotiate with a contractor, and judge whether a product belonged on the shelves. He had spent decades learning the business.

But the company now carried more inventory, processed more transactions, and served customers through systems that required coordinated decisions.

The old methods had not suddenly become worthless.

They had become insufficient.

"What's the number you're worried about?" I asked.

Patricia turned the laptop toward me.

"The projected cash requirement for the next two supplier cycles."

The figure was larger than I expected.

I studied the assumptions.

Some of the forecast depended on the seasonal inventory selling through at the pace Ben had projected. Other assumptions depended on several contractor accounts paying within their usual windows. The model also assumed that the company could delay certain discretionary purchases without damaging supplier relationships.

It was not an absurd forecast.

It was optimistic.

"Who approved these assumptions?"

"The draft came from the office. Your father reviewed it."

"Did Ben?"

"Not yet."

I leaned back.

"Then don't send it to him as if it's final."

"I won't. But I need to understand the operational side before I challenge it."

We spent the next hour checking reorder cycles, supplier terms, and the difference between accounting profit and available cash.

I explained why a high-margin order could still be dangerous if the stock remained unsold too long. I showed her how the inventory dashboard tracked products that were tying up cash without generating enough turnover. We compared the current forecast with historical purchasing patterns.

The result was a more conservative projection.

It didn't predict disaster.

It showed that the company would need tighter purchasing discipline, better collections on overdue accounts, and a temporary pause on several discretionary expenses if it wanted to maintain a safe operating buffer.

Patricia saved the revised model.

"This is exactly what I needed."

"Then you've got it."

She looked at me.

"There's another issue."

I waited.

"The succession plan assumes the business will expand its contractor sales next year. Your father wants to open another branch or warehouse location."

I stared at her.

"Has he approved a site?"

"Not formally. He's been speaking with a commercial property broker."

"Does the forecast include the cost of a second location?"

"Only a preliminary allowance."

"Then the forecast isn't ready."

"I agree."

She closed the folder.

"Luke, I need you to understand something. I'm not trying to pull you back into the company. But your father is talking about expansion while we are still tightening the current operation."

"I understand."

"And if you know something about the systems that changes these assumptions, I need you to tell me."

"I'll answer questions within the scope we've agreed on. I'm not taking over the forecast."

"Fair enough."

As I stood to leave, Patricia said, "One more thing."

"What?"

"Your father has been telling people that you are stepping away because you're angry about Ben's promotion."

I looked at her.

"Is that what you think?"

"No. I think you stepped away because the arrangement was never properly defined."

That was the closest thing to vindication I had received from anyone at the company.

It felt surprisingly small.

"Thank you," I said.

I was halfway to the parking lot when Dad caught up with me.

"Patricia says you've been reviewing the financial forecast."

"She asked me to explain the operational assumptions. I did."

"Why wasn't I included?"

"Because she was checking the model before circulating it."

He folded his arms.

"She tells me the cash projections are more conservative now."

"They reflect the current inventory exposure and the payment cycles."

"You're making the business look weaker than it is."

"I'm making the forecast more realistic."

"We've been in business for thirty-five years. I know what this company can handle."

"You do know this company. But knowing it doesn't mean every forecast is correct."

His face darkened.

"You think because you built a spreadsheet, you understand the business better than I do."

"No. I think because you built the business, you should want accurate information before you risk its future."

For a moment, he looked genuinely wounded.

Then the anger returned.

"Ben is supposed to be learning from me, not from a report designed to make him afraid."

"Then teach him how to read the report."

He stared at me.

I could see the argument forming: I was disrespectful. I was ungrateful. I was making the family look divided.

But none of those accusations would change the numbers.

Dad looked toward the store.

"When I was your age, I didn't need a consultant to tell me how to run my own company."

"When you were my age, the company was smaller, the supply chain was different, and you weren't trying to expand while changing leadership."

He looked back at me.

"You're enjoying this."

"No."

"You're enjoying proving me wrong."

I shook my head.

"I'm tired of having to prove that I'm right before anyone takes the work seriously."

I walked away before he could turn the conversation into another contest.

That evening, Ben called.

"I saw the revised forecast," he said.

"Patricia sent it?"

"She sent it to me and Dad. He thinks it's too cautious."

"What do you think?"

"I think the number is uncomfortable."

"That wasn't my question."

He was quiet.

"I think it's probably closer to reality than the first version."

I looked out at the city lights.

"Then what are you going to do?"

"Meet with Denise and Patricia tomorrow. We're going to separate what we know from what we hope will happen. We'll work out a purchasing plan that doesn't depend on everything going perfectly."

"Good."

"Luke?"

"Yeah?"

"I don't think I can convince Dad to stop talking about the second location."

"Then don't start by convincing him. Start by asking what the second location will cost, what problem it solves, and how the current store will perform if the expansion takes longer than expected."

Ben let out a slow breath.

"That's what I was going to ask you."

"I know."

"But I wanted to ask before I asked."

I understood what he meant.

He was trying to learn the difference between asking me to make a decision for him and asking me to explain how to make one himself.

"Ask Denise and Patricia first," I said. "They know the operation. If you still need a technical explanation, put it in the project request."

"Okay."

After we hung up, I sat at my desk and looked at the old family photograph beside my monitor.

Dad stood outside the store on its tenth anniversary, one arm around Mom and the other around me. Ben was small enough to stand in front of us, holding a toy hammer.

We were all smiling.

I had spent years believing that if I made myself useful enough, my place in that picture would remain secure.

May you like

Now I was beginning to understand that being needed and being valued were not the same thing.

And the business my father had built was about to learn that distinction the hard way.

Related Stories

Other posts