Capacity
Show load requirement, duration, redundancy need, expansion plan, and whether the request is tied to a live project.
- Load requirement
- Duration
- Expansion plan
Engine for technical B2B · Power And BESS CRM
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
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.
Show load requirement, duration, redundancy need, expansion plan, and whether the request is tied to a live project.
Capture geography, site control, interconnect status, utility dependency, and known facility constraints.
Track buyer role, decision path, budget confidence, proposal owner, next action, and deadline risk.
Field set
A field only earns its place if it changes routing, follow-up, specialist involvement, or forecast visibility.
Capacity, site, buyer role, project stage, owner, next action, and stale reason.
Interconnect uncertainty, finance dependency, partner dependency, procurement path, and schedule risk.
Proposal sent, buyer input missing, technical review needed, partner waiting, and decision date.
Related paths
Power and BESS fields work best when project readiness, buyer role, and inquiry routing are handled consistently.
Use this when the team needs a simple red/yellow/green readiness view before handoff.
Use this when the same inquiry could come from an owner, EPC, developer, team, or finance stakeholder.
Use this when the CRM issue is valuable enough to inspect inside the full AI System Plan.
Next step
The free plan reviews your current CRM fields and lists the few readiness fields worth adding for power and BESS deals.
Get your free plan