Quote

When prices went out in the body of an email, nothing recorded how long the price was good for. A rep types one line: thirty seats runs about $7,000 a year. The recipient files the email and goes into internal discussion. When that discussion ends is not something the seller gets to know.

Six months later the email comes back. Pricing changed once in the meantime and the same configuration now runs $9,000, but the buyer arrives holding the old number and asks for it. The seller has no grounds to refuse, because no conditions and no dates were ever written down. The $2,000 conceded that way then drags down every renewal figure for years afterward.

A quote exists to put a fence around a price. Record what the price is for, how long it stands, and what assumptions produced it, and the number becomes one offer rather than a standing promise. It also becomes useful to the other side at the same moment. An email body can't be submitted for internal approval; a quote can, which is often the real reason a buyer asks for one even when they already know the price.

Six things usually go inside. The first three build the number and the last three fence it in.

1. Configuration and quantity — which plan, how many seats. In software those two values are what determine price, so an error here makes everything else wrong. Seat counts also move between the quote and the signature more often than anything else does, which is why this line gets confirmed rather than assumed.
2. Unit price and total — per seat per month, and the figure across the whole term. Give the monthly rate without the total and the customer's finance team has to multiply it themselves, which is where numbers stop agreeing.
3. Discount — list price and applied price side by side, with the percentage. Add a line on why it came down. If the number assumes a three-year term, that sentence belongs here.
4. Validity — how long this price stands. Thirty days is common. This one line is what makes a quote a quote; without a date it isn't a price, it's a promise, and promises don't expire.
5. Contract term — the period the price covers. A one-year number and a three-year number are different numbers.
6. Payment terms — annual prepayment or quarterly invoicing, and how many days after invoicing payment is due.

What's absent matters as much. Indemnity limits, termination mechanics, and how personal data gets handled don't go in a quote. Those rules belong to the master service agreement (MSA), which governs the relationship as a whole, and to the non-disclosure agreement (NDA) signed before information changes hands. Start writing them into a quote and a one-page document becomes a legal review item, and the person who only wanted to check the price gets no answer.

The rep writes it, but not alone.

Discounts bring approvals with them. Every company has a rule about who can cut how much, so anything past a rep's own discretion has to pass a manager or a founder before the document goes out. That's the difference between a company where a quote takes a day to issue and one where it takes a week, and the gap is a process choice rather than a workload problem. In the last week of a quarter, that delay is a frequent cause of a missed deal.

Three parties read it, and each reads a different line.

1. The practitioner reads configuration and quantity, checking whether the seat count matches their team.
2. The approver reads the total and the contract term. How much per year and how many years of commitment is often the entirety of the approval decision. If this person wasn't in the meeting, the total on the page is the only number they ever see.
3. The finance contact reads payment terms and validity. When money leaves and how long the price stands both feed straight into budget allocation.

Because three people read three different lines, this document has to stay short. One page is the standard. When explanation is needed, you don't lengthen the quote — you write a separate proposal that carries scope and conditions as well.

"Put a thirty-day validity on this one. I don't want someone showing up with it six months later again."

Tie the price to a period.

"That quote assumes a three-year term. Switching to one year raises the unit price."

Restating that the discount was bought with commitment.

"Quote approval took two days, so it didn't go out in the last week of the quarter."

Internal process cutting into deal speed.

At Pagedeck, Sofia issues three versions together: one year, two years, and three years. Building it so the per-seat rate falls as the term lengthens turns the conversation from cutting the price into choosing a term. Once there are three options to pick from, requests for a discount drop off on their own.

Grace personally reviews only quotes with a discount above 15 percent. What Grace looks for isn't the percentage but whether the document says why the number came down. Without that line, a year later the discounted figure is simply the list price. Last quarter one quote with an unexplained 20 percent cut was sent back on the spot, and it went out the next morning with a three-year term attached to the same figure.

A common belief is that sending a quote settles the price. It went out as a document, so it feels agreed, and most of the time the contract does land at that number, which reinforces the impression. But this document is one side's offer. The buyer has committed only when their own process produces a numbered purchase order (PO). Deals counted in the forecast on the strength of a sent quote are the ones that fall out in the final week of the quarter.

The other mistake is quoting low to make approval easier. Leading with a number shaped to the customer's budget feels like it speeds things up. Two things follow instead. First, that number becomes the starting line for next year's renewal, and raising it to list in year two requires explaining why the price went up — an explanation that rarely works. Second, the buyer learns that asking costs nothing. A procurement specialist who watched a price drop without being asked opens the next negotiation lower than they otherwise would have.