Choose a plan around the operation. The agreed commercial scope covers the workflows, data, delivery, environments, and responsibilities involved.
Compare three starting points, then define the actual commercial, technical, and delivery boundaries with the people responsible for the operation.
Prices are always under consultation. These packages describe operating models and additional work that can be scoped, not a published rate card.
Network system of record
For an operator or owner using Fiber and Field as the network system of record.
Tasks and embedded analytics are not included.
Coordinate the operation
For teams coordinating the network, work execution, and operational reporting.
Scale, governance and deployment
For larger environments that need governance, staging, SSO, or customer-owned infrastructure.
Prices are always under consultation. These tables and accordions describe what can be scoped around the three packages, not a published rate card.
Use the access that matches the work. Full users edit the licensed products, Tasks-only users complete assigned work, and Read-only users consume permitted data. Allowances are confirmed in consultation.
| Access | What they can do | Availability |
|---|---|---|
| Full Web/Mobile | Create, edit, approve or submit within licensed products. The same person can use the browser, tablet or phone without a second licence. | Dedicated SaaS and Shared SaaS |
| Tasks-only | Restricted access to Weezie Tasks and mobile Tasks for completion participants who do not require Fiber or Field editing. | Dedicated packages |
| Read-only | View, search and consume permitted records and dashboards, without operational changes or submissions. | Dedicated SaaS and Shared SaaS |
Fiber and Field stay together as the operational system of record. Tasks and embedded analytics are available in eligible Dedicated packages, not as separate products.
| Capability | Starter | Growth | Enterprise | Shared |
|---|---|---|---|---|
| Weezie Fiber | Included | Included | Included | Included |
| Weezie Field | Included | Included | Included | Included |
| Tasks and mobile Tasks | Not included | Included | Included | Not standard |
| Embedded analytics | Not included | Standard dashboards | Governed custom scope | Not standard |
| Standard API | Included | Included | Limits confirmed in consultation | Included |
| Application environment | Dedicated production | Dedicated production | Dedicated production, with staging confirmed in consultation | Customer workspace on shared services |
| BYOC eligibility | No | No | Eligible | No |
The distinction is resource isolation. Shared SaaS uses pooled Weezie services and infrastructure. Dedicated SaaS reserves a separate application environment for one customer. BYOC runs the dedicated application layer in the customer cloud. Setup and operating fees are confirmed in consultation.
| Operating boundary | What it is | Notes |
|---|---|---|
| Dedicated SaaS | A separate customer application environment and service stack, operated in Weezie-managed cloud infrastructure. | Dedicated production environment. Application operations managed by Weezie. |
| Shared SaaS | A customer workspace running on pooled Weezie application services and infrastructure. | Customer-specific workspace and access controls. It does not provide a customer-facing subtenant administration layer. |
| Customer Cloud, BYOC | Weezie deploys and operates the application layer in customer-provided cloud infrastructure. | Dedicated Enterprise scope. Customer cloud costs are separate. |
| Restricted on-premises | For air-gapped releases, restricted remote access, or non-standard infrastructure requirements. | Dedicated Enterprise exception. Release and support process defined in the statement of work. |
Prices are always under consultation. Package, users, deployment, and additional work are confirmed in the commercial discussion, not published as a rate card.
A commercial discussion can start from one priority workflow while identifying the records, teams, data, and future connections that affect the scope.
Discovery, data assessment, migration, configuration, integrations, enablement, validation, and rollout are reviewed as separate scope decisions.
Bring the priority workflows, operating constraints, data condition, integration boundaries, delivery needs, and responsible teams to a commercial discussion.