Welcome back to Pelotalk, an engineering podcast by Pelotech featuring candid conversations about how real organizations build, ship, and run software in production.
In this episode, hosts Kav and Joachim dig into one of the most quietly broken relationships in most companies: the one between finance and engineering. Drawing on client stories – including a $2B e-commerce company that capped its infrastructure to save $10,000 a month and left a million dollars a week on the table – they break down why the two sides talk past each other, the blind spots each one has, and how the sharpest teams turn that tension into a strength.
They cover:
* Why treating your internal engineering team like an agency – with internal contracts, capitalization requests, and negotiated estimates – quietly wrecks trust and outcomes.
* The two broken money mindsets: engineers who treat the company budget like their personal wallet, and those who treat it like Monopoly money.
* The full story behind the $10K/month instance cap that was suppressing $1M/week in revenue.
* Why the factory-and-asset accounting metaphor breaks down for software, and what finance professionals need to understand about what makes software different.
* What engineers should learn about their own business – COGS, CAC, customer lifetime value – and why systems thinking is the career unlock for reaching staff and principal levels.
* Why you can't plan uncertainty out of software projects, and why small bets and short feedback loops beat front-loaded process every time.
* Engineering for change instead of certainty: two-way doors, slack, small batches, and why most "irreversible" decisions aren't.
* What high-trust finance/engineering relationships actually look like – and the "same answer from a different window" test for whether yours is working.
If you care about engineering leadership, finance and engineering alignment, budgeting for software teams, and building organizations that make smarter bets, this episode is for you.
---
Timestamps:
* 00:00 – Cold open: the $10K cost cap that was blocking $1M a week
* 01:00 – Intro: why finance and engineering relationships break down
* 01:24 – Why measuring engineering productivity is so hard (especially in the AI era)
* 02:50 – The mistake of treating your internal engineering team like an outside agency
* 04:00 – Build vs. buy: the questions to ask before writing custom software
* 05:30 – How to run cheap experiments without temporary solutions becoming permanent
* 07:00 – A better way to fund projects: fixed budgets for learning instead of fixed deadlines
* 07:45 – Two broken money mindsets: the personal wallet vs. Monopoly money
* 08:30 – Client story: how saving $10K a month cost a $2B company $1M a week
* 10:30 – Why engineers shouldn't have to balance cost, business, and feasibility alone
* 12:45 – Why factory-style accounting doesn't work for software projects
* 14:00 – The business metrics every engineer should understand: COGS, CAC, and customer lifetime value
* 15:30 – How systems thinking helps engineers reach staff and principal levels
* 17:45 – Why software estimates fail: the uncertainty no amount of planning removes
* 18:55 – Small bets and short release cycles: making uncertainty less damaging
* 20:30 – Engineering for change, not certainty: small batches, slack, and early automation
* 24:20 – Two-way doors: why most technical decisions are reversible (and cheap to redo)
* 26:20 – How to validate a bet at the lowest possible cost before investing big
* 28:55 – What the best finance and engineering partnerships look like
* 30:40 – The "same answer from a different window" test for a healthy org
