The short answer
What matters here
Proposal tracking is the sales process around a solar design and offer. Teams need to know which version was discussed, what the homeowner asked, who owns the next conversation, and whether the deal is ready for contract or needs another design or finance review.
A practical workflow
Treat the proposal as a decision process
The proposal file matters, but the surrounding decisions determine whether the deal advances cleanly.
- 01
Keep the offer in context
Attach or link the relevant design, utility information, financing context, and current sales stage.
- 02
Capture the review
Record homeowner questions and any requested changes so the next conversation starts from the right version.
- 03
Own the follow-up
Assign a specific next action and date rather than treating a sent proposal as a completed task.
- 04
Hand off the accepted offer
Carry the agreed scope and documents into contract and installation planning.
Buyer's checklist
Questions to ask about proposal follow-up
Use these questions with your team and any CRM provider. The answers should reflect your actual process, including exceptions.
- Can we identify the proposal version tied to the current deal?
- Where are requested design and finance changes recorded?
- Who follows up when a proposal is pending?
- What information moves forward when the customer signs?
How Spark fits
Keep design and sales context together
Spark describes proposal and design integrations alongside a shared CRM record. Scope the exact documents, versions, and approval steps your team needs during a demo.
Book a DemoExplore the relevant parts of Spark
Common questions
Clarify the decision
Is this a solar design tool?
No. This workflow concerns the CRM record and follow-up around a proposal. Design creation belongs in the tools your team uses for that work.
What changes when a proposal is revised?
The team should preserve which offer is current, why it changed, and whether pricing, contract, or operations details need another review.