A knowledge base your team and your AI can both read. Obsidian and Claude, shown end to end.
Thursday 24 September 2026 · 9:00 to 10:30 PM · Google Meet

Chartered Accountant (ACCA · C.A.(M) · FCA Singapore) and MIA board member. Featured in Business Insider for pioneering AI inside the accounting profession.

Builds and ships AI workflows in the wild — Claude projects, MCP servers, multi-agent pipelines and data dashboards. Turns messy business problems into working AI solutions.

Drives AITraining2U's mission to equip 100,000 Malaysians with practical AI skills — hands-on with AI agents, automation and applied analytics for enterprise teams.

Founder of Urbanite Enterprise, an AI consultancy for Malaysian SMEs. Nineteen years of mission-critical network operations at Telekom Malaysia, now delivering Claude, n8n and multi-agent workflows in production.























I am going to show you a knowledge base that is actually running, tell you what it does for me, and point at how it is built.
What a second brain is, what it buys you, and where to start on Monday.
A step by step build. That is a two day class, and ninety minutes would do it badly.
Because the worst thing a session like this can do is promise a workshop and deliver a trailer. You should know which one you are in.
Electrical and electronic engineering, Imperial College London. Straight into Telekom Malaysia.
Eight years restoring international cables, ending as the manager of the restoration office.
Head of a quality unit through an ISO 9001 migration, then business control for the network operations centre.
Six years as an account manager for education customers, public universities and the ministry.
Left on a voluntary separation plan. Started again, with a laptop and one folder.
Back then I ran the office that restored all of TM's international cables. Best Manager, 2013.
Where the network is watched around the clock, and where nothing works unless the last person wrote it down.
Every job I did well depended on something someone wrote down. AI did not change that lesson. It made it pay ten times over.
AI agents as digital colleagues. My first AITraining2U class, and I was asked to show the room my own system.
Rapid prototyping. Building working apps by describing them, nine days later.
Agentic automation. Wiring assistants into the tools a business already runs on.
Invited to help teach the two day class, the biggest one yet. I taught the knowledge base and multi agent section.
The same material I am showing you tonight, taught hands on with the room building along.
The knowledge base and multi agent day, now on the class's trainer roster.
I talk to one assistant. It decides which specialist the work belongs to and briefs them.
Researcher, archivist, writer, reviewer and more. Each one is a note describing a job, with its own memory.
Every role reads from and writes to the same knowledge base. Without it, they are twenty strangers.
It is the clearest proof of tonight's point. The team is only as good as what is written down.
Nineteen years of documents and correspondence, searchable by meaning, not exact words.
Open source tools, 8GB of memory, and nothing leaves the machine.
Redrawn with AI from my June original. The numbers are June's. It has grown since.
Read in full and queried as one library. Every answer cites its source.
Explainers, slides and reports, made from the same grounded answers.
NotebookLM made this in one pass, and some of the small text is garbled. I left it that way on purpose. It is the best argument for checking I have.
You have those answers somewhere. The question is whether you can get them back in under a minute, and whether they survive the person who knew them leaving.
The file exists. Nobody knows which folder, which version, or which of the three copies is current.
The same vendor gets re-evaluated. The same policy gets re-written. Nobody calls it rework because nobody counts it.
Somebody remembers the number. Nobody can show where it came from.
Final_v2.docx Final_v2_REVISED.docx Final_v2_REVISED_use_this_one.docx notes.txt scratch.txt meeting (1).docx meeting (1) copy.docx
Everyone recognises this folder. That recognition is the whole problem.
Not an app you buy. A folder, a habit, and two rules.
--- type: vendor tags: [procurement, freight] --- # Lateral Logistics Offer: RM11.80 per unit, 12 month commit, NET30. Risk: only two depots. Ties into [[Q3-Targets]] Blocks [[Project-Atlas]]
Plain text on your own disk. No database, no lock in.
Ninety five thousand notes. I am not going to open it, and you would not want me to.
One point per note. It started as one folder and one habit, and nothing in it was planned.
I can still find anything in it in seconds, and so can the assistant. That is not because it is tidy. It is because it is linked.
Person, project, vendor, decision. One canonical note each, never three copies.
A note belongs to many topics. A folder only lets it belong to one.
So the assistant reads a map and follows two links.
One note after each meeting, a weekly tidy. The move that compounds.
If you have seven notes, structure buys you nothing. It starts paying at a few hundred, sooner than people expect.
Faster, because less is read. Cheaper, for the same reason. And more accurate, because the few notes it reads are the right ones.
You can check the answer. Which is the next thing I am going to show you.
Retrieval Augmented Generation. Scary name, simple idea: before the AI answers, it looks things up in your notes first, the way you would check a file before replying to your boss.
Without it, the AI is sitting a closed book exam: it answers from general knowledge and fills gaps with confident guesses. A tidy, linked vault is the book. Good notes in, good answers out.
A working vault, opened on screen. Everything in it is invented, so I can click anywhere.
The privacy control is which folder you point the assistant at, not which assistant you use. So tonight I point it at a copy where every client, project and person is fictional.
What did we agree with the cold chain client, and what has to happen before it is final?
The terms sit in one, the approval in another, the open action in a third. It has to follow the links.
Not "according to your files". The actual note, which I can open in front of you.
Agreed: the rate and terms in the scope letter, subject to two things. Before it is final: 1. the signed variation 2. finance clearing the cash impact Sources: [[Tanjung-Cold-Chain]] [[Decisions-Log]]
Illustrative shape. The live one is run on screen.
You forward the answer and the note. They do not have to trust you, and you do not have to remember.
Ask it something the vault does not contain and it should tell you so, rather than inventing something plausible.
The next person asks the same question and gets the same answer, with the same source.
None of this makes the assistant right. It makes the assistant checkable, which is a different and more useful property.
In anything that gets signed, a person still approves. The system does not remove that, and it should not.
One folder. One note after your next meeting. If you do that for a month and never open it again, you have lost an hour and learned something true.
Once the knowledge is written down, it stops being a filing exercise.
So the finance agent and the project agent never disagree about what was decided.
One client note serves sales and projects. Nobody keeps a second copy.
Tell me your department, and I will ask Claude for use cases, against tonight's fictional vault.
An original short film, eighty seconds, made with AI tools for this session.
Fifteen shots, each written down before anything was generated.
It is a fictitious Malaysian solar installer, invented for the film.
n8n is a trademark of n8n GmbH. This film is an independent work and is not affiliated with, endorsed by or sponsored by n8n GmbH.
Any other names, marks or brands appearing in it remain the property of their respective owners.
This is not a knowledge base. It is what the same habit of writing things down lets a small team do next.
A solar installer makes one wish. A team of assistants picks it up, hires the specialists it needs, and hands back something that works.
Every character in it is a written role. That is the same idea as a note: if you can write the brief, you can build the thing.
Yes it is a bit rough in places. It was made on a small budget of credits, by the team, as a piece of our own work rather than a client job.
The company in it does not exist.
Fifteen shots, each with its own note: what happens, what is said, what it must not do.
Nothing was generated until someone agreed what it would cost and what it was for.
Which caught things the people who made it could not see any more.
The film is an original work made for this session. Any names, marks or brands appearing in it are the property of their respective owners, and the company shown in the story is fictitious.
That was a fair instruction and I have kept to it. What I skipped is a two day class where you build it in the room, with your own files, and leave with it working.
For ops, finance and non technical teams drowning in repetitive work. Build no code agents for chatbots, reconciliation, OCR and reporting.
For Microsoft 365 organisations and IT governed teams. Governed agents across Word, Excel, Teams and SharePoint.
For power users and teams standardising on Claude. Claude Code, Cowork and multi agent systems mapped to your business.
For non technical founders and product managers. Build and ship working apps with Claude Code and vibe coding tools.
For developers, MLOps and data engineers. Production AI with Google ADK, RAG, MCP and agents, model agnostic.
Opens the booking form. Pick a course and a date.
Mastering Claude and Multi-Agent Orchestration, by AITraining2U. Two days, hands on, HRD Corp claimable.
Details and dates from Warren, right after this.