RooflineOS: a season is the unit of work
July 30, 2026
A holiday lighting company sells between August and October, installs between October and December, takes it all down in January, and spends the rest of the year recovering and preparing. Almost every piece of software sold to contractors assumes a business that looks roughly the same in March as it does in November. That assumption is where the takedown booked in October gets lost in January.
One job, two visits, one season
In RooflineOS an install and its takedown are sold, scheduled, and closed as a single seasonal job rather than two disconnected visits. That sounds like a small modelling decision. It is the entire product. When the season is the unit of work, the takedown cannot be forgotten, because it was never a separate thing that could be forgotten — it was always part of the job you already sold.
The calendar the product models runs the way the year actually runs: pre-sell, design and quote, the install rush, lit and paid, takedown, then close the books. Crews stand up in October and stand down in January, and the roster, skills, and payroll have to tolerate that rather than fight it.
Priced before the truck moves
The wedge is the estimate. Satellite measurement produces linear feet, linear feet produce the price, and the price goes out on an approval link — with no first-visit truck roll to measure a roof someone may never buy. During a ten-week rush, the drive time you don’t spend measuring is the capacity you get back.
The homeowner doesn’t create an account to approve it, and doesn’t create one to pay either. Asking a customer to register before they can give you money is a reliable way to not get paid.
The season is financially inverted, too
- Materials and labour are paid for months before the customer pays — working capital runs backwards.
- Most of your inventory spends the season on other people’s houses, and some of it doesn’t come back.
- Weather rewrites the schedule overnight, without asking.
- Labour is seasonal by definition, so the systems around it have to be seasonal as well.
Every feature states its status, publicly
Twenty-nine capabilities are catalogued. Five are live, fourteen are in beta, and ten are roadmap — and each one says which it is, on the marketing site, where a buyer can see it before they talk to me. Roadmap features are excluded from pricing tiers by rule, so you cannot accidentally pay for something that doesn’t exist.
This is a deliberate position, not a temporary artifact of being pre-launch, and it stays after launch. The category is full of software that oversells to someone standing on a roof. There are no customers yet, so there are no testimonials or case studies here, and the price points are illustrative pending the beta. When there is proof, I’ll show proof.
The takeaway
If your business runs on a season, software that models a month will keep losing the things that span one. Model the season, price before the truck moves, and say plainly which features exist today.
Capabilities this touches