Named Account Lead: One Accountable Person, Discovery to Handover

Eight months into a build, you are sitting across the screen from the third project manager you have met on the engagement. The first ran your discovery. The second inherited a wiki that the first never quite finished. The third has joined to "stabilise" the project ahead of launch. Each handover lost a week. Each new manager arrived without the conversational memory of why a particular trade-off was made in sprint two. Each one rebuilt a working relationship from zero, while your team did the unpaid emotional labour of explaining the product to someone new. By the time the third introduction happens, you are no longer being managed. You are managing the engagement on the vendor's behalf, and you are doing it for free.

The failure pattern this article is about is not a single bad project manager. It is the structural choice — common across the agency industry — to staff engagements with whoever is available on the project management bench, rotate them as utilisation demands, and treat continuity of accountability as somebody else's problem. That choice creates the rotating cast you have probably experienced at least once. It is also, in our experience, the single largest predictor of whether the relationship between client and vendor compounds or quietly decays.

The argument of this article is that a named account lead — one named senior person, accountable for the engagement outcome, from Discovery Workshop™ through to handover — matters more than any other piece of project management process you might invest in. Not because process is unimportant, but because process administered by a rotating cast becomes a series of disconnected status meetings. Accountability without ambiguity is the foundation of every engagement that works. It is the structural commitment that makes the rest of the Built to Last™ 2.0 project delivery framework hold together over time.

The Argument

There is a strong version of this argument and a careful one. The strong version: every other piece of engagement discipline — change control, decision logs, risk registers, sprint demos — is downstream of who is accountable for the outcome. Without a single owner, the artefacts become defensive rather than productive. They exist to allocate blame later instead of surfacing reality now. The careful version: a strong project management process can paper over the absence of named accountability for a while, but the seams show under pressure. When a deadline slips, a scope conversation gets tense, or a senior stakeholder asks the question that nobody has rehearsed an answer to, the difference between an engagement with one accountable person and one with a rotating cast becomes immediately visible.

The reason is simple. Accountability is not the same as task ownership. A project manager owns the tasks on a sprint board. An account lead owns the outcome the tasks exist to produce. Those are different jobs. They sometimes get done by the same person. They are almost never well-served by being rotated between three different people across an eight-month engagement.

What you are buying when you engage an agency is not, in the end, a set of deliverables. It is the judgment that decides what to build, what to defer, and what to flag as risk before the risk becomes an incident. That judgment compounds. The person who ran your discovery knows why the scope was shaped the way it was. The person who ran sprint four knows the trade-off you accepted on the auth flow. The person who is going to be on the launch call ought to know both. When all three are the same person, the engagement gets better month over month. When they are not, the engagement gets thinner.

What "Named" Actually Requires

It is easy to put a name on the kickoff slide. The harder commitment is what stands behind the name.

A genuine named account lead is the same senior person from week one to handover. Not a different person each sprint. Not a delivery manager paired with a "client success" representative who shows up only when escalations happen. One person, with the authority to make commitments on the agency's behalf, who is in the engagement deeply enough to know its history without consulting a wiki.

This person carries the institutional memory of the engagement. They were present in the Discovery Workshop. They saw the Locked Scope Document™ produced. They sat through the architecture decisions in sprint zero. They understand why the original ambition was de-scoped and what was de-scoped to make room. When a request comes in during sprint six that contradicts a decision made in sprint two, they can name the contradiction in the meeting rather than three days later by email.

They are reachable when it matters. Reachable does not mean available 24/7 — that is a sustainability problem and an honesty problem. It means that when something is genuinely on fire, the client knows whom to call, and that person picks up. It also means that during business hours, asynchronous messages get a response inside a day rather than a week. The bar is low. Most engagements fail it routinely.

They have the authority to commit. The named account lead is not a relay between the client and an unnamed senior person inside the agency. If a scope change needs to be approved, they can approve it. If a sprint needs to be replanned, they can replan it. If a difficult conversation needs to be had, they have it directly — not by email forwarded from someone else. The absence of this authority is one of the most reliable tells that a "named lead" is nominal rather than real.

They stay through handover. The day the engagement ends and the product is being transitioned to the client team is the day the lead's understanding of the engagement is most valuable. A handover led by someone who joined three weeks ago is not a handover; it is a document drop. The structural commitment of staying through handover is what turns an engagement into a relationship that compounds, in line with our delivery approach across custom software engagements.

What the Lead Actually Does

The role is easier to describe by what it is not than by a tidy job description.

It is not a project manager. The lead may also do project management — sprint planning, ticket grooming, status reporting — but the core of the role is judgment, not coordination. The work that distinguishes the lead from a PM is the work nobody can write a Jira ticket for: noticing that sprint three is drifting toward the wrong shape and naming it; noticing that the client is increasingly silent in demos and asking why; noticing that two stakeholders are giving the team contradictory direction and forcing the resolution in a meeting rather than letting it surface as bugs in week ten.

It is not a sales account manager. A sales AM owns commercial relationship continuity. A named account lead owns delivery outcome accountability. The two roles share a vocabulary and almost nothing else. A lead who is measured on upsell rather than outcome quickly stops being useful to either side.

It is not a steering committee. Many agencies attempt to replace named accountability with a committee structure — multiple senior people who weigh in, none of whom is on the hook. This is the worst version. It produces meetings without decisions and a documentation trail that protects everyone except the client.

The role is, properly, a senior practitioner — usually a delivery lead, engineering lead, or principal who has shipped products before — who carries the client's outcome on their own scorecard. They run the Discovery Workshop, attend the architecture session, are present at sprint demos, sit inside the Production Readiness Review™ before launch, and stay through the post-launch period. They write the Decision and Accountability Log and the Change Control Register entries that matter. They are the person whose name is on the wall when the engagement is being audited internally — which means they have an interest in surfacing risk early, not late.

Where It Fails Even When It's "There"

Some of the most painful versions of this failure happen when a named lead exists in name only.

The first failure mode is the bait-and-switch. A senior name appears on the proposal. After the contract is signed, day-to-day delivery is handed to someone two levels more junior, with the named lead reappearing only for monthly steering meetings. The relationship is, in practice, with the junior delivery manager. The senior name functions as a brand asset, not an accountable person.

The second is the part-time lead spread across too many engagements. The named person is real, the seniority is real, but they are nominally on six engagements simultaneously. Each gets fifteen per cent of their attention. They cannot carry institutional memory for any of them well. The client experience is of a person who is always slightly behind on the context — which is functionally similar to a rotating cast, with the added frustration of looking like it should be better.

The third is the lead who is structurally not empowered. The seniority is real, the attention is real, but every decision that matters has to be ratified by a partner or principal who is not in the engagement. The lead becomes a relay. The accountability is theatre. Clients feel this within a few sprints.

The fourth is the engagement that has structural single-point-of-failure risk. Even when the named lead is real, empowered, and engaged, what happens if they leave the agency mid-engagement? A serious version of the role includes a documented continuity plan — a deputy who has been in the room throughout, so a transition is recoverable in days rather than a re-onboarding in weeks. The point of a single accountable person is not to depend on that single person's continued tenure; it is to provide a single, clear locus of responsibility while the engagement is in flight, with a deputy structure that protects the client if circumstances change.

One Composite

A mid-sized SaaS client we worked with came to us after eight months on a build with another vendor. Across those eight months they had been introduced to three different project managers. The first ran a kickoff that everyone remembered fondly. The second arrived in month three after the first was "redeployed onto a higher-priority account" and spent the first two weeks re-reading documentation. The third was brought in around month seven to "stabilise" the project as a launch deadline drifted.

The technical work, according to a code review we ran, was not bad. The engineers had done sound work. The damage was structural and human. By the time we picked up the engagement, the client team was exhausted from rebuilding context every time a new PM joined. They were no longer raising risks because each new PM had to be educated on what the risk was before they could act on it, and the education cost more energy than the risk itself. Trust had not collapsed; it had quietly evaporated.

The engagement that replaced it was a contrast worth naming. One named lead from week one through handover, ten months later. The same person in the Discovery Workshop, the architecture session, every sprint demo, the launch call, and the 90-day post-launch review. The client told us afterwards that the most valuable difference was not anything specific the lead did; it was that they only had to explain things once. The conversation in month ten could pick up directly from the conversation in month one. That is what a relationship compounding looks like, and it is what most engagements never get to experience because they are starting over every three months by design.

When This Matters Most, When It Can Wait

It would be dishonest to claim this matters equally for every engagement.

It matters most when the engagement is long enough to develop institutional memory worth preserving — anything over three months, and especially anything over six. It matters most when the work spans more than one phase of the Built to Last 2.0 framework — discovery into build into post-launch — because the value of the named lead is the continuity across those phases. It matters most for clients whose internal team is small enough that explaining the product to a new face costs real productivity, which is the case for most founders and most mid-market product teams.

It matters less for short, single-phase pieces of work — a two-week spike, a fixed-scope component build, a one-off audit. In those cases a competent project manager who is good for that scope is enough. Continuity from discovery to handover is not a useful concept when there is no discovery and no handover.

It also matters less when the client's internal team is the primary owner of the engagement and the agency is providing capacity, not judgment. That is a different shape of relationship; we run it under a team-as-a-service model, where the equivalent commitment is a named squad lead rather than a named account lead, but the principle is the same: one person, accountable, present from start to end.

What this is never, in our experience, optional for is the multi-month product build where the client is betting real budget on the outcome. There, the named account lead is the structural commitment that lets the rest of the framework do its work.

What to Do This Week

If you are mid-engagement and reading this with a sinking recognition, the action is direct. Ask your vendor, in writing, two questions: Who is the single accountable person for the outcome of this engagement, and what is their continuity commitment from now through handover? If the answer is a list of three people, or if it equivocates, you have learned something important about why the engagement feels the way it does.

If you are scoping an engagement, ask the same questions before signing. Treat the answer as load-bearing. For the broader question of how to evaluate a vendor before you commit, our founder's guide to hiring an app developer covers the surrounding decisions. The companion read on the other side of named accountability is the Knowledge Transfer Protocol — what the named lead must build into the system, not into themselves, so the engagement is recoverable even if circumstances change.

Frequently Asked Questions