The connected platform

One relationship. Two purpose-built experiences.

The customer keeps their own ClickSabi account. The provider keeps their own ClickSabi Pro workspace. A project relationship carries the right information between them, and nothing crosses it without permission.

The architecture

You keep your own account. Your provider keeps theirs. The project is what connects them.

Customer experience

Proposals, comparison, research and the projects shared with them.

Relationship

The connection itself. It carries only what the provider shares, under its permissions.

Provider workspace

Design, proposals, delivery, scheduling, payments and service in ClickSabi Pro.

01 · Context survives the handoff

An accepted proposal does not become a fresh start.

The proposal a customer accepts stays attached to the project that follows it, so scope, pricing and terms remain part of the same record instead of being rebuilt from memory in another tool.

Proposal, acceptance and project stay on one record. What the customer can see is still set by the relationship.

02 · Each side gets its own experience

Connecting joins a project, not two accounts.

A customer follows the work in language built for a decision. A provider runs the operation in a workspace built for delivery. The two sides do not see identical screens, and neither one gains access to the other's workspace.

Shared when it should be
Proposals, signed contracts, milestones, payment requests and status, warranties, and the documents, appointments or messages a provider chooses to share. The provider decides item by item, and permissions on the relationship control what opens.
Private when it shouldn't
Internal notes, team assignments, analytics and AI suggestions stay provider-side. Proposal analysis, comparisons, competing quotes, company research and Advisor conversations stay with the customer.

Connecting is optional, and ending a connection stops sharing while preserving the history.

03 · The relationship continues after installation

The connection is still useful once the system is running.

Warranty details, shared documents and service history stay attached to the same project, so a later question has somewhere to land. Care and service can continue around that relationship.

Customers can track their system and its paperwork on their own. A provider is not required for Asset Care.

Explore your side

Two experiences. Start with yours.

Homeowner

Understand the proposal before you sign, and follow the work after you do.

Business buyer

Evaluate commercial solar with the proposal, the numbers and the provider evidence together.

Solar provider

Run design, proposals, delivery, payments and service from one workspace.

Personal and Pro are separate account types. A personal account is not upgraded into Pro.

FAQ

Questions about the connection