12 questions to ask a web studio before starting
Good questions save more than haggling over price. They surface mismatched expectations before they become a handover dispute.
Process and deliverables
What exactly is included — how many pages, which features, who writes the copy and prepares photos? What is excluded and what does it cost? How many revision rounds are covered?
What do the stages look like and when am I involved? What happens if the timeline slips? A good answer is specific with past examples; a bad one is 'individual approach'.
Technology and ownership
What will the site be built on and why for my case? Can I edit text, prices and pages myself? Who owns the domain, hosting and source code after handover?
'It will be on our platform' means you cannot leave and will pay indefinitely. That can be acceptable — but the decision should be conscious.
Marketing and support
What SEO work happens during development? Who sets up analytics and goals? Will the Uzbek version be complete and how are language versions linked technically?
What is covered by warranty, what does post-launch support cost, and how fast do you respond if the site goes down on a weekend?