Multi-site retail rollout
To be published with the customer's measured baseline, installed scope, verified savings, and incentive capture.
LumenAudit Pro is the operating system for retrofit work. Field capture, engineering scope, savings models, incentives, procurement, and commissioning all resolve against a single tenant-scoped project — so the proposal, the bill of materials, and the closeout package can never disagree.
No credit card · One user · Lighting audit, proposal PDF, and Excel BOM included
Product screenshot using sample project data.
Free beta is open. The lighting audit-to-proposal path is the entry point.
Nine discipline modules resolve against one tenant-scoped project record.
Built by people who run audits, estimates, BOMs, and closeouts for a living.
Log in remains separate from beta signup.
A single site walk becomes a workbook, a takeoff, a savings model, a quote, a purchase order, and a closeout packet. Each one is a separate document. Each one drifts. By the time the customer signs, nobody can prove the numbers still agree.
A workbook has no concept of a project. It has cells. Rename a tab, copy last quarter's file, paste a fixture count one row low, and the error propagates silently into the proposal. There is no validation, no ownership, no version anyone trusts, and no way to answer "which number is current?" without opening five files.
Most audit software stops at the audit. It captures fixtures and prints a savings summary, then hands you a PDF and walks away. Estimating happens elsewhere. Procurement happens elsewhere. Commissioning happens elsewhere. The tool that knew the scope is not the tool that has to defend the price.
Lighting in one app. HVAC in a workbook. EV in a consultant's deck. Estimating in the bid software. Rebates in a portal. Nine disciplines, nine systems, zero shared identity for the site. Portfolio reporting becomes a manual reconciliation exercise every quarter.
Why this needs an operating system, not another app. Multi-discipline energy work is not a document problem — it is a state problem. Scope, cost, savings, incentive eligibility, procurement status, and verification evidence are facets of one object that changes over months and passes through five teams. Anything that models it as a stack of files will keep producing deliverables that quietly disagree. The fix is a system of record with one canonical project, typed data, enforced access boundaries, and generated outputs.
LumenAudit Pro holds the project as a typed record and moves it through the real lifecycle. Each stage reads what the previous stage wrote. Nothing is re-entered, so nothing can drift.
Areas, fixture counts, wattage, mounting, controls present, photos, and site conditions — captured offline on a phone or tablet.
Replacement logic, controls sequence, HVAC and EV measures, plan takeoff reconciliation, and quantity validation against the captured inventory.
Energy and demand savings, maintenance avoidance, material and labor cost, markup, incentives, payback, ROI, NPV, and IRR.
Bill of materials generated from the same counts that priced the job, with vendor packages and order tracking against the awarded scope.
Installation progress, controls verification, punch items, measurement and verification, and a closeout package that references the original audit evidence.
The proposal, BOM, and financial model are outputs of the record, not documents someone assembles afterward. Production time collapses because the assembly step disappears.
Tenant-scoped access, role boundaries, and export gating mean project data does not leak between customers or leave through an unreviewed attachment.
One count feeds every calculation. Change a quantity and the savings, the price, the incentive, and the material list all move together — or the system tells you why they can't.
Three ways to run a retrofit business. Only one of them holds state.
| Capability | Spreadsheets | Single-purpose audit tools | LumenAudit Pro |
|---|---|---|---|
| Source of truth | Whichever file was opened last | The audit, until it is exported | One tenant-scoped project record |
| Disciplines covered | Whatever you build by hand | Usually lighting only | Lighting, controls, HVAC, EV, electrical |
| Estimating and BOM | Separate workbook | Separate system | Generated from the audited counts |
| Field capture offline | Paper, then re-keyed | Varies; often connection-required | Offline-ready PWA with sync |
| Access control | File permissions | Account-level | Tenant isolation plus role scoping |
| Lifecycle coverage | Ends at the quote | Ends at the report | Runs through commissioning closeout |
Each module writes into the same canonical project. Turn one on and its measures roll into site totals, portfolio reporting, and the customer deliverable without a reconciliation step.
Capture areas, counts, wattage, burn hours, and replacements with photo evidence. Savings, proposal PDF, and Excel BOM generate from the same rows.
Design zones, write the sequence of operations, then close the loop with commissioning checks recorded against the same fixtures you audited.
Capture equipment, runtime, and efficiency inputs so mechanical measures roll into project savings and payback next to the lighting scope.
Document ports, service capacity, trenching, and utilization assumptions to size an EV opportunity against real electrical headroom.
Build estimates from assemblies and materials with labor rates, overhead, markup, and profit applied by rule instead of by memory.
Resolve electrical plan PDFs into fixture, circuit, and panel counts. Every extracted row is reviewed before it is allowed into the bid.
Model utility incentives, energy and demand savings, payback, ROI, NPV, and IRR directly from audited quantities — then track the claim.
Roll individual sites into portfolio hierarchies. Compare savings density, capital required, and pipeline stage across every property in the program.
Organization roles, approval workflow, version history, and closeout reporting so a finished project can be audited long after the crew leaves.
The free beta starts with the lighting audit workflow; the remaining modules are part of the platform and open through evaluation. Planning electrical infrastructure work first? Get a free Electrical Infrastructure Readiness Score.
Count the fixtures once. Everything below is generated from that record, which is why the quote, the material list, and the closeout packet stay in agreement.
Branded PDF with scope, savings, payback, and the assumptions written out where a facility director can check them.
Excel BOM built from the audited counts, with part detail your distributor can quote against without a translation call.
Energy, demand, and maintenance savings against installed cost. Payback, ROI, NPV, and IRR on stated assumptions.
Incentive modeling tied to the measure list, plus rebate claim tracking so the money that justified the project actually lands.
Vendor-ready buy package derived from the awarded scope, with ordering status visible on the project instead of in an inbox.
Installation records, controls verification, and measurement and verification evidence bound to the original audit rows.
Evaluation teams ask the same five questions. Here are the answers, without the marketing layer.
Every project, site, fixture, cost, and document belongs to a tenant. Access is scoped at the data layer with row-level policies, not filtered in the interface — so a misrouted link or a shared login cannot surface another customer's project.
Field capture runs as an installable progressive web app with local persistence and a sync queue. Auditors work through basements, warehouses, and parking structures with no signal, and the record reconciles when connectivity returns.
Proposal PDFs, BOM workbooks, and shared client links are gated by plan and role, and share tokens are scoped and revocable. Exports are events against the project, not files that quietly leave it.
Sites, areas, fixtures, measures, assemblies, materials, incentives, and verification records are first-class typed entities with defined relationships. Rollups are computed from those entities, so a total can always be traced back to the rows that produced it.
Encrypted transport with strict transport security, hardened response headers and content security policy, role-based authorization, two-factor authentication on platform administration, object storage for documents and photos, and error and performance monitoring on the production API.
Field counts, replacement logic, cost, photos, and the customer deliverable stay attached to one project from walkthrough through closeout.
Multi-measure projects roll up cleanly. Savings, incentives, and capital requirements hold together across lighting, controls, HVAC, and EV scope.
Standardize how every site is captured, priced, approved, and reported, so a hundred buildings behave like one repeatable process.
Takeoff, assemblies, labor, and markup live next to the audit that generated them, which removes the spreadsheet handoff entirely.
LumenAudit Pro is in free beta. Rather than fill this section with stock quotes, we are holding it for named customers and measured outcomes from the beta program. The slots below are reserved and intentionally empty.
Reserved for a beta customer's own account of moving a real project from field walk to signed proposal.
Reserved for an estimating or operations lead describing the change in proposal turnaround time.
Reserved for a multi-site program owner on portfolio standardization across properties.
Logos appear here only with written permission from the customer.
To be published with the customer's measured baseline, installed scope, verified savings, and incentive capture.
To be published with pre- and post-installation measurement and verification data.
To be published with combined lighting, controls, and mechanical scope economics.
Beta participants who run a real project end to end are invited into the case-study program. You review and approve every number before anything is published.
Join the case-study programSet the sliders to how your team actually works. The model assumes an audit reaches a proposal-ready state in about 2.4 hours on LumenAudit Pro; change that figure and the cost assumptions to match your own operation.
Planning estimate only, based on your inputs and the assumptions shown. Actual results depend on project mix and team workflow.
A ten-minute walkthrough: field capture on a phone, engineered scope, savings and incentive modeling, generated proposal and BOM, then closeout. Same record the whole way.
Full walkthrough video is being recorded
Until it is published, book a live guided demo and we will run the same five stages against a project like yours.
Live demos run on sample project data, never on another customer's records.
LumenAudit Pro is in open beta. The lighting audit-to-proposal path is free and complete. Paid tiers are published below as a roadmap so you can plan, not as a countdown timer.
No credit card. Beta users may be asked for product feedback.
For crews running continuous audit and proposal volume.
For ESCOs and multi-site programs with procurement and security review.
Beta accounts will not be converted to a paid plan without notice. Pricing, tier names, and module packaging are subject to change before general availability.
Straight answers on scope, access, and what beta actually means. If your review needs something not covered here, ask and we will send documentation rather than a sales deck.
Not yet. The current path is the free beta, which covers the lighting audit-to-proposal workflow end to end. Team and enterprise tiers are presented as a roadmap, and enterprise evaluations run through a sales-assisted process until self-service pricing is published.
One user, the lighting audit workflow, project setup, offline field capture with photos, savings and payback modeling, proposal PDF export, and Excel BOM export. No credit card. Beta onboarding and support are available by request.
Yes. Controls and sequence of operations, HVAC, EV charging, electrical estimating, plan takeoff, rebates and financials, procurement, portfolio analytics, and commissioning all live on the platform against the same project record. The free beta opens with the lighting path; the rest is available through an evaluation.
Every record carries a tenant identity and access is enforced at the database layer with row-level policies, backed by cross-tenant mutation tests in the automated suite. Exports and shared client links are gated by plan and role, and share tokens are scoped and revocable.
Yes. The Free Facility Opportunity Scanner sizes a building's retrofit opportunity with no account, and the Electrical Infrastructure Readiness Score checks service capacity before you plan EV or mechanical scope. When you join the beta you can rebuild that facility as your first real project.
Take one real site from field capture through savings, proposal, and BOM. If the numbers hold up, bring the rest of the portfolio.
Prefer a walkthrough of your own process? Book a Workflow Review