CRM
Nutshell
Rest of world Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 3 of 4 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Nutshell (WebFX) · www.nutshell.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.
No written verdict for this product
The panel scored Nutshell, but the summary our synthesizer wrote did not survive our own contradiction check — twice. Rather than print a paragraph we cannot stand behind, we print none. Every score, rationale and source below is unaffected; read them and draw the conclusion yourself.
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
Unlimited contacts and custom fields are confirmed, but unlimited custom fields only show up at the $79 tier, and the evidence is completely silent on dedupe, merge, validation or anything beyond contacts-and-companies — so duplicates accumulate unchecked as far as this evidence goes. 1 2
The Data Protection Officer
Unlimited contacts and companies with custom fields and interaction tracking exist, rising to unlimited custom fields at the top tier, but the evidence is silent on dedupe, merge, validation and permissioned field access. Silence on hygiene is information: this is the 'duplicates accumulate unchecked' world with slightly better than cosmetic customization. 1 2
The Sales Ops Lead
Custom fields and unlimited contacts/companies are confirmed, with unlimited custom fields at the top tier, but the evidence is silent on required fields, validation, dedupe and merge tooling — the hygiene enforcement my 40 seats live by is unevidenced. That's a step above 'cosmetic customization' only because the field model scales. 1 2
The RevOps Integrator
Unlimited contacts and companies with custom fields and interaction tracking exist, and custom fields run to unlimited at the top tier — but the evidence shows zero dedupe, merge, validation, or anything beyond the standard objects. That lands between 'customization is cosmetic' and 'custom fields with basic dedupe', with the hygiene half missing entirely. 1 2
The Migrator
Unlimited contacts and companies with custom fields, activity tracking, and auto-logged call transcripts is a decent core, but the evidence is completely silent on dedupe and merge — the two things I'd check first before trusting an import. No evidence of field validation, field-level permissions, or anything beyond the standard object trio, so this sits below the 5 anchor. 1 2
The Skeptic
"Unlimited contacts and companies with custom fields" is the entire data-model story — nothing on dedupe, merge tooling, field validation or permissioned access, so duplicate decay is your problem. Custom fields go unlimited only at the top tier, which tells you the model is a tier lever, not a deep one. 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
Drag-and-drop pipelines exist with tier-gated pipeline counts (5 on Pro, 10 on Business, unlimited held at the top), and reporting is canned 'quick insights' — no stage requirements, no probabilities, no win/loss capture, no forecasting of any kind evidenced. This is a kanban with tiered walls, not a process. 1 2
The Data Protection Officer
Drag-and-drop pipelines scale from 5 custom pipelines to unlimited by tier and 'reporting' is claimed, but there is no evidence of stage requirements, win/loss capture, forecasting, quota tracking or a custom report builder. Nothing here produces numbers a finance department would sign off on. 1 2
The Sales Ops Lead
Multiple custom pipelines are real (5 on Pro, 10 on Business, unlimited at Enterprise) and the board is drag-and-drop, but there is zero evidence of stage gates, required fields per stage, win/loss capture, quota tracking or any forecast view — the reporting line reads 'quick insights,' which is dashboard-screenshot territory no CFO signs. rubric level 3 exactly: pipelines exist, nothing is enforced, canned reports only. 1 2
The RevOps Integrator
Multiple pipelines are real but capped by tier (5 on Pro, 10 on Business, unlimited at the top), with drag-and-drop boards and canned 'quick insights' reporting. No stage requirements, no win/loss capture, no forecast view, no quota tracking anywhere in the evidence — a sales department could run it, a finance department could not report off it. 1 2
The Migrator
Multiple pipelines confirmed, tiered 5/10/unlimited by plan, with drag-and-drop and a vague 'quick insights' reporting claim — but nothing on stage requirements, win/loss capture, forecast views, or a custom report builder. That's the 3 anchor: pipelines exist, enforcement and finance-grade rollups don't show up anywhere. 1 2
The Skeptic
Drag-and-drop pipelines that are metered by tier — 5 on Pro, 10 on Business, unlimited only at Enterprise — is my kind of tell: the core object is an upsell. No evidence of stage gates, required fields, win/loss capture or anything a finance team would call a forecast; "quick insights" and marketing attribution is all the reporting on record. 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
The only real automation evidence is email marketing ('segment audiences, automate, and track engagement') plus form/chatbot lead capture — no record-level workflow builder, no branching, no routing anywhere in the evidence. 1 2
The Data Protection Officer
The only automation evidenced is marketing-flavored — email campaigns with segmentation and automation, lead capture via chatbot, forms and landing pages. No workflow builder, branching, delays, routing or webhooks appear anywhere in the evidence; email flows are barely more than templates. 1 2
The Sales Ops Lead
Email marketing automation with segmentation, AI call transcription/summarization, and chatbot lead capture are confirmed, but no workflow builder, multi-step sequences, branching, routing or webhooks appear anywhere in the evidence. This is marketing-side if-this-then-that, not pipeline infrastructure. 1 2
The RevOps Integrator
The only automation evidenced is email marketing (segment, automate, track) and auto-tracking of contacts captured by landing pages and chatbots — no workflow builder, no triggers on records, no sequences, and webhooks appear nowhere in the evidence. That is above bare email templates but well below if-this-then-that plumbing. 1 2
The Migrator
The only automation in evidence lives inside email marketing — 'segment audiences, automate, and track engagement' — plus AI assist helpers. No record-level triggers, no multi-step sequences on deals, no lead routing, no webhooks; even the anchor-3 if-this-then-that on records is unproven, so I can't go above the midpoint of nowhere. 1 2
The Skeptic
The only automation evidenced is inside the email marketing module ("segment, automate, track") — no workflow builder, branching, sequences or routing anywhere in the evidence. Worse, the AI that would remove manual work runs on a metered bucket: 10 "outcomes"/month on Foundation, 20 on Growth, with "clear upgrade options when limits are reached" — the feature is its own upsell. 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
Two-way Gmail and Outlook sync for email and calendar is genuinely there, and SQL data access exists but only as enterprise bait on the $79 tier; no documented REST API, no webhooks, no native directory evidenced. Better than BCC logging, well short of a first-class API. 1 2
The Data Protection Officer
Two-way Gmail and Outlook sync is the anchor-5 credential, but the rest is thin: no documented REST API, no webhooks, no native integration directory in evidence. SQL data access is the one deep channel and it is gated to the $79 top tier. 1 2
The Sales Ops Lead
Two-way email and calendar sync with Gmail and Outlook is confirmed — the first half of rubric level 5 — but the evidence evidences no documented REST API, no webhooks and no native integration directory. The only raw data path is SQL access, and that is gated to the $79 top tier. 1 2
The RevOps Integrator
Two-way email and calendar sync with Gmail and Outlook is the real thing and I credit it — but there is no documented REST API, no webhooks, no OAuth, and no native integration directory anywhere in the record. SQL data access on the top tier is a tier-gated data path, not an ecosystem; this is one solid sync holding up a stack that isn't evidenced. 1 2
The Migrator
Two-way sync with Gmail and Outlook is confirmed, which earns real credit, and SQL data access exists as a raw channel — but only on the $79 top tier. No documented REST API, no webhooks, no native integration directory anywhere in the evidence; the ecosystem half of this criterion is simply absent from the evidence. 1 2
The Skeptic
Two-way Gmail/Outlook sync is real and I'll credit it, but it's also the ceiling: no documented REST API, webhooks, marketplace or native directory on record. The one API-shaped thing is SQL data access, reserved for the $79 top tier — data access as a tier perk, not a first-class surface. 1 2
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
Ann Arbor company owned outright by WebFX, and the evidence carries zero sovereignty attributes — no DPA, no EU region, no subprocessor list, nothing. My European contacts' data would be sitting under US law by default with no documented mitigation. 1
The Data Protection Officer
A US entity in Ann Arbor owned by WebFX, with no sovereignty attributes on record — no EU hosting, no DPA, no subprocessor list, exactly the anchor-0 profile. Worse, the 'Prospect finder' add-on surfaces strangers' contact info inside the CRM, the enrichment posture I reject outright. 1
The Sales Ops Lead
US company (Ann Arbor) owned by WebFX, and the evidence records no sovereignty attributes at all — no DPA, no EU hosting option, no subprocessor list. rubric level 0 fits verbatim: US entity, US-default hosting, no public DPA or subprocessor list. 1
The RevOps Integrator
A US vendor in Ann Arbor owned by WebFX, with no sovereignty attributes on record: no EU hosting option, no DPA, no subprocessor list. This is the anchor zero case — European buyers' personal data sits under US entity reach with nothing published to mitigate it. 1
The Migrator
Ann Arbor company proudly owned by WebFX, zero sovereignty attributes on record: no DPA, no subprocessor list, no EU hosting option. That is the 0 anchor verbatim — US entity, US-default hosting, nothing published — and I'd want that in writing before any EU personal data touched this system. 1
The Skeptic
US company in Ann Arbor, "proudly brought to you by" WebFX, and the evidence records no sovereignty attributes whatsoever — no DPA, no subprocessor list, no EU hosting option. That is rubric level 0 read back verbatim. 1
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
Getting in is decent — free data migration during the trial and free onboarding — but the evidence says absolutely nothing about export, which means exit capability is unevidenced and I'd be taking it on faith. In is a service, out is a question mark. 1 2
The Data Protection Officer
Getting in is a vendor-assisted 'free data migration during your trial' rather than documented self-serve import, and export is entirely unevidenced — no CSV export, no API-based exit path beyond SQL access locked to the top tier. For a system holding other people's personal data, an unevidenced exit is a compliance liability, not just lock-in. 1 2
The Sales Ops Lead
Free data migration during the trial gets you in with help, and top-tier SQL access is a genuine exit valve for raw data. But nothing evidences self-serve export of deals, activities, notes or files on lower tiers — the silence on export is itself the information. 1 2
The RevOps Integrator
Getting in is free human-assisted migration, but only during the trial; getting out is evidenced solely as SQL data access on the top tier. No self-serve CSV import with mapping, no full-object export, no sign that notes, activities or files leave with you — closer to 'import is a support ticket' than to genuine portability. 1 2
The Migrator
Getting in is vendor-assisted ('free data migration during your trial') — generous but time-boxed and not self-serve dedupe tooling — while the only data-out channel in evidence is SQL access locked to the top tier. No export of notes, activities, or files is documented, no API export, no data-return terms; I've escaped systems that disclosed more than this, and it still hurt. 1 2
The Skeptic
Getting in is handled — free human-assisted migration, but only during the 14-day trial, which is a conversion window, not a data policy. The evidence documents no self-serve export at all; the only general-purpose egress on record is SQL access locked behind the $79/seat tier, which prices your own exit. 1 2
Pricing transparency
panel disagrees
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
Every tier is publicly priced per user per month from $13 to $79, no seat minimums or maximums, no card required for the trial, and a stated 15% annual split — my 3-seat invoice is a two-minute exercise. Docked because several add-ons are 'starting at' meters (SMS $15, email $5, prospect finder $37) with no published scales, and AI outcomes live in opaque usage buckets with 'clear upgrade options' when you hit the cap. 1 2
The Data Protection Officer
Per-seat prices for every tier, the annual split (15% off), no seat minimums, and itemized add-ons are all public, which is close to rubric level 8. Docked because the homepage and pricing-page captures disagree on tiers ($42 and $79 appear only on the homepage), VAT treatment is unstated, and the AI-outcome meter's overage is an 'upgrade option' rather than a number. 1 2
The Sales Ops Lead
Per-seat prices for every tier ($13–$79/user/month), the annual split (15% off), no seat minimums or maximums, and every add-on carries a number — the invoice for 40 seats is nearly computable. It stops short of 8 because AI outcomes are a metered monthly bucket, three add-ons are 'starting at' prices, and VAT treatment is stated nowhere. 1 2
The RevOps Integrator
Every tier carries a public per-user monthly price ($13/$25/$42/$59/$79), the annual split is computable at 15% off, seat minimums are explicitly none, and limits are stated (pipelines per tier, AI outcome buckets). Docked from higher because three add-ons are 'starting at' prices, VAT treatment is unstated, and there's no calculator — but a buyer can get close to the real invoice in minutes. 1 2
The Migrator
All five tiers priced per user per month, no seat minimums, 15% annual split, free cardless trial, and six add-ons with real numbers — I can almost compute the invoice. Docked because three add-ons are 'starting at' prices, VAT treatment is never stated, and AI outcomes are a metered bucket whose overage rates aren't published, so the real bill at renewal still has fog in it. 1 2
The Skeptic
Credit where due: four tiers publicly priced per-seat, 15% annual split, no seat minimums — the base invoice computes. But the real one doesn't: six add-ons stack on top, three priced "starting at" and one per-user ($16/user engagement), AI outcomes metered in monthly buckets, VAT treatment unstated, and the homepage's "quotes, invoices and contracts in your CRM" quietly becomes a $79/month add-on on the pricing page — the two captures don't even agree on the tier ladder. 1 2
European sovereignty — proven facts
3 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 | Incorporated in US ⚠ unverified | 0/3 pts | 5 Report an error |
|---|---|---|---|
| Ownership | Not determined ⚠ unverified | — | uncited Report an error |
| Data residency | US by default ⚠ unverified | 0/3 pts | 3 Report an error |
| Subprocessors | US CLOUD Act reach ⚠ unverified | 0/2 pts | 3 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.
- Weak sourcing — Ownership. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Legal entity. The page states headquarters rather than a register of incorporation; the Terms name only "Nutshell, Inc." and the footer an Ann Arbor, MI address, so the US code is derived from the headquarters statement.
- Weak sourcing — Data residency. No EU hosting option is offered anywhere in the excerpts; EU customers are covered only by EU Standard Contractual Clauses in the Data Processing Addendum, not by an EU region.
- Weak sourcing — Subprocessors. AWS is a US-headquartered provider regardless of server region; the full subprocessor list (email/SMS delivery, payment processors, AI model providers such as OpenAI and Anthropic) is referenced but not among the excerpts.
- 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 could not confirm any compliance information on the vendor’s own pages as captured, so this page shows none rather than a statement we cannot stand behind. Know more? Tell us
- 26 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
- 16 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
- 8 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
- 5 subprocessors 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 data 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 integrations 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 support 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 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. 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
- The panel’s written verdict is withheld: our own re-read found claims in it that the evidence does not carry, and a second synthesis did not fix them. The scores and the material below are unaffected. Know more? Tell us
Sources (15)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.nutshell.com Checked 15 Sep 2026 Details →
- 2 Vendor pricing page www.nutshell.com Checked 15 Sep 2026 +1 earlier capture: 11 Sep 2026 Details →
- 3 Security / trust page support.nutshell.com Checked 30 Sep 2026 Details →
- 4 Terms of service www.nutshell.com Checked 30 Sep 2026 Details →
- 5 Legal notice — found from the homepage www.nutshell.com Checked 30 Sep 2026 Details →
- 6 Contact & data model — found from sitemap support.nutshell.com Checked 1 Oct 2026 Details →
- 7 Contact & data model — found from sitemap support.nutshell.com Checked 1 Oct 2026 Details →
- 8 Pipeline & forecasting — found from sitemap support.nutshell.com Checked 1 Oct 2026 Details →
- 9 Pipeline & forecasting — found from sitemap support.nutshell.com Checked 1 Oct 2026 Details →
- 10 Automation & workflows — found from sitemap support.nutshell.com Checked 1 Oct 2026 Details →
- 11 Automation & workflows — found from sitemap support.nutshell.com Checked 1 Oct 2026 Details →
- 12 Integrations & API — found from sitemap www.nutshell.com Checked 1 Oct 2026 Details →
- 13 Integrations & API — found from sitemap support.nutshell.com Checked 1 Oct 2026 Details →
- 14 Import, export & exit — found from sitemap support.nutshell.com Checked 1 Oct 2026 Details →
- 15 Import, export & exit — found from sitemap support.nutshell.com Checked 1 Oct 2026 Details →