Founder Almanac/Paul English
PE

Paul English

Kayak

Technology1970s-2010s
20 principles 5 frameworks 6 stories 10 quotes
Ask what Paul would do about your problem

Core Principles

customer obsession

Make money through clear, measurable value creation. Display these metrics visibly to keep your team connected to the actual economic impact of their work.

Kayak displayed a real-time counter of daily travel searches on a prominent screen. This connected programmers directly to their company's revenue driver, showing that every search represented tangible value: 75 cents for flights, $2 for hotels.

hiring

Recruit trusted collaborators repeatedly across ventures. Building long-term relationships with people you know and trust creates stability and institutional knowledge across multiple company attempts.

Paul worked with the same core group across multiple startups spanning decades. When Billo, Schwenk, and Rago heard Paul was starting Boston Light after previous failures, Billo immediately recognized the pattern and committed despite past losses, saying he believed this one would work.

Someday, this boy's going to get hit by a truck full of money, and I'm going to be standing beside him.

innovation

Pleasure is enhanced when you accomplish something with limited tools. Constraints breed satisfaction more effectively than abundance.

Paul discovered that writing software within strict memory limitations for the Atari 2600 and other constrained systems created deeper satisfaction than programming without bounds. The constraint forced elegance and optimization.

One rather curious thing I've noticed about aesthetic satisfaction is that our pleasure is significantly enhanced when we accomplish something with limited tools.

leadership

Share significant proceeds with your core team. Redistribute wealth among people who built the company with you to align interests and recognize their contribution.

When Paul sold Boston Light Software for $33.5 million, he gave half his own proceeds to his team. Later at Kayak, he ensured his lieutenants Billo and Schwenk owned stock worth nearly $20 million each, making them financially independent partners in success.

learning

Learn software engineering through applied work, not theory alone. Day jobs in programming provide clinical education equivalent to any academic program.

Paul took night classes in computer science at UMass Boston while working full-time as a programmer for seven years. His jobs rewriting administrative software, programming centrifuges, controlling high-speed cameras, and working alongside PhDs at Data General provided practical knowledge that complemented his academic study.

Paul's day jobs added up to a supplemental course, like clinical rotations in medical school.

mindset

Being a founder requires abandoning the boundary between work and life. Your identity merges with your company in ways that make failure feel personal and success feel incomplete.

Unlike employees who clock out and separate themselves from their job, founders cannot maintain this boundary. Paul found himself obsessed with his companies, unable to disengage even after selling them, and struggling with depression when success arrived because it meant becoming an employee again.

As of tomorrow morning when I wake up, I'm now an employee.

Recognize that technological advancement democratizes opportunity in ways previous generations never experienced. A person with the right skills can rise regardless of family background or social class in knowledge-based fields.

Paul's rise in technology allowed him to succeed despite not coming from Boston's Anglo-Saxon elite families. Unlike the construction industry where politics mattered, software required only belonging to what Donald Knuth called the 2 percent of people born to program, making class and connections irrelevant.

Do not conflate personal mental health with professional success or failure. A company setback or personal crisis does not define your worth, and vice versa.

Paul experienced severe depression triggered by Kayak's successful sale and media attention, not by failure. The book emphasizes that successful people struggle with mental illness in ways that are often invisible to outsiders, and success does not prevent psychological suffering.

Seek clarity about your condition and what you can control. Understanding your symptoms is more valuable than abstract diagnostic labels. Focus on concrete steps to manage impact.

Paul rejected the stigma of bipolar disorder as a label and instead focused on identifying specific symptoms he experienced and testing medications that reduced them. He was pragmatic about treatment, discontinuing lithium when it flattened his energy even though it helped with depression.

The labels are kind of dumb and meaningless because no one really knows how the mind works.

Code offers a refuge where you maintain complete control. Unlike human relationships, computers respond predictably to your commands and don't argue or ignore you.

Growing up in a chaotic household with seven siblings, Paul found programming to be a solitary world where he was entirely in charge. In his basement room at any hour, he could create universes within code where there was no time but the present and no place but the small system he was building.

In his basement room it could be of any time of day or night and when he was coding or watching a message being painted on his screen he felt as though there was no other time than now and no other place but the small universe he was creating in his current program.

operations

Keep meetings small and time-conscious. Interrupt unproductive meetings by visibly signaling that fewer people and less time can solve the same problems.

Paul would pop his head into large, long meetings and suggest that three of the dozen people present could solve the problem in half the time. He hung a tally clicker outside the main conference room as a visible reminder of his expectation for smaller gatherings.

I'm paying attention. I want meetings of three people, not 10.

resilience

Program yourself out of depression through focused work. When facing setback and despair, channeling energy into building something tangible can restore momentum and identity.

After turning down Yahoo's acquisition offer and experiencing three years of depression, Paul worked part-time as a programmer earning $80 an hour. He gradually built Boston Light Software through a contract with the Boston Globe, and this act of creation restored his sense of purpose and capability.

He had programmed his way out of depression.

View mental illness not as a complete liability but as a condition with managed symptoms and untapped capabilities. Even significant psychological challenges do not preclude building successful companies and creating value.

Paul was diagnosed with bipolar disorder and spent 30 years managing episodes of hypomania and depression through medication, trial and error, and occasional abandonment of treatment. Despite struggling with mental illness, he founded multiple companies, one acquired for $1.8 billion, and earned $120 million.

What's really important is what are the symptoms you're having and are they that bad? And then what things can we do to make those symptoms be less?

sales

Negotiate aggressively by studying how others do it. Watch successful negotiators operate and apply their tactics in your own high-stakes situations.

Paul learned negotiation by observing his father at yard sales, where his dad would disarm sellers with humor, throw out absurdly low numbers, and let the unexpected offer create the anchor point. Years later, Paul used this same playbook to negotiate Boston Light's sale from $0 revenue to $33.5 million.

strategy

Ideas are cheap. Multiple failed attempts across decades can be justified if one or two succeed spectacularly. A 2 percent success rate can fund a lifetime of exploration.

Paul had approximately 50 different ideas throughout his career, with 15-20 actually being started as companies, apps, or divisions. Most failed, but two significant successes (Boston Light and Kayak) more than compensated for all the losses, teaching that portfolio approach to entrepreneurship.

Build for a big market with clear demand. Even ideas that seem unconventional can succeed if they address massive customer pain and you have the technology to execute.

Addison Gage harvested ice from Massachusetts ponds and shipped it worldwide to warm climates before refrigeration existed. The enormous market demand in hot countries justified the logistics. This historical example taught Paul that vision and market size matter more than an idea seeming obvious upfront.

No matter how wacky an idea can succeed if it aims at a big market, all those hot places without refrigeration, and if there are technologies to execute it.

Frameworks

The Revenue Visibility Framework

Display metrics that connect work directly to economic value in real-time and prominently. Show team members the output of their labor in quantifiable form (searches, transactions, revenue generated) so they understand the relationship between coding and company value. This maintains motivation and clarity during scaling.

Use case: For scaling software companies that need to remind engineering teams of customer impact and business model mechanics.

The Meeting Interruption Protocol

Observe meetings opportunistically and interrupt ones that are too large or too long. Use visible signals (tally clickers, walking in, making suggestions) to set expectations about meeting efficiency without formal policy. This creates cultural pressure toward smaller, faster meetings.

Use case: Maintaining meeting discipline in growing organizations where meetings proliferate and expand in size.

The Recurring Collaboration Model

Recruit the same core team members across multiple ventures over decades. Build trust through shared previous failures and wins. When you start a new company, reach out to people who have worked with you before, even if the previous venture failed. They already understand your style and vision.

Use case: For serial entrepreneurs who start multiple companies and want to maintain institutional knowledge and trust without constantly building new teams from scratch.

The Observational Negotiation Technique

Learn negotiation tactics by studying how others operate in informal settings (yard sales, casual transactions). Observe the sequence: disarming opener (humor), shocking anchor number, letting the other party find stability in the unexpected offer. Apply these tactics in formal negotiation.

Use case: Preparing for high-stakes deals when you lack formal negotiation training. Learn from observation of skilled negotiators in low-stakes contexts.

The Via Negativa Approach

Define success not by what to add but by what to subtract. When things are not working, the solution is to eliminate wrong activities rather than add more. Stop doing the wrong things first, then watch the right things catch up.

Use case: When scaling stalls or depression sets in, use subtraction (leaving jobs, killing projects, abandoning ideas) rather than addition as your primary strategy.

Stories

In seventh grade, Paul bought a dime bag of marijuana for $10, resold it for profit, scaled to an ounce, and stored it in his attic in a WWII munitions box. He never got caught and quit after a year. By eighth grade, he had earned enough to buy several used cars if he had been old enough to drive.

Lesson: Entrepreneurial instinct emerges early in people who become founders. Recognizing market opportunity and scaling operations is a pattern, not learned behavior. Successful founders often show these traits in childhood before they have any business training.

Paul worked as a musician and thought that was his path until a computer science professor displayed an algorithm on the board. Paul realized his own algorithm was shorter and faster. He thought, I'm way smarter than this guy, and decided to pursue programming full-time.

Lesson: A moment of clarity about your relative advantage in a field can redirect your entire career. Paul's switch from music to programming came from a single comparison that revealed he had aptitude for coding that exceeded his teaching peers.

After Netcentric failed, Paul spent three years depressed and nearly broke, working part-time as a programmer for $80 an hour. He gradually built Boston Light Software through a $50,000 contract to improve the Boston Globe's website. The act of creation restored his sense of purpose.

Lesson: Depression can be overcome through sustained creative work. When stuck in despair, focus on building something tangible with your skills rather than waiting for motivation. The process of making something often restores the mindset you need.

Paul's negotiation for Boston Light started with a $40 million ask when the company had $50,000 in revenue and no profitability. The Intuit negotiator said, are you fucking kidding me? She hung up. Paul called back, acknowledged the ridiculousness, but held firm saying he was negotiating with four other companies. They ultimately agreed to $33.5 million.

Lesson: Anchor high even if dismissed immediately. The opening bid sets the range. Coming back with conviction and mentioning competition shifted the negotiator's perception of Paul's BATNA. Never let an initial rejection kill the deal.

Paul told his elderly father he had sold his company for $33.5 million. His father, a man who prided himself on never being fazed, visibly lost his composure and asked, Who negotiated for you? When Paul said he did, his father asked, How do you know about negotiating? Paul replied, Dad, it's exactly what I saw you do at yard sales.

Lesson: Your parents teach you through observation more than instruction. Paul spent years watching his father disarm sellers, anchor absurdly low, and close deals. He applied this exact playbook decades later in high-stakes corporate negotiation.

Paul and colleagues booked flights from Boston to Los Angeles on September 11, 2001, but switched to a less expensive itinerary at the last minute. The original flight was American Airlines 11, which crashed into the North Tower.

Lesson: Luck plays a role in outcomes beyond your control. Paul's decision to save money on airfare that day was arbitrary and could have been fatal. Survivors often downplay how chance events shaped their success.

Notable Quotes

Fuck you. I will never do homework.

At Boston Latin School, the headmaster warned that one in three students flunk out and that four to six hours of homework a night is expected. Paul's internal monologue rejecting this authority.

I'm paying attention. I want meetings of three people, not 10.

Paul's message when hanging a tally clicker outside the main conference room at Kayak to signal his expectation for smaller, more efficient meetings.

No matter how wacky an idea can succeed if it aims at a big market, all those hot places without refrigeration, and if there are technologies to execute it.

Reflecting on how Addison Gage's ice harvesting business succeeded by targeting a massive market (hot countries without refrigeration) with proven technology (insulated shipping).

It's a funny thing about mania. It feels so good that when it is with us, we feel cured feel cured perfect and we don't want the meds anymore.

Reflecting on the challenge of medication compliance during hypomanic states when the high feels so good that treatment seems unnecessary.

What's really important is what are the symptoms you're having and are they that bad? And then what things can we do to make those symptoms be less?

Paul's pragmatic approach to mental illness: focus on observable symptoms and manageable interventions rather than abstract diagnostic labels.

In his basement room it could be of any time of day or night and when he was coding or watching a message being painted on his screen he felt as though there was no other time than now and no other place but the small universe he was creating in his current program.

Explaining why Paul retreated to programming as a solitary refuge where he maintained complete control and presence in chaotic family dynamics.

If someone invented a drug that normal people could take to feel like I feel this morning, the inventor would be a billionaire.

During a hypomanic high, Paul describing the euphoria and energy he experiences, highlighting why treatment compliance is difficult.

One rather curious thing I've noticed about aesthetic satisfaction is that our pleasure is significantly enhanced when we accomplish something with limited tools.

A philosophical observation about why constraining software to limited memory (Atari 2600) created more satisfaction than unconstrained coding.

I love the highs. I can feel the blood racing through my veins and I get a lot done.

Paul expressing the attractiveness and productivity of hypomanic states, which made him question whether treatment was necessary.

As of tomorrow morning when I wake up, I'm now an employee.

Paul's reflection the day after Kayak was acquired by Priceline. Despite selling for $1.8 billion, he was troubled by losing control and independence.

More Technology Founders

Want Paul's advice on your business?

Our AI has studied Paul English's biography, principles, and decision-making frameworks. Ask any business question.

Start a conversation