CRM
Samdock
EU-Made Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Samdock GmbH · www.samdock.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.
Samdock at a glance
- Vendor
- Samdock GmbH
- Headquarters
- Not stated on the vendor’s pages as of 13 Oct 2026
- Data hosting
- Default not stated; pages mention Germany source, captured 13 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 13 Oct 2026
- Panel verdict
- The AI panel rates Samdock 1.5/5, the mean of 6 judges. Samdock is a German CRM for SMEs built around sales pipeline and contact management, with one native partner, Lexware Office: contacts import in one click with duplicate detection, quotes are created in Lexware from deal data, payment status is visible, and Zapier covers the rest. how scores are made
- As of
- Vendor pages captured 13 Oct 2026; evaluated by the panel 15 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Samdock is a German CRM for SMEs built around sales pipeline and contact management, with one native partner, Lexware Office: contacts import in one click with duplicate detection, quotes are created in Lexware from deal data, payment status is visible, and Zapier covers the rest. Contact management stands out, scores clustering at 4 behind automatic customer history, dynamic lists and lead and deal management. Weakest of the product criteria are data portability, 1 to 2, and sales pipeline, 2 to 3: inbound is documented only from Lexware, we found no public information on export of any kind, and the listed Analytics & Reporting shows no detail. Automation scores cluster at 3: stage-triggered quote creation and document filing, with no public information on branching, delays or sequences. Integrations and sovereignty spread widest, 2 to 4: the Lexware link and stated hosting on German servers sit against no public information on a documented API, a data processing agreement or a subprocessor list, and the captured pages give different figures for the legal entity's name. No prices appear on the captured pages.
Speaks for it
- Contact management scores cluster at 4, backed by automatic customer history, dynamic customer lists and lead and deal management.
- One-click contact import from Lexware Office that checks existing records for duplicates.
- Stage-reached automations that create quotes in Lexware Office with deal information and file quotes and invoices to the correct contact.
- Hosting on German servers stated on the vendor's own pages, in German and English.
- Zapier connection to over 5,000 tools alongside the native Lexware Office integration.
Held against it
- Data portability scores sit between 1 and 2, with no public information on export of contacts, deals, notes or activity history.
- Sales pipeline scores run 2 to 3, with no public information on required fields per stage, win/loss capture or forecasting behind the listed Analytics & Reporting.
- No public information on a documented API, webhooks, or two-way email and calendar sync.
- No public information on a data processing agreement, subprocessor list, or retention and deletion controls.
- The captured pages give different figures for the legal entity's name.
Best for
- You run a small German-speaking business on Lexware Office and want quotes, invoices and payment status tied to your deals.
- You want a drag-and-drop pipeline with stage-triggered automations and an automatic customer history, and can start without IT resources.
- Your contacts arrive mainly from Lexware Office and you want duplicates caught on import.
- You value a help center available 24/7 in German and English.
Avoid if
- You need forecasting, stage probabilities or reports a finance department can sign — the pages show a stage board with a listed Analytics & Reporting feature and no detail behind it.
- You need a documented exit — the only inbound path shown is the one-click Lexware Office contact import, and we found no public information on export or migration tooling.
- You depend on multi-step workflows with branching, delays or routing — the automations shown are single trigger-and-action steps off pipeline stages.
- Your DPO must hold a data processing agreement and subprocessor list before rollout — what the pages show is the hosting statement and a German legal notice.
The scores
| Criterion | Panel median |
|---|---|
| Contact & data model | 2 of 5 |
| Pipeline & forecasting | 1 of 5 |
| Automation & workflows | 1.5 of 5 |
| Integrations & API | 1.5 of 5 |
| European sovereignty | 2 of 5 |
| Import, export & exit | 1 of 5 |
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
Leads, deals, dynamic customer lists and an automatic customer history give me the standard spine a one-person shop needs, and the Lexware import checks for duplicates as contacts come in. But I found no public information on custom fields, required fields or merge tooling, so anything past the standard model is a guess. 1 3 4
The Data Protection Officer
Lead and deal management, dynamic customer lists and an automatically maintained customer history are confirmed, and the Lexware contact import checks existing records for duplicates — though that duplicate checking is evidenced only for the Lexware path. We found no public information on custom fields, field types and validation, merge tooling, or permissioned field access, which keeps this in the basic tier with history on the record as its one real hygiene point. 1 3 4
The Sales Ops Lead
Lead, deal and contact management with an automatic customer history and duplicate checking when contacts arrive from Lexware Office is the honest core, but we found no public information on custom field types, validation, required fields, or merge and dedupe tooling across the whole database — exactly the hygiene a 40-seat team needs to keep records clean. 1 3 4
The RevOps Integrator
Records carry an automatic customer history, dynamic customer lists, and quotes and invoices that file themselves to the right contact when a status changes — plus duplicate detection on the Lexware import. We found no public information on custom fields, field validation, merge tooling, or permissioned field access, so the model looks like clean standard records rather than a system that bends to a business. 1 3 4
The Migrator
Leads and deals exist with automatic customer history landing on the record, and the Lexware import checks existing contacts for duplicates — that last one I genuinely appreciate. But I found no public information on custom fields, field types, merge tooling or any model beyond the standard objects, and duplicate detection is evidenced only at that single import door. 1 3 4
The Skeptic
Automatic customer history, dynamic lists and lead-and-deal management are on the feature list, and contacts coming in from Lexware Office are checked against existing ones — that is the only hygiene we see. We found no public information on custom field types, merge tooling, required fields or permissioned field access, so I cannot push this past the middle of the road. 1 3 4
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
Pipelines with stages exist, reaching a stage can fire an action, and analytics and reporting show up as a homepage bullet with nothing behind it. I found no public information on required fields per stage, win/loss capture, forecasting or a custom report builder, so what I see is a board, not an enforced process. 1 4
The Data Protection Officer
A staged pipeline is confirmed — deals move by drag and drop, automations fire when a stage is reached, and quotes are generated from deal data — and analytics and reporting appear as a listed feature with no detail behind them. We found no public information on multiple pipelines, stage probabilities, required fields per stage, win/loss capture, forecasting or quota tracking, so this reads as a simple sales board with named-but-unsubstantiated reporting rather than a process a finance department can lean on. 1 3
The Sales Ops Lead
What the pages evidence is a sales pipeline with stages, stage-triggered automations and a feature named "Analytics & Reporting" with no depth shown; we found no public information on multiple pipelines, stage probabilities, required fields per stage, forecast or quota views, or a custom report builder — nothing here a CFO would sign. 1 3 4
The RevOps Integrator
Pipelines have real stages — automations fire when a stage is reached — and an analytics-and-reporting module is named in the feature list, which is more than a bare kanban. We found no public information on stage requirements, win/loss capture, forecasting views, quota tracking, or a custom report builder, so there is nothing here a finance department could sign off on. 1 3
The Migrator
Pipeline stages are real and reaching one can fire an automation, but nothing in the captured pages shows required fields per stage, win/loss capture, probabilities or forecast views. A feature list names "Analytics & Reporting" with no detail behind it — for anything a finance department would sign, I found no public information. 1 3 4
The Skeptic
Stages exist because automations fire on reaching one and deals carry information into quotes, but that is the whole evidence of process. We found no public information on stage probabilities, required fields per stage, win/loss capture, forecasting or any report builder beyond the bare words "Analytics & Reporting" — no finance department signs off on a bullet point. 1 3 4
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 one automation on show is trigger-on-stage: hit a pipeline stage and a quote is created in Lexware Office carrying the deal's information, plus automatic filing of quotes and invoices to the right contact. That's honest if-this-then-that that pays off between customer calls, but I found no public information on branching, delays, email sequences or routing. 3 4
The Data Protection Officer
The confirmed capabilities are stage-reached triggers, quote creation in Lexware from deal data, and automatic filing of quotes and invoices to the correct contact on status change — genuine if-this-then-that on records, listed as "Sales-Workflows". We found no public information on multi-step sequences, branching, delays, lead routing or webhooks as workflow steps, so this sits at the simple-trigger level. 1 3 4
The Sales Ops Lead
Triggers on reaching a pipeline stage that create a quote in Lexware Office, plus automatic filing of quotes and invoices to the right contact on status change, are real record-level automation; we found no public information on multi-step sequences, branching, delays, round-robin routing or per-step logging. 1 3 4
The RevOps Integrator
Automations are trigger-action pairs off pipeline stages, and the standout action is a good one: create a quote in Lexware Office with all the deal's information, one-click or drag and drop. We found no public information on multi-step workflows, branching, delays, email sequences, lead routing, or webhooks as steps, so this is simple if-this-then-that rather than automation infrastructure. 1 3 4
The Migrator
Simple, useful if-this-then-that: a pipeline stage reached creates a quote in Lexware Office or files a document to the right contact, set up without a consultant. I found no public information on multi-step sequences, branching, delays or lead routing, so this sits at the basic tier. 1 3 4
The Skeptic
What is captured is honest if-this-then-that: a stage is reached and a quote or invoice appears in Lexware Office, documents file themselves on the contact when status changes. We found no public information on multi-step sequences, delays, branching, lead routing, webhooks or workflow limits — useful plumbing for one partner, not automation as a platform. 1 3 4
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
Zapier to over five thousand apps plus a native Lexware Office connection — contacts in, quotes out, payment status visible — is a real spine for a one-person German business. We found no public information on two-way email and calendar sync beyond an inbox bullet, on a documented API, or on webhooks, so external systems are not first-class from what's published. 1 3 4
The Data Protection Officer
One native partner carries the weight here: a Lexware Office integration with one-click contact import, quote and invoice handoff and payment-status visibility, plus a Zapier connection to thousands of tools and an inbox for mail and inquiries. We found no public information on a documented API, two-way email and calendar sync, webhooks or OAuth apps, so external systems are reached through one native partner and a connector service rather than a first-class interface. 1 2 3 4
The Sales Ops Lead
One deep native connection to Lexware Office for contacts, quotes and invoice status, plus a Zapier bridge to thousands of tools, is a workable SME baseline, and an inbox for mails and inquiries exists; we found no public information on a documented API, webhooks, OAuth apps, or two-way email and calendar sync for the major providers. 1 2 4
The RevOps Integrator
The one deep native connection goes straight to the money — quotes pushed to Lexware Office, payment status flowing back, contacts imported with duplicate checking — which is exactly the kind of revenue-stack link I want to see. But the whole directory is that single accounting partner plus a Zapier bridge to 5,000-plus tools; we found no public information on a documented public API, webhooks, OAuth apps, or two-way email and calendar sync for the major providers. 1 3 4
The Migrator
Connectivity as shown is Zapier plus one deep native partner — Lexware Office, with guided setup and quote creation flowing back into the deal — plus an inbox for mail and inquiries. I found no public information on a documented API, webhooks, or two-way email and calendar sync, and an API I cannot read about is an API I cannot plan an exit around. 1 3 4
The Skeptic
One deep native partner — Lexware Office, with contact import, quote creation, invoicing and payment status — plus Zapier standing in for "over 5,000 tools" is the entire captured directory. We found no public information on a documented API, webhooks, OAuth apps or calendar sync, and Zapier-as-API is what a vendor builds when it would rather not document one. 1 2 3 4
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
Hosted on German servers is stated plainly, and hosting there by default rather than as an option is worth something for my customers' data. But I found no public information on a data processing agreement, a subprocessor list, or the legal entity's jurisdiction, so a cautious DPO has nothing to sign. 3 4
The Data Protection Officer
German hosting is stated plainly in both language versions ("Gehostet auf deutschen Servern" / "Hosted on German servers") and a German legal notice is published, though the captured pages give different figures for the legal entity name (Samdock.ONE GmbH in the legal notice). That is a real starting point for EU processing, but we found no public information on a data processing agreement, a subprocessor list, residency commitments at signup, consent fields, or retention and deletion controls — for a database of other people's personal data, that paperwork silence is what this score reflects. 2 3 4
The Sales Ops Lead
Hosting on German servers is stated as the default and the legal notice names a German company (Samdock.ONE GmbH), which is more than most vendors show; but we found no public information on a data processing agreement, a subprocessor list, consent handling, or retention and deletion controls, so a DPO cannot verify where processing actually ends up. 2 3 4
The RevOps Integrator
The captured pages state hosting on German servers and present a German CRM company, which is better than an EU region on request. We found no public information on a published DPA, a subprocessor list, or retention and deletion controls, and the captured pages give different company names for the vendor entity, so the sovereignty story rests on hosting location alone. 2 3 4
The Migrator
"Hosted on German servers" is stated plainly on two pages and the legal notice carries a German limited-liability company name, which is more than many can say. But I found no public information on a data processing agreement, a subprocessor list, data residency terms or retention and deletion controls — a DPO cannot sign this off from what's captured. 2 3 4
The Skeptic
"Hosted on German servers" is stated on the vendor's own pages and the legal notice shows a German company form — and there the paper trail stops. We found no public information on a data-processing agreement, a subprocessor list, retention or deletion controls, or confirmed residency beyond the hosting claim; "German servers" is a marketing sentence until the DPA backs it. 2 3 4
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 from Lexware is one-click with duplicate detection, which is the easy half of the story. I found no public information on export of any kind, on general CSV import, or on API access to pull my history back out — we found no public information on exit at all. 3 4
The Data Protection Officer
Getting in is partially evidenced: one-click Lexware contact import with duplicate detection on existing records. We found no public information on export of any kind — contacts, deals, notes, activity history or files — nor on a public API, migration tooling or contractual data-return terms, so from the public pages I can see a way in and we found no public information on a way out. 3 4
The Sales Ops Lead
Inbound is self-serve for one named source — a one-click Lexware Office contact import with duplicate detection — but we found no public information on general CSV import with mapping, any export of deals, notes, files and activity history, migration from other CRMs, or contractual data-return terms; the exit path is an unknown. 1 3 4
The RevOps Integrator
Getting in is addressed from exactly one source: one-click Lexware Office contact import with duplicate detection. We found no public information on export of any kind — objects, activity history, attachments — nor on general CSV import with mapping or migration paths from other CRMs, which is the classic shape of a closed ecosystem where exit is undescribed. 3 4
The Migrator
The one entrance in evidence is a one-click contact import from Lexware Office that recognizes duplicates already in the system — good hygiene, but limited to a single source and to contacts. For the way out — export of deals, notes, activity history and files, API extraction, or contractual data-return terms — I found no public information at all, and an undocumented exit is a risk I score, not a benefit of the doubt. 3 4
The Skeptic
The way in is documented and narrow: one-click contact import from Lexware Office with duplicate detection, a single partner's path. We found no public information on general CSV import with mapping, any export of notes, activities or files, migration tooling or contractual data-return terms — an exit that is not documented in anything captured is not a feature. 3 4
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.
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
I could not find a single number — no tiers, no per-seat price, no billing period, no trial terms — on the captured pages, so the invoice I would pay with my own card is not computable from what is public here. From where I sit, that sits at the bottom of the scale. 1
The Data Protection Officer
No price appears anywhere in the captured pages — not per seat, not per tier, not at renewal — and the homepage presents features without figures while the integration and legal-notice pages carry none either. We found no public information on tiers, billing periods, VAT treatment, seat minimums or add-ons, so a buyer cannot compute any invoice from public information alone. 1 2 3 4
The Sales Ops Lead
The captured pages show no prices at all — no tiers, per-seat rates, billing periods, VAT treatment or renewal terms — so no buyer can compute a real invoice from public information alone; every commercial detail is a sales conversation. 1 3 4
The RevOps Integrator
We found no public information on pricing in the captured pages — nothing on tiers, per-seat prices, billing period, VAT treatment, or renewal rules. A buyer cannot compute any invoice, at any seat count, from what has been captured. 1
The Migrator
The captured pages carry no prices of any kind — no tiers, no per-seat figures, no billing period, no renewal or VAT terms. I found no public information on pricing; a buyer cannot compute even a rough invoice from what is published here. 1 2
The Skeptic
No price, tier, billing period, seat minimum or renewal term appears in any captured page — homepage, legal notice or integration pages. A buyer cannot compute the invoice for even one seat from public information, and a CRM with no visible price list is one that prices the deal after it has met you. 1 2 3 4
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 ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Questions about Samdock
Is Samdock European?
Yes. whats-best.ai classifies Samdock as EU-Made.
Where does Samdock store data?
The default storage location for customer data is not stated on the vendor’s pages as of 13 Oct 2026. The vendor’s pages mention Germany as hosting location, per the vendor’s page captured 13 Oct 2026.
Does Samdock have a free plan?
Not stated on the vendor’s pages as of 13 Oct 2026.
What are the best alternatives to Samdock?
As of 21 Oct 2026, the panel rates Pipedrive (3/5), Bitrix24 (3/5) and HubSpot Sales Hub (3/5) highest among the other 49 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 Pipedrive (EU origin, foreign-owned). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Samdock alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 13 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data residency, Legal entity. Not confirmed on the vendor’s own pages as captured.
- 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.
- 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
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are 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
Sources (4)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.samdock.com Checked 13 Oct 2026 Details →
- 2 Legal notice www.samdock.com Checked 13 Oct 2026 Details →
- 3 Integrations & API — found from sitemap www.samdock.com Checked 13 Oct 2026 Details →
- 4 Integrations & API — found from sitemap www.samdock.com Checked 13 Oct 2026 Details →