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.
Jamie Duncan
If you run a US solar or battery installer in the 5-15 person range, there's a good chance Pipedrive is in your stack. The reason is honest: it's the friendliest sales pipeline you can buy. The alternative for that team size is HubSpot (heavier than you need), Salesforce (more expensive than you want to admit) or ServiceTitan (priced for HVAC contractors at scale, not clean energy SMBs). Pipedrive installs in a morning and your sales rep actually opens it in the morning.
The pipeline view works. The drag-and-drop stages work. The forecast view is good enough. For the first 12-18 months the tool delivers what it promises.
The problem isn't the sales pipeline. The problem is the right-hand edge of the pipeline. Pipedrive stops at deal-closed. For a solar or battery installer in the US, deal-closed is when the real operational work starts: site survey package, Authority Having Jurisdiction (AHJ) permit application, utility interconnection submission, install scheduling, commissioning and Permission to Operate (PTO), Investment Tax Credit (ITC) documentation for the customer. That work happens in spreadsheets, a second SaaS tool, or someone's head. None of those scale past around 15 installs a month.
See the Pipedrive-to-Payaca handoff side by side
The clearest 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 AHJ permits, utility interconnection state and ITC documentation tracking.
Credit where it's due. Pipedrive is the SMB CRM that installs without an implementation consultant and gets used.
Sales reps adopt it. The pipeline view is genuinely useful, every deal in a column-per-stage layout with the deal 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 holds up in the field. 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 lead qualification, track the proposal sent, see the deal sitting in "verbal yes" 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 - and Pipedrive doesn't see any of it.
Every installer hits the same wall, usually around the time monthly volume reaches 15+ installs or the first dedicated operations hire is made.
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 operational work opens up that Pipedrive doesn't model.
A second tool gets bought, or a spreadsheet appears in Google Drive, to track:
None of these are exotic edge cases. They are the operational core of every US install business. And they all live outside Pipedrive.
The cost isn't the subscription on the second tool. It's the gap between systems. The customer's address is re-typed in three places, the permit application is delayed because the survey notes weren't transferred, the ITC paperwork is missing when the customer asks for it at tax time the following spring.
Installers we've spoken to running a Pipedrive + spreadsheets + permitting-tool 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 9kW residential solar plus 13.5kWh battery install, say - and walk it through both systems.
Pipedrive: A new deal is created, customer details captured, source tagged ("Google", "referral", "EnergySage"). Drag the deal into "Site visit 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 at this stage. The data model is doing more work behind the scenes - the same record will follow the customer through to PTO - but the screens look the same.
Pipedrive: The surveyor visits the property, takes measurements, takes photos of the main panel and the roof. Photos get emailed to the office or uploaded to Google Drive. System design is done in a separate tool (Aurora, OpenSolar, Scoop Solar). 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 design data live against the project record. Design tool integrations mean the system specs, the production estimate and the layout are pulled in. The proposal builds from that data without re-keying.
Pipedrive: A proposal is generated in a separate tool (Better Proposals, PandaDoc, an in-house template). 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 specs, the production estimate, the federal ITC line, any state or utility incentives, the financing options, 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 permitting tool, or the operations manager's head takes over.
Payaca: The same project record moves into the install pipeline. The AHJ permit stage opens with the right submission portal for that jurisdiction. The utility interconnection state appears as a field with deadlines attached. The install scheduling assigns crew and materials against the same record. Nothing is re-typed.
Pipedrive: This is where the parallel universe operates. The permit application is filled in by hand from the surveyor's notes. The interconnection portal is logged into separately, the submission number copied back to a finance spreadsheet. The install team works off a printed sheet. The PTO arrives weeks after install and gets stuck to the corner of someone's monitor. The ITC documentation is assembled in the spring when the customer's accountant emails asking for it.
Payaca: Every compliance step is a stage in the project workflow with the data already in place. AHJ permit submission can be enforced as a gate before install. Utility interconnection state is on the project. Install scheduling pulls from the same crew calendar. Commissioning is signed off in-app and the PTO request triggers automatically. The customer's ITC documentation pack is generated from the record on demand.
This is the part Pipedrive cannot do, and not because of a missing integration. The data model doesn't have a place for it.
US installers in the 10-25 install per month range running Pipedrive plus spreadsheets typically show one of three signs that the operational layer is breaking.
The first sign is the office coordinator. A full-time person whose job is reconciling data between Pipedrive, the design tool, the permitting tool, the interconnection portals and the install scheduler. Re-typing addresses, chasing survey notes, updating the install calendar. This role gets hired 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 permit application that didn't get filed because nobody updated the spreadsheet. An interconnection application that was approved months ago but install was scheduled before the approval was attached. A PTO that got delayed because the inspection sign-off didn't propagate. Individually each one is cleaned up with apologetic emails. Collectively they erode margin and customer-survey scores.
The third sign is the ITC documentation request. The customer's accountant emails in February asking for the system commissioning date, the line-item invoice and the spec sheet for the equipment installed. The information exists, but it's scattered across the proposal tool, the permit portal, the install scheduler and the finance spreadsheet. The hour of office time it takes to assemble that pack is the unbilled cost of the disconnected stack.
Pipedrive shows up on inbound calls from US installers more than any other named CRM at the SMB end of the market. The pattern is consistent.
The business adopts Pipedrive when it's 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 twelve weeks of operational work, depending on AHJ and utility timelines. The spreadsheets multiply.
A separate tool gets bought for the design (Aurora, OpenSolar). Then another for permitting (Solo, PVComplete). Then another for scheduling. Pipedrive stays, but it's now the smallest tool in the stack and the rest of the operation runs elsewhere.
The decision to move is usually triggered by one of two events: the office coordinator quits and the new hire can't make sense of the system, or an ITC documentation gap embarrasses the business with a customer at tax time.
Honest answer: if your business is genuinely sales-only, with installation subcontracted out and a third party handling the permit and interconnection 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 site visit 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 operations 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 US 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 or AHJ permit state.
Mid-sized US solar and clean-energy installers spend two engineers a year keeping a bespoke CRM alive that handles maybe 60% of the workflow. Permits, AHJ inspections, NEM interconnection and ITC handling end up on spreadsheets. Here's the real cost of the build, and what the off-ramp usually looks like.
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.