Financier

GoodLeap and R11

GoodLeap is a residential solar financier that pays installers in milestones as a project moves from contract through installation to grid connection.

Where it stops

Almost no installer runs one funder. They run several, and each one's milestone vocabulary means something different: M1 is contract at one funder and installation at another, and a document package that satisfied one funder comes back from the next for a standard nobody wrote down. Offices learn these rules by rejection, one returned submission at a time, and the accumulated knowledge ends up in whichever coordinator has been there longest rather than anywhere the company owns.

What R11 does with it

• Each funder's milestones are kept in that funder's own terms, so a label is never silently translated into another funder's meaning.
• A package is built the way this funder wants it rather than the way the last one did, so the rules live in the system instead of in one person's memory.
• A returned or rejected submission becomes a visible hold on the job, not an email that one person saw.

Questions

Does R11 replace the GoodLeap portal?

The funder's portal stays the funder's portal. R11 owns the work around it: what was submitted, what came back, what is still outstanding, and which job each of those belongs to. That work is where the delay actually accumulates.

What happens when GoodLeap changes its requirements?

The requirement changes in one place rather than in several people's habits. That is the point of holding funder rules on the system instead of in the team's memory, and it is why a rule change does not have to be relearned by rejection.

Can R11 change anything in our GoodLeap account?

The connection reads only. R11 records what the financier reports and writes nothing back to it.