We create digital solutions that work for businesses
An unsuccessful website often begins with an unclear agreement rather than poor design or code. The client expects a sales tool, the supplier interprets the job as a set of pages, and both sides later dispute whether content, integrations, mobile layouts, and SEO were included.
A business does not need to write a hundred-page technical specification alone. It needs to define goals, audiences, journeys, scope, acceptance criteria, and ownership. This guide helps you prepare for a studio discussion, compare proposals, and accept a completed website using evidence rather than personal taste.
“We need a modern website” does not define what should change after launch. Choose the primary job: generate enquiries, sell products, present services, automate bookings, attract partners, or support existing customers.
Write the model in one sentence: who should visit, what action they should complete, and how the business will measure success. For example: “Apartment owners in Kyiv should choose a renovation service, review examples, and submit an enquiry; success is measured by qualified leads attributed to the website.”
| Question | Weak answer | Useful project answer |
|---|---|---|
| Who is the website for? | Everyone | Small-business leaders comparing suppliers |
| What is the main action? | Learn more | Submit a brief or book a consultation |
| What are we selling? | Our services | Three packages with different scope and timelines |
| How will we measure success? | More customers | 30 qualified monthly enquiries with tracked sources |
If the format is unclear, explore business website development. A catalogue, checkout, payment, and delivery require dedicated online store planning, while one campaign hypothesis may only need a landing page.
A brief captures the business context before estimation. It does not replace the specification, but it helps the studio propose the right structure and prevents unknown risks from being hidden in the quote.
List target actions: calls, forms, orders, payments, registrations, downloads, or messenger clicks. Define metrics the business can monitor, such as leads, sales, average order value, conversion rate, acquisition cost, and website revenue. Use the guide to calculating website ROI to build a financial model.
Describe two to four customer groups: their job, decision criteria, objections, and required information. Then outline short journeys covering the traffic source, first page, comparison points, and final action.
Prepare a list of services, categories, products, regions, languages, and content types. Assign responsibility for copy, photography, prices, legal pages, and translations. “Content will come later” almost always affects structure and timing.
Share three to five links and explain what is useful: catalogue logic, price presentation, selection flow, or photography style. Do not ask for a copy; the solution should match your own sales model and brand.
State the target date, budget range, existing domain, hosting, CMS, CRM, accounting system, and mandatory integrations. A launch tied to a season or campaign must be known before the schedule is agreed.
The specification turns a need into a testable scope. It may be a document or a set of approved prototypes and requirements, but every deliverable needs a clear acceptance criterion.
Define page types, menu depth, filters, search, breadcrumbs, and language relationships. For a large website, focus on templates: service, category, product, article, author, or location pages.
Describe forms, accounts, basket, payments, delivery, booking, import, and notifications. For each feature, identify the user, input, expected outcome, and errors that must be handled.
“Connect the CRM” is not precise enough. Name the system, fields, transfer direction, lead creation rules, duplicate handling, and access owner. Apply the same detail to payments, delivery, telephony, and email platforms.
Agree on the concept, prototype, key templates, responsive states, and review rounds. Test readability, contrast, forms, keyboard navigation, and small screens—not only visual style. WCAG 2.2 is a practical accessibility reference.
The scope should include editable titles, descriptions, H1s, canonicals, alt text, Open Graph data, sitemap, robots.txt, redirects, and indexing rules. Define analytics events for CTAs, forms, phone links, messengers, basket actions, and payments. Establish the foundation with SEO services before development is complete.
Agree on supported browsers, image optimisation, caching, HTTPS, backups, and recovery. Core Web Vitals cover loading, responsiveness, and visual stability, but acceptance should not be reduced to one laboratory score.
Replace “works correctly” with measurable outcomes: a form sends data to the CRM and displays confirmation; test payment succeeds; the order has the correct items and total; pages work on agreed devices; an editor can change content without a developer.
Compare the work breakdown rather than one total. Two “corporate website” proposals may include different levels of research, prototypes, templates, content, integrations, testing, and support.
| Budget area | What to clarify |
|---|---|
| Discovery and prototype | Interviews, sitemap, journeys, number of prototypes |
| Design | Unique templates, responsive states, review rounds |
| Development | CMS, modules, roles, integrations, migration |
| Content | Copy, photography, translation, population |
| Testing | Devices, browsers, forms, payments |
| Launch | Domain, hosting, SSL, analytics, sitemap, redirects |
| After launch | Warranty, support, backups, SEO |
Use BB STUDIO pricing as a reference, but request an estimate for your scope. A 10–20% reserve can cover new ideas; mandatory integrations should not be hidden under “extras”.
The agreement should define scope, stage deliverables, working and review timelines, cost, change control, warranty, confidentiality, and rights. Identify who owns the domain, hosting, repository, design files, licences, and service accounts.
Link payments to visible outcomes: discovery and prototype, design, development, testing, and launch. Scope changes receive a separate estimate with their budget and timeline impact. Read freelancer versus web studio for a broader comparison of delivery models.
Final acceptance covers the complete business journey, responsive behaviour, configuration, and account handover.
Follow a customer path from advertising or Search to an enquiry or payment. Test forms, emails, CRM records, order statuses, and mobile interaction. A website is ready when the complete journey works, not simply when the homepage loads.
Verify contacts, prices, company details, languages, buttons, links, and form errors. Ensure the primary action is visible and banners do not cover content. The Design and UI/UX section provides more guidance on identifying user barriers.
Open the free website tools and run an independent baseline check:
These checks do not replace full QA, but they give the client independent visibility into important settings.
The business should hold access to the domain, hosting, CMS, analytics, Search Console, CRM, repository, and paid services. Request an editor guide, backup map, and warranty support contact.
Not alone. The client knows the business; the studio translates that context into structure, features, and criteria. Both sides should approve the result together.
Define review rounds for each stage rather than counting scattered messages. One consolidated list from the responsible stakeholder saves time and prevents contradictions.
Record the change separately, including its scope, cost, timeline, and impact on approved work. That is normal scope management.
Content structure is needed before prototyping, while final material should ideally arrive before design is complete. Real copy and images affect blocks, page length, and responsive behaviour.
Content growth can continue later, but URL structure, metadata, canonicals, sitemap, performance, and analytics should be built into the foundation.
Commissioning a website is a managed business project: a clear outcome, defined scope, staged deliverables, testable criteria, and transferred ownership. This approach makes proposals comparable, protects the budget, and produces a working sales channel rather than a collection of pages.
Explore the BB STUDIO portfolio or send a short project outline to receive a proposed structure and staged estimate.
Prepared by the BB STUDIO team. This article draws on our practice planning, designing, developing, and accepting business websites.
Web development
SEO
Design & UI/UX
Hosting & tech
Let’s create something amazing together Leave your number — we will call you back within 15 minutes during working hours.
We will call you back shortly.
