Starter
For presenting a brand, service, product or project professionally, with core pages, responsive design, an enquiry form and essential SEO foundations.
€1.295A useful website budget starts with the job the site needs to do. Introducing a business, publishing a multilingual service library and connecting customer enquiries to an internal system are different projects. This guide explains the current catalog options and the decisions behind a tailored quote, so you can compare scope rather than a headline price alone.
For presenting a brand, service, product or project professionally, with core pages, responsive design, an enquiry form and essential SEO foundations.
€1.295A broader content structure, editable areas, advanced forms, multiple languages or core integrations, built around conversion.
from €2.450Custom functionality, dashboards and third-party integrations, advanced interaction, membership, booking or payment capabilities.
Quoted to scopeB2B prices; VAT / BTW excluded.
The number of pages matters, but the number of distinct page types is often more important. Several service pages using one consistent structure can be simpler than a small site containing a product catalog, booking flow and member area. We first map the main visitor journeys, then decide which information needs its own page. This avoids paying for empty pages or hiding important information inside an overloaded homepage.
A multilingual site involves more than a language switch. Navigation, page addresses, metadata, forms and contact messages need coherent counterparts. The scope depends on how many languages you need, who provides approved translations and how new content will be maintained. We agree which language versions are ready for delivery and which require your review. Automatic translation is not a substitute for checking important commercial or legal text.
A basic enquiry form and a form connected to a CRM have different technical requirements. Integrations require access arrangements, field mapping, validation, error handling and checks when a provider changes its API. Before including an integration, we identify the actual data flow and the people responsible for the external account. Existing subscriptions or paid provider services remain separate unless the written scope explicitly includes them.
A management panel should solve a recurring operational need, such as editing content or following up enquiries. It also introduces user permissions, stored data and maintenance responsibilities. Booking, membership and payment features require their own discovery rather than being treated as decorative additions. We distinguish a straightforward public website from an internal application and propose a smaller first version when that makes the project easier to operate.
An assistant is a separate functional component with approved knowledge, usage limits and ongoing operating costs. The website quote does not silently include it. If it is relevant, we describe the questions it should handle, the information it may collect and the point at which a person should take over. The assistant catalog separates setup from recurring use; a broader connection to internal systems requires its own scope discussion.
The quote needs to say whether you provide final text, images and brand materials or want help preparing them. Copywriting, translation and custom production are different work from implementing a supplied design and content set. We also agree what you receive at handover, which accounts belong to you and which third-party licenses have their own conditions. Clear ownership makes future changes less dependent on a particular supplier.
Delivery and ongoing support are separate decisions. A site may need content updates, technical maintenance or additional functionality after launch. We agree what is included in the initial handover and how later requests are handled. Hosting, domain renewals and external subscriptions should be visible in your operating budget. No unlimited support, fixed delivery deadline or ranking outcome is implied by the catalog price.
It suits a clearly bounded presentation site with essential pages and an enquiry route. More content, editable areas or connected systems may call for a broader option. We check the actual requirements before recommending one; the lowest catalog option is not presented as the price of every possible website.
Custom workflows depend on data, permissions and external systems that cannot be assessed from a page count alone. An individual quote describes those dependencies and what will be tested. It is more useful than fitting an unknown project into a package whose limits become apparent only during development.
Yes, provided the first version is chosen with the likely next step in mind. Tell us about expected languages, content updates and integrations early. We can identify what is sensible now and what can wait, without promising that every future change will be effortless or already included.
Only when those items are explicitly listed. Building the site, hosting it and maintaining it are separate responsibilities. The proposal should make any recurring charges and external accounts clear, so you can compare both initial work and the practical cost of keeping the site running.
Describe your business, target audience, desired languages and the action visitors should take. Share existing content and mention any systems the site must connect to. A list of priorities is more helpful than an exact technical specification; we can clarify the missing details together.
Yes. The service is delivered remotely worldwide, with Europe and Türkiye as the main markets and particular attention to the Netherlands and Germany. Language, working arrangements and project responsibilities are agreed for your situation. This does not imply a local office or branch in your country.
Zekvion works remotely with organisations worldwide, with a practical focus on Europe and Türkiye, especially the Netherlands and Germany.
Discuss your project