Field Notes
Why We Built Solar1: Operating Principles for a Connected Install Business
Fragmented tools cost installers more than they think — in margin, in mistakes, and in the hours nobody bills for. The thesis behind Solar1, and the principles that guide how we build it.
We started Solar1 after watching capable solar teams lose money not to competition or hardware, but to their own tooling. The work was good. The system around the work was a patchwork. And the patchwork quietly taxed every job.
The thesis
An install business runs on one thing: an accurate, shared picture of every project from first call to PTO. When that picture is split across a CRM, a design tool, spreadsheets, and an accounting package, every handoff is a chance to lose information — and every lost piece of information is rework, delay, or margin gone.
So we built Solar1 around a single operating record instead of another point tool. The goal isn’t to add software; it’s to remove the seams between the software you already depend on.
The principles we build by
- One record over many copies — a project should have a single source of truth, not five drifting versions.
- Connect, don’t rip-and-replace — your team already runs tools that work; Solar1 syncs with them rather than forcing a migration.
- Automate the busywork — if a human is copying data between systems, that’s a bug we should fix, not a job we should staff.
- Make the money legible — finance should never trail the field; status and billing live on the same record.
Where we’re headed
Every release pushes toward the same end state: an installer can run sales, design, permitting, install, and finance on one connected record, and spend their time on jobs instead of on reconciling tools. That’s the business we wanted to exist. So we’re building it.