The Rival Summer Camps

If you grew up on '80s and '90s summer camp movies, you know the trope: two camps on opposite sides of a lake, one full of preppy jocks, the other full of nerds, and the nerds getting one over on the jocks through gumption, grit, and resourcefulness. That is what these companies feel like from inside. Past a certain headcount, past a certain square footage, product and go-to-market stop being co-located. Different floors, different buildings, eventually different cities. The salespeople are on the phone all day. Customer success and support are on the phone all day. The engineers are never on the phone. Each camp develops its own heroes, its own scoreboard, its own inside jokes, and the lake between them gets wider every quarter.

The trade across the lake is where it breaks. When a rep and an engineer finally talk, they are not speaking Italian and Brazilian Portuguese, two languages close enough that an Italian can move about Brazil and be fine. These two languages don't share roots, because they were built to express different things. One is built for deals: stages, dollars, timelines, proof. The other is built for craft: systems, tradeoffs, elegance, impact. So when the rep says "$5K MRR on the line," they have said something precise and meaningful in their own language, and what arrives on the far shore is "I am greedy."

To translate a language you have to know what its speakers use it to say, and underneath both of these languages is the same sentence: evidence that I belong here.

Everybody is seeking place, purpose, and belonging in a community. It is the most fundamental human wiring there is. It is why people of extraordinary intelligence will mention Mercury being in retrograde with a straight face. We looked up at the stars, decided a cluster of them was shaped like an animal, learned which animal was overhead when we were born, and concluded that we are that animal and behave as it behaves. That is a species desperate to know where it fits. Am I supposed to be here? What am I supposed to be doing? In America, for better or worse, the job answers those questions, and performance in the job takes a principal role in how we define ourselves. Go to a cocktail party full of strangers and the first question is what you do, and everyone is sizing everyone up by the answer.

Now put the two camps against that wiring. On the sales side of the lake, the W-2 matters. People need to feed their families, and the variable check is real money. But the number matters even more as proof of belonging. The best thing that can happen to you in sales is to be a top performer on a winning team: the scoreboard announces, in public, that you belong here and the tribe is glad you came. On the engineering side, that mechanism doesn't exist. When the engineer at the next desk gets a pay bump, you do not think more highly of them. Money proves nothing to this tribe. Belonging in engineering is earned by doing something that makes the best people you know look over and nod, the economy of coolness from Chapter 2.

So the rep prices everything in deals because deals are how worth is proven at their camp, and the engineer hears greed because at her camp invoking money for status would be gauche. Nobody in that exchange is wrong about their own culture. They are wrong about each other's.

I have heard more than one engineer reason their way, in so many words, to the conclusion that the salespeople are unnecessary. They're hanging out, high-fiving, having fun. They don't write software. PagerDuty never wakes them at 3 AM. The product is getting pretty good, so they're basically order takers. And did you see the comp figures in that finance review?

Here is what a salesperson actually does all day: they get told no, over and over and over again.

An engineer hears that and immediately says, I don't like that. Correct. Now do six hours of calls and twelve hours of research, calling in favors, asking questions, annoying the engineers, all to prepare for one conversation, and have the person on the other end say: we're going in a different direction. It's no longer a priority. We went with a competitor. Then do it again tomorrow, and the day after, for a living. It is emotionally exhausting to be in sales. Respect that, before any machinery, before any mechanics, before a single integration or dashboard.

There is a selfish reason to do this too. Mastery of what actually happens on the phone with a prospect is the most obvious goldmine of information available to a product manager, and it extends directly to support calls and renewal calls. Yet walk into one of these public companies around town, grab a PM, and ask what happens at the other camp on a Tuesday. They don't know. They have never watched a deal die. They could not name the three objections their own product's pitch hits every week. Understanding what is difficult about a role that is not yours is among the most useful things you can do at work, and almost nobody in product does it.

The classic prescription is shadowing: headset on, extra chair pulled into the pod. Do it if you can; nothing replaces watching a no arrive in real time. If it isn't practical, your company's calls are recorded, and the recordings can be searched, clipped, and grouped by theme, so "every objection about pricing on sales calls in the last thirty days" is a question you can simply ask. This chapter's video walks through it.

What you will find is not a horror show. You will find people talking about your product well, often better than you expected, and hitting gaps they cannot answer. You will find the silence after a prospect asks for something the product doesn't do. You will find a rep absorb a no with grace at 4:40 and dial again at 4:45.

If you did nothing else in this entire course but come to understand a day in the life of a salesperson, you would be unrecognizably closer to being a revenue-oriented product person. Get out of the crystal castle.

The shock of that understanding is necessary. If you don't know where somebody is coming from when they speak another language, you will never understand what they are saying, no matter how carefully they say it.

So run the scene from the top of this chapter again. The rep gets off the elevator and says: I have a $5K MRR deal on the line, and I have a question. Nobody laughs now. You are not assuming greed, because you know what a deal costs the person carrying it and what the number means at their camp. They are speaking their native language of proof: this matters, and the evidence is stated in the units they trust. What they have carried up the elevator is a customer with money ready who cannot buy, which is among the most valuable sentences that ever crosses the lake.

This attitude adjustment is the prerequisite for everything in the next two chapters, the shared language and the transparency machinery. In my experience it may also be sufficient: teams that got this far and built nothing at all still worked differently within a month. Attitude is a choice, and this one is available to you the moment you close this chapter and open five call recordings.

1. Run the prompt and read the prospect it builds. A rep spends hours preparing for one conversation; you get ten minutes.
2. Take the call, about twenty minutes, answering every objection as if the deal were yours, until the prospect says no or you run out of answers.
3. After the debrief, write one short page: what it felt like, which objections landed hardest, and what you'd want from product if this were your job tomorrow. No feature proposals. This week you're learning what a no costs, and planning the fix gets in the way.
4. Keep the page; Chapter 12 asks for it. If you can, sit in on one live call this week and set it beside yours.

Paste this into whatever AI you work in, ideally one connected to your company's material: Claude Code in a company-brain folder, Cowork, Codex, or similar. Clear half an hour; the call runs until you end it.

Every PM and engineer who has ever rolled their eyes at a forwarded deal thread. And if you sit on the sales side and somebody in product sent you this chapter, that is them crossing the lake; meet them halfway.