Industries

Connect the inquiry to a clear next step

A new inquiry starts an operational decision: what is being requested, does it fit the business, and who should respond? Looking at lead generation only as a way to collect contact details leaves those questions unresolved. For a contractor evaluating marketing support, the handoff deserves as much attention as the source of the inquiry. A contact record needs enough context to support a useful first conversation.

If search work is part of the scope, our website rule applies. We only do SEO on a site we built.

Ninetyfifth Marketing's documented work for Solterra Hardscape includes a website, SEO, Meta advertising, and lead automation within hardscape design-build and outdoor-living work. That is the evidence behind this page. It does not establish experience across general landscaping, concrete, or construction, and it does not support a claim about lead counts or attributed revenue. The following buying considerations explain how to assess a proposed engagement within a clearly defined scope.

Define what counts as a relevant inquiry

Before discussing contractor leads, establish which requests the business wants to receive. A hardscape design-build inquiry might involve a homeowner exploring an outdoor-living project, but the label alone does not describe the property's location, the requested work, or the buyer's planning stage. A useful brief would state the eligible project types and the information needed to decide whether an initial consultation is appropriate.

A proposed definition should also distinguish a new opportunity from other contacts. A supplier message, a repeat submission, and an existing customer's question can all enter the same inbox. Treating them as interchangeable would make review difficult. Ask how the proposed intake process would preserve those distinctions and who would make the final assessment when an inquiry does not fit a simple category.

Use questions that support a decision

Each field on a proposed form should earn its place. A property location can support a service-area check. A short project description can help determine whether the request belongs with the person handling design-build consultations. A timing question can prepare the first conversation. These are examples of possible intake choices, not details established by the documented work. Their value depends on whether the receiving team can use the answers.

Trace the path from interest to ownership

The documented scope includes Meta ads and lead routing, which makes the connection between marketing and intake a relevant subject for evaluation. Documentation of those activities does not establish a particular form design, software stack, routing rule, or response sequence. A prospective buyer should request those implementation details in a proposal rather than infer them from the existence of lead automation.

For a proposed engagement, the inquiry path should be understandable without a technical diagram. Someone sees a message, submits information, and reaches a destination where a person can act. The proposal should name that destination and explain how responsibility is assigned. If several people receive a notification, it should still be clear who owns the response and how the others can tell that action has been taken.

• Identify where a request originates and which information accompanies it.
• Specify the system or inbox that would hold the inquiry record.
• Assign responsibility for reviewing the request and contacting the person.
• Define what should happen when information is missing or ownership is unclear.

Keep routing separate from qualification

Routing answers where an inquiry should go. Qualification answers whether the requested work fits the business. A proposed system can support both, but they require different decisions. An address might determine the appropriate office, while a project description might require a person's judgment. Ask whether the proposal preserves the original request so that staff can review the context instead of relying entirely on an automated label.

Consider a hypothetical request for an outdoor-living project that includes a service the business does not offer independently. Automatically discarding it based on one phrase could remove useful context. Automatically accepting it could create a misleading expectation. A proposed process could send that request for review and give the recipient the full description.

Write the first response around the actual next step

An acknowledgment and a consultation confirmation serve different purposes. In a proposed engagement, an acknowledgment could confirm receipt and explain what information may be needed next. A consultation confirmation would require an actual scheduling decision. The wording should reflect that distinction so a person submitting a request understands whether they are waiting for review, choosing a time, or supplying additional details.

The buyer should also decide how staff handle requests that cannot move forward. A clear internal status and an appropriate response can keep a record from remaining indefinitely open. If automated communications are proposed, their content, triggers, and handling of contact preferences should be reviewed before activation. Any questions about current communication or privacy rules should be addressed with qualified counsel as part of implementation.

Agree on review categories before collecting reports

A proposed reporting approach should preserve the difference between an inquiry, a reviewed opportunity, a consultation, and a signed agreement. Those stages are not interchangeable. Decide who updates each stage and what evidence supports the change. Otherwise, a report may depend on assumptions about events that happened in a phone call or an estimator's separate notes.

Useful review questions include whether requests concern the promoted service, whether locations fit the operating area, and whether the receiving team has enough information to respond. A proposed system could record reasons a request does not progress, provided the categories are clear and practical. That creates a basis for discussing scope and process without promising a volume of work or assuming revenue attribution.

Ask for a proposal that names the handoffs

The documented evidence supports a conversation about hardscape design-build marketing, Meta advertising, and lead automation. A proposal should go further by identifying the intended inquiry source, destination, ownership rules, review stages, and responsibilities on your team. It should also identify what remains subject to discovery. Bring your service boundaries and current intake process to that conversation so the proposed work can be assessed against a concrete operational need.