Most founders don’t start their journey delivering milk at 3AM, dodging spiders in suburban Australia, but Geoff McQueen did. Now a four-time founder and former CEO of a $14M ARR SaaS company, Geoff has lived the full arc, from scrappy services work to building, scaling, and exiting a product company and is now building an AI-native platform with WorkSights AI. In a recent conversation on the SaaS That App podcast with hosts Aaron Marchbanks and Justin Edwards, Geoff shared hard-earned lessons on why most SaaS companies struggle to scale, what founders get wrong about growth, and why the so-called “SaaS-pocalypse” is both real and misunderstood.
If your product roadmap keeps slipping, it’s tempting to blame Engineering. The story usually sounds like this: estimates were wrong, velocity dropped, “the team isn’t moving fast enough,” or the codebase must be the issue. Sometimes those things are true. But in most teams, recurring roadmap slip is a planning and decision system problem that simply shows up in Engineering’s calendar.
AI agent” is one of those terms that sounds futuristic, but the practical version is simple: An AI agent is software that can take a goal (like “qualify inbound leads” or “resolve common support requests”), use your business data, and then do steps in your systems—often with minimal human help.
For many teams, the answer is yes—but only when the upgrade is treated as a productized engineering initiative with clear outcomes: security posture, delivery speed, operational stability, and developer productivity.
Delta Systems architect Nolan Alimonti explains how Claude Code and Codex change daily development workflows—and why code review becomes the real bottleneck.
When engineering delivery slows down, the right fix isn’t always “hire more engineers.” This guide walks through high-signal indicators, practical first actions, and the key metrics (lead time, WIP, blocked time, incident load, and decision latency) to confirm what’s really holding the team back.
Decide whether to upgrade or rewrite a legacy Ruby on Rails app using a simple Risk–Value–Time framework. Learn when hybrid modernization wins, when rewrites are justified, and how to choose in 2 weeks.
Most teams budget for the obvious part of an MVP: the design and engineering work to get something shippable. What quietly derails timelines and burns runway are the decisions that never make it into a proposal — around architecture, security, QA, DevOps, billing, and what happens after you launch.
Most SaaS founders think they know how their company is doing. Revenue is coming in, the bank account looks healthier at the end of the month than at the beginning. So everything must be fine, right? Not so fast. Anthony Nitsos, the Founder and Lead Guru at SaaS Gurus, compares it to flying a plane through thick clouds with no instruments. You think you’re above the ground. You feel like the speed is right. But you have absolutely no idea, and that’s a terrifying way to run a company. Anthony joined Aaron Marchbanks and Justin Edwards on this episode of SaaS That App to unpack why finance is the strategic engine that keeps the whole operation from slamming into a mountain nobody saw coming.
If you're building or scaling a software product, these three titles can look interchangeable on paper. In reality, they solve different problems — and choosing the wrong one at the wrong stage is an expensive mistake. A fractional CTO creates strategic clarity part-time. A full-time CTO owns technology as a permanent competitive function. A tech lead keeps your engineers executing at quality. The right answer has less to do with your org chart and more to do with what your business actually needs this quarter.