Partner pathway
When a project needs finance analysis outside your core scope.
This is not a partner programme or a referral funnel. It is a quiet coordination route for specialists who need a finance workstream without displacing the lead adviser.
Handoff map
Keep each specialist inside the work they are best placed to own.
| Lead specialist | What stays with them | Where I can add finance analysis |
|---|---|---|
| Lawyers | Legal interpretation, drafting and enforceability | Translate PPA, payment security, termination and covenant positions into cash-flow and financing consequences. |
| Technical advisers | Engineering assumptions, certification and technical diligence | Translate yield, availability, degradation, CAPEX and schedule into sensitivities, coverage and returns. |
| EPC teams | Scope, delivery, pricing and construction execution | Test what EPC price, contingency, delay or change-order exposure does to debt headroom and sponsor economics. |
| Consultants / advisers | Client relationship, strategy and lead mandate | Add modelling, risk-to-cash analysis, memo drafting or decision support behind the team. |
| Developers | Project ownership and development decisions | Add temporary project-finance capacity where the internal team is overloaded or a specific model / lender workstream needs an owner. |
Ways to work
Coordination should be simpler than the project.
You introduce the project and I work directly with the project owner on a clearly separated finance scope.
You remain the lead adviser and I own a defined modelling, finance-review or decision-support workstream alongside the wider mandate.
Where appropriate, outputs can follow your team format and remain behind your client relationship.
Commercial boundary
Explicit before private files move.
Referral, joint-delivery or white-label terms are agreed case by case before work starts. An introduction does not create a commission, exclusivity or fee-sharing arrangement.
NDA, conflict considerations, ownership of client communication and review responsibility are clarified before confidential project files are shared.
Refer a live project
Start with the non-confidential decision problem.
Private files can follow after scope, roles and confidentiality requirements are clear.