Services / Finance-Fit Intake

Finance-Fit Intake

Structured intake for finance-aware Energy System Packs, beneficiary evidence, supplier-risk screening, BYOS readiness, orchestration fit, and Community Energy Bank readiness.

Finance-Fit Intake

Start a structured intake before the review conversation becomes expensive or ambiguous

Use this intake to collect the minimum context for finance-route screening, beneficiary evidence, supplier-risk review, orchestration fit, and Community Energy Bank readiness.

Abstract intake and qualification visual showing buyer, region, supplier, telemetry, and finance-route inputs.

pilot-readyServices / Finance-Fit Intake

The intake prepares a review request only. It does not confirm eligibility or create an approval.

This route opens a structured email draft from the static release. No backend ticket, CRM record, or automated intake system is created here.

Use the intake when the discussion is concrete enough to classify buyer, jurisdiction, assets, finance route, supplier-risk posture, orchestration readiness, and Community Energy Bank relevance.

Audience

Municipalities • C&I operators • SMEs

Core Focus

Hero: Start a Finance-Fit Energy System Intake

Best Next Route

Supplier Candidate Intake

Start Here

Qualification dimensionsField guide and grouped questionsBuyer classes and jurisdiction pathOrchestration and Community Energy Bank readiness

Intake Next Move

Use this route when a visitor is ready to move from conceptual pack reading into a structured qualification request that a human reviewer can actually act on.

Review five-score pack screening

Jump To Section

Finance-Fit Intake Guide

Hero: Start a Finance-Fit Energy System Intake

The intake collects enough structured context to classify a prospect by buyer class, jurisdiction, use case, asset state, BESS / BYOS readiness, finance route interest, beneficiary class, supplier-risk posture, orchestration readiness, and Community Energy Bank fit.

• The output is a structured review request for a human follow-up, not an automated approval workflow.
• This route is designed for storage-first Energy System Packs and related diligence, not for generic contact traffic.

What this intake does

The intake gathers evidence and unknowns early so the follow-up discussion starts from concrete facts instead of broad sales language.

• Classify buyer, region, project type, and operating objective
• Map asset state, telemetry posture, and BYOS conditions
• Identify likely finance route, beneficiary class, and public-sector constraints
• Prepare a clean handoff for finance-fit review, pack review, regional mapping, Community Energy Bank finance, or future scoring work

What this intake does not do

The intake is a qualification and evidence-gathering flow. It is not a substitute for advisors, authorities, or final engineering review.

• No grant application, funding approval, or supplier approval
• No tax-credit qualification, permit approval, or interconnection approval
• No legal, tax, accounting, procurement, engineering, or cybersecurity certification advice
• No savings guarantee or grid-revenue guarantee

Qualification dimensions

Each intake is classified across the core readiness dimensions below before it moves into a human review path.

Dimension	Purpose
Jurisdiction and authority path	Identify country, state, utility/DSO area, AHJ, and public-sector constraints.
Beneficiary class	Identify buyer class and possible funding-route evidence needs.
Asset and BYOS state	Map PV, BESS, inverter/PCS, EMS/BMS, metering, telemetry, and mixed-fleet status.
Supplier-risk posture	Identify provider-fit, cloud/control-chain, firmware, and service-route issues.
Finance-fit pathway	Map grants, rebates, tax credits, loans, leases, PPAs, ESCO, public procurement, or community finance.
Orchestration readiness	Map telemetry, identity, control boundaries, reserve policy, operator approval, and audit evidence.
Community Energy Bank readiness	Map asset, capacity, reserve-policy, event, allocation, assurance, and governance ledger readiness.

Intake questions / field guide

The on-page workspace uses these grouped questions and mirrors them into the prepared email draft.

Group	Field	Input	Notes
Organization and scope	Organization	Text	Identify the request owner, commercial position, and jurisdiction path before deeper review.
Organization and scope	Role	Text	Use a real-world role or function, not an internal system role.
Organization and scope	Buyer class	Select	Identify the request owner, commercial position, and jurisdiction path before deeper review.
Organization and scope	Region / jurisdiction	Select	Identify the request owner, commercial position, and jurisdiction path before deeper review.
Organization and scope	Utility / DSO / AHJ if known	Text	Capture the authority path if it is already known.
Organization and scope	Project type	Text	Example: retrofit, new build, public resilience, shared storage.
Use case and assets	Use case	Select	Map the operating objective, site scale, and current asset posture, including BYOS context.
Use case and assets	Approximate size	Text	Use a simple class or rough kWh / MW estimate if known.
Use case and assets	Existing assets	Select	Map the operating objective, site scale, and current asset posture, including BYOS context.
Use case and assets	BESS / BYOS status	Text	Summarize whether this is native, retrofit, mixed-fleet, or uncertain.
Use case and assets	Preferred supplier or hardware	Text	Optional candidate hardware or supplier direction.
Telemetry and orchestration readiness	Telemetry availability	Select	Capture control visibility, cloud dependency, and the minimum inputs needed for orchestration-fit review.
Telemetry and orchestration readiness	Remote monitoring / cloud dependency	Select	Capture control visibility, cloud dependency, and the minimum inputs needed for orchestration-fit review.
Finance and beneficiary posture	Funding route of interest	Select	Map the likely finance route, beneficiary class, and review timing without overstating eligibility.
Finance and beneficiary posture	Beneficiary class	Text	Use the simplest beneficiary label that matters for program or procurement review.
Finance and beneficiary posture	Public-sector constraints	Textarea	Use when procurement, security, public-benefit, or authority constraints already exist.
Finance and beneficiary posture	Community Energy Bank relevance	Select	Map the likely finance route, beneficiary class, and review timing without overstating eligibility.
Finance and beneficiary posture	Timeline	Text	Capture urgency, deadline pressure, or deployment window.
Primary follow-up risk	Primary risk / question	Textarea	Summarize the main uncertainty or blocker.
Primary follow-up risk	Preferred next step	Select	State the blocking issue and the preferred human follow-up once the intake reaches review.

This route remains a static mailto flow. It prepares a structured email draft only.

Buyer classes

Use the closest buyer class first, then refine the beneficiary and jurisdiction details in the intake form.

• municipality / public sector
• C&I / campus
• SME
• industrial
• rural business / farm
• energy community
• school / hospital / public facility
• EPC / installer
• hardware / OEM
• utility / DSO reviewer
• nonprofit / community facility
• residential / small site
• strategic investor / partner
• other

Region and jurisdiction path

Region is used as an entry point. Utility / DSO / AHJ details matter when authority path or interconnection posture is already known.

• USA
• EU
• Bulgaria
• Germany
• Netherlands
• Spain
• France
• Italy
• Portugal
• Texas
• California
• New York
• Florida
• Hawaii
• Rural USA
• Other / not sure

Funding route interests

Funding interest is treated as a readiness signal, not a claim of program eligibility or funding approval.

• grant / rebate
• tax credit / domestic content
• loan / guarantee
• lease / PPA / ESCO
• public procurement
• community / cooperative finance
• private finance
• not sure yet

Asset / BYOS status

Asset-state capture helps determine whether the next step is finance review only, pack review, orchestration readiness, or mixed-fleet diligence.

• new project
• existing PV / solar
• existing BESS
• existing inverter / PCS
• existing EMS / BMS
• mixed BYOS fleet
• existing telemetry
• site only / no assets yet
• not sure
• Common use case: backup reserve
• Common use case: peak shaving
• Common use case: self-consumption
• Common use case: grid congestion

Orchestration and CEB readiness

This intake formalizes two additional readiness layers so future scoring UI work can start from consistent intake evidence.

Model	Score	Label	Meaning
CS-ORCHESTRATION-FIT	OF-A	Operator-ready	Telemetry, control boundaries, reserve policy, and operator workflow are already legible.
CS-ORCHESTRATION-FIT	OF-B	Telemetry-ready	Telemetry and visibility are strong, but operator workflow or reserve policy still needs review.
CS-ORCHESTRATION-FIT	OF-C	Pilot-mappable	A bounded pilot path is plausible with adapter, workflow, or telemetry-gap work.
CS-ORCHESTRATION-FIT	OF-D	Gap-heavy	Major gaps remain in telemetry, control-chain, auditability, or local operator ownership.
CS-ORCHESTRATION-FIT	OF-X	Out of scope	Current control posture is too opaque or too risky for responsible orchestration review.
CS-CEB-FIT	CEB-A	Ledger-ready	Asset, capacity, reserve, event, allocation, assurance, and governance inputs are mostly available.
CS-CEB-FIT	CEB-B	Governance-ready	Governance and reporting logic are plausible, but some metering or reserve details still need work.
CS-CEB-FIT	CEB-C	Concept-ready	A Community Energy Bank path is commercially relevant but still early in asset or governance definition.
CS-CEB-FIT	CEB-D	Needs structure	Shared-storage governance, beneficiary mapping, or reporting evidence is materially incomplete.
CS-CEB-FIT	CEB-X	Not relevant now	Community Energy Bank logic is not presently a meaningful fit for the project path.

Static inquiry handoff

When the visitor starts the intake, the shared inquiry workspace opens a structured field set and ends by preparing a mail draft.

• This opens an email draft. No backend ticket is created by the static release.
• The resulting draft preserves the route, intent, routing tag, and structured question set.
• Use Contact if the visitor needs a broader pilot, partner, research, or general inquiry path instead.

Boundary note

The intake prepares a structured review request only. It does not confirm eligibility, approvals, savings, or revenue.

• The intake prepares a review request only.
• It does not confirm eligibility.
• It does not create a grant, loan, tax, permit, interconnection, or procurement approval.
• It does not provide legal, tax, accounting, procurement, engineering, or cybersecurity certification advice.
• All program, supplier, and jurisdictional data must be refreshed before reliance.

Related Routes

Supplier Candidate Intake

Intake

Have supplier evidence to submit for review? Start the Supplier Candidate Intake to map provider fit, sovereign/control-chain posture, finance evidence, orchestration readiness, and Community Energy Bank readiness.

Supplier Candidate Registry

Registry

Before a supplier can be considered for an Energy System Pack, CitizenSolar screens provider fit, sovereign/control-chain posture, finance evidence, orchestration readiness, and Community Energy Bank readiness where applicable.

California Energy System Pack Mapping

Pilot

For a USA C&I example, review California Energy System Pack Mapping for peak shaving, BESS/BYOS readiness, and finance-fit screening.

Bulgaria Energy System Pack Mapping

Pilot

For an EU municipal example, review Bulgaria Energy System Pack Mapping for Community Energy Bank and public-resilience readiness.

Finance-Fit Energy System Review

Finance

Canonical bounded review service for finance-route, beneficiary, and supplier-risk readiness.

Five-Score Pack Screening

Screening

Public readiness-classification model for provider fit, sovereign stack, finance fit, orchestration readiness, and Community Energy Bank readiness.

Energy System Packs

Finance

Commercial pack architecture for finance-aware storage-first deployment packaging.

USA Energy System Packs

Catalog

Illustrative USA pack catalog for beneficiary, supplier, and finance-route mapping.

EU Energy System Packs

Catalog

Illustrative EU pack catalog for beneficiary, sovereignty, and finance-route mapping.

Finance-Ready Pack Architecture

Finance

Evidence model for provider, sovereign, finance, beneficiary, supplier, and reporting readiness.

Community Energy Bank Ledgers

Banking

Seven-ledger structure relevant to Community Energy Bank fit and governance evidence.

Orchestration Readiness Review

Service

Operational readiness route for telemetry, reserve policy, BYOS integration, and operator workflow review.

Contact

Generic static inquiry route if the intake is not the right starting point.

Recommended Next Action

Continue through the right route

Review five-score pack screening