Solar CRM Pricing India: Plans, GST, and 3-Year Cost

Solar CRM pricing India buyers face should be compared as a controlled three-year ownership cost. A free plan, per-user price, or discounted annual total does not prove the required workflow, deployment cost, contract, support, or exit.

Quick answer: Solar CRM pricing in India must be compared as a three-year ownership cost. Normalize users, roles, billing, minimum seats, GST, implementation, migration, messaging, integrations, storage, APIs, devices, training, administration, support, renewal, and exit. Accept a plan only after critical requirements, limits, security, contract terms, pilot results, and usable exports pass.

The arithmetic in this guide uses first-party public observations checked on 10 August 2026. Prices, taxes, editions, limits, and terms can change. Refresh them before approval and record the exact page, currency, billing state, and date.

Solar CRM Pricing India: Dated Public Observations

The QuickEstimate pricing page, Zoho CRM pricing page, and Salesforce India pricing page are vendor-owned sources. They do not prove implementation effort, workflow fit, service quality, security outcome, or return.

Disclosure: SurgePV and QuickEstimate have a commercial relationship. QuickEstimate receives no automatic rank. Apply the same requirements, evidence, pilot, TCO, contract, and exit gates to every option.

Do not convert USD through an unstated exchange rate. Record the vendor quote currency, invoice currency, payment date, bank conversion, card or transfer charge, withholding question, GST, and accounting treatment.

Do not compare monthly and annual views in the same column. Record the displayed unit, billed frequency, commitment, renewal, proration, cancellation, refund, and user-change rules.

Define the CRM Before Pricing It

A plan is inexpensive only when it closes the buyer’s requirements without uncontrolled work. Define jobs, data, users, roles, integrations, security, service, and exit before calculating seats.

Classify users by work rather than title:

• Lead intake, consent, duplicate review, ownership, and assignment
• Sales qualification, calls, messages, tasks, appointments, and pipeline updates
• Site survey, photographs, documents, notes, location, and field follow-up
• Solar quotation, price, tax, finance, subsidy context, approvals, and revisions
• Design, shade, yield, electrical, engineering, and proposal handoff
• Procurement, installation, commissioning, warranty, service, and customer handoff
• Manager approval, forecasting, reports, exception review, and audit
• Administration, permissions, integrations, data quality, security, support, and export

Count named users, occasional users, managers, administrators, integration identities, API users, service accounts, portals, guests, and external partners separately. Confirm how the vendor licenses each class.

Record entities, branches, brands, territories, languages, currencies, tax registrations, teams, pipelines, products, price books, approval levels, and reporting structures. A single-company configuration may not fit a group.

Define the system of record for lead, contact, site, opportunity, quote, design, document, consent, activity, installation, warranty, and service data. Avoid two systems silently owning the same field.

The solar CRM software India guide covers product selection beyond price. The free solar CRM guide covers free-plan limits and operational risk.

Build a Requirement-to-Plan Matrix

For every requirement, label evidence as public, contract-confirmed, clean-account observed, independently verified, or unknown. Then classify the plan response.

Do not score a custom build as included. Do not assume an integration because both products publish API pages. Confirm authentication, objects, fields, events, rate limits, errors, retries, monitoring, support ownership, and commercial scope.

Require plan-specific proof for permissions, audit, exports, reports, automations, storage, API access, mobile apps, support, sandboxes, backups, retention, and security. Edition names can hide material limits.

Calculate Seat Scenarios Without Inventing Quotes

Use public arithmetic only where the observed plan, unit, minimum, and term support it. Keep taxes, discounts, add-ons, implementation, and future changes outside the base licence column.

QuickEstimate public Pro arithmetic

The observed Pro unit was ₹6,999 per user yearly with a three-user minimum. The table shows arithmetic, not an order form or future price.

At 25 users, the public page also directs buyers to Enterprise. Do not assume the Pro arithmetic is an available or preferred enterprise offer. Request a dated itemised quote.

The Free plan can be evaluated for one user and the displayed monthly proposal limit. Do not value missing requirements at zero. Price the workarounds, controls, exports, and later migration.

Zoho public annual-view arithmetic

The observed Zoho pricing page displayed monthly per-user INR units under its annual view. Multiplying by twelve gives an unchanged annual base before local taxes and other costs.

The page displayed Free for up to three users and said local taxes were additional. Verify the exact checkout, billing, support, user types, limits, add-ons, and contract before approval.

Zoho also describes team-user concepts and separate limits. Do not replace full licences with a cheaper role until the exact user can perform every required job.

Salesforce public unit arithmetic

The observed India page displayed USD per-user monthly units. Record one-year arithmetic in USD before conversion, tax, implementation, support, apps, storage, and other costs.

Starter showed monthly or annual billing for the cited observation. The other cited editions showed annual billing. Obtain the exact order form, SKU, currency, billing, support, and renewal terms.

The Salesforce for solar companies guide covers workflow and governance fit. The Zoho solar CRM guide covers its solar-EPC decision boundary.

Build a Three-Year TCO Workbook

Separate each row into known, quoted, estimated, and unknown. Keep source, date, owner, quantity, unit, currency, tax, escalation, confidence, and evidence link.

Use this structure:

Three-year TCO = subscription + implementation + migration + integrations + usage + devices + people + governance + support + renewal + exit + risk contingency

Do not subtract GST as an assumed credit. Show tax separately, then let qualified tax and finance reviewers determine treatment and eligibility.

Year 0: selection and deployment

Include requirements discovery, process mapping, security and privacy review, vendor diligence, contract review, pilot, configuration, custom fields, roles, permissions, workflows, reports, templates, and acceptance.

Price source inventory, cleanup, deduplication, consent mapping, migration design, test loads, reconciliation, attachments, history, archival, cutover, rollback, and post-cutover corrections.

Include integration discovery, credentials, mapping, connector licences, API access, build, test, error handling, monitoring, support ownership, and documentation. A working demo does not prove production durability.

Include training design, trainer time, user time, manager time, administrator time, adoption support, SOP updates, and temporary productivity loss. Separate vendor work from internal work.

Years 1 to 3: operate and govern

Include subscriptions, added or removed users, add-ons, usage, messaging, telephony, storage, APIs, connectors, devices, MDM, security tools, support, administration, reporting, data quality, and audits.

Price workflow and branch changes, new lead sources, integrations, vendor updates, connector failures, permission reviews, and incident response. Include backup or export tests and staff onboarding or offboarding.

Add scheduled renewal review, price change, currency movement, tax, payment fees, negotiated discount expiry, minimum-user risk, dormant licences, seasonal workers, and contractor access.

Exit or replacement

Include final exports, attachments, history, metadata, configuration, code, reports, consent records, audit data, archives, documentation, reconciliation, import to a replacement, parallel operation, and decommissioning.

Price vendor assistance, partner work, internal admin, security review, legal retention, deletion verification, account closure, connector removal, credential rotation, and support during transition.

Test exit during the pilot. A CSV of contacts is not a complete exit package when activities, files, relationships, history, consent, and configuration matter.

Price the Costs Outside the Seat

The licence is often the easiest field to observe. The expensive uncertainty sits in people, data, connectors, messaging, controls, changes, and exit.

Requirements and implementation

Price interviews, process maps, data model, roles, fields, pipelines, approval rules, templates, reports, automation, security, testing, deployment, and documentation. Separate required configuration from optional redesign.

Identify the implementation provider and contracting entity. Record rates, units, assumptions, deliverables, acceptance, changes, travel, tax, support, warranty, and handover. A vendor referral does not transfer accountability automatically.

Data cleanup and migration

Inventory spreadsheets, old CRM records, messaging exports, forms, documents, quotations, contacts, activities, and service records. Record owners, formats, duplicates, invalid fields, consent status, retention, and deletion duties.

Price profiling, mapping, normalization, validation, deduplication, enrichment, archive, test migration, error correction, final cutover, rollback, and reconciliation. Count records, attachments, relationships, history, and custom objects separately.

Messaging, calling, and lead sources

Price messaging-provider fees, templates, conversations, numbers, verification, telephony, recordings, storage, consent records, opt-outs, connectors, support, and changes. Do not infer a third-party rate from the CRM page.

For Meta, IndiaMART, website, referral, marketplace, telephony, WhatsApp, email, and other sources, price capture, mapping, duplicate control, consent context, assignment, retries, reconciliation, and support.

The Meta lead CRM guide covers connector acceptance. The IndiaMART lead CRM guide covers marketplace source and authentication boundaries.

APIs, connectors, and custom work

Confirm whether the chosen edition includes the required API. Record request limits, objects, fields, events, batch behavior, authentication, webhooks, errors, retries, logs, monitoring, support, and data direction.

Price every product involved. A connector can require CRM, source, automation platform, middleware, cloud, monitoring, security, and support subscriptions. It can also require ongoing administrator time.

Custom functions and applications create maintenance, regression, documentation, security, developer, testing, and replacement costs. Record ownership and source-code handover where applicable.

Storage, documents, and retention

Estimate structured records, attachments, photographs, call files, message files, quotations, reports, and audit data. Model growth, retention, archive, deletion, backup, restore, export, and legal hold.

Do not assume additional storage is included or available at the same unit. Obtain exact plan limits, overage, add-on, region, retention, and export evidence.

Administration, security, and support

Price user setup, permissions, role review, field changes, workflows, reports, integrations, data quality, support tickets, release review, testing, documentation, training, and audits.

Include identity, SSO, MFA, device, MDM, logging, monitoring, incident, vendor-risk, privacy, retention, deletion, backup, and business-continuity work. Public security claims are not independent assurance.

Support price must include scope. Record channel, hours, language, response, severity, escalation, named contacts, implementation support, integration boundary, premium plan, and renewal.

Downtime, errors, and workarounds

Estimate cost from duplicate leads, failed assignments, lost consent context, stale prices, quote errors, connector delays, sync conflicts, export defects, manual reconciliation, and unavailable reports.

Do not claim a productivity saving without a measured baseline and pilot. A faster step can shift work to administrators, reviewers, or another system.

Treat Public Vendor Statements as Evidence, Not Outcomes

QuickEstimate

The public price is a dated vendor statement. Its product, pricing, security, privacy, terms, and refund pages require a single written commercial and data interpretation before payment.

The pricing page displayed a 30-day refund statement. The public refund policy described a contact request within seven days and other conditions. Do not resolve that conflict by choosing the preferred sentence.

The public pages also require clarification across Free versus trial wording, annual billing, renewal, proration, backup scopes, and residency. Resolve login, transmission security, deletion, and contract-entity wording.

Review the QuickEstimate security page, privacy page, terms, and refund policy. Treat them as first-party evidence.

The QuickEstimate pricing analysis performs the product-specific contract and arithmetic review. This page uses QuickEstimate only as one CRM TCO input.

Zoho CRM

The pricing page displayed editions, INR units, annual and monthly controls, Free for three users, team-user information, support choices, migration offerings, and local-tax language. Verify the exact checkout and account region.

Use the Zoho CRM feature comparison to map edition limits. A feature name does not prove the buyer’s workflow, volume, connector, security, or support need.

Confirm user types, modules, automation, reports, APIs, storage, sandboxes, portals, mobile, support, migration, data location, privacy, export, contract, and deletion for the intended account.

Salesforce

The India pricing page displayed USD units and edition-specific billing statements. It did not make implementation, migration, apps, storage, connectors, messaging, administration, and Indian tax disappear.

Salesforce’s API edition guidance shows why plan names matter. Confirm exact SKU, API access, limits, apps, support, security, operating zone, contract, and order form.

Use the Salesforce export documentation to plan a test. Export frequency, permissions, fields, files, relationships, history, and configuration require exact-edition review.

Handle GST, Currency, and Procurement Separately

Keep supplier identity, GSTIN, place of supply, invoice, HSN or SAC, tax amount, payment, credit, foreign currency, withholding, and accounting questions in a qualified review track.

The GST taxpayer search manual provides an official verification route. Registration status does not decide the buyer’s tax treatment or input-tax-credit eligibility.

For each vendor, record legal supplier, contracting entity, billing address, tax registration, invoice currency, payment beneficiary, tax invoice fields, credit note, refund, and renewal. Match them before payment.

Show three views in the workbook:

1. Pre-tax operating and capital cost by evidence class.
2. Tax and transaction amounts before any assumed recovery.
3. Management cash flow after qualified finance and tax decisions.

Do not hide exchange-rate risk inside a converted list price. Use dated scenarios for currency, bank spread, card or transfer fee, taxes, and renewal.

Run a Costed Pilot Before Annual Commitment

Use representative users, roles, data, devices, lead sources, quotations, integrations, reports, and failures. A sales demo proves presentation, not production acceptance.

Define baseline measurements before configuration.

• Time and steps from lead receipt to owned follow-up
• Duplicate rate, missing-field rate, stale-owner rate, and unresolved consent context
• Quote preparation, approval, revision, design handoff, and customer-send time
• Manual entry, reconciliation, spreadsheet, messaging, and reporting hours
• Missed tasks, delayed responses, connector failures, sync conflicts, and support cases
• Administrator, manager, trainer, reviewer, security, and user time

Create pilot cases for website, referral, Meta, IndiaMART, manual, import, duplicate, invalid, withdrawn-consent, and reassignment events. Add lost, won, installation handoff, service, export, and account-closure cases.

Include device and failure cases. Test poor connectivity, duplicate webhook, connector outage, expired credential, permission denial, user offboarding, large file, special characters, wrong tax field, and retry behavior.

Measure results against fixed acceptance limits. Separate vendor-controlled time, buyer-controlled time, third-party time, and unknown delay. Do not adjust the score after the test.

Record pilot cost for subscriptions, implementation, migration, integrations, messaging, devices, users, administration, support, security, data cleanup, and remediation. Include internal labour.

Do not extrapolate a percentage saving from a small test without a defensible workload model. Report observed task results and the uncertainty around wider deployment.

The mobile CRM guide covers field-device acceptance. The CRM and quotation guide covers the lead-to-price and revision boundary.

Test Three-Year Sensitivity

Create low, base, and high cases. Change one assumption at a time, then run combined stress cases.

Calculate the break-even requirement in operational units, not an unsupported revenue promise. Example units include administrator hours, corrected quote errors, recovered assignments, or removed reconciliation steps.

Keep benefits and costs in comparable time periods. Do not count a one-time migration benefit every year. Do not omit recurring governance because it is internal labour.

Set stop conditions. Examples include a failed mandatory security gate, unusable export, uncontrolled consent loss, connector reconciliation failure, excessive administrator load, or unclosed contract conflict.

Contract Renewal and Exit Before Purchase

Obtain the order form, master terms, data terms, security schedule, support schedule, implementation scope, acceptable-use terms, price schedule, refund terms, and service-specific documents.

Confirm legal entities, services, editions, users, minimums, billing, term, renewal, price changes, taxes, payment, suspension, cancellation, refund, proration, downgrade, and added-user treatment.

Define implementation deliverables, source data, mapping, configuration, integrations, testing, acceptance, changes, defects, documentation, training, warranty, support, and handover.

Review confidentiality, data roles, processing, locations, subprocessors, transfers, security, access, encryption, retention, backups, deletion, incidents, audit, government requests, and business continuity.

Define availability and support evidence without inventing an SLA. Record channels, hours, severity, response, escalation, exclusions, maintenance, third-party connectors, remedies, and order precedence.

Before renewal, recalculate actual users, requirements, feature use, limits, add-ons, usage, support, admin, integrations, security, exports, service results, and replacement cost. Do not renew from the prior invoice alone.

For exit, require usable export formats, files, relationships, history, activities, consent, audit, configuration, code, reports, dictionaries, and documentation. Define timing, assistance, fees, retention, deletion, and account closure.

Test a restore or import into a neutral environment. File generation alone does not prove completeness, integrity, relationships, readability, or future use.

Use a Five-Pass Decision Rule

1. Requirements pass: critical jobs, users, data, integrations, reports, devices, and controls fit the exact plan.
2. Evidence pass: public claims, contract, clean-account pilot, and independent review are labelled and sufficient.
3. TCO pass: three-year known, quoted, estimated, unknown, tax, currency, people, risk, renewal, and exit costs are accepted.
4. Governance pass: security, privacy, consent, support, data quality, administration, audit, and continuity are owned.
5. Exit pass: exports, relationships, history, configuration, documentation, deletion, and replacement have been tested.

Reject or defer the purchase when a mandatory pass remains open. Do not average a failed security, contract, data, or exit gate into a high feature score.

SurgePV is not a CRM. Budget solar design software, shadow analysis, generation and financial modelling, and proposal software as separate technical layers when required.

Audit Users and Licences Each Quarter

Start with a roster, not the vendor invoice. Record person, entity, location, manager, job, role, plan, licence type, start, last activity, integrations, approvals, and offboarding status.

Classify each account:

• Active named user performing plan-required work
• Manager or reviewer needing reports, approvals, or audit access
• Administrator changing configuration, security, integrations, or data
• Integration or service identity with documented purpose and owner
• Temporary, contractor, partner, portal, guest, or team user
• Dormant, duplicate, shared, departed, suspended, or unowned account

Do not share named licences to avoid seat cost. Shared access weakens identity, attribution, permissions, offboarding, investigation, and audit. Confirm vendor licensing and security rules.

For every cheaper role, test the actual job. A limited user may view data but fail record ownership, reports, automation, integrations, approvals, or administration. Price the operational workaround.

Reconcile the roster with the vendor admin console, identity provider, HR record, branch list, connector list, and invoice. Investigate every mismatch.

Review licences before hiring, transfer, leave, contractor change, branch closure, plan renewal, and integration deployment. Remove access through a controlled offboarding process.

Track cost per active user, qualified lead, accepted quote, completed handoff, and administered workflow only when definitions are stable. Do not treat correlation as product-caused improvement.

Accept Implementation Through Evidence

Define deployment stages and acceptance artifacts before work begins. A configured screen is not an accepted production system.

Requirements acceptance

Approve user stories, data definitions, system boundaries, roles, permissions, consent context, lead sources, duplicates, pipelines, quotations, design handoff, reports, integrations, security, retention, support, and exit.

Record exclusions and later-phase work. Do not let a missing requirement become an unpriced implementation assumption.

Configuration acceptance

Require a configuration register for entities, modules, fields, validation, layouts, pipelines, statuses, roles, sharing, automation, templates, reports, dashboards, integrations, notifications, and retention.

Each item should identify requirement, owner, environment, change, tester, result, release, and rollback. Protect production changes through approval and regression tests.

Migration acceptance

Reconcile source counts, target counts, rejected rows, duplicates, owners, relationships, attachments, activities, consent, dates, values, and samples. Keep the error log and approved disposition.

Test rollback and archive access. Confirm that users can find the history needed for operations, disputes, warranty, service, reporting, and legal retention.

Integration acceptance

Test normal, duplicate, late, malformed, missing, unauthorised, rate-limited, retried, and failed events. Reconcile source, middleware, and CRM counts.

Confirm logs, alerts, owners, support boundaries, credentials, rotation, documentation, downtime procedure, replay, and recovery. Price unresolved defects and monitoring effort.

Production acceptance

Run user acceptance, permission, security, device, report, load, backup or export, support, and offboarding cases. Close defects or document an authorised residual risk.

Link implementation payment to accepted artifacts. Retain enough value to secure documentation, correction, training, and complete handover.

Operate a Monthly CRM Cost Register

The finance owner should not wait for annual renewal. Record monthly subscriptions, users, add-ons, usage, messaging, telephony, storage, APIs, connectors, cloud services, support, contractors, and internal labour.

Compare actuals with the approved TCO model. Explain variance through volume, price, currency, tax, users, implementation, defects, change requests, integrations, support, or policy decisions.

Use one owner for each variable.

Flag unused licences, unowned integrations, rising errors, manual reconciliation, failed exports, and stale permissions. Investigate unknown storage growth, unresolved security actions, and support cases without ownership.

Use changes to update the next forecast. A low first-year implementation estimate should not remain the three-year base after scope growth.

Distinguish Related Pricing Guides

This article compares the complete Indian solar-CRM ownership model across vendors. It does not replace a product-specific contract review or workflow selection guide.

Use the QuickEstimate pricing analysis for its exact public plan arithmetic, terms, refund, security, privacy, and conflict register. Use the QuickEstimate review for the broader desk-review method.

Use the best CRM for installers guide for category and shortlist decisions. Use the CRM app guide for Android, iPhone, tablet, web, offline, session, device, and sync acceptance.

Use integration-specific pages for IndiaMART, Meta, Tally, quotation, and messaging boundaries. A product can have a suitable licence price but fail a critical connector or data-control requirement.

Issue a Comparable CRM Price Request

Send every shortlisted vendor the same user roster, requirements matrix, data profile, integration list, security questions, implementation stages, support cases, and exit test. Ask for one itemised response.

Require these commercial fields:

• Legal supplier, contracting entity, invoice currency, GSTIN, tax basis, beneficiary, and quote validity
• Product, edition, SKU, user type, quantity, minimum, unit, billing term, commitment, and renewal
• Free, trial, discount, credit, onboarding, proration, user change, downgrade, cancellation, and refund terms
• Add-ons, messages, calls, numbers, storage, APIs, connectors, sandboxes, support, security, and overages
• Requirements, configuration, migration, integrations, testing, training, documentation, deployment, and acceptance
• Travel, taxes, payment fees, foreign exchange, partner charges, third-party products, and buyer work
• Renewal notice, price change, data export, assistance, archive, retention, deletion, and exit fees

Make vendors label each field included, excluded, limited, quoted separately, usage-based, buyer-supplied, third-party, or unknown. A blank response is not included scope.

Request a three-year cash schedule rather than one annual total. Show invoice dates, tax, currency, minimum users, renewal, discount expiry, planned user growth, and support changes.

Normalize implementation by deliverable and acceptance. Compare requirements, configuration, migration, integrations, security, tests, training, documents, production support, and handover separately.

Ask the vendor to identify every assumption. Convert material assumptions into a confirmed fact, qualification, contingency, or blocking condition before award.

Create a deviation ledger across price, requirement, limit, term, security, support, data, and exit. Record owner, evidence, impact, decision, and expiry.

Refresh the quote immediately before approval. Public prices, exchange rates, tax records, editions, limits, partners, timelines, and terms can change during selection.

At award, preserve the public evidence, quote, order form, contract set, requirements matrix, clarification log, pilot report, TCO workbook, approvals, and baseline exports. Later changes should reference that file.

Block Price-Only Procurement

Do not award when the cheapest plan fails a critical requirement, licence rule, security control, contract term, support boundary, or exit test. Record the failed gate.

Do not award from a public price page without a dated quote and applicable contract. The page may omit tax, minimums, usage, implementation, support, renewal, and third-party costs.

Do not award an enterprise quote with one unexplained total. Require licences, editions, users, services, implementation, migration, integrations, support, security, taxes, currency, renewal, and exit as separate fields.

Do not accept a discount that depends on an unreviewed term, auto-renewal, minimum, bundle, reference right, data condition, partner service, or restricted refund. Price the commitment and exit.

Do not treat a free pilot as zero cost. Record buyer data, user time, administrator work, integration effort, security review, training, export, and remediation.

Do not ignore unknown fields to force a comparison. Assign an owner and deadline. Use a contingency only when the decision authority accepts the residual risk.

The final approval should state the selected plan, user basis, three-year cost, assumptions, evidence date, and pilot results. Record contract deviations, tax review, security status, support, renewal, exit, and accountable owners.

Frequently Asked Questions

How much does solar CRM cost in India?

Public plans range from free to per-user subscriptions, while enterprise scope may require a quote. Compare dated list prices only after normalizing plan, users, billing, tax, implementation, usage, support, and exit.

What public CRM prices were observed on 10 August 2026?

QuickEstimate listed Free at ₹0 and Pro at ₹6,999 per user yearly with 3 users minimum. Zoho displayed INR editions. Salesforce India displayed USD per-user prices.

Does QuickEstimate provide GST invoices?

Its pricing FAQ states that it issues tax invoices with GST, HSN, and registered details. Verify the legal supplier, invoice, tax treatment, and input-tax-credit eligibility with qualified advisers.

What costs are missing from CRM seat pricing?

Include requirements, implementation, cleanup, migration, integrations, messaging, storage, API use, devices, security, training, administration, support, downtime, renewal, export, archive, and replacement.

How should QuickEstimate pricing be evaluated?

Use its dated first-party price as one input. Disclose the relationship, resolve public contract conflicts, test requirements and exports, and apply the same TCO and acceptance gates used for alternatives.

Can Zoho or Salesforce list prices be compared directly?

No. Normalize currency, billing, taxes, edition, licences, feature limits, APIs, storage, support, implementation, integrations, administration, contract, and exit before comparing cost.

Should a solar EPC choose annual billing?

Only after comparing the saving with cash flow, deployment risk, user changes, renewal, price changes, cancellation, refund, support, export, and replacement rights in writing.

How should a solar EPC test CRM value before purchase?

Run a controlled pilot with representative users, data, devices, connectors, failures, permissions, reports, exports, and support cases. Measure time, errors, rework, adoption, administration, and TCO.

Is SurgePV included in solar CRM pricing?

No. SurgePV is not a CRM. Budget technical layout, shading, electrical design, energy modelling, financial analysis, and proposal software separately when those functions are required.