Message match
A sheet that sets the ad headline beside the page headline and the first screen, one ad group at a time, so the promise is carried through in the same words. Where an offer has two audiences, it gets two versions of the headline. You receive: the message-match sheet, approved by you before design starts.
Page design and copy
A single-column page with the offer, the reasons to act, the proof you can document and one button, designed for a phone first and a wide screen second. You approve the layout and the copy before it is built. You receive: the approved design and the written copy.
The form
Only the fields needed to call or book, each with a visible label, the right autocomplete value and an error message that says what to fix. Anything you can learn on the phone stays off the form. You receive: the form specification, with the reason for each field.
Consent and disclosures
Consent wording beside the button wherever texts or automated calls follow, a link to your privacy policy and a working opt-out path. Your attorney approves the final wording, because the scope covers placement and design, not legal advice. You receive: the consent wording as built and a note of where it appears.
Speed and accessibility
A budget set before the build against Google’s published thresholds, then measured on a phone and again on real visits once there is enough traffic. Keyboard and screen reader passes are done by hand against WCAG 2.2 AA. You receive: the budget sheet and the test record.
Lead tracking
Events for the form, the call tap and the booking, sent to analytics and the ad platform, with the lead record in your CRM carrying the campaign it came from. The scope includes a traced test submission, from the click to the CRM row. You receive: the tracking map and the traced test submission.