30-60-90 Day AE Ramp Plan

A 30-60-90 day plan can organise an account executive's first three months. It cannot prove that the person will reach full productivity within 90 days or that the framework shortens ramp time.

That distinction matters. The Bridge Group's 2026 AE study reports an average 6.2-month ramp to full productivity across 158 B2B companies surveyed in the first half of 2026. Its anonymous, aggregate, observational data does not test this plan or represent every segment and role.

Use the framework below as a SalesTap planning method. Replace every example milestone with evidence your own AE role can reasonably produce.

A 90-day plan is not a 90-day ramp claim

The first three months test whether the AE can learn, execute with supervision, and increasingly own the workflow. Revenue may lag when the sales cycle exceeds the review period. Define full productivity before the person starts: a full quota period, pipeline contribution, independent execution, or an agreed combination. Keep that definition fixed.

Separate leading evidence from lagging outcomes:

• Leading evidence: buyer knowledge, process simulations, discovery quality, CRM accuracy, next steps, and manager-assessed execution.
• Lagging outcomes: first qualified opportunity, first closed-won deal, ramp-quota attainment, and first full-productivity period.

They answer different questions. Correct execution can precede long-cycle revenue, while a quick inherited deal may not demonstrate repeatability.

Before day 1: set the role-specific baseline

Build the plan from the job the AE is entering. Record the territory, sales-cycle definition, pipeline source, deal ownership, product scope, systems, and manager capacity.

Inspect a recent cohort in the same role and segment and record when each person reached the proposed milestones. Keep a small historical sample as internal context, not an industry benchmark. Our B2B sales benchmarks guide explains the separation.

Prepare the conditions the plan assumes:

• timely system, data, product, and content access, with named owners;
• approved examples of discovery, demos, proposals, and deal reviews;
• a territory and lead-flow plan consistent with the ramp expectations;
• a feedback cadence plus written milestone definitions and sign-off owners.

If these inputs are missing, the scorecard should record an organisational dependency rather than silently marking the AE behind.

Days 1-30: learn and demonstrate

The first phase should test comprehension through work products, not attendance. Explaining a buyer problem and applying it in a simulation provides stronger evidence than module completion alone.

A practical Month 1 could include:

• debriefing approved calls to identify the buyer's stated problem, evidence, stakeholders, and next step;
• connecting approved capabilities to supportable customer outcomes without inventing proof;
• completing a CRM simulation covering stages, required fields, activity capture, ownership, and handoffs;
• practising discovery, demo, and follow-up in role-specific scenarios;
• completing required security, privacy, recording, and contact-policy training.

Set the volume of calls and practice from available coaching capacity; no source checked establishes a universal optimum. For recordings, follow the organisation's access controls and applicable consent or notification rules.

At the checkpoint, record what passed, what needs another attempt, and which company inputs remain missing.

Days 31-60: execute with supervision

The second phase moves into controlled execution with an agreed review boundary. A complex-enterprise AE may co-run discovery; a transactional AE may own more of the cycle sooner.

Use a consistent rubric. For discovery, cover the stated problem, impact evidence, decision participants, next action, and CRM write-back. For a demo, score alignment with verified needs rather than feature coverage.

Pick a sustainable coaching cadence. A weekly deal review and a small number of call reviews are examples, not proven frequencies. End each session with one behaviour to retain, one to change, and one later interaction where the change will be checked.

A first qualified opportunity or independently run discovery can work when lead flow permits. Do not mandate a closed deal by an arbitrary day; deal source, inherited pipeline, cycle length, and buyer timing can distort it.

Days 61-90: own the workflow

The third phase tests increasing independence. The AE should prepare and run the relevant interaction, update the system of record, explain the evidence behind the stage, and propose the next action without the manager reconstructing the deal.

For an account-based role, add a manageable set of account plans with known stakeholders, evidence gaps, business hypotheses, and next actions. The account-based selling playbook provides a testable mapping approach. Do not impose a universal account count or stakeholder threshold.

Set ramp quota from internal opportunity-creation and sales-cycle data. If deals take longer than the AE has been in seat, Month 3 bookings are incomplete evidence. Review pipeline quality, progression, and execution too. Any reduced quota percentage is a company decision, not this article's benchmark.

At Day 90, record what the AE can own, what still needs supervision, missing inputs, and the next test. No single exercise proves the ramp succeeded.

Use a bilateral scorecard

The scorecard should hold the company and the AE accountable. A simple version looks like this:

| Checkpoint | AE evidence | Manager obligation | If evidence is missing | | --- | --- | --- | --- | | Days 1-30 | Buyer, product, process, CRM, and policy demonstrations | Access, examples, instruction, rubric, and timely feedback | Separate skill gaps from missing inputs; assign a new evidence date | | Days 31-60 | Supervised calls, opportunity evidence, accurate records, and applied coaching | Representative work, observation, coaching, and clear sign-off | Narrow the gap to a specific behaviour or dependency; retest it | | Days 61-90 | Increasingly independent execution, account or territory planning, and defensible deal reviews | Appropriate pipeline opportunity, governance, and calibrated ramp expectations | Extend supervision or revise the input plan; do not rewrite the standard after seeing the result | | After Day 90 | Progress towards the predeclared full-productivity definition | Continued coaching and an explicit transition to normal expectations | Keep the ramp open and record why; 90 days is a checkpoint, not an automatic pass |

The AE and manager should acknowledge the milestones, evidence, dependencies, and review dates before performance is judged against them.

Measure ramp without flattering the plan

Track first qualified opportunity, independent core workflow, closed-won deal, ramp-quota attainment, and full productivity separately. Define the start and end events for every duration.

Compare like roles and segments. Keep inherited opportunities separate from AE-created pipeline, and keep people still ramping visible rather than dropping them from the cohort. Reporting only completed ramps removes unresolved observations and can make the programme appear faster than the full cohort warrants.

If ramp improves after this plan is introduced, call it an observed internal change, not proof of causation. Hiring, territory, product, enablement, lead flow, manager capacity, or the market may also have changed. Our sales-tech quota audit applies the same reasoning to tools.

The takeaway

A useful 30-60-90 plan sets role-specific evidence, names the support the company owes, and makes the Day 90 decision explicit. Define full productivity before day one, judge leading and lagging measures separately, and keep the plan open when the evidence says the AE is still ramping. The calendar supplies review points; your operating data supplies the standard.

Source check: The Bridge Group's 2026 AE study was checked on 9 August 2026 for its sample, fieldwork period, average ramp figure, methodology, and limitations. The phases, scorecard, milestone examples, and measurement method are SalesTap editorial guidance, not validated performance thresholds.