# Business systems owner

> The person who owns the system the business runs inside — the CRM or order system: how the process is shaped in it, whether its records still mean anything, and what the numbers coming out of it are allowed to claim.

Page: https://flyvolo.ai/en/careers/business-systems-owner
Impact index: 52/100 · confidence Low confidence · assessed 2026-09-11
This is not a probability of losing a job.

## Scope

The internal owner of a company's CRM, order or workflow system — often called sales ops, revenue operations or business systems, and in smaller firms simply the CRM team. Not the vendor's support desk, and not a software engineer building the product the company sells: this role configures, governs and explains a system somebody else built.

## Tasks

### Shaping the process inside the system

- Direction: Being augmented
- Basis: evidenced (verified records attached)
- Why: Building the configuration got much cheaper: describing a workflow in words and getting the objects and automations back is squarely what these tools do. Knowing which of the described steps is the one people actually skip, and why, did not — that is learned by watching the team, not by reading the process document.
- What this does NOT establish: Faster configuration means more configuration, not less work. Every rule added is a rule that will later be wrong and have to be found — so the role's hours move from building to untangling, and untangling is invisible on a roadmap.
- Records:
  - 2026-04-01 · Deployment · Census BTOS supplement: 16% of AI-using US firms replaced existing software or equipment with AI-integrated solutions — https://flyvolo.ai/en/changes/ev-20260401-business-systems-owner-3 (source: https://www2.census.gov/library/working-papers/2026/adrm/ces/CES-WP-26-25.pdf)

### Keeping the records worth trusting

- Direction: Automating
- Basis: evidenced (verified records attached)
- Why: Matching records that refer to the same real thing is entity resolution, and it is one of the clearest places current models beat rules — they handle the messy cases string matching never could. Deciding which duplicate survives when the two disagree on a number that matters is still a business call.
- What this does NOT establish: Cleaner data makes everything downstream more trustworthy, which is the point — and it also removes the only visible artefact of this job. Nobody notices records that were never wrong, so the work reads as an absence, which is a poor position when the budget is set.
- Records:
  - 2025-10-06 · Deployment · The UK Ministry of Justice links and deduplicates people's records across prison, probation and court case systems with a probabilistic model in production, having judged rules unsuitable — https://flyvolo.ai/en/changes/ev-20251006-business-systems-owner-4 (source: https://www.gov.uk/algorithmic-transparency-records/moj-splink-master-record)
  - 2024-08-01 · Policy mandate · The EU AI Act requires a deployer that controls a high-risk system's input data to ensure it is relevant and sufficiently representative (Article 26(4)), from 2 December 2027 — https://flyvolo.ai/en/changes/ev-20260802-business-systems-owner-1 (source: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02024R1689-20260727)
  - 2023-02-01 · Deployment · US immigration agency USCIS reports a machine-learning model, deployed since February 2023, that decides which case records from seven systems belong to the same person; false matches go to staff — https://flyvolo.ai/en/changes/ev-20230201-business-systems-owner-5 (source: https://github.com/ombegov/2025-Federal-Agency-AI-Use-Case-Inventory/blob/3c225ba8438e48306ace7698c8c7feb9486cbc69/Data/2025_individually_reported_AI_use_cases.csv)

### Deciding what the system may decide alone

- Direction: New task
- Basis: evidenced (verified records attached)
- Why: When the system only stored what people did, this decision did not exist. Now that it acts, someone has to set the boundary, and the person who understands both the configuration and the business consequence is this one. The duty arrived with the capability and was assigned to nobody.
- What this does NOT establish: Setting the boundary is not the same as being allowed to hold it. This role usually has the knowledge and not the authority: when sales wants the automation to send more, the person who can say no is further up, and being overruled repeatedly is how the boundary erodes without any decision ever being recorded.
- Records:
  - 2026-04-30 · Constraint · China's cyberspace regulator reported 868 filed generative AI services and 530 registered applications as of 30 April 2026, and requires every live application to display which filed service it uses — https://flyvolo.ai/en/changes/ev-20260430-business-systems-owner-2 (source: https://www.cac.gov.cn/2026-05/13/c_1780413225190669.htm)
  - 2026-04-01 · Deployment · Census BTOS supplement: 16% of AI-using US firms replaced existing software or equipment with AI-integrated solutions — https://flyvolo.ai/en/changes/ev-20260401-business-systems-owner-3 (source: https://www2.census.gov/library/working-papers/2026/adrm/ces/CES-WP-26-25.pdf)
  - 2024-08-01 · Policy mandate · The EU AI Act requires a deployer that controls a high-risk system's input data to ensure it is relevant and sufficiently representative (Article 26(4)), from 2 December 2027 — https://flyvolo.ai/en/changes/ev-20260802-business-systems-owner-1 (source: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02024R1689-20260727)

### Making the numbers mean something

- Direction: Automating
- Basis: evidenced (verified records attached)
- Why: Writing the query and drafting the commentary are both commodity now. LinkedIn put a plain-language query tool in front of hundreds of staff across its business units precisely because data experts were spending much of their time fetching numbers for colleagues — and it only worked once experts had written down what each key table means.
- What this does NOT establish: Self-service reporting does not remove the person who knows the number is wrong. It multiplies the number of people confidently quoting a figure whose caveat they never saw — so the work shifts from producing reports to correcting them in meetings, which is slower and harder to defend as a headcount.
- Records:
  - 2024-12-09 · Deployment · LinkedIn deployed a text-to-SQL assistant used by hundreds of employees across its business verticals, saying data experts had spent much of their time helping colleagues find data — https://flyvolo.ai/en/changes/ev-20241209-business-systems-owner-6 (source: https://www.linkedin.com/blog/engineering/ai/practical-text-to-sql-for-data-analytics)

### Getting the team to use it properly

- Direction: Still human-led
- Basis: evidenced (verified records attached)
- Why: In-product help and assistants answer the how questions. They cannot answer the why-should-I question, which is the one that actually determines whether the field gets filled — and that answer requires knowing what the person is measured on and being able to change it. When two governments rolled out an AI assistant, use depended on the attitudes of staff's teams and managers, and fell short where people had not been taught; the tool did not bring itself into use.
- What this does NOT establish: This is the first task cut when the role is under pressure, because it produces nothing shippable. Cutting it does not show up as a problem for two quarters, and then shows up as data nobody trusts — by which time the cause is no longer attributable.
- Records:
  - 2024-12-30 · Pilot · A UK department's evaluation of a 1,000-licence Copilot pilot found that team and line-manager attitudes shaped how much staff used the tool, and self-led training beat formal sessions — https://flyvolo.ai/en/changes/ev-20241230-business-systems-owner-7 (source: https://assets.publishing.service.gov.uk/media/68adbe409e1cebdd2c96a19d/dbt-microsoft-365-copilot-evaluation.pdf)
  - 2024-08-23 · Pilot · Australia's Treasury found staff in its 14-week Copilot trial used the tool less than expected, citing high initial expectations, technology limits and a lack of education and training — https://flyvolo.ai/en/changes/ev-20240823-business-systems-owner-8 (source: https://evaluation.treasury.gov.au/sites/evaluation.treasury.gov.au/files/2025-02/evaluation-generative-artificial-intelligence.pdf)

## How to cite this

- The unit is the task, not the job title: say which tasks are changing and which are not.
- Carry each task's basis and its limits with it; an inferred judgement is not a finding.
- This page gives no number of years. Do not derive one from it.
- More: https://flyvolo.ai/llms.txt