Industries

Find the boundary between a stock template and the website you need

Start with the change you need to make

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

A website request becomes easier to evaluate when it names the exact change. Rewriting an introduction, moving a form, changing an inventory layout, and adding a separate destination are different tasks. They may involve different controls and different owners. Before choosing an implementation, identify what the shopper should be able to understand or do, then inspect where the current stock template supports that requirement.

Planning a DealerCenter website starts with this boundary: which parts can be changed through the available template, and which require another implementation route? Ninetyfifth Marketing's method centers on making that distinction explicit. The result of the assessment should be a scope with known editing responsibilities, identified dependencies, and a clear explanation of what needs verification before anyone promises a particular design.

Separate editable content from page structure

Content and structure can look similar in a design conversation while requiring very different work. Replacing a paragraph is a content change. Placing that paragraph above a search tool is a structural change. Adding an image to an existing slot differs from changing how that image behaves across screen sizes. An assessment should describe these requests separately and verify the controls available in the specific website.

Content questions

Identify which headings, paragraphs, images, navigation labels, and calls to action can be edited. Then check whether those edits apply to one page or recur elsewhere. A shared label can affect more than the screen currently under discussion. Record who has access to make the change and whether the edit can be previewed. These details determine how a content recommendation becomes a publishable page.

Structural questions

Inspect the arrangement of page sections, available layouts, placement of forms, and relationships between shared elements. Do not assume that an element visible on the page has an independent editing control. If a requested arrangement is unavailable, document the limitation and the decision it creates. The next step might be adapting the design, requesting platform assistance, or considering a separately scoped page.

Use a concrete request to test the template boundary

Take a hypothetical request to explain the dealership's appointment process before a visitor sends an inquiry. The smallest implementation might be an editable paragraph beside an existing form. A more involved version might require a new section with its own heading, supporting details, and action. A separate landing page would introduce navigation and handoff questions. These are alternative scopes to evaluate, not interchangeable descriptions of the same task.

The assessment should test the smallest suitable change first. Can the explanation fit in an available field without becoming difficult to read? Does it appear near the relevant action on a narrow screen? Does the confirmation still describe what the visitor requested? If the available template cannot support the intended sequence, that finding should inform the scope before a detailed layout is treated as approved.

Choose among adapting, extending, and separating

Adapting the existing template means shaping the content and page plan around verified controls. This approach deserves consideration when the required explanation and action fit the current structure. Its tradeoff is that the design must respect those constraints. A proposal should show how the content fits, including mobile placement, instead of presenting a visual concept that depends on controls nobody has confirmed.

Extending the existing experience requires a precise account of what needs additional access, platform support, or development. The word custom is insufficient by itself. Identify the component, the desired behavior, the party responsible, and the dependency. If feasibility is unresolved, make verification a scoped step. A request should not become a delivery commitment simply because a similar arrangement appears elsewhere on the internet.

Separating a page from the stock experience creates its own responsibilities. The page needs a location, a maintenance owner, a route back to relevant website content, and a defined inquiry destination. Any vehicle-specific information requires an agreed source and update process. A separate page should therefore be evaluated as an operating choice as well as a design choice, with the added responsibilities visible in the proposal.

Keep the inventory relationship explicit

A marketing page can discuss the dealership generally or refer to specific vehicles. That distinction affects maintenance. General content may need editorial review when dealership information changes. Vehicle-specific content also needs a decision about availability, links, and ownership of updates. The assessment should establish whether inventory remains within the existing experience and how any additional page connects to it.

For example, a general page about arranging a visit could send shoppers to the existing inventory area. A page featuring a particular vehicle would need a defined response when that vehicle is no longer available. Neither path should be assumed from a mockup. Agree on the intended behavior and the person responsible for it before publishing content that depends on changing inventory.

Treat the form as a boundary of its own

A form's appearance does not explain its destination. When reviewing a template, inspect the fields, visible instructions, confirmation, and receiving workflow separately. A layout change may leave delivery untouched; a replacement form may require a new delivery specification. The scope should state which situation applies. An attractive inquiry section is incomplete if nobody can identify where its submissions are expected to arrive.

Use a test inquiry with controlled information to trace the intended path. Check that the receiving record preserves the context needed to interpret the request and that the confirmation matches the action taken. Where a separate routing mechanism is involved, document it as a connected workstream. Template editing and lead routing should each have acceptance criteria, even when they appear together on the same page.

Ask for an implementation map before approving the build

A useful implementation map lists each requested change, its location, the available control, the responsible party, and its acceptance condition. It should also identify unanswered questions. This gives a dealership a practical way to compare proposals: one may adapt existing sections, while another may introduce a separate page and additional maintenance. Those differences should be understandable without interpreting a design file or a technical shorthand.

Bring the current website and a short list of specific frustrations to a scope discussion with Ninetyfifth Marketing. Describe the visitor action behind each request, such as understanding an appointment process or finding the appropriate inquiry form. That makes it possible to assess the stock template boundary and define the next verification step before selecting a larger website project.