Roofers: the weather moves the job. The record should not move with it.
A roof job is started, stopped by rain, restarted a week later and finished on a Saturday. Four visits, one price, and a paper trail that exists mostly as a series of WhatsApp voice notes.
Orbit is in development. Join the waitlist and we WhatsApp you when it opens.
sealed the valley on the fourways job. 2nd visit, rain stopped us tuesday
Added to Fourways — roof repair ✅
thats it, invoice it
Invoice #0077 drafted — R7,400.00. Tap to check and send.
ILLUSTRATIVE EXAMPLE
Where it goes
What costs a roofer money after the job.
One job, many visits
Because the work is spread across days that are chosen by the weather rather than by you, the job never has an obvious moment at which someone sits down and writes it up. So nobody does.
Emergency leak repairs are billed last
Storm work is urgent, unplanned and priced on the spot. It also arrives in clusters, five in a week, and by the following month you can no longer separate one from another.
Materials arrive on site, not through your hands
Sheeting and tiles are often delivered straight to the site. If the delivery note does not get attached to the job on the day, the cost surfaces weeks later on a statement with no job attached to it.
What Orbit does about it
One message, at the end of the job.
Orbit is being built for work that happens in pieces. Each visit is one message — what you did that day, on which roof — and the job accumulates rather than waiting for a single write-up that never comes. When the last sheet goes on, the whole job is already written.
Storm weeks are the clearest case. Five leak repairs in four days, each one recorded as it is finished, means five invoices that can be drafted on the Friday instead of five arguments in September. The record is made while the detail is still in your head, which is the only time it is accurate.
Material deliveries can be logged the moment the truck arrives. Say what came and which roof it is for; the cost sits with the job instead of appearing on a supplier statement three weeks later attached to nothing.
What it keeps for you
- A job that survives being started, stopped and restarted
- Each visit recorded on the day it happened
- Deliveries logged against the roof they were dropped at
- Draft invoices ready the moment the job closes
Orbit drafts. You send.
Questions
Roofers ask us this.
Can one job run across several visits?
Yes — that is the shape roofing work has, so it is the shape Orbit is being built around. Each message adds to the same job rather than creating a new one, and the invoice is drafted from the whole thing when you say it is finished.
How do I handle emergency call-outs during a storm?
The same way as anything else: one line per job, sent when you come down. The value is that five repairs in a week stay five separate, correctly priced jobs instead of one blurred memory.
Can I log a delivery that went straight to site?
Tell Orbit what arrived and which job it was for and it holds the cost against that job. Reading supplier delivery notes automatically is a Vyso platform capability on the roadmap for Orbit, not part of the first release.
Does Orbit remind me to go back and finish a job?
Nudges for jobs that have been open a while are planned. Nothing on this page is a description of a shipped feature — Orbit is in development and the waitlist is how you hear when that changes.
Orbit for other trades
Orbit for roofers.
Orbit is being built now. The list is free, it commits you to nothing, and founding pricing is locked for the people on it.