Answer
Run a solar software trial on your own representative project cases, not the vendor's demo site. Keep the inputs, assumptions and outputs for each case, test a revision, and get export and exit terms in writing. A trial shows workflow fit. It does not prove engineering approval or productivity gains.
Last updated: November 2026
A software trial should end with an evidence-backed buying decision. A polished demonstration is useful for orientation, but your team also needs to know what happens with its own inputs, revisions, reviewers and exports. Test the work you intend to do, including the exceptions that are common in your projects.
SurgePV publishes this post and sells solar design software. The method below applies to any vendor, including us.
This is an operational evaluation method, not proof of engineering accuracy, regulatory acceptance or future commercial results. Keep customer identifiers and confidential files out of a trial unless their use, provider access and retention are authorized.
How do you define the decision before opening the trial?
Write down the workflow you are evaluating: residential layout, commercial production modeling, electrical documentation, proposals or another bounded task. State which roles will use it and which outputs must be delivered. A tool may fit one stage without covering the whole project.
Separate mandatory requirements from preferences. For each requirement, define observable evidence: an editable geometry correction, a supported equipment model, a source-labeled analysis run, an export your receiving team can use, or a permission restriction you can test. Do not substitute a feature name for a completed task.
NASA’s decision-analysis guidance describes evaluating alternatives against criteria and recording the decision basis. Adapt that approach to procurement. It is not a solar-software certification or a mandatory scoring system.
Want a sanitized project run through a guided demo?
Bring one of your own cases and see the design workflow on your inputs, not a canned site.
Book a DemoChecking cost first? See the SurgePV pricing page
Which cases should a solar software trial use?
Use your own authorized projects and the same comparison basis for every tool. Choose cases that expose your actual workload, not only the easiest demonstration site. Useful cases include a routine roof, a constrained site and a revision with missing information. The number of cases and the trial duration depend on scope, access and review capacity. There is no universal minimum that proves fit.
Retain the input package, equipment version, assumptions and expected deliverable for each case. When you compare tools, reconcile weather sources, geometry, loss treatment, output boundary and analysis period before you interpret different production results. Agreement between tools does not prove accuracy, and a difference alone does not tell you which result is wrong.
A free public reference helps here. The PVWatts Calculator from the US National Laboratory of the Rockies (formerly NREL) asks for system size, module type, array type, system losses, tilt, azimuth and DC to AC size ratio, among other inputs. Running the same inputs through it gives you a rough sense of whether a trial result is in the right range. It is a plausibility check, not a bankable yield estimate.
Six tests to run in every trial
| Test | Evidence to retain | Question for the buyer |
|---|---|---|
| Create the initial project | Source files, input mapping and unresolved fields | Can the team start without invisible defaults? |
| Correct a roof or equipment choice | Before/after revision and affected outputs | Which dependencies update and which require manual review? |
| Model production | Inputs, model/version, units and assumptions | Can a reviewer reconstruct the result? |
| Prepare a proposal | Accepted design reference, scope and financial basis | Does the customer output describe the current project? |
| Transfer work to another role | Export, receiving task and return reason | Can the next person use it without private coaching? |
| Retrieve or exit the trial | Accessible files and written retention/export terms | What remains usable when access ends? |
Keep trial outputs preliminary until the responsible reviewers authorize their use. A completed test is not permit approval or permission to operate.
Key Takeaway
The revision test and the exit test expose the most. A tool that looks fine on a fresh project can still force manual rework when the roof changes, or leave you without usable files when access ends.
How do you measure completed work, including corrections?
Record active task time separately from waiting for vendor help, missing inputs or reviewer decisions. Include the time needed to correct an output and transfer it. State the task boundary and whether the operator had training or live assistance.
Do not compare an experienced user of one tool with a first-time user of another without disclosing that difference. Report failed or uncompleted tasks alongside successful ones. A small trial can reveal specific limitations. It cannot support a universal productivity or conversion claim.
Pro Tip
Give two people the same case file and ask each to build it independently. If their results differ, the gap tells you how much of the outcome depends on the operator rather than the tool.
What does SurgePV publish about trial access and pricing?
SurgePV’s pricing page publishes per-user annual prices and states that the current public offer is a guided demonstration rather than a self-service trial. A demo does not require a credit card. Anything beyond that, such as trial length or included functions, is not published, so ask for it in writing.
Figures above come from the SurgePV pricing page, checked November 2026. Team rates require the stated seat count, and renewal and cancellation terms are set in your quote.
What commercial and data terms should you get in writing?
Obtain current written terms for trial access, included functions, user roles, usage limits, paid dependencies, export formats, support, data location and deletion. Ask what changes when the trial ends. Do not assume a public free-trial offer includes every feature, or that a demonstration shows an integration available in your configuration. The software integrations guide lists the integration questions worth asking.
For SurgePV, request a guided evaluation using a sanitized case and ask the vendor to demonstrate the required design workflow and outputs. Record what was demonstrated, what was described but not shown and what remains unavailable or unknown.
Copy-ready trial decision record
DECISION AND WORKFLOW:
REQUIRED ROLES AND DELIVERABLES:
MANDATORY REQUIREMENTS / PREFERENCES:
CASE ID / APPROVED INPUT PACKAGE / SOURCE DATES:
TOOL CONFIGURATION / VERSION / ASSUMPTIONS:
TASK / OPERATOR / TRAINING OR ASSISTANCE:
RESULT / OUTPUT LOCATION / REVIEWER:
ACTIVE WORK / WAITING / CORRECTION TIME:
FAILED OR UNTESTED REQUIREMENTS:
MANUAL DEPENDENCIES / EXPORT AND EXIT LIMITS:
CURRENT WRITTEN COMMERCIAL AND DATA TERMS:
DECISION / CONDITIONS / OWNER / REVIEW DATE:
Ready to run your own evaluation?
Walk through your required design steps with the SurgePV team and fill in the decision record with what you see.
Request a Guided DemoWant the numbers first? Read the SurgePV pricing page
What should you do after the trial?
Choose, reject or extend the evaluation based on the requirements that matter. An unresolved mandatory requirement should stay visible in the decision. If you are still building the shortlist, how to choose solar design software covers the criteria. After selection, use the software adoption workflow to plan training, controlled rollout and ongoing support. Choosing a tool and establishing daily use are separate tasks.
Frequently Asked Questions
What should a solar software trial control?
A solar software trial should control the active project version, the source data, the review status, the owner and the exception path. Without those, two testers can run the same case and get results nobody can reconcile.
How long should a solar software trial last?
There is no universal trial length that proves fit. Size it to the cases you need to run and the reviewer time you can spare, and extend it only if a mandatory requirement is still untested.
What projects should I use to test solar design software?
Use your own authorized projects: a routine roof, a constrained site and a revision with missing information. Easy demo sites hide the exceptions that cost you time later.
Does SurgePV offer a free trial?
SurgePV’s pricing page says the current public offer is a guided demonstration, not a promised self-service trial, and that a demo needs no credit card. Ask the sales team for the access terms in writing.
How do I compare solar production results between two tools?
Match the weather source, geometry, loss assumptions, output boundary and analysis period first. Differences between tools are only meaningful once those inputs are the same.
What should I get in writing before ending a solar software trial?
Get the trial access terms, included functions, usage limits, export formats, support scope, data location and deletion terms. These decide what you can still use when access ends.
Sources
Primary research and reference material used for this desk-research article.
Where this fits
This article is part of SurgePV's Solar Business & Operations hub, which works through the topic from first principles to the decisions a project team actually has to make.

