Planning a custom business website: what to prepare and what happens after launch

A website is often the first place a customer lands after seeing your name on a sign, a social post or a search result. Whether you are building a first site or replacing an outdated one, a little preparation makes the project smoother and the result more useful.

This guide covers what to settle before work begins, what a well-built business website typically includes and what happens after launch. Where it describes how a specific company works, it says so and links to that company's own pages. That company is NULYNQ LLC, which has a profile in this directory.

Start with what the site needs to do

Before any design work, write down short answers to these questions:

1. Who is the site for? Describe your typical customer and what they are trying to find out.
2. What should visitors do? Call, book, request a quote, buy or visit in person. Choose one main action and one backup.
3. Which services matter most? List them in the order you want to be known for them.
4. What do you already have? Logo, brand colors, photos, project examples, service descriptions and any existing website.
5. What is wrong with the current site, if there is one? Outdated information, slow pages, trouble on phones or difficulty making changes are all useful to know.

A provider can help you sharpen these answers, but arriving with a first draft saves time.

What a solid business website includes

Whoever builds it, look for these basics:

• A layout that works on every screen. Desktop, tablet and phone, not just the one the designer used.
• A structure built around your goals. Navigation and pages that lead visitors toward your chosen action, rather than a pile of pages in the order they were written.
• Fast, accessible foundations. Pages that load quickly and can be used by as many people as possible, including people using assistive technology.
• Separate pages for services and projects. A page for each service, and for the work you want to show, gives visitors specific answers and gives search engines something specific to find.
• Clear contact paths. Forms and calls to action placed where visitors are ready to act.
• Search basics. Descriptive page titles and descriptions, clean page addresses and a clear heading structure.

A note on search results

A well-structured site gives search engines what they need to understand your pages, but structure alone does not guarantee a ranking. The company above makes the same point on its website: no one can guarantee rankings, but a solid foundation improves a site's chances of being found. Treat any provider that promises a specific position in search results with caution.

What happens during the project

Custom website projects tend to follow a similar arc, though the details differ by provider:

1. Discovery. The provider learns about your business, audience and goals and looks at your current site.
2. Design. You see a design direction and page layouts and give feedback before the build starts.
3. Build. The site is built to work on all screen sizes, with speed, accessibility and search-friendly structure in place from the start.
4. Launch and handover. The site is tested on different devices, goes live and is explained to you.

Ask about timing and cost at the outset. Both depend on the number of pages and on whether the site needs special features, so a good provider will scope the work with you and agree a price before it begins.

Why launch is not the finish line

Websites age. Hours, services and photos fall out of date, small technical problems build up, and chances to improve the site go unnoticed because nobody is looking. Ongoing care usually covers:

• Content updates. New services, photos, offers, hours and announcements.
• Routine maintenance. Regular upkeep that catches small problems early.
• Health checks. Periodic reviews of speed, links, forms and key pages.
• Improvements. Measured changes to layout, content and calls to action, based on how the site is performing.
• New pages. A new service page, project gallery or landing page as the business grows.

You can handle this yourself, hire a provider or use the team that built the site. What matters is deciding who is responsible before launch rather than after something breaks.

Questions worth asking before you sign

• What is included in the price, and what would count as extra?
• Who owns the design, the content and the domain name when the project ends?
• Who updates the site after launch, and how do I request changes?
• Will you manage a site that someone else built, or only your own work?
• How will the site be tested on phones and tablets before it goes live?
• What do you need from me, and by when?

For a similar checklist aimed at software, see Questions to ask before building a custom business app.