Skip to content

    Sherpa is now Navorda. Read the announcement

    Navorda
    Core platform
    Navorda Platform

    Your energy portfolio. Under control.

    Govern projects, milestones, dependencies, baselines and decisions in one place.

    See what changed across the portfolio — and give your enterprise AI read-only access to the same authorized context. A defined scope you can start with, not a transformation you have to buy first.

    Projects · Milestones · Baselines · Decisions · Reporting · MCP included

    Last updated

    See what's included
    The problem

    Your forecast changes. Your organization should remember why.

    🗂️

    Projects tracked in scattered files

    Every country, every team, its own spreadsheet. There is no current common view of the pipeline.

    ⏳

    Old expectations disappear

    The quarterly and committee baselines become hard to reconstruct. What did we expect in January? Somebody has the file.

    🔁

    Reporting needs rebuilding

    Management asks which assets moved, and the team gathers spreadsheets and emails again — for every cycle.

    The problem isn't that milestones move. It's losing the context of the change.

    What changed?

    What did we expect? What changed? Where do we act next?

    Every reporting cycle Navorda Platform locks a version — Budget, Forecast, a monthly snapshot or a custom baseline. Locked versions never change, so today's dates can always be read against what was committed, milestone by milestone, project by project.

    When the RtB forecast for next quarter moves from 820 MW to 650 MW, Navorda Platform shows the committed MW against the forecast MW for that milestone and period, and the projects behind the difference: which milestone moved, from when to when, who owns it, and the decision recorded about it where there is one. The reason is whatever the team wrote down — Navorda keeps the context, it does not invent it.

    Illustrative example with fictional data. The approved January baseline forecast 820 MW reaching RtB next quarter; the current forecast is 650 MW, a net change of minus 170 MW. Two projects explain the difference: Alcázar Solar, 120 MW, RtB moved from 15 March to 28 June, 105 days late, owner M. Ortega, decision D-041 keeps it in the Q3 portfolio; Vento Norte, 50 MW, grid approval before RtB moved from 2 February to 20 May, 107 days late, owner J. Haas, no decision recorded yet.

    Illustrative. Fictional portfolio, projects and dates. Navorda Platform compares the MW committed in the locked baseline with the MW now forecast, per milestone and period, and lists the projects and milestones behind the difference; the reason is whatever the team recorded.
    Project relationships

    When the substation slips, every project behind it knows.

    Projects rarely stand alone. Two plants share a substation; a line waits on a grid connection; a BESS is co-located with the solar park beside it. Navorda Platform records these structural relationships — project to project, plant to line to substation — separately from the milestone-to-milestone dependencies inside each project.

    An upstream slip therefore shows its downstream impact without anyone reconstructing the chain in a meeting. The chain is a property of the model, not of someone's memory.

    Illustrative dependency chain. Solar Alpha, 120 megawatt-peak, and BESS Beta, a co-located storage project, both evacuate through the shared substation Norte, which depends on a 220 kilovolt grid connection expected in September 2027. When the grid connection slips, the substation, and with it both projects, inherit the delay.

    Illustrative example.

    Included in Navorda Platform

    Eight capability groups. One project model.

    🗂️

    Projects & attributes

    Your pipeline in one governed project registry, with capacities, country, technology, responsibilities, the configurable attributes your organization actually tracks, and KPIs: metrics captured as direct input or calculated from Platform data, such as the latest permit date.

    🏁

    Milestones, templates & dependencies

    Model permits, land readiness, RtB, NtP, COD and country-specific milestones. Each milestone carries its date — past or future — a comment, and who created or changed it and when. Reuse templates and link the milestones that depend on each other.

    🪜

    Automatic stage

    Keep project progression aligned with milestone completion according to your configured rules — the stage follows the milestones, nobody sets it by hand.

    📐

    Baselines & deviations

    Freeze reference forecasts, compare versions and surface the projects and commitments whose dates changed — including the MW committed to reach a milestone in the approved baseline against the MW now forecast, period by period.

    🏢

    Project ownership & infrastructure links

    Associate projects with their SPVs and connect related assets, including shared substations and infrastructure projects. Shareholder trees are optional, in Navorda Transactions.

    📈

    Embedded reporting

    Work with the portfolio from native Navorda views, dashboards, comparisons and reports, without a separate BI implementation. The Power BI semantic twin is optional, in Navorda Connect.

    ⚖️

    Decisions

    Record management decisions in the context of the relevant project, milestones and evidence — who decided what, on whose behalf, and what follows.

    🤖

    Enterprise AI through MCP

    Connect compatible AI to the governed Platform context, read-only and under your user permissions. Navorda AI agents and the enterprise API are optional.

    Enterprise AI through MCP

    Ask your AI about the same portfolio your team governs.

    The Navorda MCP Connector is included in Navorda Platform. Your organization's own AI — Claude, ChatGPT or any MCP-compatible client — reads the governed Platform context live, read-only, under each user's permissions, instead of reasoning from exports pasted into a chat.

    • MCP Connector — included with Navorda Platform: your enterprise AI reads the permitted context.
    • Navorda AI — optional: Navorda's own embedded agents, running inside Navorda.
    • Navorda Connect — optional: the REST API, the Power BI semantic twin and enterprise integrations, for systems rather than AI.

    Illustrative exchange between a user and their enterprise AI reading Navorda through the MCP Connector. User: How many MW do we now expect to reach RtB next quarter? AI: The current forecast is 650 MW. User: What was the approved baseline? AI: 820 MW in the January baseline; the difference is −170 MW. User: Which projects explain the difference? AI: Two projects with changed RtB dates, based on the authorized milestone and baseline records: Alcázar Solar (120 MW, +105 days) and Vento Norte (50 MW, +107 days). Illustrative exchange. Answers depend on data quality, user permissions and the MCP tools currently available. The connector does not invent missing reasons or grant access to unlicensed modules.

    Illustrative exchange. Answers depend on data quality, user permissions and the MCP tools currently available. The connector does not invent missing reasons or grant access to unlicensed modules.
    Self-valuation

    What teams can now answer

    1. Which projects are drifting from the committed baseline, and when did the drift start?
    2. Which assets are at risk of missing RtB this quarter — and which permit or land milestone is the reason?
    3. How many MW reach RtB next quarter against the approved baseline, and which projects explain the difference?
    4. Which milestones (NtP, COD, PAC) have changed since the last board cycle?
    5. Which SPV owns this project?
    6. If the shared substation slips a quarter, which projects inherit the delay?
    7. What did the Investment Committee decide about this project — and did it happen?
    Getting started

    Start with your existing project list.

    1

    Bring representative projects and attributes

    Create projects or import the list you already keep. Set technology, stage, capacity, location, portfolio structure and responsibilities.

    2

    Configure milestone templates, stage logic and a baseline

    Define the milestones that match how your organization develops — permit and land-readiness milestones included — link the ones that depend on each other, set the stage rules, and lock a first baseline.

    3

    Compare changes, review reports, capture decisions, connect AI

    Read deviations against the baseline, work from the embedded views, record the decisions taken, and connect your enterprise AI through the included MCP Connector when you are ready.

    Your energy portfolio. Under control. screenshot

    The portfolio view: every project, every stage, the KPIs your board asks about — read from the same record the teams work in.

    Built on the same operating model

    One record. Every question about it.

    The milestone that gates RtB, the milestones that depend on it, the baseline it is measured against and the decision taken about it are not four lists. They are one project record — and every optional add-on, agent and connector reads that same record rather than copying it.

    Navorda Platform governs the project. Add-ons deepen specialist workflows.

    Navorda Platform includes: Project, then Milestone & dependency, then Baseline, then Decision, then Embedded report, then MCP to your AI. Optional add-ons extend it: Risks, then Parcels, then Postings, then Transactions, then Agreements, then Models, then Enterprise systems. A permit milestone slips → the milestones that depend on it move → the baseline shows the deviation → the decision taken about it is recorded on the project → the portfolio view and your enterprise AI read the same change.

    What is included

    A complete foundation. Without buying everything on day one.

    Navorda Platform includes projects with configurable attributes and KPIs; milestones for development, permitting and land readiness with templates and dependencies; automatic stage from milestone logic; baselines and deviation control, including committed versus forecast MW per milestone and period; project-to-SPV ownership; relationships between projects and shared infrastructure; embedded reporting; the Navorda Decisions register; and the included read-only MCP Connector for compatible enterprise AI.

    CapabilityNavorda PlatformOptional add-on
    Projects, configurable attributes and KPIs (manual metrics and KPIs calculated from Platform data)Included—
    Milestones, including permit and land-readiness milestonesIncluded—
    Milestone templates and dependenciesIncluded—
    Automatic project stage from milestone logicIncluded—
    Baselines and deviation controlIncluded—
    Committed versus forecast MW per milestone and periodIncluded—
    Project-to-SPV ownership associationIncluded—
    Project-to-project and shared-infrastructure relationshipsIncluded—
    In-application portfolio reportingIncluded—
    Decisions registerIncluded—
    Read-only MCP Connector for enterprise AIIncluded—
    Quantified risk management—Navorda Risks
    Geospatial land, parcels and contracts—Navorda Land
    Project financial management—Navorda Finance
    Transaction and SPA lifecycle—Navorda Transactions
    Shareholder trees and ownership percentages—Navorda Transactions
    Offtake and PPA governance—Navorda Offtake
    External Excel and model governance—External Models Governance
    Enterprise integrations with ERP, CRM and treasury—Enterprise Integrations
    Power BI Semantic Model Twin—Navorda Connect
    REST API for enterprise applications—Navorda Connect
    Embedded AI agents—Navorda AI

    Add-ons extend the same underlying project model.

    Every optional capability reads and extends the same project record. Nothing is re-entered or copied into a second system when an add-on is activated.

    Specialist depth is optional: Navorda Risks, Navorda Land, Navorda Finance, Navorda Transactions (SPAs and shareholder structures), Navorda Offtake, External Models Governance, Enterprise Integrations, Navorda Connect (Power BI Semantic Model Twin and REST API) and Navorda AI extend the same project model when the organization needs them.

    FAQ

    Frequently asked questions

    Navorda Platform includes projects with configurable attributes and KPIs; milestones for development, permitting and land readiness with templates and dependencies; automatic stage from milestone logic; baselines and deviation control, including committed versus forecast MW per milestone and period; project-to-SPV ownership; relationships between projects and shared infrastructure; embedded reporting; the Navorda Decisions register; and the included read-only MCP Connector for compatible enterprise AI. Specialist depth is optional: Navorda Risks, Navorda Land, Navorda Finance, Navorda Transactions (SPAs and shareholder structures), Navorda Offtake, External Models Governance, Enterprise Integrations, Navorda Connect (Power BI Semantic Model Twin and REST API) and Navorda AI extend the same project model when the organization needs them. Every add-on extends the same project record: existing projects, milestones and baselines stay where they are when a module is activated, and there is no separate edition — Navorda Platform is the one core product.

    Project milestone, dependency and baseline information is included, so a slipped milestone is visible without any add-on. Dedicated risk registers, scoring, mitigation tracking and quantified time-at-risk and cost-at-risk are available through Navorda Risks, an optional add-on that extends the same project record.

    Navorda Platform treats permits like any other milestone: each permit milestone carries its date — in the past or in the future — a comment, and who created or last changed it and when, with templates and dependencies around it, and the project stage is derived from them. There is no separate permit register; the milestones are the register. Specialist land parcel, contract, landowner and geospatial processes require Navorda Land.

    Yes. Navorda Platform captures metrics as direct input on each project — MW is one; your organization can add its own, such as square metres per MW — and calculates KPIs from Platform data, such as the latest permit date. A KPI whose raw material lives in an add-on needs that add-on: the secured-area percentage, computed from parcels and contracts, comes with Navorda Land.

    Yes, and it is one of the platform's strengths. For a milestone and a period, Navorda Platform shows the MW committed in the locked baseline against the MW now forecast, the difference, and the projects and milestones behind it — who owns each one and which decision, if any, was recorded about it. The reason is whatever the team wrote down; Navorda keeps the context, it does not invent it.

    Navorda Platform associates each project with its owning SPV. Shareholder structures — HoldCo relationships, shareholders, ownership percentages, cap tables and the ownership hierarchy — are part of Navorda Transactions, the optional add-on that also manages the SPAs that change them. Activating it later extends the record you already maintain.

    Yes. The Navorda MCP Connector is part of Navorda Platform for authorized, read-only access to supported Platform information from compatible enterprise AI clients. Permissions, supported tools and organizational configuration determine what each user can access: the connector is off until an admin enables it, every user authorizes their own client, and tools over add-on data return results only where that add-on is licensed.

    No. MCP lets your own compatible AI access authorized Navorda context. Navorda AI — Navorda's embedded agents, running inside Navorda — is an optional intelligence add-on. A Platform customer can use their own AI through the MCP Connector without buying Navorda AI.

    No. Native reporting is included in Navorda Platform, and so is the read-only MCP Connector. The Power BI Semantic Model Twin, the REST API and Enterprise Integrations are optional enterprise-connectivity capabilities under Navorda Connect.

    Yes. External Models Governance, an optional add-on to Navorda Platform, governs assumptions, provenance and critical outputs from external models without replacing them. Attach the project's workbook (.xlsx or .xlsm), link the output cells you care about — CapEx, IRR, NPV — to governed project fields, and each value carries its file, sheet, cell, who linked it and when, read-only while linked. Pair the model's assumption cells (NtP, MW, CapEx, tariff) with the live project fields they should mirror: when the project moves and the model does not, the project shows a model-outdated warning and the outputs from that workbook are flagged as stale. Checks only read and compare; nothing is written into the model or into Navorda. Links and checks target project-level fields today, and linked values are not exposed through the MCP Connector, Navorda Connect or Navorda AI. Details: navorda.com/products/external-models

    Yes. Navorda Platform is designed to start with the projects and milestones the organization needs to govern and to expand as requirements grow — bring your existing project list, set your milestone templates, lock a first baseline. Actual onboarding, contract scope and active-project limits depend on the agreed subscription.

    Yes. Add-ons extend the same underlying project model. Existing projects, milestones and baselines remain in Navorda while the enabled workflows expand, subject to deployment details — nothing is re-entered or migrated to a second system.

    Yes. Navorda Decisions, part of Navorda Platform, is the governance register: each investment committee, board or steering committee decision is recorded on the project it concerns with its forum, date, reference in the minutes, rationale and alternatives, approved amount and capacity, and the counterpart it was taken on behalf of — the COO, the Investment Committee, a shareholder, an SPV, a lender. Conditions carry a status and a due date, commitments become owned, dated Activities, evidence is attached, and closing a decision stamps the date and the user. Records are versioned and role-based like the rest of the platform, and the Navorda MCP Connector exposes them read-only. It is a register of record, not an approval workflow: it does not route approvals, collect votes or sign documents. Details: navorda.com/products/decisions

    Your portfolio, governed from the first milestone.

    Start with the project information you already maintain. Add workflows, models and integrations as your organization needs them.

    Explore pricing