Portfolio
Everything referred, wherever it got to. Dead and parked deals stay in every denominator on this page \u2014 a partner who brought forty sites and funded one is a different partner from one who brought one and funded one.
Conversion
Where the money is
Why deals died
Matrix
Every live project as a square. Click one to open it. Position is what it means: right is a better grid connection, up is better numbers, and the corner where both are high is where buyers actually are.
Pipeline
Where every live deal sits. A stage with a ▲ has deals that cannot pass its gate yet — click it to see which.Board
Drag a card to move it; the gates still apply, so a card that lands somewhere it has not earned bounces back and says what is missing. Use Columns to hide stages you do not work.
Verification
Third-party feasibility and bankability review, in the same console as everything else. Assign a deal to a reviewer, watch the clock, read the signed opinion.
Assignments
| Site | Reviewer | Asked for | Status | Turnaround | Verdict |
|---|
Pipeline
Every deal, with who brought it and how far it got. Attribution locks when a deal leaves Referred.
Deals
| Site | Brought by | Stage | Size | Capex | Closed | Drawn | Age |
|---|
Imported deals
| Site | Brought by | Came in | Stage | Screening rep | Still to fill in | Age |
|---|
Partners
Two relationships per organisation, counted separately: what they brought and what they supplied. A manufacturer who refers a site and then sells you its cells is doing both, and one combined number hides the second.
By organisation
Sorted by capital closed on deals they originated. Set what each one is to us, and tick the ones we co-develop with — those get their own book on the JD partners tab.
| Organisation | Role in the ecosystem | Joint development | Referred | Live | Funded | Conversion | Closed $ | Supplied $ | Median days to close |
|---|
JD partners
The partnerships we develop inside. Each one is its own book with its own finish line — a project is ready when it reaches the stage that partner takes over at, not when it reaches ours. These projects still count everywhere else on this portfolio; this is the granular view.
Funding
Five numbers, never merged: requested, committed, closed, drawn, deployed. Committed is a promise, closed is a legal obligation, drawn is cash that moved, and deployed is what is actually in the ground.
Draws needing action
Requested or approved, not yet funded| Site | Draw | Purpose | Amount | Status | Requested |
|---|
Funded deals
| Site | Investor | Closed | Drawn | Undrawn | Deployed | Utilisation |
|---|
Supply and BOM
Every bill-of-materials line across the portfolio, by supplier. This is the loop back to the partner who referred the site: the referral and the purchase order it produced sit in the same view.
By supplier
| Supplier | Lines | Deals | Specified $ | Committed $ | Also referred |
|---|
All lines
| Site | Category | Item | Supplier | Qty | Total | Status |
|---|
Inbox
Deals that already exist in the marketplace, the intake queue and the editor, and are not yet in the portfolio. Adopting links the two records — nothing is copied and nothing moves.
Adoptable records
| Record | Source | Filed by | Status | Size | Suggested stage |
|---|
Buyer Folder
How close each project is to the Omega Buyer’s Marketplace, by the six data sets a buyer receives: Summary, Scope, Technical, Engineering / IA, Financial and Legal. This is a different question from the stage ladder — a site can sit in permitting with no legal package at all — so it sits alongside the Matrix rather than replacing it.
Closest to the marketplace
| Project | Ready | The six data sets | Blocking |
|---|
Design
Every project in the site editor. The ones created from a deal carry it with them; the rest are older drawings you can still open, and link to a deal if they belong to one.
Editor projects
| Project | Client | Mode | Deal | Elements | Updated |
|---|
Assignments
Who is carrying what. Assignment is a different axis from stage — a deal in pre-development may have design finished and permitting stalled, and one in permitting may have design not started.
By person
| Person | Deals | Design lead | Dev lead | Next due | Overdue |
|---|
Unassigned past screening
Deals we are spending on with nobody named| Site | Stage | Capex | Age |
|---|
Users
Approve access, set roles, and scope limited administrators to the organisations they manage. Nobody can grant a role above their own, approve themselves, or touch the owner account. Accounts are suspended, never deleted — the record of who had access, and when, is the one thing you need after an incident.
Access requests and members
| Person | Organisation | Role | Status | Last seen | Actions |
|---|
Settings
Your profile and how this console behaves for you. Changes apply everywhere immediately — the Users page, every assignee dropdown, and the name against your activity lines.
Profile
Access
This console
Organisations
What kind of partner each organisation is, and the referral arrangement. This lives on the company, not on whoever from it happens to be logged in.
Registry
| Organisation | Kind | Referral basis | Agreement | Brought / touched |
|---|