CRM
Freshsales
Rest of world Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Freshworks Inc. · www.freshworks.com
Report an error on this page Is this your product? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Freshsales is an AI-powered sales CRM from Freshworks Inc. (San Mateo HQ, NASDAQ: FRSH). The bench scores it strongest on pricing transparency (6 across the table) and contact management, weakest on sovereignty, data portability and integrations, with automation pinned at 4. The pricing strength is concrete: Growth, Pro and Enterprise carry public per-user prices (€9/€39/€59, billed annually), add-ons are priced, and a 21-day trial with no credit card required is stated — though only annual rates are shown and the skeptic flagged a $9-versus-€9 starting-price mismatch between captures. Judges credit a real data model (custom fields from Growth; custom modules and field-level permissions at Enterprise) but find the evidence silent on dedupe and merge. The recurring weakness is isolation and exit: the evidence evidences no API or external integrations beyond built-in chat, email and phone channels, and lists no sovereignty attributes on record. flagged splits found none above threshold; the widest spreads (contact management 4-6, sales pipeline 2-4) turn on whether a kanban without enforced stages counts as process.
Speaks for it
- Public per-user prices on all three tiers (€9/€39/€59 billed annually) with add-ons priced too, putting pricing transparency at 6 across the table
- 21-day trial with no credit card required, stated on the vendor's own page
- Real data-model depth — custom fields from Growth, custom modules, field-level permissions and audit logs at Enterprise (contact & data model 4-6)
- Automation holds at 4 across the table on basic workflows at Growth and sales sequences from Pro
- Chat, email and phone channels bundled on the Growth plan, with a Freshsales Suite combining sales and marketing
Held against it
- Sovereignty scores fall at 0-1 with the evidence listing no DPA, subprocessor list or EU hosting option anywhere in the evidence
- Data portability scores 0-1 with no import, export, CSV, migration tooling or API appearing anywhere on the evidence
- Integrations scores 1-2: no API, webhooks, two-way email or calendar sync, or native integration evidenced — only built-in channels
- Sales pipeline scores 2-4 with forecasting insights Enterprise-only and no stage requirements, win/loss capture or quota tracking evidenced
- Only annual-billed rates are shown and the Freddy AI Agent meters €45 per 100 sessions, leaving the real invoice non-computable in advance
Best for
- You're a startup or SMB that wants a publicly priced entry point — Growth at €9 per user/month billed annually — and can evaluate it on the 21-day trial with no credit card required.
- Your team lives inside one tool and wants chat, email and phone channels, basic workflows and sales sequences bundled rather than stitched from external apps.
- You want custom fields at the entry tier now, with custom modules and field-level permissions available later at Enterprise.
Avoid if
- You need a documented exit path — CSV export, API access or migration tooling — before signing; the evidence records none.
- Your revenue stack depends on API or two-way email/calendar sync; integrations scored 1-2.
The scores
Contact & data model
Show reasoningHide reasoning
How this is scored
Depth and hygiene of the core records — contacts, companies, deals, custom fields, deduplication.
0 — A flat address book; no relations between people, companies and deals.
3 — The standard three objects exist but customization is cosmetic: few field types, no required fields, duplicates accumulate unchecked.
5 — Custom fields across objects, basic dedupe on create, activity history on the record; complex models still need workarounds.
8 — Rich field types with validation, merge and dedupe tooling, relationships beyond the standard model, permissioned field access.
10 — A genuinely modelable system: custom objects or equivalent, bulk hygiene tooling, field-level history — the data model bends to the business, not the reverse.
The Solo Seller
Custom fields and lifecycle stages arrive at the €9 Growth tier and contact scoring at Pro, so records aren't flat — but there's no evidence of dedupe, merge, or validation anywhere, and custom modules plus field-level permissions are Enterprise-hostage features. 2 1
The Data Protection Officer
Custom fields from Growth and custom modules plus field-level permissions at Enterprise show a real data model, but the evidence is entirely silent on deduplication, merging and activity history — the hygiene that keeps a database of other people's data from rotting — so I cannot go above mid. 1 2
The Sales Ops Lead
Custom fields from Growth and custom modules plus field-level permissions and audit logs at Enterprise show a real data model, but the evidence evidences zero dedupe or merge tooling and no required-field validation — the hygiene layer a 40-seat team lives on is undocumented. 1 2
The RevOps Integrator
Custom fields and lifecycle stages start on Growth, territory management and custom activities on Pro, and custom modules plus field-level permissions finally appear at Enterprise — real depth, but the top-tier gating plus zero evidence of dedupe, merge or field-level history caps it mid-scale. 2 1
The Migrator
Custom fields appear from Growth up, and Enterprise adds custom modules plus field-level permissions, with lifecycle stages and contact scoring also on record. But there is not one word about dedupe, merge or hygiene tooling anywhere — and hygiene is exactly where my migrations bled — so this stays below the 8 anchor. 1 2
Pipeline & forecasting
Show reasoningHide reasoning
How this is scored
Whether the pipeline enforces a process and produces reporting a finance department accepts.
0 — A kanban of deals with amounts; nothing is enforced, nothing rolls up.
3 — Multiple pipelines and stage probabilities exist, but no required fields per stage and only canned reports.
5 — Stage requirements, win/loss capture and standard forecast views; custom reporting is limited or an add-on.
8 — Enforceable process (required fields, stage gates, routing), custom report builder, forecast by team and period with quota tracking.
10 — Forecasting a CFO signs: weighted and commit-based views, historical snapshots, attainment tracking, and reporting composable enough to answer questions the vendor never anticipated.
The Solo Seller
Kanban with drag-and-drop plus lifecycle stages and Freddy deal recommendations is the whole story; forecasting insights sit behind Enterprise and there's zero evidence of stage requirements, win/loss capture, or any report builder. Nothing is enforced. 1 2
The Data Protection Officer
Kanban with drag-and-drop and Freddy AI deal recommendations is board-and-bells, not enforced process; forecasting appears only as gated 'forecasting insights' at Enterprise, with no evidence of required stage fields, win/loss capture or a custom report builder. 1 2
The Sales Ops Lead
Kanban with drag-and-drop, contact lifecycle stages and Freddy's deal recommendations exist, but forecasting is only an 'insight' locked behind the Enterprise tier; nothing on required fields per stage, stage gates, quota tracking, or forecast snapshots I could hand a CFO. 1 2
The RevOps Integrator
A drag-and-drop kanban with lifecycle stages and "forecasting insights" reserved for the Enterprise tier is the entire pipeline story: no stage gates, no required fields per stage, no report builder, no quota or win/loss capture anywhere on the evidence. 1 2
The Migrator
Kanban with drag-and-drop and contact lifecycle stages exist, but forecasting only shows up as an Enterprise 'insight', and the evidence evidences no required fields per stage, no win/loss discipline, no custom report builder, no quota tracking. A pipeline that doesn't enforce a process is a board with amounts. 1 2
The Skeptic
Kanban views and contact lifecycle stages are confirmed, but forecasting is an Enterprise-only 'insight' feature and nothing evidences required fields per stage, win/loss capture or quota tracking. A kanban of drag-and-drop cards with a top-tier forecast carrot is anchor-3 territory, not a process a finance department signs. 1 2
Automation & workflows
Show reasoningHide reasoning
How this is scored
Triggers, sequences and routing that remove manual work without a consultant.
0 — No automation beyond email templates.
3 — Simple if-this-then-that on records; no multi-step sequences, no branching.
5 — Multi-step workflows with delays and branching, email sequences, basic lead routing — capped by tier or count.
8 — Full workflow builder across objects with webhooks as steps, round-robin routing, sequence analytics.
10 — Automation as infrastructure: versioned workflows, error handling, per-step logs, and limits generous enough that the feature is not its own upsell.
The Solo Seller
"Basic workflows" on Growth and sales sequences plus Freddy lead routing on Pro are real but explicitly tier-capped; no evidence of branching, delays, webhooks, or limits that aren't themselves an upsell. 2 1
The Data Protection Officer
The vendor's own ceiling language is 'basic workflows' on Growth and 'sales sequences' on Pro; task automation and AI lead routing are claimed but nothing evidences branching, delays or webhooks, so I sit between the simple-rules and capped-tiers anchors. 1 2
The Sales Ops Lead
'Basic workflows' at Growth plus sales sequences and AI-assisted lead routing at Pro land this between anchors — real sequences and routing, but no evidence of branching, delays, webhooks, or round-robin, and the sequences sit a tier up. 1 2
The RevOps Integrator
"Basic workflows" on Growth, sales sequences on Pro, and generic task automation put this in the middle band, but nothing on branching, delays, webhooks as steps, or even workflow-count limits — a consultant would still be guessing at what the builder can do. 2 1
The Migrator
The vendor's own words are 'Basic workflows' on Growth, with sales sequences gated to Pro plus generic task automation — no branching, no webhooks as steps, no sequence analytics, no routing rules evidenced. Tier-capped and thin; I've seen this become a consultant project. 1 2
Integrations & API
Show reasoningHide reasoning
How this is scored
Two-way email/calendar sync, native connections, and an API that treats external systems as first-class.
0 — No API, no sync; data enters by CSV and leaves never.
3 — One-way email logging (BCC), a handful of Zapier triggers, a read-mostly API.
5 — Two-way email and calendar sync for the major providers, a documented REST API with sane limits, a modest native directory.
8 — Deep native integrations for the revenue stack, webhooks, OAuth apps, API parity with the UI for core objects.
10 — An ecosystem: public API covering everything the UI does, event streams, a marketplace, and sync so reliable the CRM can be the system of record without being the only system.
The Solo Seller
Built-in chat/email/phone channels and a sales+marketing suite are product features, not integrations: the registry contains no API, no two-way calendar sync, and no native directory. Absence of evidence here scores near the floor. 2 1
The Data Protection Officer
The evidence evidences no API, no email/calendar sync, no native directory, no webhooks and no marketplace — only built-in chat/email/phone channels and an internal sales-marketing suite bundle; by the evidence's rule of evidence, external integration capability is essentially absent. 1 2
The Sales Ops Lead
The entire sheet is silent on API, two-way email/calendar sync, and any integration directory; the only connectivity evidenced is Freshworks' own chat/email/phone channels, so external systems are not first-class on this record. 1 2
The RevOps Integrator
The evidence contains no API, no webhooks, no two-way email or calendar sync, no Zapier, no native directory — not even BCC logging. Built-in chat/email/phone channels and a vendor-internal sales-plus-marketing suite are product features, not connections; as evidenced, nothing in a revenue stack can plug into this CRM. 1 2
The Migrator
The evidence evidences no API, no two-way email or calendar sync, no Zapier, no native directory, no webhooks — only bundled chat/email/phone channels and a sales-marketing suite. 1
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where other people's personal data actually lives and under whose law — entity, hosting, subprocessors, DPA.
0 — US entity, US-default hosting, no public DPA or subprocessor list.
3 — A DPA exists and an EU region is available on request or on top tiers; subprocessor exposure to US CLOUD Act reach is broad and undocumented.
5 — EU hosting selectable at signup, published DPA and subprocessor list; core processing still touches US entities.
8 — EU entity or EU-default hosting with published subprocessors, consent-friendly fields, retention and deletion controls; residual US exposure named and narrow.
10 — European entity, EU-only processing including subprocessors, deletion that provably deletes — sovereignty a DPO can sign off without a caveat file.
The Solo Seller
Freshworks Inc. is a US-listed, San Mateo-headquartered entity and the evidence records no sovereignty attributes at all — no public DPA, no subprocessor list, no EU region option. Priced in euros doesn't mean processed in Europe. 1
The Data Protection Officer
Freshworks Inc., San Mateo HQ, NASDAQ-listed — a US entity with no EU hosting, no DPA, no subprocessor list anywhere on record, while Freddy AI scores and writes over contacts' personal data with zero disclosure of where that processing happens. This is the anchor-0 posture exactly, and no EUR price tags change it. 1 2
The Sales Ops Lead
Freshworks Inc. is a NASDAQ-listed, San Mateo-headquartered US entity and the evidence records no DPA, no EU hosting option, and no subprocessor list — there is nothing here a European DPO could sign. 1 2
The RevOps Integrator
Freshworks Inc. is a US-listed, San Mateo-headquartered entity with "no sovereignty attributes on record" — no DPA, no subprocessor list, no EU hosting option anywhere in the evidence. That is the bottom anchor verbatim. 1 2
The Migrator
Freshworks Inc., San Mateo HQ, NASDAQ-listed, and the evidence records zero sovereignty attributes — no EU region, no published DPA, no subprocessor list, nothing. This is the anchor-0 case exactly: US entity, US-default assumptions, CLOUD Act exposure unexamined. 1 2
Import, export & exit
Show reasoningHide reasoning
How this is scored
Getting in with history intact, and out with everything — the anti-lock-in criterion.
0 — Import is a support ticket; export is contacts-only CSV missing notes, activities and files.
3 — Self-serve CSV import with mapping; export covers main objects but drops activity history, attachments or relations.
5 — Guided migration from major competitors, full-object CSV export, API access sufficient to rebuild the database elsewhere with effort.
8 — Complete export (all objects, history, files) self-serve in open formats, import with dedupe and dry-run, no API metering that prices exit out of reach.
10 — Exit as a feature: documented full-fidelity export, migration tooling both directions, and contractual data-return terms — leaving is a weekend, which is exactly why you can stay.
The Solo Seller
Nothing in the registry mentions import, export, migration, or API extraction in any direction, so I can't even sketch how I'd get my contacts out. Total silence on an anti-lock-in criterion scores at the bottom. 1
The Data Protection Officer
No import, export, migration tooling or API appears anywhere in the evidence — the exit story is simply never told; a 21-day card-free trial is easy entry, not exit, and silence on extraction of contacts' data scores at the floor. 1 2
The Sales Ops Lead
Nothing in the evidence touches import, export, or migration — no CSV tooling, no API export, no exit terms — so on this record there is no documented way in with history or out with anything. 1 2
The RevOps Integrator
Not one fact about import, export, CSV, migration or API pull — the only data-motion affordance on the evidence is a support email address, which is exactly the import-as-support-ticket scenario anchor zero describes. Exit terms are unevidenced and therefore uncredited. 1 2
The Migrator
Total silence: no import, no export, no migration tooling, no API on record — not even a claim of contacts-only CSV. A vendor that published nothing about exit has, for my purposes, no exit; I must assume leaving this system is a support-ticket project with my notes and activity history as hostages. 1 2
Pricing transparency
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.
0 — No public prices at all; every tier is a sales conversation.
3 — An entry price exists, but the tiers most buyers need are unpriced, or per-seat maths is obscured by bundles, minimums or mandatory onboarding fees.
5 — Most tiers carry real numbers with billing period and VAT treatment stated, but at least one commonly needed capability hides in an unpriced tier or usage-metered add-on.
8 — Every tier priced publicly including annual/monthly split; limits, seat minimums and overage rules stated; only genuine enterprise contracts are custom.
10 — Complete price computability: every tier, add-on, usage meter 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
Three tiers publicly priced per seat (€9/€39/€59) with even add-ons priced, a 21-day no-card trial, and no seat minimums in evidence — more honest than most. But only annual-billed rates are shown, VAT treatment is unstated, and Freddy AI meters €45/100 sessions, so the real monthly invoice still needs homework. 2 1
The Data Protection Officer
All three tiers priced at €9/€39/€59 per user billed annually with the branded-documents add-on and the Freddy AI session meter also priced is genuinely better than most. But no monthly-billing figures, VAT treatment, seat minimums or renewal terms are stated, so the real invoice — especially at renewal — is not computable from these pages alone. 1 2
The Sales Ops Lead
All three tiers and even the usage-metered add-ons carry public per-seat prices (€9/€39/€59 annual, €45 per 100 AI sessions), which beats most vendors; but only annual billing is shown, VAT treatment, seat minimums and tier limits are unstated, so the real monthly invoice still needs a conversation. 1 2
The RevOps Integrator
All three tiers and both add-ons carry public per-user EUR prices with the annual billing period stated, plus a 21-day no-card trial — genuinely computable at entry. But only annual pricing is shown (no monthly split, no VAT treatment) and limits like workflow or sequence counts are undisclosed, so the real invoice at Pro and above still has holes. 2 1
The Migrator
Credit where due: all three tiers carry real numbers (€9/€39/€59 per user billed annually) and even add-ons are priced, with a 21-day no-card trial. But only annual rates are shown, VAT treatment is unstated, and Freddy AI Agent is a usage meter (€45/100 sessions) that makes the real invoice uncomputable in advance. 1 2
The Skeptic
Credit where due: all three tiers carry numbers (€9/€39/€59 per user, billed annually) and even the add-ons are priced — Branded documents €19/user and Freddy AI Agent at €45 per 100 sessions. But monthly-billing rates, VAT treatment, seat minimums and plan limits are absent, and session-credit AI pricing makes the real invoice non-computable — plus the $9 vs €9 starting-price mismatch between captures. 1 2
European sovereignty — proven facts
0 of 4 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 |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 11 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 compliance on the pages we read (freshworks.com/crm, freshworks.com/crm/pricing, support.freshworks.com/support/solutions/articles/50000001081-export-data, support.freshworks.com/support/solutions/articles/50000011460-why-did-i-receive-a-warning-or-failure-message-about-data-export-size-and-how-can-i-fix-it-). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 10 pricing 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
- 4 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
- 2 hosting 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 legal 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 (4)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor product page www.freshworks.com Checked 16 Sep 2026 Details →
- 2 Vendor pricing page www.freshworks.com Checked 16 Sep 2026 +1 earlier capture: 11 Sep 2026 Details →
- 3 Import, export & exit — found from sitemap support.freshworks.com Checked 1 Oct 2026 Details →
- 4 Import, export & exit — found from sitemap support.freshworks.com Checked 1 Oct 2026 Details →