A pipeline that closes itself.

One record per job, from lead to paid

A roofing job passes through more hands than almost anything else a contractor sells. A rep knocks it, an estimator prices it, a production manager schedules it, a crew builds it, the office invoices it, and somewhere in there an adjuster gets involved. When each of those people works in a different tool, the job exists in five partial versions and none of them is right.

Trussi keeps one record. The address, the measurements, the photos, the signed contract, the material orders, the schedule, the invoices, and every message sent to the homeowner live on the same project. Anyone who opens it sees the current state of the job rather than their own department's slice of it.

That single record is also what makes the reporting believable. Job level profit and loss is only as good as the costs attached to the job, and costs only attach reliably when the ordering, scheduling, and invoicing all happen against the same project.

AI scoring, so reps chase the right deals

Trussi's lead scoring engine is patented - U.S. Patent 12,131,277 - and it is trained on how roofing deals actually behave rather than on generic sales heuristics. It weighs the signals that matter in this trade: property and roof age, storm activity, whether the job is insurance or retail, how quickly the homeowner responded, how many times the estimate has been opened.

The output is a ranked list. A rep with thirty open leads and four hours of daylight does not need a longer list, they need to know which four to drive to. Automated follow ups cover the rest, so a lead that is not worth a visit today still gets a touch instead of going cold.

Stages that match how you actually run

Pipeline stages are configurable because no two roofing companies run the same process. Insurance restoration work needs claim and supplement stages that retail work does not. A company selling three trades needs different qualification than one selling only roofs.

Stage changes drive the rest of the system: entering production triggers scheduling, a signed contract opens invoicing, and a completed job starts the collections clock. The pipeline is not a reporting view bolted on top, it is the thing that moves the work.