Back to Blog

Bring One Real Workflow, Not a Wishlist: How to Prepare for an Agentic AI Course

By | Published | Updated | 7 min read

Two figures in dark suits, seen from behind, study a single glowing silver path on a glass sheet; unused dim path sheets lie farther along the dark table

On 13 November 2026, The Straits Times published a feature on the winners of the inaugural SME AI Impact Awards, organised by the Infocomm Media Development Authority and the Singapore Business Federation. One of the firms recognised, with the SME Adoption Excellence Award, was You Tiao Man, a wholesaler of you tiao and traditional Asian snacks.

Its founder, Audrey Chew, told the paper the problem "was never the volume. It was six different formats", with different names, prices and pack sizes for the same product, arriving through channels that could not speak to each other. The outcome she stressed was a team that could run the work themselves: staff who "can now read an automation flow, write a good prompt and fix a broken step themselves instead of waiting for a vendor."

That is a useful starting point if you are deciding whether to sign up for an Agentic AI course. You will get more from the days in the room if you arrive with one real, messy workflow and enough detail to practise on it, rather than a list of tools you want to try.

This post is a prep guide for that. It is about choosing the work and mapping it before class, not about writing the brief an agent will follow. If you already have a workflow in mind and need that next step, see Write the Brief Before You Build the Agent.

Choose one workflow you already live with

A good practice workflow has four traits.

It happens often. Weekly or daily work gives you recent examples. A process that runs twice a year is harder to check against reality.

It already has rules. There is a usual path, and a set of exceptions people already know. Rule-heavy work is easier to talk through than work that is mostly taste or negotiation.

It is painful enough to be worth the time. If nobody would notice an improvement, class time will drift toward interesting tools instead of the job.

It is safe enough to practise on. Leave aside your most sensitive process: payroll, a live payment run, or a customer file you could not share even in anonymised form. You want something real, not something that would hurt if a practice pass went wrong.

You do not need the most strategic workflow in the business. You need one you can describe honestly, including where it breaks. If you find yourself saying "it depends" at every step, that is not a reason to abandon it. Those gaps are useful. They show you what still lives only in someone's head.

A wishlist of tools is a poor substitute. "I want to try an agent for email, invoices, the CRM and reporting" is several pieces of work, not one. Pick one, and leave the rest for later.

Sketch it on one page

Before the course, write the workflow down on a single page. You are not writing a policy, and you are not writing an agent brief yet. You are making the work visible enough that you, and later a trainer or a teammate, can talk about the same job.

Use these headings:

  1. Trigger. What starts the work? A customer email, a supplier invoice, a form submission, a weekly cut-off?
  2. Inputs, and where they come from. Name the documents, systems and people involved. "The order" is not enough. Is it the online-store export, a message in a chat app, a PDF in an inbox, or all three?
  3. Handoffs. Who touches it after the trigger, in what order, and what do they pass on?
  4. Approvals. Who can say yes, to what, and at which point? "A manager checks it" is too vague. "The finance lead approves before anything is posted" can be checked.
  5. Common exceptions. The cases that break the usual path: missing data, a repeat customer, a price mismatch, a rush request. List the ones that already happen, not every case you can imagine.
  6. Proof of done. How would anyone tell the job is finished and done properly? Which record, which field or status, and who can see it?

If a heading is blank, that is the point of the exercise. Fill what you can from memory, then check two recent examples and mend the gaps.

Here is a short, illustrative sketch, not a client story. A distributor takes customer orders from an online store, a messaging channel and a retailer portal. The trigger is a new order in any of those three places. Inputs include the order itself, the product codes in the catalogue, and the delivery slot in the warehouse sheet. The sales coordinator consolidates the order; warehouse picks it; finance invoices it. The sales owner confirms an unusual discount; finance approves if the invoice does not match the order. Exceptions include a product name that does not match the catalogue, a split delivery, and a portal order that arrives twice. Done means the order is in the warehouse list, the invoice is in the finance system against the right customer, and the customer has a confirmation.

Your page will look different. It should. Use your own systems and your own role names.

What to bring on the day

Bring the one-page sketch. Bring two or three recent examples, with names, account numbers and anything sensitive removed. If the workflow uses a form, an invoice or a screenshot of a record, an anonymised copy is more useful than a perfect description.

Bring your laptop and a charger. A personal laptop is safer if your work laptop blocks app installs. A paid AI subscription is encouraged but not required.

Leave the rest behind: a catalogue of tools to evaluate, a ten-item transformation plan, and any document you would not be comfortable putting on the table in a classroom. You will get further with one workflow you can open and walk through.

A 20-minute exercise this week

You can do this before you decide to sign up.

  1. Write down three workflows you touch in a normal week.
  2. Against each one, ask: is it frequent, rule-heavy, painful, and safe enough to practise on? Cross out any that fail the last test.
  3. Pick one. Fill the six headings on a single page.
  4. Take two recent examples and walk them through the sketch. Note every point where you had to invent a step, guess a source, or admit you do not know who approves it.
  5. Write the owner's name, the approval points, and the proof of done in one sentence each.

If the page is still thin after twenty minutes, spend another ten with the person who actually does the work. Their exceptions list will be better than yours.

By the time you sit down in class, you should be able to say: this is the job, this is what starts it, this is where it usually breaks, and this is how we tell it is done. That is enough to practise on. The brief for an agent can come later.

Practise it in a classroom

If you want to work through a real workflow with guidance, Nexius Academy's next public run of Agentic AI-Driven Business Innovation for Productivity is on 14, 15 and 22 January 2027, 9am to 5pm, at Lifelong Learning Institute, Paya Lebar. It is a 3-day, in-person course. Registration closes on Thursday 7 January 2027. Details and official registration help are on the course page. Eligibility and final fees depend on official criteria.

If three days is more time than you can spare, a shorter 2-day Foundations course is also available.

Come with one workflow, not a wishlist. The mapping you do this week is the part that makes the class useful.

Sources

About the Trainer

Melverick Ng is Founder of Nexius Labs and Master Trainer at Nexius Academy. He has trained business teams and non-technical professionals to design practical AI workflows for sales, operations, and customer support.

Talk to a Course Advisor