Surge Products: The Equipment List

This page is a list of equipment, not a brochure. One paragraph per product. What it does, what it runs on, and the case where you should not buy it.

The list exists because the same conversation keeps happening after an implementation. The pipeline is configured, the fields are agreed, the team has been trained. Something still does not work. It is almost never the CRM as a whole. It is one specific gap: a question reporting cannot answer, a data set nobody trusts, a sending volume a normal mailbox cannot carry. Each product below closes one of those gaps and nothing else.

None of this is a suite. Each tool is licensed on its own and works against a standard Pipedrive account through the API. You can run one of them, or none of them. If the honest answer to a section below is that you do not have that problem, skip it. A tool bought for a problem you do not have becomes a maintenance obligation.

Data and reporting

Surge Reports

Reporting that spans more than one object. It reads deals, activities, people, organisations and products together, so a single view can answer questions Pipedrive Insights has to split across several reports. Typical output is a dashboard on revenue, source and rep performance, priced from 1,500 euro depending on how many questions it has to answer. The mechanics of that gap are set out on the reporting page. You do not need it when every question you ask fits inside one object. Deal counts, pipeline value, win rate by stage: Insights already does that, and doing it twice is worse than doing it once.

Surge Dedupe

Duplicate detection across people, organisations and deals, matching on email address, phone number and name. It scores candidate pairs and presents them for review. A human decides which record survives and which fields carry over, every single time. Nothing is combined without that decision. The full anatomy is on the duplicate records page. You do not need it in an account under roughly five thousand records with one intake route, because the merge feature inside Pipedrive plus a monthly hygiene pass will keep up on its own.

Getting data in and out

Surge Shift

Migration tooling. It maps source fields to Pipedrive fields, runs imports in a fixed object order, keeps the source identifier on every record, and produces reconciliation counts you can check against the old system. It is built for the case where the source is a real CRM with relations, history and attachments. The procedure it follows is documented on the migration page. You do not need it for one spreadsheet of five hundred rows. That is a morning of careful column work and the standard Pipedrive importer.

Surge Connect

A connection layer between AI assistants and the CRM, using OAuth 2.1 and scoped access rather than a shared API token pasted into a chat window. It exists because the fastest way to leak a customer database in 2026 is an assistant with unrestricted read access and no audit trail. Token and webhook basics are covered in the admin glossary entry. You do not need it if nobody at your company points an AI assistant at company data, or if your policy already forbids it.

Demand and intake

Surge Reach

Sending at volume with domain warm up, suppression handling and unsubscribe management, writing activity back to Pipedrive so replies land on the right record. Volume is the reason it exists: past a few thousand messages a month, a normal mailbox becomes a liability rather than a channel. The trade-offs are on the outbound page. You do not need it below a few hundred emails a month. At that size your own mailbox is more deliverable than any platform, and personal beats scaled every time.

Surge Forms

Forms that write straight into the CRM, with validation on the fields that matter and routing built into the submission rather than bolted on afterwards. The value is that the record arrives complete, so it can be assigned by rule instead of by hand. See lead routing for what that enables. You do not need it when your existing website forms already post clean, mapped data into Pipedrive and nothing is being retyped.

Surge Chat

An embeddable chat widget that qualifies the visitor and creates the record in the CRM with the conversation attached. It suits sites where a real question arrives outside the form, and where somebody is actually available to answer. You do not need it if your traffic is thin, or if nobody can respond within the hour. An unanswered chat widget is worse for trust than no widget at all.

Proposals

Surge Quote

It starts from the transcript of a sales conversation and turns that into a proposal. You steer the draft with prompts until it says what was actually agreed, then publish it as a public link you can share with the buyer. The gap it closes sits between the call and the document, where the words that convinced somebody get replaced by last quarter's template. What the native route looks like is on the quotes and documents page. You do not need it when your proposal comes out of a fixed template and rarely varies. If scope, price and terms are the same every time, a Smart Docs template with merge fields is faster and there is nothing left to steer.

Setup and adoption

Surge Setup

Guided configuration of a Pipedrive account: pipelines, stages, fields, permissions and the automation layer, built from answers rather than from a blank screen. It compresses the work described in the six step method for teams that want to drive it themselves. You do not need it if a partner already built your account and the team uses it without complaint. Rebuilding a working setup is the most expensive way to feel productive.

Surge Adopt

Adoption measurement: which habits stick, which fields stay empty, which users quietly stopped logging activity. It includes a Chrome extension on manifest v3 for the nudges that have to happen inside the CRM screen. The extension is published in the Chrome Web Store, so it installs like any other. You do not need it when adoption is already visible in your data and your managers act on what they see.

What we do not build

Two exclusions, so the list is honest. We do not take on work without a CRM component, and we do not build standalone websites. Both are fine businesses. Neither is ours, and the products above exist only because they came out of implementation work.