Solar Energy CRM
Selling solar does not end with one meeting; the consumption bill, the roof measurement, the sizing, the bid and the grid application spread over months. In that time prices change, the application waits its turn, and the customer does not remember which bid they last saw.
Roof area, consumption data and target installed capacity are fields on the project record; bid revisions are versioned, and a price past its validity date drops off the open list.
- Run rooftop and ground-mount projects through separate processes, and keep consumption data and target installed capacity on the opportunity record
- Version the bid together with its revisions, and stop a price past its validity date from staying on the open list
- Track connection application and contract dates as fields, and list the files awaiting an answer by date
- Set up a follow-up task and reminder sequence for projects that have been inactive for a long time
| Project Opportunity | Every solar project is an opportunity record; roof area, consumption data and target installed capacity sit in fields on that record. |
|---|---|
| Bid Version | A bid is a record with a validity date; revisions accumulate as separate versions, and a price whose term has expired drops off the open list. |
| Application Tracking | The distribution company application is a date field; the application date and the expected answer date are entered on the record, and overdue files drop into a list. |
| Follow-up Sequence | A contact sequence can be defined for a project that has gone quiet; when the number of days you set runs out, that definition supports opening a task for the person responsible and scheduling a message to the customer. |
In solar sales, the business you lose is not the business that was turned down, it is the business that was forgotten. The customer sends their electricity bill, the system is sized, a bid goes out; then the connection application is filed and an answer is awaited for weeks. During that wait the panel price and the exchange rate change and the bid goes stale; when the customer calls to ask where things stand, it is not even clear who has the file. On top of that, a bid given for a rooftop is not the same process as a ground-mount project, yet the two get mixed into the same list.
In Rapitek CRM every project is an opportunity record and its stages are set up to fit your process: survey, sizing, bid, application, contract. Consumption data, roof area and target installed capacity sit in fields on the record; bid revisions accumulate as versions and a price past its validity date drops off the open list. The application filed with the distribution company is a date field — it does not connect automatically to the application systems, your team enters the date — but once it is entered, files whose answer is overdue drop into a list according to that date, so no application waits in silence.
The scope of the plans and the separately priced items are written on the pricing page.
