25 questions to ask before ordering a website

The success of a website project is usually decided long before any code is written — at the stage of the first negotiations. A client who asks the right questions protects themselves from months of misunderstanding, unexpected extra charges and arguments in the spirit of "we never agreed on that". Drawing on the experience of hundreds of projects, we have collected twenty-five questions whose answers you must know before signing a contract. They are grouped into five stages: about your business, about the contractor, about the work process, about technology, and about life after launch. Next to each question we explain why it matters and which answer is a good sign.

The customer journey in Uzbekistan has changed: people first search on Google or Telegram, compare, and only then reach out. A business with no digital presence around ordering a website simply isn't part of that comparison — the customer never sees it. Below we examine the question from an entrepreneur's viewpoint: practical steps and the real logic of costs.

In short: what we'll cover

• ✓Questions for yourself: goal and outcome (questions 1–3)
• ✓Questions for yourself: audience and content (questions 4–6)
• ✓Questions for the contractor: portfolio and experience (questions 7–10)
• ✓The most important questions: who owns the code, domain and hosting? (questions 11–13)
• ✓Process questions: timeline and stages (questions 14–16)
• ✓Process questions: revisions and communication (questions 17–18)
• ✓Technology questions: platform and speed (questions 19–21)
• ✓Technology questions: security and integrations (question 22)
• ✓After launch: warranty and support (questions 23–24)
• ✓The final question: is the site ready to grow? (question 25)

Questions for yourself: goal and outcome (questions 1–3)

The first three questions are for you, not the contractor, because the answers define the whole project. Question one: what business problem must the website solve? "A beautiful website" is not a goal; "turning ad traffic into leads" or "looking credible in tenders" is. Question two: how will you measure success? Monthly leads, calls, catalog downloads — it must be a number. Question three: six months from now, what does the site have to be doing for you to consider the money well spent?

When a client arrives without these answers, the contractor also works on guesses: one expects a landing page, the other builds a portal. Clear answers become the backbone of the brief, make proposals easy to compare and protect you from chaotic scope creep of the "let's add this too" kind. One hour of internal discussion will be the cheapest and most useful hour of the entire project.

Most traffic in Uzbekistan comes from phones — so we test every solution first on an inexpensive Android over slow 4G. A site that feels fast on office Wi-Fi is not yet a result.

Questions for yourself: audience and content (questions 4–6)

Question four: who visits the site and how do they make decisions? A young audience expects fast answers on a phone; a corporate buyer looks for documents, certificates and details. Question five: where does the client arrive from — ads, Google search, a link on a business card? The traffic source changes the structure: ads need landing pages, search needs in-depth service pages.

Question six is the one most often forgotten: where will the content come from? Texts, photos, product data, team pictures — without them even the best design stays empty. Experience shows the most common reason projects slip is not code but waiting for content. Decide before the start: what you prepare yourselves, what you order from the contractor, and whether that work is included in the quoted price. Answering these three questions is what makes the project timeline real.

Questions for the contractor: portfolio and experience (questions 7–10)

Question seven: do you have projects similar to our niche? Ask for working links, not screenshots, and open them on your own phone: do they load fast, are they usable? Question eight: what exactly did you do on those projects? Some contractors show other people's work — clarify "was the design yours, was the code yours?". Question nine: can you share contacts of two or three past clients? A good contractor does not dodge this, and dodging is itself an answer.

Question ten: who is on the team and who will handle my project? With a freelancer one person does everything — cheaper, but if they fall ill or disappear, the project stops. In an agency the designer, developer and project manager are separate people — more expensive but more stable. Either can be the right choice; what matters is knowing in advance whom you are working with and what happens if that person becomes unavailable.

The most important questions: who owns the code, domain and hosting? (questions 11–13)

Question eleven may turn out to be the most expensive line in the contract: whose property will the website code be? Some contractors keep the code, binding you to them forever: every change goes through them, and if you try to leave, you lose the site. The correct answer: after full payment the code is yours and is handed over together with the source files. Question twelve: in whose name is the domain registered? Only yours — this is non-negotiable, because the domain is your brand itself.

Question thirteen: who holds the hosting and will I have access? A site living on the contractor's server is a site under their control: in a dispute, access can be cut off. Good practice: hosting on your account, with the contractor holding working access. Get written answers to these three questions and put them into the contract — one sheet of paper today spares you the biggest problems of the future.

Process questions: timeline and stages (questions 14–16)

Question fourteen: what stages is the project divided into, and what will I see at each one? A professional process looks roughly like this: analysis and brief, design mockup, development, content loading, testing, launch. Every stage must end with a demonstrable result — that way problems surface early, not at the end. Question fifteen: what is the total timeline and what does it depend on? The answer "ready in a month" inspires less confidence than "design takes two weeks, plus your approval time on top".

Question sixteen: how are payments split? Common practice is staged payment: an advance at the start, a second part after design approval, the balance after delivery. One hundred percent prepayment is a risk; paying everything at the end is unacceptable for the contractor — no serious team will agree. A payment schedule tied to stages is the fairest scheme, keeping both sides disciplined.

Process questions: revisions and communication (questions 17–18)

Question seventeen prevents half of all project disputes: how many revision rounds are included in the price, and what do extra ones cost? Beware of a contractor promising "unlimited revisions" — that is either inexperience or a promise that will later be paid for with quality. Healthy practice: two or three revision rounds per stage, anything beyond estimated separately. It is also important to agree on what counts as a "revision": swapping a color is one thing, rebuilding a page's structure is another.

Question eighteen: how is communication organized? Whom do I write to, how fast do answers come, how often do I get a status update? A good contractor has a system: a short weekly report, one responsible contact, agreements confirmed in writing. A project's greatest enemy is silence: two weeks of quiet usually means the work has stalled. When communication rules are agreed at the start, nobody has to live on guesses.

Technology questions: platform and speed (questions 19–21)

Question nineteen: what technology will the site be built on, and why that one? It does not matter whether the answer names WordPress, Next.js or something else — what matters is that the choice is justified by your task. For a blog and a simple corporate site WordPress is enough; when speed, security and unique features are critical, custom development on modern frameworks is stronger. The answer "we only work with this" is a sign that you are being fitted to the technology rather than the technology to you. Question twenty: will I be able to manage the site myself — change texts, prices, news — or will every small edit require calling you?

Question twenty-one: how are speed and mobile adaptation guaranteed? A good answer is measurable: a PageSpeed score, loading time, a list of test devices. Ask about the future here too: can the site grow — if a new language, a new section or a store module is added, will everything need to be torn down and rebuilt? Good architecture may look excessive today, but two years from now it saves serious money.

Technology questions: security and integrations (question 22)

Question twenty-two bundles several sub-questions: how are security and connections to external systems handled? Is an SSL certificate installed, where and how often are backups stored, how is admin panel access protected — these three form the minimal protection kit of any website. If an online store is planned, ask separately about payment systems: is Payme, Click or Uzum integration included in the price, and does the team have experience with them?

Raise the CRM topic here as well: where do leads from the site end up? In the simplest case — in email or Telegram; in a good setup — directly in amoCRM or Bitrix24, with a responsible manager assigned automatically. Even if you do not use a CRM yet, ask whether the site will be able to connect to one later — that keeps the door open for the next stage. Get the list of integrations in writing: what is included in the price and what is billed separately.

After launch: warranty and support (questions 23–24)

Question twenty-three: how long is the warranty and what does it cover? Bugs found after delivery — a form broken through the developer's fault, a crashed page — must be fixed for free during the warranty period. A healthy warranty lasts at least several months and is written into the contract. Clarify what the warranty does not cover — for example, changes you made yourself or outages of third-party services.

Question twenty-four: how does support work after the warranty, and what does it cost? A website is a living organism: updates, security patches and small changes are needed constantly. Learn the options: is there a monthly maintenance package, what does it include (hours, monitoring, backups), or is every request billed separately? One crucial point: if you decide to move to another contractor, will documentation and access be handed over in full? To avoid ending up in a "you can do nothing without us" situation, get this answer in writing.

The final question: is the site ready to grow? (question 25)

Question twenty-five ties the project to the future: who will develop the site after launch, and how? Who watches the analytics, who works on SEO, who fills the blog? Building a website is the start of a marathon, not the finish line. Reading Google Analytics 4 reports, reacting to Search Console issues, maintaining a content plan — these tasks need an owner: your team, the contractor, or a dedicated specialist. A site left without an owner becomes a statistic within a year.

What this list of twenty-five questions gives you is one thing above all: the ability to decide based on information rather than emotion. A good contractor is not afraid of these questions — on the contrary, they stand out by having ready answers. At Innosoft Systems every project begins exactly with finding these answers together: at a free consultation we analyze your goal, propose a transparent plan and fix every agreement in the contract. When your questions are ready, the conversation becomes productive.

Where the investment pays back

A website is not a showcase — it's the foundation of a sales channel. For a business it delivers these measurable results:

• ✓Ad efficiency grows: the same ad budget turns into more leads on a fast, reliable site
• ✓Organic traffic compounds: every customer from Google arrives without an ad fee
• ✓A trust signal: before a big purchase, customers research the company — a professional site shortens the path to a contract
• ✓Information 24/7: questions about price, address and services get answered on the site — the phone line frees up
• ✓Measurability: GA4 and Search Console show exactly which channel brings customers

Preparing to order a website: 8 steps

1. Describe the site's business goal and success criterion on one page
2. Define the audience profile and the main traffic sources
3. List the content: which texts and photos come from whom
4. Check the live portfolios of at least 3 contractors on your phone
5. Ask every candidate who owns the code, domain and hosting
6. Get the stages, deadlines and payment schedule as a written proposal
7. Clarify the number of revisions, the warranty and support terms
8. Put every answer into the contract, and only then sign

What affects the price and timeline?

In the budget, separate two kinds of costs: one-time (development, design, content) and recurring (domain, hosting, maintenance). A suspiciously cheap offer for ordering a website usually hides the second part or cuts quality (testing, security, documentation) — you'll pay the difference anyway, just at a higher rate. Insist that both cost types are written into the contract.

Solutions proven in practice

In website projects our choices serve speed and SEO — a beautiful but slow site doesn't work for business:

• ✓Next.js (React) — pages are rendered on the server, so Google reads them fully and indexes them fast
• ✓Core Web Vitals control: LCP under 2.5 seconds is written into the project spec
• ✓Image optimization: WebP/AVIF formats and lazy-loading — fast even on mobile traffic
• ✓Google Analytics 4 + Search Console: from day one you measure which page brings customers
• ✓Security: SSL, regular backups and updates are part of maintenance

Why work with Innosoft Systems?

When choosing a partner for ordering a website, look at the portfolio and the process. Innosoft Systems is an IT Park resident; the team has worked for 5+ years and our projects serve more than 700,000 users. Our main measure isn't technology but the client's business metric: number of orders, cost per lead, revenue growth. That's what goes into the contract.

What to expect from the partnership

• ✓A free initial analysis and a line-by-line estimate
• ✓A solution built on modern, well-documented technology
• ✓Payme, Click, CRM and other needed integrations
• ✓Delivery with GA4 and Search Console configured
• ✓A contract guarantee and constant communication

Questions & answers

Wrapping up

A practical tip: before starting work on ordering a website, write down one number — what one customer costs you today (ad spend / number of customers acquired). Recalculate it in six months. The argument about whether the project works is settled not by feelings but by those two numbers.

The final math is simple: built right, ordering a website becomes an asset, not an expense — it delivers customer flow, saved working hours and a measurable result. Built wrong, you pay twice: first for a solution that doesn't work, then for rebuilding it. So before starting, fix the goal and the metric — the rest can be done in stages with an experienced team.