Questions about a Belgium-connected website or software project

Must every page be available in four languages?

The language scope follows the actual audience, required information and review capacity. We identify complete tasks rather than count translated homepages. An unavailable version needs an accurate explanation and a useful alternative; it should not silently become a different service.

What language will we use for development?

Technical discussions and delivery are in English. Dutch, French and German publication needs agreed sources and appropriate reviewers. Customer support languages are a separate operating decision, not something established by a language selector.

Can the current content system stay?

Often the first question is whether it already supports the needed relationships and editing controls. A broken switch or unclear review state may be repairable. A replacement needs evidence that its benefits justify migration, retraining and the recreation of useful existing routes.

Is a translation approval valid after the source changes?

It must remain tied to what was actually reviewed. Publishing workflow work can identify the affected version and related surfaces. The authorized owner decides whether older published wording remains accurate while a new version awaits review.

Can a customer belong to more than one organization?

A portal can be scoped for that arrangement, with explicit membership and access rules. The selected organization, document list and direct download checks must agree. An email address or language choice is not enough to establish permission.

Can you connect the site to invoicing or payment tools?

We can investigate the supported technical exchange and its account requirements. Your accountant and providers determine the applicable invoicing and payment arrangement. The work must distinguish a draft, issuance, transfer acknowledgement and payment state; none can be inferred merely from a browser return.

Does an EU-hosted site settle all data-handling questions?

Hosting location is one part of the arrangement. Access, providers, information collected, retention, support and any transfer requirements still need assessment by the appropriate people. We implement the agreed technical controls without declaring a general compliance result from a hosting label.

How are private reviews tested?

With fictional records, isolated environments and suitable provider test facilities. We inspect errors, changed requests, ordinary-role access and separate records that should remain unchanged. Real customer messages, payments and invoice issuance are excluded from a development rehearsal.

Can a focused AI feature be included?

Where it has a defined task, permitted sources and a useful review method. A search or draft assistant should expose what the responsible person needs to verify. It does not authorize a commercial decision or make untranslated or unapproved content publishable.

What determines price, timing and later support?

The included tasks, languages, source condition, provider capabilities, access, review and handover. Scope factors and working responsibilities explain those decisions. Send one current example so the first proposal can be grounded in observable work.