If You're Going to Specialize, How Do You Pick the Right Vertical? Fintech, Healthtech, Proptech—Which One?

OK, so the consensus seems to be: specialization can be valuable, but pick wisely.

That leads to the obvious next question: If you’re going to specialize in a vertical, how do you actually choose which one?

I’m looking at the landscape right now and feeling a bit overwhelmed:

  • Fintech: 18% funding growth, fast exit cycles (3-7 years), massive market
  • Healthtech: $25-30B annual investment, long-term impact, complex regulations
  • Proptech: Real estate tech, huge market, regional variations
  • Climate tech: Growing urgency, government support, mission-driven
  • EdTech: My current space, meaningful work, complex sales cycles

And that’s just the obvious ones. There’s also defense tech, supply chain tech, legal tech, construction tech…

Here’s what I’m wrestling with as a PM

Different verticals have completely different dynamics:

Fintech characteristics:

  • Fast learning cycles (payment flow, you know if it works or fails immediately)
  • High regulatory complexity (PCI-DSS, KYC/AML, state-by-state licensing)
  • Dense ecosystem (every company needs payments)
  • Exit opportunities are strong
  • But: Crowded market, lots of competition

Healthtech characteristics:

  • Long validation cycles (clinical studies, regulatory approval can take years)
  • Extremely high compliance burden (HIPAA, FDA, clinical protocols)
  • Societal impact is massive and meaningful
  • Sticky customers once you’re in
  • But: Sales cycles are brutal, procurement is painful

Proptech characteristics:

  • Tied to real estate cycles (macro-sensitive)
  • Regional variations are huge (every state/country different)
  • Transaction volumes can be enormous
  • But: Consolidation risk, dominated by big players

My framework for evaluating this

I’ve been thinking about it through these lenses:

  1. Personal interest - Will I still be curious about this in 5 years?
  2. Growth trajectory - Is the market expanding or mature?
  3. Skill adjacency - Does this build on what I already know?
  4. Risk tolerance - Am I OK with the volatility/cycles of this vertical?

For me, fintech made sense because:

  • I worked in consulting with financial services clients (adjacency)
  • Fast feedback loops match my learning style (interest)
  • Digital finance is clearly growing (trajectory)
  • I was OK with regulatory complexity (risk tolerance)

But I’m curious about other people’s decision process

For those who’ve chosen a vertical:

  • How did you evaluate the options?
  • What factors mattered most to you?
  • Did you try multiple verticals before committing?

For those still deciding:

  • What’s holding you back from choosing?
  • How do you evaluate growth potential in a vertical?

For leaders:

  • How do you advise people on vertical choice?
  • Are there warning signs that someone’s picked the wrong vertical?

Feels like this is a 3-5 year career bet, minimum. Want to make sure I’m thinking about it the right way and not missing obvious factors.

How do you pick the right vertical to specialize in? :bullseye:

David, this is such an important decision and I love your framework. Let me add the long-term strategic perspective.

Don’t pick based on 2-year trends. Pick based on your 10-year worldview.

When I was making career choices in the early 2000s, I bet on cloud transformation before “cloud” was even a common term. Not because I was brilliant, but because I believed enterprise software would inevitably move from on-premise to hosted services.

That belief shaped 15+ years of career choices and turned out to be correct.

My advice: Pick a vertical aligned with what you believe about the future.

Framework for evaluating vertical potential

1. Problem complexity trajectory

  • Is the problem getting simpler (commoditizing) or more complex?
  • Healthcare: Getting MORE complex (genomics, personalized medicine, AI diagnosis)
  • Payments: Getting MORE complex (real-time settlement, cross-border, regulatory expansion)
  • Web hosting: Got SIMPLER (AWS/cloud made it commoditized)

2. Market size and growth

  • Is the TAM expanding or contracting?
  • Healthcare: Expanding (aging population, digital health adoption)
  • Climate tech: Expanding rapidly (regulatory push, market demand)
  • Legacy on-premise enterprise: Contracting

3. Regulatory moats

  • Does regulation create defensibility or just burden?
  • Fintech/Healthtech: Regulation creates moats (hard to enter, sticky once in)
  • Consumer social: Low regulatory moats (easy to enter, easy to disrupt)

4. Your unique insight

  • Do you see something others don’t about this vertical?
  • If you’re just following the herd, you’re late

My path: Enterprise SaaS infrastructure

I chose enterprise cloud/SaaS in the 2000s because I believed:

  • Companies would move from owning infrastructure to renting it (correct)
  • Software would shift from perpetual licenses to subscriptions (correct)
  • APIs and integrations would become critical competitive differentiators (correct)

Those beliefs turned out right and shaped a valuable career.

Warning signs you’ve picked wrong

  • You’re bored within 6 months - Domain interest matters more than you think
  • You’re constantly explaining why the vertical will succeed - If you’re defensive, you might not actually believe in it
  • Adjacent moves feel impossible - If you can’t see where you’d go next from this vertical, it might be too narrow

Vertical choice is reversible

People overestimate the penalty of choosing wrong. Yes, you’ll invest 2-3 years building domain expertise. But if you pick wrong, you can pivot.

I know VPs who went from:

  • E-commerce → Fintech (payment expertise transferred)
  • Gaming → Healthtech (ML/data science transferred)
  • Media → EdTech (content delivery expertise transferred)

The key: Pick adjacent verticals when you pivot, not completely unrelated ones.

Healthcare → Fintech (healthcare payments) is easier than Healthcare → Gaming.

My recommendation

Evaluate verticals by:

  1. 10-year growth trajectory (not 2-year trends)
  2. Increasing complexity (not commoditizing)
  3. Alignment with your worldview
  4. Personal interest that sustains over years

And avoid overcrowded spaces unless you have unique insight. Lots of people are rushing into AI/ML right now. Unless you have a differentiated perspective, you’re just competing in a crowded market.

Pick the vertical where your unique insights and interests align with long-term growth. That combination is rare and valuable.

Oof, David, I feel this question deep in my bones. :sweat_smile:

I chose wrong once, and it taught me everything about how NOT to pick a vertical.

My mistake: Building in a vertical that bored me

When I started my B2B SaaS company, I picked enterprise project management as the vertical. Why?

  • Big market :white_check_mark:
  • Clear pain points :white_check_mark:
  • Willing to pay :white_check_mark:
  • VC interest :white_check_mark:

What I didn’t consider: Did I actually care about project management?

Spoiler: I did not. :grimacing:

I spent three years learning about Gantt charts, resource allocation, agency workflows, construction project timelines… and I was BORED OUT OF MY MIND.

When you’re bored by your domain:

  • You don’t read industry blogs in your free time
  • You don’t get excited talking to customers
  • You don’t notice the subtle patterns that competitors miss
  • You build what’s obviously needed, not what’s transformatively better

Meanwhile, our competitors were often led by former project managers who LOVED this stuff. They noticed workflow nuances I completely missed. They anticipated user needs I couldn’t see.

Domain interest isn’t a nice-to-have. It’s a competitive advantage.

What I’m doing differently now

I’m specializing in accessibility and inclusive design because:

  • Personal connection: I have family members with disabilities. This isn’t abstract to me.
  • Genuine curiosity: I read WCAG specs for fun (weird, I know :grinning_face_with_smiling_eyes:)
  • Emotional investment: When I make something accessible, it feels meaningful
  • Natural network building: I volunteer with disability advocacy groups, attend a11y conferences

I still spend hours learning technical details (ARIA attributes, screen reader behavior, keyboard navigation patterns). But it doesn’t feel like work because I actually care.

My framework for picking vertical

Before committing 2-3 years, test these questions:

  1. Would you read about this domain in your free time?

    • If no, you’ll struggle to develop deep expertise
  2. Can you name 5 industry publications/blogs you’d follow?

    • If you can’t, you’re not curious enough about the space
  3. Would you attend a conference about this vertical even if your company didn’t pay?

    • Genuine interest shows up in willingness to invest personal time/money
  4. Can you explain why this vertical’s problems are interesting, not just lucrative?

    • If you can only articulate the market opportunity, not the problem’s intrinsic interest, warning sign
  5. Do you know anyone in this vertical you’d want to learn from?

    • Having role models/mentors matters for sustained interest

My recommendation: Try before you commit

Before specializing, try to get exposure to a vertical through:

  • Consulting/contracting - Work with companies in the space for 3-6 months
  • Side projects - Build something small in the vertical to see if it sustains your interest
  • Community involvement - Lurk in industry Slack groups, forums, conferences

If you’re excited after 6 months of exposure, commit. If you’re already bored, pivot.

The emotional sustainability question

David, you mentioned fintech matches your learning style (fast feedback loops). That’s SO important and often overlooked.

Different verticals have different rhythms:

  • Fintech: Fast iteration, immediate feedback
  • Healthtech: Slow validation, long cycles
  • Enterprise B2B: Long sales, delayed feedback

Match your personality to the vertical’s rhythm. I need fast visual feedback, which is why design systems work better for me than enterprise architecture would.

Pick a vertical you’d still be interested in if the money disappeared. That’s the sustainability test. :light_bulb:

David, I love both Michelle’s strategic lens and Maya’s passion-first approach. Let me add the EdTech journey perspective because I think it illustrates why mission + growth trajectory matters.

Why I chose EdTech

I could’ve stayed at Google or Slack (both great companies, strong comp, clear growth paths). Instead, I jumped to an EdTech startup as VP Eng.

The factors that mattered to me:

1. Mission alignment

  • Education equity is deeply personal to me (first-generation college student, HBCU grad)
  • When I explain what I do at parties, I feel proud, not just professionally successful
  • That emotional connection sustains me through hard scaling challenges

2. Technical complexity + social impact

  • EdTech isn’t just “software for teachers”—it’s ML for personalized learning, data privacy for minors, accessibility for diverse learners, scale for millions of students
  • Combines interesting technical problems with meaningful outcomes

3. Growth trajectory

  • Remote learning accelerated EdTech adoption permanently
  • Every school, university, corporate training program needs technology
  • Market growing but not overcrowded (unlike, say, fintech)

4. Career mobility

  • EdTech skills transfer to adjacent verticals: healthcare (patient education), enterprise (corporate learning), consumer (lifelong learning)
  • Not a dead-end specialization

The data I looked at

Before joining, I researched:

  • Market size: Global EdTech market $340B by 2025, growing 16% annually
  • Investment trends: Consistent funding even outside hype cycles
  • Exit opportunities: IPOs (Coursera, Duolingo), acquisitions, sustainable growth
  • Regulatory landscape: More complex than consumer tech (FERPA, COPPA) but clearer than healthtech/fintech

Felt like the sweet spot: growing market, clear demand, not yet oversaturated.

Career path observation

The most successful leaders I know changed verticals 2-3 times in their careers, but with intention:

  • Vertical 1 (years 0-7): Build deep expertise, establish credibility
  • Vertical 2 (years 7-12): Transfer learnings to adjacent space, leverage expertise
  • Vertical 3 (years 12+): At this level, vertical matters less than leadership/strategy

Example: My mentor went from e-commerce → fintech → EdTech. The thread? Building transaction systems at scale with regulatory complexity. She transferred her expertise across growing verticals.

My framework for vertical evaluation

Ask these questions:

Growth potential:

  • Is this a $50B market growing to $100B (EdTech) or a $500B market growing to $550B (enterprise software)?
  • I’d rather own 1% of fast-growing market than 0.1% of massive mature market

Problem density:

  • Are there 100 interesting problems to solve or 5?
  • Healthcare has infinite problem density (genomics, diagnostics, treatment, prevention, admin)
  • Some verticals have 1-2 key problems that get solved, then commoditize

Defensibility:

  • Once you build expertise, are you valuable for years or months?
  • Healthcare knowledge compounds (regulations + biology don’t change fast)
  • Framework knowledge decays (React expertise from 2015 isn’t valuable in 2026)

Transferability:

  • If this vertical stalls, where can you go next?
  • EdTech → corporate learning → healthcare education (clear path)
  • Crypto → ??? (harder adjacencies)

Red flags I watch for

Hype exceeds fundamentals:

  • If everyone’s rushing in but TAM is unclear, be skeptical
  • Crypto in 2021, maybe some AI verticals in 2026

Regulatory uncertainty:

  • If the entire vertical depends on unclear regulations, risky
  • Healthcare has complex but stable regulations
  • Some crypto applications had existential regulatory risk

Narrow winner-take-all dynamics:

  • If 1-2 companies will capture 80% of market, tough for startups/careers
  • Social media had this (Facebook/Twitter dominated)
  • Developer tools have healthier distribution (many winners)

My advice

Pick a vertical where:

  1. You’re genuinely curious about the domain (will sustain 3-5 years)
  2. Growth trajectory is strong (not mature/declining)
  3. You see clear transferable skills to adjacent verticals (career mobility)
  4. Mission resonates with your values (emotional sustainability)

Maya’s right that passion compounds differently than pure skill. And Michelle’s right that long-term worldview matters more than short-term trends.

The intersection of growth + mission + personal interest is where sustainable careers live. :bullseye:

All great perspectives here. Let me add the financial services angle since I’ve lived in this vertical for a while now.

Why I chose fintech/financial services

Your framework resonates, David. Here’s how I evaluated it:

Skill adjacency (most important for me):

  • I started in embedded systems at Intel, moved to software architecture at Adobe
  • Financial systems combined my interests: high-reliability requirements (like embedded) + complex software architecture
  • Payments infrastructure is basically distributed systems with money—fascinating technical challenges

Personal interest:

  • I genuinely find financial systems interesting (how money moves, clearing/settlement, risk management)
  • Reading about payment rails evolution, cross-border transactions, regulatory frameworks doesn’t feel like work
  • That curiosity helped me notice patterns and opportunities others missed

Growth trajectory:

  • Digital payments were clearly growing in 2010s (fintech wave)
  • Every company needs payment infrastructure
  • Regulatory complexity creates moats and job security

Risk tolerance:

  • Financial services is stable (people always need banking/payments)
  • Not as exciting as crypto or emerging tech, but that stability was valuable to me
  • Recession-resistant career choice

The technical depth question

One thing I’d add to your framework: Look for verticals with deep technical problems, not just domain knowledge.

Healthtech example:

  • Surface level: “You need to know HIPAA”
  • Deep level: “You’re solving real-time patient monitoring with ML, genomic data analysis at scale, clinical decision support systems with safety constraints”

The domain knowledge (HIPAA) is table stakes. The technical problems are what make it interesting long-term.

Fintech is similar:

  • Surface: “You need to know PCI-DSS”
  • Deep: “You’re building distributed transactions with exactly-once semantics, fraud detection ML systems, real-time settlement with eventual consistency guarantees”

If a vertical is mostly domain knowledge without deep technical challenges, you might get bored once you learn the domain.

Advice for choosing

Look for the intersection:

  1. Domain complexity - Rich enough to stay interesting for years
  2. Technical complexity - Genuinely hard engineering problems
  3. Market growth - Expanding not contracting
  4. Personal fit - Aligns with your interests/values

Healthcare has all four:

  • Domain: Biology, clinical workflows, health outcomes (infinitely complex)
  • Technical: ML, real-time monitoring, data privacy, scale
  • Market: Aging population, digital health adoption, massive TAM
  • Personal: Meaningful work, helping people

Climate tech has all four:

  • Domain: Energy systems, carbon tracking, sustainability metrics
  • Technical: IoT at scale, optimization algorithms, grid management
  • Market: Regulatory push, market demand, existential importance
  • Personal: Mission-driven, generational impact

Crypto had 2-3 but not all:

  • Domain: Decentralization, consensus mechanisms (interesting but narrow)
  • Technical: Distributed systems, cryptography (genuinely hard)
  • Market: Speculative growth, unclear long-term TAM
  • Personal: Some people care deeply, others just chasing money

The knowledge compounding question

Choose verticals where knowledge compounds over time:

Compounding domains:

  • Healthcare (biology + regulations + clinical practice stack on each other)
  • Financial systems (payments + risk + compliance interconnect)
  • Enterprise infrastructure (distributed systems knowledge builds on itself)

Non-compounding domains:

  • Framework-specific development (Angular knowledge didn’t help with React)
  • Platform-specific expertise (Facebook API knowledge became obsolete)
  • Flavor-of-the-month technologies (remember CoffeeScript specialists?)

Example from my team

I mentored someone who was deciding between two offers:

  • Crypto startup: $200K, cutting-edge tech, hype-driven
  • Healthcare infrastructure: $165K, meaningful work, growing steadily

He picked healthcare because:

  1. Genuinely interested in health outcomes (volunteer EMT)
  2. Saw 10+ years of interesting problems (genomics, personalized medicine, AI diagnosis)
  3. Valued stability and mission over maximum comp
  4. Technical challenges (real-time patient monitoring, data privacy) were fascinating

Three years later, he’s a senior engineer at a health tech company, deeply fulfilled, and the crypto startup folded.

The right vertical is the one where you’d still show up even if the compensation normalized. That’s the sustainability test.

Great discussion, everyone. This is exactly the kind of thinking that leads to sustainable, fulfilling careers. :light_bulb: