The software

Built for the half of the job nobody built for.

R11 is operations software for residential solar contractors. It holds every installation on one record, from the signed contract through utility approval, and does the office work that sits between those two points: permitting and interconnection filings, funder document packages and milestone tracking, document filing, and the daily assignments that move a job forward.

Every tool a solar contractor owns was built to win the sale. The half that comes after it, the permits, the funder packages, the utility, the inspections, was left to spreadsheets and whoever has been there longest. That half decides how many jobs you can actually deliver, and it is the one R11 is built for.

See it run a job

Bring the job that is already late.

ContractSurveyDesignPermitInstallInspectPTOpermit filedpackage sentphotos filedone recordcontract to PTO

What it runs

  • Anyone in the office can answer where a job is

    Every installation sits on one record that runs from the signed contract through site survey, design, permitting, install, inspection, and utility approval. The stage a job is at is a fact on the record, not a guess assembled from a spreadsheet, an inbox, and a group text.

    • One record per installation
    • Contract through PTO
    • No side spreadsheet
    spreadsheet?inbox?group text?1420 RidgeviewPermitting, day 6everyone gets the same answer
  • Work stops living in one coordinator's head

    Tasks, assignments, comments, and holds sit on the project itself rather than in somebody's inbox. When the person who knew is out, the job does not stop, because what it is waiting on is written on the job.

    • Assigned on the project
    • Holds are visible
    • Survives a day off
    1420 RidgeviewOrder the meter socketDLCity wants a revised plan setMRon hold, waiting on the citySchedule the inspectionDL
  • The document is already where you would look for it

    Permits, site photos, plan sets, and contracts land in that customer's existing folder in the contractor's own Google Drive. Your paperwork accumulates in the account you already own, so it is never hostage to a vendor and never in a folder nobody can find twice.

    • Your Drive, your account
    • Filed to the customer folder
    • Every write logged
    PermitPlan setSite photos1420 Ridgeviewyour Drive, your accountevery write recorded in the audit log
  • You find out a job is stuck before the funder does

    Funding milestones are recorded as the financier reports them, and what is still outstanding is visible on the day it becomes outstanding. A finished install and a funded install are different facts, and any system that quietly treats them as one will eventually report money that never arrived.

    • Reported, not inferred
    • Outstanding stays outstanding
    • Dated to the report
    Install milestonereported Jul 2Activation at PTOoutstanding since Jul 8recorded as the financier reports it, never predicted

Start without switching

R11 reads your design tool, your CRM, your funder portals and your accounting system on day one. Nothing to migrate, no re-entering your book, and no implementation quarter before the first job runs through it.

From there it takes the delivery work over one workflow at a time, until the record the office opens is R11 and the spreadsheet beside it is the thing nobody has needed this week. Your documents sit in your own Google Drive throughout, because the ambition is to own the work, not to hold your paperwork hostage. If you are placing this beside what you already own, operations software and a CRM solve different halves of the job.

See what it connects to

Put your worst job through it.

Not a prepared demo. The install that is already late, already redesigned, and already missing a document. That is the one worth watching.

See it run a job