Fire & safety expertise, built into software
Your codes, drawings and engineering judgement, turned into purpose-built software. Fifteen specified workflows across the fire lifecycle — each one stops where a named engineer decides.
Estimator, specialist fire contractorWe recount sprinkler heads every time the drawings are revised. We need a take-off we can defend, sheet by sheet.
-
Requirements agentBRD with sheet, zone and dedupe rulesQueuedWorkingDoneSign-off
-
Design agentEstimator review queue, BOM screensQueuedWorkingDoneSign-off
-
Build agentSymbol extraction, dedupe, releaseQueuedWorkingDoneSign-off
-
QA agentTests from acceptance criteriaQueuedWorkingDoneSign-off
-
Deploy agentYour cloud, SSO enabledQueuedWorkingDoneSign-off
In one paragraph
DeX is Colakin’s agentic AI software development platform. For fire & safety it has been used to specify fifteen software workflows covering the lifecycle from tendering through engineering, delivery and commissioning to service and management reporting. Each workflow assembles evidence, retrieves source clauses and surfaces conflicts — and each one stops at the point where a named engineer decides. The software never determines compliance and never stands in for an authority.
- Workflows specified
- 15, each with its own requirements document
- Lifecycle stages
- Tendering to service and management
- Markets configured
- Australia, USA, UK, UAE, Singapore
- Build claim
- ~1/10th time, ~30% of traditional cost
Built for teams who keep people and buildings safe
- Fire protection consultants
- Specialist fire contractors
- Design and build contractors
- Fire services maintenance
- Asset owners and facilities
One map, six stages, fifteen workflows
The lifecycle as your business actually runs it. Every workflow has a requirements document behind it.
Pre-Sales & Tendering
Engineering & Design
Design, continued
Service & Management
Pick the one costing you the most
Filter by who feels the pain. Every card opens the full use case, flow and limits.
AI Fire Design & Engineering
Drawings and specs in. An evidence-linked design basis out.
Intelligent Drawing Review
Candidate clashes pinned to sheet, revision and coordinate.
Code & Specification Compliance
A clause-by-clause matrix. The reviewer decides, never the software.
Product & Equipment Selection
Certification scope as a hard filter, not a footnote.
Quantity Take-Off & BOM
A bill of materials where every line shows its sheet and zone.
Estimation & Costing
Every rate carries its source, so price changes explain themselves.
Customer-Ready Quotations
An approved estimate becomes a branded offer, exclusions checked.
Value Engineering
Every alternative passes a compliance gate before it is costed.
Engineering Drawing Automation
Draft placement against approved criteria. The designer accepts.
Technical Submittal Automation
Superseded certificates caught before the package goes out.
Procurement & Project Intelligence
Each shortage tied to the site milestone it actually moves.
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.
Management & Operational Intelligence
One trusted view. Every figure opens to its source.
Five buyers, one map
Who uses which workflow. A fire engineer and an estimator do not have the same bad day.
Swipe to see the whole diagram
See a workflow step by step
Every one starts from your documents and stops at a named approver.
Quantity Take-Off & BOM
A bill of materials where every line shows its sheet and zone.
Who’s involved
-
01
Estimator
Set the drawing scale
Established per sheet so lengths and counts mean something.
-
02
Automated
Extract symbols and segments
Devices counted, pipe runs measured, each tied to its sheet and zone.
-
03
Automated
Deduplicate across sheets
Devices appearing on two overlapping sheets are caught rather than counted twice.
-
04
Estimator
Verify the quantities
The estimator reviews by zone and system, with the basis of every line visible.
Estimator verifies the quantities?
Yes BOM released to purchasingNo Lines queried and re-measured -
05
Estimator
Release a traceable BOM
Exclusions and review status carried through to purchasing.
-
Output
What lands at the end
A traceable item and quantity list by sheet, zone and system, showing the count or length basis for every line, plus exclusions and review status.
Testing & Commissioning Assistant
Handover evidence assembled as you test, not afterwards.
Who’s involved
-
01
Engineer
Select procedures
The right test sheets for the systems actually installed.
-
02
Engineer
Capture field results
Readings and photographic evidence recorded where the test happens.
-
03
Automated
Check thresholds
Results measured against the acceptance criteria, with failures raised immediately.
Result within the threshold?
Yes Test passedNo Defect raised, retest scheduled -
04
Engineer
Manage defects and retests
Each defect tracked to closure with its retest evidence attached.
-
05
Witness
Record witness approval
A record without a witness signature stays pending. It does not quietly pass.
-
Output
What lands at the end
Test sheets, a deficiency log, the retest trail, a signed commissioning report and a handover evidence manifest.
Site Inspection & Maintenance
The client report comes from the record the technician signed.
Who’s involved
-
01
Supervisor
Assign the visit
Site, regime and scope allocated to a technician with the history attached.
-
02
Technician
Identify assets
What is actually on site, matched to what the record says should be.
-
03
Technician
Capture field evidence
Findings and photographs recorded against the asset, on site.
-
04
Technician
Classify defects
Severity and corrective action, consistently, not by individual habit.
Defect found?
Yes Classified with a corrective actionNo Asset passes, next service set -
05
Supervisor
Produce a reviewed report
The client report generated from the signed record, then reviewed.
-
Output
What lands at the end
A signed inspection record, defects with photographic evidence, a corrective action list and a client service report.
Less rework, more evidence
The manual steps around your existing CAD, estimating and service systems.
From requirement to live software
A specialist agent handles each stage. You approve the outputs that matter before the next one starts.
- 1
Describe
Your process, sites and standards, in plain language.
- 2
Requirements
BRD with user stories and acceptance criteria.
You approve - 3
Wireframes
Screens for field, office and reviewer roles.
You approve - 4
Build
Working code, data model and integrations.
- 5
Test
Automated QA against every acceptance criterion.
- 6
Deploy
Into your cloud or on-premise.
You approve - 7
Support
Changes as standards and sites evolve.
Your safety data stays yours
Deploy where you need
Cloud, on-premise or customer-managed networks.
Privacy-first AI
Sensitive details are processed in isolation during generation.
Full audit trail
Every sign-off and change is timestamped and attributable.
Connects to what you run
ERP, CAD, service and document systems through APIs.
Configured for the market you work in
Standards are examples only. Nothing applies to your projects until you confirm it.
Australia
- Sprinklers
- AS 2118.1
- Inspection & testing
- AS 1851
- Authority
- Building surveyor
United States
- Sprinklers
- NFPA 13
- Inspection & testing
- NFPA 25
- Authority
- AHJ
United Kingdom
- Sprinklers
- BS EN 12845
- Inspection & testing
- BS 5839
- Authority
- Building control, golden thread
United Arab Emirates
- Sprinklers
- UAE Fire & Life Safety Code
- Inspection & testing
- Civil Defence maintenance
- Authority
- Civil Defence
Singapore
- Sprinklers
- SS CP 52
- Inspection & testing
- SS 575
- Authority
- SCDF
Meet Kathir
“The goal isn't to replace expertise with AI. It's to put expertise at the centre of what AI helps build.”
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.
From a question to a pilot, in five steps
Nothing hidden behind a discovery call. Stop at step one and keep the document.
- 01
You ask for the requirements document
The full BRD for the workflow you care about, sent as written.
Same day - 02
A ten-minute wireframe walkthrough
A clickable prototype of that one workflow.
10 minutes - 03
The Fire Fit Check
Five questions: fit, hours lost, who approves spend, whether your documents can be shared, and timing.
One call - 04
A scope built on your rules
Your standards, your document formats, your approval gates.
Within a week - 05
A pilot against your own baseline
One workflow, your data, your engineers.
Q1
Fire & safety software, answered plainly
What is DeX?
Does DeX decide whether a fire design or installation complies?
How much time or cost will these workflows save us?
Do we have to take all fifteen?
Which codes and standards are supported?
How is this different from our CAD, estimating or service software?
Can we see the actual requirements?
Which markets do you work in?
Start with the one workflow costing you the most
Tell us which part of the lifecycle hurts and we send the requirements document for it. If none of the fifteen fits, we say so.
- The requirements document, usually the same working day
- A ten-minute wireframe walkthrough with the people who specified it
- No claimed percentage saving — your pilot measures it