Capacity
Show load requirement, duration, redundancy need, expansion plan, and whether the request is tied to a live project.
- Load requirement
- Duration
- Expansion plan
Power And BESS CRM
Show readiness.
Power and BESS opportunities stall when the CRM only says lead, meeting, or proposal. The useful fields show whether the project is real, ready, owned, and moving.
Direct answer
Power and BESS CRM fields should show readiness.
The core CRM fields are capacity need, use case, site control, interconnect status, timeline, buyer role, budget confidence, partner dependency, proposal status, owner, and next action.
Site
Capture geography, site control, interconnect status, utility dependency, and known facility constraints.
- Site control
- Interconnect
- Utility dependency
Commercial path
Track buyer role, decision path, budget confidence, proposal owner, next action, and deadline risk.
- Buyer role
- Proposal owner
- Deadline risk
Field set
Keep the fields useful enough for the weekly review.
A field only earns its place if it changes routing, follow-up, specialist involvement, or forecast visibility.
Must-have
Capacity, site, buyer role, project stage, owner, next action, and stale reason.
- Capacity
- Owner
- Next action
Risk fields
Interconnect uncertainty, finance dependency, partner dependency, procurement path, and schedule risk.
- Interconnect
- Finance dependency
- Schedule risk
Status fields
Proposal sent, buyer input missing, technical review needed, partner waiting, and decision date.
- Proposal status
- Missing input
- Decision date
Related paths
Connect CRM fields to the larger qualification system.
Power and BESS fields work best when project readiness, buyer role, and inquiry routing are handled consistently.
Project readiness scorecard
Use this when the team needs a simple red/yellow/green readiness view before handoff.
- Readiness score
- Routing signal
- Next step
Buyer roles
Use this when the same inquiry could come from an owner, EPC, developer, team, or finance stakeholder.
- Role
- Decision path
- Handoff
Power and BESS audit
Use this when the CRM issue is valuable enough to inspect inside the full Revenue Audit.
- Audit path
- Build case
- Pipeline view
Next step
Start with the audit.
If there is a measurable revenue problem worth fixing, the Revenue Audit shows whether a Revenue System Sprint is the right next move.
Apply for a Revenue Audit