In this episode, Jeff Mains sits down with Luv Kapur, a technology leader at Bit who's reshaping how enterprises build software. Luv shares his journey from leading platform engineering at one of Canada's largest pension funds to joining a startup on a mission to help organizations scale development through composability and AI-powered tools.

The conversation explores how AI is fundamentally changing software development—not by writing more code, but by enabling teams to compose better solutions with less custom code. Luv challenges the hype around code generation, arguing that the real bottleneck isn't writing code but translating business requirements into sound architecture and reusing battle-tested components.

Luv also offers a grounded perspective on AI's impact on jobs, the importance of discoverability in component libraries, and practical advice for CTOs building composable organizations.

[0:00] - Episode introduction: AI-powered, cloud-native enterprise development tools

[1:00] - The hidden cost of poor discoverability in internal libraries and how it silently slows high-performing teams

[4:26] - Luv's background: From leading platform engineering at Healthcare of Ontario Pension Plan to joining Bit

[4:47] - The spark for the leap: Believing in the mission of helping enterprises scale development globally

[5:19] - The consistency problem: When products span multiple teams but feel disjointed to users

[6:37] - Building a platform team whose customers are developers themselves

[7:23] - Discoverability as the key problem: Developers couldn't find what already existed

[9:24] - Why inner source software transforms development artifacts into invaluable organizational assets

[11:37] - Viewing your org chart as a dependency graph, not a hierarchy

[15:51] - The AI hype is justified, but code generation isn't the real bottleneck

[17:01] - The bottleneck is translating business requirements into software architecture, not writing code

[18:41] - AI should help us do less work, not more work

[19:27] - Why developers won't lose jobs: There's infinite work, not finite work

[20:19] - Reusing battle-tested components increases quality and reduces surface area for errors

[21:59] - Reducing AI context to dependency graphs and APIs prevents hallucinations

[23:05] - Private enterprise data is the gold mine for AI value

[24:35] - The rise of citizen developers: Non-technical people building with natural language

[26:40] - Empowering citizen developers with internal component marketplaces

[27:19] - How AI changes the build vs. buy equation through faster prototyping

[30:09] - Internal tools will be hit hardest by AI disruption

[34:41] - SaaS companies must align with core business value to stay sticky

[36:19] - The biggest mistake: Equating vibe-engineered solutions with production-ready software

[39:01] - Building AI muscle: Start with clear scoped goals, not vague initiatives

[40:45] - The future: Higher skill ceiling, elimination of junior developer roles, but more opportunities overall

[43:45] - Junior developers must contribute to open source and build visible impact

[44:31] - The one capability every software leader needs: Willingness to adopt AI and keep learning

In this episode, Chris Carter reflects on a pivotal leadership mistake that deeply impacted his team—making a team member cry during a meeting.

Chris candidly shares the emotional aftermath, the lessons learned from his mentor and spouse, and how this experience reshaped his approach to leadership. The discussion offers valuable insights for SaaS leaders on empathy, accountability, and team management.

[0:00] Chris Carter opens up about a critical leadership error: making a team member cry in a meeting.

[0:11] He discusses the emotional toll and the importance of seeking advice from trusted mentors and loved ones.

[0:20] Chris emphasizes the need to treat every team member equally and avoid leading through fear or threats.

[0:55] He highlights the importance of understanding the root cause of performance issues—whether personal or professional—and considering alternative solutions.

[1:10] Jeff Mains asks how Chris made amends and the broader impact on the team.

"I made the mistake one time of making a team member cry. Literally, I made him cry in one of our meetings and I felt horrible afterwards."

"As a leader, you can't lead by fear. You have to work with your team, not threaten them."

"If someone is struggling, try to help them first. If it doesn't work out, replace them quickly but compassionately."

"You never know what's going on in someone's life outside of work. Empathy matters."

1. Lead with Empathy: Understand that your team members are people first, employees second.
2. Seek Guidance: Don’t hesitate to consult mentors or loved ones when facing tough leadership moments.
3. Avoid Fear-Based Leadership: Inspire and support your team rather than intimidating them.
4. Address Issues Directly: If a team member is underperforming, address it quickly and fairly.
5. Consider the Whole Person: Recognize that personal issues can affect work performance—be flexible and supportive.
6. Learn and Grow: Mistakes are inevitable; what matters is how you respond and grow as a leader.

cc@approyo.com

http://www.Approyo.com

https://www.linkedin.com/in/christopher-carter-885159/

X.com/Approyo

The Captain's Keys

Small Fish, Big Pond – https://smallfishbigpond.com/ Use the promo code ‘SaaSFuel’

Champion Leadership Group – https://championleadership.com/

Website - https://championleadership.com/

Jeff Mains on LinkedIn - https://www.linkedin.com/in/jeffkmains/

Twitter -

Happy New Year and welcome back to the SaaS Fuel Podcast! In this episode, Jeff Mains sits down with Leslie Shreve, workload management and efficiency expert, and founder of Productive Day. Leslie shares her proprietary system, Taskology, and dives deep into the real reasons why busy SaaS leaders and professionals feel overwhelmed, despite using the latest tools and productivity hacks.

Together, they unpack the hidden costs of “gray work,” the myth of the infinite workday, and why most task management apps fall short. Leslie offers a practical, actionable framework for regaining control, reducing stress, and making real progress—one atomic task at a time.

The Hidden Cost of Modern Work Chaos

(00:47) – Being busy doesn’t mean being productive. The proliferation of tools and notifications can drain focus and create “gray work.”

Gray Work and Quiet Cracking

(06:00) – “Gray work” is the time lost managing disconnected tools and notes. “Quiet cracking” is when professionals appear composed but are overwhelmed inside.

The Infinite Workday

(09:00) – Without boundaries, workdays can feel endless, leading to burnout. Protecting personal time is essential for health and productivity.

Why Most Productivity Apps Fail

(15:00) – Apps like Asana, Trello, and Notion offer features, but without a clear method, they can overwhelm rather than help.

The Myth of the To-Do List

(22:00) – A to-do list is only useful if it’s complete, digital, and actionable. Paper lists and scattered notes don’t cut it.

The Fast Action Formula & Atomic Tasks

(28:00) – Break projects into the smallest possible action steps, each with a clear what, how, why, and when. This makes progress achievable and reduces stress.

Time Defense vs. Time Management

(35:00) – Protecting time (a “time shield”) is more effective than trying to manage every minute. Block focused time and let others schedule around it.

“Gray work is what happens when you’re chasing after tasks and notes, but nothing feels like it’s getting done.”

“Technology alone won’t save you. You need a method to cut through the noise.”

“Don’t outsource thinking, decision-making, and execution—those are your superpowers as a leader.”

“Atomic tasks are the smallest, most actionable steps. That’s where real progress happens.”

“Protect your time like it’s your most valuable asset—because it is.”

1. Centralize Your Work – Avoid scattered notes and tools; create a single digital hub for all tasks and information.
2. Break Down Projects – Turn big projects into atomic tasks with clear action steps.
3. Prioritize Ruthlessly – Focus on the few actions that truly move the needle, not just what’s urgent.
4. Protect Your Time – Use a “time shield” to block focused work periods and defend against interruptions.
5. Embrace Flexibility – Plans will change; adapt quickly without losing sight of your priorities.
6. Don’t Rely on Tools Alone – Methods and systems matter more than the latest app or hack.