---
title: "How Do I Add Numbers and Metrics to My Resume?"
description: "Ask \"how much?\", \"how many?\", \"how often?\", and \"compared to what?\" for every bullet. When exact figures are unavailable, name the scope."
canonical: "https://mortit.com/blog/how-to-quantify-resume-achievements"
---
Resume Writing

# How Do I Add Numbers and Metrics to My Resume?

Four questions to ask for every bullet point, a before/after table across five role types, and what to write when you genuinely cannot get the number.

8 min read Updated October 2026

By [Arash Abdollahi](https://mortit.com/about), Founder Published by [MORT](https://mortit.com/) Updated October 2026

TL;DR

**Ask "how much?", "how many?", "how often?", and "compared to what?" for every bullet.** If you managed a team, name the headcount. If you ran a campaign, give the result. If you cannot get an exact figure, name the scope instead - such as "for a 200-person organisation." When you genuinely estimate, say so with "approximately" or a tilde.

Most resume advice tells you to quantify your bullets. Very little tells you how. This guide gives you a concrete method: four questions that convert any vague duty into a measurable achievement, a comparison table showing the transformation across five role types, and honest guidance on what to write when the numbers are gone.

## Why numbers matter on a resume

A number does two things a vague phrase cannot. First, it signals specificity: you were close enough to the work to measure it. Second, it gives a reviewer a reference point to compare you against other candidates. "Improved team performance" and "reduced deployment time by 40% for a team of 8 engineers" describe the same type of contribution, but only the second one is extractable - a reviewer can use it, remember it, and repeat it to a hiring committee.

The average corporate job opening attracts around [250 applicants, of which 4 to 6 are called for an interview](https://www.glassdoor.com/blog/50-hr-recruiting-stats-make-think/) (Glassdoor, long-standing benchmark). At that volume, reviewers make fast judgements. A bullet with a specific figure stands out because it reads as evidence, not a claim.

For context on the basics of what to include in this section of your resume, see our guide on [what to put in the work experience section](https://mortit.com/blog/what-to-put-in-work-experience-section-resume). This post focuses specifically on the quantification step.

## The four questions to ask for every bullet

Before you write or revise a bullet, run it through these four questions. You do not need a yes to all four - one good answer is enough to strengthen the bullet.

#### The four questions

-   **How much / how many?** - Size, volume, headcount, budget. "Managed a team" becomes "managed a team of 6." "Handled supplier contracts" becomes "negotiated contracts with 14 suppliers."
-   **How fast / how often?** - Time saved, frequency, cadence. "Ran weekly reports" becomes "automated weekly reporting, cutting preparation time from 4 hours to 20 minutes."
-   **By how much did it improve?** - Percentage lift, reduction, growth rate. "Increased revenue" becomes "grew quarterly revenue by 22%."
-   **Compared to what?** - Baseline, target, or industry average. A percentage without a baseline is weak. "Improved conversion by 12%" is stronger than "improved conversion," but "improved conversion from 2.1% to 3.3%" is stronger still.

Apply the questions in order. Start with "how much / how many?" because scope is always available, even when outcome figures are not. Work outward from there.

## Before and after: turning vague bullets into quantified achievements

The table below shows the transformation across five common role types. Each weak version is a real duty; each strong version answers at least one of the four questions above.

| Role type | Weak (vague duty) | Strong (quantified achievement) |
| --- | --- | --- |
| **Engineering** | Improved team performance | Reduced deployment time by 40% for a team of 8 engineers, cutting release cycles from 3 weeks to 4 days |
| **Sales** | Exceeded quota | Closed 118% of annual quota ($1.4M ARR), ranking 2nd of 22 account executives in the EMEA region |
| **Marketing** | Managed social media accounts | Grew LinkedIn follower count from 4,200 to 11,800 over 9 months while reducing cost-per-click by 31% |
| **Operations** | Improved supply chain processes | Renegotiated contracts with 6 suppliers, reducing procurement spend by approximately 18% (~£220,000 annually) |
| **Management** | Led a cross-functional team | Led a 14-person cross-functional team across 3 departments to deliver a £1.2M product launch 2 weeks ahead of schedule |
| **Customer Success** | Managed key accounts | Managed a portfolio of 40 enterprise accounts ($3.2M ARR), maintaining a 94% annual renewal rate against a team average of 87% |
| **Data / Analytics** | Built dashboards for the business | Built 12 automated Power BI dashboards used by 80+ stakeholders weekly, replacing 6 hours of manual reporting per analyst |

All figures in the table are illustrative examples showing the transformation method, not measured data. Use your own real numbers; the structure is what transfers.

## Metrics by role category

The right metrics vary by function. Here are the figures most relevant to common role types.

#### Sales and revenue roles

Quota attainment (as a percentage), revenue closed or grown (in currency), deals closed (count), pipeline built, average contract value, renewal rate, and ranking within a team or region.

#### Operations and supply chain

Cost reduction (percentage or absolute), process time saved, error or defect rate, supplier count, contract value, throughput volume, and SLA compliance rate.

#### Engineering and product

Deployment frequency, latency or uptime improvements, user count, feature adoption rate, bug reduction, team size, and time-to-ship comparisons.

#### Marketing

Reach (impressions, followers, subscribers), conversion rate, cost-per-click or cost-per-acquisition, revenue attributed to campaigns, A/B test lift, and budget managed.

#### Management and leadership

Direct reports, total headcount, hiring completed, retention rate, budget owned, delivery outcomes (on time, under budget), and promotions from within your team.

## What to do when you genuinely cannot get the number

Numbers from past roles are often hard to retrieve. You may no longer have access to the system, the project may have been confidential, or the organisation simply did not track that metric. Here is what to do in each case.

**Estimate with a qualifier.** If you know you saved roughly two hours per week on a process, write "approximately 2 hours per week" or "~2 hours per week." An honest estimate with a qualifier is acceptable; a made-up precise figure is not. Do not inflate: if an estimate feels risky to defend in an interview, it is too high.

**Substitute scope for outcome.** If you cannot measure the result, describe what you worked with: team size, budget, number of clients, volume of transactions, or geographic reach. "Supported procurement for a 500-person manufacturing site" has no percentage in it, but it tells the reviewer more than "supported procurement."

**Name the impact qualitatively, once.** "Rebuilt the onboarding process, reducing the number of support tickets in the first 30 days" is weaker than a percentage but still better than "rebuilt the onboarding process." One directional statement per bullet is fine when a number is genuinely unavailable. Do not use multiple vague qualifiers to compensate.

#### The cardinal rule

Never invent a number. A fabricated metric will be probed in an interview, and a credibility failure there ends the process immediately. An honest scope statement costs you nothing and risks nothing.

## Common mistakes to avoid

Adding numbers to a resume is not just about inserting percentages. These are the mistakes that undermine the effort.

**Percentages without a baseline.** "Improved conversion by 15%" is ambiguous. 15% of what? From 1% to 1.15% is trivial. From 20% to 35% is significant. Always give the reader enough context to judge the size of the change.

**Inconsistent units.** Mixing currencies, fiscal years, and time periods in the same bullet forces the reviewer to do mental arithmetic. Keep each bullet self-contained and consistent.

**Numbers on low-stakes bullets.** Quantifying every bullet regardless of significance creates noise. Focus your numbers on the work that mattered most. A bullet about "attended 3 team meetings per week" is worse for having the number in it.

**Ignoring which bullets the job description cares about.** If the role is focused on revenue, your revenue bullets need the strongest numbers. Spend time quantifying the bullets most relevant to the posting, not all bullets equally. Our guide on [how to match your resume to job descriptions](https://mortit.com/blog/how-to-match-your-resume-to-jobs) covers this prioritisation step in detail.

## Using MORT to identify which bullets to quantify first

Knowing which bullets matter most for a specific role saves time and produces a better result. MORT is an AI job-matching platform for people who want to apply to more relevant jobs in less time. It scans thousands of company career pages, scores every job 0-100% for compatibility with your skills and experience, and generates a tailored resume for each application. The compatibility score surfaces the skills and outcomes a specific job weights most, which tells you exactly which of your bullets are worth quantifying first. You can also use the [MORT ATS checker](https://mortit.com/ats-checker) to see how your current resume matches a specific posting before you apply.

## Frequently asked questions

### What if I no longer have access to the exact numbers?

Estimate with a clear qualifier. Say "approximately" or use a tilde before the figure. If you genuinely cannot estimate, substitute scope for outcome: name the team size, budget, or volume you worked with. "Managed customer accounts" becomes "Managed a portfolio of 40 enterprise accounts." Scope is stronger than a bare duty even without a percentage.

### Should I add numbers even if they are very small?

Usually yes, with context. A 5% improvement sounds modest in isolation, but "reduced customer churn from 18% to 13% over two quarters" tells a clear story. Small numbers are fine; naked percentages without a baseline are not. Always give the reader enough information to judge whether the result was meaningful.

### What if my role does not have obvious metrics?

Every role has scope metrics even when it lacks output metrics. Count the things you touched: number of stakeholders managed, documents produced, tools deployed, suppliers negotiated with, training sessions delivered. Scope answers "how much?" and is a valid substitute when outcome percentages are not available.

### How do I quantify a management or leadership role?

Name the headcount directly managed, the hiring you did, and the budget you owned. Then add one outcome per major initiative: "Led a team of 12, hired 4 engineers, and reduced time-to-deploy from 3 weeks to 4 days." Headcount, budget, and delivery speed are the three clearest management metrics.

### Does every bullet need a number?

No, but aim for a number or a scope figure in at least two of every three bullets on your most recent roles. Prioritise the bullets that describe your highest-impact work first. A bullet with strong scope or a named outcome is always better than one that reads as a bare duty.

## Know which bullets to quantify for each role

MORT scores every job 0-100% for how well it matches your skills and experience, then generates a tailored resume per application. Use the compatibility score to see which of your bullets the job weights most, so you quantify the right ones first.

[Start Free](https://app.mortit.com/signup) [Check Your Resume](https://mortit.com/ats-checker)

## Related Resources

### [What to Put in the Work Experience Section](https://mortit.com/blog/what-to-put-in-work-experience-section-resume)

The four fields every entry needs and how to write strong bullet points

### [How to Match Your Resume to Job Descriptions](https://mortit.com/blog/how-to-match-your-resume-to-jobs)

The step-by-step way to tailor for a specific posting

### [How to Write a Resume Summary](https://mortit.com/blog/how-to-write-a-resume-summary)

The opening section that sets up everything below it

### [How to Write an ATS-Friendly Resume](https://mortit.com/blog/ats-friendly-resume-guide)

Format and keyword guidance to get your resume past applicant tracking systems

## Sources

-   Glassdoor, "50 HR & Recruiting Stats" (~250 applicants per corporate opening; 4 to 6 interviewed; long-standing benchmark): [glassdoor.com](https://www.glassdoor.com/blog/50-hr-recruiting-stats-make-think/)