Sales Motion as a Hiring Constraint: The DNA-Driven Hiring Brief

The hiring brief goes out for an enterprise AE. Candidates come in with logos: Salesforce, ServiceNow, Workday. Six months later, quota attainment is 40% and the VP of Sales is explaining to the board that "the talent pool is thin." Nobody mentions that the product closes in 14 days on a self-serve trial and the AE's job was supposed to be 6-month multi-stakeholder deals. The reps weren't wrong for the role. They were wrong for the product. The brief was written for the deal size the founders wanted, not the motion the product actually requires.

The Three Dimensions That Drive Sales Motion Complexity

Every product has a natural selling motion baked into its architecture. That motion is determined by three variables, and getting any one of them wrong produces a hiring brief that will reliably select the wrong candidate.

Implementation Complexity

Complexity is how much a buyer has to change to get value from the product. A tool that plugs into Slack and surfaces insights in 30 seconds has near-zero implementation complexity. A platform that requires a 90-day integration, data migration, and IT sign-off has maximum complexity. The rep you need is downstream of this score.

Low-complexity products sell on evidence, not on explanation. The buyer can try it, see it work, and decide. A rep who spends three calls explaining architecture is adding friction to a motion that doesn't need it. High-complexity products cannot be trialed into purchase. Someone has to guide the buyer through what the product will become once deployed, and that requires a different kind of rep entirely: someone who can hold a multi-threaded conversation across IT, procurement, and the business unit without losing the thread.

Time-to-Value

TTV is the honest answer to the question: how long before the buyer sees something that feels like a win? Products with TTV under 30 days can close on momentum from a trial. Products with TTV over 90 days require the rep to sell a future state the buyer cannot yet see.

This distinction is critical for hiring because selling a future state is a fundamentally different skill from closing on demonstrated value. The PLG-assist rep is essentially a concierge for a value the product has already delivered. The enterprise AE is a storyteller, a project manager, and a political navigator. Treating these as the same job, differentiated only by deal size, is where the mismatch begins.

Buyer-User Split

The buyer-user split measures how far the economic buyer sits from the person who will actually use the product day-to-day. When the user and buyer are the same person, the product sells itself to the person experiencing the problem. When the buyer is two levels above the user, someone has to translate the user's pain into executive language and build a business case the buyer can approve.

A developer tool bought by developers has almost no buyer-user split. An HR platform bought by a CHRO on behalf of 5,000 employees has an enormous one. The rep who thrives in the first environment fails in the second because the skills that win developer trust (technical depth, rapid demo, low-pressure follow-up) are orthogonal to the skills that win CHRO buy-in (business case construction, ROI framing, relationship management across functions).

What Each Combination Implies for the Hiring Profile

The matrix of complexity, TTV, and buyer-user split produces five distinct hiring archetypes. Most companies hire from two of them and wonder why they cannot scale.

Low complexity, short TTV, low buyer-user split: this is the PLG assist profile. The product already sells itself to the user. The rep's job is activation, expansion, and conversion from free to paid. The candidate background to screen for is customer success, not sales. They should be comfortable with usage data, fluent in product features, and skilled at identifying expansion signals inside an existing account. Their quota is net revenue retention, not new ARR.

Low-to-medium complexity, medium TTV, medium buyer-user split: this is the mid-market AE profile. The product needs some explanation, the buyer is one level above the user, and deals close in 30-60 days. The candidate should show evidence of running a full sales cycle without heavy pre-sales support. They need to be able to demo credibly without an SE, build a basic business case, and manage a small buying committee. The red flag in a resume here is a history of working with dedicated solution engineers on every deal. That candidate will stall in a mid-market motion where they are expected to carry the technical conversation themselves.

High complexity, long TTV, high buyer-user split: this is the enterprise AE profile. Deals are 6-18 months. The buying committee has 8-12 stakeholders. IT, legal, security, and procurement all have veto power. The candidate should show a history of multi-threaded deals, documented champion development, and the ability to maintain momentum across a quarter without a single decision-maker. Logos matter here, but context matters more. An enterprise AE who sold a product with 30-day implementation cycles is not the same as one who sold a platform requiring organizational change management.

High complexity, any TTV, high buyer-user split where the technical evaluation is the deal: this is where the solution engineer becomes load-bearing. The SE is not there to support the AE. In highly technical products, the SE often determines whether the deal moves past proof of concept. Hiring an AE without a paired SE in this environment is asking the rep to perform a job they were never designed to do.

Enterprise AE vs Mid-Market AE vs PLG Sales Assist vs Solution Engineer

These are not seniority levels. They are different roles with different skill requirements, different incentive structures, and different failure modes.

Enterprise AE

The enterprise AE's primary skill is political navigation. They need to build a champion who will advocate internally when the AE is not in the room. They need to manage security reviews without losing momentum. They need to keep a deal alive through two or three "go back and confirm the budget" moments that would kill a mid-market cycle. The signal in an interview is how they talk about deals that stalled. Enterprise AEs know exactly why deals died and what they would do differently. Mid-market AEs often attribute losses to price or competition because their cycles are short enough that they never identified the real internal dynamics.

Mid-Market AE

Mid-market AEs win on velocity and clarity. They compress cycles by asking better discovery questions early, qualifying out faster, and running tight POCs when they need to. Their failure mode in an enterprise role is that they optimize for speed in a motion that requires patience. They call for the close too early. They escalate too aggressively. They cannot sustain 8-month deal cycles without losing confidence that the deal is real.

PLG Sales Assist

The PLG assist is hired to convert product-qualified leads, not to prospect. Their inbound funnel is the product itself. Users who hit certain usage thresholds, activate key features, or invite multiple team members are handed to the assist rep for a conversation about upgrading or expanding. The rep who succeeds here is consultative, not pushy. They know the product deeply enough to help users realize value they have not yet found. The failure mode is hiring a quota-hungry outbound AE in this role. They start cold-calling free users, creating friction in a motion that was working through patience and product-led nudges.

Solution Engineer

SEs own the technical proof. When the buying decision turns on whether the product can integrate with the existing stack, survive a security audit, or handle a specific edge case in the customer's data model, the SE is the person who answers those questions credibly. Solution consultants, by contrast, own the value proof. They are deployed when the question is not "can this technically work" but "what will the business outcome be." The hiring brief for an SE screens for depth and precision. The brief for a solution consultant screens for business acumen and communication. These are different candidates and confusing them produces expensive mis-hires.

The Mismatch Pattern

PLG founders hire enterprise reps because the deal size in the enterprise looks attractive compared to the $50/month self-serve user. The reasoning is visible in every board conversation: "If we just move upmarket, one enterprise deal is worth 500 self-serve accounts." That math is correct. The hiring conclusion is not.

The PLG product closes in days or weeks because the value is demonstrable, the implementation is simple, and the user and buyer are often the same person. An enterprise AE dropped into this environment starts doing what they were trained to do: slow the process down, add stakeholders, build consensus, negotiate terms. Every one of those behaviors creates friction in a product that was closing on its own. The deals that were closing in 14 days now take 60, and the rep claims credit for "sophisticated selling." Quota attainment looks fine for two quarters because they are closing some deals. Then the pipeline breaks because the rep has been manufacturing enterprise-style complexity in deals that did not require it, and the buyers who wanted to move fast went to a competitor who let them.

The reverse mismatch is less common but equally destructive. A PLG-native rep hired into an enterprise role will run a 30-day trial and expect a decision. When the CIO says "we need to bring in IT and run this through our vendor assessment process," the PLG rep has no playbook. They follow up too aggressively, fail to identify the internal champion, and the deal dies from neglect of a buying process the rep did not know how to navigate.

What the Discovery Call Looks Like When the Rep Type Is Wrong

You can identify a motion mismatch in one discovery call. The signals are specific.

Enterprise Rep in a PLG Product

The rep asks for a 60-minute discovery before offering a trial. They want to understand the full organizational context, the existing vendor landscape, the budget cycle, and the decision-making structure. The buyer, who wanted to sign up and try the product that afternoon, either drops off or sits through the call and signs up for the free tier the moment it ends. The rep logs the call as "active opportunity" and schedules a follow-up. The buyer is already three features deep into the product and will either convert without the rep or churn because nobody helped them activate. Either way, the rep did not cause the outcome.

PLG Rep in an Enterprise Product

The rep offers a trial immediately without scoping whether the buyer's environment can support one. The enterprise buyer's IT team blocks the integration at the network level because no one ran it through the security review process. The rep interprets the IT friction as a buying objection and starts discounting. The real problem is that the product requires a structured POC with IT involvement, and the rep did not know to propose one. The deal dies not because the product was wrong but because the selling motion was wrong for the product's technical requirements.

Mid-Market AE in an Enterprise Role

They identify one champion and build the entire deal around that person. When the champion goes on parental leave in month four, the deal goes cold because no one built a second thread into IT or finance. The rep reports the deal as "on hold" and moves on. An enterprise-trained AE would have been building the IT relationship since month two precisely because they know champions disappear.

The DNA-Driven Job Description

Most job descriptions for sales roles are lists of responsibilities and quota expectations. They describe what the rep will do, not the selling environment they will operate in. A DNA-driven brief specifies the motion before the responsibilities.

The opening section of a DNA-driven brief answers four questions. First, what does the buying committee look like? How many stakeholders, what functions, what level of executive involvement? Second, what does the sales cycle look like? Length, key milestones, average number of calls before close? Third, what is the rep expected to own versus what is supported by pre-sales or CS? Fourth, what does a lost deal usually look like in this environment?

The skills section then follows directly from those answers. For an enterprise AE brief, the required skills include multi-threaded account management, executive communication, POC scoping, and security review navigation. For a mid-market AE, the required skills include full-cycle ownership, light technical qualification, and business case construction without pre-sales support. For a PLG assist, the required skills include product fluency, usage data interpretation, and expansion conversation without creating pressure on the existing relationship.

The experience section stops screening for logos and starts screening for contexts. "Sold into companies with 1,000-5,000 employees where IT had vendor approval authority" is more useful than "sold enterprise software." "Closed deals from product-qualified leads in a usage-based pricing model" is more useful than "experience in PLG." The context tells you whether the candidate's wins came from the same selling environment your product requires.