Kathir
Fire & Safety Industry Business / Technology Expert
Kathir brings more than eighteen years in fire & safety into the DeX programme. His job is not to describe the industry to engineers — it is to make sure the software being specified matches how the work is actually done on site, in the office and at handover.
Who Kathir is
Kathir is a fire & safety industry business and technology expert with more than eighteen years in the industry, working with Colakin on the DeX fire & safety programme. His role is to make sure each specified workflow matches how the work is actually done — on site, in the design office and at handover — and to hold the line on what the software must never claim to do.
- Industry experience
- 18+ years in fire & safety
- Focus
- Commissioning, inspection, asset history
- Markets
- Australia, United Kingdom, United States, United Arab Emirates
- Workflows led
- 12 · 13 · 14 (Commissioning & Service)
AI is only as good as the expertise behind it
The hard part is not having the knowledge. It is connecting it to software without losing what makes it trustworthy.
The goal isn't to replace expertise with AI. It's to put expertise at the centre of what AI helps build. Kathir — Fire & Safety Industry Business / Technology Expert
Expertise sets the requirement
Every one of the fifteen workflows started as a business requirements document written around real fire & safety practice, not around what a model happens to be good at.
The engineer keeps the decision
The approval gate is in the requirements, not bolted on afterwards. Software that quietly decides compliance would be worse than the spreadsheet it replaced.
Refuse the numbers you haven't earned
None of the fifteen workflows carries a claimed percentage saving. Benefits get measured in a pilot, against your baseline, or they don't get claimed.
Standards are local
AS 1851 in Melbourne, NFPA 25 in Houston, BS 5839 in Manchester, Civil Defence maintenance in Dubai. The requirements treat every standard as an example until a client confirms it.
The three workflows closest to the field
Eighteen years of commissioning, inspection and service work sit behind these. Read them first if your pain is after installation.
Testing & Commissioning Assistant
Handover evidence assembled as you test, not afterwards.
Site Inspection & Maintenance
The client report comes from the record the technician signed.
Digital Asset & Maintenance History
One device, one timeline, a source behind every entry.
Ten minutes, one workflow, real questions
A clickable wireframe with the person who specified it, not a capability deck.
- 1
Your workflow today
You describe the manual steps. If none of the fifteen fits, we say so.
00:00 - 2
Click through the wireframe
Extraction simulated, labelled as demo data throughout.
02:00 - 3
Where your standards plug in
Your regime, your report format, your approval gates.
06:00 - 4
What it refuses to do
The approval gate, the compliance limit, the out-of-scope list.
08:00 - 5
Fit check, or an honest no
Not a fit is a fine outcome, and we will tell you.
10:00
What this software will not do
Life-safety work. These limits are written into the requirements, not added as a disclaimer.
It does not decide compliance
The software assembles evidence, retrieves source clauses and shows conflicts. It does not determine whether anything complies. A named engineer does.
It does not stand in for an authority
An approval recorded in the software never implies consent from an AHJ, Civil Defence, building control or a building surveyor.
Nothing leaves without a named reviewer
Every output carries who approved it. Anything unverified keeps a draft marker until someone signs it.
It does not do sealed engineering
Hydraulic network calculation, definitive sprinkler layout, sealed design, BIM geometry authoring and final cost estimates are all out of scope by design.
Your standards, not ours
NFPA, EN, BS, ISO, FM, UL, LPCB and Civil Defence appear in the requirements as examples. None is assumed to apply to your projects until you say so.
That is a claim about how fast Colakin builds software with DeX, and it is supported by delivered projects. It is not a claim about what any of these fifteen workflows will save your business. The requirements deliberately leave that to a pilot, measured against your own baseline.
Working with Kathir
What does a fire & safety expert do on a software programme?
Which workflows does Kathir lead?
Can I talk to him directly about our workflow?
Is DeX a fire & safety product?
Bring a workflow to the walkthrough
Ten minutes with the people who wrote the requirements. Bring the process that costs your team the most time.
- A clickable wireframe of one workflow, labelled as demo data
- The requirements document afterwards, whether or not you proceed
- An honest ‘no’ if none of the fifteen fits what you do