From an agreed direction
to a working platform.
This Implementation proposal builds on the approved Foundations phase. It covers the development and launch of Liapor's product website on Payload CMS and Next.js, with one shared platform and locally managed content.
(implementation) investment for CMS core and CZ + DE launch
33 760 EUR(844 000 CZK)
One-off implementation, excluding VAT.
Planned sequence: Czech launch, German launch, then further local versions. Scheduled CZ: 15 Dec 2026. DE: 26 Jan 2027. AT: 23 Feb 2027.
Ongoing care is separate, from 372 EUR (9 300 CZK) per month excluding VAT.
Proposal for review. The documented solution, final commercial scope and launch schedule must be aligned before acceptance. Foundations is not charged again in this offer.
A shared foundation.
Independent local teams.
Where we are
Payload CMS is the selected technology. Homepage V1 is the preferred direction. The current documentation describes the solution and links to design and megamenu prototypes. Final design and specification approval remain to be confirmed.
What this delivers
A consistent product platform that local teams can maintain themselves. Shared components and product structures support local content, product availability, navigation and SEO settings.
The documentation is the technical reference. Its existence does not by itself confirm that every feature is approved and included in the implementation price.
Solution specification & documentationBuilt once.
Managed market by market.
(01) platform
A website your editors can run.
Next.js and React power the responsive frontend. Payload CMS provides content types, a library of reusable blocks and Live Preview. Editors assemble pages from prepared sections; new block types or structural design changes require development.
The content model covers products, application pages, general pages, references, news, downloadable documents and shared media. Drafts, autosave, version history and three permission roles support everyday publishing.
(02) localisation
One CMS. Local decisions.
Manage local content, product availability and navigation within one CMS. System administrators, market administrators and editors have access appropriate to their assigned versions. Visitors switch to the equivalent local page when it exists.
The documented coverage contains 10 destination versions: EN, DE, CZ, AT, Swiss German, Swiss French, PL, HR, SI and NL. Hungary redirects to AT; Luxembourg and Belgium redirect to NL. These redirects are not three additional full versions.
(03) discovery
Find products. Start a conversation.
Local full-text search and combinable product filters help visitors find relevant content. Filter settings can be shared through the URL. Product enquiry and contact forms save submissions in the CMS and send localised confirmation and notification emails.
Local metadata, XML sitemaps, schema.org, hreflang and editable 301 redirects support search visibility. GTM connects GA4 and Microsoft Clarity; Google Search Console is configured separately. Consent choices control non-essential measurement.
(04) delivery
Test, launch and hand over.
The priced workstreams cover development, testing, project management, assistance with content entry, CZ launch, CZ SEO and redirects, analytics and consent setup, editor training, post-launch behaviour analysis, DE launch and DE SEO setup and redirects. The exact deliverables are subject to final scope alignment.
Testing covers the agreed functionality, responsive display, performance and release readiness. Image optimisation and responsive implementation support performance; no unverified Core Web Vitals score is guaranteed.
AI translation, integrations and scope boundaries
The documentation describes AI translation when copying a page into another version. Confirm its implementation scope, provider and consumption terms. The previously discussed MCP server is a separate, optional implementation detail, not an assumed launch requirement.
The architecture supports a future CRM connection. A completed CRM, PIM or DAM integration is not included unless expressly agreed. Existing product PDFs can be offered for download; a separate print version is not planned.
Migration and content responsibilities
Migration feasibility and scope depend on analysing each version's source data. References and news, including related images, are potential candidates for automated transfer. Complete automated migration of all pages is not promised.
Liapor supplies final text, photographs and product-to-application relationships. Copywriting and full content entry are excluded from the base price. Assistance with content entry is a separate priced workstream. The previous audit of 89 CZ pages is not an agreed migration volume.
What needs to be aligned before development
Confirm the version of the specification, remaining mobile and megamenu decisions, component list, migration scope, acceptance criteria and included local launches. A prototype or a preferred design is not the same as final approval.
The earlier reference to four included versions must be reconciled with the current budget and ten-version destination structure. Platform readiness for all markets does not mean all launches are included in the base price.
One-off build.
Ongoing care.
(01) implementation
33 760 EUR(844 000 CZK)
One-off, excluding VAT.
CMS core and the launch of the Czech and German websites.
Development & launch
28 040 EUR(701 000 CZK)- Frontend developmentComponents, responsive pages and agreed website functions9 600 EUR(240 000 CZK)
- Payload CMS coreContent types, localisation, permissions and Live Preview12 000 EUR(300 000 CZK)
- TestingAgreed functional and release checks1 800 EUR(45 000 CZK)
- CZ launchDNS, Cloudflare, indexation and launch checks1 200 EUR(30 000 CZK)
- CZ SEO setup and redirectsSearch transition for the Czech version1 400 EUR(35 000 CZK)
- DE launchRelease of the German version1 200 EUR(30 000 CZK)
- DE SEO setup and redirectsSearch transition for the German version840 EUR(21 000 CZK)
Measurement & optimisation
1 400 EUR(35 000 CZK)- Measurement and consent setupGTM, analytics and cookie consent configuration400 EUR(10 000 CZK)
- Post-launch behaviour analysisReview of user behaviour after release1 000 EUR(25 000 CZK)
Project support & training
4 320 EUR(108 000 CZK)- Project managementCoordination, reviews and delivery management2 600 EUR(65 000 CZK)
- Content-entry assistanceSupport for Liapor editors; not full content production720 EUR(18 000 CZK)
- Editor trainingFurther training tailored to your team, beyond initial onboarding1 000 EUR(25 000 CZK)
Further local versions
Additional investment per version. Not included in the implementation total.
- Launch of further local version (AT, PL, NL, EN...)Per additional version, excluding VAT480 - 960 EUR(12 000 - 24 000 CZK)
- SEO setup further versionPer additional version, excluding VAT360 - 720 EUR(9 000 - 18 000 CZK)
(02) ongoing care
592 EUR(14 800 CZK)
Per month, excluding VAT.
Optimum, recommended in the SLA proposal.
- Managed cloud hostingDaily backups and infrastructure operation
- Standard service and supportIncident handling under the separate SLA proposal
- Availability commitmentAt least 99.90% under the proposed SLA terms
- Two scheduled updates per year
- Monitoring and issue resolution
- Cloudflare FreeUnmanaged plan
- Translation service line includedUsage limits and provider terms require confirmation
Recommendation only. The selected service level is to be agreed with Liapor.
(implementation total for CMS core CZ + DE launch)
33 760 EUR(844 000 CZK)
One-off, excluding VAT. Includes the CMS core and the launch of the Czech and German websites, with development, testing, SEO setup and redirects, measurement setup, post-launch analysis, project support and editor training. Ongoing care and further local versions are separate.
Currency conversion follows the SLA offer: 1 EUR = 25 CZK. EUR prices are calculated from the CZK budget; CZK amounts are shown for reference.
Excluding VAT - payment schedule see below.
Further local versions and optional work
Further local versions are priced separately and are not included in the implementation total of 33 760 EUR. The following indicative ranges apply per additional version, excluding VAT:
- Launch of further local version (AT, PL, NL, EN...)Per additional version, excluding VAT480 - 960 EUR(12 000 - 24 000 CZK)
- SEO setup further versionPer additional version, excluding VAT360 - 720 EUR(9 000 - 18 000 CZK)
The final price within each range depends on the agreed scope for that version. Confirm the number of releases and whether both items apply to each destination.
Redirect-only markets are not automatically charged as full versions. Migration beyond the agreed scope, copywriting, full content entry, new integrations and additional development require a separate agreement. No total for all markets is implied.
Payment milestones
- 40% · before implementation13 504 EUR(337 600 CZK)
- 40% · after the Czech website launch13 504 EUR(337 600 CZK)
- 20% · after the German launch and delivery of the agreed scope6 752 EUR(168 800 CZK)
40% before implementation · 40% after the Czech website launches · 20% after the German website launches and the agreed implementation scope is delivered.
All amounts exclude VAT and are based on the implementation total of 33 760 EUR (844 000 CZK), using the fixed rate of 1 EUR = 25 CZK. Ongoing care and separately ordered additional local versions are billed separately.
Czech first.
Then a repeatable rollout.
(01) alignment
Confirm the delivery baseline.
Close the specification, design decisions, scope-price mapping and acceptance criteria. Agree content owners and handover dates before confirming the release plan.
Scheduled development start: 19 October 2026. See the detailed task dates below.
(02) CZ
Build and release the platform.
Create the CMS model, reusable blocks, product catalogue, permissions and frontend. Prepare content, analyse migration data, train editors and verify SEO, redirects, measurement and hosting before launch.
Scheduled CZ launch: 15 December 2026, according to the current development plan. Launch remains dependent on content readiness and release checks.
(03) DE
Validate the next market.
Prepare and approve German content, test localisation and release the DE version. Use this release to establish the repeatable process for subsequent destinations.
Scheduled DE launch: 26 January 2027.
(04) further versions
Roll out by local readiness.
Release the remaining agreed versions as content and local checks are completed. The current plan schedules AT for 23 February 2027 and further language versions for Q1-Q2 2027. Individual dates within that window remain to be agreed.
Move each released version into the selected care arrangement. [TO BE CONFIRMED: SLA commencement and phased-release billing]
The detailed schedule below follows the current development plan. Delivery depends on approved scope, ready content, consolidated feedback and completed release checks.
Ongoing care.
Three service levels.
The separate Liapor SLA proposal covers the ten destination versions. All options below are monthly and exclude VAT. Choosing a care level does not change the selected implementation technology.
| Service level | Key differences | Monthly |
|---|---|---|
| Minimum | Basic monitoring. Cloudflare Free, unmanaged. No contractual uptime guarantee. | 372 EUR(9 300 CZK) |
| OptimumRecommended | Monitoring with issue resolution. Cloudflare Free, unmanaged. At least 99.90% uptime under the proposed terms. | 592 EUR(14 800 CZK) |
| Premium | Monitoring with issue resolution. Managed Cloudflare PRO. At least 99.90% uptime under the proposed terms. | 832 EUR(20 800 CZK) |
All levels include cloud hosting with daily backups, standard service and support, two scheduled updates per year and monitoring. Service scope and incident terms follow the separate SLA proposal and the final agreement annex.
Hosting, ownership and service boundaries
The documented operating model uses (ant)-managed Hetzner Cloud and Docker. (ant) operates the server, deployments, security configuration, backups and monitoring. Liapor retains ownership of code, data and backups.
The SLA distinguishes Category A incidents, where the application or a key part is unusable, from Category B incidents, where it remains usable with limitations. Response and resolution conditions are defined in the separate proposal.
Minimum has no contractual availability guarantee. Availability commitments apply only under the selected and agreed SLA. Major upgrades and new feature development must not be assumed to be included in routine updates. [TO BE CONFIRMED: major-upgrade terms]
Licences and automatic translations
Premium already includes 100 EUR (2 500 CZK) per month for five Cloudflare PRO licences. This amount is included in the 832 EUR (20 800 CZK) total, not added again. Confirm which domains the five licences cover.
Each level includes a 20 EUR (500 CZK) monthly line for automatic translations. Confirm the provider, consumption allowance and any excess charges. This service line is separate from building the AI translation workflow; unlimited usage is not promised.
Proposed term and final agreement
The proposal provides for an indefinite term, a minimum commitment of 12 months and a three-month notice period after that minimum term. These are proposed conditions, not an executed agreement.
The final scope and prices are to be recorded in the agreement annex. Existing services should be reconciled to avoid duplicate billing. No unverified discount is applied.
Clear ownership.
One feedback stream.
The (ant) team
Ondřej Průcha leads project management and the client relationship. Jan Mrvka supports business development. Tomáš Frank is Head of Development. Delivery is supported by a dedicated senior lead developer and a senior technical supervisor.
The Liapor team
Daniel Eichhorn, Pavel Bursík and Bernd Hörbinger form the decision-making group. Jitka Faktorová is a support decision-maker. Matthias Stock is an independent marketing manager. Liapor provides final copy, images, product relationships and one consolidated response across markets.
Working rhythm and change control
Use the shared Asana project, weekly check-ins and monthly reviews. Consolidate feedback across markets before handing it to the delivery team.
Proposed change process: record the request, assess its scope, price and schedule impact, then obtain agreement before implementation. This process is proposed for confirmation.
Dependencies to settle before release
The release baseline requires approved designs and scope, ready local content, an agreed migration plan and completed acceptance checks. Agree the responsibilities, deadlines and review cycles for these inputs.
Where content, designs or feedback arrive later than agreed, review the affected release milestones together before committing to revised dates.
From build
to launch.
Development, content and release preparation, followed by a phased market rollout. Start and finish dates follow the updated development plan.
Planned kick-off19 Oct 2026
Indicative rollout · Q1-Q2 2027
Individual releases to be scheduled.
Experience you can review.
Siemens and Rako are established (ant) client references. Siemens provides a relevant example of a corporate website. Rako brings a building-materials context; specific project scope can be discussed separately.
Let’s confirm the next step.
Confirm the implementation scope, EUR prices, launch plan and preferred SLA level. We can then close the proposal and prepare the delivery baseline.
Ing. Ondřej Průcha
Offer validity: [TO BE CONFIRMED: validity period].