A promise needs an operation

A sale commits an operation to doing something. The attractive part of the offer may be a car, a meal or a room. The customer is also relying on people, preparation and timing that the offer barely mentions.

Vijay Sheth’s restaurant work and early vehicle rentals make that connection visible in Infinite Upside. The setting changes; the customer’s position remains recognizable. They need the thing they planned around. A credible account of the company’s difficulties does not provide it.

Start with one customer’s day

Take a hypothetical car reservation for a Saturday wedding. The customer needs to collect the promised vehicle at ten in the morning. On a calendar, that may occupy one neat booking. For the company, it creates questions about the preceding return, the vehicle’s location, cleaning, condition, paperwork and the person receiving the customer.

Those details have an order. A vehicle cannot be prepared at the collection point while it is still being driven there. An unanswered question about the agreement can become a queue at the desk. Each team member may have completed their own task while the customer is still waiting for the whole service.

Trace the promise backward from the moment the customer needs it. What must already be true? Who can confirm that it is true? How early would the team need to know if something changed?

Map the work behind one promise

The following is an invented planning example, not PCH’s procedure. Its purpose is to connect the customer’s requirement with the work that must finish before it.

For an offer of your own, replace the first column with the customer’s actual expectation. In the second, include work that has no separate line on the invoice. In the third, identify someone who can establish the current state. In the fourth, give the issue a person and an early enough decision point. “Tell the manager” is incomplete if no one knows when the manager must respond.

The map may show that the company has promised more control over timing than it possesses. That is a reason to change the arrangement before accepting more bookings, rather than ask employees to rescue it repeatedly.

Look between the tasks

The book’s early delivery work directs attention to what happens after an apparently profitable job. Where has the trip left the driver? How far away is the next customer? Later, placing a rental vehicle creates similar questions at a larger scale.

For a reader applying that idea, the important unit may be the full service sequence. In a hypothetical equipment rental, delivery is complete, but the next booking still depends on collection, inspection and readiness. Finishing one transaction can leave the operation badly positioned for another.

Do not turn every internal task into another customer promise. The customer need not receive the cleaning checklist. The team needs enough shared information to keep the commitment already made. At a handoff, ask whether the next person can see what remains due, where the item is and when someone must confirm readiness. A sent message does not establish that the service can now happen.

Price what you actually provide

Repeated customer questions can reveal operating choices that have not yet been made. Delivery, availability and changes may require decisions about the offer, rather than another polished answer from sales.

The first-car chapter treats this as part of understanding the company’s economics. Necessary work does not disappear because it was absent from the advertisement. It comes back as cost, confusion or a service failure. Sales and operations need to examine the same promise before either team adds more volume.

Finish the map with one ordinary change: a late return, a missing item or a shift ending. Follow it through to the customer’s appointment. If the arrangement still depends on somebody noticing and improvising, identify that work before calling the promise ready to sell again.