Handle a Request for a Price Lock Across Several Years

A longer renewal term in exchange for a price lock deserves a direct, organized response. The request often arrives before everyone has agreed on renewal scope or completed access review for a planned business unit. Pressure around a buyer’s budget meeting often pulls several unresolved topics into one demand for a number. Your job is to name the request, separate confirmed scope from pending scope, and give every open question an owner. This keeps a hurried conversation from turning into a later assumption.

Begin by writing the proposal in parts. Record proposed term length, requested price treatment, current user groups, planned user groups, and target signature date. Then create a pending section for facts nobody has confirmed. A sponsor might want another business unit included in year two, though access review has no decision yet. The account team might need a current view of how present teams use the service before adding people. Those are discussion topics with owners, not reasons to disappear from the buyer.

Use a fictional call for practice. Sourcing manager Helen says, “Give us your final price now and we will sign for three years.” Renewal manager Dev replies, “I appreciate the term proposal. Before our commercial team reviews terms, let’s confirm which business units belong in scope and where access review stands for each group.” Helen asks why access review belongs in renewal discussion. Dev says, “Contract scope should match the rollout our teams have reviewed. I will bring your request to our pricing authority, and we should set a short review with access and business sponsors.”

Dev has acknowledged Helen’s offer without treating a request as an agreement. He has also avoided vague delay. Helen hears what needs review, who holds each answer, and what happens next. Dev should not predict a decision from an internal reviewer. His role is to carry the buyer’s proposal accurately, keep everyone informed, and arrange conversations where people close to the work answer scope questions. The pricing authority makes commercial decisions through the normal internal process.

Ask scope questions before discussing a number. Start with current use. “Which teams will use the renewed service on day one?” Then separate planned additions. “Which groups do you expect to add during the term?” Ask who owns rollout readiness for every added group. Ask which access decision is open and when the owner expects an update. Record names, groups, and dates in plain language. Phrases such as broad access or future growth hide decisions people still need to make.

In this fictional account, sales teams already use the service. Helen wants a support organization added during the second contract year. Support leader Ana expects an access review update on October 3. No manager has chosen a first learning routine for support. Dev writes sales scope as confirmed. He writes support scope as pending. Ana owns an operating plan, while access lead Marcus owns the access decision. The record does not imply either person will approve terms. Their answers help define what belongs in a proposal.

Use specific language for dependencies. Dev does not write “access review in progress.” He writes, “Marcus owns the support access review and expects an update on October 3. After Marcus shares the decision, Ana and Dev will confirm whether support belongs in proposed scope.” This wording distinguishes an expected update from a promised result. Helen knows whom to include in a follow up meeting. The account team has one shared record instead of separate recollections from several calls.

Review current use with the same level of care. Dev asks Ana, “Which manager routine do you want to preserve for sales during renewal?” Ana names Theo’s Monday call review. Dev asks how many sellers take part and when Theo will next look at participation. Ana says 24 sellers and September 16. Dev records the routine and date without turning one meeting into proof of account value. The details connect confirmed sales scope to active work already on the calendar.

Ask a further question if adoption observations are mixed. Suppose two sales managers use the routine regularly, while another manager has not scheduled a review for several weeks. Dev should not state a diagnosis from a single report. He asks Ana which manager owns the missed review and what changed in the team schedule. Ana might identify a leadership absence or a conflict with a product launch. Dev records the answer and asks whether a short manager conversation belongs before the proposal review. This keeps operational work visible without using adoption as a negotiation tactic.

A buyer might press for an immediate response. Hold the sequence in short language. Dev says, “I have recorded the three year term and price lock request. Pricing will review terms after Ana and Marcus confirm scope and access status on Thursday. I will send the complete request for review after our meeting.” This offers a calendar commitment and a clear path. Dev has not claimed commercial authority or promised Helen’s preferred outcome. Helen now has a date for internal planning.

Prepare a short document for the joint review. Put Helen’s proposed term and target date at the top. Separate confirmed groups from pending groups. Beside every confirmed group, include one current operating observation and the person who supplied the detail. Beside each pending group, state the unresolved decision, owner, and expected update date. Reserve space for questions raised during the meeting. Do not fill gaps with estimates. Uncertain scope should look uncertain until an owner supplies an answer.

At the meeting, Dev reads each line aloud and asks the named owner to correct or confirm the record. He starts with sales scope and Theo’s Monday review. He asks Ana whether 24 sellers is still correct and whether September 16 remains the next participation review. He then turns to support. Marcus states the access status. Ana states whether a manager has selected a first learning routine. Helen hears each decision in the same meeting, which reduces later disagreement over what people meant by “included.”

Send written notes soon after the meeting. Use direct labels such as confirmed, pending, or needs decision. In the fictional situation, Dev writes sales confirmed for 24 sellers. He writes support pending access update from Marcus on October 3 and pending manager routine from Ana. The note should not present a commercial result as settled. Dev attaches the buyer’s term request and routes the complete record to the pricing authority. Helen receives the same scope note so her internal team sees which pieces are ready and which pieces await answers.

Practice a fictional two minute exchange with a colleague. Let Helen request a three year price lock before a Tuesday budget meeting. Let Dev state the request, ask which business units belong in current scope, and name Ana’s operating plan and Marcus’s October 3 access update. Dev schedules the Thursday review. At the end of the practice, open the recap note and enter “sales confirmed for 24 sellers” plus “support pending Marcus and Ana.” Add Thursday at 2:00 p.m. to the fictional calendar, then write Helen’s Tuesday budget meeting beside the pending scope line.