Sales Portfolio & 'Why Me' Pitch
Builds on Topic 10.
What you'll produce
A one-page sales portfolio that links your five GearGrid artifacts into one coherent deal story — cold prospect to forecasted close — plus a 60-second written "why tech sales, why me" pitch that reframes your background around the four traits SDRs are hired for (drive, communication, resilience, results) with quantified bullets. This is the single document you put at the top of your resume, paste into a LinkedIn "Featured" slot, and walk a hiring manager through in an interview. It matters because entry-level sales loops hire on traits and evidence, not credentials (Topic 10): the portfolio is proof you can already do the job, and the pitch is the 60-second close that gets you the next round. Done well, it turns six exercises into a work-sample that says "I ran a real deal" — which beats "I took a course" every time.
Instructions
- Gather your five artifacts first. Open Deliverables 1–5 (ICP & prospect list, outreach sequence, discovery plan & BANT notes, demo & objection playbook, pipeline & forecast). You are not redoing them — you are summarizing the one-line outcome of each and the thread that connects them.
- Write a one-sentence deal headline at the top: account, product, deal size, current stage, and forecast. This is the "elevator version" a manager reads in three seconds (e.g., "Worked GearGrid from cold to a committed $31.7k ARR deal forecasted to close this quarter").
- Build the deal-story table — one row per deliverable. Each row has the artifact name, the one concrete outcome it produced, and the trigger/pain thread carried forward (the "why now" you found in D1 should still be visible in D5). Use real numbers from your own artifacts, never "[trigger]" or "TBD."
- Write a 3–4 sentence "the thread" paragraph that narrates the deal as one motion: who you targeted and why now → how you booked the meeting → what pain discovery quantified → which outcomes the demo sold → where the deal sits and what closes it. This is what you'll say out loud when walking through the portfolio.
- Pull 3 portfolio proof-points — the three hardest numbers across all five artifacts (quantified pain, ARR, win-probability, activity math). These are the stats you lead with under pressure.
- Draft the "why me" pitch as ~150 words / 60 seconds spoken. Structure: (a) one line of genuine why tech sales / why this company, (b) 3 quantified reframe bullets mapping your real background to drive, communication, resilience, results, (c) one line tying it to the SDR role, (d) a confident ask for the next step (treat the pitch like a sales call — close it).
- Reframe, don't fabricate. Translate real past achievements into sales language ("ranked #2 of 14 servers on upsell," "rebuilt a route after a 40% no-show month"). Every bullet must have a number and map to a named trait.
- Read the pitch aloud and time it. If it runs over ~60 seconds, cut adjectives, not numbers. End on the ask, not on "thank you."
- Sanity-check the thread. The trigger in row 1, the pain in row 3, and the ARR in row 5 must be the same deal — a grader (and a hiring manager) will check that the story is coherent, not six disconnected files.
Worked example
(Portfolio for the GearGrid deal — Lumadesk SDR, mid-market e-commerce territory)
Sales Portfolio — [Your Name] · Aspiring SDR Deal headline: Worked GearGrid (220-person DTC outdoor-gear retailer) from a cold prospect to a committed $31.7k ARR Lumadesk deal — discovery-qualified with champion Maya Chen (Head of Customer Support), demoed to outcomes, multi-threaded up to economic buyer Devon Apraku (VP of Operations), and in redlines at Commit / 80% to close this quarter.
The deal story — five artifacts, one motion:
| # | Artifact | Outcome it produced | Thread carried forward |
|---|---|---|---|
| 1 | ICP & Prospect List | Defined ICP (e-comm, 50–500 employees, support team scaling) and a list of 10 accounts; named GearGrid's champion Maya Chen, Head of Customer Support, economic buyer Devon Apraku, VP of Operations. | Why now: order volume doubled, hiring 3 agents, Trustpilot reviews cite slow replies. |
| 2 | Outreach Sequence | 6-touch sequence led with the Trustpilot/response-time pain; touch 4 (cold-call opener) booked the meeting off a referenced 1-star review. | Same response-time trigger → became the hook that earned the call. |
| 3 | Discovery & BANT | Quantified pain: ~3,000 tickets/mo, 14-hr first-response time, ~$78k/yr in the 3 planned hires; BANT qualify-in, champion = Maya Chen, economic buyer = Devon Apraku (not yet engaged — the one open gap). | Slow replies (from outreach) → measured in hours and headcount dollars; committed next step = get Devon in the demo. |
| 4 | Demo & Objection Playbook | Demoed only 3 capabilities tied to that pain (AI reply drafting, shared inbox triage, SLA dashboard); handled "we'll just hire more agents," "price," and the "it's Devon's budget" authority objection by arming Maya with a one-page business case. | Pain from discovery → drove which 3 features to show (deflect 1 of 3 hires, cut response time) and how to multi-thread Maya up to Devon. |
| 5 | Pipeline & Forecast | GearGrid at Negotiation/Commit, $31.7k ARR (66 agents × $40 × 12), 80% probability; weighted $25.4k, in redlines with a verbal yes from Devon Apraku (VP of Operations, the economic buyer). Backed out activity: ~6 meetings/mo → ~120 touches/wk to hit an 8-meeting SDR quota. | Same deal — the buyer Maya named in D1 now owns the number; sized, staged, and forecasted honestly. |
The thread (what I say out loud): "I picked GearGrid because the 'why now' was textbook — order volume doubled, they're hiring three support agents, and their own Trustpilot reviews complain about slow replies. I opened on Maya Chen, their Head of Customer Support, because she owns the response-time metric and feels the pain daily; I led every outreach touch with that pain and booked the meeting off a referenced review. Discovery turned 'slow replies' into real numbers — 3,000 tickets a month, a 14-hour first response, and ~$78k a year in the hires they were about to make — and surfaced the one gap: the budget lives with Devon Apraku, the VP of Operations. So I demoed only the three things that move those numbers, handled the 'we'll just hire more agents' objection by showing the deal deflects one of the three hires, and used the 'it's Devon's budget' objection as the opening to multi-thread — arming Maya with a one-page business case to bring Devon into the room. That land-the-team motion is how 11 front-line agents became a 66-seat order covering the whole support org. Then I forecasted it honestly: $31.7k ARR, in redlines at Commit, 80% — closing this quarter."
Portfolio proof-points (my three hardest numbers):
- $78k/yr of quantified pain surfaced in discovery (3 planned hires) — sold against headcount, not features.
- $31.7k ARR deal built and staged to Commit (80%) — weighted forecast $25.4k.
- Worked backward from quota: ~120 personalized touches/week → 8 meetings/month, the activity math an SDR lives by.
How I defend it if a hiring manager pushes back: every number traces to a named source — the $78k is Maya Chen's own headcount math from the discovery call, the 80% is anchored to the Negotiation stage (not wishful), and the 66-seat ARR is the order-form scope Devon Apraku signed off on, not the 11-agent discovery figure. Ask me about any cell in the table and I can walk you back to the artifact it came from.
"Why tech sales, why me" — 60-second pitch (spoken, ~150 words):
"I want tech sales because I'm at my best when there's a target, a scoreboard, and a customer to win over — and Lumadesk sells something I'd genuinely enjoy pitching, because every overwhelmed support team is a problem I can prove I solve. Here's why I'm built for the SDR seat:
- Drive & results: I ran the floor at a 14-table restaurant section and finished #2 of 14 on upsell revenue for three straight quarters — I chase a number daily and like being measured.
- Communication: I handled 80+ guest interactions a shift, reading people fast and tailoring the pitch — the exact muscle a discovery call needs.
- Resilience: After a 40% no-show month, I rebuilt my regulars from scratch through follow-up and persistence instead of taking the 'no' personally — that's the SDR's whole job.
I've already worked a full deal end to end — GearGrid, cold to an $31.7k-ARR forecasted close. I'd love to bring that same motion to your team. Can we book a first-round conversation this week?"
Rubric
The app's AI scores the learner's submission against these criteria and gives feedback. Levels: Needs work (1) / Solid (2) / Excellent (3). Passing = every criterion at Solid or above.
- Coherent one-deal story — 1: artifacts listed as disconnected files · 2: a table linking all five with outcomes · 3: a single deal where the row-1 trigger, the row-3 quantified pain, and the row-5 ARR are visibly the same GearGrid deal, narrated as one motion.
- Real outcomes & numbers (no placeholders) — 1: vague summaries or "[trigger]/TBD" · 2: each artifact has a concrete outcome · 3: every row cites hard figures (tickets/mo, response-time hours, ARR, probability, activity math) pulled straight from the prior deliverables.
- Trait-mapped, quantified "why me" pitch — 1: generic enthusiasm, no numbers · 2: covers drive/communication/resilience/results with some specifics · 3: each bullet pairs a real reframed achievement with a number and a named trait, and the pitch reframes a non-sales background into sales language convincingly.
- 60-second discipline & closing ask — 1: rambling, over length, or no ask · 2: roughly 60 seconds and ends with a next-step ask · 3: tight ~150 words, leads with genuine why-sales/why-company, and closes by confidently asking for the interview — treating the pitch itself like a sales call (Topic 10).
- Interview-ready packaging — 1: rough notes, not presentable · 2: clean one-page summary you could share · 3: a polished, resume-toppable artifact with a 3-second deal headline and three lead-with proof-points you could defend under questioning.