Five Processes for the First Step in Automation
The criteria for the first process
Not every routine is ready for automation. Before choosing the first candidate, check four signs:
- Repeatability. The action happens regularly by the same rules — not once a quarter in a different way.
- Materials. There is input data: emails, meeting recordings, contracts, a database, notes. The agent works on materials, not on guesses.
- A verifiable result. The outcome can be opened and checked: a draft, minutes, an answer with quotes, a document.
- A responsible person. A designated employee confirms the result; this role keeps the automated flow accountable.
The same principles are defined in the engagement models: before launch the task, the input data, the expected artifact, the acceptance criteria, the limits and the person who makes the decision are defined.
Candidate 1: incoming email
The mail assistant determines the topic and priority of an email, highlights deadlines and commitments and prepares a draft reply in the accepted tone. It is useful when there is a large flow of typical incoming mail, a single tone of the team's replies is needed and deadlines must be tracked. A human confirms every message before sending.
Candidate 2: meeting minutes
The local meeting scribe transcribes the recording and compiles the summary, decisions, tasks and responsible persons. It suits internal meetings with sensitive data, regular status updates and interviews. In an approved fully local configuration, the recording is not sent to an external service; speaker names and decisions are checked by the person responsible for the meeting.
Candidate 3: search across contracts
The legal RAG navigator answers questions about the body of contracts and regulations with exact quotes and source references. Typical scenarios: finding clauses in a body of contracts, comparing revisions, preparing materials for the lawyer. The legal position is checked by the specialist in charge.
Candidate 4: questions about metrics
The database consultant translates a natural-language question into a query to the permitted PostgreSQL views and answers with an explanation of the calculation and a link to a source table. It takes the load of typical "how many", "what is the trend", "why did it change" questions off the analysts.
Candidate 5: preparation of requirements
The requirements analyst leads the materials from discovery to artifacts following GOST 19.201-78, GOST 34.602-89 and ISO 29148:2018, tying every requirement to a source. It is useful for teams for whom writing specifications is a regular process, not a one-off task.
If none of the five candidates fits your rules — that is an argument for an assessment before custom development, not a reason to automate an unstable process.
Adapted from the article: agentseffect.com.