YT YouTube2Text

YouTube2Text → Transcripts → After a Decade, They Let Me Go—I Shut Down the Software That Earned Them Millions

After a Decade, They Let Me Go—I Shut Down the Software That Earned Them Millions — Transcript

by Cold Revenge · 8,008 words · 1,329 segments · language en · Watch on YouTube

Open in transcriber Summarize with AI Download SRT/VTT

Full transcript

0:00Nathan called me into the boardroom with
0:02Christine from HR. Your position is
0:04being restructured, he said avoiding my
0:07eyes. Effective in 2 weeks, your role
0:10will be consolidated under Bryant's
0:12leadership. Bryant, the 32-year-old from
0:15a failed startup who once asked me what
0:17database normalization was, was now in
0:19charge of the entire platform I'd built
0:21from scratch. They appreciate your
0:23contributions, Christine added
0:25robotically. Bryant brings a fresh
0:28perspective. Translation, younger,
0:31cheaper, male. When I asked what came
0:33after the transition, she paused too
0:35long. We're exploring options, but can't
0:38guarantee anything. Translation, start
0:41job hunting. If you're new here and
0:43enjoying these powerful stories, make
0:45sure to hit that subscribe button and
0:47stay tuned for more. Let me know in the
0:49comments what part of today's story
0:51touched you most. I walked back to my
0:53desk in silence. Everyone looked away.
0:56At my station, I pulled up my original
0:58employment contract. The one I'd paid a
1:01lawyer to review when I joined 12 years
1:03ago. Section 9, all software systems and
1:06code developed by employee shall remain
1:08the intellectual property of employee.
1:11Company is granted a non-exclusive,
1:13royalty-free license, which terminates
1:15automatically upon termination of
1:17employment unless due to documented
1:20performance issues. I owned everything.
1:23Every line of code. Every system running
1:25their $200 million a year business. And
1:28for 12 years, I'd filed copyright
1:30registrations. Every module, every major
1:33update. The latest renewal, 6 weeks ago.
1:37Call my sister. They're pushing me out,
1:40I said. I need to talk to Alex. That
1:43night, over dinner, I showed my
1:44brother-in-law, the employment attorney,
1:47my contract and records. He read Section
1:509, then looked up. You own it. All of
1:53it. Then what do I do? He smiled. Let
1:56them fire you. Then we send a cease and
1:59desist the minute your employment ends.
2:01We sat at my sister's dining table,
2:04normally for celebrations, now a war
2:06room. I walked Alex through my contract,
2:08the IP clause, and 12 years of copyright
2:11registrations. His expression sharpened.
2:14You own it, he said. All of it. The
2:17contract only gave them a license, I
2:20clarified. Which terminates if they fire
2:22you without cause. He tapped his pen.
2:25Any performance issues on record?
2:28Nothing. My last three reviews said,
2:30"Exceeds expectations." They even gave
2:33me a raise 8 months ago.
2:35Then this is termination without cause.
2:38He leaned back. How dependent are they
2:40on your systems? Completely. Without
2:43them, they shut down in 6 hours. Lydia
2:46whistled. And they're handing it all to
2:48some kid who doesn't know what database
2:50normalization is? That's the plan. Alex
2:53stood. Here's what we do. You stay
2:56professional for the next 2 weeks.
2:58Document what they ask, be flawless.
3:00Meanwhile, I'll draft a cease and
3:02desist. The second your employment ends,
3:04we send it. They lose access to
3:07everything.
3:08They'll fight it. Let them. The contract
3:11is clear. Your registrations are
3:13current. They'll have to negotiate.
3:16What should I ask for? He smiled.
3:19Whatever they're desperate enough to
3:20pay. The next 2 weeks were surreal.
3:23Brian shadowed me but absorbed little,
3:26fixated on modernizing the platform.
3:29"Wouldn't it be better to rebuild?" he
3:30asked. "That old code handles $200
3:33million a year at 99.9%
3:36uptime," I said. "Rebuilding would take
3:393 years with 10 senior devs, and even
3:41then you'd miss undocumented edge cases
3:44baked into the logic."
3:45He frowned. "Nathan said you'd document
3:48everything." "I document architecture,
3:51not 12 years of institutional knowledge.
3:54That doesn't fit in 2 weeks.
3:56"Well, we'll figure it out." he said,
3:58confidently cluelessly. On my last day,
4:01they held a perfunctory goodbye lunch.
4:03Nathan praised my contributions.
4:06Christine handed me a severance packet
4:08and a non-compete. "I'll have my
4:10attorney review it." I said. Her smile
4:13tightened. "It's standard." "Still."
4:17I packed my desk into two boxes, a
4:19photo, a jade plant, a certificate, and
4:22a word plaque. 12 years of crisis calls
4:24and midnight deployments gone in two
4:27cardboard cubes. At 5:00 p.m. on a crisp
4:30October Friday, my employment ended. I
4:32drove straight to Alex's office. He held
4:35the cease and desist letter. "Last
4:37chance to back out." he said. "Once we
4:40send this, there's no turning back."
4:42"I know."
4:44We emailed it at 6:03 p.m. to Nathan,
4:47Christine, and General Counsel Eleanor
4:49Vasquez. Pursuant to section 9 of my
4:51employment contract, the company's
4:53license to use my software has
4:55terminated. Continued use constitutes
4:58copyright infringement. Cease all use
5:01immediately.
5:02I went home, changed every password, and
5:04activated the kill switch I'd built into
5:06the system. By 6:47 p.m., every login
5:09screen read, "License expired. Contact
5:13system administrator." I turned off my
5:15phone and slept deeply, peacefully for
5:18the first time in months. Saturday at
5:209:00 a.m., I powered it back on.
5:22Notifications flooded in. 47 missed
5:25calls. 132 texts. 86 emails. Nathan,
5:31call me. What the hell is this?
5:33Bryant, systems are down. Bug?
5:36Christine, urgent. Discuss your letter.
5:40Derek, sales. Clients are furious. Help.
5:43Eleanor, General Counsel. We believe
5:45there's been a misunderstanding.
5:47I called Alex. They're dead in the
5:49water, he said. No orders, no payroll,
5:53no customer data. They'll negotiate.
5:56Sunday, Nathan's voicemails turned
5:58hostile. This is extortion. We'll see
6:01you in court. That evening, Alex called
6:03back. They want to meet Monday at 10:00.
6:06Claim it's work for hire, that your
6:08contract doesn't override copyright law.
6:11Are they really seeking an injunction?
6:14They're bluffing, Alex said. Your case
6:17is solid. They're bluffing, Alex said. I
6:20spoke with a copyright litigation
6:22specialist. Your case is rock solid. The
6:25contract explicitly reserves your
6:27ownership. You've maintained
6:28registrations for 12 years and they
6:30accepted those terms the whole time. No
6:32court will override that just because
6:34they're upset. So, what do we ask for?
6:37What do you really want, Paige? I
6:39thought about it all weekend. I want
6:41them to understand what I built has
6:43value, that I had value, that they made
6:46a mistake.
6:47We can make that happen. And money.
6:50Enough that I never have to work for
6:52someone like Nathan again. Enough to
6:54launch my own consulting firm with real
6:56leverage. Give me a number. I did the
6:59math. $200 million in annual revenue,
7:02$200 per hour consulting rate, 12 years
7:05of work. $3 million. $1 million for full
7:09ownership transfer after 3 years. $2
7:11million for a 3-year consulting contract
7:14to ensure a smooth transition.
7:16Alex raised an eyebrow. That's
7:18aggressive. Every day offline costs them
7:21$300,000.
7:23It's already been 3 days. That's nearly
7:25a million gone. My offer is generous. I
7:29like how you think. I'll draft the
7:30proposal. See you Monday at 9:30.
7:34Monday morning, I wore my navy suit,
7:36tailored, professional, and the pearl
7:38earrings my sister gave me for my first
7:40senior role. I looked like exactly what
7:43I was, someone who knew her worth. Alex
7:46met me in the parking lot, briefcase in
7:48hand, expression unreadable. Negotiate,
7:51don't argue. Stay professional. I'll
7:54handle the law, you're the technical
7:56expert. And remember, you hold all the
7:59leverage. Inside the executive
8:01boardroom, Nathan looked wrecked,
8:03wrinkled shirt, loosened tie. Bryant sat
8:06pale beside him. Christine had her
8:08tablet ready. Eleanor Vasquez, general
8:11counsel, held a stack of documents. At
8:14the far end, two strangers radiating
8:16authority, board members. "Ms. Donovan,"
8:20Eleanor began, "we believe this can be
8:22resolved reasonably." "I hope so," I
8:25said. "Your cease and desist claims
8:28ownership," she continued, "but under
8:30copyright law, employee-created work is
8:32work made for hire. It belongs to the
8:34employer. Your contract can't override
8:37federal law." Alex didn't flinch. "17
8:41U.S.C. section 101 allows parties to
8:43modify work made for hire by written
8:45agreement. Section 9 of her contract
8:48states clearly, 'All software systems
8:50developed by employee shall remain the
8:53intellectual property of employee.'
8:55That's not ambiguous. It's enforceable."
8:58"The language is unclear," Eleanor
9:00countered. "It's not." Alex slid a copy
9:04across the table. One board member
9:06leaned forward, an older woman with
9:08silver hair. "I'm Katherine Mills, board
9:11chair. I've reviewed the contract. Mr.
9:14Hartley is correct. We accepted these
9:16terms when we hired her." Nathan
9:18snapped, "This is hostage taking. She's
9:21demanding millions for systems we paid
9:23her to build." "She's enforcing her
9:26rights," Alex said. "She's not
9:28demanding, she's negotiating a new
9:30license." "Eleanor, what terms?" I spoke
9:34for the first time. "Three things. One,
9:37formal acknowledgement that I built
9:39these systems and was terminated without
9:41cause, ending your license. Two, a
9:44three-year consulting agreement for $2
9:46million to train your team. Three, full
9:49ownership transfer to you after 3 years
9:51for $1 million. Silence. $3 million.
9:56Nathan said flatly. A bargain, I
9:59replied. You've already lost nearly a
10:01million in downtime. Rebuilding would
10:03take 3 to 5 years. Even if you could
10:06replicate the undocumented business
10:07logic, it still needs someone like me to
10:10bridge the gap. My offer is the
10:12cheapest, safest path.
10:14This is extortion, he hissed. This is
10:17contract law, Alex said. She could walk
10:20away and let you figure it out alone.
10:22Catherine turned to me. Professionally,
10:25how long to rebuild? Minimum 3 years, I
10:28said. Realistically, 4 or 5. And you'd
10:31still need my expertise during that
10:33time. The consulting route is far less
10:35risky. Can you restore access today? The
10:39other board member asked. He was
10:41younger, maybe 50, with the tired eyes
10:43of someone who'd seen several
10:44emergencies. Within 1 hour of signing an
10:47agreement, I said. Eleanor pulled out
10:50her phone, stepped away from the table.
10:52She spoke in low tones to someone for
10:54several minutes, then returned. We need
10:56time to discuss this internally. Can you
10:59give us the room? Alex and I waited in
11:01the same lobby where I'd sat for my
11:03interview 12 years ago. The furniture
11:05was different now, more expensive.
11:07Everything about Peak Innovations had
11:09upgraded over the years, fueled by the
11:12platform I'd built. How do you feel?
11:15Alex asked quietly. Nervous. Angry.
11:18Vindicated. All of it. You're doing
11:21great. Stay strong. They're over a
11:24barrel and they know it. 45 minutes
11:26later, Eleanor came out. We'd like to
11:29make a counter offer. Back in the
11:31conference room, the energy had shifted.
11:34Nathan looked like he wanted to flip the
11:35table, but Catherine had clearly taken
11:38control.
11:39"Here's our position," Catherine said.
11:42"We agree that your contract is
11:43enforceable and that we terminated the
11:45license when we ended your employment.
11:47We're prepared to offer a two-year
11:49consulting agreement at 1.5 million
11:52total, plus a one-time payment of
11:54750,000 for permanent ownership transfer
11:57of all systems. 2.25 million total."
12:01I looked at Alex. He gave the smallest
12:03nod. "2.5 million," I said. "Two-year
12:07consulting agreement at 1.2 million,
12:10ownership transfer for 1.3 million. And
12:13I want Bryant removed from any role
12:15involving my systems." Nathan's face
12:17went red. "You can't dictate our
12:19staffing decisions." "I can dictate who
12:22has access to my intellectual property,"
12:24I countered. "Bryant demonstrated in 2
12:27weeks that he doesn't have the expertise
12:29to maintain these systems. If you want a
12:32successful transition, you need someone
12:34competent managing the process."
12:36Catherine looked at Nathan. "Bryant can
12:38be reassigned. That's not an issue."
12:41"Fine," Nathan bit out. "And one more
12:44thing," I said. "I want a public
12:46acknowledgement. Company-wide email from
12:49Nathan stating that my contributions
12:51were undervalued and that ending my
12:53employment was a mistake."
12:55"Absolutely not," Nathan said. "Then no
12:58deal." I stood up. "You can rebuild from
13:01scratch. Page," Catherine said
13:04carefully. "Surely we can find a
13:06compromise here." "That is the
13:08compromise," I said. "I could ask for 10
13:11million. I could demand Nathan's
13:13resignation. I could drag this out in
13:16court for years while your company
13:17hemorrhages money and customers.
13:19Instead, I'm asking for fair
13:21compensation and professional
13:22acknowledgement. That's not
13:24unreasonable." The room was silent
13:27except for the faint hum of the HVAC
13:29system. "Write the email," Catherine
13:31told Nathan. "We're not going to let
13:34pride destroy this company." Nathan's
13:36jaw worked.
13:37He looked at Eleanor, who shook her head
13:39slightly. No help there. "Fine," he
13:42finally said. "Draft it now," Alex said.
13:46"We'll review it before we sign
13:47anything."
13:48Nathan pulled out his laptop with
13:50visible reluctance. He typed for several
13:53minutes, his fingers striking the keys
13:55harder than necessary. Finally, he
13:57turned the screen toward us. The email
13:59was grudging but adequate. It
14:01acknowledged that my contributions had
14:03been significant and that the decision
14:05to restructure my position had been
14:07reconsidered in light of operational
14:09needs. It stopped short of calling it a
14:11mistake, but the implication was clear.
14:14"Not good enough," I said. "We write the
14:17second paragraph. I want explicit
14:19acknowledgement that my expertise was
14:21undervalued and that you should have
14:23handled my transition differently."
14:25"You're enjoying this," Nathan said.
14:28"I'm ensuring I don't get screwed
14:29again," I replied. "Write it." He
14:32rewrote it. The new version was better,
14:35acknowledging that my technical
14:37expertise and institutional knowledge
14:39were not adequately valued and that the
14:41company regrets the manner in which the
14:43employment transition was handled.
14:45"Acceptable," Alex said. "Now let's
14:48discuss the contract terms."
14:50The negotiation took another 3 hours.
14:53Every clause, every contingency, every
14:56detail had to be specified. Payment
14:58schedule, deliverables, termination
15:01conditions, confidentiality
15:02requirements, non-disparagement clauses.
15:06By 3:00 p.m. we had a complete
15:07agreement. Alex and Eleanor had worked
15:10out the legal language. Catherine had
15:12approved the financial terms. Nathan had
15:15signed off, though he looked like it
15:16physically pained him. "One last thing,"
15:19I said. "I want it in writing that I'm
15:21not bound by any non-compete. I'm free
15:24to consult for other companies,
15:26including your competitors." "That's
15:28standard in our agreements," Eleanor
15:30said. "Make it explicit. No ambiguity."
15:34She added the language. Alex reviewed
15:37it. We both signed. "When can you
15:39restore access?" Catherine asked. "Give
15:42me 20 minutes," I said. I went out to my
15:46car, pulled out my laptop, connected
15:48through my phone's hotspot. The system
15:50administration panel loaded quickly. I
15:53reset the master passwords, reactivated
15:55the licensing modules, verified that all
15:58services were running properly. At 3:47
16:01p.m. on Monday, October 30th, 2023, Peak
16:05Innovations regained access to the
16:06systems that ran their entire business.
16:09My phone buzzed immediately. Messages
16:12from the IT team, from Derek in sales,
16:14from various people throughout the
16:16company. "It's back up."
16:18"Thank God." "Everything's working
16:20again." I forwarded the confirmations to
16:23Alex and Catherine. "Access restored."
16:26"All systems operational."
16:28The first payment, $750,000,
16:31hit my account the following morning.
16:33The remainder would come in installments
16:35over the next 2 years, but seeing those
16:37numbers in my bank account made
16:39everything real. I'd won. Nathan's email
16:42went out Wednesday morning to the entire
16:44company. I wasn't on the distribution
16:46list anymore, but Janet forwarded it to
16:49me with a simple message, "Holy shit."
16:52The response was apparently immediate
16:54and intense. People started reaching
16:56out. Former colleagues, industry
16:58contacts, even a few journalists who'd
17:01heard about the situation through
17:02professional networks. "Is it true you
17:04locked them out of their own systems?
17:07Did you really get millions? How did you
17:09have the leverage to make them
17:10apologize?" I didn't comment publicly,
17:13but privately, I felt vindicated in a
17:16way that money alone couldn't have
17:17achieved. The consulting work started
17:20the following Monday. I showed up 3 days
17:22a week, worked with their new technical
17:24lead, a woman named Olivia Chen,
17:26competent, experienced, humble enough to
17:29know what she didn't know. "I read
17:31through the documentation you left," she
17:33said during our first meeting. "It's
17:35incredibly thorough, but I'm sure there
17:37are things that aren't documented,
17:39things you just know from working with
17:40these systems for so long."
17:42"There are," I admitted. "That's why I
17:44built in 2 years for transition. We'll
17:47go through every major module, every
17:49integration point, every quirk and
17:51workaround." "I appreciate that. And for
17:54what it's worth, I'm sorry about what
17:56happened. You shouldn't have been pushed
17:58out." It was nice to hear, even if it
18:00didn't change anything. Bryant, I
18:02learned, had been reassigned to the
18:04marketing technology team, far away from
18:06anything I'd built. He'd apparently been
18:09vocal about the situation, calling me
18:11vindictive and unreasonable. Nobody
18:13seemed to be listening. Nathan avoided
18:16me completely. We were never in the same
18:18room if he could help it. On the rare
18:20occasions we passed in the hallway, he
18:22looked through me like I was invisible.
18:24Catherine, on the other hand, made a
18:26point of checking in monthly. "How's the
18:28transition going? Any concerns?"
18:31"Olivia's excellent," I told her.
18:34"She'll be fine once we complete the
18:35knowledge transfer." "Good. And Paige, I
18:39want you to know that I've reviewed our
18:40entire technical hiring and retention
18:42strategy. What happened to you is
18:44unacceptable. We're implementing changes
18:47to ensure it doesn't happen to anyone
18:49else." It was something. Not enough, but
18:52something. By month six, I'd developed a
18:54routine. 3 days a week at Peak
18:56Innovations, 2 days building my own
18:58consulting practice. Word had spread in
19:01the industry about what happened. Some
19:03people thought I was a hero. Others
19:05thought I was difficult, vindictive, the
19:07kind of person who'd hold a company
19:09hostage. I didn't care much about either
19:11characterization. What mattered was that
19:14company started reaching out.
19:16Organizations that wanted someone who
19:18understood not just technology, but the
19:20business implications. Someone who
19:22documented meticulously. Someone who
19:25understood the value of intellectual
19:26property protection. I registered
19:29Donovan Technical Consulting in month
19:31seven. My first client was a mid-sized
19:33logistics company that needed to
19:35overhaul their warehouse management
19:37system. My second was a healthcare
19:39startup building a patient data
19:41platform. By month 10, I had four active
19:43clients and was turning down work. By
19:46month 18, I'd hired two junior
19:48developers to help with implementation
19:50work while I focused on architecture and
19:52client relationships. The second
19:54installment from Peak Innovations came
19:56through on schedule. Another $750,000.
20:00My accountant helped me structure
20:02everything properly, set up retirement
20:04accounts, invest wisely. I bought a
20:06house. Not a mansion, but a comfortable
20:09three-bedroom in a good neighborhood
20:11with a dedicated office space and a
20:13garden where I could grow actual plants
20:15that weren't succulents. The two-year
20:17mark arrived faster than I expected.
20:19Olivia had mastered the systems. She'd
20:22even made some improvements,
20:23optimizations I'd wanted to implement,
20:25but never had time for. The technical
20:28team at Peak Innovations was stable,
20:30competent, no longer dependent on me.
20:33The final payment cleared. $1.3 million
20:36for complete ownership transfer of all
20:38the systems I'd built. I signed the
20:40transfer documents in Catherine's
20:42office. Nathan wasn't there. He'd left
20:45the company six months earlier, taking a
20:48position at a competitor. I'd heard
20:50through the industry grapevine that it
20:52wasn't entirely voluntary. Board
20:54pressure, apparently. "Thank you for
20:56everything." Catherine said as I signed
20:59the last page. "You handled this with
21:01more grace than I think I would have in
21:03your position." "I handled it the way
21:05the contract allowed me to, I said.
21:08That's not grace. That's just
21:10understanding my rights. Still, we
21:12learned a lot from this situation about
21:15valuing expertise, about contract
21:17negotiation, about not taking people for
21:20granted. She paused. I hope there are no
21:23hard feelings.
21:25I thought about that. Were there hard
21:27feelings? Yes. Nathan had tried to push
21:29me out after 12 years of dedicated work.
21:32He'd undervalued my contributions and
21:35assumed I'd have no recourse, but I'd
21:37won. Completely, decisively,
21:39financially. The hard feelings had been
21:42processed through legal channels and
21:44converted into a very satisfying sum of
21:46money. "No hard feelings," I said, "just
21:49lessons learned."
21:51I ran into Bryant at a technology
21:53conference 8 months after the consulting
21:55contract ended. He was presenting on
21:57modern architecture patterns, recycling
22:00slides from presentations I'd seen
22:02online.
22:03He saw me in the audience and lost his
22:05place mid-sentence, recovered, kept
22:08going, but the confidence was gone.
22:10Afterward, in the networking session, he
22:11approached me. "Paige, hey. How have you
22:15been?"
22:16"Excellent," I said truthfully. "My
22:18consulting practice is doing well. How
22:21are things at Peak?" "I'm actually not
22:23there anymore," he admit. "D
22:26moved to a different company about 4
22:28months ago. The marketing tech role
22:30wasn't really It wasn't what I wanted to
22:32be doing." "I see," I said neutrally.
22:36"Look, about everything that happened
22:38He shifted uncomfortably.
22:41I didn't realize the situation. Nathan
22:43made it sound like you were being
22:44difficult, like you were holding things
22:46up. I didn't know you actually owned all
22:48that code." "Most people don't read
22:51contracts carefully," I said. "I learned
22:54too." "Yeah." He looked down at his
22:56conference badge. "I learned a lot from
22:58that situation, too, about intellectual
23:01property, about understanding what
23:03you're stepping into. It was as close to
23:06an apology as I was going to get. I
23:08decided to be generous. Good luck with
23:10your career, Bryant. Take the time to
23:12learn the fundamentals. They matter more
23:15than the latest trends.
23:17He nodded, clearly relieved to escape
23:19the conversation and moved away. Janet
23:21from marketing found me at the hotel bar
23:23that evening. She'd left Peak
23:25Innovations 6 months after I did. Landed
23:28at a competitor with a substantial
23:30raise. I heard what you did, she said,
23:33sliding onto the bar stool next to me.
23:35The whole cease and desist thing.
23:37Getting millions. Making Nathan
23:39apologize. It's legendary. It was just
23:43contract enforcement, I said. It was
23:45brilliant. She ordered a gin and tonic.
23:48You know half the technical staff quit
23:50after you left, right? They saw how the
23:52company treated you and decided they
23:54didn't want to stick around to see if
23:56they were next. I didn't know that.
23:58Olivia's good, but she's managing a
24:00skeleton crew. They've had to outsource
24:03a lot of development work. It's
24:05expensive and messy. She took a sip of
24:07her drink. You broke something when you
24:09left. Not just the systems. The culture.
24:13People realized they weren't valued. I
24:15thought about that. I hadn't intended to
24:17break the culture. I just intended to
24:20protect myself, to enforce my rights, to
24:22not be taken advantage of. But maybe
24:25those things were connected. Maybe
24:27standing up for yourself showed other
24:28people that they could stand up for
24:30themselves, too. How's your new job? I
24:33asked. Amazing. They actually listen to
24:36the marketing team. Can you imagine? She
24:39laughed. What about you? I heard you
24:41started your own firm. Donovan Technical
24:44Consulting. We're small, but growing.
24:47Four employees now. Thinking about
24:49hiring two more next quarter. You hiring
24:52marketers? She asked with a grin. Are
24:54you to
24:56Maybe. Send me the details. I'm serious.
25:00We exchanged business cards. Hers was
25:02from her current employer, sleek and
25:04expensive. Mine was simpler, just my
25:07name and credentials, but it represented
25:09something I'd built entirely on my own
25:11terms. The consulting practice continued
25:14to grow. By the end of year three, I had
25:17eight employees and had to move out of
25:18my home office into actual commercial
25:20space. Nothing fancy, just a small suite
25:24in a professional building with a
25:25conference room and dedicated desks for
25:27everyone. I hired Janet six months after
25:30that conference conversation. She built
25:32out our marketing strategy, helped us
25:34position ourselves in the market,
25:36brought in clients I never would have
25:37found on my own. You know what makes
25:39this place different? She said during a
25:42team meeting one day. We all know
25:44exactly what we're worth. We all have
25:46clear contracts. We all understand our
25:48intellectual property rights. Nobody's
25:51getting screwed here. That had been
25:53intentional. Every person I hired got a
25:56comprehensive contract that explicitly
25:58addressed ownership, compensation,
26:00benefits, termination conditions. I paid
26:02competitive salaries and refused to rely
26:05on equity promises or we're a family
26:07rhetoric to justify below market rates.
26:10My employees own their work within
26:12reasonable bounds. The company had
26:14licenses to use what they developed, but
26:16if someone left, they could take their
26:18expertise with them. No non-competes, no
26:20golden handcuffs, just fair terms and
26:23mutual respect. That's the goal, I said.
26:26Nobody should have to go through what I
26:28went through to get fair treatment. Year
26:30four brought a major milestone. We
26:32landed a contract with a Fortune 500
26:35company to overhaul their entire
26:36enterprise resource planning system. The
26:39kind of project that could define a
26:40consulting firm's reputation. The
26:43project manager they assigned to work
26:44with us was efficient, detail-oriented,
26:47and familiar. It took me a moment to
26:49place her. Christine, former HR director
26:52from Peak Innovations. Paige Donovan,
26:55she said when we met for the kickoff
26:57meeting and I couldn't read her
26:58expression. I wondered if our paths
27:01would cross again. Christine, this is
27:04unexpected. I left Peak about 2 years
27:06ago. Joined this company as VP of Human
27:09Resources. When I heard your firm was
27:12bidding on this project, I recommended
27:14you. That was genuinely surprising. Why?
27:17Because what happened with you taught me
27:19something important, she said frankly.
27:22We treated you poorly. I was part of
27:24that. I sat in that room with Nathan and
27:27watched him fire someone who'd built the
27:28entire technical infrastructure and I
27:31didn't speak up. I didn't question it. I
27:34just did my job as HR director, which
27:36was to protect the company from
27:37liability. She paused, looked
27:39uncomfortable. But protecting the
27:41company from liability isn't the same
27:44thing as doing what's right. You were
27:46right to enforce your contract. You were
27:48right to demand fair compensation. And
27:51you were right that Nathan was a
27:52terrible manager who didn't understand
27:54the value of the people who worked for
27:56him. I appreciate you saying that, I
27:58said carefully. I've changed how I
28:01approach HR because of what happened
28:03with you, she continued. I push back now
28:06when executives want to make stupid
28:07decisions about valuable employees. I
28:10make sure contracts are fair. I advocate
28:12for proper succession planning and
28:14knowledge transfer. Because watching
28:16your company nearly collapse when you
28:18locked them out was one of the most
28:20stressful experiences of my career and
28:22it was entirely preventable. It was, I
28:25agreed. So I'm recommending your firm
28:27because I know you're competent, ethical
28:29and you won't cut corners. And
28:31personally, I'm hoping we can work
28:33together professionally. What happened
28:35at Peak doesn't need to define our
28:37relationship going forward. I considered
28:40that. Christine had been complicit in my
28:42termination, yes. But she'd also just
28:44acknowledged it openly, explained how
28:47she'd changed, and given me a major
28:48contract. People could learn. People
28:51could grow. "I'd like that," I said.
28:54"Let's start fresh." The Fortune 500
28:57project took 18 months and was wildly
28:59successful. It led to three more major
29:02clients, all referrals from Christine's
29:04network. By year five, Donovan Technical
29:07Consulting had 22 employees and revenue
29:10in the high seven figures. I hired
29:12Olivia away from Peak Innovations to be
29:15my VP
29:17She'd done excellent work there, but the
29:19company was stagnating under new
29:21management. They'd brought in a new CTO
29:23who wanted to replace everything I'd
29:25built with a commercial off-the-shelf
29:27solution, despite Olivia's protest that
29:29the custom system was actually superior.
29:32"I can't watch them dismantle what we
29:34built together," she told me over lunch
29:36when I made the offer. "The new CTO
29:39doesn't understand the business
29:40requirements. He just wants something
29:42shiny he can put on his resume."
29:45"Then come work for me," I said. "Help
29:47me build something better." She
29:49accepted. Peak Innovations called six
29:52months later. The off-the-shelf solution
29:54had failed spectacularly.
29:56Data migration issues, functionality
29:58gaps, integration problems with their
30:01vendor systems. They were hemorrhaging
30:03money and customers. Katherine, still
30:05board chair, made the call personally.
30:07"Paige, I know this is a lot to ask
30:09after everything that happened, but we
30:11need help. The new system isn't working.
30:14We need someone who understands our
30:15business, our requirements, our
30:17history." "You need the old system
30:19back," I said. "We need expertise. Your
30:22expertise. Can your consulting firm take
30:25this on?" I quoted them triple my
30:27standard rate. They accepted without
30:29negotiating. Olivia led the project
30:32personally, working with a team of four
30:34developers from my firm. It took six
30:36months to unwind the disaster and get
30:38them back to functional operations. Not
30:41back to my original system, that ship
30:43had sailed when they decommissioned it,
30:45but to something stable built on similar
30:47architectural principles. The project
30:50bill was $2.8 million.
30:52Peak paid it. Nathan, I learned from
30:54Catherine during one of our project
30:56status calls, was no longer in the
30:58industry. He'd flamed out at two
31:00different companies after leaving Peak.
31:02Got a reputation for being difficult to
31:04work with and had eventually left tech
31:06entirely. Last I heard he was doing real
31:09estate. Catherine said, "Probably better
31:12for everyone." "Probably." I agreed.
31:15Year six brought another turning point.
31:17A major tech publication ran a feature
31:19article about consulting firms that were
31:21changing how the industry worked.
31:23Donovan Technical Consulting was
31:25profiled prominently with a particular
31:28focus on our employment practices and
31:30intellectual property policies. The
31:32article included quotes from several of
31:34my employees about why they chose to
31:36work for us. "I know exactly where I
31:38stand." one developer said. "No
31:41ambiguity, no surprises. Page treats us
31:44like professionals who deserve clear
31:46terms and fair compensation.
31:48I've worked at places that promised
31:50equity and never delivered." a project
31:53manager said.
31:54"Here I get paid well in actual money
31:56and I know what I'm building. That's
31:58worth more than empty promises." The
32:01article also included a brief mention of
32:03what had happened at Peak Innovations.
32:05Not the full story, but enough context
32:07to explain why I'd structured my company
32:09the way I had. "Ms. Donovan's experience
32:12being terminated from a previous
32:13employer after 12 years of service,
32:16despite having built the company's
32:18entire technical infrastructure,
32:20informed her approach to contracts and
32:22employee rights." the article stated.
32:24She settled with the company for an
32:26undisclosed sum after enforcing
32:28intellectual property rights that gave
32:30her leverage to negotiate favorable
32:32terms. The article tripled my consulting
32:35inquiries in the following month. Some
32:37were from companies legitimately
32:39interested in our services, but many
32:41were from individual developers and
32:43technical professionals who wanted
32:45advice on protecting themselves. I
32:47started getting emails like, "I'm
32:49negotiating a contract with a startup.
32:52What clauses should I include to protect
32:54my intellectual property?
32:56I built a critical system for my
32:58employer, but I'm worried about being
32:59pushed out. What are my options?
33:02My company wants me to sign a
33:04non-compete. Is it enforceable? Should I
33:07negotiate?" I couldn't respond to all of
33:09them personally, but I saw a need. A gap
33:12in the market for education and
33:14resources about technical professionals'
33:16rights. I started a newsletter, "Know
33:19Your Worth: Contract and IP Rights for
33:22Technical Professionals." It covered
33:24employment contracts, intellectual
33:26property law, negotiation strategies,
33:29industry standards for compensation. The
33:31subscriber list grew to 10,000 people in
33:346 months, 20,000 by the end of the year.
33:37I began speaking at conferences, not
33:39about technical architecture, but about
33:41professional advocacy. How to read
33:43contracts. How to negotiate effectively.
33:47How to protect your work. How to know
33:49when to walk away. The tech industry
33:51relies on skilled professionals being
33:53too humble or too scared to advocate for
33:55themselves, I said during a keynote at a
33:58Women in Technology conference. We're
34:00taught that passion should be enough.
34:02That we should be grateful for
34:03opportunities. That asking for fair
34:06compensation is somehow mercenary or
34:08unprofessional. I paused, looked out at
34:11the audience of several hundred women.
34:13"That's garbage. You are professionals
34:16with valuable skills. You deserve clear
34:18terms, fair pay, and respect. And if a
34:21company won't give you those things, you
34:23deserve to walk away with what you
34:24built." A standing ovation surprised me.
34:28Afterward, dozens of women approached
34:30with their own stories. Situations where
34:32they'd been undervalued, pushed out,
34:34taken advantage of. Many were still in
34:37those situations, unsure how to proceed.
34:39I gave them what advice I could, but
34:41mainly I listened. Because that's what
34:43I'd needed 12 years ago when Nathan
34:45fired me. Someone to witness what had
34:47happened and confirm that it was wrong.
34:50Year seven, I wrote a book. Owning Your
34:52Work: A Technical Professional's Guide
34:54to Contracts, Rights, and Fair
34:56Compensation.
34:57Covered everything I'd learned the hard
34:59way. Contract negotiation, intellectual
35:02property basics, employment law
35:04principles, documentation strategies,
35:06when to fight and when to walk away. The
35:09book was published by a major tech
35:10publisher and became a surprising
35:12bestseller in the professional
35:13development category. Not Harry Potter
35:16numbers, but enough to matter. Enough
35:18that people started recognizing my name
35:20beyond just the consulting work. I did a
35:23podcast interview about the book, and
35:25the host inevitably asked about the Peak
35:27Innovation situation. "That must have
35:29been incredibly stressful," she said.
35:32"Going up against a company like that.
35:34Weren't you scared they'd crush you
35:35legally?" "I was terrified," I admitted.
35:39"But I was more scared of letting them
35:41take what I'd built without a fight. I'd
35:43spent 12 years being careful,
35:45documenting everything, maintaining my
35:47rights. I'd planned for this
35:49possibility, even though I'd hoped it
35:50would never happen." "What advice would
35:53you give to someone in a similar
35:54situation?" Three things. First, read
35:57your contract. Actually read it word by
35:59word. Understand what you're agreeing
36:01to. Second, document everything. Every
36:04project, every contribution, every
36:07decision. Third, maintain boundaries
36:10between personal and professional. Keep
36:12your work separate from the company's
36:14work where possible. Register copyrights
36:16if appropriate. Protect yourself before
36:19you need protection.
36:21And if someone finds themselves already
36:22in trouble, already pushed out or
36:25undervalued, get a good lawyer.
36:27Understand your leverage, and don't be
36:29afraid to use it. Companies make
36:31decisions based on cost-benefit
36:33analysis. If it's cheaper to treat you
36:36fairly than to fight you, they'll treat
36:37you fairly. You just have to make sure
36:39the math works in your favor. The
36:41podcast episode went viral by tech
36:44podcast standards. Hundreds of thousands
36:46of downloads. It led to more speaking
36:49invitations, more consulting clients,
36:51more people reaching out with their own
36:53stories. Year eight, I hired a dedicated
36:55person just to manage the education side
36:57of the business. Workshop facilitation,
37:00online courses, resource development. We
37:03created a comprehensive program for
37:05technical professionals on protecting
37:07their rights and negotiating
37:08effectively. Donovan Technical
37:10Consulting expanded into Donovan
37:12Professional Group with separate
37:14divisions for consulting services and
37:16professional education. We were at 35
37:19employees and growing steadily. Not
37:21explosive growth, but sustainable
37:23growth. The kind that came from doing
37:26good work and building a solid
37:27reputation. I bought a bigger house, got
37:30a dog, started dating someone I met
37:32through professional networks. A patent
37:34attorney who understood intellectual
37:36property obsession. Began to build a
37:38life that wasn't defined entirely by
37:41work, though work remained central. The
37:43money from Peak Innovations had been
37:45invested wisely. Between that and the
37:48consulting firm's success, I was
37:50financially secure in a way I'd never
37:52imagined possible. Not billionaire
37:54wealthy, but comfortable. Free. Able to
37:57make decisions based on what I wanted
37:59rather than what I needed. I traveled to
38:01conferences in different countries.
38:04Spoke to technical professionals in
38:05Europe, Asia, Australia. The issues were
38:08universal. Undervaluation, unclear
38:11contracts, companies taking advantage of
38:14passionate people who didn't know how to
38:15protect themselves. Year nine brought a
38:18full circle moment. A small startup
38:20reached out looking for help building
38:22their enterprise platform from scratch.
38:24The founder was a woman in her late 20s,
38:27brilliant but inexperienced with the
38:29business side. During our initial
38:31consultation, she mentioned she'd been
38:33working on the core technology in
38:34graduate school before founding the
38:36company. "Do you own the intellectual
38:38property?" I asked. "Or does the
38:41university?" She looked confused. "I
38:44built it, so I own it." "Not
38:47necessarily. Most universities claim
38:50ownership of IP developed using their
38:52resources. Did you check your student
38:54agreement? Your research grant terms?"
38:57Her face went pale. "Oh god. I didn't
39:00even think about that." We spent the
39:02next 3 hours going through her
39:04documentation. Turned out she did own
39:06the core IP barely. She'd been careful
39:08to develop the critical algorithms on
39:10her personal laptop outside of
39:13university facilities without using
39:15grant funding. But it was close. "You
39:18need to clean this up immediately." I
39:20told her. "Register copyrights. Get a
39:23formal IP assignment from the university
39:25if needed. Clarify ownership before you
39:28bring on investors or partners. Because
39:30if this becomes ambiguous later, it
39:33could destroy your company." "How do you
39:35know all this?" she asked. I told her
39:38the story. Not the full version, but
39:40enough. How I built a platform, been
39:42pushed out, enforced my rights, and
39:44turned it into a career teaching others
39:46to protect themselves. "I want to do it
39:48right from the beginning." she said.
39:51"Can you help me?" "That's what we do.
39:53We worked with her for 6 months. Set up
39:56her corporate structure properly. Wrote
39:58employment contracts that were fair to
40:00everyone. Designed her equity
40:02compensation system to be transparent
40:04and equitable. Built a technical
40:07infrastructure she actually owned and
40:09understood. 3 years later, she sold that
40:11startup for $80 million. She sent me a
40:14bottle of champagne and a note. Thank
40:17you for teaching me to value my work.
40:19Year 10 since the Peak Innovation
40:21situation, I got a letter. Not an email.
40:24An actual physical letter delivered to
40:26my office. The return address was from
40:28Nathan Spencer. I stared at it for a
40:31full minute before opening it. My
40:33assistant, hovering in the doorway,
40:35asked if I needed anything. "I'm fine."
40:38I said, though I wasn't sure that was
40:39true. The letter was handwritten. Two
40:42pages. Dear Paige, "I'm writing this
40:45because I've career.
40:50I'm not sure if this letter will mean
40:52anything to you, but I need to say it
40:54anyway. I was wrong. About everything. I
40:57was wrong to push you out after 12
40:59years. I was wrong to undervalue your
41:01contributions. I was wrong to assume
41:03your work was interchangeable and
41:05replaceable. I was wrong to be
41:07dismissive during your termination
41:09meeting. I was wrong to try to fight you
41:11instead of negotiating fairly when you
41:13enforced your contract rights. Most of
41:15all, I was wrong about what leadership
41:17means. I thought it meant making tough
41:19decisions and moving quickly without
41:21sentiment. I thought it meant always
41:23projecting confidence even when I didn't
41:25understand something. I thought it meant
41:27keeping people on their toes, keeping
41:29them slightly insecure so they'd work
41:31harder. I was wrong about all of that.
41:34What happened with you taught me lessons
41:35I should have learned earlier. That
41:37expertise has value. That institutional
41:40knowledge matters. That treating people
41:42fairly isn't just ethical, it's
41:44practical. That contracts mean
41:46something. That you can't just assume
41:48people have no recourse when you treat
41:50them poorly. I've been out of the
41:52industry for several years now. After
41:54Peak, I had two other positions that
41:56ended badly. The pattern was similar. I
41:58didn't respect the people who worked for
42:00me. I made decisions without
42:02understanding the technical
42:03implications. I prioritized appearing
42:05decisive over actually being right.
42:08Eventually, I had to accept that the
42:09common factor in all those failures was
42:11me. I'm not asking for forgiveness. I'm
42:14not sure I deserve it, but I want you to
42:17know that I understand what I did wrong
42:19and I'm genuinely sorry. You deserved
42:21better. The company deserved better.
42:24Everyone I worked with deserved better.
42:26I read your book last month. It's
42:28excellent and painful to read knowing
42:31I'm part of the cautionary tale that
42:33informed it. But I'm glad you wrote it.
42:35The advice is solid. I wish I'd
42:37understood those principles when I was
42:39actually managing people. I'm working in
42:42real estate now. Residential sales. It
42:45suits me better. Shorter relationships,
42:47clearer transactions, less opportunity
42:50to do lasting damage through bad
42:51management. I hope your consulting firm
42:54continues to thrive. I hope you're doing
42:56well personally and professionally. And
42:58I hope that someday when you tell the
43:00story of what happened at Peak
43:01Innovations, you can include that I
43:03eventually understood how badly I messed
43:05up. Sincerely, Nathan Spencer. I read
43:08the letter three times. Was it enough?
43:11Did it change what had happened? Did it
43:13make the stress and anxiety and fighting
43:15worth it?
43:17But it was something. I filed the letter
43:19away in my desk drawer and went back to
43:20work. That evening, I video called my
43:23sister. Lydia appeared on screen in her
43:25kitchen cooking something that smelled
43:27good even through the digital
43:29connection. "How are you doing?" she
43:31asked. "You look contemplative." I got a
43:34letter from Nathan today. "Your old boss
43:37Nathan? The one who fired you?" "That's
43:40the one. He apologized. Said his
43:42therapist suggested he make amends."
43:45"Wow. How do you feel about that?" I
43:48thought about it. Honestly, I don't
43:50know. It's nice that he recognized he
43:52was wrong, but it doesn't change
43:54anything. I still had to fight for what
43:56was rightfully mine. I still spent
43:58months stressed and anxious. I still had
44:01to completely rebuild my career. "But
44:03you did rebuild it," Lydia pointed out.
44:06"Better than before. You own your own
44:08company. You're financially secure.
44:11You're helping other people avoid what
44:13happened to you. None of that would have
44:15happened if Nathan hadn't been a
44:16terrible boss. That's a depressing
44:18silver lining.
44:20Welcome to life. Sometimes the worst
44:22things lead to the best outcomes. She
44:25stirred whatever she was cooking. Are
44:27you going to respond to him? I don't
44:29know. Maybe. What would I even say?
44:32Thank you for the apology. I accept it.
44:35Go to hell. Whatever feels right to you.
44:38I sat with that question for several
44:39days. Finally, I wrote back. Not a long
44:42letter, just a brief note. Nathan, thank
44:45you for your letter. I appreciate the
44:47apology and the acknowledgement of what
44:49happened. What you did was wrong and it
44:52cost me significantly in terms of stress
44:54and professional disruption. But it also
44:56forced me to advocate for myself in ways
44:58I might not have otherwise. The
45:00experience informed how I built my own
45:02company and how I teach others to
45:04protect themselves. I hope you've
45:06genuinely learned from those experiences
45:08and that you treat people better going
45:10forward. That matters more than any
45:12apology to me personally. I don't know
45:14if I forgive you. I'm still working on
45:16that. But I accept that you've grown and
45:18changed and that's worth something.
45:20Paige. I sent it and moved on. Year 11
45:24brought new challenges and
45:25opportunities. The consulting firm
45:27expanded into cybersecurity services. We
45:30hired specialists, built out new service
45:33offerings, landed government contracts
45:35that required security clearances and
45:37rigorous vetting. The professional
45:39education side continued to grow. We
45:41launched an online platform with
45:43courses, templates, resources. It
45:46generated passive income that
45:47supplemented the consulting revenue
45:49nicely. I spoke at a TEDx event about
45:52workplace power dynamics and
45:54professional rights. The talk was titled
45:56Know Your Worth: How One Contract Clause
45:59Changed My Life. It got over a million
46:01views online. The comments were mixed.
46:04Some people called me a hero. Others
46:06called me vindictive, greedy, petty.
46:09Some said I was justified. Others said
46:11I'd held a company hostage and ruined
46:13good people's livelihoods. I'd learned
46:15to ignore the noise. What mattered was
46:18the private messages from people who
46:19said the talk helped them. Who said it
46:21gave them courage to negotiate better
46:23terms. Who said it helped them
46:25understand they weren't powerless. Those
46:27messages made everything worthwhile. I
46:30ran into Katherine Mills at an industry
46:32gala last year. She'd retired from the
46:34Peak Innovations board, but remained
46:36active in the business community. Page,
46:39I was hoping to see you here. She gave
46:42me a warm hug. I've been following your
46:44company's success. You should be very
46:46proud. Thank you. It's been quite a
46:49journey. I owe you an apology, too, she
46:52said. I was on the board when Nathan
46:54terminated you. I should have questioned
46:56that decision more aggressively. Should
46:59have insisted on better succession
47:00planning. Should have recognized your
47:02value before the crisis forced us to.
47:05You made it right, I said. You could
47:07have tried to fight me legally. Instead,
47:10you negotiated fairly. That mattered.
47:13Still, we learned expensive lessons from
47:15that situation. The company has
47:17completely revamped how they handle key
47:19personnel. Better contracts, better
47:22retention strategies, better respect for
47:24institutional knowledge. She paused.
47:27Though honestly, Peak has never been the
47:29same since you left. Olivia did
47:31excellent work, but the culture changed.
47:34People became mercenary. Everyone
47:36negotiating for maximum leverage. Nobody
47:39trusting that loyalty would be rewarded.
47:41Can you blame them? I asked. After
47:44watching how I was treated? No, she
47:47admitted. I can't. We broke something
47:50when we pushed you out. Some things
47:52can't be repaired. It was a sobering
47:54thought. I hadn't intended to break
47:56company
47:58I just wanted fair compensation for my
48:00work. But actions have consequences, and
48:03companies that treat people poorly
48:04create environments where nobody trusts
48:06anyone. Today, 12 years after Nathan
48:09fired me and 11 years after I locked
48:11Peak Innovations out of their systems,
48:13Donovan Professional Group employs 53
48:16people across three divisions. Technical
48:18consulting, cybersecurity services, and
48:21professional education. We generate
48:23approximately 15 million in annual
48:25revenue. Not enough to make me a
48:27billionaire, but more than enough to
48:29build the life I want. I own my home
48:31outright. No mortgage, no landlord,
48:34nobody can take it away. I have
48:36investments that will sustain me through
48:37retirement, even if the business
48:39disappeared tomorrow. I have autonomy,
48:41security, freedom. More importantly, I
48:44have satisfaction. Every person who
48:46works for me has a clear contract that
48:48protects their rights. Everyone knows
48:50exactly what they're worth and what they
48:52own. Nobody will be surprised if things
48:55change. Nobody will be pushed out
48:57without recourse. I've helped hundreds
48:59of technical professionals negotiate
49:01better terms, protect their intellectual
49:03property, and understand their leverage.
49:06Some of them have started their own
49:07companies. Others have stayed at their
49:10employers, but with better compensation
49:12and clearer roles.
49:13The book is in its third edition. The
49:16newsletter reaches over 100,000
49:18subscribers. The online courses have
49:20been completed by tens of thousands of
49:22people globally. I'm not famous. I'm not
49:25on any lists. I'm just someone who stood
49:28up for herself once and turned that
49:30experience into something larger. If
49:32you've made it this far in the story,
49:34you know what I want to say. If you've
49:36ever been undervalued at work, if you've
49:37ever been pushed out after giving
49:39everything, if you've ever wondered
49:41whether you had any power in a situation
49:43where you felt powerless, you're not
49:45alone. Read your contracts. Document
49:47your contributions. Understand what you
49:50own. Know your worth. Protect yourself
49:53before you need protection. And when
49:55someone shows you they don't value you,
49:56believe them. Then make sure it costs
49:58them appropriately. The platform I built
50:01for Peak Innovations is still running,
50:03still processing hundreds of millions in
50:05transactions annually. They own it now
50:07fully and completely. But every time
50:10they log in, every time they generate a
50:11report, every time they process an
50:13order, they're using something that
50:15almost brought them to their knees
50:16because they didn't appreciate what they
50:18had. I built something new instead.
50:20Something I control completely.
50:22Something that helps other people avoid
50:24what happened to me. That's worth more
50:26than any amount they could have paid me
50:28to stay. Hit that subscribe button if
50:30you believe in standing up for yourself.
50:33Smash the like if you've ever had to
50:34fight for what you deserved. Drop a
50:36comment below with your story about the
50:39boss who underestimated you, the company
50:41that took you for granted, the moment
50:43you realized you had more power than
50:44they wanted you to know. Because we're
50:46not alone in this. And the more we share
50:49these stories, the harder it becomes for
50:51companies to get away with treating
50:53talented people like disposable
50:54resources. Thanks for listening to mine.
50:57And remember, know your worth, protect
51:00your work, and never let anyone convince
51:02you that standing up for yourself is
51:04somehow unprofessional. You deserve
51:06better. We all do.

About this transcript

This page contains the full transcript of After a Decade, They Let Me Go—I Shut Down the Software That Earned Them Millions by Cold Revenge , generated from the public captions YouTube serves with the video. The transcript has 8,008 words across 1,329 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.

What you can do with it

Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to translate the transcript into 100+ languages.

Free YouTube transcript tool

YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, translation to 100+ languages, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.