Answers before you scope a solar operations rollout.

Solar1 is being shaped around the operating record that connects lead intake, project delivery, finance, inventory, and service. During early access, the relevant workflows and boundaries are reviewed with each installer before configuration begins.

That is not assumed. The assessment identifies which records should live in Solar1, which familiar tools should remain, and where a controlled handoff is needed. The initial rollout is limited to workflows the team can map and validate with confidence.

Solar1 is primarily evaluated with growing residential installers, while shared commercial workflows can also be assessed. Project types, approval paths, records, and reporting needs are documented before anyone treats a workflow as part of the rollout scope.

It begins with a workflow assessment covering current records, owners, handoffs, exceptions, and control requirements. That discovery informs a proposed scope, and configuration work starts only after both sides understand what will be reviewed and validated.

There is no fixed schedule before discovery. Timing depends on workflow scope, data quality, integration boundaries, decision availability, and the number of roles involved. The assessment is used to define practical phases and acceptance checks for the specific team.

Training needs are scoped by role and rollout phase rather than treated as a generic handoff. Teams review their configured records and decisions, validate representative scenarios, and identify internal owners before a workflow is considered ready for wider use.

Potential connections are evaluated individually. The assessment documents the systems, supported records, direction of exchange, ownership, failure handling, and reconciliation needs before an integration is included in scope or described as available.

Migration can be scoped after the source data is reviewed. The team decides which active records and history are useful, maps required fields, plans cleanup, and agrees on validation checks. Some older material may be better retained as an archive.

Data quality is a shared implementation responsibility. Solar1 can help define mappings and review checks, while the installer provides source context, resolves ambiguous records, and names people who can approve results before migrated data is accepted.

Start with a workflow assessment request. Solar1 will review your company profile, operational priorities, current systems, and decision timeline to determine whether there is a suitable implementation scope for the present early-access stage.

Commercial terms are prepared after scope discovery. The quote can reflect workflow breadth, data migration, integration work, rollout phases, training, access requirements, and support expectations. Published evaluation material is not a binding project quote.

Yes. Relevant access roles, data handling expectations, review needs, and operational controls should be raised during evaluation. Any requirement that affects configuration, hosting, support, or approval must be confirmed in the proposed scope.