Do this in week one
- 1. Take your best-performing page and produce ten derivative assets from it
- 2. Build a brief template the model fills in before it writes anything
- 3. Draft next month's calendar from last quarter's traffic data
Productivity & daily use
Quick answer
Enter your job title and the tool identifies the single highest-leverage AI use for that role, with the hours it saves each week and the first prompt to try. It deliberately returns one recommendation rather than a list, because narrow, repeated use beats broad experimentation for building a habit.
Every role has one use that returns more than all the others combined. Start there, not with a list of forty tools.
Published · Last updated
Your highest-leverage use
Turn one asset into twelve
Repurposing is pure translation work: same facts, new format and length. Models do it near-perfectly and it is the single biggest time sink in content teams.
Publishing unedited first drafts. Detection is the least of your problems; sameness is.
Here is a source article. Produce a newsletter intro, five social posts and three ad headlines that reuse only facts present in the source. Do not invent statistics.
People who get real value from AI almost always do one thing repeatedly until it is reliable, then add a second. People who get nothing from it try a different tool every week and never build a prompt worth reusing.
The hours figure scales with the length of your week and assumes you keep the review step. Treat it as the ceiling of a habit that takes about a month to form, not as an immediate saving.
The avoid line is role-specific for a reason. The failure that damages a lawyer is not the failure that damages a marketer, and the guardrail is what keeps the time saved from being spent cleaning up afterwards.
| What it answers | The highest-leverage AI use for your role. |
|---|---|
| How the answer is produced | Leverage is frequency multiplied by time saved multiplied by how reliably a model handles the task. |
| What you need to enter | Choose the role that matches your day-to-day work. |
| Where it stops being reliable | Role-level advice cannot know your team's specific tools or constraints. |
| Cost and sign-up | Free, runs in your browser, no account and no stored inputs. |
Leverage is frequency multiplied by time saved multiplied by how reliably a model handles the task. Most people optimise for the third factor alone, picking the most impressive-looking use case rather than the one that repeats twenty times a week.
The tool maps your role to its recurring work, then ranks those tasks on all three factors. The winner is frequently unglamorous — reformatting, summarising a recurring input, producing a first draft of the same document type — precisely because unglamorous work is what repeats.
Alongside the recommendation you get a concrete prompt pattern for that task, because the gap between a mediocre and an excellent result on repetitive work is almost entirely in how the request is framed.
People choosing their first AI use case tend to pick the most impressive-sounding option — drafting a strategy document, generating a complex analysis — because it demonstrates the technology's ceiling. That instinct optimises for the wrong variable. A task performed twenty times a week returns compounding value even at a modest saving per instance, while an impressive but quarterly task returns a one-off saving no matter how dramatic it looks in a demo.
Interpreting a role-based recommendation well means checking it against your actual calendar rather than your job title, since two people with the same title often spend their weeks completely differently — one project manager might spend hours in status reporting while another spends hours in stakeholder negotiation, and only one of those maps well onto a language model's strengths. The supplied prompt pattern matters as much as the task identification, because the gap between a vague request and a well-framed one is usually the entire difference between a usable first draft and one that needs rewriting from scratch.
What changes the recommendation most is how much of the task is genuinely repetitive versus how much requires fresh judgement each time — reformatting a recurring report is highly repetitive even though the underlying numbers change weekly, while responding to a new client query is not repetitive even though it superficially resembles the last one. The common mistake is abandoning a recommendation after one mediocre result instead of iterating the prompt, when the pattern usually needs two or three refinements before it reliably produces a usable draft.
The recommendation also assumes you will actually build the habit, and that is where most people quietly drop the idea within a week. A task that saves four minutes each time it happens does nothing for anyone if it only gets tried once, out of curiosity, and never again. Attaching the recommendation to an existing trigger — the same point in your calendar where the task already happens — turns a one-off experiment into a habit far more reliably than remembering to use the assistant on general principle.
For this role, the highest-leverage task is drafting a first-pass summary of each CV against the job description's key requirements, done dozens of times a week. The tool supplies a prompt pattern asking for a structured comparison against named criteria rather than a general opinion, which produces a consistent, scannable output the recruiter can accept or override in under a minute per CV.
For this role, the recommendation is generating a first draft of differentiated worksheet variants from one base lesson, a task repeated for every class taught each week. The prompt pattern specifies the year group, learning objective, and the specific way the variant should differ, because a vague request for 'an easier version' reliably produces material that misses what actually needs simplifying.
For this role, the highest-leverage task is turning a set of raw figures and a one-line instruction into a fully formatted explanatory email, done for nearly every client interaction. The supplied prompt pattern asks for the explanation to be structured around what changed and why, in that order, because clients consistently respond better to being told the reason for a number before being shown the number itself, and a generic prompt tends to produce the two in reverse.
Because leverage comes from frequency. A five-minute saving on a task you do daily beats an hour saved on something quarterly.
Pick the nearest match. The underlying task families generalise well across desk-based roles.
No. Every recommendation works with any general-purpose assistant.
Check your organisation's data policy before pasting anything client-identifiable into a general-purpose assistant, and if in doubt, apply the same prompt pattern to a redacted or synthetic version of the data first to confirm the approach works before deciding how to handle the real thing.
Written and reviewed by Jim Vernon, Editor, AI Intelligence International. Published by AI Answer Engine, a service of AI Intelligence International, and checked against our editorial standards.