How do you answer "who will implement this?" in an AI deal?

With a name, a number, and a date. Name the person on your side who owns the rollout, say how many hours a week you need from the buyer's team, pick one first use case, and put a handover date in writing before the contract. AI buyers have already seen the demo work. What they doubt is that it will work inside their company.

Why is implementation the question now?

Because one of the biggest model labs is paying to solve it.

EdTech Innovation Hub reported on Oct 7 that Anthropic is committing $100 million to Claude Frontier Academy, a program to train 10,000 "Frontier Deployed Engineers" by the end of 2027. Engineers from Accenture, Bain, Capgemini, Deloitte, McKinsey and Morgan Stanley are in the first cohorts. Training runs through a simulated enterprise deployment, from picking a use case and getting through security review to handover. Engineers who pass an assessment then lead a real Claude project inside their own organization during a 12-week residency.

Anthropic's Steve Corfield describes the goal as taking Claude "from an idea to a system in production." That's the gap a lab just put $100 million into.

If Anthropic is paying to train 10,000 engineers to get Claude into production, your buyer is right to ask who's getting your product there.

What is the buyer really asking?

"Whose time does this eat, and what happens when it breaks?"

Under the purchase label, "an AI tool for X," sits a simpler desire. The buyer wants to look smart for picking you six months from now. The fear is a stalled rollout with their name on it.

Matt Dixon and Ted McKenna's research for The JOLT Effect, built on more than 2.5 million recorded sales conversations, found that 40% to 60% of deals are lost to customer indecision. They put the majority of those down to fear of failure, ahead of love for the status quo. "Who will implement this?" is that fear said out loud.

What should the answer include?

Five things on one page, before the proposal.

1. A named owner on your side. A person with a calendar. "Our team" doesn't count.
2. The hours you need from theirs. For example, two hours a week from one ops lead for six weeks. If you don't know your number, look at your last few deployments and find out.
3. One first use case. One workflow, with a before-and-after number they already track.
4. The security and data path. Who reviews it, what you send them, and when.
5. A handover date. The day their team runs it without you, and what "running it" means.

This lives inside the mutual action plan and gets restated in the proposal.

Should I charge for implementation?

Charge for it, or scope it tightly. Don't give it away without limits.

Free, open-ended setup sounds generous on the call and becomes free consulting by week three. A paid or tightly scoped implementation tells the buyer you've done this before. It also gives them a stake, which makes their two hours a week actually show up.

If you're early and implementation is free, cap it in writing: one use case, a fixed number of weeks, named people on both sides.

What if I don't have implementation capacity?

Sell smaller, or partner.

A founder with no deployment team shouldn't promise an enterprise rollout. Pick buyers whose first use case one person on their side can stand up with your help. Map the work first, so you know what that one person actually has to do.

The consultancy names in Anthropic's first cohorts point at the other path. The firms your buyers already pay to implement software are building AI deployment benches. An implementation partner who already sits inside your buyer's account can answer this question better than your deck. If you go that way, run it like a real partner motion with shared accounts and named owners.

What mistakes lose the deal at this question?

• Saying "most customers are live in a day" to a buyer with a security team.
• Naming a support inbox instead of a person.
• Hiding the hours you need from their team until after signature.
• Promising a handover date you've never hit before.
• Treating implementation as a post-sale onboarding detail. If the buyer doesn't believe the rollout, there's nothing to onboard.

What should I do this week?

1. Pull your last five closed-won deals. Write down who on the buyer's side did the work and how many hours it took.
2. Turn that into a one-page implementation plan.
3. Bring it to the second call, not the last one.
4. Put a named owner and a handover date in every open proposal.
5. Count how many deals ask "who will implement this?" and how many of those close.

The buyer has seen the demo work. Show them the person and the date that make it work for them.

Start Signals, Convert, Grow

FAQ

Is this the same as customer onboarding?

No. Onboarding happens after signature. This answer happens before it, so the buyer has a reason to sign. The plan you sell becomes the onboarding plan later.

What is a forward deployed engineer?

An engineer who works with or inside a customer's organization to get software into production. Anthropic's new program calls them Frontier Deployed Engineers and trains them on a full deployment, from use case to security review to handover.

When should I bring up implementation?

On the second call, once the buyer agrees the problem is worth solving. Waiting for the proposal stage means the buyer has already been worrying about it alone.

Can a solo founder sell this way?

Yes, if the first use case is small. Name yourself as the owner, cap the hours, and pick buyers whose first workflow one person on their side can run.