How to Quantify Your Resume When You Don't Have Sales Numbers

The Advice Assumes You're in Sales. Most People Aren't.

"Quantify your resume" is the most repeated piece of resume advice there is, and it's usually followed by an example like "increased revenue by 30%" or "closed $2M in new business." If you're in sales, that's easy. If you're an engineer, a support lead, a designer, or an operations manager, it can feel like the advice simply doesn't apply to you — so you fall back on vague verbs like "managed," "helped," and "responsible for."

The truth is almost every role generates numbers. You're just not used to looking for them, because nobody handed you a quota. Here's where to find them, organized by the kind of work you actually do.

Five Places Numbers Hide Outside of Sales

1. Volume and throughput

How much did you personally move through the system? A support agent can count tickets closed per week. An editor can count articles published per month. A recruiter can count requisitions filled per quarter.

• Weak: "Handled customer support tickets."
• Better: "Resolved an average of 45 support tickets per week, 20% above the team average."

2. Time saved or time-to-completion

Did you make something faster? Onboarding, approvals, builds, reviews — anything with a "before" and "after" duration is quantifiable, even if you have to reconstruct the before number from memory or old tickets.

• Weak: "Improved the onboarding process for new hires."
• Better: "Redesigned new-hire onboarding, cutting time-to-first-commit from 3 weeks to 8 days."

3. Error rate or quality

Fewer bugs, fewer returns, fewer escalations, fewer typos caught in review — reductions in bad outcomes are just as compelling as increases in good ones, and they're often easier to measure because someone was already tracking the problem.

• Weak: "Improved code quality on the team."
• Better: "Introduced a pre-merge checklist that reduced production incidents from 6/month to 1/month."

4. Scale and scope

When you can't measure a change, measure the size of what you were responsible for. Budget managed, team size, number of systems maintained, number of stakeholders coordinated across.

• Weak: "Coordinated cross-functional projects."
• Better: "Coordinated a 12-person cross-functional launch spanning 4 departments and a $180K budget."

5. Cost avoided or saved

You don't need a P&L to have saved money. Renegotiating a vendor contract, automating a manual process, or catching a bug before it shipped all have a dollar value attached, even if you have to estimate it conservatively.

• Weak: "Automated a manual reporting process."
• Better: "Automated weekly reporting, saving roughly 6 hours of manual work per week across the analytics team."

When You Genuinely Don't Have the Exact Number

Sometimes you really can't go back and pull the data — the ticket system is gone, the old dashboard was deleted, the project ended two jobs ago. In that case, a defensible estimate beats a vague verb every time. Say "approximately" or "an estimated" and use a number you could explain if asked in an interview. A recruiter reading "reduced onboarding time by an estimated 40%" will trust it more than "significantly improved onboarding," because it signals you actually thought about impact instead of just listing duties.

The Real Problem Isn't Memory — It's Timing

Most people try to reconstruct these numbers eighteen months later, right before a job search, when the context is already gone. The moment you actually know the before-and-after numbers is the week you did the work — not the week you're updating your resume. This is the gap Strivo is built to close: you talk through a project or a win in the moment, in your own words, and it gets stored and later turned into a specific, numbers-backed resume bullet or interview story when you actually need one.