Case Study 1: Six Kindnesses

Tier 3 — Illustrative. The Achebe–Lindqvist wedding and all vendors are composites created for teaching. The pattern — a cash-flow crisis assembled from individually reasonable accommodations — recurs constantly and is almost never diagnosed until it is acute.

This is the case behind the chapter's opening, with the dates and the arithmetic.

The Wedding

Nkechi Achebe and Mattias Lindqvist. 150 guests, $61,000, a coastal hotel with in-house catering. Wedding on 12 September. Planner engaged the previous July — a fourteen-month engagement.

The budget was never a problem. At month twelve it stood at $61,400 against a $61,000 plan — $400 of variance, 0.7%, which is about as good as a fourteen-month engagement gets. The planner's tracker was immaculate.

There was no payment calendar.

The Six Requests

Every one of these was reasonable. Every one was granted. Not one of them was recorded anywhere except in an email thread.

What Had Actually Been Built

💰 Run the Numbers: the calendar nobody was maintaining

As originally contracted — money due in each month:

Month	Due
March	$3,200
April	$2,100
May	$4,900
June	$3,850
July	$2,400
August	$9,100
September (to the 12th)	$11,300
Final six weeks	$18,400 (30% of budget)

After the six accommodations:

Month	Due
March	$1,520
April	$2,130
May	$3,950
June	$1,975
July	$2,400
August	$15,780
September (to the 12th)	$11,300
Final six weeks	$27,080 (44% of budget)

$8,680 had been pushed into a window that already held $18,400.

And the true figure was worse than the table shows, because the September column contains the caterer's balance, which is due at −14 days — 29 August — putting it in the same forty-one-day span. Counted properly:

$16,400 due between 1 August and 11 September, from a couple who had said "things are tight" six times in five months.

The Discovery

23 July. The planner, doing a routine confirmation pass, opened the hotel's contract to check the balance date and noticed it read "1 August."

She had moved it herself in June and had not thought about it since.

She spent forty minutes building the payment calendar she should have built in month two, and then she called.

The Conversation

📋 The Planner's Script: raising an accommodation pattern

The hardest part is that the planner caused this, and the client has done nothing wrong except ask for things they were granted. Both facts have to be in the first thirty seconds.

Opening:

"I've made a mistake and I want to talk about it before it becomes a problem rather than after.

Over the last five months you've asked me six times to move a payment date. I said yes every time, which was the right answer each time — and I never once looked at what all six of them added up to. I did that this morning.

You have sixteen thousand four hundred dollars leaving your account between the first of August and the eleventh of September. Forty-one days."

Then the question, and it is the same fork as always:

"So I need to ask you the question I should have asked in March. Is this a timing thing — money that's coming later — or has something changed? I'm not asking to be nosy. I'm asking because they're different problems and there's still time to solve either one."

What Nkechi said:

"It's… both, I think. Mattias's bonus was supposed to be in June and it's now November. And we've been spending more than we meant to on things that aren't the wedding."

The planner's reply:

"Okay. Thank you. That's actually the easier version of the two, because the money exists — it's just in the wrong place at the wrong time.

Give me two days. I'm going to go back to four of your vendors and ask about staging, and I think I can move somewhere between six and nine thousand out of that window. I'll come back with a real calendar and we'll see what's left."

What she did not say, and it is the discipline of the chapter: nothing about the six requests, nothing about "you should have told me," nothing about the spending on things that were not the wedding. That last one in particular — a client who volunteers that they have been overspending has taken a real risk in telling you, and the only correct response is to use the information and never mention it again.

The Fix

Four calls, two days.

💰 Run the Numbers: what staging recovered

Vendor	Balance	Asked	Result	Moved out of the window
Caterer	$14,200 | Stage into three | **Yes** — 3 × $4,733 at −90, −45, −14 days	$9,466
Rental company	$5,190 | Stage into two | **Yes** — half at −60 | **$2,595**
Hotel (venue balance)	$4,700 | Move back to 20 August | **Partial** — moved to 15 August | $0 (still in window)
Photographer	$2,600 | Stage into two | **No** — sole proprietor, fee is her income | $0
			Total recovered	$12,061

The window fell from $16,400 to $4,339.

Two things about that table are worth more than the number.

The caterer said yes immediately, and the planner had never asked at booking. That single question — asked fourteen months earlier, for free, when it was a scheduling detail rather than a favor — would have prevented the entire case.

The photographer said no, and was right to. A sole proprietor whose fee for a September Saturday is her income for that Saturday cannot lend it to a client. The planner accepted immediately, thanked her, and did not press. Three months later that photographer referred a client. Chapter 12 is about why those two facts are related.

What It Cost Anyway

The crisis was averted. It was not free.

That last row is the real cost and it does not appear in any budget. Nkechi's messages for the following six weeks were shorter and more checking — "just confirming the caterer got the second payment?" — which is the behavior of a client who has discovered that something was not being watched.

It recovered. By the wedding it was gone. But the product this couple was buying was the confidence that someone had it handled (Chapter 1), and for six weeks in the middle of their engagement they did not have it, because of six emails nobody had added up.

Post-Mortem

Root cause: no payment calendar existed, so there was no artifact against which an accommodation could be evaluated. Each request was assessed in isolation because there was nothing else to assess it against.

Contributing causes:

1. Staging was never requested at booking. The caterer agreed instantly in July. In the previous July it would have cost one sentence and would have removed $9,466 from the final cluster before the problem existed.
2. The tracker was immaculate and irrelevant. $400 of variance on $61,000 is superb budget management and it told the planner nothing about the actual risk. A perfect budget can coexist with a cash-flow crisis, and the planner's confidence in the one obscured the other.
3. "Things are a bit tight" was said six times and never asked about. Signal three of §7.5, ignored six times.
4. The accommodations were never recorded. Had each one been logged as a change to the calendar — even one line in the tracker's notes column — the cumulative effect would have been visible by request four.

What went right:

1. She built the calendar the moment she noticed, and called the same day.
2. She named her own error first, and named it as an error rather than as circumstance.
3. She asked the timing-versus-change question, and got a truthful and slightly embarrassing answer because she asked it in a way that permitted one.
4. She did not moralize — not about the six requests, and specifically not about the volunteered overspending.
5. She asked four vendors and accepted one refusal cheerfully.
6. She solved it in two days.

The transferable rules:

1. Build the payment calendar in month two. Its value is entirely in existing before the deposits are paid.
2. Ask every vendor about staging at booking. Free, thirty seconds, and it is the whole fix in retrospect.
3. After a second delay request, rebuild the calendar before agreeing to a third. This is the rule the chapter's exercise D.3 asks you to design, and it is a good answer: it does not require refusing anyone, and it catches the pattern at request three rather than request six.
4. A clean budget is not evidence of a healthy engagement. Variance and cash flow are different instruments measuring different things.
5. When a client volunteers something embarrassing, use it and never mention it again.

Discussion Questions

1. The planner told the client she had made a mistake. She had — but the client had also asked six times without ever explaining why. Argue that the shared responsibility should have been named. Then argue that naming it would have cost more than it was worth.

2. Rule 3 — rebuild the calendar after a second delay request — catches this at request three. Design a rule that catches it at request two, and then say honestly whether you would actually follow it.

3. The photographer refused and was thanked. Construct the case that a planner should press harder on behalf of a client in difficulty. What does your answer imply about whose interests the planner is representing?

4. Nkechi volunteered that they had been overspending on non-wedding things. The planner used the information and never mentioned it. Is there a version of this engagement where she should have raised it? (Compare exercise D.5.)

5. The client's confidence was reduced for six weeks and then recovered. If the product is calm (Chapter 1), how would you price six weeks of its absence? Does the answer change how you think about the nine hours of remediation?

Mini-Project

Build the accommodation log.

Design the mechanism that would have caught this. Constraints: it must live inside a document you already maintain, it must take under fifteen seconds per accommodation, and it must surface the cumulative effect without requiring you to remember to look.

Consider: a notes column on the tracker that records every date change; a recomputed final-cluster total displayed at the bottom of the payment calendar; a rule that any date change triggers a re-sort and re-total; a hard threshold — "if the final six weeks exceed 40% of budget, raise it."

Then test your design against the six requests in this case. At which request does your mechanism fire? If it fires at five or six, redesign it.

References

Tier 3 — Illustrative. Nkechi Achebe, Mattias Lindqvist, and all vendors and figures are composites created for teaching.

Tier 2 — Attributed practice. The pattern of final-cluster concentration (30–55% of budget in the last six weeks) and the differential willingness of vendor categories to stage payments reflect commonly reported industry practice rather than measured data.

Related chapters: The payment calendar — Chapter 7 §7.2. Staging requests at booking — Chapter 7 §7.2.1. Drift signals — Chapter 7 §7.5. The shortfall procedure — Chapter 7 §7.7. Vendor relationships as an asset built before it is needed — Chapters 1 and 12. Selling calm — Chapter 1 §1.4.