Jamie Fox

PagerDuty is stuck. 10 straight quarters between $400M–$500M in ARR. And now, growth is just 8% YoY. At this scale, the best SaaS companies are accelerating-not flatlining. Magic number: 0.17 CAC payback: 84 months Share price at all-time lows Some signs of life in FCF and operating margin, but it’s clear: Go-to-market efficiency is the problem. #SaaS #PagerDuty #ARRGrowth #CACPayback #B2B #StartupMetrics #GTMEfficiency

1

Your VP of Sales Just Called: Another $3M Deal Stalled in Security Review The pattern is predictable. Your buyer loves the product, but their vendor risk team asks 47 questions you can’t answer fast enough. The deal goes to a competitor who provided framework-mapped evidence in 72 hours. This isn’t a security problem. It’s an evidence problem. The Reality Enterprise buyers audit against NIST CSF 2.0, CIS Controls v8, and FedRAMP. With 60% of organizations experiencing supply chain incidents, static questionnaires fail. They demand continuous visibility into 3rd, 4th, and 5th party dependencies with auditable evidence. The solution isn’t better security. It’s faster validation. Phase 1: Identity Foundation (Days 1-90) Deploy phishing-resistant MFA (FIDO2/WebAuthn). Implement device trust for managed endpoints only. Automate joiner/mover/leaver workflows. Eliminate standing privileges via just-in-time access. Frameworks: CIS Control 6, NIST CSF PR.AA-01, SOC 2 CC6.1 Evidence: Live access reviews showing zero standing admin credentials. Value: Serves PEOPLE while creating DATA foundation. Phase 2: Supply Chain Intelligence (Days 90-180) Deploy continuous monitoring (SafeSecurity/Panorays) to map vendor dependencies. Integrate SBOM generation into CI/CD. Verify library integrity before builds. Require 30-day subcontractor change notification. Frameworks: NIST SP 800-161, OWASP SCVS, CIS Control 15 Evidence: Dependency graphs showing production libraries. Report Log4j exposure in minutes. Value: Serves DATA and PROCESS through systematic visibility. Phase 3: Architectural Proof (Days 180+) Implement Confidential Computing (AWS Nitro/Intel SGX) to encrypt data in active memory. Partner with FedRAMP accelerators to inherit NIST 800-53 infrastructure controls. Frameworks: NIST SP 800-53 (FedRAMP High), DoD IL5, Confidential Computing Consortium Evidence: Cryptographic attestation proving code integrity and data sovereignty. Value: Serves TECHNOLOGY and BUSINESS by unlocking regulated industries. The CASCADE Pattern PEOPLE: Identity establishes accountability. DATA: Frameworks provide evidence. PROCESS: Automation eliminates overhead. TECHNOLOGY: Architecture guarantees sovereignty. BUSINESS: Alignment accelerates growth. Each layer serves the previous. What This Enables Present evidence, not opinions: - CIS Control 6 proves access discipline - NIST SP 800-161 proves supply chain visibility - Confidential Computing proves data sovereignty - FedRAMP proves federal readiness You cite the standard, demonstrate the control, close the deal. The Question Are your security investments accelerating sales or blocking them? Winners turn six-week reviews into 72-hour confirmations. That’s security serving business velocity. That’s the cascade operationalized. What framework requirement currently blocks your enterprise pipeline? #Cybersecurity #EnterpriseGrowth #NIST #CISControls #B2BSales

8

Premature scaling ramps costs before product-market fit. Cash burns fast. Real case: SaaS firm hired 20 salespeople at $500K revenue—folded in 9 months. Nail PMF first. Break the pattern: Prove 80% retention. Scale one lever at a time. Track unit economics >1x. #StartupLessons #FounderAdvice #ScaleSmart #EntrepreneurLife

2

SaaS CEOs: still struggling to balance automation and personalization? Your buyers expect tailored experiences but your team’s buried under manual workflows. Here’s how one fintech leader is engineering both… without adding headcount. Most CEOs think more automation means less human touch. Totally wrong. Automation isn’t about eliminating humans. It’s about eliminating friction. When banks digitize the loan process, the goal isn't to speed, it’s connection.   You can automate document collection, status updates, and compliance but still keep customers feeling seen. This fintech founder explains how to use rule-based logic to personalize every touchpoint, without reps getting involved. That’s how you build loyalty from first click to funding. SaaS leaders who don’t design around the customer's journey are already losing. It’s not about what your system can do it's about how it feels to your customer.   This guest reveals how even complex loan applications can become intuitive, conversational experiences.   The playbook? Use automation to deliver proactive value, reassure the customer, and remove the guesswork. Most SaaS platforms are reactive. The winners automate for anticipation. ✅ The “invisible automation” tactic that delights customers (without them knowing it’s automated).   ✅ Why loan abandonment rates drop when you personalize one overlooked step.   ✅ How to eliminate 80% of customer questions before they ever have to ask. 🎧 Want to see how fintech leaders are redefining customer experience through automation? Watch the full podcast with Molly Borst → Link in comments What’s one area of your SaaS product that could benefit from invisible automation today?

2

1 Comment

Profitability isn’t a growth lever. PagerDuty’s story shows a profitable SaaS business can still stall when expansion slows. ARR around $500M, up ~3% YoY, with NRR at 100% and a roughly flat base of about 15k customers for years. That combo reminds us that efficiency matters, but investors still link value to durable growth. A big TAM claim (about $50B) doesn’t help if penetration remains near 1% and growth stays in the low single digits. Outbound lesson: balance expansion within existing accounts and new-logo velocity, and watch NRR as a leading indicator. In practice, that means thoughtful ICP focus, retention-driven messaging, and staged plays that target both pipeline quality and renewal upside. How does your program balance new logos vs. expansion today? #B2BSaaS #Outbound

1

The "per seat" business model is officially dead for CRMs. For the last 20 years, the logic of SaaS pricing was simple. You build a database, and you charge companies for every human who logs in to update it. The model aligned perfectly with growth. As a company hired more people, Salesforce made more money. But in an AI-first world, this alignment breaks. The promise of AI agents is that they do the work for you. They update the CRM, they qualify the leads, and they manage the pipeline. If the AI works, you should need fewer humans logging into the system, not more. This creates a massive conflict of interest for incumbents. As a result, we are seeing a divergence in business models: - Legacy Incumbents (Salesforce, HubSpot): Incentivized to keep your headcount high so they can charge for access. - AI Challengers (Clarify, etc.): Incentivized to lower your headcount so they can charge for outcomes. The incumbents are trapped. They cannot pivot to outcome-based pricing without cannibalizing their existing revenue base because they are punished for making you efficient. They have to keep selling you "seats" even as the world moves to "agents." This is how I believe startups are going to disrupt legacy monopolies. They will commoditize the core software that incumbents rely on for revenue, and they will monetize the one thing the giants can't. The disappearance of work. P.S. Patrick Thompson breaks down the economics of this shift (and how he is betting against Salesforce) in our latest episode - https://lnkd.in/eTe6bd-3

36

9 Comments