top of page

FIELD NOTE | 

November 7, 2025

The Contract Is a Promise

The salesperson may earn the customer's trust. The organization has to keep it.

Years ago, I was adjunct faculty teaching a college course on sales. Early in the term, I asked my students what kinds of jobs they had.

One student said Uber.

Uber was new enough that the answer didn't immediately register as a sales job to the room.

When I said sales, a lot of them were thinking about something closer to the stereotypical used-car salesman. Someone trying to convince you to buy something. Someone with a commission on the other side of your yes. Several had stories about salespeople who had made them feel pressured or manipulated. We all knew the stereotype.

So we started pulling Uber apart.

What makes someone give a driver five stars?

The car being clean mattered. Promptness mattered. Helping with luggage might matter. Conversation mattered. Knowing when not to make conversation mattered.

Pretty soon the class was finding sales everywhere.

I loved teaching for moments like this. You could sometimes watch an idea move through the room. Someone would offer an example, somebody else would extend it, and suddenly they weren't trying to remember something I had told them. They were using it to see things they hadn't noticed before.

I thought I was teaching them to recognize selling outside a Sales department.

I think now we were talking about promises.

I had worked in sales myself, including insurance, and I never thought my job was simply to persuade someone to buy something.

The customer had information I didn't have. I had information they didn't have.

They knew their business, their risks, their priorities, their constraints, what they could afford and what they were trying to protect. I knew things about the products and carriers they couldn't necessarily know from the outside. I understood what implementation would look like. I knew what could happen when they filed a claim, how different carriers tended to respond, and what some of those choices might eventually mean for their business and reputation.

My job was to get enough of that information between us to make a good decision about whether we were a good fit.

Sometimes the answer should be no.

That matters because the quality of a sale isn't determined only by what happens at the moment someone agrees to buy.

Insurance makes this unusually obvious. You can buy a policy today and not discover what the promise is actually worth until something terrible happens years later.

The sale happens now.

The evidence comes later.

The loop can take twenty minutes or five years

An Uber ride compresses this almost perfectly.

A rider makes a decision. The driver arrives. The service is delivered. The rider experiences it. Twenty minutes later, there may be a rating and a tip.

Promise and evidence sit very close together.

The same person may be doing nearly all of the work. Selling, delivering, communicating, adjusting, noticing whether the customer wants to talk, keeping the car clean, getting the customer where they said they would go.

There aren't many places for the promise to get lost.

Now stretch that architecture across a multimillion-dollar, multi-year enterprise contract.

The person who made the promise may not be involved in implementation. The implementation team may hand the customer to someone else. Product decisions made months later may change what is possible. The account may change hands. People on both sides may leave. Billing, support, renewals and product changes may all become part of the customer's experience of a decision they made years earlier.

The salesperson may earn the customer's trust.

The organization has to keep it.

And that requires something different.

As the distance between promise and delivery grows, trust has to survive beyond the individual relationship that created it.

The contract isn't the whole promise

I've been calling the contract a promise, but that isn't quite right.

A contract records some of the promise.

The legal obligation and the experienced promise aren't necessarily identical.

That doesn't mean whatever the customer expected was therefore promised. Customers make assumptions. People misunderstand each other. A salesperson can say "we can probably do this in six weeks" and a customer can hear "we guarantee you'll be live in six weeks."

But the opposite happens too.

A contract can carefully limit an organization's legal obligation while the customer made the decision based on representations, conversations and expectations that never appear neatly in the final document.

"It's in the contract" can be legally dispositive without telling us everything worth knowing about whether trust was kept.

There is information in the gap.

What did we represent?

What did the customer understand?

What did we formally commit to?

What did we know about our ability to deliver it?

And what actually happened?

Keeping those things reasonably coherent is part of the work.

A promise has to survive the organization

Once the customer says yes, the external promise begins generating internal ones.

Sales gives Implementation information it needs to deliver.

Product maintains capabilities the customer depends on.

Implementation commits to dates and outcomes.

Finance bills according to agreed terms.

Systems preserve information other people will need later.

Support responds when expected reality and actual reality diverge.

Each handoff contains another commitment: I will do this. You can rely on this information. This will be ready then. This person owns that.

The contract may be signed once. The organization keeps—or breaks—the promise repeatedly.

This is also why every function can hit its KPI while the promise still fails.

Sales can hit its number by closing an agreement whose implementation complexity is invisible in the compensation plan. Product can deliver its roadmap while the customer's actual use case remains fragmented. Finance can optimize collections in a way that damages a relationship it cannot see.

Locally, everyone can be right.

The customer still experiences one company.

The customer does not experience the org chart.

For a long time, I thought of customer experience as a relatively simple sequence: brand promise, customer expectation, company action, customer experience.

I still think that's useful.

What I underestimated was how much can exist inside company action.

Hundreds of people. Dozens of systems. Handoffs. Reorganizations. Decisions made years after the original sale. Information that has to remain intact long after the people who originally understood why it mattered are gone.

Someone has to design for that.

In retrospect, I don't think moving from sales into operations and systems took me as far away from the customer as it might appear.

I kept following the promise.

Eventually, much of my work became designing some of the infrastructure through which promises survive.

The CRM field that preserves why a customer bought something. The product architecture capable of representing what was sold. The billing logic that reflects the agreement accurately. The handoff that carries context instead of just moving a record. The decision rights that allow someone to fix a problem before it becomes a breach of trust.

None of those things looks much like sales.

They are part of keeping one.

A twenty-minute Uber ride can hold much of its promise inside one human relationship.

A five-year relationship cannot.

The longer the distance between the promise and the evidence, the more the organization itself has to become capable of remembering what it said it would do.

Maybe that's what I was beginning to see in that classroom.

The students thought we were expanding the definition of sales.

I think we were beginning to see how far a promise sometimes has to travel after someone says yes.

bottom of page