Are you comparing external software engineers or agencies by their hourly rates? In this episode, I explain why that can be one of the most expensive mistakes in software buying.

A lower rate can change the staffing mix, increase the number of billed hours, and add uncertainty that is invisible in the first offer. I have worked on both sides - as a freelancer and consultant, and as the manager hiring external teams - so I break down what rate negotiations actually change.

You will learn:

• Why the lowest hourly rate can produce the highest final cost
• What happens when an agency has to recalculate after a discount
• When hourly comparisons are valid and when they are fiction
• Why providers charge for uncertainty and difficult collaboration
• The body-lease exception, and how to negotiate it intelligently
• What to evaluate instead of just the hourly rate

Code Meets Business is where I explain technology, product, and business without the jargon wall or corporate theater.

In this episode, I give the uncomfortable answer: yes, but not as a full-time individual contributor. A CTO needs enough hands-on technical fluency to build, ship, inspect, and challenge real technology without becoming the engineering team's bottleneck.

You will learn:

• Why reading about technology is not the same as building it
• The difference between technical fluency and stealing work from your team
• The practical minimum bar for a CTO
• Why AI makes engineering judgment more important, not less
• How to spot architecture theater before it becomes an expensive decision

Code Meets Business is where I explain technology, product, and business without the jargon wall or corporate theater.

What is technical debt, and how much is it costing your company?

In this episode, I break technical debt into three types: the obvious shortcuts you choose, the hidden work that catches you later, and the ignored debt everyone knew was coming but nobody budgeted for.

Technical debt is not just a code problem. It is a business cost created by complexity, maintenance, and decisions that feel convenient today. I explain how product choices, technical architecture, and team habits can make that future bill larger or smaller.

You will learn:

• The difference between obvious, hidden, and ignored technical debt
• Why no digital product is ever completely free of maintenance cost
• How AI can reduce documentation pain without eliminating complexity
• Why every edge case can become an expensive long-term decision
• What leaders should budget for before they call a product "done"

Code Meets Business is where I explain technology, product, and business without the jargon wall or corporate theater.

Most companies are not failing at AI because the models are weak. They are failing because they have no guardrails, they pour AI into broken work, and they use a language model as an expensive calculator. In this CPTO Roast, Jens breaks down his current top three AI adoption failures.

You will learn:

• Why every department shipping its own AI tools is a production incident waiting to happen
• Why sandboxing intern experiments is not optional
• Why AI on broken processes and unread reports creates noise, not ROI
• When not to use an LLM at all
• Why real agents take months of setup, not a two-day trial

Code Meets Business is where a real CPTO explains technology, product, and business without the jargon wall or the corporate theater.

Your engineering team asks for refactoring. No new feature. No shiny launch. Should you pay for it?

I break down the three reasons software needs this invisible work:

• Cleanup: the warehouse that grew over time and now slows every change
• Deliberate shortcuts: the house built without the floor needed for the next feature
• Modernization: a living system adapting to changing dependencies, security, and external services

Then comes the business decision: the good, the bad, and the ugly. Keep valuable systems healthy. Reject overengineered "we might need it later" platforms. And when you deliberately accept risk in a low-criticality system, make the cost visible instead of pretending it does not exist.

Code Meets Business is where a real CPTO explains technology, product, and business without the jargon wall or the corporate theatre.

What is a CPTO - and why are companies rethinking the split between product and engineering leadership? In this episode, Jens explains what a Chief Product and Technology Officer actually does, why the CTO/CPO divide creates expensive trade-offs, and why AI makes shared product and technology accountability more important.

You will learn:

• What a CPTO is and when the role makes sense
• Why CEOs often become the human API between product and engineering
• How AI changes the relationship between product management and engineering
• How to recognize or hire a strong CPTO

Code Meets Business is where a real CPTO explains technology, product, and business without the jargon wall or the corporate theatre.