Knowledge base/Implementation/How long does a typical Weaver implementation take?

Context

There is no honest one-size-fits-all answer, but there are honest ranges. The question is usually really 'when can we start getting value?' and that has a more concrete answer. We avoid big-bang implementations; the risk profile of 50-year asset programmes doesn't tolerate them.

Pilot operational in 8–12 weeks. Full programme deployment is a multi-year engagement.

Explanation

The typical engagement breaks into three phases:

Phase 1

Pilot (8–12 weeks)

Scope and reference data review, standard model deployment, first integration (typically Revit/IFC plus one structured-data source), one ISO 19650 workflow operational. End state: a single asset or sub-asset operating on Weaver with real data and real users.

Phase 2

Programme rollout (3–9 months)

Extend integrations across all source systems, train the first cohort of Certified Weavers, roll out the audit and approval workflows your teams use daily. End state: Weaver is operational across the programme; your team owns day-to-day operations.

Phase 3

Steady state (ongoing)

Weaver runs autonomously inside your environment. We stay engaged for major releases, ISO standard updates, and the occasional architectural review. Your Certified Weavers handle configuration changes.

We default to pilot-first because for assets that operate for decades, the cost of a confident decision is small and the cost of an over-confident one is large. Evidence before scale.