Stratagems #11: Lena Watched Her Own AI Platform Get Cut. An Ember Stayed.

Better to sacrifice a part to preserve the whole.
— The 36 Stratagems, Sacrifice the Plum Tree to Preserve the Peach Tree

Previously on this series: #10: Lena Watched a Team Adopt Her AI Template. Leo Didn't Know the Knife Was in the Contract. — Lena joined CoreStack as a consultant to help Leo build his reporting system. He thought she was there to help. Five weeks later, he realized the contract he signed wasn't just a template renewal — six months of data baselines were already locked inside the VeriTest framework.

Meanwhile, the CoreStack consulting engagement was still running, and VeriTest's internal AI evaluation platform had already gone live — but today, Lena was dealing with her own company's business.

Marcus Reed walked into the office and set the folder on Lena's desk. The cover read "VeriTest AI Evaluation Platform · Q3 Review."

"The board wants an answer," he said. "Three directors asked me separately."

Lena didn't reach for the folder. She already knew what was inside.

"I'll have a proposal by Tuesday."

Marcus paused at the door. He didn't turn around. The door closed a little softer than usual.

Lena looked at the folder cover. The AI Evaluation Platform — the project she'd staked her credibility on in front of the board. Last year, she'd told them: "The future of consulting is AI-powered assessment. We need to build this capability ourselves."

The board approved it.

Twelve months later, the platform was running. The demo looked great. VPs loved showing it off when clients visited. But Lena knew what the directors were really asking — not "Is this platform good?" but "How much did this thing make?"

She didn't have an answer.

She opened the folder.

The Numbers

Lena spent two days pulling data. During the day, she had Leo's QBR at CoreStack to get through. At night, she switched over to VeriTest's own financials.

She broke VeriTest's product lines apart and ran the numbers on each one.

The last row made her stop writing.

She pulled up the platform's admin dashboard:

Active users (last 30d):    12
Internal users:               7
External users:               5
Monthly inference cost:    $15K
Q3 platform revenue:       $22K

She closed the tab. The numbers didn't need explaining. Of those 12 active users, most were automated evaluation engine requests — not human interaction.

The methodology system — she'd always known it existed, and she'd always known it was underfunded. VeriTest's senior consultants had built their own delivery framework over the years: assessment templates, risk checklists, industry benchmarking databases, historical case references. New consultant ramp time, delivery quality consistency, client renewal rates — all of it rested on this system.

But it had no product form. No UI. No demo. No sales pitch. Nobody had ever mentioned it at a board meeting — because the board didn't know it existed.

It had been limping along on a marginal budget the whole time. Maintained by a semi-retired senior consultant, two half-days a week, $9K a quarter.

Lena compared the two sides.

$200K in, $22K out. An 89% negative margin.

$9K in, supporting $3M annualized delivery — renewal rates seventeen points above industry — and not a single director knew its name.

She stared at the notebook for a long time.

She already knew the answer. But she didn't close the notebook.

She knew what she was about to recommend — and this time, she wasn't cutting someone else's feature for a client. This time, she was cutting down what she'd built herself.

She picked up the pen. The signature box sat at the bottom right of the proposal's first page.

She didn't sign.

For a second, she ran through tomorrow's conversation with the platform's tech lead — the engineer who'd built this thing from zero with her, pulled all-nighters tuning models, spent weekends fixing pipelines. He wasn't the type to go back to delivery work. She knew where he'd end up after that talk.

She signed. The pen hit the table louder than the numbers ever did.

She didn't look at the signature again. Closed the folder. The sound carried in the empty office, louder than usual.

The Pitch

Lena walked into Marcus's office. The proposal sat face-down on the table.

"You read it?"

Marcus flipped it open. Two pages in, he stopped on the third.

"You're shutting down the AI platform?"

"Not shutting down. Stopping it as a standalone operation. Embedding the capability back into the delivery lines."

"Is there a difference?"

"The difference is — shut it down, the team scatters, the tech assets rot on the server. Embed it back, and we can pull it out again in three years if we need it. We just stop running it as its own product team."

Marcus closed the proposal. Said nothing.

"Aren't you curious why?"

"I don't need to see your numbers twice," he said. "What's the headcount plan?"

"Five back to delivery. Two stay on core engine maintenance. One — I'll talk to him."

"Who?"

"The platform tech lead. He won't go back to delivery."

Marcus nodded. "You talking to him, or me?"

"I'll do it."

Checkmate

The boardroom was quieter than usual.

Lena's proposal was only four pages. Page one: the AI platform's cost-revenue curve. Page two: the methodology system's coverage and actual support scope. Page three: the integration plan — core engine embedded into delivery lines, independent product team dissolved, $67K/month in redirected spend — $54K to methodology upgrades, $13K to cover core engine maintenance and operations. Page four: the execution timeline.

She turned to page one and started.

The AI platform's numbers. Twelve months of cumulative cost. The client conversion funnel. She'd memorized every figure.

"My recommendation: stop the AI platform's independent product operations. Integrate its core capabilities into the consulting delivery system. Redirect the freed resources into systematic methodology development."

A director spoke. "You pitched this platform last year."

"I did."

"You said it was VeriTest's future competitiveness."

"I meant it then," Lena said. "And I mean it now. But the path to that competitiveness isn't burning three years of runway on a standalone product team waiting for it to break even. It should live inside our delivery capability first, funded by client revenue, not investor patience."

Another director flipped through the proposal. "The methodology system — we haven't paid attention to this before. Can it hold?"

Lena glanced at Marcus. He didn't speak.

"It's been holding for four years," Lena said. "On $9K a quarter. It just never made it to the boardroom."

A pause.

"Lena."

The one who spoke was the director who'd been quiet the entire meeting — the oldest, sitting at the far end of the table.

"Last year you convinced us to fund this platform. Now you're convincing us to kill it. How do I know you won't be back in six months telling us to kill the methodology too?"

Lena held his gaze.

"Because I won't."

"You said the same thing last year."

"Last year I meant it. I mean it now too. The difference is — **last year I told you what I believed. This year I'm telling you what I saw. "**

The director watched her for a moment. Didn't push further.

The room was silent for a few seconds.

The directors exchanged glances. No vote. No formal decision. One director said "Proceed as recommended," and nobody objected.

Lena gathered her papers and walked out.

In the hallway, Marcus caught up.

"The board didn't say thank you."

"I don't need them to."

She walked into her office, closed the door, and sat down.

She opened the notebook to the project charter — the first line read "VeriTest AI Evaluation Platform · Initiation · Proposed by Lena." She looked at it for ten seconds. Closed it.

She never opened that folder again.

Aftermath

Ninety days later.

The AI platform team had gone from eight people to two — the core engine maintenance crew. The original five had been redistributed across the delivery lines. The evaluation models accumulated on the platform had been packaged into modules and embedded into the standard due diligence workflow. Clients no longer saw "AI Assessment" as a product name — but the deliverables now had an extra page of automated analysis. Nobody noticed that page had once been the core output of the now-defunct platform.

The methodology upgrades moved in two directions: the delivery knowledge base expanded from 40 cases to 120. New consultant ramp time dropped from ten weeks to seven.

The real validation came quietly.

Lena read a record during the quarterly delivery review —

Thursday afternoon, a junior consultant in his third month, preparing a client due diligence report, pulled up a historical case from the knowledge base. A similar architecture migration project six years ago — the same risk pattern hadn't surfaced until the fourth month after deployment, costing the client $200K. In the risk assessment section, he'd added a citation line: "See VeriTest Delivery Case Library #47."

As far as the records showed, nobody noticed the citation — not the client, not the project manager, not management.

But VeriTest's renewal rate had ticked up 1.2 points this quarter.

Nobody knew where that 1.2% came from. Lena did.

Lena went to the kickoff with Marcus. The fintech client's tech lead wasn't a talker — he exchanged pleasantries and opened VeriTest's due diligence report immediately.

"Your report goes way deeper than the other two," he said, flipping to the risk assessment page. "You flagged a similar case from six years ago — the other two firms didn't do that. Only yours did."

Lena nodded. Didn't respond.

Marcus glanced at her. He didn't say anything either — but she recognized that look. It was the same case, used in two different reports. But sitting in that room, she was the only one who knew the truth: that case was in the report because the methodology budget had been approved — funded by her own platform that she'd cut.

Lena was at Third Cup when Marcus's message came through.

"Q4 methodology budget approved. At your numbers."

She typed back:

"Don't tell me. Tell the team."

Marcus replied with one word:

"Done."

Lena took a sip of her coffee. It was cold.

She glanced at her phone. The lock screen was still a screenshot of the AI platform's launch page from the day it went live the year before.

Someone behind the counter brought a fresh cup over. Didn't ask what she wanted — he just put the right one down.

"Switch?"

"No. This is fine."

She took a sip. The coffee was cold. She didn't put the cup down.

She never changed the lock screen. Not because she forgot. Because she wanted to keep it.

This is what Sacrifice the Plum Tree to Preserve the Peach Tree means — not giving up, but cutting down what you built yourself, so the pieces can keep something more important alive.

🤖 AI Post-Mortem

[36 Stratagems Tactical Database v3.1] Loaded
[Tactic Match] Sacrifice the Plum Tree to Preserve the Peach Tree
[Analysis Mode] Full-field scan
━━━━━━━━━━━━━━━━━━━━
Tactic Match: ~91%
Operator: Lena
Action: Recommended dissolution of own AI platform project, redirected budget to consulting delivery methodology
Objective: Trade a visible initiative for an invisible but critical capability
Result: $67K/mo redirected. Delivery knowledge base: 40→120 cases. Ramp time: 10→7 weeks.
Renewal rate: +1.2pp (quarter)

Decision Evaluation:
  - Target: Board's AI platform ROI concern
  - Sacrifice: AI Evaluation Platform (Lena's own project, 12 months in production)
  - Keeper: Consulting Delivery Methodology & Knowledge Base ($9K/qtr, zero board visibility)
  - Net: -6 FTE, +$54K/mo for methodology, $13K/mo retained for platform maintenance.

Risk Assessment:
  Personal cost: High. Ownership on record. Board questioned the reversal.
  Institutional cost: Low. Team redistributed. Technology preserved.
  Reputation cost: Medium. First reversal in VeriTest tenure.

Core Insight: The hardest sacrifice is the one you volunteer before anyone asks you to.

Next stratagem: Borrow a Corpse to Return the Soul

P.S. English isn't my first language. I use AI to polish the writing and smooth out the rough edges. Thanks for reading. ☕ Buy me a coffee