There's a vendor relationship I've been thinking about lately. Not because of how much we communicate, but because of how little we need to. The interactions are sparse, almost skeletal. A message every few weeks, maybe a scheduled check-in quarterly. And yet the whole thing works with an efficiency that feels almost suspicious.
Then there's the other kind: the vendor who emails constantly. Status updates, check-ins, clarification questions, follow-ups to previous follow-ups. The inbox fills up. You start recognizing their name before you even open the message. And somehow, despite all this activity, something always feels slightly misaligned.
The difference isn't effort. It's clarity.
When a vendor relationship requires constant email, it's usually because something fundamental wasn't settled at the beginning. The scope is fuzzy. The expectations are implied rather than explicit. The success metrics exist in someone's head but not on a shared document. So the vendor keeps reaching out, trying to course-correct through conversation, asking questions because the answers weren't baked into the initial agreement.
The relationships that hum along quietly are the ones where the groundwork was done upfront. Not through endless preliminary meetings, but through actual clarity. A clear contract. Defined deliverables. Agreed-upon timelines. Metrics that both sides understand the same way. Once those things exist, the email volume drops dramatically because there's less to negotiate in real time.
It's counterintuitive because we've been taught that good business relationships require lots of touching base. More communication equals more attention equals better outcomes. But that's not quite right. What actually correlates with good outcomes is shared understanding. Communication is just the mechanism for getting there. Once you have it, you need less of it.
The vendors who understand this tend to be efficient in a way that feels almost boring until you realize that's the whole point. They send one email instead of three. They include all the relevant context upfront so you don't have to ask clarifying questions later. They propose a meeting only when a meeting would actually solve something, not as a default touchstone.
This matters more now than ever, honestly. Everyone's drowning in email. Attention is fractured. The vendor who can deliver value while keeping your inbox quiet has learned something that vendors who treat email volume as a proxy for engagement haven't. That something is: your time is the actual constraint, not communication.
The trap is easy to fall into from either side. If you're the vendor, constant emails feel like you're staying visible and responsive. If you're the client, you might interpret silence as neglect. But neither interpretation holds up. The vendor who sends weekly status updates that say nothing new isn't being responsive; they're wasting your time. The client who feels neglected by infrequent contact might actually just have an unclear agreement that makes them anxious.
Good vendor relationships have something in common with well-designed software: they minimize friction through clarity. The fewer decisions you have to make in real time, the fewer emails you'll need to exchange. The more explicit the agreement, the fewer surprises that require emergency coordination.
This is worth thinking about the next time you're evaluating a vendor or auditing an existing relationship. Count the emails, sure, but ask yourself what they're really trying to solve. Is this communication volume a sign of responsiveness or a sign that something foundational wasn't clear enough? The answer usually tells you everything you need to know about whether the relationship is actually working.