The CS Café

The CS Café

The churn you are calling budget is often a build

Hakan Ozturk | The CS Café's avatar
Hakan Ozturk | The CS Café
Sep 06, 2026
∙ Paid

The build-vs-buy math just flipped.

More than 1/3 of enterprises have already replaced at least one SaaS tool with something they built in-house, and most plan to build more this year.

You hear it more and more.

A customer goes silent for a few months, and at renewal they tell you they are consolidating tools and building the workflow in-house.

You log it as a budget loss. Leadership asks what happened. The decision was made a quarter ago, and nobody in CS was in the room.

The churn you are calling budget is often a build. And a build you never priced is a renewal you already lost.

I covered the pricing model in a previous post: Outcome-Based Pricing Is Killing The SaaS Renewal Model.

Today I’m focusing on the build side.

The Build Decision Leaves Fingerprints

The customer does not announce that they are building your tool themselves.

They scope it while your health score still reads green. The signals look like ordinary account activity, which is why most teams read right past them.

Here are the 4 tells that an account is drifting toward replacing you, while there is still a quarter left to change the outcome.

  1. The technical buyer starts asking about export and API access

    Framed as a data-portability question, it is the first step of a migration off you. Nobody scopes an exit they are not considering.

  2. The workflow you own gets described as “just a” something

    When a customer flattens your product into a generic noun, they have already decided it is commodity.

    Commodity is what teams rebuild.

  3. The account goes silent right after an internal AI mandate

    A top-down “find what we can build ourselves” directive lands, and your champion stops replying within the week.

    That is evaluation running in the background.

  4. The conversation shifts from outcomes to cost per seat

    When the champion moves from “what can this do” to “what are we paying,” procurement already has the file, and procurement compares you against a build estimate you have never seen.

If two or more of those are live in your book, you have a build-risk account and a clock.

What you do in the next 90 days decides whether the renewal is a confirmation or a fight you walk into blind.

The system that walks you in with the build already priced is below.


Paid members get the full operating system. You walk in with the comparison already made and the internal case for staying already written in their own language. The QBR stops being a value pitch and becomes the moment the customer talks themselves out of the build.

Here is how you can run it this week.

This post is for paid subscribers

Already a paid subscriber? Sign in
© 2026 Hakan Ozturk · Privacy ∙ Terms ∙ Collection notice
Start your SubstackGet the app
Substack is the home for great culture