We install roofs.
And we write the software that goes with them.
FLINT is a roofing company first. We opened an Android workshop because the tools we were sold to track our own jobs did not survive contact with a roof.
Runs in your browser, nothing is sent. A rough estimate: an on-site survey is still needed.
One company, two trades
They do different work, on the same jobs. That overlap is what makes the second one useful.
Roofing
The original business. New roofs, renovation, zinc work, and everything that keeps water out.
- New roofs and full replacement
- Zinc work, gutters, flashing
- Waterproofing and weak-point repair
- Maintenance, moss removal, emergency callouts
Software
The Android workshop. Field applications built for a gloved hand and a missing signal.
- Trade applications for construction
- Offline by default
- Play Console release and compliance
- Rescue work on apps that grew heavy
CRM Toiture
The software we wrote for ourselves and then opened to other companies. Quotes, jobs, photos, scheduling: everything a roofer currently writes in a notebook that ends up soaked.
It runs without a signal. In a village, under a zinc roof or in a basement, the connection drops and the app keeps going. Data syncs when the network comes back.
A developer who has stood on a roof writes different software
That is not a slogan. Here is what it changes in practice.
Gloves
Our buttons are the size of a gloved thumb. Free text entry on a roof is a bad idea, so we use lists, buttons and voice dictation instead.
Signal
We lost enough measurements to a missing bar of reception that offline is not a checkbox in our apps. It is how they normally behave.
Time
No foreman fills in a twelve-field form in the rain. One photo and two taps is the budget we allow ourselves.
The quote
Sloped area, waste, overlap: our code applies the same rules as our own take-off sheet, because the same house writes both.
A roof to replace, or an app to write?
Both arrive in the same inbox, and someone from the team answers.
[email protected]