SightKit was built by Mark and Stuart, two engineers with backgrounds in frontline maintenance and operational leadership.

Before writing software, they worked on North Sea oil platforms - high-hazard environments where safety, clarity, and consistency aren’t optional. Between them, they’ve delivered hands-on maintenance, fault-finding, risk assessments, permit support, work scope planning, and the day-to-day problem solving that keeps complex assets running safely.

Both progressed from technicians into supervisory roles for major operators. That shift brought responsibility not just for delivering work, but for the systems that control it: permits, risk assessments, work orders, safety observations, incident investigations, registers, and the documentation that sits behind every job.

Across sites and sectors, the same issue kept appearing: critical information was scattered. Spreadsheets, PDFs, email chains, shared drives, and disconnected systems all created friction. Good intent was there - keep people safe, keep work controlled - but the tools didn’t always make that easy.

SightKit was built to reduce that friction.

The goal was a single, flexible platform that matches how work actually happens: a digital toolbox of modules that can be used independently or combined into a wider system. Clear workflows, consistent records, and audit-ready traceability - without unnecessary complexity or forced processes.

Everything in SightKit is shaped by operational reality: what needs captured, when decisions get made, and how information should move from the frontline to supervision and management.

SightKit isn’t “tech for tech’s sake”. It’s practical software for safety and operations, built by people who’ve been accountable for both the work and the systems behind it.