Who is the Customer, Really?

Spend enough time inside a growing SaaS company and you’ll hear the same phrase over and over:

“We just closed another logo.”

I know what people mean. I still hate it.

Not because the shorthand is wrong, but because it’s lazy! A logo is a visual artifact. A customer is a relationship. When we collapse the latter into the former, we lose signal—and that loss shows up later in messy churn analysis, confusing expansion stories, and metrics that feel right until someone asks a follow-up question.

This post is about why defining the customer actually matters, why I believe the MSA is the cleanest unit of definition, and the tradeoffs that come with being more precise than comfortable.

---

Why “Logos” Break Down

Calling something a “logo” works fine at the surface level. It stops working the moment complexity shows up.

Large organizations rarely behave like a single customer. They have:

• Multiple buying centers

• Different budgets and economic owners

• Different problems they’re trying to solve

• Different renewal and expansion paths

Yet we treat all of that as one win because it fits neatly into a slide.

The result? We blur together relationships that behave very differently. When one part of the organization expands and another stagnates, we don’t know why. When something churns, we argue about whether it “counts.” When ARR holds steady but customer count drops, the narrative starts to wobble.

None of that is a reporting problem. It’s a definition problem.

Defining the Customer at the MSA Level

The cleanest fix I’ve seen is also the least glamorous: define a customer as a distinct MSA-governed relationship.

An MSA is objective. It exists or it doesn’t. It defines scope, responsibility, and commercial terms. Most importantly, it represents a real, economic relationship—not a brand name.

Once you anchor on the MSA, a few important things happen.

1. Relationships become quantized into clear, defensible units. Your customer count isn’t a vibe anymore; it’s a set of contracts. ARR rolls up cleanly. Churn has an actual denominator. Finance, sales, and leadership are finally talking about the same thing.

2. It forces sales and go-to-market teams to focus on relationships instead of corporate umbrellas. In practice, that often means maintaining multiple CRM records under the same parent organization. That feels inefficient—until you realize each record represents a different buying motion, stakeholder group, and success definition. Each one deserves attention on its own terms.

3. It acknowledges an uncomfortable truth: different parts of the same company often have very different needs. Treating them as one customer leads to one-size-fits-none implementations and missed expansion opportunities. Treating them as distinct relationships gives you clarity on what’s working, what’s at risk, and where growth actually lives.

The Upside: Clarity and Expansion

Yes, this approach usually increases your customer count. That tends to make people uneasy.

It shouldn’t.

If one “logo” becomes three MSAs, you didn’t inflate anything—you finally counted reality correctly. This is especially powerful in land-and-expand models, where growth comes from entering new buying centers over time. Each MSA becomes a clean landing point with its own expansion curve, rather than noise buried inside a monolithic account.

You also get cleaner retention and expansion math. Instead of asking why a logo is flat, you can see exactly which relationship is stalling and which one is accelerating. That’s the difference between storytelling and insight.

The Tradeoff: More Operational Friction

There’s no way around it: this creates more work.

Multiple MSAs mean more legal coordination, more CRM records, and more internal discipline. Sales ops and finance carry additional overhead. It’s the main reason teams resist this model.

While it is more effort to track this, the real question is whether you’d rather pay that cost upfront or pay it later in confused metrics, awkward board conversations, and decisions made on partial truth.

At scale, clarity is almost always cheaper than ambiguity.

The Bottom Line

Defining the customer is foundational.

Every downstream metric—ARR, NRR, churn, CAC payback—rests on that definition. If it’s fuzzy, your conclusions will be too.

An MSA-based definition isn’t flashy. It’s disciplined. It forces honesty about how customers actually behave and how growth really happens. While it introduces complexity, it introduces a nuanced truth rather than a convenient fiction.