Determine the result that the site should give

Define the visitor’s main action: order a service, book an appointment, buy a product or request a quote. Then describe the audience, region and reasons for choosing the company. This shapes the structure and copy; it is not a formality before design.

For example, for a service with an individual estimate, it is important to explain what the price depends on and what data is needed for calculation. For goods with a clear price – availability, characteristics, delivery and payment. Do not force both scenarios to work through the same abstract “Learn more” button.

Prepare materials for drawing pages

Collect a list of services or product categories, working conditions, confirmed preferences, photos and real examples. Mark that it is already ready, what needs to be created and who is responsible for approval. The case requires a task, completed work and a result that can be confirmed.

Do not replace the missing reviews with fictional ones. If the project is new, show a process, a demonstration example with an honest mark and team experience that can be described reliably. An empty block with big promises does not solve the trust problem.

Plan the structure and test the visitor journey

Identify the main sections and pages for individual needs. Services, prices, examples, company information and contacts should be linked clearly. Add a blog with a plan of specific topics, and not as an empty menu item “for SEO”.

Go through the user flow with the words: “A person gets to a service, sees conditions, views an example and sends an enquiry”. If you need to open five non-obvious sections to answer a simple question, the structure should be simplified. The example of the organization is given in articles about the structure of the site services.

Illustrative diagram

What should be ready at each stage

  1. ObjectiveAudience and main action
  2. StructurePages, materials and user flow
  3. RealizationDesign and working features
  4. LaunchVerification, access and support
Illustrative development workflow: each stage begins after the previous stage is approved.

Before development, check that the content management system supports your workflows. For guidance, see Practical criteria for choosing a CMS.

Wireframes, design and development: what to agree on

Stage What the owner gets What to check
Prototype Sequence of blocks and actions Whether there is enough information to decide
Design Designing key templates Readability, mobile appearance, form states
Development Work Pages and Integrations Whether the agreed user flow works
Filling Real texts, photos, products Completeness, accuracy and no placeholder content
Acceptance checks Verified site Enquiries, purchases, accesses and instructions

Agree not only the main page. The service, article, category, product product page and error page may have their own needs. For the form important states to send, error, expectation and confirmed success. They are better defined before programming.

Check the website before publishing

  1. Open all the key templates on your phone and computer.
  2. Submit a test enquiry and make sure that it was received responsibly.
  3. Check phone, email, work hours and post messages after sending.
  4. For the store, pass a test order, payment in agreed test mode and error handling.
  5. Check the titles, meta descriptions, main addresses and availability of the pages you need to search.
  6. Make sure that the analytics captures the desired action once.
  7. Check the owner’s backup, restore order and accesses.

If the site replaces the old one, save the URL list and configure the corresponding redirects. The new design is not a reason to lose materials that already receive visitors. Moving is discussed in detail in the WordPress Transfer Plan.

What the owner should receive after launch

Access to domain, hosting and admin panels, license list, editing instructions and support terms. Specify who updates the system, reacts to a form failure and checks backups. The presence of the site on the Internet does not mean that these duties are already distributed.

After the launch, review the first real enquiries. Do people understand the proposal correctly? Don’t they constantly ask for information that should be added to the page? These questions help to choose subsequent improvements based on usage.

What do you need from the customer? Objectives, materials, exact terms of service and the person who makes the decision. Accesses are transferred in an agreed manner, and not published in the document.

Can I start in stages? So, if the first version fully performs the main scenario. Unfinished payment or non-working form should not be called the minimum version.

How to assess the budget? Compare the required format with the cost of creating a website and prepare a short task.

Editorial Cartel Digital. Practical advice and examples, prepared on 17–18 October 2026. Illustrative scenarios do not represent client project results.

Need a plan for your website?
Find out about Website creation, cost of work Or describe us the task.