Configuration review
Edition, business model, timeline and regional requirements are checked for fit.
Choose the edition, launch setup, integrations and support level. The page then shows indicative guidance in the appropriate currency for the selected configuration.
The estimate reflects the selected edition, launch setup, integrations and support. A final proposal follows a review of the implementation requirements.
Review marketplace capabilities ↗Select the operating requirements to view an indicative implementation range.
The configurator reduces unnecessary back-and-forth, but the final proposal still confirms ownership, integrations, migration, delivery responsibilities and launch acceptance.
Edition, business model, timeline and regional requirements are checked for fit.
Included foundation, custom work, migration and third-party dependencies are separated clearly.
Milestones, responsibilities, support and payment schedule are documented before work begins.
Deployment, verification, handover and rollback expectations are agreed for launch.
The public estimator is guidance. Exact responsibilities and exclusions are written into the reviewed proposal.
No. It is an indicative range based on the selected configuration. Final pricing follows a requirement review.
Yes. The operating model should match the current business, while later contributor or integration capability can be scoped separately.
They are reviewed separately because storage, payment, email, PMS, API and other services vary by deployment.
Yes. Branding, domain, commercial policies and buyer-facing experience are configured for the purchasing business.