Enterprise sales has operated on roughly the same timeline for 30 years. Educate the market. Run a pilot. Prove the business case. Navigate security review. Negotiate the contract. The cycle stretched over months because software implementations required months of configuration, training, and change management before value was visible.
Andreessen Horowitz’s analysis of AI sales velocity identifies a fundamental break from this model. The title of their piece is direct: “AI Doesn’t Just Change What You Sell. It Also Changes How You Sell It.” And the central argument is not that AI makes sales faster — it is that AI products are evaluated and purchased at a speed that the traditional enterprise sales motion was not designed to handle, and the teams that have not adapted are losing deals to teams that have.
Here is what speed means in this context, why it changes the commercial model, and what GTM teams selling any B2B product can do with the insight.
The Traditional Enterprise Sales Timeline and Why It Existed
The multi-month enterprise sales cycle was not arbitrary. It emerged from the actual complexity of enterprise software adoption. Implementation required IT involvement. Training required time. Configuration required professional services engagement. The buyer needed to see a detailed ROI model because the cost of a wrong decision — measured in failed implementations, wasted consulting spend, and organizational disruption — was high.
The POC existed as a risk mitigation tool. Three months of limited deployment allowed the buyer to validate assumptions before committing to full rollout. The multi-stakeholder review existed because implementation touched enough functions that buy-in from multiple teams was genuinely necessary for success.
For traditional software, this timeline made sense. For AI products, it is increasingly a structural mismatch.
AI products — particularly the API-first and developer-facing AI tools that are defining the category — reach full operational value in hours or days, not months. An engineering team that integrates an AI coding assistant is seeing productivity impact the same week. A sales team using an AI research tool is generating better-briefed calls within days. There is no 90-day implementation runway before value is visible because there is no 90-day implementation at all.
The problem, according to a16z’s analysis, is that enterprise sales teams are still using the 90-day POC as their default evaluation structure even when the value evidence is available in 90 minutes.
The Three Ways AI Speed Rewrites Enterprise Sales
1. Evaluation Cycles Compress — But Only If the Seller Compresses Them
The a16z analysis identifies the first shift: buyers of AI products are now capable of completing meaningful evaluations in dramatically shorter timeframes than traditional software evaluations require. An engineering team can spin up a test environment, run real workloads through an AI API, and generate substantive performance data in an afternoon. A revenue team can test an AI research or personalization tool on a live campaign within a week.
The sellers who are winning are the ones who have redesigned their commercial process to match this compressed evaluation timeline. They are not offering 90-day POCs as the default. They are offering structured, outcome-defined evaluations that are designed to surface clear value evidence within two to four weeks — sometimes within a single session.
The sellers who are losing are the ones running AI products through enterprise sales processes designed for traditional software: multi-meeting discovery sequences, lengthy proposal cycles, and three-month pilots that the buyer never needed and finds frustrating to navigate.
For outbound teams, the implication is sequencing and messaging. The sequence designed to move an enterprise prospect from awareness to discovery call to proposal over eight weeks is the wrong structure for a product that can demonstrate clear value in a single session. The sequence should be designed to get a prospect into a hands-on evaluation as quickly as possible — which means the outreach has to be specific enough that a prospect can make a fast decision about whether the evaluation is worth their time.
2. The Sales Conversation Starts Later in the Buyer’s Journey
When evaluations compress and product value is visible quickly, buyers complete more of their evaluation before they engage with a sales team. They have tested the API. They have read the documentation. They have run their own benchmark. By the time a prospect agrees to a sales conversation, they are not in early-stage discovery — they are in late-stage qualification.
This changes what the first sales conversation should accomplish. Traditional discovery — “tell me about your current process, what challenges are you facing, what are you hoping to achieve” — assumes a buyer who has not yet articulated their requirements. The AI-era enterprise buyer has already articulated their requirements. They have already run the test that answers the basic performance questions. They want to know: can this product meet our security requirements? Can it scale to our volume? What does the enterprise contract include that the API tier does not?
The sellers who are winning have redesigned their discovery motion to acknowledge this reality. They open with what they know about the buyer’s evaluation context — which signals they have observed, which usage patterns they have identified, which features the buyer’s team has already engaged with — and they move immediately to the commercial questions that the buyer is actually ready to discuss.
This is precisely the challenge that made the Cursor and Anthropic GTM model so effective: they designed their sales engagement to start from where the buyer already was, not from the beginning of a journey that the buyer had already completed independently.
3. Speed Creates a New Security and Trust Requirement
Here is where the a16z analysis gets counterintuitive. Faster evaluation timelines do not mean abbreviated security and procurement review. Enterprise buyers who can validate product value in days still need weeks or months to complete security assessments, legal review, and procurement processes.
The implication is that the value proof and the security/compliance review need to run in parallel, not sequentially. In the traditional model, POC success triggered the start of security review. In the compressed model, security review should begin as soon as there is a genuine purchase intent signal — which is detectable much earlier in the process than it used to be.
For GTM teams, this means building the security and procurement readiness materials — SOC 2 reports, security questionnaire templates, standard DPA language, procurement process guides — into the sales toolkit as early-stage resources rather than final-stage deliverables. The buyer who is six days into a successful evaluation and ready to make a purchase decision should not spend another 90 days waiting for security review documents that could have been provided on day one.
The sellers who have pre-built this infrastructure are reducing their sales cycles not by compressing the evaluation — which the buyer controls — but by removing the procedural delays that slow the process after the buyer has already decided they want to buy.
The Operational Playbook for Faster Enterprise Sales
The a16z framework has specific operational implications for how GTM teams should structure their outbound, their sequencing, and their commercial conversations.
Identify Evaluation-Ready Signals, Not Just Awareness Signals
Standard outbound targeting is built around ICP fit — does this company match the profile of an ideal customer? The compressed AI sales cycle adds a second filter: is this account in an active evaluation window right now?
Evaluation-ready signals include: API usage that has increased significantly in the past 30 days, team expansion in technical functions where your product is relevant, a recently completed security onboarding with a related product in your category, or direct competitor comparisons visible through review site activity. These signals indicate that the account is not just a good fit — it is in an active buying window where a well-timed outbound sequence will find a receptive audience.
The signal-led outbound infrastructure that routes these signals into sequences automatically is the same architecture that drives standard intent-based outbound — it just has to be calibrated for AI product evaluation signals rather than generic intent categories. For the full technical architecture, see the Signal-Led Outbound Playbook.
Compress the Time to First Value Contact
The first sequence touchpoint for an evaluation-ready account should not be a standard awareness email. It should be a direct invitation to the fastest path to value evidence — whether that is a structured 30-minute session with a specific outcome, a sandbox environment pre-loaded with their use case, or a side-by-side performance comparison against their current tooling.
The language matters: “I would like to introduce you to our platform” is designed for a buyer at the beginning of their journey. “Your team has been evaluating AI solutions for code review — here is the most efficient path to seeing whether ours solves the specific problem” is designed for a buyer who is already in evaluation mode and has no patience for awareness content.
Design Sequences Around the Commercial Handoff, Not the Discovery Conversation
In a compressed evaluation timeline, the sequence architecture should be built backward from the commercial conversation, not forward from awareness. The sequence is successful when it produces a prospect who has completed a meaningful evaluation, has a clear view of the value case, and is ready to discuss commercial terms. That is a very different goal than generating a discovery call.
Sequence structure for evaluation-ready accounts:
- Day 1: Specific, signal-based first email identifying the evaluation context and offering the fastest path to value evidence
- Day 3: Technical resource relevant to the specific use case their evaluation has focused on (not a product overview deck)
- Day 5: LinkedIn touchpoint referencing a specific technical post or contribution from their team
- Day 8: Follow-up addressing the most common objection at this evaluation stage for their company profile
- Day 14: Commercial framing — what enterprise includes versus the tier they are currently using
This sequence is built for a buyer who already understands the product. A buyer at the beginning of their journey needs different content at every touchpoint. Mixing the two populations into a single sequence design is how sequences fail with high-intent accounts while continuing to run on autopilot.
Pre-Build the Trust Infrastructure for Speed
The security review, DPA templates, and compliance documentation that enterprise buyers need to close a deal should be prepared in advance and delivered proactively — not requested and then assembled under deadline pressure. Pre-building this infrastructure is a RevOps function that directly affects commercial velocity: the faster a buyer can complete their internal procurement requirements, the faster the deal closes after they have decided to buy.
For GTM teams using CRM enrichment tools to track account status, the signal that an account has entered serious evaluation mode should trigger automatic delivery of the security and procurement package — not wait for the buyer to request it. See What Is CRM Enrichment for how the enrichment infrastructure that supports this kind of trigger-based delivery works.
What the a16z Analysis Means for Non-AI Products
The speed argument a16z is making is not limited to AI products. It is a directional analysis of where enterprise buying behavior is heading — toward faster evaluation, later sales engagement, and parallel processing of value proof and procurement compliance — that applies to any B2B product where:
- Value is demonstrable quickly (within days rather than months)
- Buyers have access to enough self-service information to complete meaningful pre-sales research
- The technical complexity of implementation does not require extended professional services engagement
For most modern B2B SaaS products, at least two of these three conditions are true. The enterprise sales motion that was designed in 2010 for complex on-premise software is an increasingly poor fit for the products and buyers of 2026. The teams that have not updated their commercial process are carrying a structural disadvantage into every enterprise deal.
The Revenue Outcome of Getting Speed Right
The commercial math behind the speed thesis is straightforward. If a typical enterprise deal currently closes in 120 days, and operational changes reduce that cycle to 60 days, two things happen: first, you close twice as many deals in the same period with the same headcount. Second, the pipeline that was stuck waiting for security review, POC completion, or multi-meeting approval processes converts at a higher rate because fewer deals stall and lose momentum.
The a16z framework does not promise that all enterprise deals can close in 30 days. It identifies the specific friction points — evaluation timeline mismatch, security review sequencing, discovery conversation calibration — where deliberate process design creates measurable acceleration. Each friction point removed is a compounding improvement to commercial velocity.
For GTM teams, the entry point is usually the easiest friction point to address: getting the first value touchpoint earlier. Not a discovery call. A structured, outcome-defined session that puts the product in front of the prospect’s actual use case within the first week of engagement. That single change, implemented consistently, improves pipeline velocity in every deal it touches.
Frequently Asked Questions
Does the a16z speed thesis mean traditional enterprise sales is over?
No. It means the traditional enterprise sales timeline is being compressed at the evaluation stage, not eliminated. Security review, legal negotiation, and procurement compliance still take the time they take. The acceleration happens at the front of the process — getting from first outbound contact to a serious commercial conversation faster — which translates into shorter overall deal cycles even when the back-end procurement process remains unchanged.
How do you identify when an account is evaluation-ready versus just ICP-fit?
Evaluation-ready signals include: significant increase in API or product usage in the past 30 days, expansion of technical headcount in relevant functions, active competitor comparison activity visible through review platforms, or direct signals like security assessment initiation or procurement team involvement. These signals indicate buying intent, not just profile fit.
What is the right sequence length for a compressed AI sales cycle?
Shorter than standard outbound — typically 5–7 touchpoints over 14–21 days rather than the 30–45 day standard sequences. The compressed timeline means high-intent accounts make faster decisions, and a sequence that runs for 30 days is designed for a buyer who is still researching — not for one who is ready to evaluate now. For accounts that do not convert in the compressed window, longer nurture sequences at lower frequency continue to develop the relationship until evaluation readiness reappears.
How should GTM teams change their discovery call structure for AI-era buyers?
Start from what you already know. Open with the specific usage data, evaluation signals, or technical context you have observed — not with generic questions about their challenges. Move immediately to the commercial and technical questions the buyer is actually ready to discuss: enterprise plan features, security requirements, volume pricing, implementation scope. Reserve “what are you trying to accomplish” for accounts where you genuinely have no signal data — not as the default opening for every conversation.
