The Dev Who Sat in a Sales Call

Posted3 months agoActive3 months ago

xsh6942

2 points

2 comments

ag404labs.comOtherstory

calmpositive

Debate

0/100

SalesSoftware DevelopmentCommunication

Key topics

Sales

Software Development

Communication

A developer shares their experience of sitting in on a sales call and the insights gained from it, sparking discussion on the value of cross-functional understanding.

Snapshot generated from the HN discussion

Discussion Activity

Light discussion

First comment

11m

Peak period

0-1h

Avg / period

Key moments

01Story posted
Oct 1, 2025 at 12:13 PM EDT
3 months ago
Step 01
02First comment
Oct 1, 2025 at 12:24 PM EDT
11m after posting
Step 02
03Peak activity
2 comments in 0-1h
Hottest window of the conversation
Step 03
04Latest activity
Oct 1, 2025 at 12:53 PM EDT
3 months ago
Step 04

Generating AI Summary...

Analyzing up to 500 comments to identify key contributors and discussion patterns

Discussion (2 comments)

Showing 2 comments

duxup

3 months ago

1 reply

I worked at a company that for a very short time had engineering, tech support, and sales and such all follow a person from another department around for a little while. It opened up communication and understanding far beyond anything ever had, but it of course ended after a short while. It was inconvenient, and I think it upset some managers who were the gatekeepers of communication and process and otherwise useless humans.

I still fight regularly for a meeting with clients that isn't a list of ideas or features, but is a "why do you want to do this thing" explanation from the very top. I don't always get it, but when I do the new feature right out of the gate, almost every dang time.

xsh6942Author

3 months ago

I've had the same experience, cross-department shadowing at a listed fintech. It worked tremendously well... For 3 months until they invoked "too many meetings" rule to shut it all down. IMO it died because it exposed how many people's entire job was controlling information flow. The "useless humans" you mentioned? Their job security depends on being the bottleneck. If developers understand customer problems directly, what's the PM doing all day? If sales knows what engineering can actually deliver, why do we need three layers of "roadmap prioritization"?

When engineers can talk directly to customers, when support understands the product, when sales knows what's actually possible, suddenly half the middle management layer has nothing to do.

View full discussion on Hacker News

ID: 45439485Type: storyLast synced: 11/17/2025, 12:08:47 PM

Want the full context?

Jump to the original sources

Read the primary article or dive into the live Hacker News thread when you're ready.

Open link View on HN