IS WORK OVER?

Automation index

How much of a Fundraiser’s job can AI already do?

A letter and a CRM come earlier. Asking for the money in person and getting it again do not.

This percentage does not predict how many people will lose their jobs.

Task comparison

Fundraiser

Where the time goes

Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.

The time saving for each task is estimated separately.

TaskShareAIPoints
Campaigns, CRM and the donor letter.
Estimate

No public source provides a precise figure. This is our estimate.

16%48%+7.7
The meeting, the no, and asking again.
Estimate

No public source provides a precise figure. This is our estimate.

18%14%+2.5
Events, legacies and the member base.
Estimate

No public source provides a precise figure. This is our estimate.

16%36%+5.8
Transparency, the annual report and what you can say.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
The major donor, the board and the conflict of interest.
Estimate

No public source provides a precise figure. This is our estimate.

18%18%+3.2
That they give again, and not spending more than comes in.
Estimate

No public source provides a precise figure. This is our estimate.

16%12%+1.9
Total100%26%

Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low

Skills and activities

  • raise funds
  • donor campaigns
  • member CRM
  • ask for legacies
  • run events
  • transparency report
  • major donors
  • keep members

Sources for this job· O*NET 13-1131.00· ESCO/ISCO 2432

Backend developer

Where the time goes

Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.

The time saving for each task is estimated separately.

TaskShareAIPoints
Endpoint, the contract and the test.
Estimate

No public source provides a precise figure. This is our estimate.

18%48%+8.6
Spike, the queue and the one that drops.
Estimate

No public source provides a precise figure. This is our estimate.

16%40%+6.4
Key, the secret and not leaving it in the repo.
Estimate

No public source provides a precise figure. This is our estimate.

16%22%+3.5
Migration, the rollback and not improvising in prod.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
Product, the deadline and not cutting the one that matters.
Estimate

No public source provides a precise figure. This is our estimate.

18%14%+2.5
That it takes the spike, and not leaving the key.
Estimate

No public source provides a precise figure. This is our estimate.

16%12%+1.9
Total100%27%

Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low

Skills and activities

  • endpoints
  • API contracts
  • queues
  • secrets
  • migrations
  • rollback
  • backend tests
  • write server code

Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2512

Analyse my job

Jobs with similar scores

  1. 237University tutor27%
  2. 238Credit analyst26%
  3. 239Librarian26%
  4. 241Ship agent26%
  5. 242Financial controller26%
  6. 243Drafter26%