Collaboration stages
The website creation process, from defining goals to testing and launch.
Every project starts with the real needs of the business. We agree on what needs to be built, what is optional, which accounts we create together with the client and how the result will be checked before publication.
Overview
A clear process divided into six phases.
The exact order may vary depending on the project. Authentication, an admin interface, a database, checkout and payments are included only when required and explicitly listed in the proposal.
Phase 01
We define the desired outcome and the boundaries of the project.
Defining the goals
We determine what the website must achieve: present the business, generate quote requests, calls, messages, bookings, sales or a clearly prioritized combination. We define the audience, the area in which the services are offered and the visitor’s primary action.
Defining the required functionality
We separate essential features from optional ones. We assess pages, forms, integrations, languages, user accounts, content management, checkout and payments only in relation to the project’s goals.
Setting the price
The price is set after the structure and functionality have been clarified, based on complexity. The proposal states what is included, what is optional and which third-party services or costs are separate.
Phase 02
We prepare the project data, access and infrastructure.
Processing the data required for the project
We identify only the data required for the agreed setup. Depending on the project, this may include the name of the account holder or representative, the phone number, the service area and existing business email addresses.
This data may be required for the domain registrar account, hosting, business email, a dedicated Google Account and, if the business is eligible, management of the Google Business Profile shown on Google Maps. Before any setup begins, the project documents state why this data is needed, the responsibilities, the providers involved and the access required during the project.
Creating and managing the required accounts
CERB creates all accounts required for the project together with the client and manages them for the duration of the project. At handover, the client changes all passwords, or they are changed together with the client. The new passwords are known only to the client, CERB’s access ends, and the client assumes full management and control of the accounts. Recovery options and two-factor authentication are configured when available.
Choosing the domain
If a domain has not already been registered, we choose an option that is relevant to the brand, easy to recognize and available for registration. The domain is registered through an account created together with the client and then connected to the hosting platform.
Phase 03
We build the structure, interface and interactions.
Creating the page structure
We define the pages, sections and order of information. Navigation, headings, internal links and buttons are organized so visitors can understand the offer and easily reach the primary action.
Creating the design
We define the color palette, typography, layout, spacing and component styles. Transparency effects and transitions are used only when they preserve readability, contrast, performance and the user’s reduced-motion preference.
Adding JavaScript interactions
JavaScript is added when an interaction cannot be implemented properly with HTML and CSS alone. Menus, validation, filters and other interactive components must have clear states, keyboard support and a fallback appropriate to their role.
Phase 04 · Optional
We add dynamic functionality only when the project requires it.
These features are not automatically part of every website. They affect the project’s architecture, security, testing and cost and are explicitly included in the proposal.
If required
Administrator and client accounts
We implement account creation, authentication and user management when the project workflow genuinely requires identities and private areas. A payment does not automatically require a client account; the decision is based on the experience and data required by the service.
If required
Website management interface
We can build a protected interface where the administrator can edit the elements agreed as editable: images, copy, contact details, addresses, company information, the logo or other agreed data.
This option requires authentication, authorization and a database that manages accounts and dynamic content. The available actions and editable fields are defined before development.
If required
Checkout functionality
For projects that sell products or services, we can build the checkout journey: selecting items, checking information, clearly presenting the order and confirming the outcome. Success, cancellation and error flows are designed and tested separately.
If required
Payment processor integration
If the project includes checkout, we choose a payment processor suited to the business together and integrate it using its official methods. Sensitive payment data is not stored in the website code, and confirmations are validated through the provider’s secure flows.
Phase 05
We connect the website with people and make it usable in more than one way.
Forms and contact integrations
Depending on the project, we create contact forms, integrate Google Maps, add email links and click-to-call buttons, and build forms that prepare a message and redirect the user to WhatsApp. The destination of the data and the final sending step are explained clearly.
Screen reader compatibility
A screen reader is assistive software used on the visitor’s device. The website is prepared for interpretation through semantic HTML, page landmarks, headings in a logical order, form labels, text alternatives and accessible names for controls.
Keyboard navigation
Interactive features must be usable without a mouse, in a logical order and with visible focus. Menus and overlays provide a way to close them, and the interface does not rely solely on color, hover, motion or icons to convey information.
Phase 06
We audit the project before launch.
Testing covers both what visitors see and use and the technical information read by browsers, assistive technologies and search engines.
Account audit
We check that each account has the required details, the correct owner, recovery options and available security measures. During handover, we confirm that all passwords have been changed by or together with the client, that the new passwords are known only to the client and that CERB’s access has ended. Passwords and recovery codes are not included in the audit report.
Code and functionality audit
We test the navigation, links, forms, interactions, authentication, administration, checkout and payment features that exist in the project. We also check responsive rendering, keyboard use, focus, errors, performance and behavior in the browsers agreed for the project.
Copy and SEO information audit
We review visible copy, spelling, contact details and message consistency. We also check page titles, descriptions, heading structure, alternative text, canonical URLs, links between pages and structured data used by search engines.
Launch and post-publication support
Once the identified issues have been resolved and the final version confirmed, the website is published on the agreed domain. Websites built by CERB may include maintenance and optional 30-day monitoring, as specified in the project proposal.
Next step
Do you have a project and want to decide which stages apply?
Send us the goal, the type of business and the features you have in mind. The proposal is prepared after we separate the requirements from the options.