Article · 8 min read · 2025

Products as infrastructure

The mental shift from 'app' to 'infrastructure' — and what it changes about retention, pricing, and the kind of company you become.

Share

Most founders think they're building products.

What they're actually building… are apps.

And that's the problem.

Because apps get used.

Infrastructure gets relied on.

And the difference between those two determines:

  • whether you get churn
  • whether you can charge properly
  • and what kind of company you become

The default trap

Most products start the same way:

"Let's build an app that solves this."

So the focus becomes:

  • features
  • UI
  • usability
  • onboarding

And if it's good… people use it. Occasionally. When they remember.

Why that model breaks

Apps live on the edge of behaviour.

They depend on:

  • intention
  • memory
  • effort

Which means:

  • retention is fragile
  • engagement fluctuates
  • value feels optional

At any moment, the user can think:

"Do I actually need this?"

And if the answer is no — even once — they're gone.

The reframe

App vs Infrastructure

If you strip it back, there are two fundamentally different product types.

### Apps

Sit on top of workflows. Help complete a task. Improve an experience.

But they are:

👉 optional 👉 replaceable 👉 easy to ignore

### Infrastructure

Sits inside the workflow. Structures how something gets done. Removes friction from the system.

And becomes:

👉 embedded 👉 relied on 👉 difficult to remove

The difference in one line

Apps are something you open
Infrastructure is something that runs

What this changes

This shift isn't philosophical. It's practical. It changes everything about how your product behaves in the market.

What this looks like with BookedIn

BookedIn could easily be positioned as:

a platform to find and book CPD speakers

That's an app. Something you visit when you need something. Something you can replace.

But that's not the real opportunity. The real opportunity is this:

becoming the system behind how CPD gets booked

That means:

  • structuring availability
  • standardising pricing visibility
  • removing back-and-forth
  • enabling comparison
  • increasing reliability

Not occasionally. But every time.

"Should I use BookedIn?"
"This is how we book CPD."

Where most founders get it wrong

They optimise for features, UI, and short-term usage — without asking:

"Where does this sit in the workflow?"

If the answer is "at the edge", you've built an app.

If the answer is "at the centre", you're building infrastructure.

The tension

You can't hide behind nice UI, feature releases, or surface-level value.

You have to actually work. Every time.

Why this matters now

We're entering a phase where:

  • building apps is easier than ever
  • features are increasingly commoditised
  • AI accelerates development

Which means:

👉 apps are becoming cheap

The real advantage shifts to:

👉 infrastructure

The layer that connects, structures, and enables.

The shift that changes everything

Most founders are trying to build better apps.

They should be building infrastructure.

Because apps get evaluated. Infrastructure gets embedded.

What I'm learning

You don't build something valuable by making it better. You build something valuable by making it necessary.
Something people use
Something people rely on

Because apps compete. Infrastructure compounds.

Quick signal
How did this land?
Direct from the Claudiverse

The Console — my personal newsletter, in your inbox.

Long-form pieces, frameworks, teardowns, and the thinking behind what's being built. Stay close to the work — and to what's next.

Latest from the Console
Why the next decade rewards systems thinkers

Read by founders, operators, and people building what's next.

Continue reading