NetHunt CRM
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by NetHunt · www.nethunt.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
NetHunt CRM at a glance
- Vendor
- NetHunt
- Headquarters
- Not stated on the vendor’s pages as of 1 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 1 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 1 Nov 2026
- Panel verdict
- The AI panel rates NetHunt CRM 2.5/5, the mean of 6 judges. NetHunt CRM is a Gmail-native CRM that scored highest on automation, at 6–7, where judges credited documented run history with per-run status, stated failure reasons, and retry that re-runs only the failed step. how scores are made
- As of
- Vendor pages captured 22 Sep 2026 to 1 Nov 2026; evaluated by the panel 27 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
NetHunt CRM is a Gmail-native CRM that scored highest on automation, at 6–7, where judges credited documented run history with per-run status, stated failure reasons, and retry that re-runs only the failed step. Contact management, integrations and data portability clustered at 5–6, resting on customizable folders with import-time duplicate checking and mismatch review, ten named integrations plus a JSON API over HTTPS, and CSV or Google Sheets export with a Record ID round-trip. Sovereignty was the weakest criterion at 3: the contracting entity is NetHunt Inc. at a Middletown, Delaware address, hosting location is not stated on the captured pages, the one named subprocessor is Mouseflow web analytics, and the privacy policy was last updated April 7, 2020. Sales pipeline scores sat at 5, covering everyday stage management and configurable reports while revenue forecasts appear only as a homepage claim. Splits were minor — the widest gap on any counted criterion was one point. Pricing is reported but not counted: the pages show a free trial and talk-to-sales, and no public prices appear on the captured pages.
Speaks for it
- Automation scored 6–7 on per-run workflow history, stated failure reasons and retry of only the failed step
- CSV import offers field mapping, duplicate checking on email or name, and mismatch review before the import is finalized
- Export covers folders, views and timeline events to CSV or Google Sheets, with Record ID round-trips for bulk updates
- Ten integrations are named — including Gmail, Slack, Zapier and WhatsApp — plus webhooks and a documented JSON API over HTTPS
- Multiple pipelines support stages you can add, rename or delete, with configurable pipeline reports and period comparison
Held against it
- Sovereignty scored 3, with the registered entity NetHunt Inc. at a Middletown, Delaware address and hosting location not stated on the captured pages
- The privacy policy was last updated April 7, 2020, and the only named subprocessor is Mouseflow web analytics, whose location is not stated
- Email exports carry From, To, CC, time and subject but not the content, and photo icons are excluded from general export
- Revenue forecasts appear only as a homepage claim, and we found no public information on quotas, goals, win/loss reasons or stage gates
- We found no public information on API rate limits, third-party OAuth apps, or Microsoft email and calendar sync
Best for
- You sell from Gmail all day — the CRM runs inside the Gmail inbox and unifies Gmail, WhatsApp, Instagram and VoIP conversations
- You want self-service data movement — CSV import with duplicate checking and mismatch review, export to CSV or Google Sheets, and Record ID round-trip updates
- You need automations you can operate yourself — run history with per-run status, stated failure reasons and retry of just the failed step
- You capture leads from web forms and chats into records, with Slack notifications when a deal is won
Avoid if
- You must document a stated data-residency chain — the registered entity is NetHunt Inc. of Middletown, Delaware, USA, and the captured pages state no hosting location
- You need exported email content for archive or migration — export covers From, To, CC, time and subject, not the content
- Your team runs on Microsoft email and calendar — the product requires Gmail account access to operate
The scores
| Criterion | Panel median |
|---|---|
| Contact & data model | 3 of 5 |
| Pipeline & forecasting | 2.5 of 5 |
| Automation & workflows | 3 of 5 |
| Integrations & API | 3 of 5 |
| European sovereignty | 1.5 of 5 |
| Import, export & exit | 3 of 5 |
Contact & data model
Show reasoningHide reasoning
How this is scored
Depth and hygiene of the core records: contacts, companies and deals linked to each other, custom fields, activity history on the record, import hygiene and deduplication.
0 — Not a CRM data model; the product is an address book or mailing list with no companies or deals.
3 — Contacts, companies and deals linked to each other, with a few custom fields and notes on the record.
5 — Custom fields on contacts, companies and deals, an activity timeline (emails, calls, meetings, notes) on each record, and duplicate detection or merging of records.
8 — Custom objects or relationships beyond the standard model, field types with validation and required fields, bulk merge and deduplication tooling, and field-level permissions.
10 — A modelable system of record: custom objects with their own relations, pipelines and permissions, field-level change history, data-quality tooling (enrichment, bulk cleanup, rules) documented, and the model exposed completely through the API.
The Solo Seller
Records sit in folders I can reshape myself — custom fields, renamed stages, custom views — and the import maps columns, creates fields on the fly, flags mismatches before committing, and checks duplicates on email or first/last name. Comments, call logs and emails live on each record's timeline, and contact enrichment is offered. We found no public information on custom objects with their own relations, bulk merging, or field-level permissions, so I capped this in the middle. 1 4 9 11
The Data Protection Officer
Records sit in customizable folders with user-defined fields, a required Name identifier, and a timeline of comments, call logs and linked Gmail threads, while import offers field mapping, duplicate checking on email or name, and pre-import correction of mismatched formats. The enrichment that 'builds comprehensive customer profiles with verified contact details' is offered with no statement of where those details are sourced, which I record as a consent risk rather than a hygiene credit. We found no public information on bulk merging, field-level permissions, or field-level change history, so the documented hygiene reaches everyday working level, not governed-system level. 1 3 4 9 11
The Sales Ops Lead
Records sit in customizable folders where new fields can be created at import time, and each record carries a real timeline — comments, call logs and linked email threads — with duplicate checking on email or name when importing into an existing folder. Field-level permissions and bulk merge tooling are documented nowhere I read, and companies as a distinct linked object never appear, so hygiene is import-time only. 1 2 3 4 9 11
The RevOps Integrator
Records live in customizable folders with custom fields, and each record carries a timeline of comments, call logs and linked emails; duplicate detection on import matches Record ID, email, first name or last name, and enrichment is advertised on the homepage. Required-field enforcement is minimal (Name only), and we found no public information on custom objects with their own relations, bulk merge tooling, or field-level permissions. That puts it a step above the mid-level data model. 1 3 4 11
The Migrator
Records live in customizable folders with custom fields, per-record comments and a timeline of calls and emails, and the import path has real hygiene: duplicate checking against email or name, mismatch review before commit, and comment-level dedupe. Enrichment is offered and stages and views are tweakable. We found no public information on bulk merge after import or field-level permissions, which is where I stop. 1 3 4 11
The Skeptic
Records sit in customizable folders where you can create fields yourself at import, and each record carries a timeline of comments, call logs and email metadata — visible in the export options — with import-time duplicate checking on email, first name, last name or Record ID plus a mismatch review before you commit. Data enrichment is advertised as a feature. We found no public information on record merging outside the import flow, custom objects with their own relations, or field-level permissions, so this reads as solid mid-tier hygiene rather than a modelable system of record. 1 3 4 11
Pipeline & forecasting
Show reasoningHide reasoning
How this is scored
How deals move through a sales process and what the pipeline reports: pipelines and stages, probabilities, forecasts, goals or quotas, win/loss analysis and sales reporting.
0 — No deals or pipeline; the product manages contacts or tickets only.
3 — A visual pipeline of deals with stages and amounts, and a pipeline overview or simple sales report.
5 — Several pipelines with stage probabilities or a weighted value, a revenue forecast view, sales goals or targets, and standard sales reports or dashboards.
8 — An enforceable process (required fields or stage gates per stage), win/loss reasons captured and reported, a custom report builder, and forecasts by team and period with quota or goal attainment.
10 — Forecasting a CFO signs: weighted and commit-based forecast categories, historical snapshots of the pipeline, attainment tracking per rep and team, and a report builder that combines any objects and fields.
The Solo Seller
Multiple pipelines, stages I can add, delete or rename, deals carrying name, potential value and probability of closing, drag-and-drop cards, and a summary of total value per stage — enough to run my deals in an afternoon. Pipeline reports are configurable by stage, manager and deal-value field with period comparison, and revenue forecasts are advertised. We found no public information on goals or quotas, win/loss reasons, or required fields gating a stage, so it stays a working pipeline rather than a forecasting suite. 1 5 6
The Data Protection Officer
Multiple pipelines with addable, deletable and renamable stages, deals carrying name, potential value and probability of closing, drag-and-drop movement, and a summary of total deal value and deal count per stage, backed by configurable pipeline reports with period comparison and a homepage claim of revenue forecasts. We found no public information on sales goals or quota attainment, win/loss reason capture, or enforceable stage gates, so the evidence covers daily pipeline management and reporting but nothing of forecast governance. 1 5 6
The Sales Ops Lead
Multiple pipelines with add, delete and rename on stages, a probability-of-closing field on the deal, and pipeline reports configurable by folder, stage field, won/lost fields, value field and manager with period comparison. That is where it stops for me: no quotas or goals, no required fields per stage, no win/loss reasons captured, and revenue forecasts appear only as a single homepage bullet with nothing behind it — not a forecast a CFO signs. 1 5 6
The RevOps Integrator
Multiple pipelines with drag-and-drop stages, deal probability and potential value are documented, and pipeline reports compare periods, break down won/lost by manager, and accept currency, number or formula fields for deal value. The homepage advertises revenue forecasts, but we found no public information on sales goals or quotas, win/loss reason capture, or stage gates that enforce the process. Capable mid-level pipeline reporting, not yet forecast-grade. 1 5 6
The Migrator
Multiple pipelines with stages you can add, rename or delete, per-deal probability of closing, drag-and-drop stage movement and a pipeline summary of value per stage, with reports configurable by stage, deal-value field and manager and period comparison. Revenue forecasts appear only as a homepage capability line, and we found no public information on sales goals, quotas, stage gates or win/loss reason capture. 1 5 6
The Skeptic
Multiple pipelines with stages you can add, delete or rename, per-deal potential value and "probability of closing", drag-and-drop cards and a summary of total value and per-stage counts are documented, plus pipeline reports configurable by folder, stage, value and manager with period comparison. Revenue forecasts appear as a homepage reporting claim while the help pages document pipeline reporting only. We found no public information on stage gates, win/loss reason capture, quotas or goal attainment. 1 5 6
Automation & workflows
Show reasoningHide reasoning
How this is scored
Triggers, sequences and routing that remove manual work without a consultant: workflow rules, email sequences, task creation and lead assignment.
0 — No automation of any kind; every step is done by hand.
3 — Trigger-based automations on records (a field change or stage change creates a task, sends an email or updates a field), or email templates with scheduled follow-ups.
5 — A visual workflow builder with triggers, conditions and actions, email sequences or cadences with delays, and automatic assignment of leads or deals.
8 — Multi-step workflows across objects with branching and webhooks or custom code as steps, round-robin and rule-based routing, sequence analytics, and automation limits stated per tier.
10 — Automation as infrastructure: versioned workflows with per-run logs and error handling, test or sandbox runs, and limits generous enough that the feature is not its own upsell — all documented.
The Solo Seller
Workflows are triggers plus actions: a field change, a deal changing stage, a new chat, a VoIP call or a webhook event can create records, send emails, assign tasks and notify Slack when a deal is won, with an email marketing module and templates alongside. The run history is what a one-person shop needs — every run logged with status, the failure reason, and retry of just the failed step, individually or in bulk. We found no public information on branching, round-robin routing, sequence analytics or per-tier automation limits. 1 7 8
The Data Protection Officer
Eight trigger types are documented — stage and field changes, new records and contacts, chat conversations, VoIP calls, web form submissions and webhook events — feeding actions such as creating records, sending emails, assigning tasks and updating information, with Slack notification on a won deal. Every workflow keeps a dated run history showing the reason each run failed, and failed steps can be retried individually, in bulk or by step without rerunning the whole automation. We found no public information on branching, round-robin routing, sequence analytics or per-tier automation limits, which is what separates usable automation from automation infrastructure. 1 7 8
The Sales Ops Lead
Trigger-and-action workflows with a wide trigger set — stage change, field change, new chat, VoIP call, web form, webhook — and actions that create records, send emails, assign tasks and update fields. The operational half is what I rate: run history with a status per run, the failure reason on each failed run, and retry that re-runs only the failed step, in bulk or one by one. I found no public information on branching, delay steps, round-robin routing or per-tier automation limits. 1 7 8
The RevOps Integrator
Eight documented triggers — stage and field changes, new records and contacts, new chats, VoIP calls, web form submissions and webhook events — feed actions that create records, send emails, assign tasks and notify Slack. What wins me over operationally is the run-level history: status per run, the stated reason for failure, and retries that re-run only the failed step, individually or in bulk. We found no public information on branching, delays, round-robin routing, or per-tier automation limits. 1 7 8
The Migrator
Workflows are triggers plus actions, with eight documented triggers covering stage and field changes, new chats, VoIP calls and web form submissions, and campaigns that launch off a trigger. The operational side is unusually real: per-run history with status, failure reasons shown, and retry that re-runs only the failed step, individually or in bulk. We found no public information on branching, delays, round-robin routing or automation limits per tier. 1 7 8
The Skeptic
Eight named triggers — field change, deal stage change, new record, new contact, new chat, new VoIP call, web form submission, webhook event — drive actions like creating records, sending emails, assigning tasks, updating information and pinging Slack, and every run lands in a history view with per-run status, failure reasons and retry per step or in bulk. That is real error handling, not a marketing badge. We found no public information on branching, delays or cadences, lead routing rules, or automation limits per tier. 1 7 8
Integrations & API
Show reasoningHide reasoning
How this is scored
Email and calendar sync, native connections, an integration marketplace, and an API that treats external systems as first-class.
0 — No integrations and no API; the product stands alone.
3 — Email logging (BCC or plug-in) or a calendar connection, a handful of named integrations or a Zapier/Make connector.
5 — Two-way email and calendar sync with Google and Microsoft, a documented REST API, and a directory of native integrations.
8 — A marketplace of named native integrations for the revenue stack, webhooks, OAuth apps for third parties, API rate limits stated, and API coverage of all core objects.
10 — An ecosystem: a public API covering everything the UI does, event streams or webhooks for every object, SDKs and a sandbox, and two-way sync with named ERP, support and marketing systems documented.
The Solo Seller
Gmail, Google Workspace, WhatsApp, Instagram, Slack, Intercom, Apollo, Hunter, Facebook, Zapier and webhooks are named natively, and the whole CRM lives inside my Gmail inbox — exactly the low-friction setup I want. The API is documented over HTTPS with create, update, search and delete on records plus comments, call logs and Gmail thread links, and triggers for new or changed records. We found no public information on Microsoft sync, OAuth apps for third parties, stated rate limits or a marketplace. 1 9 10
The Data Protection Officer
The vendor names a set of native integrations — Gmail, Google Workspace, Apollo, Facebook, WhatsApp, Instagram, Slack, Zapier, Hunter and Intercom — plus webhooks and a documented API over HTTPS using GET and POST with JSON, covering folders, records, comments, call logs and Gmail thread linking, with an MCP connection for ChatGPT and Claude. Authentication is an email-and-key pair on an API whose documented paths sit under a Zapier-oriented namespace; we found no public information on rate limits, OAuth for third-party apps, SDKs, or any Microsoft email or calendar connection. The ChatGPT and Claude connection is a personal-data export whose receiving processors are not named, a point I flag under sovereignty. 1 9 10
The Sales Ops Lead
A named native list — Gmail, Google Workspace, Apollo, Facebook, WhatsApp, Instagram, Slack, Hunter, Intercom — plus Zapier and webhooks, and a documented JSON API over HTTPS covering folders, records, comments and call logs with change triggers. The API is Basic-auth with GET and POST only, rate limits are not stated, and no Microsoft connection appears on any page I read. 1 9 10
The RevOps Integrator
The Google connection is genuinely native — the CRM runs inside Gmail and the privacy policy confirms access to email content, attachments and Calendar events — plus ten named integrations including Slack, Intercom and Apollo, a Zapier connector, advertised webhooks, and an MCP bridge to AI tools. The documented API covers folders, records, comments, call logs and Gmail-thread linking over HTTPS with Basic authentication, but the endpoint paths sit under a Zapier-shaped API version one, and we found no public information on rate limits, OAuth apps for third parties, or any Microsoft or Outlook connection. 1 2 9 10
The Migrator
Gmail is home turf with deep Google account access, and the directory names ten integrations including Slack, WhatsApp, Apollo and Zapier, plus webhooks and an MCP option. A documented JSON-over-HTTPS API covers listing folders and creating, searching, updating and deleting records, with endpoints for comments, call logs and Gmail thread links. Authentication is a Basic API key built from your email, and we found no public information on rate limits, an OAuth app model, or sync with Microsoft. 1 9 10
The Skeptic
The product is Gmail-native — it takes access to contacts, email content, attachments and Google Calendar — and lists ten named integrations including Slack, WhatsApp, Instagram, Apollo, Hunter and Intercom, plus Zapier, webhooks and MCP hooks for ChatGPT and Claude, with a documented JSON API over GET and POST that reads and writes records, comments and call logs. The API base path is itself labelled for Zapier, authentication is a Basic API key, and we found no public information on rate limits, OAuth for third-party apps, or any Microsoft email or calendar sync. 1 2 9 10
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where other people's personal data actually lives and under whose law: contracting entity and parent company, hosting location, subprocessors (hosting, email and calendar sync, telephony, enrichment, AI features), and the data processing agreement. Independently sourced by the sovereignty pipeline; describe what is proven, and treat what is not stated as unknown rather than non-EU.
0 — Proven non-EU end to end: non-EU entity and non-EU hosting with no EU option, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist; hosting location and subprocessors are not stated, or hosting is non-EU with an EU option on request or on top tiers.
5 — EU hosting stated (as default or selectable), a data processing agreement and a subprocessor list published; parts of the chain (email sync, enrichment, AI, support) may run through non-EU providers.
8 — EU contracting entity and EU hosting on named infrastructure, subprocessors listed with their locations, retention and deletion controls documented, and security certifications (ISO 27001, SOC 2) stated.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor including AI and sync providers, deletion documented as complete, and certifications published with their scope.
The Solo Seller
The contracting entity is proven to be NetHunt Inc. at a Delaware, USA address, and the privacy policy names Mouseflow as a web-analytics subprocessor that may record visitor clicks. A data processing agreement is published and NetHunt states it serves only as a GDPR data processor. The captured pages state no hosting location and no full subprocessor list, so where my customers' data physically sits remains unknown to me. 1 2 9
The Data Protection Officer
A data processing agreement and a privacy policy are published and the vendor states it serves only as a GDPR data processor, but the registered entity is NetHunt Inc. at a Middletown, Delaware address and the policy was last updated on April 7, 2020. The single named subprocessor is Mouseflow web analytics with no location given, and we found no public information on hosting location, subprocessor locations, security certifications, or deletion guarantees — while the product requires full Gmail access including email content and attachments, and its enrichment and ChatGPT/Claude features run through unnamed providers. This is paper processor language over an American contracting entity with the entire data-residency chain unstated. 1 2 9
The Sales Ops Lead
A data processing agreement and privacy policy exist and NetHunt states it serves only as GDPR data processor, but where customer data is hosted is not stated on the captured pages, and the registered address given is NetHunt Inc., 651 N Broad St, Suite 206, Middletown, DE 19709, USA. One subprocessor is named — Mouseflow for web analytics — with no locations, and no ISO 27001 or SOC 2 certification is stated. 1 2 9
The RevOps Integrator
The contracting entity is stated as NetHunt Inc. of Middletown, Delaware, USA, a GDPR data processor role is declared, and a data processing agreement is published. Hosting location is not stated on the captured pages, and the only named subprocessor is Mouseflow for web analytics — we found no public information on hosting, email sync or telephony providers or their locations. Entity proven non-EU, agreement in place, chain undocumented. 1 2 9
The Migrator
The legal counterparty is NetHunt Inc. at a Delaware address, a data processing agreement is published, and the privacy policy names the GDPR processor role and one web-analytics subprocessor, Mouseflow. We found no public information on hosting location or a full subprocessor list, so I know who I contract with but not where my data sits. Security measures are described qualitatively with no certification named. 1 2 9
The Skeptic
The registered entity is NetHunt Inc. at 651 N Broad St, Middletown, Delaware, a data processing agreement is published, the GDPR data-processor role is stated, and Mouseflow is named in the privacy policy as a web-analytics subprocessor. We found no public information on hosting location, a full subprocessor list, deletion controls, or ISO 27001 and SOC 2 certifications. A privacy policy last updated April 7, 2020 still carrying the 2026 copyright is the tell on how current this legal paper is. 1 2 9
Import, export & exit
Show reasoningHide reasoning
How this is scored
Getting in with history intact, and out with everything: self-service import with field mapping, migration from other CRMs, export of records, activities and files, and API access for the rest. The anti-lock-in criterion.
0 — No import or export in the product; data enters and leaves only through the vendor's support.
3 — Self-service CSV or Excel import with field mapping and a CSV export of contacts and other main lists.
5 — Import with field mapping and duplicate handling, an import or migration path from named CRMs, and export of all main objects (contacts, companies, deals, activities) to CSV or Excel.
8 — A complete self-service export of all objects with activity history, notes and files in open formats, migration tooling or a migration service from named competitors, and an API sufficient to copy the whole database.
10 — Exit as a feature: a documented full-fidelity export (all objects, relations, history and files) on demand, import with dry-run, and data-return and deletion terms written into the contract.
The Solo Seller
Getting in is self-service: CSV import with field mapping, mismatch review before committing, duplicate checking, and a Record ID round-trip so an export to Google Sheets can be edited and re-imported as updates. Getting out covers folders, views and timeline events — comments, call logs and email metadata — to CSV or Google Sheets. Email body content and photo icons are stated as excluded from export, and we found no public information on a migration path from named competitors. 3 4 10 11
The Data Protection Officer
Import is genuinely self-service: CSV with field mapping into a new or existing folder, duplicate checking against email or name, correction of mismatched formats before the import is finalized, and re-import by Record ID to update records. Export covers folders, views and timeline events — comments, call logs, and email From, To, CC, time and subject — to CSV or Google Sheets for use in another service, but the export of emails explicitly excludes their content, and photo icons are left out of a general export with only manual workarounds. We found no public information on a migration path from named CRMs or on data-return and deletion terms written into the contract. 3 4 11
The Sales Ops Lead
Import is genuinely hygienic — field mapping with create-new-field, duplicate checking, mismatch correction before the import lands, and update-by-Record-ID via export-modify-reimport — and export covers folders, records and views to CSV or Google Sheets including timeline comments and call logs. Two documented gaps hold it back: exported emails carry only From, To, CC, time and subject rather than the content, and photo icons are excluded from the general export with manual workarounds offered. 3 4 11
The RevOps Integrator
Import is self-service with field mapping, duplicate handling, mismatch review before finalizing, and a round-trip update path via Record ID between Google Sheets and the CRM; the API adds create, search and update on records. Export covers folders, views and timeline events (comments, call logs and email metadata) to CSV or Google Sheets, but the export documentation states that email exports cover only From, To, CC, time and subject rather than the content, and that photo icons are not included in a general export; we found no public information on a migration path from named competitors. Respectable entry and exit, short of full-fidelity. 3 4 9 11
The Migrator
Getting in is the best part: CSV import with field mapping, duplicate checking on selectable match fields, mismatch review before commit, and a Record ID round-trip so an exported spreadsheet can be re-imported as an update. Getting out is self-service CSV or Google Sheets for folders and records, optionally including comments, call logs and email metadata. The vendor's own warnings are the scar tissue I look for: exported emails carry From, To, CC, time and subject but not content, photo icons are excluded from general export with manual workarounds, and we found no public information on migration tooling from named competitors or data-return and deletion terms in the contract. 3 4 9 11
The Skeptic
CSV import comes with field mapping options, duplicate checking and mismatch review before commit, and export covers folders, views and timeline events — comments, call logs, email metadata — to CSV or Google Sheets, with Record ID round-trips for bulk updates. The export documentation itself warns that email bodies and photo icons are excluded from a general export, with manual workarounds offered instead. We found no public information on migration tooling from named competitor CRMs, and the API's read path works folder by folder. 3 4 9 11
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real invoice — per seat, per month, at renewal — from public pages alone: tier prices, billing periods, seat minimums, add-ons, usage meters and onboarding fees.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price or one priced tier; the other tiers or the per-seat scaling are not public.
5 — Public per-tier prices per seat or per account with the billing period (monthly or annual) stated, and the main inclusions of each tier listed.
8 — Every tier priced publicly with the annual/monthly split, seat minimums, limits and overage rules, add-ons priced, and VAT treatment stated; only genuine enterprise contracts are custom.
10 — Complete price computability: every tier, add-on, usage meter, onboarding fee and renewal rule public, with a calculator or table that makes the invoice at 3 and 30 seats a two-minute exercise.
The Solo Seller
The homepage offers a free trial and 'Talk to sales', but we found no public information on tier prices, per-seat rates, billing periods or seat minimums in the captured pages, so I cannot compute what 1 or 5 seats would cost me per month. The free trial is the only pricing-adjacent fact published here. 1
The Data Protection Officer
The captured public pages show a free trial alongside 'Talk to sales' and 'Request demo' calls to action, and we found no public information on tier prices, billing periods, seat minimums, add-ons or onboarding fees anywhere we read. A buyer cannot compute any invoice from these pages; the buying motion on the evidence is a sales conversation. 1
The Sales Ops Lead
The captured pages show a free trial and talk-to-sales and request-demo calls to action, but no tier price, billing period, seat minimum or add-on price appears anywhere I read, so I cannot compute an invoice at 40 seats from public pages alone. 1
The RevOps Integrator
The homepage offers 'Talk to sales', 'Start free trial' and 'Request demo', and we found no public pricing information on any page we read — no tier prices, billing periods, seat minimums, add-ons or onboarding fees. A buyer cannot compute an invoice from these captures. 1
The Migrator not rated — no public information
We found no public information on tier prices, billing periods, seat minimums, add-ons or renewal rules; the captured homepage shows a free trial and talk-to-sales as the entry points. I cannot compute an invoice from what I read. 1
The Skeptic
Across the homepage, help centre, API pages and legal pages we found no public prices at all — no tiers, no per-seat figures, no billing periods, no add-on prices — only a free trial and a "Talk to sales" call to action. A buyer cannot compute a one-seat invoice from the captured pages, let alone a renewal. 1
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about NetHunt CRM
Is NetHunt CRM European?
Not determined: the vendor’s pages as captured do not say where NetHunt CRM is based.
Where does NetHunt CRM store data?
Not stated on the vendor’s pages as of 1 Nov 2026.
Does NetHunt CRM have a free plan?
Not stated on the vendor’s pages as of 1 Nov 2026.
What are the best alternatives to NetHunt CRM?
As of 20 Nov 2026, the panel rates Pipeliner CRM (3.5/5), Attio (3/5) and HubSpot Sales Hub (3/5) highest among the other 57 CRM products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Attio (UK / wider Europe, United Kingdom). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: NetHunt CRM alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- We found no public information on pricing on the pages we read (nethunt.com, nethunt.com/legal/privacy, help.nethunt.com/en/settings/how-to-import-data-from-spreadsheets, help.nethunt.com/en/getting-started-with-net-hunt-crm/data-import, help.nethunt.com/en/getting-started-with-net-hunt-crm/setting-up-your-first-sales-pipeline, help.nethunt.com/en/views-and-reports/pipeline-reports and 6 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 3 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 data fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.nethunt.com Checked 22 Sep 2026 Details →
- 2 Legal notice — found from the homepage nethunt.com Checked 30 Sep 2026 Details →
- 3 Contact & data model — found from sitemap help.nethunt.com Checked 1 Oct 2026 Details →
- 4 Contact & data model — found from sitemap help.nethunt.com Checked 1 Oct 2026 Details →
- 5 Pipeline & forecasting — found from sitemap help.nethunt.com Checked 1 Oct 2026 Details →
- 6 Pipeline & forecasting — found from sitemap help.nethunt.com Checked 1 Oct 2026 Details →
- 7 Automation & workflows — found from sitemap help.nethunt.com Checked 1 Oct 2026 Details →
- 8 Automation & workflows — found from sitemap help.nethunt.com Checked 1 Oct 2026 Details →
- 9 Integrations & API — found from sitemap nethunt.com Checked 1 Oct 2026 Details →
- 10 Integrations & API — found from sitemap help.nethunt.com Checked 1 Oct 2026 Details →
- 11 Import, export & exit — found from sitemap help.nethunt.com Checked 1 Oct 2026 Details →
- 12 Data processing agreement (dpa) — found from the homepage nethunt.com Checked 1 Nov 2026 Details →