VOLOVLOAutomation risk & transition, task by task
AskOccupationsMajorsBusinessFoundersChangesMethodSearch occupations, majors…中文
VLO
VOLO

Understanding how automation changes work — task by task, with the evidence shown and the uncertainty admitted.

AskOccupationsMajorsBusinessFoundersChangesMethodAboutRole diagnosisPrivacyTerms
© 2026 VOLO
Occupations
All occupations
AI / software
Translator / InterpreterBank tellerCopywriterCustomer service representativeAdministrative assistantSoftware tester / QA engineerGraphic designerParalegalVideo editorAccountant / BookkeeperMarketing specialistData analystJunior software developerHR / recruiterFinancial analystJournalistSales / account managerProduct / UX designerBusiness systems ownerLawyerPharmacistPartnerships / channel managerArchitectFirst-line manager / team supervisorSchool teacherRegistered nurseAI implementation lead
RPA / self-service
Operations coordinator
Robotics
Retail cashier / shop assistantWarehouse workerAssembly line workerChef / cookElectrician
Autonomous driving
Ride-hail / taxi driverTruck driverDelivery rider / courier
Majors
All majorsEnglish / Foreign languagesComputer scienceAccountingPsychologyJournalism / CommunicationFinance / EconomicsLawVisual communication designMarketingNursingBusiness administrationEducation and teacher training
Guides
Ask VOLOFor businessFor foundersRecent changesRole diagnosisMethod & evidenceAboutSearch
Enter as:I have a jobI am studyingI run a companyI am building something
On this pageWhat stays freeA worked exampleWhat is in itWhat it will not doHow to ask
Role diagnosis

Your roles, not the occupation

Everything on this site describes occupations in general. A company is not a list of occupations — it is a specific roster, in a specific market, doing a specific mix of tasks. Mapping that roster against this evidence, task by task, is work, and it is the only thing here that costs money.

What stays free#

All of it. There is no task judgement, no evidence record and no source link behind a payment, and there will not be.

36 occupations broken into tasks, 90 verified records with their sources, the majors, the recent-changes timeline, the method page, and both ways of asking — typing and calling. If a paywall ever appears over a task judgement, this paragraph is the thing to hold us to.

A worked example#

A made-up company — 22 people, B2B software. The company is hypothetical; every number below is computed from the same task judgements and records the rest of this site runs on.

RoleHeadsChange methodStays humanNew dutiesEvidence behind it
Sales / account manager42112/6 tasks · 1 records
Customer service representative32213/5 tasks · 4 records
Marketing specialist22113/5 tasks · 2 records
Junior software developer61213/5 tasks · 3 records
Product / UX designer21212/5 tasks · 2 records
Accountant / Bookkeeper12214/6 tasks · 3 records
HR / recruiter12213/5 tasks · 3 records
Operations coordinator23113/6 tasks · 1 records
Partnerships / channel manager1221none
The column that matters is the last one

For Partnerships / channel manager we have no verified record at all. That is not a gap we would paper over in a report — it would be written down as a blind spot, because a confident answer about a role we have no evidence for is worth less than none. Sales / account manager, Marketing specialist, Product / UX designer, Operations coordinator rest on one or two records each, which is thin, and the report says so next to the finding rather than in a footnote.

Across this roster the evidence points at 9 duties that automation created and that nobody is assigned to by default — usually the most actionable part, because it is work appearing rather than work leaving.

What is in the report#

  • Your roster resolved to occupations — including the ones that do not resolve cleanly, which is itself a finding about how your company names work.
  • Per role: which tasks should change method, which stay with a person, and which duties automation created. Each with its basis — verified record or platform inference — and what the judgement does not establish.
  • The blind spots, named. Roles where we have no evidence, and roles where the evidence is one record from a source with a stake.
  • One thing per role you can check inside your own company this week, without buying anything.

It is written against the same rules as the site, and the sources are all links you can open yourself. If you disagree with a judgement, you can go to the record and see what it rests on.

What it will not do#

These are the same refusals as the rest of the site, and they do not get relaxed because someone is paying:

  • It will not tell you who to make redundant, and it will not rank your people. It is about tasks, and tasks are not headcount.
  • It will not give you a readiness score, a risk percentage, or any single number for your company. A number is where people stop reading.
  • It will not tell you what your product, your org chart or your business model should become. That needs per-company workflow and cost data we do not have, and we will not guess it for a fee.
  • It will not recommend a vendor. Nobody pays to be in it, and nobody pays to be left out of it.

How to start#

This is new and it is not a checkout yet: there is no payment page, and the first few are being done by conversation so they get done properly before anything is priced. Send your role list — titles and rough headcount is enough, no names — and you will get back whether there is enough evidence to make a report worth buying. Sometimes the honest answer is no.

Send a role list

Analysis, not advice — the same terms as the rest of the site apply, and decisions about your company remain yours. Who makes this and who pays for it