Start with your operating reality
Write a short brief before requesting proposals. Include your trade, priority services, actual coverage, booking capacity, and the types of inquiries your office declines. Separate urgent repairs from planned estimates or maintenance agreements because those customers need different information. Explain whether you operate from one location, dispatch across a region, or manage several staffed locations. Share existing website and measurement access carefully. A useful prospective partner should ask about these constraints and explain how they affect the plan. A generic proposal that arrives before these questions are discussed may leave important work outside its scope.
Ask what the deliverables will change
Request examples of the decisions behind each proposed activity. A technical audit should identify issues, explain their likely impact, and establish who implements fixes. Content work should specify which customer questions or service gaps it addresses and who verifies business facts. Local visibility work should reflect real business eligibility and operating locations. Ask what happens after recommendations are delivered, including development dependencies and review rounds. A long checklist can conceal a plan that stops at advice. You need enough detail to distinguish research, implementation, and ongoing review without expecting an agency to predict every discovery before access is available.
Agree on evidence and account ownership
Discuss measurement before discussing success. Ask how the agency will distinguish relevant traffic from calls outside your area, duplicate inquiries, and requests for services you do not offer. The proposal should explain the baseline, reporting sources, and any limits in attribution. Keep your domain and core business accounts under business-controlled ownership, with permissions suited to each person's role. Clarify who owns approved content, design files, and tracking configurations when the engagement ends. If a partner presents previous results, ask what work they performed and what other changes influenced the outcome. A case study informs a conversation; it does not predict your results.
Read the commercial and release details
Compare the total commitment, including setup fees, development work, paid tools, cancellation terms, and any costs outside the quoted retainer. Confirm who approves website changes and how the team handles a broken form or incorrect phone link. Ask how progress will be reviewed when priorities change or implementation is delayed. Avoid treating a ranking guarantee as a substitute for a clear agreement: search results remain outside an agency's control. Finish with a written scope that your office can understand. The right next step may be a bounded diagnostic project, an implementation project, or ongoing support, depending on the condition of your site and business needs.