# Our Competitor Had an AI That Covered 97.2%. We Had a Spreadsheet and a Fake Quote. Guess Who Won. > Source: > Published: 2026-06-18 15:36:12+00:00 You walk into the RFP briefing. Your competitor has 200 people, 97% AI coverage, and a 4-day delivery promise. You have 15 people and a proposal you haven't even finished writing. Do you bet on better tech, or on understanding people better — and playing dirtier when you have to? This story is your answer. When Finova's RFP landed, everyone in the industry knew how big this was. Cross-border payment system. Multi-currency settlement + compliance + risk. Their last deployment had a P0 incident — an exchange rate module drifted by four decimal places in an edge case, and audit chased it for two months. So Finova's CTO made it clear: **a $1.8M contract, and whoever signs off owns the result.** $1.8M. Enough to keep a small testing company alive for a whole year. Plenty of firms showed up at the briefing. But only two were real contenders. **QualiGuard** — mid-sized, just closed their Series A, 200 people, their own AI testing platform called Aegis. A $1.8M contract was barely a rounding error for them — but with Series A money comes the pressure to show revenue growth for the next round, and Finova was a trophy client in the cross-border payments space. The case study was worth more than the project itself. Derek stood at the podium, flipping through slides packed with numbers: **Aegis delivers 97.2% test automation coverage. Full Finova platform testing in four business days.** No "we'll try." Just "we can do it." **VeriTest** — small, fifteen people. Marcus spent the whole morning working the room with Finova's people. I sat in the back row with nothing. Marcus slid back over and leaned in: "Their PPT makes yours look like a joke." I didn't answer. I was watching Derek's boss. Sarah — QualiGuard's VP, Derek's direct supervisor. She sat in the front row, off to the side, and never once looked at Derek during his entire presentation. She was on her phone. As one of the few women running a technical department, I watched her longer than I watched Derek. When Derek flashed Aegis's coverage curve on screen, Sarah was replying to emails. When Derek said "Aegis is the result of 18 months of R&D, with AI prediction accuracy reaching 82%," Sarah was scrolling something on her phone. When Derek finished and the room applauded, Sarah flipped her phone face-down on the table. She didn't clap. At the coffee break after the briefing, I didn't go talk to Finova's CTO. I went to find Marcus. "Run two people for me." "Who?" "Sarah and Derek from QualiGuard. I need to know their dynamic." Marcus frowned. "Why? We haven't even written a proposal." "Derek just pitched for 40 minutes, and his boss didn't look at him once. Two most likely explanations: either she's heard it a hundred times and can't stand it anymore — **or she's waiting for him to screw up.** " Marcus looked at me. "Lena, which one's worse?" "The second one. Because if she's waiting for him to slip — **we don't need to beat Derek. We just need to put a knife in Sarah's hand — one he won't see coming.**" Marcus nodded. He knows how deep my technical chops go. And he knows my philosophy on dirty work: **when you have the tech, fight clean. When you don't, fight dirty. When you can't win either way, find another path.** He's never doubted my read on things. Derek didn't wait for the submission deadline. He played his hand early. On May 14, QualiGuard sent word through an intermediary to Finova's CTO: "Aegis is already testing your system — first round's on us." Smart move. The first one to deliver always has the advantage — even if what they deliver is half-baked. On May 16, Derek sent Aegis's test report to Finova's technical review team. Subject line: *Finova Full Platform Assessment — Aegis v2.3*. I saw the report on the morning of May 17. When Marcus forwarded it, he expected me to look at the coverage and pass rates first — 97.2% coverage is a knockout punch in any bidding scenario. But I did something Marcus didn't understand. I flipped to the appendix. Not the body of the report. The **system log appendix** — auto-generated timestamps from Aegis, buried in the last three pages. Most people in a bidding scenario only read the summary and conclusions. But I've been doing testing for fifteen years — five of them as CTO before we got acquired. Took the payout, started my own shop, brought Marcus in as partner. And in that time, I've seen too many projects with beautiful reports and disastrous execution. **I never read what people wrote. I only read what they actually ran.** Aegis's logs showed: ``` Test Session: AEG-FINOVA-0512 Status: COMPLETED ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ |Start: 2026-05-12 11:20:03 UTC |End: 2026-05-12 14:32:07 UTC |Duration: 3h 12min 4s ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ |Total Reqs: 2,347 |Passed: 2,312 |Failed: 0 |Skipped: 35 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ |Avg Resp: 47ms |P99 Resp: 189ms |Max Resp: 312ms ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ |External Deps: 0 ``` I stared at "External Deps: 0" and "Avg Resp: 47ms" for a long time. Finova does cross-border payments. Two years ago I consulted for a company with a similar architecture — they had 9 external dependencies, and a single exchange rate API had a P50 response time of 120ms. **Sandbox environment. Expected — all pre-testing runs in sandbox.** I didn't check the coverage. I checked the execution time first. **2,347 test cases in 3 hours and 12 minutes.** I made seven phone calls. The first was to Marcus: "Find out Finova's production environment setup — how many external dependencies do they have?" Twenty minutes later Marcus messaged back: **14 external dependency services. API rate limit at 1,000 requests per minute per account.** I made six more calls. I don't know many people, but the ones I know are in the right places — one former colleague spent two years on Finova's infrastructure team. The sixth call confirmed the key piece: **Finova's production CI pipeline takes at least 24 hours for a full run.** Half of those 14 external dependencies are banking-grade interfaces, each request takes 800ms minimum, and the rate limit kills any parallelism. I laid out the math: ``` Finova production full test — theoretical estimate: 2,347 test cases — split 7:3 external/internal 1,642 external × 800ms avg dependency response = 1,314 seconds (pure dependency wait) + internal execution time (est. 20,000 seconds) ≈ 5.9 hours — assuming zero bottlenecks But API rate limit is 1,000 req/min: External triggers: 1,642 / 1,000 = 1.64 min queueing + real queue time at least 3× estimate → Safe estimate for full run: 24h+ Aegis execution time: 3h 12min ``` I closed my notebook. Derek's test ran in a sandbox. Nothing unusual — all pre-tests run in sandbox. But something else caught my attention. I went back to his proposal. 97.2% coverage, four business days delivery. Finova's production CI takes 24 hours per run. Even if Aegis is faster than traditional CI, four days gives you at most two complete iterations. But testing isn't just about running — you also analyze, fix, and re-run. Four days. Ninety-six hours. Subtract 24 hours for one run — how many iterations can you fit in the remaining 72? I didn't know the answer. But I knew one thing: **if there was even one person on Finova's review team who could do this math, Derek was in trouble.** I picked up my phone. I didn't call Finova. I called Marcus. "Can you still reach that former QualiGuard employee?" "I can. But it'll cost." "How much?" "Five thousand." "Pay it. I don't need technical data — I need the dynamic between Sarah and Derek." Marcus was quiet for two seconds. "Lena, we've got seventy grand left in the account." "I know. Pay it." I knew that five thousand, if I was right about this, **wouldn't buy us a project. It would buy us the cost of putting the knife in Sarah's hand.** May 18. Marcus met a guy named Roy for coffee. Roy was a former senior test engineer at QualiGuard who'd left a month ago — and not on good terms with Sarah's team. Five thousand dollars bought three recordings. Marcus transcribed them and sent them to me. **Recording one: three months ago, Sarah told Derek to cut Aegis's GPU budget.** Sarah: "Aegis costs $31,000 a month in GPU expenses. That's more than a manual testing team. Where's the justification?" Derek: "GPU is the engine of Aegis. Cut GPU, you cut coverage." Sarah: "Then cut coverage. The client is paying for manual testing rates, not GPU cluster rates." **Recording two: two months ago, Sarah cut Aegis's GPU allocation by 50% without Derek's consent.** Derek: "You could have at least told me first." Sarah: "I did. You didn't listen." **Recording three: one month ago, Derek lost it at a team meeting.** Derek: "Sarah doesn't understand the technology. All she reads are spreadsheets. Aegis now takes 40% longer to run a full regression than before. She doesn't know, and she doesn't care. All she cares about is this quarter's P&L." I finished reading the last transcript and put my phone down. "Sarah doesn't get the tech. Derek thinks she's holding him back. Derek needs full regression to prove Aegis works — because cutting test volume is admitting Aegis can't deliver." Marcus asked: "So what do we do?" "So we make Sarah force Derek to do something he's afraid to do." I had Marcus prepare a document. Not a real bid. A document that **looked like a real bid.** The gist: VeriTest planned to bid at $1.3M — 25% below the industry average, more than 20% below QualiGuard's expected price. The proposal looked legit: attachments, technical approach, delivery timelines. The only difference: **this proposal wasn't for Finova. It was for Sarah to see.** I found someone who did business with both companies — not a friend, but reliable for the right price. Had him "accidentally" let the contents of our fake bid slip to Sarah. "You sure Sarah will buy it?" "A manager who only reads spreadsheets, in the middle of bid season, sees a competitor 20% below her price — **she won't question whether it's real. She'll take the number straight to Derek and tell him to match it.**" It played out exactly as I predicted. May 20. Word came through from Roy: **Sarah called Derek into her office for 45 minutes. When he walked out, his bid had changed — from $1.8M to $1.5M.** When I got the news, I didn't smile. "Derek just cut $300K." Marcus was doing the math on his end too. "They were at $1.8M with a 40% margin. Sarah pushed him to $1.5M with a hard floor — margin can't go below 22%." I did the calculation. "Cost ceiling went from $1.08M to $1.17M. He actually has an extra $90K to play with." "And?" "And here's the problem — he's got an extra $90K in cost room, but he lost $300K in revenue. Sarah already cut his GPU once. It's not that he can't afford more compute — **it's that he can't go back to Sarah and say 'you were wrong to cut it, I need it back.' That's slapping his boss in the face** — he won't do it. The bid's due in two days, he's got no time for that fight. His hands are tied. The only path forward is to reduce test volume and let AI fill the gaps." "Switching from full regression to sampling?" Marcus asked. "Exactly. Run fewer real test cases, let the AI extrapolate coverage from historical data. And it's not voluntary — his boss made him cut the price. He doesn't have the guts to say no." I leaned back in my chair. Aegis at full GPU could probably finish a full regression in about 12 hours — based on 2,347 test cases and industry execution benchmarks. Sarah cut his compute by half, pushing it to 17 hours. I opened my laptop and wrote a quick script to simulate Derek's situation: ``` """ Aegis compressed test strategy estimate Based on: Sarah cut 50% GPU → full test slows by 40% → 20% price cut """ full_test = {"cases": 2347, "time_hours": 12, "coverage": 0.972} # Aegis full GPU baseline (QualiGuard internal env) gpu_cut = {"time_hours": full_test["time_hours"] * 1.4} sample_rate = 0.40 ai_prediction_accuracy = 0.82 actual_coverage = ( sample_rate * full_test["coverage"] + (1 - sample_rate) * full_test["coverage"] * ai_prediction_accuracy ) print(f"Claimed coverage: 97.2%") print(f"Actual effective coverage: {actual_coverage*100:.1f}%") print(f"Gap: {(full_test['coverage'] - actual_coverage)*100:.1f} percentage points") print(f"This gap in a financial system = P0") ``` "So now Derek's test plan is: **run 40% of the real cases, let the AI extrapolate the remaining 60%** of coverage. And he can't tell anyone — because admitting it means admitting Aegis can't deliver what it promised." "Is Derek going to lose?" "No. On paper, his plan still looks good — sampling plus AI prediction is a legitimate approach. The problem isn't the plan itself." "Then what is it?" "The problem is he won't tell the client he's using sampling. He'll call it 'full regression.' **And the moment he says 'full' — we've got something to cut open.**" On May 23, Finova's procurement office officially received both bids. **QualiGuard proposal summary:** | Item | Detail | |---|---| | Price | $1,500,000 | | Testing method | Aegis fully automated | | Delivery timeline | 4 business days | | Coverage guarantee | ≥ 95% (line level) | | Proof point | Aegis pre-test report (attached) | **VeriTest proposal summary:** | Item | Detail | |---|---| | Price | $1,275,000 | | Testing method | Manual + AI hybrid | | Delivery timeline | 14 business days | | Coverage guarantee | ≥ 90% (line level) | | Pre-test | None | The comparison was clear. QualiGuard at $1.5M — $225K more than VeriTest, but only about 18% higher. Factor in delivery speed (4 days vs 14) and technical capability (97% automated vs hybrid), and Finova's CTO James was leaning toward QualiGuard. On May 27, internal scores leaked — QualiGuard technical score 86, VeriTest 72. Derek posted on LinkedIn: "Technology is not about who has more people. It's about who has the right tools. Proud of the Aegis team. Looking forward to Finova's next chapter." Forty-plus likes underneath. When Derek posted that — I could tell, he genuinely believed it. His problem wasn't that his technology was bad. It was that he trusted it too much to see his own boss sharpening the blade. At the same time, I was running my own Aegis behavior analysis on my laptop. I couldn't use Aegis — but I could reverse-engineer its logic. Derek's public materials mentioned Aegis's core architecture: a coverage-driven reinforcement learning selection strategy. In other words, Aegis doesn't write test cases — it selects them. It picks the subset of the test asset library that contributes the most to coverage. I did the math: ``` Aegis selection strategy (based on public materials): Full test asset library estimate: for a Finova-scale system ≈ 8,000-12,000 cases Aegis report ran: 2,347 → Selection ratio ≈ 20%-25%, reasonable If Derek runs sampling + AI prediction: Actual execution ≈ 40% × 2,347 ≈ 940 cases AI-predicted coverage ≈ 60% → Real coverage ≈ 40% × 97.2% + 60% × expected value The problem isn't coverage percentage. It's AI prediction accuracy — Derek mentioned at the briefing that Aegis's prediction accuracy is 82%. 82% fill accuracy covering 60% of the gap: Real composite coverage ≈ 40% × 97.2% + 60% × (97.2% × 0.82) ≈ 38.9% + 47.8% = 86.7% 10.5 percentage points below what's reported. In a financial system, that's a P0. ``` I didn't share this calculation with anyone. But I knew one thing: after Sarah squeezed Derek's budget, his plan had a technical hole. Frank didn't need to find it — I could have cut straight through it myself. But I didn't. Not because I couldn't. Because having someone else land the blow was cleaner than doing it myself. "You're not worried at all?" Marcus asked. "About what?" "The scores. We're 14 points behind." "Scoring is scoring. The review meeting is the review meeting." "What's the difference?" "Scoring is one CTO closing his office door. The review meeting is three departments sitting around a table. The CTO can have his favorites — but the CFO and the head of risk aren't going to take a bullet for his ego. Derek still doesn't realize his biggest problem isn't our proposal." "Then what is it?" "**His biggest problem is his boss wants him to lose more than he wants to win.** " Finova's bid review meeting was scheduled for the afternoon of May 29. Six people in the room. CTO James, CFO Mark, risk lead Frank, plus two technical reviewers and procurement. QualiGuard presented first. Derek was in a suit, tie perfectly knotted. His team had put together 40 slides — from Aegis's architecture diagram to heat maps of Finova's test coverage, every number backed by data. He spoke for 35 minutes. Then he dropped the pre-test results: **2,347 test cases. 97.2% coverage. 3 hours 12 minutes. Zero failures.** James nodded. Then came Q&A. Frank — the risk lead, mid-forties. Started as a developer, moved to architecture, then to risk. Twelve years at Finova. He was the one who spent two months auditing the last P0 incident. He flipped open his notebook. "Derek, your proposal says four business days delivery, 97.2% coverage. What's that number based on?" Derek clearly hadn't expected the first question to go there. "—Based on Aegis's test data from the Finova environment. 2,347 test cases. Full regression." Frank turned another page. "I've read your Aegis test logs — execution time was 3 hours 12 minutes. Finova's production CI full run is typically 24 hours or more, that's not a secret. But that's not what I'm curious about." He closed his notebook. "What I'm curious about is — your proposal guarantees delivery in 4 days. 4 days is 96 hours. If a full run takes 24 hours, you've got 72 hours left for analysis, fixes, and re-runs. That's tight — but it works if you're running full regression." He looked at Derek. "Here's the problem — Finova's cross-currency settlement module alone, our own CI pipeline runs it in 16 to 18 hours. Everyone in the industry knows that scale. Your Aegis logs show 3 hours 12 minutes per run — that's from **our sandbox environment**, not Finova's production environment. At 17 hours per real iteration, in a 4-day window — how many iterations are you planning to run?" Derek didn't answer immediately. Twenty seconds of silence. "—Our test strategy is determined by Aegis's automated selection mechanism. Coverage is above 97%." "I didn't ask about coverage," Frank said. "**I asked — 4-day delivery, how many iterations are you planning to run?**" Derek didn't answer. Because the answer was one he couldn't say. Frank didn't push further. He closed his notebook and wrote something down. For the remaining 10 minutes Derek spoke, Sarah never looked at him. VeriTest's presentation came after. I stood up. No slides. Just a PDF and a laptop connected to Finova's network. I spoke for 20 minutes. I didn't talk about how good our proposal was. I talked about Finova's architectural vulnerabilities — not as an attack on QualiGuard, but as a technical analysis. "Finova's cross-border payment system has three critical bottlenecks. Multi-currency exchange rate settlement consistency — that's where your last P0 happened. Risk engine rule hot reload — you can't validate this in a test environment, it needs a production canary. Third is the stability chain of your 14 external dependencies — third-party interfaces are uncontrollable, so you need circuit breakers as a safety net." James raised an eyebrow. These weren't blind spots for him — but he hadn't expected someone to tear into Finova's system this deep in 20 minutes. "**Our proposal isn't designed to cover 97% of your code. It's designed to cover your three biggest risks. Code coverage is a means. Business correctness is the goal.**" I didn't pile on Frank's questioning. I didn't need to. Every point Frank had made was already sitting in that room — hitting ten times harder coming from him than it ever would from me. But I landed another blow. "Our delivery timeline is 14 days. That's because we need the first 5 days to do one thing — run a full-chain probe test on production, in a canary deployment. Not for coverage assessment. Just for external dependency health checks and circuit breaker validation. This step can't be skipped. Whoever wins this bid, I'd recommend Finova do this before any new testing begins." James nodded. It sounded like I was looking out for Finova. And I was. But I also knew — saying this out loud meant making it clear that **QualiGuard's 4-day delivery physically couldn't include this step.** **I didn't name names. Everyone knew who I was talking about.** During the mid-meeting break, I saw something in the hallway. Sarah pulled Derek into a stairwell. They talked for less than two minutes. Derek turned and walked away. Sarah didn't follow. I pieced it together later from context — she gave him an out. A chance to voluntarily withdraw the delivery commitment from his proposal during the re-convened session, admit the mistake, let the company handle it internally. He didn't take it. When the meeting reconvened, QualiGuard was asked to give a supplemental statement. Before Sarah stood up, she closed her eyes for a split second. A tiny gesture, barely noticeable. Most people wouldn't have seen it. But I did — and it wasn't nerves. It was her confirming a decision she'd already made. She cleared her throat. She said three things: "QualiGuard's proposal regarding delivery timeline was based on Derek's personal technical assessment and had not gone through management review. We sincerely apologize for this. There is a discrepancy between our resource planning and the delivery commitment made. If Finova selects QualiGuard, we will submit a revised delivery plan led by a new technical lead. We have already initiated an internal remediation — the new delivery plan will be submitted to the review committee within 48 hours." The room went quiet for about five seconds. James's expression didn't change. Frank wrote something down. Derek didn't stand up to fight it. His face was calm — the kind of calm that isn't real peace, just the stillness of someone who knows there's nothing left they can do. I sat across the room and watched. I gave Sarah a score in my head: **Clean cut. No hesitation, no wasted motion, not a single unnecessary word. Cut clean.** **A good VP, when a project goes sideways, has only two options — save the project or save yourself. Sarah chose the latter.** She wasn't going to let Derek's technical decisions damage her professional reputation. Even if the decision itself wasn't malicious — running a pre-test in a sandbox, the data was real, nothing was fabricated. But he told the review committee it was "full regression." That's what killed him. At the moment a client is questioning your credibility, facts don't matter anymore. What matters is who can be thrown overboard. Derek was thrown overboard. **Not because his solution was bad. Because Sarah needed someone to throw overboard.** After the meeting, I ran into Derek in the parking lot. He was leaning against his car door, loosening his tie. He stopped when he saw me. Derek spoke first. "That bid — I cornered Sarah after the meeting and asked where she heard it. An intermediary. You leaked it." I didn't say anything. "You set me up. Made sure my boss saw your lowball number. You knew she'd squeeze me." "I didn't know she'd squeeze you." "Then what did you know?" "I knew that once you saw that number in her hands, you'd try to prove you were better than us. How she'd react was her business. How **you'd** react — I had a pretty good read on that." Derek let out a laugh. Not the amused kind. "That arithmetic Frank did in the meeting — you'd already calculated the 4 days don't add up. You waited for someone else to take the shot. That's cold." I said: "I never claimed I played clean." Derek pressed: "So you think you're cleaner than me?" "I'm not comparing who's cleaner." I looked at him. "**I only care about winning. And right now, I'm winning.** " Derek looked at me. Silent for a moment. "Let me ask you something." "Go ahead." "How did you know Frank would ask that question?" "I didn't." "Then —" "I didn't know he would. But I knew your 4-day promise — anyone who divides 96 hours by 17 hours can see it doesn't work. I bet that someone on Finova's review team could do basic arithmetic. I was right." Derek yanked off his tie. "Next time you want to leak a fake bid, find someone else. Whoever you used — doesn't matter, that kind of play doesn't cost much. Five thousand, eight thousand — it's your style. You've got enough left in the account for another round?" I paused mid-step getting into my car. I turned back and looked at him. "Derek." "What?" "Next time you put together a proposal — make sure your boss knows what you're doing out there." I closed the door and drove off before he could answer. Finova chose VeriTest. Not because our testing was better. Because QualiGuard's delivery timeline literally didn't add up — Finova's internal review classified it as "material omission in the bid proposal." Frank wrote in his review report: **"Recommendation: do not select QualiGuard — without confirmation of delivery capability, contract performance risk cannot be assessed."** Sarah saved herself without giving Derek a second thought. But more importantly — those three sentences she said at the meeting, someone repeated them. Inside QualiGuard, word spread fast. Derek's situation inside the company was worse than losing the bid itself. VeriTest got the contract. $1.275M. Marcus was already calculating how long that would keep us alive. June 2. The celebration dinner was at a steakhouse. After three glasses of whiskey, Marcus finally asked the question he'd been holding onto. "That fake bid — how did you know Sarah would take it to Derek?" "A manager who only reads spreadsheets, in bid season, sees a number 20% below hers — she's not going to verify it. She's going to take it to Derek and tell him to match it. The exact number doesn't matter to her. What matters is 'theirs is lower than ours.' " "What if he didn't cut?" "He would have. Because his boss Sarah has been after him for three months. Losing the bid costs him one project. Losing to Sarah — that's not just losing a project anymore. He can't approve a budget, he can't lead his team. That's everything." Marcus cut a piece of steak but didn't eat it right away. "One more thing. Your fake bid was $1.3M. Our real bid was $1.275M — only $25K apart. What if Sarah checked?" "She wouldn't. Because she doesn't care about the number itself. She cares about the words 'lower than us.' $1.3M or $1.275M — to her, same thing. Both are 'lower.' " Marcus raised his fourth glass. "To QualiGuard's VP." "To Sarah." "You think she knows she was set up?" I chewed my steak before answering. "She knows. And she doesn't care. Because she walked away clean. That's what smart people do." Outside the window, the financial district lights were coming on. Somewhere out there was Finova's building. I looked at the lights and said something I hadn't planned. "Guess where Derek is right now." "Home. Or cleaning out his desk." "No. He's updating his resume." "You sure?" "He's not the type to quit. He didn't lose on the technology — he lost because his boss stabbed him in the back. Guys like that don't accept it. He'll find another company. Somewhere without a Sarah." "Will he change?" "No. Because what beat him wasn't the tech. It was office politics. He thought this was a technical competition — but it was about people the whole time. AI is a tool. Code is a tool. Test reports are a tool. **Tools don't decide who wins. The people holding them do.** " Marcus checked his watch. "And our AI?" "We use it too. But we know it's just a tool. The difference is — we never told the client AI could replace people. We said AI helps people test, people make the decisions. Derek lost because he promised something he couldn't deliver. **AI can hit 97% coverage. But AI doesn't know what it doesn't know. People do. So people make the decisions, AI does the execution. He got the order backwards.**" A month later. I saw Derek's update on LinkedIn. New profile picture. New company — healthcare information systems. Same title: Director of Testing. A row of congratulations comments underneath. I scrolled past that post and stopped. That day on the podium, when he said "we can do it" — he really believed it. Not the kind of belief that's pretending. The kind where you fool yourself. Aegis didn't lie to him. Sarah didn't either. **He lied to himself.** I clicked like. As I hit that button, I wasn't sure if I was saluting him or the version of myself that almost became him. I put down the mouse and remembered that day at the briefing, sitting in the back row with nothing. **It wasn't AI that lost. It was people who thought technology could beat politics.** **Your company has been through a bidding war too, hasn't it?** **Did you lose on the technology, or did you lose in the office politics?** **Did winning come from having better AI — or knowing when to hand someone the knife?** **Next time you're in that review room — are you Lena, or are you Derek?** *His AI ran on a GPU cluster. Mine ran on a laptop with a broken cooling fan and café Wi-Fi. Still running. Buy me a coffee ☕* *This is Chapter 15 of AI, Ego & Regret — and the final chapter. From the first story to this one, every comment, every share, every late-night message you left has been the fuel that kept me going through all 15 stories. Thank you. I couldn't have done this without you.* *This series is taking a break for now. I'll post a separate retrospective on all 15 stories. A new series is already taking shape — different format, same rawness.* Disclosure: Written with AI assistance (per community guidelines)