Making the offer quickly after the decision
The decision meeting produces one artifact: a signed decision note that names the chosen candidate, the score evidence, the agreed salary band and the offer expiry. Write it in the meeting, not after it. The offer call then happens within one working day, and the written offer follows within two hours of that call.
Speed is not pressure. A short offer window works when the candidate already knows the band, the start date and the first-week plan. If your process has run for three weeks, a candidate kept waiting a further week is the most common reason a small team loses its first choice. The table below sets out the trade-offs.
| Offer speed | Drop-off risk | Team effort spent | What to prepare first |
|---|---|---|---|
| Same day as decision | Low, roughly 1 in 10 candidates reopens the search | 2 hours of manager time, 1 hour of admin | Salary band, start date, first-week schedule |
| 2 to 3 days | Moderate, roughly 3 in 10 candidates take another call | 4 hours of manager time, 2 hours of admin | Approval chain, reference check slots |
| Over a week | High, roughly 6 in 10 candidates accept a competing offer | 6 or more hours of chasing, rebooking and re-explaining | Nothing, the delay is the problem |
Run a thirty-minute offer preparation call before the final interview stage, not after it. Produce the salary band, the start date options and the first-week outline in that call. The decision note then becomes a formality. SHRM talent-acquisition coverage repeatedly notes that delays between decision and offer are a leading cause of declined offers, so treat the offer call as part of the interview loop, not a separate admin task.
Counter-offers: what to negotiate and what to hold
Before the offer call, write a negotiation grid with three columns: negotiable, fixed, and trade. Salary sits in negotiable within the band. Start date sits in trade, meaning a later start can be exchanged for a signing adjustment or an earlier review. Equity structure, notice periods and role scope sit in fixed, and you say so plainly on the call.
- State the band and the offer figure in the first two minutes.
- Ask what would make the offer workable, then stay silent for ten seconds.
- Write the candidate's ask in the grid before responding.
- Respond to negotiable items on the call; respond to fixed items within one working day in writing.
A founder who has spent six weeks interviewing often concedes on fixed items to close quickly. That is the wrong trade. Concede on start date or on a review at ninety days, and hold the band ceiling. If the candidate's counter sits above the band, say the band is the band and offer the review instead. The written follow-up email repeats the agreed terms in five lines or fewer so both sides have the same record.
Rejection messages that keep the door open
Every candidate who reached a scored interview gets a rejection within two working days of the decision. Write from a template with three parts: the decision, one specific reason tied to the role brief, and one line about future openings. Do not use the phrase "not a culture fit" and do not leave the reason blank.
For candidates rejected at CV stage, send a short note within five working days. This is where the founder with a vague ad and a pile of mismatched CVs recovers goodwill: rewrite the ad before reposting, and tell the mismatched applicants which requirement they missed. A rejection email that names the missing requirement is the cheapest employer-brand work a small team can do.
- Decision stated in the first sentence.
- One reason drawn from the scoring grid, not from memory.
- One sentence on what would change the answer.
- Invitation to stay in touch, with no promise of a future role.
Keep a rejection log with the date sent and the reason code. After ten rejections, read the log and look for a pattern in the reason codes. A repeated code usually means the role brief is wrong, not the candidates.
Onboarding handoff: the first week planned before day one
The onboarding handoff is a one-page plan written before the offer is accepted, not on the new hire's first morning. It names the first-week schedule, the first task with a real deliverable, the person who answers questions, and the thirty-day check-in date.
Build the plan in a forty-five-minute session with the hiring manager and one teammate. The output has four parts:
- Day one: accounts, tools and a named buddy, completed before the start time.
- Days two and three: two short meetings with adjacent teams, thirty minutes each.
- Days four and five: one small deliverable the new hire can finish and show.
- Day thirty: a scheduled check-in with three written questions sent in advance.
Atlassian's hiring-process guidance treats the handoff as part of the hiring loop rather than a separate HR task, which matches what small teams see: a new hire with no first-week plan spends their first month guessing at priorities. Send the plan to the new hire two days before the start date so day one begins with work, not setup.
Measuring your hiring process after each hire
Run a thirty-minute retrospective within two weeks of the start date. The artifact is a one-page loop review with four numbers and two notes. The numbers are: days from role brief to first interview, days from final interview to offer, offer acceptance outcome, and days from acceptance to start. The notes are one thing that worked and one thing to change.
Track the same four numbers across hires. A pattern of offers taking more than three days points at the approval chain. A pattern of first interviews arriving more than ten days after the role brief points at scheduling. Neither problem is solved by interviewing more candidates.
Close the review by assigning one change to one person with a date. That single action is what separates a hiring process that improves from one that repeats the same delay every quarter. File the loop review beside the role brief so the next hire starts from evidence rather than memory.
Today, open your last decision note and check the date on it against the date the offer was sent. If more than two working days passed, write the offer preparation call into your next loop and run it before the final interview stage.
Sources
The substance of this page rests on the published material linked below. It is independent of this site and was read before writing.