Field notes

The capture-lead role, reconsidered

The shape of the capture-lead role we started with, the shape it became, and why the difference matters for anyone hiring into the role in 2026.

PursuitAgent 3 min read Team & Workflow

We hired our first capture lead about a year ago. The role description we wrote at the time reads, today, like a document from a different company. Here is the shape we started with, the shape it became, and what changed.

The shape we started with

The original job spec, May 2025:

  • Owns the bid/no-bid decision on inbound RFPs.
  • Runs the capture call for each pursued RFP: buyer research, competitive analysis, win-theme development.
  • Works with proposal manager to hand off an approved capture plan before drafting begins.
  • Attends the gold-team review for each bid.
  • Logs outcomes back to the capture tracker.

About 60% internal-facing (planning, coordination) and 40% external-facing (buyer research, occasional calls with relationship-holders inside target accounts).

The shape it became

A year later the role is about 50/50 and the task mix looks different:

  • Bid/no-bid remains. This is still the core responsibility and the one that hasn’t changed.
  • Capture-call prep is now heavily AI-assisted. Buyer research that used to take a capture lead 3–4 hours is now a 20-minute review of an AI-drafted brief. The role is judgment on top of the brief, not the drafting of the brief.
  • Relationship work expanded. The hours freed from research went to actual conversations with people at target accounts — pre-RFP outreach, informal debrief calls after losses, warm intros for the account team.
  • Post-mortem ownership became explicit. The capture lead now owns the post-mortem for every pursued bid, including the write-back to the KB. This used to be ambiguously shared with the proposal manager and the work didn’t reliably happen.
  • Gold-team attendance was dropped. We realized the capture lead’s feedback at gold-team was too late to be useful; their input belongs at the kickoff and at the draft-outline review, not at submit-minus-one.

Why the shape changed

Three things drove it.

First, AI-assisted buyer research got good enough that the four-hour-on-Google version of capture prep was no longer the best use of a senior person’s time. The hours freed up went to judgment and relationships.

Second, the capture-lead-attends-gold-team pattern had the feedback arriving too late. A capture lead’s input belongs at outline review, two weeks earlier. The same critique heard at gold team is frustration.

Third, post-mortem write-back was the single highest-leverage activity nobody owned. The eight-stage pipeline makes this explicit as stage 8; in practice it was orphaned for most of the first year. Moving it to the capture lead’s spec put it on a named calendar.

What this means for anyone hiring the role in 2026

Two specific recommendations:

Hire for relationship range, not research output. The person who would have been great at capture-lead work in 2020 was a relentless researcher. The person who is great at it now is someone who reads a 20-minute AI-drafted brief critically and then uses their time to talk to people. These are different candidates. Interviewing for the old role and hiring the wrong kind of person is the most common mistake we see.

Write post-mortem ownership into the job spec. Not “participates in post-mortems” — owns them, runs them, is on the hook for the KB write-back. Without explicit ownership, the activity doesn’t happen. We learned this the hard way.

The takeaway

The role name stayed the same. The role didn’t. A 2025 job description for capture lead is a 2026 recipe for a bad hire. Rewrite it.

Sources

  1. 1. The 8-stage RFP response pipeline
  2. 2. SME collaboration, the in-year update