How to Build a Raise Request Around Your AI Skills
Jordan’s weekly report used to take an hour and a half. An approved AI tool got the first draft done faster. Then Jordan checked the figures, fixed the mistakes and handed it off. How much time did the team get back once Jordan counted the checks and corrections? That’s the number worth bringing to a raise request.
If AI helped you do better work, start with one result your manager can verify. Show what improved, what it took and what you contributed. Then connect that result to your broader responsibilities and ask for a specific change in pay or a review of your role. Nobody in payroll needs to see your finest prompt.
Pros and Cons of Using AI Results in a Raise Request
Pros
- A small test can show whether the new workflow saves time or improves the work.
- Crediting reviewers and teammates makes the result easier to verify.
- A specific pay request gives your manager something concrete to take into a review.
Cons
- Setup and review can eat into the time saved on a first draft.
- Permission to use a tool may come with restrictions on data, storage and sharing.
- Good results can support your case while pay bands, budgets and approval still affect the answer.
Reviewed November 9, 2026, using U.S. wage data guidance and NIST’s generative AI risk profile. Jordan, the pilot and the pay figures are fictional. This is general career and financial education.
Start Your Raise Request With Better Work
Pick a result your manager already cares about. A coordinator might get a weekly report to the team before a meeting. For an analyst, fewer corrections to a recurring reconciliation might matter more. Ask what changed for the team. Getting the report out early only helps if somebody can use it sooner.
Jordan chose the weekly report because it took time every week and a reviewer could check the same finished work either way. Keep a note of the wider job, too. One faster report can strengthen a record of good work. A manager may need to see that you took on more responsibility or sustained the improvement over time.
Get Permission Before You Test Anything
Ask which tool, account and data you can use for the task. If the rules are unclear, start with a public or fictional example only after you’ve confirmed the tool is allowed. Keep confidential documents, client details, credentials and employee information out of any tool that hasn’t been approved for them. Removing a name can still leave enough detail to identify someone.
Decide who will check the result and what they will check it against. The NIST generative AI risk profile identifies privacy risks and recommends verifying sources in AI outputs. Jordan checked the report’s numbers against the approved records and kept notes in the work system. Get permission before moving even a summary outside that system.
Find out whether your employer supplies the approved tool. If you’re tempted to pay for another subscription, run a subscription audit first. Your manager can help you pick a task you can test with what’s already available.
Choose a Small Test Your Manager Can Review
Start with a repeated task you can finish and check. Agree on what counts as a good result, how much time to spend testing and when to stop. Ask for time within your normal work schedule and include anyone who’ll do added checking.
Could I try the approved assistant on the first draft of the weekly report? I’ll keep our existing checks and track the time through handoff. Can we agree on what the reviewer should check and meet after six reports?
If your manager cares more about fewer corrections than faster delivery, write that down before you start. The pilot can then answer the question your team needs answered.
Count the Work From First Draft to Handoff
Six reports at Jordan’s usual 90 minutes each would take nine hours. In the test, preparation and drafting averaged 20 minutes. Verification took another 20, and fixes and handoff took 10. That’s 50 minutes per report, or five hours for six reports. Jordan also spent an hour and a half on setup and practice. Subtract five hours of work and 1.5 hours of setup from the nine-hour baseline. The team got 2.5 hours back.
Use recent, similar reports for the comparison. If one required a dozen exceptions and another needed only a few line edits, note the difference or compare them separately. Add reruns, failed drafts and any review time a teammate took on. Moving ten minutes to somebody else’s calendar doesn’t give the team ten minutes back.
Record who checked the result and whether it met the agreed standard. If the old time is an estimate, mark it as one. A small pilot can tell you what happened on these runs. A new template or practice may have helped as well.
Separate Time, Cash and Quality in a Raise Request
Jordan had 2.5 hours available for other work. That can help if the team uses it to clear a backlog or get a report out earlier. The team did not verify any avoided charges, and it spent an extra $30 on the tool for the pilot. The pilot’s net cash cost was $30. If you multiply the hours by a wage, label it as an estimate of what the staff time is worth. Use receipts or invoices for claims about actual cash.
Give quality its own line in the report. If a reviewer accepts all six reports or requests fewer corrections, record what they checked and what they found. A workflow that takes the same time and produces fewer errors may still be worth keeping. If it needs more review and the work gets worse, tell your manager and reconsider the test.
Write a One-Page Brief for Your Raise Request
Start with the problem and why your team cared. Then list what you changed, the result across the test period and how someone can verify it. Name the people who helped, the costs and the limits. Use links to approved internal records if they’re needed and permitted.
I tested the approved workflow on six comparable weekly reports. The team got 2.5 hours back after setup, and the reports met our existing checks. The test cost an extra $30. I designed the checklist and documented the handoff. I’d like to talk about what it would mean for my role if I take ongoing responsibility for this work.
Bring the rest of your record into the conversation. If you’ve started training colleagues, taken ownership of a recurring process or improved delivery on other work, show how that changed what the team relies on you to do. A manager can use that context when they discuss your role level.
Choose a Raise Request You Can Support
Compare pay for similar responsibilities and location. Check your employer’s pay band if you can access it, and look at current postings with a similar level and schedule. The Bureau of Labor Statistics wage overview shows how to find wage data by occupation and area. An occupational figure covers more than one employer or seniority level, so use it as a reference alongside the closer matches.

Choose what you want the manager to consider. Ask for a specific amount within your role’s band, or ask for a promotion review if the responsibilities now match a higher level. Check who can approve it and when the next pay decisions happen. Use pay figures for jobs with responsibilities close to yours.
Suppose you’re asking to move from $60,000 to $64,800. That’s 8% more in base pay, or $4,800 a year before deductions. It works out to $400 per month or about $184.62 per check across 26 equal pay periods. The workbook shows full-year gross pay. Your effective date and deductions affect what actually arrives, so wait for the change to show in payroll before updating your monthly budget reset.
Ask for a Meeting and Leave Room for an Answer
Book time specifically to discuss compensation. Bring the one-page brief, your wider work record and the pay comparison. If you want to practice with a tool, use fictional details on an approved account. Keep your compensation records and company material where policy allows.
I’d like to review my base pay. Over the past [period], I’ve taken on [responsibility] and delivered [verified results]. Based on the scope of my role and [pay reference], I’d like to discuss moving to [amount]. What would the approval process look like?
Use your own facts and language. Explain how you used the approved tool and who checked the work. Then let your manager respond. Is the question about the evidence, your role level or the budget? If you’re being asked to own more work, agree on what can move off your plate and how the new work will be evaluated.
What to Do if Your Raise Request Has to Wait
Ask what would make a review possible. If the manager wants to see the work sustained, agree on a measure, a date and who will review it. If the constraint is the budget, ask when the next decision is made and what can be considered then.
Send a short follow-up that records the agreement. For example, “Thanks for meeting with me. I’ll track [agreed result] through [date], and we’ll review it with [decision-maker] on [review date]. Let me know if I’ve missed anything.”
If your pay follows a contract or formal progression rules, check the applicable process. When base pay is frozen, discuss options you’d actually use, such as paid training or a formal promotion review. A review that keeps slipping may be a reason to look elsewhere. The job-search guide can help you look at other roles while you decide what to do.
Use a Month to Gather Your Evidence
In week one, agree on the task, permission and what a good result looks like. Spend week two recording the work and checks. If the task runs weekly, start with the runs you can finish and take more time to build a useful sample.
Use week three to review what’s happened so far and gather pay references. In week four, write the brief or schedule the discussion around your employer’s review calendar. Jordan’s six weekly reports would take longer than a month. Let the actual work set the date for your request.
Frequently Asked Questions
Can I Make a Raise Request Just Because I Learned AI?
You can ask for a pay review. Give your manager something they can evaluate, such as verified results, new responsibilities or the ability to handle work at the next level. A course may help you develop the skill you need to do that.
Should I Explain That I Used AI?
Follow the disclosure rules at work. Describe the tool’s role, the checks you did and what the team delivered. Give teammates credit for their work and distinguish the team’s result from your contribution.
What if the Test Takes Longer Than the Old Process?
Record the extra time and check whether the output improved. If you spent longer and got the same or worse results, stop and tell the manager what you found. That can save the team from expanding a workflow it doesn’t need.
Do I Need to Pay for a Certificate Before Asking?
Ask which skills or credentials your employer actually values. You can run a small, approved test without buying a certificate. Keep training decisions separate from the pay review unless a credential is part of the role’s requirements.
The Bottom Line
Jordan can show the team got 2.5 hours back, what it cost and how the work was checked. The next step is to show how the improvement fits Jordan’s broader responsibilities, then ask what it would take for that work to count in a pay review. Start by asking your manager which recurring task they’d like to see improve.
Free Raise-Ready Tools
Use the Raise-Ready Evidence Kit PDF to agree on the test, write the brief and prepare the conversation. The Work Wins Tracker Excel workbook logs up to 12 runs, totals the time and cash effects separately, and compares gross pay scenarios. Use the files only where your employer’s policy allows. Enter your email and agree to the newsletter signup below to receive both tools. You can unsubscribe anytime.
Put this article into action
Get this article’s free PDF worksheet and Excel workbook.







