Answer
A solar quotation app is the phone or tablet front end of solar quotation software. Test five things on your own device and plan before you buy. They are offline editing, price and discount limits, tax and subsidy controls, delivery proof, and data export. A store badge shows the app exists. It does not show that those tasks work.
Buy the system on its controls and accept the app on device evidence. Try each required task on the target device and account before rollout. If a task fails, or its totals do not match, treat it as an open risk instead of assuming the feature works.
Last updated: November 2026.
This is the reference page for solar quotation software on the SurgePV blog. Narrower workflows keep their own guides, listed at the end.
Need the design numbers behind every quote?
SurgePV produces the layout, bill of materials and energy-yield figures a quotation depends on. Walk through one of your own projects in a guided demo.
Book a DemoChecking cost first? See the SurgePV pricing page.
Solar quotation tools compared: what each vendor documents
SurgePV publishes this guide, sells one of the tools below, and has a commercial relationship with QuickEstimate. The table lists what each vendor’s own pages state in October 2026. It does not rank them.
| Tool | Platforms the vendor lists | Offline use | Price on the vendor’s page | Quotation scope the vendor lists |
|---|---|---|---|---|
| Aurora Sales Mode | Tablet-friendly sales proposals; customers get a mobile-friendly web proposal | Not stated on the pages read | Basic USD 135 per user per month billed annually (USD 159 monthly). Premium USD 220 (USD 259 monthly). Enterprise is custom | Proposals with pricing set per watt, per component or as a flat fee, plus adders, discounts and incentives |
| QuickEstimate | iOS app, Android app and web app | Not stated on the pages read | Free plan: INR 0, 1 user, 10 proposals a month. Pro: INR 6,999 per user per year, minimum 3 users (3 x 6,999 = INR 20,997 a year) | BOM breakdown, GST at 5% on solar goods, PM Surya Ghar subsidy calculation, branded PDF, WhatsApp or email sharing, admin-set price list |
| SurgePV | Web application; no native mobile quotation app is claimed | Not claimed | USD 1,899 per user per year for one seat, USD 1,499 per user for 3 seats, USD 1,299 per user for 5 seats. Access is through a guided demo | Proposal generation and bill of materials output from the design, with financial modeling |
Sources: Aurora pricing and Aurora Sales Mode; QuickEstimate’s download, pricing and quotation-system pages; SurgePV’s pricing page. Vendor feature lists are the vendors’ own statements. Run the acceptance tests below before you rely on any of them.
- SurgePV five-user planUSD 1,299
- SurgePV three-user planUSD 1,499
- Aurora Basic (annual)USD 1,620
- SurgePV IndividualUSD 1,899
- Aurora Premium (annual)USD 2,640
Source: Aurora and SurgePV pricing pages. QuickEstimate lists INR 6,999 per user per year, so it is left out of this USD chart, checked October 2026.
Key Takeaway
Price is only one column. Two tools at similar prices can differ on offline use, approvals and delivery proof, which the acceptance tests below check.
Separate the quotation from everything near it
A quote lists the items, quantities, price, terms, and how long the offer is valid. A proposal presents a wider technical, financial, and company case.
A CRM (customer relationship management) opportunity tracks a sale. A contract records the agreement. An invoice asks for payment. Accounting records and matches the money.
Keep those items linked but separate. A sent quote does not mean a customer accepted it. An accepted quote is not automatically a signed contract or a paid invoice.
This page covers the quote itself. It covers the document, its sources, its price controls, its versions, how it reaches a customer, and what proof survives afterwards. It covers that work on a phone, a tablet, and a desktop browser, because the same quote crosses all three.
Two nearby decisions have their own guides. Proposal content and layout is a separate problem from quote control. Pre-quote cost estimating happens before a quote exists.
Identify the exact application surface
“Mobile app” can mean several things. Test each one separately.
| Surface | Evidence to request |
|---|---|
| Native Android app | Publisher, package, store listing, OS range, region, release, update, permissions |
| Native iPhone or iPad app | Developer, listing, OS range, device class, region, release, permissions |
| Progressive web application | URL, install behavior, browser support, cache, update, offline scope |
| Responsive mobile browser | URL, supported browser, viewport, touch workflow, local storage |
| Tablet browser | Device, browser, orientation, keyboard, files, rendering, approvals |
| Desktop browser | Administrative, approval, reporting, configuration, and export parity |
| Customer quote view | Browser, identity, access, version, expiry, response, download, privacy |
For each surface, record the vendor, publisher, and package or URL. Record the OS (operating system), supported version, device, and region. Record the language, release, and update. Add permissions, local storage, accessibility, plan, role, and support.
A download page or store badge tells you where to look. Open the direct listing, install the app, and check account eligibility, region, plan and task yourself.
Treat the listing itself as a declaration, not a test result. Google’s own documentation describes the Data safety section as information the developer provides. Google Play also publishes target API level requirements that govern which builds may be updated. Apple documents its own release and availability controls through App Store Connect. Read all three before you accept a vendor’s mobile-support statement.
Do not assume iOS and Android do the same tasks. A phone screenshot tells you nothing about the tablet.
Build a task parity matrix
Test each required task on each target surface. Parity means the same tasks work on each device.
Tasks can include creating a customer and choosing a site. They include choosing the technical source, entering items, and editing quantity and price. They include discounts, the margin view, tax, and the subsidy scenario. Add the template, approval, generation, preview, and send. Add delivery, response, revision, and withdrawal. Add reporting and administration. Add import, export, archive, and deletion.
| Task | Device test fields |
|---|---|
| Create or find customer | Search, duplicates, legal buyer, contact, site, owner |
| Select technical source | Project ID, design revision, BOM, equipment, validity |
| Build commercial lines | Item, unit, quantity, price source, tax, option, exclusion |
| Review margin | Cost basis, markup basis, gross margin basis, permissions |
| Approve | Role, threshold, reason, timestamp, stale-source reset |
| Generate and preview | Number, version, rendering, pagination, terms, recipient |
| Send | Channel, sender, recipient confirmation, permission, provider evidence |
| Revise or withdraw | Immutable history, superseded link, approval reset, visibility |
| Export and archive | Complete data, documents, audit, format, retrieval, deletion |
Record each result as pass, fail, or not available. Use plan-limited, role-limited, region-limited, or untested where they fit. Do not turn “planned” into “available.”
Build a solar quotation app acceptance register
Use one row for each required task and failure case. Accept a task only when someone else can repeat the proof.
| Acceptance field | Required record |
|---|---|
| Surface | Native app, PWA, mobile browser, tablet, desktop, or customer view |
| Environment | Device, OS, browser, app release, region, language, network, and storage |
| Account | Contracting entity, plan, tenant, role, permissions, and feature flags |
| Source state | Customer, project, design, item, price book, tax, and subsidy versions |
| Action | Exact taps, entries, approvals, generation, send, response, or export |
| Expected result | Allowed edit, blocked edit, state transition, output, and audit event |
| Failure result | Error, queue, hold, retry, escalation, fallback, and recovery |
| Reconciliation | IDs, versions, quantities, totals, recipients, messages, and downstream records |
| Evidence | Screen record, log, export, message ID, document, timestamp, and reviewer |
| Decision | Pass, conditional pass, fail, untested, or not applicable |
Record the tester, test date, data set, and evidence location. Keep screenshots only as supporting records. They are not the sole production evidence.
Define pass limits before testing
The buyer should state which failures block rollout. Examples include a wrong recipient and an unauthorized discount. Others are a duplicate final number and a missing audit event (a log entry that shows who did what). Others are a stale technical source, an unreconciled offline edit, or an incomplete export.
Avoid vague acceptance such as “easy to use.” Define task completion, error handling, required proof, and recovery.
Accessibility also needs task evidence. W3C publishes WCAG 2.2 as the reference for web-content accessibility. Test readable text, zoom, contrast, touch targets, keyboard behavior where it applies, labels, focus, and document output. Use the criteria that apply to you. Qualified review decides which legal and contractual duties attach.
Test the supported languages and number formats your team uses. Check dates, timezones, and currency. Check decimal separators, units, and text wrapping.
Preserve a production-like baseline
Create a synthetic (made-up) baseline tenant, which is a test account. Fill it with approved roles, item data, price books, tax scenarios, subsidy scenarios, templates, and message channels.
Freeze the baseline version before each test cycle. Record each configuration change.
After an app update, rerun the tests for formulas, permissions, offline use, and sync. Also rerun them for page rendering, delivery, export, and deletion. A past pass does not prove a later release.
Close conditional passes
A conditional pass needs an owner, a workaround, an expiry date, the leftover risk, and a closing test. Do not leave permanent workarounds undocumented.
If a required task works only on desktop, say so. Do not market the full workflow as mobile.
If an action needs network access, say so in field instructions. Do not call the complete workflow offline.
Map quotation objects
Avoid one oversized customer record. Map the actual objects and identifiers.
The model may include these objects. They are the legal seller, customer, legal buyer, contact, site, and meter. They also include the opportunity, project, design, equipment set, BOM (bill of materials, the parts list), item, and price book. Add tax treatment, subsidy scenario, finance option, and quotation. Add alternates, allowances, and exclusions. Add the template, approval, recipient, message, consent, and acceptance. Finish with the attachment, task, activity, and audit record.
Pick one system of record for each object. That is the one place that holds the official copy. Record stable IDs and links between systems.
A site can have several contacts. A legal buyer can control several sites. One design may support several commercial options.
Do not overwrite project identity when a rep changes a contact. Do not merge distinct sites because they share a phone number.
Separate each state
Use clear quote states:
- draft
- technically pending
- technically approved
- commercially pending
- commercially approved
- ready
- generated
- previewed
- sent
- accepted by provider
- delivered
- failed
- viewed, when supported
- accepted by customer
- rejected
- expired
- withdrawn
- superseded
- revised
- reopened
- won
- archived
- deleted
Keep these states separate: design, approval, generated document, and delivery. Keep apart the customer response, opportunity stage, contract, and invoice. Keep payment, project, and accounting apart too.
Define allowed transitions and roles. A user should not jump from draft to sent when approvals are required.
Use a fixed quote number (one that cannot be changed) and a version link. Each PDF or web view should trace back to the source snapshot, approval, recipient, channel, issue date, timezone, and validity.
Trace technical and quantity sources
The mobile app should not become an uncontrolled design editor. Quote facts need source evidence.
Trace the site and project identity and the design revision. Trace the exact modules and inverters, and the capacity. Trace strings, shading, generation, BOM, storage, export, warranty, and other technical facts where they apply. If the BOM is the weak link, see how to generate a solar BOM and review it before it reaches a quote.
Each value should record its source system, record ID, revision, date, owner, checker, and approver. It should also record any assumption and limitation. It should record the validity and any override evidence.
Map items, quantities, units, and conversions. Map alternates and owner-supplied materials. Map allowances, exclusions, and scope.
Mobile editing must not silently change a controlled fact. These include layout, equipment, capacity, and energy. They also include BOM, tax, subsidy, and warranty.
If an edit is allowed, classify it as a commercial override or a technical change. A technical change should return to the responsible design workflow.
Quote software does not replace survey, design, or engineering review. It does not replace review by a professional, an authority, a utility, or a manufacturer. It does not replace tax, legal, or finance review.
Control price, markup, and margin
Build a price-book register before you test calculations.
| Price field | Required evidence |
|---|---|
| Item master | Stable ID, name, description, unit, status, version |
| Cost basis | Supplier or source, amount, currency, effective date, expiry |
| Conversion | Source unit, target unit, formula, rounding, test |
| Selling price | Rule, effective date, region, customer class, approval |
| Markup | Named formula and base |
| Gross margin | Named formula and revenue basis |
| Discount | Type, amount, limit, authority, effect |
| Price floor | Rule, role, exception, approver, audit |
| Other costs | Freight, logistics, labor, overhead, contingency, finance, warranty |
Markup and gross margin are different formulas. Name and test both. A percentage without its basis is invalid.
Here is a worked example with hypothetical numbers. An item costs 80,000 and sells for 100,000. Markup is (100,000 - 80,000) / 80,000 = 25% of cost. Gross margin is (100,000 - 80,000) / 100,000 = 20% of price. Now say a rep adds 20% to cost. The price is 96,000 and the gross margin is 16,000 / 96,000 = 16.7%. Test that the app applies the formula you named.
Give each of these its own permission. They are item, quantity, cost, price, discount, and margin. They are also tax, subsidy, finance, terms, approval, send, withdrawal, and administration.
Each override should record the old value, new value, and reason. It should record the evidence, requester, approver, and timestamp. It should also record affected versions, margin effect, tax effect, and audit event.
Test rounding at item, tax, subtotal, option, and final-total levels. Define currency and exchange-rate basis.
Keep tax review outside the app’s authority
GST is India’s Goods and Services Tax. The CBIC GST rates page is the official place to find notified entries. Your tax adviser classifies the exact solar contract.
Several tax questions need a current review by a qualified person. They are classification, rate, place, time, and invoice. They are also input credit, composite or mixed supply, and contract allocation.
The GST portal is the official entry point to the statutory (legal) system. A quote app is not the source of truth for accounting or tax.
For each tax rule you set up, record the source, effective date, scope, reviewer, and approval. Add a regression test (a repeat test that catches new errors) and an expiry review.
Do not present a quote as an invoice. Do not treat quoted tax as the final legal ruling.
Treat subsidy as a separate scenario
The PM Surya Ghar National Portal is the official entry point to the scheme. Eligibility and payment are decided one customer at a time.
Date each subsidy input and re-read the current guidelines before each quote.
Keep CFA (central financial assistance) or another subsidy outside the base commercial total. The only exception is when the contract explicitly controls the scenario. Never show it as guaranteed cash.
Record the scheme, authority, capacity, and route. Record the eligibility assumptions and equipment conditions. Record any prior benefit and the customer contribution. Record the portal or DISCOM (power distribution company) state and the evidence date. Record unresolved conflicts and the final-authority caveat.
When the evidence goes out of date, mark the scenario stale and reset approval. Do not quietly reuse it for another customer.
Control numbering, versions, and documents
The quote should identify the seller, buyer, address, number, and version. It should show the issue date, timezone, validity, currency, rounding, tax basis, and line items. Add options, alternates, exclusions, and warranties. Add payment, delivery, and installation scope. Add assumptions, the change rule, acceptance, privacy, and the next step.
Require unique numbers. Allow no duplicate final identifiers. Keep approved and customer-accepted versions fixed, so nobody can change them.
A revision needs a reason and the source change. It needs the affected fields and a comparison view. It also needs an approval reset, a link to the replaced version, and recipient visibility.
Block these quotes or mark them clearly. They are expired, replaced (superseded), and withdrawn quotes. They are also quotes that are technically stale, commercially stale, tax-stale, or subsidy-stale.
Define the checks and steps for each stage. They are completeness and technical review. They are commercial review, tax or finance review, and legal review. Then come generation, page rendering, preview, and recipient check. Last come send permission, delivery, and response. Then come expiry, withdrawal, revision, and archive.
Preview the exact customer output before sending. Test long descriptions, page breaks, fonts, tables, totals, attachments, and language.
Trace each quote figure back to the design
Check that the price, quantities and yield on a quote match an approved design revision before it goes out.
Book a DemoChecking cost first? See the SurgePV pricing page.
Pro Tip
Put the test phone in airplane mode, edit a quote, change a discount, then reconnect. Check that the totals, the version number and the audit entry all match what you changed.
Test offline and synchronization behavior
“Works offline” needs task-level proof. Some apps may open saved copies of records but block generation, approval, or sending.
Test each of these offline, one by one: create, edit, price lookup, approval, generation, preview, send queue, withdrawal, export, and search.
For the sync link, record the system of record, field ownership, direction, event, and timing. Record the API or file, authentication, version, rate limit, and retry. An API is the way two systems talk to each other. Add idempotency (the same action sent twice gives the same result). Add conflict handling, the error queue, alerts, replay, correction, and deletion. Add reconciliation (matching the records).
Failure cases should include:
- reconnection after several edits
- two users editing one quote
- duplicate send action
- out-of-order update
- deleted source record
- expired session or token
- app update and schema change
- device storage exhaustion
- failed attachment
- replay after timeout
Define who resolves conflicts. It could be the server, the last accepted version, the field owner, or a human reviewer. Never rely on silent last-write-wins (the latest save overwrites the rest) for controlled commercial fields.
After sync, match the quote number, version, items, quantities, formulas, and totals. Also match approvals, recipient, messages, and audit events.
Secure the mobile device workflow
Map how people sign in. Cover authentication and MFA (multi-factor sign-in). Cover sessions and biometric options where supported. Cover the local cache (saved data on the device), downloads, screenshots, and clipboard. Cover camera, location, contacts, files, notifications, deep links, and the share sheet.
Define which permissions are needed and why. Deny unnecessary access during the pilot.
Test these device cases: lost, stolen, shared, repaired, resold, rooted or jailbroken, unsupported, and offboarded. Keep BYOD (bring your own device) and company-managed device controls apart.
Define session expiry and remote revocation. Define how local data is removed. Define backup behavior and device replacement. Check each with evidence.
Never let any of these be the only production record. They are a personal WhatsApp account, a shared consumer login, and a personal cloud drive. They are also a screenshot, a local gallery, or a copied PDF.
The central record should keep the source, version, recipient, delivery, response, approval, and audit proof.
Control delivery and customer response
Email, SMS, WhatsApp, app, web link, PDF, portal, download, and in-person display are different channels.
For each send, record the sender, recipient, permission, purpose, and approved template where it applies. Record the number, version, timestamp, timezone, and provider message ID. Add acceptance, delivery, failure, and view if supported. Add retry, opt-out, suppression, fallback, and archive.
Accepted by a messaging provider is not delivered. Delivered is not viewed. Viewed is not accepted. And customer acceptance, on its own, is not a signature or a contract. It is not an invoice or a payment. It is not a won project, an installation, or a satisfied buyer. Keep a separate field for each one.
Test the wrong-recipient route. A user should confirm the legal buyer and intended contact before sending.
Test resend and revision. The customer should know which version is current and which is withdrawn.
A clicked Accept button is not automatically a signature. The Controller of Certifying Authorities publishes the official eSign framework for India. Have counsel confirm whether a given acceptance binds the buyer.
The WhatsApp solar proposal guide covers deeper controls for messaging.
Separate consent, privacy, and acceptance
These are all different records: notice, service message, sales consent, and channel permission. So are quote acceptance and signature. So are opt-out, suppression, withdrawal, correction, deletion, grievance, and retention.
MeitY’s DPDP Rules and commencement material describes a framework that starts in phases, on set dates. DPDP means Digital Personal Data Protection. A qualified reviewer should decide the current duties for your exact data use.
Quotes may go out over SMS or a commercial messaging channel. If so, TRAI (India’s telecom regulator) runs a separate consent registration route for commercial messages. A CRM opt-in field is not the same record.
Map the vendor, store, cloud, and document host. Map messaging, analytics, and crash reporting. Map support, payment, signature, and other subprocessors. A subprocessor is another firm that handles the data.
Record data classes, purposes, roles, and regions. Record transfers, retention, deletion, incidents, rights, grievance, and contract proof.
Do not assume security or data location (residency) from a short marketing line. Settle any conflict between vendor documents before you sign.
Run a production-like synthetic pilot
Use synthetic customers, sites, quotes, and recipients only. Test the exact production-like devices, roles, plans, regions, and channels.
Use a case matrix for the pilot.
| Test family | Required cases |
|---|---|
| Identity and access | Wrong login, expired session, lost device, offboarding |
| Device and network | Phone, tablet, browser, offline, reconnect, update, storage failure |
| Technical source | Wrong project, stale design, changed equipment, invalid quantity |
| Commercial | Wrong unit, wrong price, unauthorized discount, floor breach, margin versus markup |
| Tax and subsidy | Stale rule, review hold, qualified scenario, ineligible assumption |
| Version and output | Duplicate number, expired validity, withdrawal, revision, rendering failure |
| Delivery | Wrong recipient, failed send, retry, resend, opt-out, fallback |
| Reconciliation | Generated, accepted, contract, invoice, credit, payment, handoff, accounting |
| Exit | Complete export, archive retrieval, retention, deletion, user and device removal |
For each case, define the source, channel, device, and role. Define the expected state, allowed edit, blocked edit, approval, and output. Add audit proof, reconciliation, fallback, and the pass limit.
Test formulas using known synthetic values. Cover units, conversions, markup, gross margin, discounts, rounding, taxes, options, and totals.
Test failure recovery, not only the case where everything works. Record each defect, its severity, and its owner. Record the fix, the retest, and the sign-off.
Reconcile beyond the generated quote
Match these records against each other. Start with source quantities, calculated totals, and the generated quote. Then check the customer-accepted quote, contract, invoice, credit, and payment. End with project handoff and accounting.
The app should not become the accounting authority just because it is handy. Define the system of record for each later state.
Use stable identifiers and version links. Record intentional differences, such as an accepted change after the quote.
Review counts and values by status. Look for records that are missing, duplicated, failed, withdrawn, replaced, or orphaned (cut off from their parent).
Sometimes the quote lives inside a CRM rather than beside it. In that case the CRM-side quotation lifecycle adds opportunity, price-book, and handoff controls. This page does not cover them.
Compare total cost and contract terms
Put each price on the same basis. Compare the plan, seats, devices, quotes, templates, item limits, and price books. Compare storage, messages, and integrations. Compare API, setup, and migration. Add training, support, backup, and security. Add overages, taxes, renewal, export, archive, and exit.
Use current vendor evidence for each line. Do not invent a universal app price or implementation cost.
The contract should cover who owns the data and documents. It should cover intellectual property and security. It should cover uptime, changes, and support. It should cover subprocessors and privacy. It should cover export, termination, deletion, audit, and exit help.
Define the renewal notice, price change, plan downgrade, and feature removal. Define the usage overage, support route, invoice, refund, cancellation, and dispute process.
Run a complete export during the pilot. Test records, versions, PDFs, and attachments. Test approvals, messages, consent, audit, and configuration.
Plan offboarding and exit
Define how you will remove users, end sessions, and remove devices. Define local-data deletion and reassignment. Define what happens to open approvals and queued sends. Define audit retention.
The exit pack should include customers, sites, projects, and technical-source links. It should include items, price books, quotes, versions, and approvals. It should include recipients, delivery, and responses. It should include attachments, audit, consent, and configuration.
State the file formats and identifiers. State how records link to each other. State the timestamps, timezones, code lists, and how deletion is confirmed. A folder of PDFs is not a complete business export.
Test restoration into a neutral review environment. Check that accepted versions remain identifiable.
Plan for vendor failure and app removal. Plan for an unsupported OS and product change. Plan for account termination and messaging-provider change.
Evaluate QuickEstimate under identical gates
Disclosure: SurgePV and QuickEstimate have a commercial relationship. QuickEstimate is therefore a related-party candidate in this guide.
The QuickEstimate download page lists iOS, Android and web access. It also describes proposals, a pipeline and WhatsApp sharing. Confirm store availability and check that each task works on your own device.
The quotation-system page lists a BOM breakdown and GST at 5% on solar goods. It also lists PM Surya Ghar subsidy calculation, revisions and WhatsApp or email sharing. Check the formulas, sources, approvals and the current plan.
The pricing-calculator page describes price configuration and margin functions. Test units, formulas, permissions, floors, updates, and audit.
Review current pricing, security, privacy, and terms together. Settle any conflict over the legal entity, units, backup, geography, and which document wins.
Apply the same gates to each tool. The gates are channel, source, price, margin, tax, and subsidy. They are also permission, version, offline, sync, delivery, and privacy. The last ones are pilot, cost, contract, support, export, and exit.
Keep SurgePV in its verified boundary
SurgePV covers technical solar design and proposal output. These feed design-linked project material.
SurgePV is not a native mobile quotation app, CRM, price database, tax authority, subsidy authority, accounting system, messaging provider or QuickEstimate integration.
Technical design and BOM sources still need version and approval control before commercial use.
Keep related decisions distinct
This page is the reference for solar quotation software and the apps in front of it. Nearby decisions have their own guides:
- the CRM-side quotation lifecycle, when the quote is built inside CRM
- choosing a solar CRM app for the mobile CRM decision, which is not the same product category
- estimating cost before a quote exists
- what belongs in the proposal document
- sending documents over WhatsApp, where messaging rules govern
- India-specific CRM requirements
- Zoho CRM for solar, when a general CRM is the system of record
Frequently Asked Questions
What is a solar quotation app?
It is a phone, tablet, or mobile-web workflow for building and controlling a commercial solar quotation. The quote lists items, quantities, prices, terms, and validity. The app should keep proof of the technical sources, permissions, approvals, versions, and recipients. It should also keep proof of delivery, response, audit, export, and archive.
Can a field rep change prices or discounts on site?
Only within documented permission and approval rules. The app should enforce units, price sources, floors, discount limits, and margin policy. Each override should record the old and new values, reason, and evidence. It should record the requester, approver, timestamp, affected versions, and commercial effect.
Should a solar quotation app calculate GST automatically?
Software may calculate configured tax scenarios, but it is not the tax authority. Several tax questions need a current review by a qualified person. They are classification, rate, place, time, and invoice. They are also input credit, composite or mixed supply, and contract allocation. Record the rule source, effective date, reviewer, assumption, and approval.
Can a solar quotation app deduct PM Surya Ghar subsidy?
It can show a separate dated scenario when current official evidence supports the inputs. Do not present CFA (central financial assistance) as guaranteed cash. Record the scheme, authority, capacity, and route. Record the eligibility assumptions and the equipment conditions. Note any prior benefit. Note what the customer pays. Record the portal or DISCOM state, evidence date, conflicts, and final-authority caveat.
What should happen when a mobile quote is edited offline?
The app should show that it is offline. It should keep the source snapshot, queue permitted actions, and block unsafe actions. After reconnection, it should check the sign-in, detect conflicts, and prevent duplicates. It should apply a defined merge rule and record audit events. It should match totals and versions, and show failures so someone can correct them.
Is QuickEstimate ranked as the best solar quotation app?
No. SurgePV and QuickEstimate have a commercial relationship, so this guide ranks nothing. QuickEstimate lists iOS, Android and web apps and a quotation system with BOM, GST and PM Surya Ghar subsidy calculation on its own pages. Test it under the same gates as any other tool. Test the exact device, region, plan, and role. Test offline use, sync, and formulas. Test approval, security, delivery, export and exit.
Is SurgePV a native mobile quotation or CRM app?
No. SurgePV is a web application for technical solar design, bill of materials, energy yield and financial modeling, and proposal output. It does not claim a native mobile quotation app, CRM, price book, tax or subsidy authority, accounting system or messaging provider.
Sources
Primary research and reference material used for this desk-research article.
Where this fits
This article is part of SurgePV's Solar Design hub, which works through the topic from first principles to the decisions a project team actually has to make.


