Built around the solar handoff. Configured around your workflow.
Solar1 is an early-stage software startup operating from India and building an operating system for U.S. solar installers and EPCs.
Fit and implementation scope are confirmed during a guided assessment.
A connected foundation for the U.S. solar business
Founded in 2025, Solar1 is an early-stage, founder-led software startup operating from Kerala, India and building primarily for solar installation companies and EPCs in the United States.
We are building a connected platform for CRM, project operations, permitting, interconnection, field teams, inventory, finance, service, and the other workflows involved in running a solar installation business.
Our core ERP foundation is functional. We are working with the market to build deeper solar-specific workflows and prepare the platform for early design partners.
We are also building toward an agentic AI layer across Solar1's structured operational data to help teams understand projects, surface blockers, retrieve information, recommend next actions, and safely execute approved workflows.
The team building Solar1
Founder-led, with product, engineering, and go-to-market working together.
Swalah Kenb
Founder, CEO & CTO
Leading Solar1 and its product and engineering direction.
Mohammed Salman
A shared record only helps when the handoffs are clear.
Solar teams often rely on several useful systems. The operating problem appears when project context is rebuilt between them and ownership becomes unclear.
Understand the systems, project records, owners, approvals, and exceptions a team uses before proposing configuration.
Stages, fields, permissions, and reporting views should reflect the work a team is responsible for today.
Validation, role-based training, and an explicit operating owner are part of making a new workflow usable.
Map the operating problem before configuring software
The assessment follows the transitions where context is most often lost: proposal to permit, permit to install, field update to invoice, and invoice to job margin.
View the platformConfiguration should match the way the team is accountable
Project stages, fields, approvals, permissions, and reporting views are scoped against current projects, then validated with representative records before wider use.
Read pricingImplementation principles for an early-access rollout.
What a connected operating record should make clearer
The focus is practical: preserve context, clarify ownership, and make recurring operating decisions easier to review.
The signed proposal should become an operations record without a manual rebuild.
AHJ, interconnection, inspection, and PTO status should stay visible to the team that depends on it.
Labor, materials, subcontractors, and milestone billing should stay tied to the job while it is moving.
Fit, configuration, validation, and role training should be agreed before the team depends on the workflow.
Common questions
About Solar1 — answered directly.
Why does Solar1 begin with a workflow assessment?
A solar operation already has systems, trackers, approvals, and role boundaries. The assessment identifies what should remain, what must connect, and what a useful configuration needs to support.
Is Solar1 intended to replace every tool immediately?
No. The rollout should identify the authoritative system for each record and use configured handoffs where another tool should remain in place.
Why emphasize early access?
Because it is the honest buying path right now. Teams should request access, walk through their workflow, and confirm fit before relying on Solar1 for operations.
See whether the Solar1 record fits your team.
Bring the workflow you run today. We will map the handoffs honestly and show what Solar1 can support in early access.