Singapore · evening and weekend cohorts
Learnaieasily is a training studio in Tanjong Pagar. We run four-week and eight-week courses where you bring your own work — a report you write every month, a stack of customer emails, a forecast nobody trusts — and leave with a working, documented way to do it faster using current AI tools.
Our position
The assistants on your desktop will be renamed, repriced and rebuilt before the year is out. The jobs sitting under those tools move far more slowly. A monthly board pack is still a monthly board pack. A tender response is still a pile of clauses that must match last year’s bid. We organise every session around a task you already own, then pick the tool that currently does that task well enough for a non-specialist to run on Monday morning.
A syllabus built as a feature tour is stale in a quarter. Ours is built as a sequence of workplace jobs. You arrive with a file you are allowed to work on. We spend the first half hour making that file usable. The rest of the night is spent getting a first version of the workflow to run on it, then writing down the steps so someone else on your team could follow them without us in the room.
That written workflow is the thing we grade, in the informal sense. There is no exam. There is a document you can share: purpose, inputs, prompts or configuration, checks, and what to do when the model drifts. A certificate of attendance is issued at the end. The document is the part that still matters in March when the product names have changed again.
We opened in 2026 for people whose job titles have nothing to do with machine learning. Marketers, analysts, operations managers, teachers and owners of small firms sit in the same room because the method is the same. Bring the work. Leave with a way to do it that you can explain to a colleague.
Programmes
The starting course if you have not yet used a model on live work. You learn how to brief a tool, how to check its output, and how to keep a short library of prompts that match the documents you already write. By week four you have a repeatable method for one weekly task.
Full outline →For people who already open a chat tool every day and still get uneven drafts. We build writing systems: tone sheets, clause libraries, review passes and a simple version log so a first draft can be trusted enough to send to a manager.
Full outline →Aimed at anyone whose week lives in rows and columns. You practise cleaning a sheet, asking better questions of it, and building a checked summary that a colleague can rerun. Spreadsheet copilots are used as helpers, never as an unreviewed source of numbers.
Full outline →The longer track. You connect a small set of steps so a weekly job runs with less copying between apps. We stay with no-code builders and keep a human approval where the output leaves the building. Only take this after Foundations or Prompting.
Full outline →A private workshop for a team that already shares a set of documents and a policy. We scope the two or three jobs that waste the most hours, teach on those files, and leave the group with a shared prompt library and a one-page rule for what may be pasted into a model.
Full outline →4sessions in a short course
Cohort format
A weeknight runs two and a half hours. The shape does not change from Foundations through Automation. Only the file on your screen changes.
Recap and questions from the week’s homework. We look at what broke when you tried the method on a quieter Tuesday, and we fix the instruction that caused it before anyone opens a new tool.
Live teaching with the tool on the shared screen. One task, shown slowly, with the checks spoken out loud so you can hear what we refuse to accept from a model.
Lab time on your own file. Two of us walk the room. You are expected to work on something real. A fictional case is a last resort if your employer has blocked every document.
Group review of two people’s work. The point is not polish. It is to hear how someone in a different role solved the same kind of check, then steal the part that fits your desk.
Setting next week’s task. You leave with a written brief, a suggested time box of 60 to 90 minutes, and one thing you must not skip: the failure note when the output is wrong.
The room
People who write the monthly board deck, the campaign recap, or the customer email that currently takes a full afternoon. They come to stop starting from a blank page each cycle.
Staff who rebuild the same forecast tab or operations report every Friday. They want a checked method for cleaning a sheet and drafting the narrative that sits on top of the numbers.
Teams drowning in role ads, screening notes and offer letters. They practise templates that keep tone consistent and leave a human to make the decision that actually matters.
Classroom staff who need the same lesson in three ability bands by Friday. They work on differentiation packs and marking comments, with a hard rule about learner data staying off the public tools.
People who do the quoting, the stock check and the after-sales replies themselves. They leave with one automation that removes a weekly chore and a note on what still needs their eyes.
Colleagues who draft tender responses, briefing notes and roster plans under tight policy. They come to learn what can be drafted by a model and what must stay in a controlled template.
What you leave with
A saved set of prompts written for your own role, with a version note on each one. You will know when you last changed the instruction and what went wrong with the previous wording. The file is yours to take back to the team.
At least one short chain that runs on a file you brought. We will not count a demo sheet we invented. It may be as small as a weekly summary. It must be something you can restart without us standing behind the chair.
A plain record of what you will and will not put into a model. It names the data types you redacted in class and the approval step you will keep when an output is sent outside the team. Managers tend to ask for this first.
Ten minutes you can run on your own laptop. You show the before file, the steps, the check, and the leftover risk. The point is to make the work visible. A product-launch performance in a meeting room is not required.
Enrolment
Seats are held for five working days after we confirm a fit. If you already know the month you can start, say so in the form and we will answer with the open dates.