About
Graftix was not designed in a workshop by people who have read about construction. It was written by a working contractor, on the back of jobs that were going wrong for entirely avoidable reasons.
The origin
Twenty-one years on the tools and running jobs in fire, security, electrical and data. Two decades of watching the same problems repeat on every single project.
Drawings printed at midnight. Device schedules living in a spreadsheet on one person's laptop. Certificates filled in with a biro and photographed badly. A WhatsApp group with four hundred unread messages containing the one answer somebody needed three weeks ago.
The tools that existed were either built for main contractors pouring concrete, or they were generic task apps that had no idea what an EICR was, let alone a cause and effect matrix. Nothing understood that the drawing is the single most important object on the job.
So Graftix got built. On real projects, against real deadlines, with the constant test of whether an engineer standing in a riser with cold hands would actually open it.
How we build
Every decision in the product gets tested against these. If a feature fails one of them, it does not ship.
The drawing comes first
If a feature cannot be reached from the plan, it is in the wrong place. The drawing is how this industry thinks.
Site conditions are the design brief
No signal, gloves on, one hand free, bright sunlight, dark plant room. That is the environment, so that is what it is built for.
No feature gates
Small firms have the same compliance obligations as large ones. Charging them extra for the paperwork that keeps them legal is indefensible.
Your words, not ours
Statuses and task types are renameable. Every business has its own language and the software should learn it, not the other way round.
Your data is yours
Exportable, in a region you choose, with tenant isolation enforced at the database rather than trusted to application code.
Trade-literate or nothing
If the product does not know what a loop, a riser, an EICR or a permit to work is, it is not built for this industry.
Where it runs
Graftix is used on campus infrastructure work spanning eighty-plus buildings, on commercial security deployments, and on small fit-outs run by two people in a van. The parent and child project structure exists because a real job needed it, not because it looked good on a roadmap.
The same is true of material pools, AI symbol takeoff and Graftix Live. Every one of them was written because a live project was being held up by the lack of it.
See what is in itGet started
Seven days, no card, every feature. If it does not fit how you work, you will know within a week and it will have cost you nothing.