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 plan
Use this when the CRM issue is valuable enough to inspect inside the full AI System Plan.
- Plan path
- Build decision
- Pipeline view
AI system fit
What AI can run here
For power bess crm fields, the useful AI system is not a generic chatbot. It is an operating layer that reads project or buyer context, prepares the next owner action, flags missing information, and keeps follow-up visible. The team still owns technical judgment, pricing, plan, proposal language, and customer commitments.
Inputs to bring
Bring the source material already used to judge the opportunity: CRM fields, RFQs, forms, call notes, proposal status, files, source pages, buyer role, owner, due date, and missing facts.
- CRM and forms
- RFQ or proposal context
- Owner and due date
Useful AI work
AI can summarize inquiries, classify readiness, draft missing-info requests, prepare handoff notes, update operating views, and surface stale follow-up before opportunities drift.
- Summaries
- Readiness classification
- Follow-up prep
Human gate
A person approves technical fit, engineering assumptions, pricing, legal terms, customer promises, sensitive language, and whether the opportunity deserves specialist time.
- Technical approval
- Pricing and plan
- Customer promise
Next pages
Keep the diagnosis connected
Technical buyers often need more than one page before they trust the recommendation. These links connect the specific problem to the larger AI System Plan path.
Technical AI Systems
Use the hub when the team needs the full view of project context, specialist handoff, proposal follow-up, and pipeline visibility.
- Hub
- Use cases
- Technical fit
Run the scorecard
Use the AI Infrastructure Scorecard when the page points to a repeatable project context or qualified-demand problem.
- Inputs
- Build decision
- Next step
Conversion Skills
Use Conversion Skills to see the public method behind prompts, tools, review gates, handoffs, and repeatable AI work.
- Skills
- Tools
- Review
Next step
Find the gap first
Start with the repeated work, the source material, and the business result. Then choose strategy, an agent, or a custom AI system.
Choose the AI path