CRM for Solar Business: How to Choose a System That Won't Leak Your Deals

A solar business doesn't lose deals because of price or product. It loses them in the gaps between touchpoints: the rep didn't call back after the site survey, forgot about the customer who's "thinking it over," sent a quote and never checked whether it was opened. Over a two-to-four-month stretch from inquiry to contract, one missed task costs you a $5,000–20,000 deal.

At Brutal Marketing we've been implementing CRM for solar energy companies for years, and we keep seeing the same pattern. Leads are coming in, the ads are working, the surveyors are on the road — and the pipeline is leaking. Deals slip between stages, nobody knows how many are actually in play, and the owner finds out the month flopped when the money is already gone.

Below is how to choose a CRM that fits the specifics of a solar business, which features actually matter (and which ones vendors push for no reason), how to build a pipeline for a long sales cycle, and where companies most often go wrong during implementation. No "digital transformation" theory — just what we do with our hands on real projects, and what directly moves the number of signed contracts.

Take the typical journey of a solar customer. They leave an inquiry, get a callback, agree to a survey, an engineer drives out, the project is calculated, a quote goes out, the customer leaves to "think," in two weeks they need a nudge, then approval, contract, prepayment, installation. That's 8–12 touchpoints stretched across months.

The cause of the losses isn't lazy reps — it's the absence of a system that holds all those touchpoints together. Thirty to fifty active deals don't fit in your head or a notebook. The customer who'll "come back next month" simply drops out. And over a quarter, those dropouts add up to half your plan.

A CRM fixes this not by magic but by mechanics: every deal sits on a specific stage, each has a next action with a date, and none hangs without a task. The rep opens the system in the morning and sees who to call today — no digging through chats and sticky notes. If you're still weighing the idea itself, we covered the basics separately in our piece on why your business needs a CRM and how to tell from the symptoms.

A lot of owners drag their feet until they hit a wall. Here are the concrete signals that the system was needed yesterday:

• You can't answer in under a minute how many deals are in play and for what total amount.
• Reps track customers in their own notebooks, spreadsheets, and phones — each in their own way.
• When a rep quits, part of the database walks out the door with them.
• The ad inquiries are there, but you have no idea which channel produces contracts.
• Customers complain that nobody called them back, even though it was promised.
• You learn the sales month flopped in its final week, when it's already too late.

If you recognize even three of these, you're already losing money — you just can't see where. A CRM makes those losses visible, and therefore manageable.

This is the key point that "solar CRM" vendors skip over. Before you pick a system, understand what makes the niche specific — otherwise you'll set up a pipeline like it's an online store and wonder why it doesn't work.

A long sales cycle
From inquiry to signature takes anywhere from three weeks to six months; in B2B and agricultural projects, longer. The customer compares contractors, waits for the season, sorts out financing. The pipeline has to survive a long "ripening" without losing the lead, and the rep has to remember every one of dozens of customers in progress. At that scale, memory and a notebook simply can't cope.

A high average deal size
A residential system runs $4,000–15,000; a commercial one, tens or hundreds of thousands. At that deal size, the cost of one lost sale justifies the entire CRM implementation. There are no "cheap" leads here — every one is worth fighting for.

A mandatory field stage
The survey and project design are a separate stage with their own logistics. An engineer goes to the site, and that work needs to be visible in the system: assigned, completed, tied to the deal with photos and roof parameters.

A technical product
Capacity, panel type, inverter, batteries, ties to feed-in tariffs or net-billing schemes — these are all parameters of a specific deal. A CRM has to store them as structured data, not as text in a note.

Seasonal demand
Peaks in spring and summer, a trough in winter. Without source analytics you pour ad budget in at the wrong moment and have no idea which channel brings real contracts rather than just inquiries. Seasonality also means a share of customers deliberately postpone the purchase to the warm season — and without a reminder system, those people just get lost. A CRM lets you plan demand: pull "postponed" leads back in as the season starts and ramp up ads when the customer is ready to pay.

These five differences are exactly where the requirements for a system come from. Now, point by point.

So we don't stay in generalities, here's the mechanic on a typical scenario we regularly see with clients before implementation.

A company sells residential systems, average deal $8,000. About 120 ad inquiries come in monthly, 60 surveys get done, and 9 contracts close. Inquiry-to-contract conversion is 7.5%. The owner is convinced the problem is lead quality and wants to pour in more budget.

The real cause turns out to be different. When we pull the data, it shows that after the quote goes out, the team simply stops working the customer. The rep made one touch, the customer said "I'll think about it," and the deal hung there without a task forever. Of 60 quotes sent, only 15 got a follow-up. The other 45 aren't "bad leads" — they're money the company threw away itself.

The fix isn't a bigger budget; it's discipline in follow-up. After we set up the pipeline and automate follow-up, every deal on the "quote sent" stage gets a chain of tasks: a call on day three, an email with a payback calculation on day seven, a check-in call on day fourteen. The rep doesn't decide whether to remember — the system walks them through it.

The result over two or three months is predictable: at the same inquiry volume nearly every quote gets followed up, and inquiry-to-contract conversion climbs from 7–8% to 11–13%. For a company with an $8,000 deal size, that's several extra contracts a month — tens of thousands in revenue without a single extra dollar in ads. That's exactly why implementation in a solar business pays off so fast: you're not buying new customers, you're just stopping the loss of the ones you already paid for.

The feature list in any CRM is long, and vendors love to sell "everything at once." In practice a narrow set does the work for a solar business. Here's what you can't skip.

The problem: a generic "new → in progress → closed" pipeline is useless for a long cycle. You can't see where exactly customers get stuck.

The cause: the stages don't reflect the real process. Survey, project, quote, approval — each is a point where the deal can die, and each needs to be visible on its own.

The fix: a pipeline built for your process with 7–9 stages, each deal carrying a status, an owner, an amount, and a win probability. Then you open a report and see: the "quote sent" stage holds 18 deals worth $140,000, and half have no task. That's your growth zone right there. For more on this, see our piece on how to spot the stage in the funnel where leads get lost.

The problem: 80% of deals in a solar business need 4+ touches, and most reps make one or two and quit.
The cause: remembering dozens of "postponed" customers by hand is impossible. A person physically can't hold who to call back in 10 days versus in a month.

The fix: automation creates the task for you. The customer moves to the "thinking it over" stage — after a set interval the system creates a "call" task, sends an email with a payback calculation, or fires a reminder. The rep doesn't decide whether to remember; they just close the tasks the system feeds them. It's worth setting up regular subscription-based messaging on top of that, so cold leads ripen with no manual effort.

The problem: the rep sent a quote and has no idea what's next. The customer is silent — because they didn't open it, changed their mind, or are just busy? With no data, you're guessing.

The fix: email open tracking shows whether the quote was read and how many times. If a customer opened the calculation three times in one day, that's a hot signal — call today. If they never opened it, the problem is the subject line or the contact. The logic of timely, relevant outreach is laid out in our piece on how to build an effective B2B messaging strategy.

The problem: reps price systems in Excel or in their heads, get the price and configuration wrong, and bleed margin on discounts they hand out on their own.

The fix: a catalog of panels, inverters, and batteries inside the CRM. The rep assembles a spec from ready-made items, the system totals it, records the discount, and won't let anyone go below the floor without approval. The deal price stops being improvisation.

The problem: the engineer gets back from the site in the evening, and the survey data lands in the system a day later — if at all.

The fix: a CRM mobile app where the surveyor updates the deal right on site, attaches roof photos, sets parameters, and moves the stage. The information doesn't get lost on the road. Why mobile and remote access matters so much for a field team, we covered in our guide on running a CRM for remote and field work.

The problem: the owner sees revenue after the fact and can't tell which ads produce contracts and which produce junk inquiries.

The cause: inquiries get counted, contracts don't. The lead source gets lost on the way to the sale.

The fix: pipeline reports plus end-to-end analytics that tie an ad channel to a closed deal. You don't see "1,000 clicks," you see "channel X delivered 40 inquiries, 6 contracts, $48,000 in revenue at $1,200 in spend." That's what your in-season budget decision is built on. For how this plays out on real data, see our breakdown of how CRM, PPC, and end-to-end analytics combine to drive growth.

The problem: the customer wrote on Instagram, then called, then emailed a question — and three different reps talk to them without knowing about each other. The person repeats everything for the third time and gets annoyed.

The cause: communication channels aren't pulled into one place. Each rep sees only their slice of the conversation.

The fix: a shared team inbox and a single deal card holding the whole history — calls, emails, messenger threads. Any rep opens the card and sees the full context. For an expensive product with a long cycle this is critical: the customer feels remembered, not processed like a number in a queue. The way good service compounds into repeat business is covered in our piece on how to increase customer loyalty.

The problem: a solar business piles up a huge database of customers who said "not now, maybe in spring" — and then forgets about them forever.

The cause: these leads didn't refuse, they postponed. But with no mechanism to bring them back, they sit in the database as dead weight, even though half of them are still planning a system.

The fix: database segmentation and automated touches timed to the season. The CRM lets you pull everyone who postponed and launch a chain — an email with updated prices, a reminder about feed-in tariff terms, an offer of a free payback recalculation. For a solar business with its seasonality, that's a separate sales channel that costs nothing in ad spend. The database you've already built brings in contracts year after year when it's worked properly.

The problem: the owner logs into the CRM once a week, drowns in deal cards, and can't tell in a minute what's happening with sales.

The fix: dashboards with the key metrics — revenue, deals on each stage, conversion, average deal size, month-end forecast. The owner opens one screen and sees the whole picture, without diving into details and without asking the sales head "how are we doing." That's control without micromanagement: you see the numbers instead of nagging people.

This is where companies overpay most often. There are niche "solar CRMs" tailored to the energy sector, and they cost several times more. The vendor's pitch: "everything's built for solar out of the box."

In practice, for a small or mid-size business a universal system with a sound setup closes 95% of the tasks for less money. The specifics of a solar business aren't unique features — they're a properly configured pipeline, deal fields, and automation. All of that is done on Pipedrive or Kommo.

A comparison of the two systems we implement most often:

If the bulk of your inquiries come from messengers and Instagram, look at Kommo CRM. If you run classic project-based sales with a long pipeline, Pipedrive will fit better. There's no universal answer: the choice depends on where your leads come from and how your process is built.

A word on the money. Niche solar CRMs position themselves as "everything for energy out of the box," but you pay for it with a subscription several times higher, and you often get a rigid system you can't bend to your process. A universal platform is cheaper, more flexible, and evolves faster, because it has thousands of times more users and a dedicated development team behind it. In years of work we've never met a solar-business task that couldn't be solved on a universal CRM with the right setup. Paying many times more for the word "solar" in the name is not the best use of your budget.

A CRM doesn't sell on its own. What sells is a properly configured process inside it. Here's a working pipeline structure for selling systems that you can take as a starting point:

1. New inquiry — the lead came in, the contact is captured, the source is tagged automatically.
2. Qualification — the rep made contact and understands the site, the budget, the readiness. Non-targets get filtered out here.
3. Survey scheduled — the engineer's visit date is agreed.
4. Survey done — site data is in the system, the project can be calculated.
5. Quote sent — the proposal with a payback calculation went to the customer.
6. Approval — the customer is deciding, touches continue, objections get handled.
7. Contract and prepayment — the financial terms are locked in.
8. Installation — the deal is handed to production.
9. Closed/won — the money is in.

The core rule: at every stage the deal always has a next task with a date. A deal without a task is a deal you're already losing. Set up automatic control: if a deal sits on a stage longer than the norm (say, "quote sent" for more than 5 days with no activity), the system flags it to the manager.

Set up separate fields for the technical parameters too: capacity, roof type, feed-in tariff eligibility, system type. That gives the rep and the analytics what a default CRM doesn't have. How structured customer work keeps a buyer engaged through a long cycle is covered in our breakdown of leads, lead generation, and lead management.

Over years of rollouts we've collected the list of rakes almost everyone steps on. Knowing them in advance saves you months and money.

Mistake 1. Rolling out the tool with no process
A company buys a CRM, moves its chaos into it, and is surprised nothing changed. A CRM doesn't create a sales process — it automates one. First you describe the pipeline, then you configure the system.

Mistake 2. Too many stages and fields
Trying to capture everything, they build a 15-step pipeline with 40 required fields. Reps sabotage it because filling it in takes too long. Start with a minimum viable version and build up.

Mistake 3. Nobody supervises usage
The system gets set up, the team gets trained — and then it's forgotten. A month later half the deals have no tasks and the fields are empty. Without quality control over the sales team, a CRM degrades into an expensive notebook.

Mistake 4. Ignoring source analytics
They count only the bottom-line revenue and never see which ad channel brings contracts. In season they pour budget in blind.

Mistake 5. Not training the team
Reps see the CRM as surveillance and work around it. Implementation isn't just configuration — it's explaining to people how the system makes their job easier. For the full set of rakes, see our piece on why CRM implementations fail and how to fix it.

A CRM with no integrations is a closed box that reps key data into by hand. Half the losses happen right at the seams: the website inquiry didn't arrive, the call wasn't logged, the messenger message slipped through. Here's what you have to connect.

Website and forms
Inquiries from landing pages and quizzes should drop into the CRM automatically and with the source attached. If a rep enters a lead by hand an hour after it came in, the customer is already talking to a competitor. With an expensive product, the speed of the first touch decides.

Telephony
Calls get recorded and tied to the deal. That's both quality control (you can listen to how a rep handled a price objection) and saved context. The manager sees who's calling, how much, and with what result.

Messengers and social
In a solar business a huge share of inquiries comes from Instagram, Telegram, and WhatsApp. If the conversation lives in a rep's phone instead of the CRM, you lose the database when they quit. Integration pulls every channel into the system.

Analytics
Connecting the CRM to ad accounts and analytics platforms closes the loop: you see the path from click to contract. For what that gives you in practice, see our breakdown of how to work with CRM analytics.

You don't have to connect everything on day one. But if telephony and website inquiries aren't integrated, you're losing data every single day and not even noticing it.

So the rollout doesn't drag on for six months and end in a dead system, stick to a clear sequence. Here's the order we launch projects in.

1. Describe the sales process. Before configuring any software, fix the real customer journey on paper: stages, owners, what happens at each step. This is the foundation — without it, any CRM is useless.
2. Choose a system to fit the process. Based on the described process and your lead sources, the platform gets selected. If you're not sure where to begin at all, refresh the basics in our piece on what a CRM system is for.
3. Configure the pipeline and fields. Stages, required fields, technical site parameters, product catalog. A minimum viable version, no overload.
4. Set up automation. Tasks for touches, reminders, trigger emails, control over stalled deals.
5. Integrate the channels. Website, telephony, messengers, analytics — by priority.
6. Train the team. Not "here's the system" but explaining how it makes the rep's job easier. Without buy-in from people, the rollout fails.
7. Supervise and refine. The first weeks matter most. You check how deals are run, what's getting in the way, what to refine. After that the system lives and grows.

Skipping the first step is the most expensive mistake. A company that buys a CRM first and only then thinks about how to work in it ends up rebuilding the project twice.

A basic CRM implementation for a small or mid-size solar business starts at $500–1,500, depending on the system, the number of integrations, and the depth of automation. That's not an expense — it's an investment that pays for itself with one or two saved deals, and at a deal size in the thousands, that happens in the very first month.

On timelines, a standard turnkey implementation takes 2 to 6 weeks. A simple pipeline with basic automation comes together faster. A complex project with telephony, website, messenger, and end-to-end analytics integration sits closer to the upper bound. We've collected the common questions on cost, stages, and pitfalls in a separate piece on CRM implementation cost, timeline, and system types.

Don't chase the cheapest or the most feature-stuffed option. Chase the one that fits your process and that the team will actually use. The best CRM is the one your reps run deals in every day, not the one with the most features in the demo. If you're weighing the approach itself, compare the paths in our piece on whether to buy, build, or configure a CRM, then look at CRM implementation for your business.

We'll build a CRM around your solar sales process: configure the pipeline for a long cycle, automate follow-up, and connect source analytics — so not a single $10,000 lead drops out of the work.

Order CRM implementation for your solar business from Brutal Marketing.