Chapter 12 - The Numbers Everyone Deserved
By the time Leah and I left Rebecca’s office, the cleaning crew had begun moving through the hallway. Leah had a laptop under one arm and three pages of handwritten figures in her other hand.
“Come back in the morning,” I told her. “You’ve done enough for one night.”
“Friday is in the morning.”
She wasn’t being stubborn. She was looking at the numbers the way she always had: as promises we had made to people who had already done the work.
We took a smaller conference room and built the forecast Maya had asked for. Leah put wages and payroll taxes on the first lines. Then came the bills that kept customers’ systems running, followed by rent, insurance, and the vendors we could not interrupt without affecting contracted work.
I read out the account balances. Leah corrected me when I tried to include a customer payment that had not arrived.
“It usually lands by Thursday,” I said.
“Usually isn’t cash.”
I took it out.
On a separate page, she listed the payments under investigation. Roughly $2.4 million had already been posted to vendors whose work and authorization required review. It was a preliminary, deduplicated figure, not an established loss. The pending $280,000 Kestrel request was not in it. Neither were party charges whose settlement we had not traced.
The necklace was a settled company-card purchase. Its authorization and any reimbursement still needed checking. Leah gave it its own line rather than quietly folding it into a total that might count it twice.
“This is going to look untidy,” I said.
“It is untidy.”
For eight years, I had seen polished board decks with one confident number at the top. Daniel had been good at presenting those numbers. I had praised him for it without asking often enough what had been left off the slide.
We made a forecast for ordinary payments processing as expected and another for a delay in customer receipts. Both assumed we held nonessential spending. Neither assumed the questioned money would come back. If the Kestrel request cleared, the margin tightened further; the bank had not cleared it, but we could not pretend it had vanished.
Near midnight, Helena joined us by video. The chief operating officer had sent over a list of essential projects and the people needed to deliver them. Rebecca went through proposed vendor holds, marking agreements the company could not simply stop paying.
Helena studied the forecast.
“Can the operating team use this tomorrow?”
“Yes,” Leah said. “If they see the assumptions. I don’t want anyone treating the customer receipts as guaranteed.”
“Then leave the assumptions on the page.”
After the call, Leah closed her laptop but kept one hand on it.
“People are going to ask whether they’re getting paid,” she said.
“They deserve a straight answer.”
“They deserve it before Friday afternoon.”
The next morning, the bank confirmed that it had received the payroll file for processing. That was progress, not proof that every employee had a deposit. Leah asked for another status update and kept the phone beside her as we joined Helena and the operating team.
The independent directors had approved temporary outgoing-payment controls. Daniel remained suspended from CEO duties and barred from directing employees or accessing company systems. The chief operating officer would continue running daily operations under board supervision. Leah would retain finance responsibilities, with added review before vendor payments went out.
I had no part in directing the independent investigation. I could answer questions about my own decisions, and I could help explain the company I had built. I could not decide what the reviewers should find.
Helena insisted on an employee meeting before our presentation to Maya. The notice was brief. It did not name Daniel or repeat the anonymous accusation against me. It said there was an independent review of company payments and an update on operations and payroll.
The conference room filled quickly. Others joined on video. I recognized people who had been with us when we could barely afford a second server, alongside people hired last month who had never met me.
Helena spoke first.
“The board has suspended the CEO pending an independent review. That is an interim action, not a final finding. Our operating leadership and finance team have authority to continue essential work under additional controls.”
She told them the preliminary review had identified approximately $2.4 million in posted payments requiring examination. She explained that the amount was not a final loss figure and did not include a pending transfer the bank had not cleared. Questions about anyone’s conduct, she said, belonged with the independent reviewers.
A hand rose near the back. It belonged to Andre, a customer support lead with two children whose school pictures were taped beside his monitor.
“Will direct deposits hit today?”
Leah took the question.
“The payroll file was submitted, and the bank confirmed receipt. We have funds for this run if ordinary processing continues. I’m waiting for confirmation on the deposits themselves. I won’t tell you they’ve arrived before I know.”
Andre nodded, but he didn’t lower his hand.
“What happens if they don’t?”
“We’ll tell everyone immediately,” Leah said. “We’re monitoring the file with the bank, and the board knows payroll is the first operating priority.”
Another employee asked whether projects would be canceled. Helena said spending on nonessential work was being deferred while the operating team reviewed commitments. Customer work would continue, and managers would discuss any changes with affected teams rather than let people discover them through rumors.
Then a young engineer I knew only as Tessa asked, “How did payments get this far without anyone noticing?”
The room went still.
I could have told her the review would answer that. It was true, but it would not have answered what she was asking me.
“I signed a delegation memo that gave Daniel authority for certain vendor and implementation spending, subject to our usual controls,” I said. “I should have monitored how that authority was used more closely. The reviewers are examining which approvals were valid and what work was done. I can’t give you their conclusions. I can tell you my oversight was not good enough.”
Tessa looked down at the table. Across from her, Andre folded his hands.
“I know an apology doesn’t pay anyone’s bills,” I added. “We’re showing you what we know today, and Leah will update you when the payroll status changes.”
Afterward, several people left without speaking to me. I did not try to stop them. Leah stayed to take questions from managers about invoices and project schedules. I watched her explain the same conditions each time, even when a simpler answer would have made the room feel better.
At noon, the bank reported that the payroll funding debit had posted and the file had moved through its next processing step. Leah sent an employee update stating exactly that. She did not say every receiving bank had credited every account.
We presented the forecast to Maya that afternoon. Helena and the operating team walked through the spending holds and payment controls. Leah showed the cash position with and without expected customer receipts, then pointed out how quickly an additional disputed outflow could change the plan.
Maya stopped her on the preliminary figure.
“Is the $2.4 million your worst-case loss?”
“No,” Leah said. “It’s posted payments flagged for review. Some may have supported actual work; some may not have. We’re checking authorization, deliverables, and any recovery. We can’t give you a defensible final number yet.”
“And the other investors?”
Helena confirmed that the update Maya had requested had gone out, with the estimate and its limits stated together. Nobody had been promised repayment.
Maya turned to me.
“You told your employees about the memo?”
“Yes.”
“You know that gives people a reason to question your judgment.”
“They already have one. They shouldn’t have to learn about it from an anonymous message.”
For a moment she said nothing. Then she asked the operating team how long it could maintain essential service under the reduced budget. Their answers were careful. They identified work they could protect and work they would pause, but no one promised that a delayed customer payment or another disputed transaction would be painless.
Finally, Maya leaned back.
“I’ll maintain my support while the board follows this plan and the review continues,” she said. “Conditional support. I want the forecast updated when the payroll deposits are confirmed, and I want to know promptly if the assumptions change.”
It was not an offer to cover a shortfall. It was time to keep operating and a requirement to keep telling the truth.
I thanked her. After we disconnected, I sat with the empty screen for a minute. Maya had not said she trusted me. I was beginning to understand why that mattered less than giving her figures she could test.
Rebecca’s phone rang before I left.
“Vanessa’s attorney delivered the messages,” she said. “The reviewers are preserving the originals and checking the context. Helena wants you informed, but you are not directing this part of the inquiry.”
I went downstairs, where Helena met me beside Leah’s office. She held a short written summary from the review team.
Messages from Daniel’s number instructed Vanessa to code the party staffing and video work as a client engagement. One told her to use the same business-development description across the entries. They supported what Vanessa had admitted about following his directions; they did not erase her choice to type a description she knew was false.
Another message named a vendor I had never heard of: Briarfield Support LLC. Daniel had told Vanessa to route an “onboarding balance” there and keep it off the reception batch. The reviewers had not established what the balance meant, whether Briarfield had performed work, or who controlled it.
Leah looked up the vendor in the finance system.
“There’s a record,” she said. “I need to see whether there were payments.”
May you like
On her screen, Briarfield’s profile carried an ordinary address, an ordinary description, and a date added months before the party. Nothing in that view told us why Daniel had named it.
Leah clicked **Payment History**.
