Lazy Leverage

← Lazy Leverage29. Sept. · 50 Min.

I Would Not Spend $50,000 on a Front End. (Do This Instead) | Lazy Leverage #128

I Would Not Spend $50,000 on a Front End. (Do This Instead) | Lazy Leverage #12829. Sept.50 Min.

We mention a lot of books on this show and never write them down. Fixed that.61 books, 39 essays, 88 episodes, free: https://lazy-leverage.saganpassport.com/

Jon's Airtable had one job description copied 135 times, once for every row. Some of it was written by people and some by AI summaries feeding off other fields, because whenever somebody needed a new thing they added a column.

Peter runs his Airtable with an iron fist and makes people justify every new field to him personally. Jon lets it sprawl and then goes in with a weed whacker. They land in the same place anyway. Jon tells his one remaining coaching client that he would not put a dime into an application layer right now, and would put all of it into the data underneath.

In this one: why venture-backed companies build for scale first while everyone else builds for whatever answers today's question. The five terms that made this click for Jon, including ETL and reverse ETL. Why Peter's market rent lives in three systems that never update each other, and what an owner sees on the portal when they disagree. Why Jon turned down a real recruiting system a year and a half ago and says he would be in trouble now if he had not. Peter's three rules for a software stack. And the three grand a month hire he thinks non-technical companies are all about to make.

Chapters:00:00 - Intro00:51 - Welcome to Lazy Leverage03:00 - Why a Data Episode Pays05:39 - Venture Builds for Scale, You Built for Profit08:04 - The Same Job Description 135 Times12:24 - Brought to You by Sagan Passport13:42 - The Plain English Definitions15:38 - The Market Rent That Lives in Three Places19:21 - Do Not Spend 50 Grand on a Front End22:47 - Why Jon Refused to Buy an ATS28:11 - All Business Software Is Just a Database33:35 - Put a Developer on Staff35:43 - The Five Problems Behind One Good Search38:06 - Peter's Three Rules for Your Stack42:58 - Who Gets to Pick the Software

References Mentioned in This Episode -

Books:Pollan, M. (2008). In defense of food: An eater's manifesto. Penguin.

Quotes Referenced:Michael Pollan, "Eat food. Not too much. Mostly plants." Peter cites it as the shape he wants for his own three rules.

People & Frameworks Cited:Source of truth, system of record, and application layerETL and reverse ETLPeter's three rules: limit where data lives, favor open and free APIs, permit no duplicationPolicy, process, tech, with tech lastThe walled gardenVectorizing a candidate database so keyword search stops missing