Ordering a website for the first time is hard not because of the technology, but because it is unclear where to start and where things can go wrong. Here is the whole path, step by step: what to decide before you call a developer, how to choose one, what to sign and how to accept the finished work.
Where to start: what to decide before you order a website
Step 1. Define the goal and the audience
Start with the outcome, not the design. What should happen because the website exists? For example, “customers request a repair quote”, “buyers place an order without calling a manager” or “partners download the price list and terms”.
Then describe who will visit. Say you run a coffee shop with delivery. A visitor arrives on a phone, hungry, with two minutes to spare. They need the menu, prices, an order button and a delivery time. The story of your shop and photos of the interior can wait.
One main goal and a clear picture of the visitor already cut half of the unnecessary pages and features.
Step 2. Choose the type of website
The goal tells you what kind of site you need:
- Landing page. One page for one offer: a service, a promotion, an event.
- Business website. Several pages about the company, services and contacts.
- Online store. Catalog, cart, payment, delivery and order management.
- Web service or customer portal. Customers sign in and see their orders, bookings or documents.
Sometimes a website is not the best answer at all. A Telegram bot may be enough for salon bookings, and regular customers may prefer an app. More on that in Website, app or Telegram bot. And if the task is simple, compare custom development honestly with a website builder: for a three-page business site it is often enough.
Step 3. Gather your materials
A website cannot launch without content, and content is what delays projects most often. Before work starts, collect:
- your logo and brand colors, if you have them;
- texts about your services or products, even rough drafts;
- photos: your own, not random ones from the internet;
- prices, delivery and payment terms;
- contacts, addresses, opening hours;
- examples of websites you like, with a note on what exactly you like.
If you have no texts or photos, that is fine. But decide right away who will make them: you, the developer for an extra fee, or a separate copywriter and photographer.
Step 4. Set a budget
Name a range you are willing to spend, and remember it is not only development. There is also the domain, hosting, texts and photos, support after launch and marketing.
Quotes on the market differ many times over, and that is not always a scam: the same word “website” can mean very different amounts of work. How the price is built and how to compare quotes fairly is covered in How much a website costs. For reference, at NOVO a website or web service prototype starts at $300, a first version at $1,200 and turnkey website development at $3,000. The exact price comes only after the brief.
Choosing a developer and signing a contract
Step 5. Decide who should build your website
The usual choice is between a freelancer, a studio and an in-house developer. Each has its strengths and risks, compared in Freelancer, studio or in-house developer.
Make a shortlist of three to five candidates and check each one:
- live projects in the portfolio: open them, click the buttons, submit a form;
- what exactly the developer did on each project;
- how they communicate: do they ask about your business or name a price right away.
Watch for warning signs: 100% prepayment, no contract, pressure like “pay today, it will cost more tomorrow”. The full list is in How not to get scammed when ordering a website.
Step 6. Write a brief
A brief makes every candidate estimate the same thing. Without it, one will price a landing page and another an online store, and you cannot compare the numbers.
You can write it in plain language, with no technical terms: your business, the goal, the audience, the pages, the features, the deadline and the budget. How to do that if you are not a programmer, with a template, is in How to write a website brief.
Step 7. Get an estimate and sign a contract
A good estimate is broken down by stages and features, not a single line saying “Website: $2,000”. It shows what is included, what is not, and what each stage costs.
The contract should cover at least:
- the scope of work, with the brief attached;
- stages, deadlines and the payment schedule;
- how the work is accepted;
- transfer of rights to the design and code;
- the domain, hosting and all accounts registered in your name.
The domain, hosting and admin access should belong to you from day one, not “after the final payment”.
Pay in stages tied to results rather than the full amount upfront. The key clauses are covered in A website development contract. If the contract is complex or the amount is large, show it to a lawyer.
Working on the project
Step 8. Prototype and design
Before anyone draws a polished design or writes code, it helps to see a layout of the main screens: what goes where and where each button leads. That is a prototype. Fixing it takes an hour; reworking a finished website takes days.
Review the prototype carefully and show it to colleagues or a couple of customers you know. The design is then built on top of it, and you approve that too. Why it pays to start with a prototype and a small first version is explained in Prototype and first version.
Step 9. Development with regular demos
During development, stay in touch and do not let the developer disappear either. Agree on regular demos of work in progress, for example every one or two weeks. That way mistakes show up early, not on delivery day.
Name one person on your side who makes decisions. When feedback comes from three managers at once and contradicts itself, the timeline will almost certainly slip.
New ideas mid-project are inevitable. Write them down and discuss them separately: some go into the current stage for an extra fee, others are better left for the next version.
Launch and life after it
Step 10. Acceptance and launch
Before the final payment, check the website yourself instead of taking anyone’s word for it. Open it on a phone and a computer, submit every form and make sure the requests actually arrive. Look for typos, check phone numbers and addresses, log in to the admin panel and try changing a price or adding a news item yourself.
Make sure you have received all access details and instructions. If you had an old website, redirects from the old addresses need to be set up, or visitors coming from search will land on empty pages. A detailed list is in How to accept a finished website.
Step 11. Support after launch
The work does not end at launch. The domain and hosting need renewing, the system needs updates, data needs regular backups, bugs need fixing and texts and prices need changing.
Agree in advance who will do this and how it is paid: hourly, a fixed monthly fee or on demand. NOVO, for example, stays on to support projects after launch, but whatever the arrangement, settle this question before delivery, not on the day the website stops loading.
In short
- Start with the goal and the visitor, not the design: they define the type of site and the scope.
- Gather materials and decide who makes texts and photos before development starts.
- Compare developers on the same brief and look at live projects, not screenshots.
- A contract, staged payments and a domain in your name protect you better than any promise.
- A prototype and regular demos catch mistakes while they are cheap to fix.
- Accept the website against a checklist and settle support in advance.