The performance marketing contract red flags roofing owners should check are vague outcome definitions, restricted account access, missing responsibilities, and no documented way to investigate disputed inquiries. Each leaves your company unable to verify what happened or decide who needs to act. Before signing, ask the provider to demonstrate the workflow and put the agreed responsibilities in writing.
This review focuses on whether your team can operate and verify the proposed system. It isn't a substitute for legal review. Bring unresolved language to an attorney rather than relying on a salesperson's interpretation.
Check whether each outcome has a definition and evidence
Search the agreement for words such as “lead,” “qualified,” “appointment,” and “result.” If those words appear without definitions, different people can read the same report and reach different conclusions.
Ask the provider to distinguish these stages:
- Inquiry: Someone submits a form, calls, or sends a message about roofing services.
- Contact: Your team establishes two-way communication with that person. An automated acknowledgment alone doesn't establish contact.
- Qualification: Your team confirms the request meets documented criteria, such as service area, roofing need, and authority to arrange the work.
- Booked estimate: The homeowner and your team agree on an estimate visit and record it on the calendar.
- Attendance: The visit actually takes place.
- Signed project: The homeowner signs the project agreement.
- Completed project: Your company finishes the roofing work.
A calendar entry doesn't establish attendance. A signed project doesn't establish completed work. The agreement should identify which stage the provider reports and which record supports it.
For qualification, specify the roofing services you accept, property types you serve, geographic boundaries, and who can authorize an inspection. Don't assume every renter inquiry is invalid; a renter may connect your team with an authorized property representative.
Ask who can change a status and whether the CRM preserves that history. A report that groups every submission under “qualified” needs clearer definitions before launch. For broader context on the label, see what performance-based roofing marketing means.
Verify access and ownership asset by asset
“Your data belongs to you” sounds reassuring, but it doesn't explain whether you can retrieve conversation history, continue using a landing page, or retain a tracking number.
Request an asset register covering:
- Google and Meta accounts, including your administrative access.
- Domains, landing pages, and the ability to edit or move them.
- Campaign creative, source files, and any third-party usage restrictions.
- CRM contacts, source information, status history, and conversation records.
- Tracking numbers, routing settings, and transfer eligibility.
- Conversion tracking and integrations connecting the platforms.
For each item, record the owner, administrator, available export, and any transfer limitations. Some software functionality and platform data can't move between systems. Those limitations should be disclosed rather than hidden behind a blanket ownership promise.
Ask for a screen-share demonstration of your proposed access and a sample export with personal information removed. A spreadsheet containing names and phone numbers isn't equivalent to a complete CRM history.
Provider-controlled infrastructure can be a legitimate operating choice. The warning sign is dependence your company hasn't knowingly accepted. If continued access requires the provider's cooperation, document the handoff procedure before your operation relies on it.
Separate managed advertising, automation, and human work
An agreement can describe a “complete system” while leaving essential work unassigned. Request a responsibility map that names the party responsible for each task.
For managed advertising, check who creates and launches campaigns, develops creative, maintains targeting, monitors delivery, and makes ongoing optimization decisions. If the proposed service is ongoing management, delivery of creative files alone doesn't satisfy that description.
For the CRM, identify who configures tracking, routing, automated SMS and email sequences, and delivery alerts. Then identify who handles replies. Automated sequences are system functionality; they don't conduct live homeowner conversations or qualify roofing needs by themselves.
The roofing company's responsibilities should explicitly cover live calls, qualification, homeowner conversations, scheduling, inspections, estimates, closing, and roofing work. If a separate appointment-setting provider is involved, document its specific responsibilities and handoff boundaries.
An owner-operator may handle every human step. The agreement should reflect actual availability and identify what happens when nobody can answer. A staffed company needs separate owners for office response, salesperson updates, and production completion records.
Check approval authority too. Who approves claims about roofing services? Who updates service areas when crew capacity changes? Who can pause a campaign promoting work you no longer accept? Missing answers create operational exposure even when inquiry delivery works correctly.
Require a review process that can distinguish different failures
“Bad lead” is too broad to guide a correction. A disconnected number, an unanswered call, and a homeowner choosing another roofer describe different events.
Request a documented process for flagging an inquiry, reviewing the underlying record, recording a decision, and making any necessary system change. It should name the reviewer and explain how unresolved disagreements are escalated.
Use evidence appropriate to the finding:
- Outside the service area: Compare the property location with the agreed boundaries and campaign settings.
- Wrong service requested: Review the advertisement, landing page, and submitted request for conflicting language.
- Duplicate inquiry: Check whether the person submitted again about the same property and project.
- No contact established: Review delivery, routing, attempted communication, and available contact details.
- Visit didn't happen: Check scheduling confirmation and cancellation records before assigning a cause.
Say a roofing company receives a repair inquiry while its campaign promotes replacement-only service. In this hypothetical situation, the reviewer should compare the homeowner's request with the campaign message and accepted-service definition. The correction could involve clearer messaging, different targeting, or better qualification.
An unanswered call alone doesn't prove an inquiry was invalid. Likewise, automated message delivery doesn't prove your salesperson received a usable notification. The process must allow either side's workflow to be examined.
Test the written workflow before launch
Use a test inquiry clearly labeled as internal. Trace it from the advertisement or form through source tracking, CRM delivery, staff notification, automated acknowledgment, and human assignment. Check that a homeowner reply reaches someone who can respond and that opt-out handling works.
Ask your office lead or salesperson to participate. For an owner-operator, run the test yourself using the device you'll actually use during the workday.
Send unresolved items back in a concise message:
Before we approve launch, please document the outcome definitions, asset access, task owners, and inquiry review procedure. Please also demonstrate lead delivery, reply routing, and a sample data export. We'll confirm our team's responsibilities against that workflow.
Agree on review checkpoints tied to observable evidence rather than assumptions about immediate results. The guide to how long roofing performance marketing takes explains why launch readiness and later campaign evaluation are different decisions.
Proceed when the written responsibilities match the demonstrated system. Request revisions when the system works but the documentation is incomplete. If the provider won't demonstrate access or clarify who handles essential tasks, leave those issues unresolved on your approval checklist rather than accepting a verbal assurance.