Contracting

For a long time, the board tracking a deal's progress ended at negotiation. The moment the buyer said yes was treated as the finish line, and whatever came after counted as paperwork. So a rep would mark a deal won the day they heard a yes on a call, and the signature would land a month later. A month of drift wrecks every number attached to it. Revenue counted for this quarter slides into the next one, and the hiring and ad budgets built on that revenue slide with it.

Pagedeck tripped over exactly this. In the last week of a quarter Sofia reported a deal with a forty-person company as done, and when Grace asked how far along it was, the picture came apart. The person who would use the product had said yes, but their procurement team had not issued a purchase number, their legal reviewer wanted to redo the confidentiality agreement first, and their security lead had sent over a twenty-item questionnaire. All three had appeared that week. The deal was signed six weeks later.

That's what earned this stretch its own name. The people you deal with here are not the people you dealt with before. The person who will use the product is asking how much easier their week gets. Procurement and legal are asking what the company is exposed to if this goes wrong. When the question changes, the way you move it changes too. Running the demo again does nothing; a sentence capping damages and a written answer about where data is stored do.

Deals that stall here also erase everything spent to get them, which is the other reason to manage the stretch separately. Lose three weeks to one missing document, miss the window when the buyer's budget gets locked, and eight months of work moves to next year.

Teams that treat this as its own stage start preparing for it much earlier. They ask, while presenting, who signs off on purchases, how many days legal review usually takes, and who issues the purchase number. People generally answer. Nobody who fails to ask finds out until all three questions surface at once, days before the signature.

The terms under this name fall into three groups: the documents that change hands, the shape the agreement takes, and the values written into it.

Documents are the paper that moves during this stretch. There are four, and they usually arrive in this order.

1. Non-disclosure agreement (NDA) — a promise not to repeat what each side shares. It typically comes first, because the buyer can't show internal material and you can't describe an unreleased feature without it. Most versions place the same obligation on both sides, and getting one signed takes anywhere from a day to a week.
2. Quote — the document stating what you'll provide for how much. Seat count, plan, length of commitment and discount all fit on one page. The expiry date printed on it says a lot about what the document is for. Without one, someone will come back with a six-month-old quote and ask for that price again.
3. Master service agreement (MSA) — the contract setting the rules that apply to every deal between the two companies: liability, how either side can walk away, how personal data gets handled. Once it exists, later purchases take one order form listing quantity and price, so it's worth the time on the first deal if you expect more.
4. Purchase order (PO) — the buyer's formal statement that they are buying. Procurement issues it with a number, and your invoice can't enter their payment process without that number. However enthusiastic your contact is, no number means no path for the money yet, which is why many companies use this document as the line between a deal that counts and one that doesn't.

Shape covers how large a commitment the agreement asks for, and there is one term here. A pilot contract is a short agreement, often around three months, that puts the product in front of one team before any full commitment. It replaces a decision made in meetings with a decision made by using the thing, so it opens doors when the buyer feels exposed. The catch is what happens at the end. Leave that unwritten and the trial simply continues. The contract needs numbers: what has to be true to convert, and what date it ends on if that doesn't happen.

Conditions are the values written into whichever document is in play. There are three, and all three feed straight into when and how much revenue gets recognized.

1. Contract term — how long the agreement runs. One year is the default, and two or three years is common. Longer commitments are usually bought with a lower price, so term and discount get negotiated as a pair rather than separately.
2. Auto-renewal clause — the sentence saying the agreement continues on the same conditions unless someone says otherwise. The notice window written beside it is the substance. If the text requires notice sixty days before expiry, a customer who changes their mind a month out is paying for another year.
3. Discount policy — the pre-set limits on who can cut how much. Ten percent at the rep's discretion, more with a manager, past twenty percent only with the chief executive, and so on. Without those steps, the last week of every quarter turns into discounting on instinct, and next year's renewal negotiation opens from the lower number.

The three groups run along a single deal. The confidentiality agreement opens the conversation, the quote puts numbers on the table, the master agreement sets the rules, and the purchase order opens the path for payment. Shape folds and unfolds that sequence once, and conditions name the same values wherever they appear. This is what makes "where is it stuck?" a short question to answer. Stuck at the NDA and stuck at the purchase order describe completely different amounts of remaining time — the first means nothing has started, the second means the terms are settled and only the buyer's internal process remains. The same phrase, in progress, points at three months in one case and ten days in the other.

Not every deal uses all four documents. A product bought with a card by one person runs on a single click-through agreement instead, and the paperwork only appears once there's a buying process on the other side. Where that process exists, the order above is worth holding to. Sending a quote before the confidentiality agreement is signed means the pricing sits in an inbox with nothing attached to it, and asking for a purchase order before the master agreement is settled sends procurement a request they have no basis to approve.

"Verbally we're done, but the purchase order hasn't come through. I can't put it in this quarter's number."

Agreement from your contact and a decision by their company are different things, and the second one is what counts as revenue.

"I can go to fifteen percent if they commit to two years. Anything past that needs Grace's approval."

Trading discount for length, and stating how far the person in the room can decide on their own.

"Their legal team wants to use their paper instead of our master agreement, with a security addendum attached. Add two weeks."

Control of the document has moved, so the timeline needs redrawing.

Pagedeck rebuilt the order of operations for that same forty-person customer. Sofia sent the confidentiality agreement before the first meeting, and once it was signed, set up a three-month pilot. The pilot contract carried two sentences: pass thirty weekly users inside three months and it converts to an annual agreement, fall short and it ends that day.

Weekly users hit thirty-four in the third month, and Sofia sent the quote the following week — forty seats, two years, fifteen percent off. Fifteen sat inside Grace's approval range, so she cleared it on the spot, while declining the buyer's request to shorten the renewal notice window from sixty days to thirty. Procurement issued the purchase number nine days after the quote went out, and that was the day the deal became a number. Against six weeks on the first deal it ran more than twice as fast, and what shrank was waiting rather than negotiating: the confidentiality agreement and the security questionnaire were already done during the pilot, so only one new person, the buyer, showed up at the end. Sofia has asked about approval steps and legal review times in every first meeting since.

The most common belief is that this stretch ends at the signature. A rep's target fills on the signing date, so letting go there feels natural. But the values fixed that day start running that day. The contract term decides which month next year's negotiation opens in, and the notice window in the renewal clause decides when that negotiation has to start. If nobody copies those dates into a calendar, a customer who says two months before renewal that they're leaving is already past the deadline, and both sides end up uncomfortable. The same window binds you when you want to raise the price. A renewal date that someone owns, with a reminder set ninety days out, costs nothing to set up on signing day and is close to impossible to reconstruct a year later.

The second belief is that this is administrative work rather than selling. Presenting and persuading feel like the real job, and paperwork feels like cleanup. Yet the conditions set here decide how the next few years with this customer go. A deal closed by granting an exit right after three months gets signed but doesn't count as annual revenue, and the job of driving usage moves over to customer success. The looser the terms used to close, the more hands the account needs later. Closing is the goal of this stretch, but the terms it closes on set next year's workload. That's why more teams now grade this stage on more than signature count: average discount, share of multi-year deals, days to signature. A quarter where those three worsen is usually a quarter stuffed with deals that skipped qualification earlier on. Deals pushed into this stretch before anyone confirmed the budget or the decision-maker tend to buy their way through it with discounts and exit rights, and those concessions are still in the file when the renewal comes around.