The seven-figure quote that hit 100% and died the same day

An education provider selling high-ticket one-to-one and small-class tuition to wealthy families had seven deliverables it wanted strung into one trackable process. The engagement never started. A seven-figure fixed-fee proposal for the whole scope was sent, rejected the same day or the next with no reason given, and the business line was recorded as abandoned. Five months had been planned.

The interesting question is not why the customer said no. It is why a proposal that had just reached 100% coverage was sent at all.

What it looked like they were buying

One process, seven pieces, no gaps. Each deliverable was individually reasonable; together they described a system that would make the institution's delivery legible to itself.

The customer's own ordering was explicit, and it is the most important sentence in the case: acquisition came first, pricing rules and system construction came after. That ordering was recorded during the investigation — before the quote, not after the rejection.

Where the money actually leaked

Not in the process the proposal was built around. The quote priced system metrics: coverage, completeness, delivery of seven modules. For this customer none of those is a revenue line. The constraint sat at the top of the funnel, and the proposal left it untouched.

The second leak was risk. A seven-figure fixed sum, with 40% payable before anything was visible, asked the customer to carry the whole downside of an unfinished system at the moment they had seen the least. The handbook's inference is that this customer expected risk to be shared; the structure offered the opposite. That is not a pricing error in the abstract. It is a mismatch between how this buyer thought about money and how the quote was built, and no amount of coverage repairs it.

The three maps

Money. Revenue came from wealthy families buying one-to-one and small-class teaching. Any system spend is a cost centre unless it feeds acquisition — which is exactly where the customer said the problem was.

Power. Who signs is not recorded. What is recorded is what the customer said first, and in a high-ticket education business the first priority usually marks where the budget attention sits. Reading the signing authority from that is an inference, not a fact.

Who loses. Two groups, both created by the final revision. Data collection moved from five platform APIs to manual collection plus SOP teaching, which transfers labour onto the customer's staff. The parent-side dashboard was deleted, which removes something parents could see. Both are adoption costs, and neither appeared anywhere in the price.

Where the judgement was initially wrong

The binding constraint was assumed to be completeness.

Version three covered 29% of the customer's requirement list. Version four rebuilt it to 100% at an unchanged total price. On paper the gap closed.

What the rebuild actually changed: coverage, the payment schedule (four instalments to five), the upfront share (60% down to 40%), the data-collection method, and one dashboard removed. Every variable except the two that decide whether a quote is payable — what the customer's own numbers will show within four weeks, and who carries the risk if they don't.

This is the most common way a second attempt fails, so it is worth naming. The first attempt was rejected for reasons nobody wrote down. The second treated "not complete enough" as the hypothesis, spent its energy on the one variable a vendor can move alone, and left the basis of payment untouched. Completeness is the variable you control; eligibility is the variable that requires the customer to say yes to something specific.

The handbook's failure review puts this on the vendor's side of the table: the reading is that the quote was rejected, not that it was outbid. Nothing is recorded about alternative suppliers, counter-offers or further negotiation. So the honest conclusion is narrower than "we lost to someone" — we never established what would have made the number payable.

What lived

Nothing in the customer's operation. Five months were planned and nothing started.

What survived was the diagnosis. "Acquisition first" was produced by the investigation, was recorded, and then was not priced. The one finding that could have changed the arithmetic of the quote was the one finding that never entered it.

At method level, the manual-collection-plus-SOP path is the only deliverable shaped like something the customer's staff could have run without a system, which makes it the only piece that might have survived contact with adoption. It was never tested.

What died

The seven deliverables as a set, the five-platform integration, the parent-side dashboard, the quote, and the relationship, recorded as abandoned.

Doing the investigation is not the same as earning the right to quote

The investigation answers what this customer needs. Quote eligibility answers on what basis this customer will pay. They come from different questions, and one does not imply the other.

Four questions to answer before any quote leaves the building, with "not recorded" counting as a failing answer:

• Which line in the customer's own accounts does this move, in their words?
• What will be judgeable within four weeks, using data they already hold?
• Who carries the risk if that four-week test fails?
• What is the payment basis — fixed, staged against checkpoints, or shared?

The corrective order that the handbook's other cases reach independently runs: interview, boundary, cooperation structure, a four-week judgeable delivery — and only then a price. Reversed, the price is a guess about a customer you have not met. That ordering is also the argument in scoping and pricing, and it is what the four-week rule turns into a date.

Ending criterion: a quote is eligible when you can name the customer's metric that will move and the date it will move by, without adjectives. If you can only describe what you will deliver, you have a scope, not a price.