What does a new website cost? Start with what it needs to do.
Page count alone cannot give you a useful answer. Two sites with the same number of pages may involve very different work: one presents information, while the other connects data, bookings or purchases. Here is what shapes the scope so you can ask better questions before seeking a proposal.
You do not need every answer; the first discussion by email is free.

What is the work behind a website?
Understanding the task.
Audience, content and what visitors need to do shape the structure. Without that work, it is easy to create a site that looks complete but does not help anyone move forward.
Designing and building the solution.
Design, responsive layouts, code, configuration, features and integrations take different amounts of work depending on what already exists and what needs to be created.
Making it usable in operation.
Content, accessibility work, testing, data migration, launch and optional ongoing maintenance all need a clear place in the scope.
Choices that often change the scope
A template or a custom solution?
A template can reduce some design and coding work when needs are simple and fit its structure. It does not remove the need for content, configuration, testing and adaptation. If the buying journey, identity or functions need a different form, a custom theme or another technology may be more suitable.
Information only, or functions too?
Booking, ecommerce, multilingual content, external data and migration need planning and testing beyond a straightforward information site.
Who will provide the content?
Copy, images, product data and translations affect the work. Even existing material may need to be reorganised for the new site.
What needs checking?
Accessibility and testing should be defined in concrete terms: which parts, which methods and who receives the results. A broad promise is not a project scope.
When does it need to be ready?
The schedule, priority, number of decision makers and speed of material and feedback all affect delivery.
An example of the work behind a store
With B2B Care, we built PC Poznań's WooCommerce store with a custom theme, adapted checkout and product data synchronisation. See how design, code and data flows came together in the store.
Questions that help you get a useful proposal
Do I need a finished specification?
No. Describe the goal and what you know. We can define the scope during our discussion.
Can a ready-made theme cost less?
In some projects, yes, if it fits the content and functions. Adaptation, content and future changes still need to be considered.
How many hours will it take?
We can estimate once the content, functions, technology and responsibilities are clear. A number before that would be misleading.
What should a proposal include?
The agreed deliverable and responsibilities. We describe design, development, content, testing, launch and optional maintenance insofar as they are part of your assignment.
How to get an answer for your project
Tell us what the website should help you achieve. A link to your current site, required functions and preferred start date can help, but none is mandatory. We discuss the need by email before estimating.
