Menova
العربية
Schedule a meeting
Menu

Courses

AI for Automation is a two-day programme from Menova for operations, finance, HR and administrative teams, taught by Ahmed Amrousy. It takes the recurring work a department repeats every week and rebuilds it as documented AI workflows the team owns and can hand over — with no coding required. It runs on-site in Egypt, Saudi Arabia and the UAE, or live online.

Last updated:

Stop doing the same task twice — turn recurring work into systems the team owns.

Most “AI adoption” never reaches the second week

An individual discovers a useful prompt, uses it for a fortnight, then reverts. Nothing is written down, nothing is owned, and the department’s actual throughput never changes.

AI for Automation treats recurring work as a systems problem rather than a personal-productivity one. The output is not enthusiasm — it is documented workflows with named owners.

What gets built

Participants map their department’s recurring work on the first morning and rank it honestly. Frequently a third of what a team wants to automate turns out to be work that should simply stop. What remains gets rebuilt, tested and documented well enough that a new joiner could run it.

The verification discipline

An automated process that is wrong 5% of the time and unchecked is worse than the manual one it replaced. A full module is spent designing the check that catches the specific error the department can least afford, and drawing the line where a human must decide.

What you leave with

  • Map the recurring work in your department and rank it by what is worth automating
  • Rebuild at least five real processes as documented, repeatable AI workflows
  • Write workflow documentation clear enough that a new joiner can run it unaided
  • Build the checks that catch a wrong output before it reaches a customer or a ledger
  • Know precisely where automation must stop and a human must decide

Programme outline

01

Finding the work worth automating

  • Mapping a department's recurring tasks in ninety minutes
  • The frequency × duration × error-cost ranking
  • Why the most annoying task is rarely the most valuable one to automate

02

The anatomy of a reliable workflow

  • GCSE-F as the specification format for a repeatable process
  • Inputs, source of truth, expected output, failure behaviour
  • Making a workflow reproducible by someone who did not build it

03

Building, live

  • Document handling — extraction, summarisation, comparison, reconciliation
  • Reporting and recurring correspondence
  • Each participant builds and tests workflows for their own processes

04

Verification and controls

  • Chain-of-verification built into the workflow, not bolted on afterwards
  • Designing the check that catches the error you can least afford
  • Data boundaries: what may never leave the organisation

05

Handover and ownership

  • Documenting workflows so they survive the person who wrote them
  • Establishing who owns, reviews and retires a workflow
  • A 30-day rollout plan for the department

Who it is for

  • Operations and shared-services teams
  • Finance, procurement and administration
  • HR teams handling high-volume recurring correspondence
  • Any department where the same task is repeated weekly

Frequently asked questions

Does AI for Automation require coding?

No. The programme is built for operations and administrative teams with no technical background. Workflows are constructed in the AI tools the organisation already has, and documented in plain language.

What kind of processes can be automated this way?

Document-heavy recurring work: extraction and summarisation, comparison and reconciliation, recurring reports, standard correspondence, meeting notes to action lists, and first-pass review of submissions. Anything repeated weekly and dependent on reading text is a candidate.

How is this different from buying an automation platform?

A platform gives you software. This gives the team the judgement to decide what should be automated and the discipline to document it. Many participants find that a third of the processes they wanted to automate should instead be eliminated.

What does the department actually leave with?

A ranked map of its recurring work, at least five workflows built and tested on real processes, written documentation for each, and a named owner and review cycle.

How do you stop an automated workflow producing a wrong result?

Verification is designed into the workflow rather than added afterwards. A full module covers building the specific check that catches the error the department can least afford, and identifying the decisions that must stay with a person.

How long is the programme?

16 hours across two days. Operations teams frequently prefer four half-days so that cover can be maintained.

What does it cost?

Pricing is set per client against team size, duration and city. Email ahmedamrousy@aucegypt.edu with your department size and the processes you have in mind for a written proposal within two working days.

Talk to Ahmed

Every Menova programme is scoped to the client. Book a short call — or send the team size, seniority and objective — and you get a written proposal with agenda, duration and price within two working days.

Schedule a meeting WhatsApp LinkedIn