- Map the customer task
- Design the content and journey
- Build and verify
- Hand over the site
Define what the new website must change
Bring the current site and a short account of what goes wrong. Customers might ask the same unanswered question, abandon a form, mistake a service area for an office location, or reach a sales team without enough context. These observations are more useful than starting with a preferred animation or a page count.
Write one primary outcome for each important page. A services page might help a prospect decide whether the work fits. A product page might let a buyer compare specifications. A contact page should explain the next step and collect only the information needed to take it. This makes content, layout and measurement decisions easier to evaluate together.
Let Salt Lake City's business mix shape the brief
The city's business-development department identifies industries including outdoor products, healthcare, manufacturing and distribution. That variety matters because the same website structure will not fit every local company. The following situations are hypothetical planning examples, not Dappr client projects or claims about any particular Salt Lake City business.
For an outdoor-products retailer with a Salt Lake City shop, separate product research from the practical details of a visit. Show the actual store location and approved hours, explain any collection process, and give someone responsibility for updating availability. Do not imply that an online product listing guarantees shelf stock unless the inventory connection supports that claim.
For a manufacturer serving buyers beyond Utah, the Salt Lake City address may establish where the company operates, while technical requirements drive the inquiry. Organize capabilities around the buyer's problem and give the quote form a clear route for relevant details. Claims about certifications, tolerances or turnaround need the company's approval before they become marketing copy.
For a neighborhood business affected by road work, current access information can be more useful than another promotional banner. Salt Lake City publishes a construction-planning resource for businesses. If the business is actually affected, an editable notice can explain its confirmed entrance or collection arrangement, identify when the notice was updated, and avoid announcing an unverified reopening date.
Resolve the content before polishing every screen
Start with a page inventory: material to retain, material to rewrite, and material to retire. The business should identify which service descriptions, photographs, staff details and product information it owns and can approve. A design schedule can stall when the layout is finished but nobody can confirm the content.
Use the first important page to establish the visual direction and the amount of explanation customers need. Review its heading, evidence, primary action and mobile sequence together. A beautiful desktop composition is incomplete if the most useful detail appears after several screens of decorative content on a phone.
Choose a platform around who will maintain it
Dappr can discuss websites across most builders. The choice should follow the editing workflow, selling requirements and integrations. A small team updating service copy has different needs from a retailer maintaining a catalog or an organization managing many content types. List those tasks before choosing a platform by name.
Identify recurring costs and dependencies separately from the build. Hosting, domain registration, platform plans, extensions and third-party services may have their own billing and renewal terms. The proposal should explain which accounts the business controls and which ongoing responsibilities are included in the agreed work.
Make the important actions usable
W3C's accessibility design guidance recommends clear labels, visible interaction states, readable contrast, consistent navigation and useful feedback. For this project, turn those principles into checks on the actual inquiry or purchase journey. Can a person identify the action, reach it with a keyboard, understand an error, and finish without guessing?
Test the full form, including unsuccessful submissions and confirmation messages. For a phone-led business, verify that the number is readable and the call link uses the intended destination. If the site sends inquiries into Dappr's CRM, scope and verify that connection explicitly. Do not assume the CRM handoff is included simply because a form appears on the design.
Plan the transition from the existing site
Before replacing a site, identify useful existing URLs and where each will lead afterward. Changes to page addresses, navigation and content can affect discovery as well as bookmarks and campaign destinations. Record the intended route mapping and test it as part of the launch work.
The launch checklist should include the agreed page content, mobile layouts, contact paths, account access and essential measurement. Separate defects from future improvements so that the business can decide what must be fixed before launch. A finished design file is one milestone; a working customer journey is the acceptance test.
Agree on the handover and the next review
The handover should identify who can edit pages, update business information and request support. Ask for the agreed access and a practical explanation of recurring tasks. If there are restrictions on a component or an integration, document them while the project context is still fresh.
After launch, evaluate the questions that started the project. Are inquiries reaching the right person? Is the form collecting useful context? Are customers still calling about information that should be easier to find? These observations help prioritize the next improvement without treating a new visual style as proof of commercial results.
Questions before you begin
Can a Salt Lake City team review the website remotely?
Yes. Dappr serves businesses remotely from its St. George office. Agree on the decision maker, review format and feedback deadlines at the start. A shared set of page decisions is more useful than conflicting comments from several people arriving after a design has been approved.
Should our site have separate pages for every Salt Lake neighborhood?
Only when a page helps a visitor with information that is genuinely specific to that area. A list of neighborhoods with interchangeable service copy adds little. For one storefront, a clear location and visit page may serve customers better than many near-identical pages.
Can we keep the builder our current website uses?
Possibly. The existing builder, account access, design constraints and required features need review. Keeping a suitable setup may be reasonable; rebuilding may be necessary when the agreed workflow cannot be delivered or maintained reliably. The recommendation should explain the tradeoff.
Will a new design automatically improve our search rankings?
No. Design can improve clarity and usability, but it does not guarantee rankings. Content, crawlability and the handling of changed URLs also matter. If search visibility is part of the project, include the relevant SEO work and migration checks in the scope.
How should we compare website proposals?
Compare the pages, content responsibilities, features, integrations, review rounds, launch checks and handover. Ask which recurring costs sit outside the project fee. Dappr's plans and a scope conversation can help frame the discussion; a price without these details is hard to compare fairly.