Sales Hire Offer Close

Sales hire offer close

Runs from the moment a hiring manager decides to offer until the new hire's first day. Produces a close plan and a Yes/No decision on the number, never an offer sent by the agent.

The prime rule: never make an offer you have not trial-closed. A formal offer is the last step of a close, not the first. If the candidate's answer to "if this lands, are you accepting?" is not yet known, the offer is not ready, however strong the final round felt.

Offers die two ways. An information gap: a number goes out before anyone confirmed what the candidate would accept. An unmanaged risk: the candidate accepts, resigns, gets bought back, and nobody rehearsed that conversation. The play closes both.

Template placeholders

Replace every {{...}} before enabling. The setup checklist in references/setup-customization-checklist.md covers each one.

• {{ATS}}: where the candidate, their stage history and interview notes live
• {{COMP_APPROVER}}: who signs the ceiling for this role
• {{REVIEW_CHANNEL}}: where the close card is posted
• {{CALENDAR}}: where notice-period touches are scheduled
• {{OFFER_OWNER}}: who holds the candidate relationship through notice (hiring manager, recruiter or talent partner)
• {{CURRENCY}}: currency for every figure on the card
• {{PACKAGE_BASIS}}: how total package is counted, for example base plus on-target commission plus super or pension plus equity at a stated value

Trial mode (recommended for the first three offers)

Build the full card but write nothing to {{ATS}} or {{CALENDAR}}. Post it to {{REVIEW_CHANNEL}} marked TRIAL and let the hiring manager run the close their usual way alongside it. Compare after day one: which risks the card called, and which it missed. Switch writes on once the card is calling them.

Diagnostic questions (before the first run)

Ask these once per team. They show where offers are leaking.

1. Of the last ten offers, how many were declined, how many accepted then reneged, and how many started and left inside six months?
2. Who can approve a number above the band, and how long does that take?
3. Does anyone ask the candidate what they will accept before the offer is written?
4. Who talks to the candidate between resignation and day one, and how often?
5. When a candidate was bought back, did anyone see it coming? What was the signal?

The play

Step 1. Pull the inputs

• From {{ATS}}: the role, stage history, interview and debrief notes, any stated reasons for moving, and any numbers the candidate has given.
• From {{COMP_APPROVER}}: the approved ceiling on {{PACKAGE_BASIS}}, in {{CURRENCY}}, and what flexes (sign-on, equity, start date, title) without a new approval.
• If the panel debrief flagged concerns or counter-offer signals, carry them in. They are the first inputs to Step 6.

Search before asking. Anything the notes already hold is used, with its date. Anything older than the last interview is reconfirmed with the candidate, not trusted.

Step 2. Run the close-ready gate

Three checks, all required:

• Motive. The candidate's real reason for moving, in their own words. "New challenge" does not count.
• Numbers. Current base, current total, expectation, walk-away and notice period, all confirmed by the candidate, not inferred from a salary band.
• Ceiling. The actual number, signed by {{COMP_APPROVER}}. Not the advertised range.

If any check fails, stop. Post a short card naming the missing check and the exact conversation that fills it, with the script from references/scripts.md. A defence built on a motive nobody established fails at the moment it is needed.

Step 3. Size the gap

Expectation against ceiling on total package, as a figure and a percentage. Keep the walk-away separate: the expectation is the opening position, the walk-away is the deal. Convert every figure to {{PACKAGE_BASIS}} first. Comparing one company's base with another's on-target earnings is the most common way two sides think they are further apart than they are.

Step 4. Build up to three structures

Price each on cost to the company, what it signals to the candidate, and its risk. references/offer-structures.md holds the structure library, the gap thresholds and the sales-specific checks. Recommend one and say why in a sentence.

Step 5. Trial close both sides

Before anything is written, ask the candidate the direct question and give the approver the honest read on whether their preferred number lands. Scripts are in references/scripts.md. Record both answers word for word. A trial close that gets "I'd have to think about it" is an answer: something is missing, and Step 2 runs again.

Step 6. Rate the counter-offer risk

LOW, MEDIUM or HIGH against the evidence bar in references/counter-offer-risk.md. Every rating cites the signal that set it. That reference also holds the sourced retention figures to use in the candidate conversation, each with its year and population.

Step 7. Rehearse the resignation

Predict what the current employer will say, who will say it and with what number, and rehearse the candidate's reply. HIGH risk means the rehearsal is booked before the offer goes out.

Step 8. Write the notice-period plan

Dated touches from resignation day to day one, each with an owner and a purpose. Minimum set: resignation day, end of week one, a mid-notice touch with the future manager or team, two weeks out on logistics, the day before start.

Step 9. Post the close card and stop

Post to {{REVIEW_CHANNEL}}, full content every time. A human makes the offer.

[Candidate] / [Role] / Offer stage / [date]
Close-ready: Motive [Y/N] | Numbers [Y/N] | Ceiling [Y/N]
Gap: expectation [X] vs ceiling [Y] on total = [Z] ([%]) | Walk-away: [W]
Recommended structure: [name] | Cost [ ] | Signal [ ] | Risk [ ]
Trial close: candidate "[answer, quoted]" | approver "[answer, quoted]"
Counter-offer risk: [LOW/MEDIUM/HIGH] because [evidence]
Notice plan: resign [date] | wk1 [date] | mid [date] | logistics [date] | start [date]
Decision: Make the offer at [number/structure]? Yes / No
          Book the resignation rehearsal before the offer goes out? Yes / No

Step 10. Write back, after the decision

Only after a human answers Yes:

• Log the close card as a note on the candidate in {{ATS}}, including the trial-close quotes and the risk rating.
• Create each notice-period touch in {{CALENDAR}} or as a task, with {{OFFER_OWNER}} as owner.
• Read every write back. Not found means retry once, then post a visible warning: "Notice plan not scheduled, manual entry needed". A missed mid-notice touch is how a quiet buy-back goes unnoticed.

Write failures never block the card. Never record an offer as made, accepted or signed. Those are human events.