How to Become a Project Manager When You're Coming From Sales
Quota work already taught you forecasting, stakeholder wrangling and delivering bad news early — here is how to repackage that for a delivery role.
By Desmond Okafor-Hale · Oct 26, 2026 · 12 min read

Moving from sales into project management is one of the shorter career switches available, because an account executive or sales manager already runs a pipeline, a forecast, a cross-functional deal team and a close plan — which is a project schedule with a different name. Most people make the move in 9 to 18 months by running real projects inside their current sales organisation, picking up one credential, and applying to roles that sit close to revenue: customer onboarding, implementation, professional services or sales operations.
The gap you have to close is artefacts and vocabulary: charters, RAID logs, change control and status reporting. The gap you do not have to close is talking to senior people about slipping dates.
Your Skills, Translated
Sales work produces evidence of project management; it just files it under different names. Use bracketed placeholders below with your own numbers from your CRM reports — do not guess them.
| Old-career skill (sales) | New-career equivalent | How to frame it on a resume |
|---|---|---|
| Running weekly pipeline reviews in Salesforce or HubSpot | Status reporting and portfolio tracking | "Reported weekly on [X] concurrent opportunities by stage, owner and close date to a VP audience; flagged slipped dates before the review, not in it." |
| Building a mutual action plan or close plan with a buyer | Project schedule, milestone plan and RACI | "Built and maintained joint milestone plans with customer stakeholders covering security review, legal, procurement and go-live dates." |
| Quota forecasting and commit/best-case calls | Schedule and scope forecasting, confidence ranges | "Produced monthly forecasts with commit and upside ranges; held [X]% forecast accuracy across [X] quarters." |
| Discovery calls that uncover a buyer's real problem | Requirements elicitation and stakeholder interviews | "Ran structured discovery with [X] stakeholders per account to document current-state process, success criteria and constraints." |
| Coordinating a solutions engineer, legal, finance and a channel partner on one deal | Cross-functional coordination without direct authority | "Directed deal teams of 4-6 specialists across presales, legal and finance with no reporting line; owned the critical path to signature." |
| Negotiating redlines, SLAs and payment terms with procurement | Contract and vendor management | "Negotiated commercial terms, SLAs and delivery schedules with procurement teams; coordinated legal review cycles to agreed dates." |
| Escalating a slipping deal and rebuilding the plan | Risk and issue management, RAID log, change control | "Identified delivery and approval risks early, escalated with options rather than status, and re-baselined timelines with the customer." |
| Handing a closed account to customer success or onboarding | Project handover, transition plan and closeout | "Owned handover packs covering scope, commitments, open risks and success metrics; ran joint kickoff calls with the delivery team." |
| Preparing and presenting a QBR to a customer executive | Steering committee and executive status reporting | "Presented quarterly business reviews to C-level customer sponsors covering progress against agreed outcomes, risks and next-quarter plan." |
| Territory planning and account prioritisation | Resource allocation and portfolio prioritisation | "Prioritised [X] accounts against capacity and effort each quarter; defended the sequencing to sales leadership." |
Two honest gaps compared with a PM who came up through engineering or operations: you have probably never run change control on a fixed-scope statement of work, and you have probably never managed a budget you did not personally generate. Say so in interviews and say what you are doing about it.
Realistic Transition Timeline
This assumes you keep working full time in your sales role and give the switch 5 to 8 hours a week.
Months 1-2 — inventory and vocabulary - Write a one-page project inventory: every deal, launch, territory migration or CRM rollout you ran, with dates, headcount involved and the outcome. - Read one methodology guide end to end (PMI's process groups, or the Scrum Guide, which takes about an hour). - Set up a free Jira or Asana account and rebuild your current quarter's account plan as a board with epics, tasks, owners and due dates.
Months 2-4 — first documented project - Volunteer to own one internal project in your own sales org: a territory redesign, a CRM field cleanup, a new onboarding playbook, a sales kickoff event. - Deliverables you must produce, because interviewers ask for them: a one-page charter with scope and success criteria, a RACI, a weekly status email, a risk log, a closeout summary. - Budget 8 to 12 weeks and roughly 3 hours a week on top of quota work.
Months 4-7 — credential and second project - Log your training contact hours as you go; PMI counts them and the number required is published in its current handbook. - Book an exam date before you feel ready — most people study 60 to 100 hours over 8 to 12 weeks and finish only when the date forces it. - Start a second project with a different shape: if the first was process, make the second a system or a vendor.
Months 6-9 — market yourself - Rewrite the resume around delivery language, not attainment language. - Hold 10 to 15 conversations with working PMs, 20 to 30 minutes each, concentrated in implementation and professional services teams. - Start applying at 5 to 8 roles a week.
Months 9-15 — interviews and offer - Expect 3 to 5 rounds per employer and 4 to 8 weeks per process; a case or scenario exercise is common at the third round. - Typical gap between first application and signed offer for a career switcher: 45 to 90 days of active applying, longer if you only want fully remote roles.
Months 15-24 — first seat - Deliver 2 to 3 projects end to end, then ask to be put on something with a budget line and a vendor, which is what gets you to senior PM or program manager.
Step-by-Step: Making the Switch
- Audit 12 months of your own sales work for project-shaped evidence. Pull your CRM reports and calendar, and list anything you coordinated that had a start date, an end date and more than three people. Cost: free. Time: 4 to 6 hours over one weekend.
- Learn one methodology properly rather than three badly. Pick either predictive (PMI-style phases, charters, change control) or agile (scrum events, backlog, sprint reviews) based on the job ads in your city. Cost: a self-paced subscription course or a library copy of a standard text — check current prices directly with the provider. Time: 20 to 30 hours across four weeks.
- Run a real internal project and write the artefacts for it. Ask your sales director for a project nobody wants: the CRM hygiene push, the new territory map, the partner onboarding process. Cost: free, plus about 3 hours a week of your own time. Time: 8 to 12 weeks.
- Get hands-on with one project tool and one documentation tool. Jira or Asana for the work, Confluence, Notion or SharePoint for the documents; Smartsheet and Microsoft Project show up often in construction, government and professional services job ads. Cost: free tiers cover a solo learner. Time: 10 hours to get genuinely fluent, not 10 minutes of clicking.
- Choose a credential and book the exam date. CAPM suits people without logged project-leadership months; CSM or PSM I suits agile-leaning employers; PRINCE2 is asked for far more often in the UK, Ireland and Australia than in the US. Fees are set by PMI, Scrum Alliance, Scrum.org and Axelos and change, so price them on the certifying body's own site, and ask whether your employer's learning budget covers exam fees. Time: 60 to 100 study hours over 8 to 12 weeks.
- Rewrite your resume into delivery language and build two versions. Version one for implementation, onboarding and professional services PM roles; version two for internal operations or PMO roles. Lead with scope, stakeholders, timeline and outcome — not attainment percentage. Cost: free. Time: 6 to 8 hours, plus a second pass after feedback from a working PM.
- Hold 10 to 15 informational conversations with PMs. Ask what their last project slipped on and what their weekly reporting cycle looks like, then use those exact words in your applications. Cost: free, or the price of coffee. Time: 20 to 30 minutes each, roughly 5 to 7 hours total over three weeks.
- Apply first to roles that touch customers. Implementation manager, onboarding manager, professional services PM, sales operations project manager and customer program manager all credit the client-facing hours you logged as an account executive. Cost: free. Time: 5 to 8 applications a week for 6 to 12 weeks.
- Prepare the compensation conversation before the offer stage. Ask at round one how the role is paid — base only, base plus annual bonus, or base plus a delivery-margin bonus — and look up current ranges for your metro in the Bureau of Labor Statistics OES tables and employer-reported sites. Cost: free. Time: 2 to 3 hours of research, 1 to 2 weeks of back-and-forth once an offer lands.
Before You Quit Your Current Job
Sales income is lumpy, which makes the runway maths different from a salaried switch. Work through these before you resign.
- You have 6 months of core expenses in cash, not 3. Three months is the usual advice for salaried switchers; commission earners should hold six, because your final months of variable pay are the ones most likely to be disputed or delayed.
- You know the exact date your last commission payment clears and whether it can be clawed back. Read your comp plan for the clause on deals that churn or cancel within 90 or 180 days of signature, and for whether payment requires you to be employed on the payout date.
- You have had a lawyer read any non-compete, non-solicit or customer-list clause. Budget one paid consultation; enforceability varies substantially by state, and a move into delivery at a competitor is treated differently from a move into sales there.
- You have at least two completed projects you can describe in 90 seconds each, with a charter, a status report and a closeout document you can show on request, with client names redacted.
- You have checked what happens to health coverage on your last day — whether coverage ends that day or at month end, and what the continuation and marketplace enrolment windows are. Confirm dates in writing with HR rather than relying on a colleague's version.
- You have a written offer with the start date, base, bonus mechanism and review cycle on it. Do not resign on a verbal offer, and do not resign before a background check clears, which typically takes 3 to 10 business days.
- You have modelled 12 months at the new base, not your on-target earnings. Compare base to base, list every expense tied to the sales job you will drop (commuting, client dinners you funded, wardrobe) and every one you will add (childcare if hours shift, certification renewal every 2 to 3 years).
- You have confirmed whether an internal move is possible first. Many employers' internal mobility policies require 12 months in your current role and a manager conversation before you can apply; an internal transfer keeps tenure, benefits accrual and your 401(k) vesting schedule intact.
Frequently asked questions
Will I take a pay cut moving from sales to project management?
Often yes in the first year, and the structure changes as much as the number. Sales pay is usually split into base plus variable commission with accelerators, while most project management roles are paid as a full salary plus an annual bonus tied to company or delivery performance, sometimes with a utilisation or margin component in consulting firms. That means your monthly income stops swinging, and your upside in a big quarter disappears. Compare your trailing 12-month W-2 against the offered base rather than comparing on-target earnings to base, and look up current ranges for your metro area in the Bureau of Labor Statistics Occupational Employment and Wage Statistics tables, which are published annually and broken out by state and metro.
Do I need the PMP before anyone will hire me?
Not usually for a first project management role, and in many cases you cannot get it yet. PMI's PMP requires documented months of leading projects, which most account executives have not formally logged, so the practical order is CAPM or a scrum credential first and the PMP after 2 to 3 years of delivery work. One detail worth knowing before you choose: scrum credentials differ on renewal — Scrum Alliance's CSM requires renewal on a fixed cycle with education units and a renewal fee, while Scrum.org's PSM I does not expire. Check both bodies' current rules, since they revise them.
I'm in my forties with 15 years in sales. Is that too late?
No, but it changes which jobs you target. Employers hiring an entry-level coordinator at 25 and an implementation manager at 45 are buying different things: the second one is buying the fact that you have handled an angry executive sponsor before. Apply to mid-level delivery roles in implementation, professional services and customer programs rather than PMO coordinator roles, where you will be screened out as overqualified. On the resume, cover the last 10 to 12 years in detail and compress anything older into a single line, and put your most recent two projects above your sales attainment history.
Should I move internally at my current employer or apply outside?
Internal first, if your company has a delivery, onboarding or professional services team — because the hiring manager can verify the internal project you ran, which an external recruiter cannot. Internal switchers also usually keep accrued tenure, benefits eligibility and their 401(k) vesting schedule, which an external move resets. The trade-off is pay: internal transfers are often made at a standard band adjustment rather than a negotiated external offer, so run the base-to-base comparison before you accept, and ask whether the move is treated as a lateral or a level change.

Written by
Desmond Okafor-Hale
Desmond writes about the mechanics of hiring: the forms, the filters, the strange rituals that decide who gets a callback. He's fascinated by the gap between what job postings say and what they mean.



