Case Study 1 — The Deal That Wouldn't Close

A composite case, assembled from the common experiences of Western firms entering the Chinese market. Names and details are illustrative.

The situation

Daniel is VP of Sales for a mid-sized American industrial-components company with a genuinely strong product — better engineered and competitively priced against the incumbent his prospective Chinese partner currently buys from. The opportunity is large: a multi-year supply relationship with a fast-growing manufacturer outside Suzhou. Daniel has closed hard deals across North America and Europe and is, by every metric at home, excellent: prepared, decisive, relentless about momentum.

His first trip goes wonderfully. His host, Mr. Zhang, the manufacturer's deputy general manager, lays on a lavish welcome banquet — private room, lazy Susan groaning with dishes, warm toasts of baijiu, photographs, laughter, a tour of the plant the next morning. Daniel leaves convinced the deal is all but done; the chemistry was obvious, the product fit is clear, and his pricing is sharp. He tells his CEO to expect a signed agreement within the quarter.

Then nothing happens. His detailed follow-up proposal gets a courteous, content-free reply. A second trip produces another superb dinner and no signature. When Daniel tries to "drive to close" — a crisp email laying out terms, timeline, and a request for a decision by month-end — the warmth seems to cool. Replies slow further. Four months in, his CEO is openly frustrated, the incumbent competitor is still supplying the plant, and Daniel cannot explain why a deal that should have closed on the merits has simply... stalled.

He is not failing. He is succeeding, slowly, in a system he is reading at entirely the wrong speed — and his attempts to "fix" it are making it worse.

The 'before': how it felt through Daniel's operating system

Run the events through Daniel's home software and his frustration is perfectly logical. In his world, business is a transaction evaluated on merits: the better product at the better price, presented clearly, wins — and good salesmanship means building momentum and closing. The banquet was lovely, but it was relationship-building around the deal — the wrapper, not the substance. Once the value proposition is obvious, lingering is just inefficiency, and a professional moves to signature. So when Mr. Zhang doesn't move, Daniel reads it exactly as he would read it back home: the buyer is stalling, or shopping his price, or simply disorganized — and the cure is more pressure, clearer asks, firmer deadlines.

Every instinct Daniel has is fluent — in the wrong language. His "drive to close" is not reading as competence. It is reading as a man who wants the contract more than the relationship — which, to Mr. Zhang, is exactly the kind of partner you do not bind yourself to for years.

The 'after': what was actually happening

In Mr. Zhang's frame, almost nothing about Daniel's situation was a problem. It was a process, and Daniel kept interrupting it.

• The relationship is the deal. Switching a multi-year supply relationship away from a trusted incumbent is a serious, risky act. In a business culture built on guanxi, you do not take that risk with someone you don't yet trust personally — and trust is built through time, meals, reciprocity, and repeated contact, not through a strong spec sheet. The banquets were not the wrapper. They were the substance: Mr. Zhang was patiently assessing whether Daniel was someone worth being bound to. (Chapters 14, 27.)
• Daniel had little guanxi, and hadn't noticed. He'd had two nice dinners — pleasant, but thin. He had not built the reciprocal, accumulated relationship that would make Mr. Zhang comfortable. From Mr. Zhang's side, the deal couldn't responsibly move yet because the foundation wasn't there.
• The pressure cost face and trust. Each deadline and "drive to close" did two kinds of damage: it implied Daniel valued the contract over the relationship (a bad sign about his character as a partner), and a firm push risked forcing Mr. Zhang toward a face-costing direct refusal. So Mr. Zhang did the polite thing — he went quiet and let the temperature drop. The cooling Daniel sensed was real; he had caused it.
• The silence was an answer Daniel couldn't read. Mr. Zhang never said no. He didn't need to. The slow replies, the deflected timelines, the renewed dinner invitations were the message: we're not there yet; invest in this, or it won't happen. Daniel heard a void; it was full.

Daniel had been "selling" expertly into a system that wasn't buying a product — it was buying a partner, and judging him by a rubric he didn't know he was being graded on.

The deeper point

This is Chapter 27 in a single story, and it dramatizes the chapter's opening claim precisely: nearly every Western misread of China is a speed error or a unit error, and Daniel committed both. The speed error: he treated the relationship as the wrapper around the transaction, when in China the relationship is the transaction and the contract merely its receipt — so he moved far too fast and read patience as stalling. The unit error: he negotiated as if Mr. Zhang were a free individual weighing a spec sheet, when Mr. Zhang was a node in a network — a company, a web of existing supplier relationships and internal stakeholders, a personal reputation on the line if he bound the firm to an untested foreigner.

Notice, too, that both operating systems are internally sensible. Daniel's drive-to-close genuinely works in markets where contracts are the bond and merits decide. Mr. Zhang's slow, relationship-first process genuinely works in a culture where personal trust is the bond and the cost of a bad partner is high. Neither is the "real" way to do business. They are two systems optimized for different things — and the collision happened below the waterline, in two unspoken theories of what a deal is.

The better approach

Daniel doesn't need to stop being a strong salesman or to fake being Chinese. He needs to recognize he's running a system, slow down, and shift from closing a transaction to building a partner relationship — letting the deal ripen rather than forcing it.

• Re-time everything. Stop driving to a quarter-end signature. Plan for a longer courtship: more trips, more meals, more presence. Treat relationship investment as the actual work of the deal, not a distraction from it.
• Build real guanxi, generously and before he needs it. Reciprocate hospitality (host a dinner of his own). Give appropriate face — praise Mr. Zhang's plant publicly, defer to his seniority, present a thoughtful (non-taboo) gift with both hands. Do small favors without keeping score. Exchange WeChat and stay warmly, lightly in contact between trips — a holiday greeting, a relevant article, a digital hongbao at New Year.
• Stop pushing; let the soft no breathe. Replace deadlines with patience. Where he must gauge progress, do it indirectly and relationally, not with ultimatums that force a face-costing refusal.
• Find the network. Understand who else inside the manufacturer has a stake, who Mr. Zhang must satisfy, and where the incumbent relationship's roots run. Let Mr. Zhang, once he trusts Daniel, guide him through that maze — which he will, because of the relationship.
• Reset his own read of silence from "stalling" to "the foundation isn't ready yet — invest, don't pressure."

Scripts Daniel could use: - (warmly, on a later trip, not by email) "I'm not in a hurry, Mr. Zhang. A relationship like this is worth doing right, and I'd rather earn your trust than rush a contract. I'm here for the long term." - (hosting his own dinner) "You've shown me wonderful hospitality. Please allow me the honor of hosting you tonight — I've been looking forward to it." - (on WeChat, at Lunar New Year) a short, sincere holiday greeting and a small digital hongbao — relationship maintenance that costs almost nothing and says I value this beyond the deal. - (when tempted to push) nothing. The most powerful move is often the patient silence Daniel finds hardest.

Firms in Daniel's position who make this shift typically find the deal that "wouldn't close" closes after all — later than the Western clock wanted, but on a foundation strong enough to survive the years the contract will run. The signature, when it comes, is not the achievement. The relationship that produced it is.

Discussion questions

1. Identify the exact belief Daniel mistook for a universal fact about "how business works." How did its invisibility to him cause the stall?
2. The chapter calls Daniel's errors a "speed error" and a "unit error." Point to the specific moments in the story where each one operated.
3. Make the strongest possible case for Mr. Zhang's slow, relationship-first process as good, rational business — not a quirk to be tolerated but a sound way to manage real risk.
4. Daniel's pushing actively cooled the relationship. Where in your own work might "driving harder" be quietly making a situation worse rather than better?
5. Where is the line between investing patiently in a relationship and simply being strung along? How would a culturally intelligent professional tell the difference without resorting to a face-costing ultimatum?

Portfolio link. In your China portfolio page, add an entry to "Behaviors I might misread": slow replies and renewed dinner invitations after a strong proposal may mean "build more relationship," not "the buyer is stalling" — invest before concluding. Then, beside it, write your personal early-warning rule: one honest signal you'll watch for to distinguish ripening from going nowhere — and commit that your response to ambiguity will be to deepen the relationship, not to apply pressure.