Pipedrive works well for the sales pipeline but stops at the deal-closed line. For UK solar, heat pump and battery installers, that's where the real work begins. A side-by-side workflow walkthrough: lead, quote, DNO, MCS, BUS, install, handover.
Jamie Duncan
Pipedrive shows up in a lot of growing installer businesses for an honest reason: it's the friendliest sales CRM you can buy. A 5-15-person solar or heat pump team picks it up because the alternative is HubSpot (heavier than they need) or Salesforce (more expensive than they want to admit). For the first 18 months Pipedrive delivers exactly what's promised - a clean visual pipeline, drag-and-drop deal stages, a sales rep who actually opens it every morning.
The problem isn't the sales pipeline. The problem is the line at the right-hand edge of the pipeline. Pipedrive stops at deal-closed. For a clean energy installer, deal-closed is when the real work starts: Microgeneration Certification Scheme (MCS) documentation, Distribution Network Operator (DNO) submission, Boiler Upgrade Scheme V5 (BUS V5) voucher state, install scheduling, commissioning sign-off, handover pack. That work happens in spreadsheets, in a second tool, or in someone's head. None of those scale.
See the Pipedrive-to-Payaca handoff side by side
The cleanest way to see where the line falls is a 20-minute walkthrough on your own workflow. Book a demo and we'll map your Pipedrive stages onto Payaca's project lifecycle, including DNO state, MCS doc pack and BUS voucher tracking.
Credit where it's due. Pipedrive is the SMB CRM that installs in a morning and gets used.
Sales reps adopt it. The pipeline view is genuinely useful: every deal in one column-per-stage layout, with a value next to it and a probability next to that. Activity tracking is light enough that reps don't resent logging calls. The mobile app is decent. The price point sits between "free spreadsheet" and "enterprise SaaS" without making anyone defensive at the board meeting.
For an installer doing 5-15 deals a month with one or two sales people, that's enough. You can run early-stage lead qualification, track the proposal sent, see the deal sitting in "verbal yes" for too long, and forecast the next 60 days with reasonable accuracy.
If the only thing your business does is the lead-to-close part of the journey, Pipedrive is a fine tool and you can stop reading.
The reason this post exists is that the lead-to-close part is roughly a third of the work in a clean energy install business. The other two thirds is what happens after the customer signs.
Every installer hits the same wall, usually around the time they start doing 15+ installs a month or hire their first dedicated ops person.
The wall has a specific shape. A deal moves to "won". The sales rep updates the stage in Pipedrive. And then a parallel universe of work opens up that Pipedrive simply doesn't know about.
A new spreadsheet appears in Google Drive, or a separate tool gets bought, to track:
None of these are exotic edge cases. They are the operational core of every install business. And they all live outside Pipedrive.
The cost isn't the subscription on the second tool. The cost is the gap between systems. The data is copied by hand, the customer's address is re-typed in three places, the DNO application is delayed because nobody updated the spreadsheet, the commissioning certificate is missing when the customer asks for it a year later.
Installers we've spoken to running a Pipedrive + spreadsheet stack consistently describe the same shape: the sales side works, the install side limps, and the office coordinator spends an hour every morning reconciling data across tools.
Pick a single project - a heat pump install for a detached house, say - and walk it through both systems.
Pipedrive: A new deal is created, customer details captured, source tagged ("Google", "referral", "MCS Find an Installer"). Drag the deal into "Survey booked". This works fine in both systems.
Payaca: A new project is created in the sales pipeline, customer details capture identical fields, source tagged. Visually similar to Pipedrive. The data model is doing more work behind the scenes - the same record will follow the customer through to commissioning - but at this stage they look the same.
Pipedrive: The surveyor visits the property, takes measurements, takes photos. Photos get emailed to the office or uploaded to Google Drive. Heat loss calculation is done in a separate spreadsheet or a tool like Heatpunk. The result is a PDF that someone attaches to the Pipedrive deal as a note.
Payaca: The same survey happens, but the photos and the heat loss data live against the project record. Heatpunk integration means the calculation is pulled in, the system design is on the same record as the customer details. The proposal builds from that data.
Pipedrive: A proposal is generated in a separate tool (Better Proposals, PandaDoc, Word, a templated PDF). It's emailed to the customer. The deal stage moves to "Proposal sent". If the customer views it, you might know via the proposal tool, not via Pipedrive.
Payaca: The proposal is generated from the project record. It includes the system design, the BUS voucher amount applied as an upfront discount (V5 requirement since 28 April 2026), the warranty terms, the deposit schedule. The customer signs in-app. The deal stage updates automatically.
This is the line.
Pipedrive: The deal moves to "Won". Pipedrive's job is done. A spreadsheet, a Trello board, a separate field service tool, or a project manager's head takes over.
Payaca: The same project record moves into the install pipeline. The MCS doc pack stage opens. The DNO submission state appears as a field with deadlines attached. The BUS voucher claim moves into a tracked status. The install scheduling assigns crew and materials against the same record. Nothing is re-typed.
Pipedrive: This is where the parallel universe operates. The DNO application is filled in by hand from the surveyor's notes. The MCS commissioning certificate is uploaded to the office filing system. The BUS voucher is tracked in a finance spreadsheet. The install team works off a printed sheet that gets binned at the end of the week. The customer's handover pack is assembled the day before by someone digging through email.
Payaca: Every compliance step is a stage in the project workflow, with the data already there. DNO submission can be enforced as a gate before install (so an install never goes ahead with the paperwork outstanding). MCS commissioning is signed off in-app and the MID submission is one action away. BUS voucher state is on the project. The handover pack is generated from what's already on the record.
This is the part Pipedrive simply cannot do, and not for lack of customisation - the data model doesn't have a place for it.
Installers in the 10-25 install per month range running Pipedrive + spreadsheets typically have one of three signs that the operational layer is starting to break.
The first sign is the office coordinator. A full-time person whose job is reconciling data between systems. Re-typing addresses, chasing the survey notes, updating the install calendar. This role is created out of necessity and never gets the credit it deserves. It's also the first cost a unified system removes.
The second sign is the missed compliance step. A DNO application that didn't get sent because nobody updated the spreadsheet. A BUS voucher that expired because the install slipped. An MCS commissioning that got handed over without the certificate. These are not catastrophes individually - they're cleaned up afterwards with apologetic emails and rework. Collectively they erode margin and reputation.
The third sign is the customer who calls in a year later asking for their handover pack. The information exists somewhere, but it's scattered across the proposal tool, the DNO portal, the MCS database, the install scheduling tool and the finance spreadsheet. The hour of office time it takes to assemble that pack is the unbilled cost of the disconnected stack.
We hear Pipedrive on inbound calls more than any other named CRM at the SMB end of the market. The pattern is consistent.
The business adopts Pipedrive when they're 5-10 people, doing 5-15 deals a month, with one sales person who needed a tool. It works. The business grows. The install side grows faster than the sales side because every closed deal is six to eight weeks of operational work. The spreadsheets multiply.
A separate tool gets bought for one of the compliance gaps - typically the design (Heatpunk, Easy MCS, Open Solar) or the proposals. Then another for scheduling. Pipedrive stays, but it's now the smallest tool in the stack and the rest of the operation is run elsewhere.
The decision to move is usually triggered by one of two events: an office coordinator leaves and the new hire can't make sense of the system, or a missed compliance step embarrasses the business with a customer.
Honest answer: if your business is genuinely sales-only, with installation subcontracted out and a third party handling the compliance pack, Pipedrive is the right answer. You don't need an install operations platform if you don't run installs.
You also don't need Payaca yet if you're under five installs a month and the founder is still doing every survey personally. The systems overhead doesn't pay back at that volume.
The crossover point we see most often is at 15 installs a month, or the moment the first dedicated ops hire is made.
Almost no one rips Pipedrive out cold. The pattern is:
A migration run this way typically takes 4-6 weeks. The painful part is the operational cutover, not the Pipedrive export.
See how Payaca helps clean tech installers save time and grow their business.
Book a demo
Decision-stage migration guide for UK clean-energy installers leaving HubSpot. What imports cleanly, what doesn't, what HubSpot stays good at, and how to sequence a 4-week cutover without losing project history.
Mid-sized UK installers spend two engineers a year maintaining a bespoke CRM that handles maybe 60% of the workflow. The other 40% is on spreadsheets. Here's what's actually being paid for, and why the build never catches up to MCS, DNO and BUS V5.
Pipedrive is the SMB sales pipeline that lots of US solar and battery installers reach for first. It does the sales side well and stops at deal-closed. A side-by-side workflow walkthrough through permitting, interconnection, ITC documentation, install and PTO.