| Property inputs | Verify current official imagery, property-input, and ordering requirements | Verify current official photo, property-input, and workflow requirements | Submitted address and available property context; coverage varies |
| Pricing | Verify current official product, property, plan, volume, region, feature, and contract pricing | Verify current official product, volume, region, feature, and contract pricing | Verify current published plan, acceptable-use, provider-limit, tax, currency, and checkout terms |
| Turnaround | Verify current official turnaround for the selected product and property | Verify current official turnaround after the required inputs are submitted | Request timing varies by data coverage, device, network, and whether the homeowner enters the texted code |
| Accuracy and suitability | Verify current official accuracy terms, coverage, report scope, limitations, and intended use | Verify current official accuracy terms, coverage, model scope, limitations, and intended use | Preliminary ballpark context only; inspect the property and verify inputs before final scope or price |
| Report, model, or visual output | Verify the selected product's current official report and visual outputs | Verify the selected product's current official model, measurement, proposal, and visual outputs | Preliminary provider-characterized roof context and contractor-configured ballpark where supported; not a precision report or 3D model |
| Workflow fit | Evaluate for the required detailed measurement or report use case using current vendor terms | Evaluate for the required measurement, model, or proposal use case using current vendor terms | Address-first estimate-to-proposal sales through Lite CRM and proposal tools; contractor decides on inspection or detailed measurement |
| Request capture and handoff | Verify current official public-capture, validation, export, and integration capabilities | Verify current official public-capture, validation, export, and integration capabilities | Lite CRM records submitted context and code entry; proposal tools and optional handoffs remain distinct and testable |