The client runs an established fire safety business spanning two distinct service brands. Their field engineers carry out dry riser inspections, wet tests, fire hydrant flow tests and remedial work across commercial sites, and every job ends with a formal certificate issued to the customer. Like a lot of small, hands-on businesses, they had grown into a workflow that worked but quietly cost them time every week.
The challenge
The certificate process was entirely manual and ran across several disconnected tools: engineers completed paper forms on site, the office retyped each one by hand into Word and Publisher templates, supporting information was tracked separately in spreadsheets, and finished certificates were printed, signed and posted. The retyping step was the real bottleneck — transcribing handwritten notes into a fiddly Publisher layout, with constant risk of typos and formatting drift, across nine different templates spanning two brands.
The approach
The project deliberately started slowly. Before writing any code, we ran a full discovery phase: analysing every existing certificate, mapping the real end-to-end workflow, and putting detailed questionnaires to the client. That groundwork stripped out assumptions that would have made the product worse — early on it looked like the app should handle "multiple hydrants per job" and "equipment tracking", but talking it through revealed certificates are printed individually and inventory features were never wanted. Cutting them kept the application lean and faithful to how the team actually works.
Now: one form in, finished certificate out
The solution
- Nine certificate types, two brands. Four in the first brand's Word style, five in the second's Publisher style — each rendered as a polished PDF matching the original layout precisely.
- Pixel-faithful output. The documents going out to customers look exactly as they always have, produced in a fraction of the time.
- No data re-entry. The team enters job details once and the finished, print-ready certificate comes out the other side.
- Deliberately simple. No login, no cloud dependency, no database to maintain — it runs locally on Windows.
- Considered, modern interface. A clean, Apple-inspired design that feels approachable to a non-technical user from the first session.
The outcome
The manual transcription step at the centre of the old workflow is gone. Instead of retyping handwritten notes into a finicky publishing template for every job, the team fills in one form and generates a finished certificate ready to print and sign — a consistent, professional document every time, with a noticeably faster turnaround and minimal training needed to adopt it. The business owns the tool outright, with nothing to subscribe to or maintain in the cloud.
“Client testimonial placeholder — drop in a quote here once you have one.”