Only 10% of resumes include measurable results. That's according to an analysis of 18.4 million US resumes, and it means that 90% of job seekers are describing duties instead of proving impact.
Meanwhile, hiring managers spend 6 to 7 seconds on their initial scan of your resume. In that window, a bullet point that says "Responsible for managing client accounts" is invisible. A bullet point that says "Managed a portfolio of 35 client accounts worth £4.2M, achieving a 94% retention rate" is impossible to ignore.
Numbers are the fastest way to prove your value. They transform vague claims into concrete evidence. And the best part: once you learn the framework, quantifying your achievements takes minutes, not hours. I use these exact formulas in JobSprout's AI writing assistant, and the before/after difference is consistently dramatic.
This guide shows you exactly how to do it, with formulas, frameworks, and 50+ before/after examples across every major industry. Whether you're writing your resume for the first time or rebuilding it after a layoff, these principles apply.
Why Numbers Work (The Psychology)
There's a reason numbers stand out on a resume. It's not just aesthetics. There are three cognitive principles at work.
1. The Concreteness Effect
Specific information is more memorable than abstract information. "Increased revenue" is abstract. "Increased revenue by 34% in 6 months" is concrete. Research consistently shows that concrete details are processed faster and remembered longer than vague claims.
2. Pattern Interruption
Resumes are walls of text. Numbers create visual breaks. When a recruiter's eye is scanning lines of prose, a percentage or dollar figure physically interrupts the pattern and draws attention. This is especially important during the 6-second scan.
3. Credibility Signal
Anyone can claim they "improved team performance." A specific claim like "improved team close rate from 22% to 31% over Q3" is harder to fabricate and therefore more credible. Numbers signal that you tracked your impact, which itself signals professionalism.
The 3 Formulas for Quantifying Anything
Every quantified achievement on your resume should follow one of these three structures. If your current bullet points don't fit any of them, they probably need rewriting.
Formula 1: Action + Metric + Outcome
The most common and versatile formula. You describe what you did, the measurable result, and (optionally) the business impact.
Led the migration of 3 legacy payment systems to Stripe, reducing failed transactions by 28% and saving the ops team 12 hours per week in manual reconciliation.
Formula 2: Before/After Comparison
Shows transformation. Particularly powerful because it gives context to the achievement.
Redesigned the customer onboarding flow, increasing completion rate from 38% to 72% and improving first-week retention by 25%.
Formula 3: Scale + Context
When you can't easily show a percentage change, describe the scale of what you managed.
Managed a portfolio of 45 enterprise accounts worth £12M in annual recurring revenue, with a 96% renewal rate over 3 years.
Choosing the Right Formula
Situation
Best Formula
Why
You improved something measurably
Before/After
Shows the delta, which is the most compelling evidence
You delivered a result
Action + Metric + Outcome
Shows cause and effect
You managed ongoing responsibility
Scale + Context
Shows scope and reliability
You don't have percentage data
Scale + Context
Scope is always quantifiable
What to Quantify (and How to Find the Numbers)
Most people think they can't quantify their work because they don't have access to dashboards or reports. I hear this constantly. And it's rarely true. You have more numbers available than you realise.
8 Categories of Quantifiable Achievement
Category
What to Measure
Example
Revenue and Growth
Sales generated, revenue increased, deals closed
"Generated £1.8M in new business revenue"
Cost Savings
Budget reduced, waste eliminated, time saved
"Reduced vendor costs by £120K annually through contract renegotiation"
Efficiency
Time saved, processes streamlined, automation
"Automated monthly reporting, reducing preparation from 3 days to 4 hours"
Scale
Team size, budget managed, users served, transactions processed
"Managed operations for a 200-person division across 4 offices"
"Grew organic traffic from 5K to 45K monthly visitors"
Speed
Delivery time, response time, time-to-market
"Reduced average customer response time from 48 hours to 4 hours"
People
Training delivered, team grown, retention improved
"Mentored 6 junior developers, 4 of whom were promoted within 18 months"
Where to Find Your Numbers
If you don't have metrics at your fingertips, here's where to look:
Performance reviews. These often contain numbers you've forgotten: targets met, projects delivered, ratings received.
Email history. Search for "results," "report," "update," or "quarterly." You've probably sent recap emails with data in them.
Project management tools. Jira, Asana, Trello, and similar tools track completion rates, timelines, and velocity.
CRM data. If you've used Salesforce, HubSpot, or any CRM, your pipeline and close rates are there.
Company reports. Annual reports, investor decks, and internal dashboards often contain metrics you contributed to.
Reasonable estimates. If you genuinely can't find exact numbers, use reasonable approximations with qualifying language: "approximately," "over," "roughly." An honest estimate is better than no number at all.
50+ Before/After Examples by Industry
Here's the core of this guide: real examples showing how to transform duty-based bullet points into quantified achievements. Find your industry and role, and use these as templates.
Technology and Engineering
Before (Duty)
After (Achievement)
"Developed features for the web application"
"Architected and shipped 8 microservices in Go, reducing API latency by 40% and improving uptime to 99.95%"
"Fixed bugs and resolved technical issues"
"Reduced production bug backlog from 85 to 12 over 6 months, cutting customer-reported issues by 73%"
"Worked on the data pipeline"
"Built real-time data pipeline processing 2.3M events daily with sub-second latency using Apache Kafka and Spark"
"Participated in code reviews"
"Reviewed 200+ pull requests, identifying 45 critical bugs pre-deployment and establishing team code review standards"
"Managed cloud infrastructure"
"Optimised AWS infrastructure spend by 32% (£95K annually) while improving deployment frequency from weekly to daily"
"Improved application performance"
"Led performance optimisation initiative that reduced page load time from 4.2s to 1.1s, contributing to a 15% increase in user retention"
Marketing
Before (Duty)
After (Achievement)
"Managed social media accounts"
"Grew social media engagement by 147% across 4 platforms, driving 2,300 qualified leads in 8 months"
"Created content for the blog"
"Published 45 SEO-optimised articles that generated 38K monthly organic visits and ranked on page one for 22 target keywords"
"Ran email marketing campaigns"
"Managed email programme for 85K subscribers, achieving 34% open rate and generating £420K in attributed revenue"
"Managed advertising budget"
"Optimised £150K quarterly ad spend across Google and Meta, reducing cost per acquisition from £45 to £28 (38% decrease)"
"Conducted market research"
"Identified a £2.1M market opportunity through competitive analysis, directly informing the launch of a new product line"
Sales
Before (Duty)
After (Achievement)
"Sold products to enterprise clients"
"Closed £2.8M in new business over 6 quarters, averaging 122% quota attainment"
"Generated leads and managed pipeline"
"Built and maintained a pipeline of 50+ qualified opportunities worth £8M using Salesforce and 6sense intent data"
"Managed key accounts"
"Grew 12 strategic accounts by 45% through upselling and cross-selling, adding £1.4M in annual recurring revenue"
"Made cold calls and sent outreach"
"Executed outbound campaigns generating 150+ qualified meetings per quarter with a 12% response rate"
"Trained new sales team members"
"Onboarded and mentored 8 new reps, with 6 reaching quota within their first quarter (vs. company average of 2 quarters)"
Finance and Accounting
Before (Duty)
After (Achievement)
"Prepared financial reports"
"Prepared quarterly financial models for a £85M P&L, presenting variance analysis to C-suite leadership"
"Managed budgets"
"Managed £12M operational budget, identifying £340K in annual savings through vendor renegotiation"
"Handled accounts payable"
"Processed 500+ invoices monthly with 99.8% accuracy, reducing payment cycle time from 30 to 15 days"
"Conducted audits"
"Led internal audit of 3 business units, identifying £180K in recoverable costs and 5 compliance gaps"
"Created financial models"
"Built forecasting model in Excel that improved quarterly revenue prediction accuracy from 78% to 93%"
Healthcare
Before (Duty)
After (Achievement)
"Provided patient care"
"Managed care for 5-6 patients per shift in a 40-bed medical-surgical unit with 97% patient satisfaction scores"
"Administered medications"
"Implemented medication reconciliation protocol that reduced medication errors by 32% across the ward"
"Trained nursing staff"
"Developed and delivered training programme for 25 nurses on new EHR system, achieving 100% adoption within 6 weeks"
"Improved patient outcomes"
"Reduced patient readmission rates by 18% through implementation of enhanced discharge planning protocol"
"Managed clinical documentation"
"Achieved 99.5% documentation accuracy across 1,200+ patient encounters per quarter"
Operations and Project Management
Before (Duty)
After (Achievement)
"Managed projects"
"Delivered 12 projects on time and under budget, with an average budget variance of -8% (£420K total savings)"
"Improved processes"
"Implemented Lean methodology that reduced order fulfilment time by 34% and eliminated £280K in annual waste"
"Coordinated teams"
"Managed cross-functional team of 25 across 3 departments, maintaining 95% sprint completion rate over 8 quarters"
"Handled vendor relationships"
"Negotiated contracts with 8 key vendors, reducing procurement costs by 22% while improving delivery SLAs"
"Oversaw daily operations"
"Managed operations for a £15M business unit processing 10,000+ transactions daily with 99.9% accuracy"
Human Resources
Before (Duty)
After (Achievement)
"Handled recruitment"
"Reduced time-to-hire from 45 to 28 days across 150+ annual hires while improving quality-of-hire scores by 20%"
"Managed employee relations"
"Reduced voluntary turnover from 22% to 14% through targeted retention initiatives and stay interviews"
"Conducted training"
"Designed onboarding programme that reduced new hire ramp-up time from 3 months to 6 weeks"
"Managed HRIS"
"Led implementation of Workday for 500+ employees, completing data migration 2 weeks ahead of schedule"
"Developed HR policies"
"Authored 12 HR policies adopted across 3 offices, ensuring compliance with UK employment law updates"
Education
Before (Duty)
After (Achievement)
"Taught mathematics"
"Achieved 78% grade 4-9 GCSE pass rate, consistently above school and national average for 3 consecutive years"
"Developed curriculum"
"Created differentiated revision programme adopted department-wide, contributing to a 12% improvement in overall results"
"Supervised students"
"Led after-school Maths Club with 15-20 regular attendees, 8 of whom achieved A/A* grades at A-Level"
"Used technology in teaching"
"Integrated dynamic graphing software into curriculum for 6 classes, improving student engagement scores by 25%"
Customer Service
Before (Duty)
After (Achievement)
"Handled customer inquiries"
"Resolved 60-80 customer inquiries daily while maintaining 96% satisfaction rating across 12 months"
"Managed customer complaints"
"Reduced customer escalations by 40% through implementation of first-contact resolution protocols"
"Trained support team"
"Developed training materials and onboarded 12 new agents, reducing average ramp-up time from 4 weeks to 2"
Quantifying "Soft" Achievements
Not everything has a revenue figure attached. But almost everything can be quantified if you think creatively about scope, scale, and outcomes.
Communication
"Presented quarterly business reviews to 15 C-suite stakeholders across 4 client organisations"
"Wrote internal newsletter reaching 2,000+ employees with consistent 45% open rate"
"Created 30-page onboarding documentation that reduced new hire questions by 60%"
Leadership
"Mentored 6 junior team members, 4 of whom were promoted within 18 months"
"Led cross-functional task force of 12 to deliver company-wide process change affecting 500+ employees"
"Managed team of 8, maintaining 100% retention over 2 years in a department with 25% average turnover"
Problem-Solving
"Identified root cause of recurring system failure that had cost £45K in downtime over 6 months"
"Proposed and implemented workflow change that eliminated 15 hours of weekly manual processing"
"Resolved interdepartmental conflict that had delayed a £2M project by 3 months"
Organisation and Planning
"Coordinated company-wide event for 300+ attendees across 3 locations with £50K budget"
"Managed migration of 15,000 customer records to new CRM with zero data loss"
"Created project scheduling system that improved on-time delivery rate from 72% to 94%"
The "So What?" Test
After writing each bullet point, ask yourself: "So what?" If the answer isn't immediately obvious, the bullet needs more context or a clearer outcome.
Bullet Point
"So What?" Response
Improved Version
"Increased sales by 15%"
"From what baseline? Over what period? What caused it?"
"Increased quarterly sales from £800K to £920K (15%) by implementing consultative selling methodology across a team of 6"
"Managed 50 people"
"To what effect? What did the team achieve?"
"Managed a department of 50, delivering 3 major product launches on schedule while maintaining 92% employee satisfaction"
"Reduced costs"
"By how much? How?"
"Reduced operational costs by £180K annually by renegotiating 8 vendor contracts and automating invoice processing"
Every metric should answer: How much? Compared to what? Why does it matter?
Common Mistakes When Quantifying
1. Using Vague Modifiers Instead of Numbers
"Significantly increased," "dramatically improved," "greatly reduced." These words feel quantitative but say nothing. Replace every vague modifier with a number.
2. Inventing Numbers
Don't fabricate metrics. If you're caught in an interview, your credibility is gone. Use honest estimates with qualifying language ("approximately," "roughly," "over") when exact figures aren't available.
3. Metrics Without Context
"Achieved 92% customer satisfaction" sounds good until you learn the industry average is 95%. Always provide enough context for the number to be meaningful: timeframe, baseline, comparison point, or business impact.
4. Over-Quantifying
Not every single bullet needs a number. If you force metrics onto everything, some will feel artificial. Aim for 60-70% of your bullet points to include quantifiable results. The remaining 30-40% can describe scope, process, or qualitative impact.
5. Listing Numbers Without Actions
"£2.4M revenue" isn't a bullet point. What did you do to generate or influence that revenue? The action is as important as the number. Use our action verbs guide to find the right language. And make sure your formatting doesn't undermine your content: our ATS-friendly resume guide covers how to structure achievement bullets so they parse correctly through applicant tracking systems.
How to Quantify When You "Don't Have Numbers"
This is the most common objection I get from users, and it's almost never actually true. Here's how to find or create metrics for roles that seem resistant to quantification.
Ask Yourself These Questions
How many? People managed, projects completed, clients served, reports delivered, presentations given
How much? Budget managed, revenue influenced, costs reduced, money saved
How often? Tasks completed per day/week/month, frequency of delivery, meeting cadence
How fast? Time saved, deadlines met, turnaround improvements
How accurate? Error rates, compliance scores, quality metrics
How satisfied? Customer ratings, employee engagement scores, NPS
What was the scope? Geographic coverage, number of locations, team sizes
What changed? Before and after comparisons of any measurable element
When Exact Numbers Don't Exist
Use reasonable approximations:
"Processed approximately 200 invoices per month" (better than "processed invoices")
"Supported a team of roughly 30 engineers" (better than "supported the engineering team")
"Managed a budget of over £500K" (better than "managed a large budget")
The key word is "reasonable." If you estimate 200 and the actual number was 180, that's fine. If you estimate 200 and it was 50, that's dishonesty. For more on tailoring these numbers to specific job applications, see our resume tailoring guide. JobSprout's one-click job tailoring can help you emphasise the right achievements for each role automatically.
Frequently Asked Questions
How many bullet points should include numbers?
Aim for 60-70% of your experience bullet points to include at least one quantifiable metric. This creates a strong impression of results orientation without feeling forced. Your professional summary should also include at least one number.
What if my company doesn't share metrics with employees?
Use proxy metrics. You may not know the company's revenue, but you know how many clients you managed, how many projects you delivered, or how many hours per week your process improvement saved. You can also estimate based on available information: "Supported an estimated £5M client portfolio based on contract values."
Should entry-level candidates use numbers?
Absolutely. In fact, entry-level candidates benefit even more from quantification because they have less experience to draw from. Only 5% of entry-level resumes include metrics, compared to 12% for experienced professionals. That means quantifying your internship, academic, or volunteer achievements puts you ahead of 95% of peers.
Are percentages or absolute numbers better?
Both have their place. Use percentages when the absolute number is small but the improvement is impressive ("increased conversion rate by 34%"). Use absolute numbers when the scale is impressive ("managed £12M budget" or "served 500+ customers daily"). When possible, include both: "Grew team from 3 to 12 (300% increase) over 18 months."
What about achievements I contributed to but didn't lead?
Use honest attribution language. "Contributed to a cross-functional initiative that reduced customer churn by 18%" is perfectly valid. "Member of team that launched product generating £3M in first-year revenue" credits the team while showing you were part of something significant. Don't claim sole credit for team achievements, but don't undersell your contribution either.
Start Quantifying Today
The gap between a resume with numbers and one without is enormous. 90% of resumes lack measurable results, which means adding even a few quantified achievements puts you in the top 10% of applicants for clarity and impact.
Start with your most recent role. Take each bullet point and ask: "Can I add a number to this?" If the answer is yes, rewrite it using one of the three formulas. If the answer is "I don't know the exact number," estimate honestly. If the answer is genuinely "no," that bullet might be describing a duty rather than an achievement, and it's worth reconsidering whether it belongs on your resume at all.
If you want help turning your experience into quantified, professional bullet points, JobSprout can help. I built the AI writing assistant specifically to strengthen vague bullet points into quantified achievements. Upload your CV, and it will suggest stronger phrasing with specific metrics and action verbs. Professional Typst typesetting that highlights your numbers, not buries them.
