The Earnings Call
A SaaS CEO rehearses the quarterly earnings call that will explain why their stock dropped 40% in a week. The AI assistant helping them prepare the talking points is, ironically, the same technology that caused the problem.
The script said partnership.
Derek Huang, CEO and co-founder of LegalPulse, read the word for the fourth time on the teleprompter his communications team had set up in the small conference room adjacent to his corner office. The teleprompter was new. In twelve years of quarterly earnings calls, he had never needed one. He had always spoken from notes, with the easy confidence of a man whose company had grown 40% year over year since Series A.
The teleprompter said: We view the emergence of AI-native legal tools not as a threat, but as a partnership opportunity that validates the category we pioneered.
Derek said the words out loud. They tasted like chalk.
"That's good," said Priya Chandra, VP of Communications, from the couch in the corner. She had her laptop open and was editing the deck in real time. "But try to smile when you say 'partnership.' Last time you said it, you looked like you were passing a kidney stone."
"I don't want to say partnership."
"What do you want to say?"
"I want to say that a company founded eighteen months ago just wiped out forty percent of our market cap by releasing a plugin."
Priya closed her laptop. "I have that version too. It's in the folder labeled 'Do Not Under Any Circumstances.'"
The plugin had launched on a Thursday. A Thursday. Not even a Monday, when you could blame it on weekly sector rotation. Not a Friday, when markets were thin and movements got amplified. A regular Thursday at 9:00 AM Pacific, announced via a blog post with the kind of understated design that Silicon Valley uses when it wants you to know it isn't trying too hard.
Introducing Claude Cowork for Legal.
Derek had read the blog post in his Tesla in the parking garage, engine off, climate control humming, while his 9:30 all-hands waited upstairs. He had read it once quickly, then again slowly, and then a third time with the clinical detachment of a cardiologist examining his own ECG and finding an irregularity.
Contract review. Case law research. Compliance analysis. Document drafting. Regulatory filing assistance. Client memo generation.
Six capabilities. Six bullet points. Six revenue streams that comprised, collectively, 78% of LegalPulse's annual recurring revenue.
By the time he reached the all-hands, his stock was down 6%. By lunch, 11%. By the closing bell, the number was 19.4%, and the Slack channel titled #leadership-war-room had 847 unread messages, all of which he could summarize without reading: What do we do?
"The analysts are going to ask about churn," said Marcus Webb, CFO, during the dress rehearsal that evening. Marcus had the projections on his iPad and the expression of a man who wished he had taken that offer from Stripe in 2024. "We need a number."
"We don't have a number," Derek said. "The quarter doesn't close for three weeks."
"They'll ask anyway."
"Then I'll say we're not providing updated guidance at this time."
"That's code for 'it's bad,'" Marcus said. "Everyone knows that's code for 'it's bad.'"
"What if I say we're seeing some near-term volatility in new pipeline as customers evaluate the competitive landscape?"
Marcus considered this. "That's code for 'it's very bad.'"
"What if I just scream into the phone for forty-five seconds?"
"That would actually be more honest."
Priya, who had been typing furiously, looked up. "I have something. What if we announce the AI partnership?"
Derek stared at her.
"The one with--" she checked her notes-- "the AI company we signed the LOI with last week. The integration deal."
"We signed that LOI because our stock cratered and we were desperate to put out a press release with the word 'AI' in it."
"Yes. But on the call, it sounds proactive."
"It sounds reactive."
"Everything sounds reactive after your stock drops forty percent in a week, Derek. The question is whether it sounds reactive and competent, or reactive and flailing."
The irony that Derek could not escape, the one that kept him up at 3:00 AM while his wife slept and his Apple Watch gently suggested he try a breathing exercise, was that he was using the exact technology that was killing his company to prepare for the call about the fact that the technology was killing his company.
He had Claude open in a browser tab. He had been using it for months. The whole company used it. The legal team used it to draft internal contracts. The marketing team used it for press releases. The finance team used it for scenario modeling. He personally used it to workshop talking points, including, at this very moment, the talking points he would use to explain why Claude was an existential threat.
He had typed: Help me draft responses to analyst questions about competitive pressure from AI-native legal tools.
And it had responded, helpfully and thoroughly, with exactly the kinds of measured, diplomatic responses that a CEO in his position would need. It even suggested he "acknowledge the disruption transparently while pivoting to LegalPulse's proprietary data advantages."
It was like asking the wolf to help you explain to the sheep why the fence was down.
The call was scheduled for 4:30 PM Eastern. At 4:15, Derek sat in the conference room with the teleprompter and a glass of water he would not drink. Priya sat to his left with the deck. Marcus sat to his right with the financials. The investor relations team was on standby in the adjacent room, monitoring the webcast.
"Remember," Priya said. "If someone asks about LegalPulse Labs, pivot to enterprise data moats."
"If someone asks about pipeline," Marcus said, "say 'secular trends.'"
"If someone asks if I've tried Claude Cowork for Legal," Derek said, "what do I say?"
There was a silence.
"Have you?" Priya asked.
"Of course I have. It's good. It's really good. It did in forty-five seconds what takes our platform six minutes. It doesn't hallucinate on contract clauses the way it used to. The case law citations are accurate. It understands context. It remembers previous conversations. It's--"
He stopped. Marcus was staring at him with an expression that suggested this was not the pre-call energy they were going for.
"It has limitations," Derek said. "Significant limitations. In regulated environments."
"There you go," Priya said. "That's the answer."
The call lasted fifty-seven minutes. Derek said partnership nine times, innovation fourteen times, proprietary data moat six times, and we remain confident four times. He did not say I use it every day and it's better than our product even once, which Priya later told him showed excellent message discipline.
The stock closed the next day down another 3%.
At 11:00 PM, sitting in his home office with the lights off, Derek opened Claude and typed: What would you do if you were the CEO of a legal tech SaaS company that was being disrupted by your product?
The response was long and thoughtful and offered seven strategic options, ranging from "pivot to AI-powered premium tier" to "explore acquisition by larger platform company." The seventh option was "accept that the current business model has a limited remaining runway and begin planning an orderly transition."
Derek read option seven three times. Then he closed the laptop, opened a bottle of the Yamazaki 18 he kept in the credenza for celebrations, and poured himself a glass for something that was not, by any reasonable definition, a celebration.
The whiskey was excellent. The irony was better.
On Monday morning, Derek arrived at the office to find the entire legal team gathered in the large conference room. They had printed out a competitive analysis. Forty-two pages. Detailed feature comparisons between LegalPulse and Claude Cowork for Legal, with red-yellow-green scoring across nineteen capability categories.
LegalPulse was red in eleven of them.
"We compiled this over the weekend," said Jessica Torres, VP of Product, with the determined cheerfulness of someone who had not slept. "The good news is we're still ahead in three areas: bulk document processing, enterprise SSO integration, and audit trail compliance."
Derek looked at the three green columns surrounded by a sea of red.
"Jessica."
"Yes?"
"Who helped you make this analysis?"
Jessica hesitated. "Claude."
Derek nodded. He sat down, opened his laptop, and typed: Draft a board memo proposing a strategic review of all options including potential sale of the company.
Forty-five seconds later, the memo was done. It was, he had to admit, quite good.