Use the RFP questions below as the starting point for your buying brief.
Download the RFP worksheet ↓Start with your buying requirements
Describe the company that will receive and work the leads, the trades it installs and the markets in scope. Include branch ownership where more than one team serves the area. State whether the program is for replacement work, repairs or both, and identify property types the teams can serve.
Give vendors a requested launch window and an intake range to discuss. Label a forecast as a forecast rather than a commitment. Explain whether you already receive leads through ping-post, direct posting or a CRM form. Ask for proposed coverage against your actual requirements instead of a national volume claim with no market breakdown.
Require a consistent response format
| RFP section | Ask the vendor to provide |
|---|---|
| Product and source | Capture-page example, campaign ownership and qualification steps |
| Distribution | Buyer count, later resale rules and territory restrictions |
| Coverage | Supported project types and proposed markets, with exceptions |
| Delivery | Posting requirements, response handling, caps and support owner |
| Commercial terms | Quote assumptions, billable event and credit process |
| Pilot | Initial scope, test plan, review dates and approval owner |
For each section, ask the vendor to mark supported, requires discussion or unavailable. Leave room for an explanation. A blank cell is ambiguous; a stated exception lets your team decide whether it changes the proposed launch. Request documents by title or link and identify anything that must be shared privately.
Ask for evidence you can inspect
Request a representative capture experience and a redacted example record showing the fields delivered. If the program uses a certificate or other capture evidence, ask how the record is linked to it and how the buyer can retrieve it. Do not request real homeowner details in an open procurement worksheet.
Ask who controls each campaign, who approves changes and how additional sources enter the program. Where a vendor relies on a platform, request the account-specific submission instructions and the proposed test cases. A platform logo in a presentation does not establish that the connection has been configured for your flow.
Choose decision rules before reading proposals
Separate requirements that must be met from preferences you can trade off. For example, an approved service area and a usable receiving route may be launch requirements. A particular report format may be negotiable if the underlying data is available. Have operations, sales and finance agree on those distinctions before scoring vendors.
Use a short evidence log beside the comparison: requirement, response, document reviewed, open question and owner. Avoid a numerical score that implies more precision than the review supports. A vendor can score well on presentation and still have an unresolved source or delivery question that prevents launch.
Turn the chosen proposal into a launch packet
Carry the final project definition, coverage list, pricing assumptions, credit rules and technical instructions into one approved packet. Resolve differences between the RFP response and the commercial agreement before anyone enables traffic. Give the receiving team the same effective version that the supplier uses.
Download the worksheet, replace each bracketed field and remove questions that do not apply. Send Adsora your completed scope to discuss a home-services lead program; confirm availability and delivery requirements during that review.