Questions worth asking early.

A focused pilot commonly takes 10–18 weeks from discovery to review, depending on source readiness, site count, workflow scope and customer availability. A single connection or advisory engagement may be shorter; a multi-region deployment may take longer. We agree milestones and acceptance criteria during discovery.

Common sources include ERP, WMS and TMS environments, carrier feeds, telematics providers, scanners, APIs and scheduled CSV or SFTP files. Integration feasibility depends on available interfaces, data permissions, quality and cadence. We assess those conditions before committing to scope.

No. Meridian is designed to add operational workflow and analytics around the systems your teams already use. Source systems remain authoritative for their own records unless a specific integration agreement defines otherwise.

Yes. A site or workflow pilot can establish the operating measures, data mappings and user feedback needed for a larger rollout. Expansion planning considers local differences rather than assuming every site has identical processes.

We use access controls, secure transmission practices, operational monitoring and documented procedures appropriate to a B2B software service. Specific architecture, access, retention and customer obligations are reviewed during procurement and onboarding. We do not claim certifications that are not held.

Customers retain ownership of the data they provide. Meridian processes that data to deliver and support the agreed service. Contractual terms describe permitted processing, retention, access and deletion responsibilities.

Workspace roles are scoped to operational responsibilities and customer administration needs. During onboarding, account owners agree who can administer users, view site information and work on exception queues. Access should be reviewed when roles change.

Operational views are designed to adapt to current mobile browsers for common review and exception tasks. Exact device, browser and workflow suitability is checked during pilot testing; not every administrative action is intended for a phone.

Refresh frequency depends on the source and connection method. Event feeds may update as events arrive; scheduled files update after delivery and validation. Each view makes its freshness context available so teams can interpret timing appropriately.

Onboarding typically includes role-based walkthroughs, a working session for site leads, quick-reference material and time for frontline feedback during a pilot. The precise mix is agreed for the deployment and customer team.

Pricing is scoped to the operating footprint, selected capabilities, data connections, support requirements and implementation effort. We discuss those factors after understanding the use case rather than publish a misleading one-size price.

Weekday business support is available during Central European business hours, excluding public holidays. A critical production incident route is agreed during onboarding. See the support page for severity definitions and initial response aims.

We review the new workflow or site, any local process and data differences, training needs and support impact. Expansion is documented with agreed measures and responsibilities before work begins.