In short
To choose a B2B CRM, I would start with the sales process: who receives enquiries, how they are assigned, when they become deals and who should follow up with the prospect. I would then compare HubSpot, Pipedrive and Zoho using the same workflow, including the website, email, WhatsApp, permissions and data exports. The choice depends on the cost of a working system, not the licence alone.
Key takeaways
- Separate companies, people and deals: a shared address book is not enough to manage sales.
- For each requirement, distinguish between an included feature, a higher-tier plan, an add-on and an external integration.
- Connect the website to the CRM with rules for deduplication, assignment and error handling.
- Treat enquiry responses, service messages and promotions as separate workflows.
- Compare the total first-year cost and test how you would leave the system too.
When enquiries arrive through the website, replies stay in personal inboxes and agreements are made in chat, the problem is not finding another place to store contacts. It is building a reliable picture of sales activity: who is looking after the company, what has been promised and which action is still missing.
I would approach CRM selection by clarifying the handover from lead generation to sales. B2B lead generation strategies bring in enquiries; the sales system needs to turn them into assigned tasks and clearly defined opportunities. Otherwise, you invest in acquisition without knowing where the process breaks down.
What is a B2B CRM, and when are Excel and email no longer enough?
A B2B CRM is a system for organising business relationships between your company and other businesses, connecting companies, contacts, sales opportunities and activities. I see it as useful when it needs to coordinate people's work, rather than simply replace a spreadsheet.
In the model I would set up, the customer company is separate from its contacts. A deal represents a specific sales opportunity; activities are the calls, meetings and follow-ups needed to move it forward. The sales pipeline is the sequence of stages these opportunities pass through.
A spreadsheet may still be enough if the process is simple and one person can keep it up to date. Its limits become clear when others need to know about a change, when the contact changes or when nobody knows whether a quote has been followed up.
- An enquiry is forwarded to several salespeople without an explicit owner.
- The same company appears under different names, with a fragmented history.
- A deal is marked as open but has no next action.
- Sales forecasts depend on people's memories.
- Handovers require searching through emails, chats and documents.
If you recognise these problems, the useful work is to design the workflow before buying the software: that is where I would start when planning lead capture and CRM. I would not choose a complex system simply to tidy up an address book.
Which requirements should you gather before choosing a CRM?
I would gather requirements described as testable actions, rather than feature names. “Integrate email” is too vague; “link a reply to the right person without making it visible to external sales agents” gives you something to test.
For each requirement, I would write down who uses it, what result they need and what would make the solution unacceptable. I would keep essential requirements separate from nice-to-haves: an interesting feature does not make up for poorly configured data access.
| Area | Requirement to bring to the demo | Acceptance criterion |
|---|---|---|
| Companies and contacts | Link several people to the same company and distinguish their roles. | The salesperson can identify the technical contact, purchasing contact and decision-maker without duplicating the company. |
| Website | Capture an enquiry and recognise an existing contact. | The enquiry is recorded without creating unnecessary records, and its source is retained. |
| Send, receive and link relevant conversations. | Replies, attachments and visibility follow the agreed workflow. | |
| Sales team and agents | Separate account portfolios, territories and responsibilities. | An agent sees what they need to manage, without viewing or exporting unauthorised data. |
| Automation | Assign an enquiry and create the next follow-up task. | Exceptions reach a responsible person rather than remaining hidden. |
| Reporting | Review conversions, timings and opportunities with no next activity. | Results can be traced back to individual records. |
| Leaving the system | Export data and rebuild associations. | Companies, people and deals can still be linked outside the CRM. |
An API is an interface that allows two software systems to exchange data. A workflow is a rule that performs actions when a condition is met. I would not add them to the requirements out of habit: I would ask which exchanges and automated actions are actually needed, how often and with what error handling.
This also brings in the choice between an all-in-one platform or an integrated stack, meaning a set of connected tools. I prefer to avoid unnecessary connections, but I would not sacrifice a process that already works simply to bring everything under one subscription.
HubSpot, Pipedrive or Zoho CRM: which meets your needs?
I would not name one universally best B2B CRM. I would take the same data and steps into each shortlisted system, comparing the plan actually required: the product name alone does not describe what you are buying.
In the table, I separate documented features from my selection guidance. By native, I mean a feature managed within the product: this does not mean it is included in every plan. An add-on extends the product; an external integration introduces another service to manage.
| CRM | When I would shortlist it | Documented features and plans | What to ask the supplier to demonstrate |
|---|---|---|---|
| HubSpot | When I want to assess sales work and enquiry handovers between departments together. | The Workflows tool documentation lists Sales Hub Professional and Enterprise among the eligible subscriptions, according to the official HubSpot guide. | I would ask for a breakdown of the products and user access required, then test capture, assignment, email and deal progression on the proposed plan. |
| Pipedrive | When the trial needs to focus on day-to-day management of opportunities, activities and sales responsibilities. | Email sync and automation start with Growth; API access, Insights reports and duplicate merging are also available in Lite, according to the official plan comparison. | Web Forms is part of LeadBooster, a paid add-on for Lite and Growth and included from Premium, as specified in the Pipedrive documentation; I would therefore distinguish the supplier's form from connecting an existing form. |
| Zoho CRM | When I want to compare a process with explicit progression rules and a more involved configuration. | The comparison lists lead and contact modules and places Blueprint, the feature for managing process transitions, from Professional upwards, according to the official edition comparison. | I would ask for a demonstration of email, permissions and reports on the proposed plan, sizing data exchanges against the edition-specific API credits in the Zoho comparison. |
My preference would be the candidate that completes the workflow with fewer exceptions and less manual work. For a CRM serving an internal sales team and external agents, I would particularly want a test with different access levels: manager, internal salesperson and external agent. A demonstration conducted only as an administrator does not answer this question.
How to interpret “CRM with email integration”
In the specification, I would distinguish between sending from the CRM, receiving replies, retrieving past correspondence and managing a shared inbox. I would ask for a separate test for each need, including linking a conversation to the correct deal when the same company has several opportunities running at once.
I would also keep individual sales correspondence separate from campaigns. When planning a B2B newsletter for lead nurturing, meaning maintaining contact with interested prospects over time, I would define a separate audience and explicit inclusion criteria. I would not automatically turn every email address in the CRM into a subscriber.
How do you set up a B2B pipeline with clear stages and responsibilities?
I would set up a short pipeline with stages that describe observable facts rather than the salesperson's impressions. Every open opportunity should have an owner, a next step and a date: without these, I would not consider it under control.
A new enquiry can stay in a qualification queue for initial assessment. I would open a deal when a relevant need and a concrete sales path emerge, rather than treating every enquiry as a potential sale.
| Suggested stage | Entry condition | Responsibility and next step |
|---|---|---|
| Qualified opportunity | The need and contact are identified, and the enquiry is relevant. | The salesperson agrees on the discussion needed to define the solution. |
| Need defined | Requirements, constraints and the decision-making process are sufficiently clear. | The owner gathers the missing information needed to prepare the proposal. |
| Proposal presented | The proposal has been delivered and a next step agreed. | The salesperson records the value, proposal version and review meeting. |
| Negotiation | The prospect is discussing specific terms or changes. | The owner updates obstacles, pending decisions and the expected close date. |
| Won or lost | There is an identifiable outcome under the company's rules. | The reason for the outcome is recorded and any operational handover begins. |
I would not use “interested” as a stage: it does not say what has happened. I would also avoid treating an opportunity as lost simply because the contact is not replying, without a shared rule on contact attempts and putting deals on hold.
For each stage, I would make only the information needed for the next decision mandatory. Asking for data the salesperson cannot yet know encourages invented entries rather than improving control.
How do you connect website forms and email without duplicating contacts?
I would connect the website to the CRM through a workflow that searches for existing records before creating new ones. Deduplication, meaning the identification of duplicate records, needs to be designed separately for people, companies and enquiries.
I would give each form submission a unique identifier. This distinguishes a new enquiry from another attempt to transmit the same enquiry after an error: recognising the person is not enough to prevent duplicate deals.
- Collect what is needed. In the form, I would ask for contact details, company and reason for the enquiry; I would also retain the source page and relevant information about stated preferences.
- Standardise the data. I would remove accidental spaces from email addresses and make phone number formats consistent, without automatically correcting ambiguous information.
- Find the person. I would use a known identifier or email address as the first criterion; a shared phone number would not be enough to merge different people.
- Identify the company. I would prioritise a reliable company identifier; I would use the name and domain as clues to check in uncertain cases, not as universal proof.
- Record the enquiry. I would update the existing record or create a new one, keeping a new need separate from a simple contact detail update.
- Assign and check. I would apply the sales assignment rule and send exceptions to a visible queue, with someone responsible for resolving them.
Hypothetical B2B scenario: from form submission to follow-up
Imagine a distributor with 6 salespeople and 90 monthly website enquiries: these are example figures, not real results. A purchasing manager requests a quote for a company already in the system.
The workflow first looks for their email address and company identifier. If it recognises the company but not the person, it creates a contact linked to the correct company record, then assigns the enquiry to the salesperson responsible for that account portfolio. If there is no reliable match, the enquiry goes for review without automatic merging.
For this scenario, I would set an internal target of a first response within 4 working hours. The salesperson clarifies the need, opens a deal if relevant and agrees on a follow-up: an activity in the CRM, not a reminder left in a chat. An identical second submission caused by a technical retry must not create another opportunity.
Migrating historical data without losing relationships
I would prepare separate lists of companies, people and deals, each with a stable identifier. In the import data, I would retain the references needed to rebuild links; I would first test a sample containing companies with the same name, multiple contacts and concurrent opportunities.
Before the full migration, I would compare records created, updated, rejected and linked. I would keep a copy of the original data and agree on a rollback procedure. I would not leave the quality of historical data to indiscriminate automatic merging.
When a connection requires transformations or steps across several systems, I would assess a dedicated integration layer. In an approach to business automation with n8n, I would start with responsibilities, error logging and controlled retries before adding more automation.
How do you integrate WhatsApp with a CRM and manage consent and access?
I would assess WhatsApp as a channel within the sales process, rather than a parallel address book. Before choosing the connection, I would clarify who owns the number, who can read conversations and how handovers work.
Vendor connections, plans and external services
- HubSpot: connecting WhatsApp to the conversations inbox requires Marketing Hub or Service Hub in the Professional or Enterprise editions, according to the official HubSpot documentation.
- Pipedrive: the dedicated page presents a WhatsApp Business integration but marks automation features as coming soon; I would therefore not count them as already available based on the presentation alone, as the note on the official Pipedrive page makes clear.
- Zoho CRM: the edition comparison specifies that sending WhatsApp messages requires credits, according to the official Zoho comparison.
I would ask the quote to specify whether it uses the vendor's connection, a partner app or an external service. I would also ask who provides support when a message fails to send: having several points of contact without anyone responsible for the connection is not an operational solution.
On the WhatsApp platform, you can reply without templates within the 24-hour window that opens and resets with each user message; outside that window, approved templates are required, according to the WhatsApp Business Messaging Policy. A template is a structured message submitted for platform approval.
The same policy requires recipients to have provided their number or username and permission for subsequent contact, and requires businesses to honour requests to stop, as set out by WhatsApp. For channel details, see how the WhatsApp Business API works: here, I would mainly check that the CRM connection lets you apply these rules.
Quote requests, service updates and promotions are not the same thing
I would not treat consent as the only possible basis for every operation in the CRM: the GDPR distinguishes consent from other lawful bases and also refers to pre-contractual steps requested by the individual, as explained in Recital 40 of the General Data Protection Regulation.
For commercial electronic communications, the Italian data protection authority refers to consent and limits the so-called soft spam exemption to email addresses collected in the context of a sale, for similar goods or services and with an option to object: it is not an exception to extend to WhatsApp, according to the authority's decision.
In the project, I would therefore separate replies to enquiries, updates necessary to provide the service and promotions. For each workflow, I would have the company's privacy adviser validate the purpose and lawful basis, without classifying a message as “service” simply because a salesperson sends it.
I would keep separate fields in the system for purpose, channel, source of the preference, date, wording shown and objections received. A generic “privacy: yes” field does not describe what you can do with that contact and makes it difficult to explain why a message was sent.
Permissions, suppliers and data location
Before signing, I would ask for the DPA, or data processing agreement, and a map of the parties involved: CRM, WhatsApp connection, email and automation. I would also collect the list of sub-processors, meaning parties appointed by the supplier to carry out part of the processing.
I would not equate “storage in Europe” with “no access from other countries”: in its FAQs, Zoho describes possible support access from India to data stored in the European Union and the associated contractual safeguards, as explained in the Zoho privacy documentation.
For each candidate, I would therefore ask about the storage region, support access, any transfers outside the EEA — the European Economic Area — and data return and deletion terms. I would submit these documents for privacy review alongside the actual system architecture: choosing the CRM alone does not cover every supplier involved.
Which KPIs should you measure from first contact to sale?
I would measure a small number of KPIs, or key performance indicators, linked to concrete decisions. Before creating charts, I would define what counts as an enquiry, a qualified opportunity and a sale: without consistent denominators, comparisons do not help decision-making.
| Metric | How I would define it | Decision it should support |
|---|---|---|
| Time to first response | Time between a valid enquiry and the first human response, using a stated working calendar. | Understand whether assignment and sales coverage are adequate. |
| Enquiries without an owner | Valid enquiries with no assigned person responsible for handling them. | Identify assignment problems or unallocated accounts. |
| Enquiry-to-opportunity conversion | Qualified opportunities generated by a group of enquiries, divided by those enquiries. | Assess the relevance of acquisition activity and the quality of qualification. |
| Win rate | Won opportunities divided by won plus lost opportunities, within the stated scope. | Compare segments and processes without including deals that are still open. |
| Sales cycle length | Time from opening to outcome, separating won and lost opportunities. | Identify slow stages and unrealistic forecasts. |
| Opportunities without a next step | Open deals with no assigned future activity. | Resume work before the history becomes an inactive archive. |
I would not divide sales closed during a month by enquiries received that same month when the sales cycle spans different periods. To understand conversion, I would follow groups of enquiries received in the same period, keeping the number of opportunities still open visible.
Hypothetical e-commerce scenario: separating orders from deals
Imagine a furniture e-commerce business with 250 monthly orders and 20 enquiries for office furnishing projects: these are illustrative assumptions. I would not turn every order into a B2B deal; I would put enquiries requiring qualification, a proposal and negotiation into the pipeline.
Suppose that, once the process is complete, those enquiries generate 8 qualified opportunities, of which 3 are won and 5 lost. In this example, enquiry-to-opportunity conversion is 8 divided by 20, or 40%; the win rate is 3 divided by 8, or 37.5%. These are calculations for the scenario, not industry benchmarks.
The operational reasoning comes before the percentage: I would link the enquiry to the existing person, distinguish the company they are buying for and retain the opportunity's source. This would let me review the shop's direct sales separately from sales work on furnishing projects.
How much does a CRM cost, including licences, migration and integrations?
I would compare the total cost over 12 months, separating software purchase, implementation and ongoing management. I would not use an entry-level price as the project budget: the quote needs to describe a configuration that can complete the required workflow.
For each offer, I would ask about currency, taxes, monthly or annual payment, commitment period, minimum number of user licences, any mandatory onboarding costs and renewal terms. The equivalent monthly price and the actual billing frequency are not the same information.
For WhatsApp, I would separate the connection from usage: Meta describes pricing for delivered messages based on category and recipient market on the Business Platform Pricing page. For the budget, I would ask which usage charges are excluded from the proposed subscription.
| Item | What it should include | How to compare it |
|---|---|---|
| Licences | Required user access, plans and components. | The same number of people and the same requirements for every candidate. |
| Configuration | Fields, pipeline, roles, rules and initial reports. | A list of configurations to be delivered and planned tests. |
| Migration | Cleaning, associations, import and validation of historical data. | Included and excluded data, with a rollback procedure. |
| Integrations | Website, email, WhatsApp and any other systems. | Documented workflows, responsibilities and error handling. |
| Adoption | Role-based training and operating instructions. | Users' ability to complete their work without continuous assistance. |
| Ongoing management | Monitoring, maintenance, support and usage. | Included activities, exclusions and support arrangements. |
As a budgeting exercise, assume 6 users and a notional licence fee of €35 per user per month: this is not the price of any of the products compared. The annual subscription would be €2,520; adding hypothetical amounts of €1,800 for configuration and training, €1,200 for migration, €2,400 for integrations and €150 per month for ongoing management would bring the total to €9,720 before taxes and any excluded usage charges. This is a calculation model, not a quote or a market average.
When is a standard configuration enough?
I would stay with the standard setup when assignment, pipeline, permissions and connections complete the process using features included in the chosen plan. In that case, I would customise only what is necessary and invest in data quality and adoption.
I would consider a bespoke project when cross-functional assignment rules, complex company relationships, connections to the ERP or business management system, or synchronisations that recover from errors without manual intervention are needed. Bespoke does not mean rewriting the CRM: it means building only the missing steps.
How to apply it in your business: first steps
I would start with one complete pilot workflow, rather than importing the entire address book. I would consider the first release successful when the team can receive, handle and close an enquiry with reliable data.
- Map the current process. Follow an enquiry from the website to its outcome and note tools, people and manual steps. Done when every step has an identifiable owner.
- Define the model and pipeline. Separate companies, contacts and deals, then write the conditions for each stage. Done when different salespeople classify the test examples in the same way.
- Prepare a shared specification. List essential requirements, access levels, connections and data to migrate. Done when every candidate can quote for the same scope.
- Test a representative sample. Include duplicates, multiple contacts, an external agent, an absent manager and an enquiry with incomplete data. Done when outcomes are correct and exceptions are visible even with non-administrator access.
- Test failures, objections and exports. Simulate a repeated transmission, a broken connection and a block on promotions; also deactivate a test user. Done when no duplicates are created, preferences are respected, activities are reassigned and exported data retains associations that can be rebuilt.
- Launch the pilot and assign ongoing management. Identify who checks unassigned enquiries, data quality and anomalies. Done when operating instructions exist and someone is responsible for applying them.
Mistakes to avoid
I would first look for errors that make the system unreliable in everyday work. A basic configuration you can control is preferable to many features without clear responsibilities.
- Choosing the most convincing screen. A guided demo does not replace testing your business process with imperfect data and non-administrator users.
- Buying the lowest-tier plan without the complete workflow. The comparison loses meaning if necessary email features, forms, permissions or connections are only costed later.
- Importing historical data without identity criteria. Merging companies and people based on similarity can destroy correct relationships; ignoring duplicates transfers the disorder to the new system.
- Opening a deal for every interaction. A contact detail update, a direct order and a new sales opportunity should not be treated in the same way.
- Automating without an owner for exceptions. An error that is logged but never read still leaves the enquiry without a response.
- Measuring only logged activities. A full calendar does not demonstrate sales progress: I would check outcomes, timings and opportunities without a next step.
Frequently asked questions (FAQ)
Can I start with a free CRM?
I would assess a free solution only after defining the work it needs to support. The test must include assignment, access, history and exports: if necessary steps are missing, savings on the licence do not solve the organisational problem.
Do I need to move all my old emails into the CRM?
I would not start with the assumption that every message needs transferring. I would define which conversations are needed for active customers and deals, who can read them and how to preserve their context; then I would test the result on a sample before extending the migration.
How do I stop salespeople from continuing to use their own spreadsheets?
I would design the CRM around the tasks they need to perform, reducing fields that do not support a decision. I would also ask management to use the system for sales meetings, rather than asking users for a second, separate report.
Should the CRM also replace the ERP or business management system?
I would keep sales work and administrative management separate unless there is a concrete need to combine them. I would first document which system controls master data, quotes, orders and customer status, to avoid building competing updates to the same information.
What happens if a salesperson leaves the company?
I would plan an offboarding procedure covering access deactivation, opportunity reassignment and a review of future activities. This should be tested before launch, including connected inboxes and conversations needed for sales continuity.
Can I change CRM later without starting from scratch?
I would prepare for this possibility during the initial selection, keeping stable identifiers and field descriptions. I would ask for a test of exporting data and rebuilding associations: obtaining a list of contacts is not the same as recovering a usable sales process.
Sources
- Create workflows – HubSpot
- What features do the Pipedrive plans have? – Pipedrive
- Compare all features of Zoho CRM editions – Zoho
- Connect a WhatsApp channel to the conversations inbox – HubSpot
- CRM for WhatsApp – Pipedrive
- WhatsApp Business Messaging Policy – WhatsApp (2026)
- General Data Protection Regulation – Parlamento europeo e Consiglio dell'Unione europea (2016)
- Decision of 3 September 2026 – Garante per la protezione dei dati personali (2026)
- Frequently Asked Questions on Privacy – Zoho (2025)
- Business Platform Pricing – WhatsApp
If you want to understand which CRM can support your sales process and how to connect it to your website, email and WhatsApp, request a free assessment: I would start with the path of an enquiry, the steps that currently break down and the requirements to include in the quote.



