Offer & Close Plan
Builds on Topic 7.
What you'll produce
A one-to-two-page Offer & Close Plan for your top finalist on the Northwind Senior Backend Engineer search — the internal document a recruiter writes before extending a verbal offer so the close doesn't get improvised in the moment. It captures what actually motivates this specific person, frames the full offer (not just the salary number), maps how you'll handle their competing offer and likely objections, sets a gentle-urgency timeline, and scripts the verbal-offer talk track you'll actually say out loud. This is the artifact that completes the search: it proves you can turn a strong candidate weighing other options into an excited "yes" through preparation and honesty, not pressure. Hiring managers and interviewers care about this because the close is where searches are won or lost — a great pipeline means nothing if your finalist signs somewhere else, and offer-acceptance rate is one of the metrics your work is judged on (Topic 9).
Instructions
- Name your finalist and pull their motivations forward. Use the candidate you screened and advanced in Deliverable 4 — same person, don't invent a new one. In 3–5 bullets, write down what genuinely drives them, ranked, drawing on real evidence from your screen notes (what they said about why they're open, what frustrates them now, what they want next). Mark which motivation is the primary lever you'll lead the close with.
- State the competitive situation in two lines. What competing offer (or counter-offer) are they weighing — company, comp, timeline to decide — and what's the one thing that company can't easily match? You're closing against something specific, so name it.
- Frame the full offer beyond salary. List the package in writing: base, equity, bonus/sign-on, then the non-comp levers — the work itself (greenfield ledger product, ownership scope), team and manager, growth/title trajectory, remote/flexibility, and anything Northwind-specific. For each lever, note one sentence connecting it to a motivation from step 1. This is what stops the close from being a salary auction.
- Pre-write your answers to the 3–4 likeliest objections. For each, write the objection in the candidate's voice, then your honest response. Cover at minimum: the competing offer / comp gap, the "company stability vs. a bigger name" worry, and one role-specific doubt (scope, on-call, tech stack — whatever your screen surfaced). No objection gets a manipulative answer; if you can't answer honestly, escalate it (e.g., to Dana) instead of spinning.
- Set a gentle-urgency timeline. Lay out the next 5–7 days as concrete dates/steps: verbal offer → written offer out → check-in cadence → a real decision date you've aligned on with the candidate (not one you imposed). Urgency comes from their competing deadline, not from a manufactured one.
- Write the verbal-offer talk track. Script what you'll actually say when you call to extend the offer — the opening (genuine enthusiasm + the number), the framing of the package, the explicit acknowledgement of their competing offer, and the close question that hands them a clear next step. Write it as words you'd speak, not bullet points.
- Name your walk-away and your escalation path. State the line you won't cross (the comp/terms ceiling Dana gave you in intake) and what you'll do if the candidate's ask exceeds it — so you're closing with a plan, not improvising under pressure.
Worked example
(Finalist: Marcus Reyes — the same candidate sourced via the Deliverable 2 Boolean string and screened as the #1, "advance — top of pipeline" finalist in Deliverable 4. Senior Software Engineer at Stripe (Payments Reliability / Payouts team), NYC; 7 years' experience (2 at Stripe, 3 at a Series C lending startup, 2 at a bank). On Stripe's payout pipeline he designed the exactly-once / idempotency + retry layer that took duplicate-payout incidents to zero over 14 months on a system doing ~6M payout events/day, and in the screen he raised double-entry ledger invariants and integer money unprompted. Northwind req: Senior Backend Engineer, greenfield ledger product, NYC hybrid. Intake band from Dana: $185K–$215K base, 0.15%–0.30% equity, up to $20K sign-on. From the Deliverable 4 screen: he asks $205K base, is a US citizen (no sponsorship), gives 3 weeks' notice / ~1-month start, and is in a final round at a later-stage fintech with a verbal expected in ~10 days — that competing-offer clock is what this close is racing.)
Finalist & motivations (ranked):
- Ownership of a greenfield system (primary lever). In the Deliverable 4 screen he said: "Stripe's great but I'm engineer #200 on a system that's already built — I want to own something from zero again." When I probed what "own" means to him, it was design authority — setting the patterns, not just shipping tickets. Northwind's ledger is greenfield, founding-era — this is his strongest pull and where I lead the call.
- Payments / financial-correctness depth. Unprompted in the screen he brought up double-entry ledger invariants and why he distrusts floats for money (uses integer minor units). The ledger's correctness model is exactly the work he gravitates to — a genuine draw, not just a paycheck.
- Compensation — a real step up, settled so it's not the deciding factor. He named $205K base when pushed for a number — inside our $185–215K band, no flag. He's not coin-operated, but the offer has to clearly beat both staying put and the competing fintech, so comp stops being a reason to hesitate.
- Manager quality / autonomy. His "own from zero again" frustration is about being one of 200 on a built system with no room to set direction. He wants trust and design latitude — a manager who sets the goal and gets out of the way.
- Accountability culture. In the screen he volunteered a miss he owned — a cache that drifted from source-of-truth and caused a 2-hour reporting discrepancy; he wrote the postmortem and added an invariant check. He wants to be somewhere ownership and honest postmortems are the norm, which is a point in Northwind's favor worth naming.
Competitive situation: From the Deliverable 4 screen, he's in a final round at a later-stage fintech (call it Series D, ~1,500 people, a bigger/safer name) and expects a verbal there in ~10 days — that's the real clock the whole close races. The role there is paying around $215K base with a small, late-stage equity grant. The one thing they can't match: it's a mature payments platform where he'd again be one of many on a system that already exists — not the greenfield, design-from-zero ownership he told me he's chasing. That gap is my whole close; I'm not winning on money, I'm winning on scope.
Full offer framing (Dana approved):
| Lever | The offer | Connects to motivation |
|---|---|---|
| Base | $212K (near top of band; he asked for $205K and the competitor is ~$215K) | Beats his own $205K ask by $7K and is within a rounding error of the bigger name — so base isn't a reason to say no. I'm not trying to win on base against a Series D; I'm taking it off the table. |
| Equity | 0.28% (4-yr vest, 1-yr cliff) | Founding-era Series B equity — many multiples of a late-stage grant in real upside if Northwind scales. This is where we actually beat the competitor on comp. |
| Sign-on | $15K | Covers the unvested Stripe equity/bonus he'd forfeit by leaving now; removes a concrete reason to stay put. (Headroom to $20K if Dana approves — see walk-away.) |
| The work | Founding engineer on the new ledger product — owns the schema, service design, and the double-entry correctness model from day one. | His #1 motivation, in his own words: "own something from zero again," with design authority, not tickets. This is the line the whole call is built around. |
| Domain | Payments infrastructure where correctness is the product — the ledger-invariant, integer-money work he raised unprompted in the screen. | His #2 motivation. He already thinks in exactly-once and double-entry; here that's the job, not a side concern. |
| Manager | Reports to Dana (VPE) directly until the team grows; Dana's style is "set the goal, get out of the way" (ex-Stripe payments herself, so she speaks his language). | Answers his "engineer #200, no room to set direction" frustration directly. |
| Growth | Clear path to Staff / first Eng lead on the ledger team as it scales from 1 → 4 engineers. | Founding scope he can't get as one of ~1,500 at the later-stage fintech. |
| Flexibility | 2–3-day hybrid in NYC (which he confirmed works in the screen), no on-call for the first quarter while the service is pre-prod. | Matches what he already said fits; the no-on-call ramp lets him focus on the greenfield design that's his #1 pull. |
Pre-written objection handling:
- "The other place is a bigger, later-stage name — it's the safer bet for me." — "Fair, and I won't pretend Series B is the same risk as Series D. Two honest things. One: Northwind is Series B with 18 months of runway and revenue growing — I can share the same deck Dana shares with candidates, no spin. Two: on your own terms, you told me you want to own something from zero again — the safe, later-stage role gives you the opposite, you'd be one of ~1,500 on a platform that already exists. 'Founding engineer who built the ledger' is the stronger story for the Staff jump you're aiming at than 'one of many on a mature payments stack.'"
- "Their base is a bit higher and the equity is more liquid." — "True on both, and I'd rather be straight than oversell. I got your base to $212K — past your own $205K and basically level with theirs — so base isn't the deciding factor either way. On equity: theirs is more liquid, mine is a bigger bet — founding-era Series B grant versus a thin late-stage slice. If you think the ledger and the company work, the Northwind equity is where the real upside is; if you don't, no equity story should talk you into it. That's an honest 'depends on what you believe,' not a pitch."
- "What if the ledger product gets deprioritized and I'm stranded on a dead bet?" — "Honest answer: it's a funded, board-level priority — it's literally why this req has been urgent for a month. But I won't promise certainty I can't give. What I can tell you is you'd report to the VPE on the company's top engineering bet, which is the safest seat in the building if priorities ever shift. You raised ledger invariants and integer money unprompted in our screen — you clearly care whether this is built right; the fastest way to judge that is to ask Dana directly. Want me to set up 20 minutes?"
- "I've got a final-round verbal coming in ~10 days — I don't want to decide before I see their number." — "Completely reasonable, and I'm not going to pressure you to jump before you've seen it. Here's what I'd suggest: let me get the written offer to you tomorrow so you can hold a real, concrete Northwind number against theirs instead of a verbal promise. You set the decision date — if it's after their verbal lands, that's fine, I just want you choosing between two real offers, not rushing one of them."
Gentle-urgency timeline (anchored to his competing verbal, expected ~10 days out per the screen):
- Day 1 (today, Mon): Verbal offer call with Marcus (talk track below). Re-confirm the timing of his other final-round verbal and agree a real decision date that sits after it, so he's choosing between two real numbers.
- Day 2 (Tue AM): Written offer in his inbox within 24h of the verbal — speed signals we want him, and gives him a concrete Northwind number to weigh against a not-yet-arrived verbal.
- Day 3 (Wed): 20-min call with Dana (ex-Stripe payments) to answer the "is this product real / is it the design ownership I want" question directly, founder-to-engineer.
- ~Day 8 (early next week): Light check-in ("anything I can get you a clear answer on before your other verbal lands?") — supportive, not chasing.
- ~Day 10–11 (after his other verbal): Decision date he set, just past his competing offer. I'm reachable, not pinging him hourly.
- Urgency is anchored to his real ~10-day competing-offer clock — I'm not inventing an exploding offer or pushing him to decide before he's seen the other number.
Verbal-offer talk track (what I'll actually say):
"Marcus — I've got good news, and I wanted to tell you myself. Northwind wants to bring you on as the founding engineer on the ledger team, and I'm genuinely excited about it. The offer is $212K base, 0.28% equity, and a $15K sign-on — that's past the $205K you'd mentioned and right alongside what the bigger-name place is likely to land at, so I don't want base to be the thing you have to weigh.
Here's why I think this is the right move for you specifically: in our screen you said you're tired of being engineer #200 on a system that's already built, and you want to own something from zero again — with real design authority, not just tickets. This is exactly that. You'd own the ledger's schema, its service design, and the double-entry correctness model from day one — the integer-money, exactly-once stuff you brought up unprompted. You'd report to Dana, who's ex-Stripe payments herself and runs 'set the goal, get out of the way.' That's the one thing the later-stage offer can't give you, because over there you'd again be one of many on a payments platform that already exists.
I know you've got a final-round verbal coming in the next week or so, and I'm not going to pressure you to decide before you've seen it. What I'd love to do is get the written offer to you by tomorrow morning so you've got a real Northwind number in hand, and set up 20 minutes with Dana this week so you can ask her directly about the product and the design scope. Does that work? And is there anything that, if I got you a clear answer on it, would make this an easy yes?"
Walk-away & escalation: Dana's ceiling from intake is $215K base / 0.30% equity / $20K sign-on. I'm opening at $212K base / 0.28% / $15K to leave real room to move. If Marcus counters — say the later-stage verbal comes in higher and he asks for $218K — I don't improvise. I tell him honestly I need to take it to Dana, and I bring Dana a recommendation, not a blank ask: e.g., go to the $215K ceiling and add the remaining $5K of sign-on headroom (to $20K) and lean on the equity-upside story, rather than blowing the band. Hard walk-away: an ask that only the base can satisfy above $215K, or insisting on a Staff title + Staff comp on day one that the founding role can't carry until the team scales — Dana ruled both out at intake. If that's a true dealbreaker for Marcus, it's a real mismatch, and I'd say so kindly rather than over-promise a number or a level I can't stand behind. Better to lose him clean than to close him into a role that won't hold.
Rubric
The app's AI scores the learner's submission against these criteria and gives feedback. Levels: Needs work (1) / Solid (2) / Excellent (3). Passing = every criterion at Solid or above.
- Motivation insight — 1: generic guesses or "wants more money," no evidence · 2: specific, ranked motivations tied to the candidate · 3: ranked, evidence-based motivations drawn from prior screen notes, with a clear primary lever the close is built around.
- Full-offer framing (beyond salary) — 1: only a salary number · 2: lists comp plus non-comp levers · 3: every lever explicitly connected to a stated motivation, so the offer answers this person, not a generic one.
- Competing-offer & objection handling — 1: ignores the competition or relies on pressure/manipulation · 2: names the competing offer and answers the main objections plausibly · 3: names the specific gap the competitor can't close and answers each likely objection honestly, escalating rather than spinning when needed.
- Gentle urgency & timeline — 1: missing, or manufactured/exploding-offer pressure · 2: a concrete next-steps timeline · 3: a dated, momentum-keeping plan anchored to the candidate's real deadline, with a decision date aligned (not imposed).
- Verbal talk track — 1: bullet points or a scripted-sounding pitch · 2: speakable words that extend the offer and acknowledge the competition · 3: a human, enthusiastic talk track that leads with the candidate's primary motivation, states the full offer, names the competing offer directly, and ends with a clear close question.
- Walk-away & honesty discipline — 1: no limits, or willing to over-promise · 2: states a comp ceiling and an escalation path · 3: clear walk-away line and escalation plan, with a non-manipulative stance that surfaces a genuine mismatch honestly rather than closing at any cost.
- Coherence with the search — 1: disconnected from earlier deliverables · 2: uses the same finalist and req · 3: the close visibly traces the thread — intake must-haves → the candidate you sourced, screened, and tracked → an offer framed around what this search taught you about them.