# Custom Dev Tooling: From Out of Reach to Non-Negotiable — Pilot to Production

> Bespoke internal tools used to cost a team-quarter. Now they cost an afternoon, so not building your own rails is the expensive choice. The new math.

Canonical: https://thegrowthproject.com/podcast/custom-tooling-now-mandatory/

*Pilot to Production*, the Growth Project podcast — hosted by Sam and Maya.

- Listen: https://thegrowthproject.com/podcast/custom-tooling-now-mandatory/
- Read the article: https://thegrowthproject.com/blog/custom-tooling-now-mandatory/
- Audio: https://thegrowthproject.com/audio/podcast/custom-tooling-now-mandatory.m4a?v=422d5ab2

## Transcript

**Sam:** [emphasis] A tool that used to need a team and a quarter now takes an afternoon.

**Maya:** And most teams are still pricing it like it's 2015. They're paying forever to dodge a one-day build.

**Sam:** Welcome to Pilot to Production, from the Growth Project. I'm Sam.

**Maya:** And I'm Maya. Today: why not building your own tools just became the expensive choice.

**Sam:** Okay, hold on. For fifteen years, the answer to "should we build this ourselves" was almost always no. And that was the right answer.

**Maya:** It was. Building a small internal tool meant pulling an engineer off revenue work. A spec, a sprint, a code review, a deploy. And then the part nobody budgets for.

**Sam:** [fast] Owning it forever.

**Maya:** Owning it forever. A bespoke tool was a liability with a maintenance bill attached. So you bought instead.

**Sam:** You find the SaaS that covers eighty percent of what you need, sign the contract, and absorb the other twenty.

**Maya:** Right. And that twenty percent is where the whole cost lives. You never see the invoice for it.

**Sam:** [fast] Because it's not on the invoice. So where does it show up?

**Maya:** As the extra step in every workflow. The export-reimport dance between two tools that don't talk. The status field that doesn't match how your team works, so everyone keeps the real status in their head.

**Sam:** And the report you rebuild by hand every Monday because the dashboard shows nine metrics and you need one.

**Maya:** That's the one. None of it is fatal. All of it is permanent. You paid for the contortion in a currency that never appears on a P and L.

**Sam:** Friction, compounding, forever.

**Maya:** The math made sense, because building was genuinely expensive. The math was correct. It's just no longer correct.

**Sam:** So what actually changed? Be precise, because I've heard a lot of "AI changes everything."

**Maya:** Narrower than that. The cost of a small, sharp tool fell off a cliff. Not the cost of a platform, not the thing you'd sell. The internal rail that does one specific job for your specific team.

**Sam:** The script that turns a two-hour Tuesday ritual into a button.

**Maya:** Exactly. That category used to start at a team-quarter. It now starts at an afternoon. And when the build cost approaches zero, the whole equation inverts.

**Sam:** [fast] Inverts how?

**Maya:** [emphasis] You're no longer weighing a quarter of engineering against a subscription. You're weighing one day against a friction tax you pay every working day until you quit the tool.

**Sam:** And this isn't the "AI replaces engineers" story.

**Maya:** No. The expensive part of small tooling was never the hard thinking. It was the grind. Scaffolding, plumbing, the tenth CRUD form, the integration boilerplate. That grind collapsed. The judgement about what to build, and whether it's worth owning, is still entirely yours.

**Sam:** So the temptation, the second people accept this, is to overreach. If building is cheap, build everything. Replace the CRM. Build a platform.

**Maya:** [fast] Don't. That's the addition trap wearing a new hat. The win isn't building big systems cheaply. It's building small, sharp ones that fit your exact process.

**Sam:** [emphasis] Chisel, not Swiss Army knife.

**Maya:** One thing, for your team, the way your team works. No roadmap, no settings page, no second user persona. And because it's small, it's cheap to throw away when the process changes.

**Sam:** That's the part that surprises people. SaaS makes you marry the tool.

**Maya:** A sharp internal tool is disposable by design. When the workflow shifts, you don't file a feature request and wait two quarters. You rebuild the chisel in another afternoon.

**Sam:** But you said it isn't free. There's a catch.

**Maya:** There's a catch nobody mentions. Cheap to build is not the same as safe to run. A tool you stand up in an afternoon still has to be one you can trust on Monday.

**Sam:** That's the vibe coding versus vibe engineering line.

**Maya:** It is. One accepts whatever the AI produces. The other stays suspicious until the tool has earned trust. The senior-operator judgement about what has to be reliable doesn't get cheaper. If anything, it gets more valuable, because now you can act on it at a tenth of the cost.

**Sam:** Alright. First thing tomorrow. Someone's listening, they've got a workflow full of papercuts. What do they actually do?

**Maya:** List your five daily papercuts. The export-reimport ritual. The report you rebuild by hand. The status everyone keeps in their head. Write them down. That's your friction tax, itemised.

**Sam:** [fast] Then reprice the build.

**Maya:** For each one, ask what it would actually take to build the sharp tool today, not two years ago. The honest number is smaller than your instinct says. Then pick the worst one and build the chisel. One papercut, one tool, one afternoon.

**Sam:** And resist making it general.

**Maya:** Resist every urge. Build it to be thrown away. And before it goes live, apply the trust test. What happens when this breaks? Who notices? What's the fallback? If you can't answer, it's not ready, no matter how fast it was to build.

**Sam:** The line moved, and most teams are still standing where it used to be.

**Maya:** [emphasis] What was discipline a decade ago is now debt. Don't bend your process around the software. Bend the software around your process.

**Sam:** This has been Pilot to Production, from the Growth Project. If you're still pricing your tooling with last decade's numbers, that's the gap we close, at thegrowthproject.com.

**Maya:** [fast] Thanks for listening. See you next time.