Harvey puts an ex-lawyer in every deployment, and now certifies people it doesn't employ

Harvey now staffs an ex-attorney inside every customer deployment — roughly 180 of them company-wide — and has begun certifying outsiders it will never employ to do the same job. Chief product officer Anique Drumright set out the structure on stage at SaaStr AI, SaaStr's own conference, and Jason Lemkin wrote it up on September 13. Figures below come from Drumright, from Lemkin's reading of Harvey's job ads, and from harvey.ai pages we checked ourselves.

The title is legal engineer, and everyone holding it walked away from practice. Most brought eight to ten years of it, Drumright said; the job ads set a lower bar, a law degree plus three years of real legal work. These are not advisers who drop in for a workshop. They sit on the account.

"180 legal engineers, ex-lawyers, help our customers build their agents. They are our subject matter experts."

That is Drumright, quoted by Lemkin from an earlier session. Harvey also fields the familiar forward-deployed pod — a product manager, a lawyer or two, engineers, building bespoke — but Lemkin draws the line most write-ups miss: the pod is rationed and the domain expert is not. Every deployment gets the lawyer. Only some get the engineers.

Adoption moved out of the support budget

The detail worth sitting with is the pay. On the careers page Lemkin read, the post-sales version offers an OTE between $220,000 and $320,000, three-quarters base and a quarter variable, plus equity. Variable comp means the person carries a number, and a domain expert with a quota is not a support function. It is a revenue function delivered by someone who used to do the customer's job.

Harvey also breaks the role into three published tracks: pre-sales, running discovery and demos beside account executives; post-sales, owning onboarding, enablement, adoption and utilization and feeding renewal and expansion; and custom work, designing agents and playbooks in plain language with no engineer writing code.

That is an accounting decision as much as an org chart. One track is a sales cost, one a retention cost, one services. Lemkin's argument is that most companies blur all three into a single "solutions" line and then cannot explain their own gross margin, and it holds up. The consequence for a marketing team is narrower: it decides which of those three people is sitting with your customer when your expansion campaign lands, and what they say about it.

The certification is the part worth copying

Harvey Academy has added a Certified Legal Engineer track — self-paced, open to anyone, badge at the end. The courses are live on Harvey's site; we confirmed the path exists. Lemkin reports Harvey's framing: the discipline is young and today's practitioners get to define it. Harvey's own page, he notes, puts AI use across law firms and legal departments at 14% two years ago against 43% now.

Read the certification as distribution, not education. Harvey cannot hire a lawyer for every legal department on earth, so it is converting the role into a credential the buyer's own staff can earn. Vendor certifications normally teach people to operate a product; this one names a job. If it takes, the vocabulary a buying committee uses to describe the work is Harvey's vocabulary, and the ceiling on Harvey's deployment model stops being Harvey's headcount.

Harvey's careers page claims over 700 partners in 58 countries and more than half the Am Law 100 — its own figures on its own site, so treat them as marketing. Lemkin puts the platform at over 25,000 custom agents, and says the $11 billion March round earmarked money to grow these teams.

What a software marketer should change

Almost nobody can copy the staffing. The diagnosis is free. Adoption stalls at the pilot because nobody in the room has ever done the customer's job, and a product tour does not redesign a workflow. If that is true of what you sell, no volume of onboarding content closes the gap, and a rival who staffs it beats you on the metric nobody publishes — pilot-to-production rate, not win rate.

• Name the individual who would be credible redesigning a live customer's workflow. If that name sits on the customer's org chart rather than yours, they set your adoption ceiling, not you.
• Find out which go-to-market role owns adoption and whether it carries a number. If none does, adoption is nobody's job and the renewal forecast is fiction.
• Move content budget from explaining the product to producing what a domain expert needs in the room: workflow maps, failure modes, the objections a practitioner raises that a buyer never will.
• Before proposing a certification program, check that the role you would name is work somebody already does. A credential for a job nobody holds is a brochure with a badge on it.

Lemkin makes the caution himself: gross margin, the hiring pool, the ramp for people leaving a decade-long career, and the difficulty of managing a former partner who will not take direction like a junior solutions engineer. At Harvey's contract sizes a quarter-million-dollar human on every deployment is defensible. At yours it may not be. That is a spreadsheet question, and it deserves an answer before it becomes a positioning one.