People usually write to us with a handful of practical worries: whether they need to code, what happens if a sitting is missed, whether a certificate means anything, and how we handle a team of two. The answers below are the ones we give on the advisory call. If your situation is odd, write anyway; the form is read by a person.
Before you enrol
We would rather you ask a blunt question now than sit through a programme that does not fit the work you actually do. Aiacademysg starts with a twenty-minute conversation, then a written read-back; enrolment is a later step, and sometimes the honest recommendation is that you do not need a course yet.
These notes cover the questions that arrive most often. They are not a substitute for looking at the programmes or at how we teach. If you are bringing a whole team, the formats on For teams will be more useful than an individual seat.
If a question here does not match your case, use the form on the contact page. We reply from hello@aiacademysg.com within one working day.
Questions
You do not need to programme to sit with us. The programmes are written for people who already have a job and want a careful way to use assistants, transcription, table generation and drafts. We work in ordinary language and in the software you already open during the week. If a later task genuinely needs a developer, we will say so in the written read-back rather than stretch a short course to cover it.
Age is not a criterion for joining a cohort. Many participants have spent decades in operations, policy, finance or administration and want a calm account of what these tools can and cannot do. The sitting is paced so that everyone can practise, not so that we finish a slide deck. If you can describe a typical week of work, you have enough to begin.
Write to us as soon as you know you will miss a sitting. For a public programme we will try to seat you in the same session of a later cohort if a place is free. You still receive the workbook pages and templates for that evening so the artefact is not missing. A live discussion cannot always be replayed, so please treat attendance as part of the work you signed up for.
We issue our own certificate of completion when you have attended the sittings and submitted the short practice pieces we set. It is a record from Aiacademysg. It is not a government accreditation, and we will not describe it as one. Some employers keep it on file as evidence that you completed a structured programme. If you need a named public credential, mention that on the advisory call and we will tell you whether we are the right place.
Yes. Two colleagues often make more progress because they can test the same workflow against the same constraints. Please say so on the form so we can keep you in one cohort. If you are closer to a group of six or eight, look at the team formats rather than buying two individual seats. We will advise on that during the call.
We teach on widely available assistant models, transcription tools, and ordinary office software used for tables, drafts and simple automation. We do not bind the programme to a single vendor. You will need an account on the tools we agree after the advisory call; we will not ask you to purchase a stack before the task is clear. If your organisation already licences a particular assistant, we can work with that.
Public cohorts have eight to fourteen seats. The cap exists so that each person can bring a real task and we can look at it without turning the evening into a lecture. Team sittings are sized to the room and to the work; we will say if a group is too large to practise properly. If you prefer a quieter start, mention it on the call.
Plan for about two hours between sittings, sometimes less. The work is to try a template on a task from your own week and to bring back what happened, including where it failed. We do not set long reading lists. If the week is unusually heavy, tell the facilitator so we can adjust.
You may transfer a reserved place to a named colleague in the same organisation if you write to us before the first sitting. The colleague still has a short advisory call so we understand the work they actually do. We do not issue open tickets that can be passed around without that conversation. Fees already paid sit against the new name; we do not add a transfer charge.
A person reads what you sent and we reply from hello@aiacademysg.com within one working day. The reply is usually an invitation to a twenty-minute call, or a few questions if the note is too thin to go on. After the call we send a written read-back within two working days. We do not add your address to a mailing list.
Yes. We work with non-profit organisations on the same basis as other teams: a scoping conversation, then a format that fits the work and the size of the group. We do not advertise public subsidies, and we will not invent a grant pathway we do not run. If the budget is tight, say so early. A half-day clinic is sometimes enough, and a six-week cohort is sometimes more than you need.
No. We do not teach you to train or to fine-tune foundation models, and we do not run a path into machine-learning engineering. If a vendor promises that a two-day course will make you an AI engineer, that vendor is not us. Our scope is using existing assistants well, checking their output, and deciding when a process change is the better spend. We will point you toward other resources if model-building is genuinely what you need.
If these answers still leave a gap, book a twenty-minute advisory call. We will look at the work you actually do and tell you which programme, if any, is worth your time. You can also read the programme details or the notes on guidance first.