Roof asset management software for every roof you are responsible for.
Curbsight is roof asset management software for the manager of many roofs: a property-management company, a multi-site operator, an insurer's book, a commercial roofer's maintenance accounts. Every address in the register carries a roof age estimate with its source, its cumulative hail exposure, a storm history with dates and stone sizes, and the photos from the last inspection, and the register ranks itself by which roofs need attention first. When a storm lands, you know which addresses it touched the same day, with the claim window counting down per roof.
What roof asset management software has to do
A manager of roofs asks five questions, and the answers usually live in four places: a spreadsheet of addresses with a year someone typed in, a folder of inspection reports, a carrier's loss run, and a weather site. What do I own? What condition is each roof in, and how old is it really? What has hit it, and how hard? Which roofs need money this year and which can wait? And on which of them can I still file? Roof asset management software is one register that answers all five per address, and keeps answering when the next storm lands. That is what this page describes, and only what is in the product today.
The register: what every roof carries
Every address in a live market arrives with these on its card before anyone is sent to look at it. An inspection adds to the record; it never has to start it.
| On the card | Where it comes from | What a manager uses it for |
|---|---|---|
| Roof age estimate | Public property records, corrected by the last inspection or a permitted re-roof; the card shows which | Lifecycle: which roofs are inside their service life, which are past it, and how sure the estimate is |
| Cumulative hail exposure | Radar hail swaths, hit by hit, for this roof | Condition risk: hits since the roof went on, the largest stone it has taken, the last date |
| Storm history | NOAA storm data and radar hail swaths, per address | Every hail and wind event at this roof with its date and size, for the loss file |
| Claim window | The storm date against the carrier's filing period | The days left to file on each roof a storm touched |
| Rank | Every address in the register, 0–100, by how likely the roof is to need work | The order the register is worked in: what to inspect this quarter, what to budget next year |
| Photo documentation | The inspection, filed to the address with annotations | Condition on record, assembled into a packet for the carrier or the owner |
| Imagery | Street-level and satellite views on the record | A look at the roof before anyone is sent to it |
Exposure, lifecycle, condition, claim windows
Exposure: the storm history per roof
Each roof carries its own hail history, not the county's average: how many radar-confirmed hits it has taken, how many since the roof went on, the largest stone, the last date, and a cumulative exposure figure in which bigger stones count for disproportionately more. Under it, every storm at this address with its size and date, and the wind events beside the hail, because blow-off is its own loss. That is the loss file for the roof, written before the claim.
Lifecycle: an age you can defend
The roof age estimate says where it came from and how sure it is: a permitted re-roof on the record beats the year the building went up, and a rep or an inspector who confirms the roof at the door beats both, for good. A very old building is not reported as a very old roof; the estimate is capped and marked, because a number nobody believes is worse than none. The register sorts on it, so the roofs past their service life are the top of the list, not a filter someone has to remember.
Condition: photo documentation per property
Photos taken on the roof or from the ground file themselves to the address, take annotations, and assemble into a packet for the carrier or the owner. Jobs and addresses group into a folder, a site, a client, a book, and a job publishes a no-login page where an outside stakeholder, a client's property manager, sees progress photos and status and can ask a question without an account. The inspection cadence is yours; the record is the same shape every time.
Claim windows: the days left, per roof
Every roof a storm touched carries the days remaining on the carrier's filing window, counting down from that roof's own storm date. Sorted, that is the list of what to file this month. Missed windows are the most expensive line on a portfolio, and the one a spreadsheet never shows.
Storm day: which addresses it touched
When hail lands, the swath is drawn on the map the day it falls, street by street rather than as a county-wide average, and every address in the register under it is flagged with its own storm date. An alert reaches your inbox when hail logs in your zips. The morning after starts with the list of roofs to inspect, in the order the register ranks them, and the filing window already counting. The public record behind it is free: the hail map and the county hail history pages show the storms whether you are a customer or not.
What is in the product today, and what is an engagement
Plainly, so nothing on this page is discovered in week two. The left column is in the product on any account with the scored layer. The right column is work we do with you, quoted on the call.
| In the product today | An engagement, quoted |
|---|---|
| A roof age estimate, the storm history and the cumulative hail exposure on every address in a live market | Standing up the counties your portfolio sits in beyond the markets live today; a county takes days, a national register takes a schedule we agree on the call |
| The register ranked, filtered and exported to CSV; the swath on the map the day it lands with every address under it flagged | Loading a register at portfolio scale: the importer maps your columns to the actual properties; at thousands of addresses we do it with you |
| Photo documentation per property, annotated and assembled into a packet; a no-login page per job where an outside stakeholder sees photos and status | Several operating companies or regions under one login, set up per account by us |
| Storm alerts to your inbox when hail logs in your zips; the free hail map and the county hail history pages as the public record | Reports on your review cadence, exports on a schedule, and any connection to the systems you already run: quoted, not shipped |
Published pricing for the two pieces that are published: $150 per seat per month for the platform, and the scored layer from $1,000 a month for 20 zips, per zip above that at a rate that declines with volume. A register at portfolio scale is quoted. Every vendor's published pricing, dated, is on the roofing software pricing index.
Who runs a roof portfolio on Curbsight
A property-management company, so the capital plan for four hundred doors starts from the roofs' own ages and hail history instead of a build year in a spreadsheet. A multi-site operator, so the roof on every location is one line in one register with its last inspection attached. An insurer or adjusting firm, so a book of addresses after a storm is already sorted by which roofs the swath touched and how hard. And a commercial or residential roofer with maintenance accounts, so the quarterly review is the register and the inspection, the estimate, the proposal and the invoice run on the same record. That contractor workflow is the rest of Curbsight: the roofing CRM, the estimating software and the field app.