In retrofit work the paperwork is the project. Rebates, financing, permits and inspections all have to line up in a specific order, and a job that gets installed before a grant is approved can turn a profitable project into an argument.
Financed big-ticket sales. A quote, a credit application and lender conditions need a clear handoff. Compare the tools that cover each step and verify how a changed deal reaches the next owner.
Sub-niches covered: Residential and commercial solar, Heat pumps and HVAC electrification, Insulation and building envelope, EV charging installation, Energy audits and modelling, Battery storage and backup power.
You likely have this problem if:
Rebate rules are known by whoever learned them last.
Financing, permits and scheduling block each other silently.
A completed install has an unclaimed rebate sitting on it.
Customers were quoted net of a rebate that was not yet confirmed.
Inspection milestones are tracked in a folder rather than on the project.
What breaks operationally:
Rebate programs each have different evidence and sequencing rules, tracked by whoever learned them last.
Financing approval, permit issuance and install scheduling are managed in three places and block each other silently.
Post-install inspection and rebate claim submission slip, so money sits unclaimed for months.
Customers are quoted on a net-of-rebate price before the rebate is confirmed.
What we build:
Rebate and grant tracker. Each program's requirements and sequencing wired to the project stage, so nothing gets installed out of order.
Permit and inspection milestones. Applications, approvals and inspections as blocking milestones on the project rather than notes in a folder.
Financing intake at quote. Finance application captured with the quote, so the customer sees a real monthly figure at the kitchen table.
Claim submission queue. Completed installs surfaced as claims to file, with the evidence already attached from the job.
Why do rebate claims get missed after a job is finished?
Because the job is closed in the installer's mind the day the crew leaves, and the claim is a separate administrative task with no owner. Making the completed install generate a claim task with the evidence already attached fixes most of it.
Can rebate program rules be kept current in software?
The requirement checklists can, and they should be editable by an administrator rather than a developer, because programs change with little notice. The mistake is hardcoding a program's rules and then discovering they moved.
Should the quote show the price before or after rebate?
Both, clearly separated, with the rebate marked as pending until confirmed. Quoting only the net number is the fastest way to a dispute when a program runs out of funding mid-project.
How do you sequence financing against permits?
Financing approval should gate scheduling and the permit should gate installation, with each one visible as a blocker on the project. Most retrofit disputes trace back to one of those two being assumed rather than confirmed.
An established product can be the right answer. VX-N scopes custom software, configuration and integrations around your requirements. Compare the workflow before deciding to replace anything.
Aurora Solar vs VX-N
Solar design, sales proposals and permitting software.
When the product fits
For solar projects, assess dedicated design and proposal software first.
When to consider VX-N
VX-N can scope the workflow from sold proposal to financing, permits, installation and customer updates.
What to test before deciding. Aurora’s solar scope is not every energy retrofit. Validate utility data, financing and permitted data access.
A product gives you its supported platform, configuration options and vendor roadmap. A VX-N engagement defines the workflow, deliverables, data access and ongoing support for your business. Compare total operating cost, implementation effort and maintenance for the same scope.
Product sources checked 11 October 2026. Independent comparison by VX-N. No vendor partnership is implied. Features, plans, regions and integration access vary; confirm them with the vendor. VX-N scope, ownership, maintenance and support are agreed before a paid build.