Lead capture layer
A request-capture requirement should define the visitor inputs, consent, routing, evidence, operating limits, and downstream handoff the contractor needs. Verify each vendor's current public documentation and contract before treating products as equivalent.
Measurement layer
A measurement requirement should specify the needed inputs, accuracy review, deliverables, turnaround, coverage, and current price. Confirm each vendor's current capabilities directly; this page does not certify them.
CRM and proposal layer
A CRM or proposal requirement should document the records, fields, permissions, automations, delivery status, retries, reporting, and current integration route. Confirm each vendor's current capabilities directly.
Solar design layer
A solar workflow requirement should separate discovery, request capture, design, proposal, and marketplace needs. Confirm each vendor's current capabilities directly rather than inferring them from a category label.
GeoQuote wedge
GeoQuote covers address-first estimates, preliminary provider-backed property context where supported, Lite CRM, proposals, typed approval, and optional consent-based follow-up or configured handoff. A submitted-number code entry does not establish identity, qualification, booking, or a sales outcome.
Evaluation scope
Evaluate GeoQuote when a roofing or solar contractor has eligible owned traffic and needs a lighter estimate-to-proposal sales workflow. Measure submission, proposal, acceptance, contact, appointment, sale, gross-profit, and total-cost outcomes from the contractor's own data.