When a business decides to build a website, it usually asks two questions first: “how much does it cost?” and “how long will it take?”. They are fair questions, but they should not come first. Both the price and the timeline are set by what the website is for, who it is meant for and what exactly it will give the business. Without answers to these three questions, the cheapest and the most expensive website will deliver the same result: a good-looking page that solves nothing.
What a website is for: start with the goal
The goal of a website should be stated in business terms and be more specific than the general thought “we should have a website”. For some it is there to bring in orders, for others to give clients reliable information about the company, for others to sell goods online, and for others to give extra proof to someone who arrived from another channel. Each of these goals calls for a different structure, different content and a different budget.
It helps to write the goal in measurable form: decide in advance how many leads per month, how many orders or what level of calls you expect. Then, after launch, you can judge whether the site is working by numbers rather than by feeling.
Choosing the type of website
Once the goal is clear, the type of website is chosen. A landing page is a one-page site built around a single offer or service; it most often leads a visitor from an ad to one action, such as leaving a request. A corporate website gives full information about the company, its services, projects and contacts, and is aimed at building trust. An online store includes a catalog, cart, payment and order management, so it is technically much more complex. There are also more complex solutions: portals, aggregators and platforms with a personal account.
Many businesses go to one of two extremes here: they either order an overly complex site for a simple goal or, the opposite, try to fit a complex business process into a one-page landing. We have separate articles in our blog on the difference between a landing page and a multi-page website, and on comparing a corporate website with a landing page, so it is worth reading them before you choose.
Planning structure and content
Before a designer picks a single color, the structure of the site must be clear: which pages there will be, how they connect and what job each page has. At this stage a sitemap and a list of blocks for each page are usually created. The main rule is simple: on any page the user must find answers to three questions — where am I, what can I do here and where do I go next.
When planning the structure, start from the user's thinking and problem, not from the company's internal departments. The client does not know what departments your company consists of and does not want to; they are looking for a way to solve their problem. So menus and headings are best written in the words the client uses, not in the company's internal language. This logic also affects visibility in search engines, because people search in exactly these words.
Design: how the website should look
Design is not just beauty but a working tool of the site. Color, typeface, button placement, text contrast and the hierarchy of elements determine where the user looks and what action they take. A good designer first builds the site as a wireframe and checks the logic, and only then moves on to colors and fonts, so that in the end every element sits in its place and does its job.
On the business side, the most useful things during the design stage are to show specific examples of what you like and dislike, to prepare the brand colors and logo in advance and to make decisions quickly. If things keep changing during design approval, it lengthens the timeline of the whole project. The mobile version must also be considered from the start of design, because many users visit the site from a phone.
Development: platform and technology
At the development stage the design turns into a working website. The key decision here is the platform: a ready-made content management system (CMS) or development from scratch. A ready-made system lets you launch faster and more cheaply and is enough for standard tasks, while custom development is needed for non-standard logic, high load or special requirements. We covered this choice in detail in our article on CMS versus development from scratch.
Beyond the platform, don't forget the admin panel: after launch you should be able to manage content, prices, orders and requests yourself without going to the developer each time. It is also worth discussing in advance whether the site needs to connect to a CRM, a payment system, notification services and analytics, because adding them later usually costs more.
Texts and images: who prepares the content
In website projects the thing that is delayed most often is not the design or the code but the content. The developer has the site ready, but without texts, images, prices and work samples the launch stands still. So it is right to start preparing content alongside development and to appoint someone responsible for it in advance.
It is important that texts are written not with generic phrases but with concrete information: you need to say clearly what you offer, to whom, on what terms and at what price. Generic phrases like “individual approach” and “high quality” give the client nothing, while specific results, timelines and work examples build trust. Images should be real too: photos of your own team and work leave a far stronger impression than typical stock pictures.
Ask a question or leave a request
Tell us your goal and we will suggest the right website type, platform and a timeline estimate.
By submitting the form, you agree to the processing of personal data.
Testing and preparing for launch
Before publishing, the site must be checked on different devices and browsers: that the mobile version looks right, that forms work, that links work and how fast pages load. A real example: if a form sends the request but it never reaches the manager's mailbox, the business can lose clients for months, and only a full check will reveal it.
Technical readiness also has to be checked before launch: SSL certificate enabled, basic settings for search engines, analytics counters connected, and a consent to personal data processing and a privacy policy in place. We wrote a separate article on the latter from the standpoint of Kazakhstan's legislation, and fixing these gaps after launch is usually more expensive and harder.
Domain, hosting and launch
The website address (domain) and the place where it is hosted (hosting) must be registered in the client's own name, that is, in the name of the company. This is very important: if the domain is registered to the developer's personal account, you may lose access to the site after the project ends or when you change developers. Choosing a domain zone, a hosting type and backups is covered in full in a separate article.
On launch day a final check is usually done before publishing, after which the domain is pointed to the new hosting. In the first days it is worth monitoring the site, forms and counters and fixing any fault quickly, because this is when the first users form their first impression of the site.
Life after launch: support and development
Launching a website is not the end of the project. Updating the platform and plugins, monitoring security, making backups, keeping content current and fixing technical faults all require steady work. A site without support gradually becomes outdated, slow and unsafe, and stale prices and broken links reduce trust in the company.
Developing the site matters too: analytics data shows which page works and where users leave, and regularly published blog articles gradually increase search traffic. Support terms are best discussed at the very start of the project, with their scope and cost set in writing.
What affects timeline and budget
The cost and timeline of a website depend on the number of pages, how unique the design is, the complexity of the functionality, the number of integrations, the chosen platform and how ready the content is. The difference between a one-page landing and an online store with a catalog, personal account and payment can be several times over, so the idea of an “average website price” is very conditional.
The best way to get an accurate estimate is to describe to the developer not a list of features but the goal and the expected result. The team can then propose the option that reaches the goal most efficiently. When estimating the total cost of the project, take into account not only development but also the costs of domain and hosting, support and content preparation.
Common client mistakes
The most common mistake is starting without a goal: a site born from the thought “everyone has one” is most often needed by no one, because it solves no specific problem. The second is jumping straight to design without discussing the technical specification and structure enough, so that changes pile up during development and the budget and timeline grow. In many cases content preparation is forgotten or left to the last moment, and the site launches with empty texts and generic pictures.
It is also common to register the domain in the developer's name, to overlook the mobile version, to leave support and security out of the budget and to never look at analytics after launch. The last one is especially regrettable: without data there is no way to tell whether the site is working, and decisions rest on feelings.
Checklist
- The website goal is stated in measurable indicators
- The website type (landing, corporate, store, platform) matches the goal
- The structure and page list are based on user questions
- The design is approved with the mobile version in mind
- The platform (CMS or custom development) is chosen to fit the task
- The admin panel and required integrations are planned
- Someone is responsible for preparing texts and images
- Forms, links and the mobile version are tested
- SSL, analytics, privacy policy and consent are in place
- Domain and hosting are registered in the company's name
- Post-launch support and development are planned
