CRM
weclapp CRM
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 4 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by weclapp SE · www.weclapp.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 weclapp CRM, 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
The vendor's own pages confirm a 'CRM' module exists inside an ERP platform and nothing more — no facts on contacts, companies, deals, custom fields or dedupe at all. For my 1-5 seat shop I can't even confirm a deal record exists, and a sheet this silent on the core objects means the anchors' low end applies. 1 2
The Data Protection Officer
The only evidence is a module list naming 'CRM' inside a five-module ERP suite; not one fact speaks to custom fields, relations between contacts/companies/deals, deduplication or merge tooling. For a system whose entire purpose is holding other people's personal data, a sheet this silent about its records reads as shallow by default. 1
The Sales Ops Lead
The registry's only CRM-adjacent fact is the module list — 'CRM, merchandise management or accounting' on one platform — with zero evidence on companies, deals, custom fields, required fields or dedupe. For a product meant to carry a 40-seat forecast, an unevidenced data model scores as an address book. 1
The RevOps Integrator
The evidence only confirms a 'CRM' module exists inside an ERP suite alongside merchandise management, accounting and projects — not one word about contacts, companies, deals, custom fields or dedupe. An unevidenced data model scores as an absent one; the module list alone doesn't even reach the 'standard three objects' anchor. 1
The Migrator
The evidence proves a CRM module exists inside an ERP platform and nothing more — no field types, no dedupe, no evidence that contacts, companies and deals even relate to each other. Anyone importing a database here is flying blind on hygiene and structure. 1
The Skeptic
"CRM" appears as one word on a five-module list and that is the entire record: no contacts/companies/deals model, no custom fields, no dedupe evidence. A named module is not a data model. 1
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
Total silence: no pipelines, stages, probabilities, required fields, forecasts or reports are evidenced on either the homepage or the pricing page. When a vendor selling a 'CRM module' publishes nothing about the pipeline, I assume there's nothing there that would enforce a process. 1 2
The Data Protection Officer
Nothing: no stages, probabilities, required fields, forecasting or reporting appear anywhere in the registry — the word 'CRM' is the entire evidence base. I cannot confirm even the kanban-with-amounts floor, so this sits just above zero on absence alone. 1
The Sales Ops Lead
No fact anywhere in the evidence covers pipelines, stage requirements, win/loss capture, forecast views or quota tracking — the pricing page markets modules, not process discipline. I cannot put an unenforced, unproven pipeline in front of a CFO. 1 2
The RevOps Integrator
No pipelines, stages, required fields, forecasts or reports appear anywhere in the evidence — the CRM module is named and nothing more. I can't credit process enforcement or finance-grade reporting that isn't even gestured at. 1
The Migrator
Not one fact about stages, probabilities, forecasts or win/loss capture — the CRM module is merely named with zero pipeline depth evidenced. Total silence scores at the bottom anchor; finance would laugh at a forecast view I can't even confirm exists. 1
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
Not one fact about triggers, sequences, routing or workflow builders appears anywhere in the evidence. The absence is the finding: automation isn't even a marketing bullet on their own site, so it can't be better than the anchor where automation barely exists. 1 2
The Data Protection Officer
Not a single trigger, sequence, routing rule or workflow is evidenced; the closest facts are the paid Helpdesk and Contract Management add-ons, which are tickets and document storage, not automation. Scoring at the floor because the evidence does not even evidence email templates. 2
The Sales Ops Lead
Triggers, sequences, routing and workflow builders appear nowhere in the module list or the detailed pricing page — if automation existed as a selling point, this much pricing detail would have surfaced it. I can't even confirm email templates. 1 2
The RevOps Integrator
No triggers, sequences, routing or workflow builder in evidence; the closest fact is a Helpdesk add-on whose claim is 'a complete and transparent ticket history,' which is record-keeping, not automation. Silence here means manual work stays manual as far as this sheet proves. 1 2
The Migrator
No evidence of triggers, sequences, or routing anywhere in the evidence; the closest facts are a helpdesk add-on and an API gated to the top two packages, which is plumbing, not automation. A workflow builder the evidence doesn't mention doesn't exist. 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
The only real integrations evidence is e-commerce plumbing — Amazon/eBay/kaufland marketplaces and Shopware/WooCommerce/Shopify stores — plus an API interface, and the API is explicitly held hostage in the Services and Trade tiers, not Starter. No email or calendar sync is mentioned at any price, which for a CRM is the one integration I refuse to live without. 2
The Data Protection Officer
An API interface exists but is gated to the Services and Trade packages, alongside genuine native commerce connectors (Amazon, eBay, kaufland.de, Shopify, Shopware, WooCommerce). What is missing for a CRM is everything I would actually probe: no email or calendar sync, no webhooks, no evidence the API is two-way. 2
The Sales Ops Lead
Genuine native e-commerce connections (Shopware, WooCommerce, Shopify, Amazon, eBay, kaufland.de) plus an API interface — though the API is gated to the Services and Trade tiers, so the €39 Starter buyer gets none. No evidence of two-way email/calendar sync, webhooks or documented API limits, which is the revenue-stack baseline my team needs. 2
The RevOps Integrator
Real native plumbing where money moves — Shopify, WooCommerce, Shopware stores plus Amazon/eBay/kaufland marketplaces — and an API interface does exist. But the API is gated to the two top packages (Services €86, Trade €163/user/month), and the evidence is mute on webhooks, OAuth, and the thing I demand first: two-way email and calendar sync. That's a commerce ERP's integration story, not a revenue stack's. 2
The Migrator
Genuine native connectors for the commerce stack (Shopify, Shopware, WooCommerce, Amazon, eBay, kaufland) and an API interface, but the API ships only with Services and Trade — Starter buyers get none — and there's no evidence of two-way email or calendar sync. Commerce-first, revenue-stack second. 2
The Skeptic
Real connections (Amazon/eBay/kaufland, Shopware/WooCommerce/Shopify) and an API exist, but they serve the ERP's commerce side; email/calendar sync — the CRM lifeline — is unmentioned, and the API ships only with services and trade packages, so Starter buyers get none of it. 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
The entity is German (Friedrich-Ebert-Str. 28, Kitzingen, B2B-only terms), which is genuinely better than a US default. But the sovereignty record is empty: no DPA, no subprocessor list, no hosting location, no deletion controls — the anchors treat undocumented processing exposure as the low end, and German paperwork alone doesn't get past that. 1 2
The Data Protection Officer
A German legal entity and address is the one genuine positive, but the evidence itself says no sovereignty attributes are on record: no DPA, no subprocessor list, no hosting location, no retention or deletion controls — 256-bit encryption and daily backups are security hygiene, not GDPR posture. Worse, the marketplace and store connectors push contact and order data into Amazon, eBay and Shopify — US CLOUD Act exposure that is entirely undocumented. I could not initial a transfer assessment on this evidence. 1 2
The Sales Ops Lead
A German SE with a German legal address keeps it off the floor, but the evidence explicitly records 'no sovereignty attributes on record' — no DPA, no subprocessor list, no hosting location, no deletion controls. A DPO has nothing to sign here. 1 2
The RevOps Integrator
A German Societas Europaea with a Kitzingen address under the 3U Holding group puts the entity squarely under EU law, well past a US-default anchor. But the registry records no DPA, no subprocessor list, no hosting location, no retention or deletion controls — the paperwork a DPO needs to sign off simply isn't in evidence. 1 2
The Migrator
A German SE at a Kitzingen address is genuinely European, but the evidence says no sovereignty attributes on record — no DPA, no subprocessor list, no hosting region, so I cannot verify where the data sleeps or who can reach it. 256-bit encryption is not an answer to a CLOUD Act question. 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
The only data-lifecycle facts are daily backups and a human-assisted onboarding process — backups are not exit, and hand-holding implementation is the opposite of self-serve import. There is zero evidence of export in any form, so I have to assume my data checks in and negotiates its own release. 2
The Data Protection Officer
Exit capability is reduced to a tier-gated API: no import tooling, no migration path, no export function and no contractual data-return terms are evidenced anywhere. For a vendor holding an ERP's worth of personal and financial data, 'the API exists on two tiers' is not an exit strategy. 2
The Sales Ops Lead
The evidence is entirely silent on import, export and migration — not even a CSV export claim — and the only extraction path is the API locked to the two top tiers. Unmeasured lock-in is assumed lock-in, and I score it accordingly. 2
The RevOps Integrator
The only data-lifecycle fact on record is daily backups, which protect the vendor's continuity, not my exit. No import tooling, no export formats, no API documentation for pulling everything out — anti-lock-in has to be proven, and here it isn't even alleged. 2
The Migrator
Daily backups are vendor comfort, not exit, and the only extraction path evidenced is an API that Starter buyers don't even get. No export formats, no import or dedupe tooling, no migration promises — leaving would be an archaeology project through a tier-gated API. 2
The Skeptic
Zero import or export evidence of any kind; the only hinted exit path is an API that Starter-tier customers cannot book, and daily backups live in the vendor's hands, not yours. Lock-in here is undocumented, which is the worst kind. 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
Credit where due: real numbers per user/month, VAT treatment stated as net, priced add-ons, and a 30-day trial that auto-cancels. But the invoice I'd actually face is a trap — the €68 CRM-only license is forbidden unless I first buy ERP Services (€86/user/month) or Trade (€163), the Bronze/Silver/Gold support tiers are unpriced, and the API hides behind the top packages, which lands squarely on the anchor where a needed capability hides in tier bundles. 2
The Data Protection Officer
Most tiers carry real per-user/month figures with net pricing and VAT treatment explicitly stated, and even the add-ons are priced — better than most. But the Bronze/Silver/Gold support tiers are unpriced, the single licenses are vague 'from €68' numbers locked to the two top packages, and no annual/monthly split or seat minimums appear, so the real invoice is still not computable. 2
The Sales Ops Lead
Per-seat net prices are public for all three ERP tiers, single licenses and add-ons, with VAT treatment stated and the single-license package restriction disclosed, plus a no-implementation-cost claim — a buyer can mostly compute the invoice. Docked for 'from €X' single-license pricing with no stated driver, unpriced Bronze/Silver/Gold support tiers, and no annual/monthly split or renewal rules. 1 2
The RevOps Integrator
Real per-user numbers for all three ERP packages, net-of-VAT treatment stated outright, add-ons priced at €55/month, and a no-implementation-costs claim — a decent public price floor. But single licenses are 'from' prices, the Bronze/Silver/Gold support tiers carry no numbers, and there's no annual/monthly split or stated limits, so the real invoice at renewal still isn't fully computable. 1 2
The Migrator
Real per-user/month numbers with VAT treatment stated (net, plus VAT) across all three ERP tiers, single licenses and add-ons, plus a public claim of no implementation or maintenance costs. But Bronze/Silver/Gold support is unpriced, no annual/monthly split appears, and single licenses require buying a full ERP package — the invoice is only computable after a support-tier sales conversation. 2 1
The Skeptic
Real per-user prices with VAT treatment stated and priced add-ons are genuinely better than most, but single licenses are "from" prices gated behind mandatory ERP packages, Bronze/Silver/Gold support tiers are unpriced, and no billing-period split or minimums are published. The invoice is computable only for the simplest case. 2
European sovereignty — proven facts
1 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 DE | 3/3 pts | 3 Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 15 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 — Data residency, Subprocessors. 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.
- 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
- 11 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 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
- 5 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
- 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
- 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 (8)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.weclapp.com Checked 15 Sep 2026 Details →
- 2 Vendor pricing page www.weclapp.com Checked 15 Sep 2026 Details →
- 3 Legal notice www.weclapp.com Checked 21 Sep 2026 Details →
- 4 Security / trust page www.weclapp.com Checked 30 Sep 2026 Details →
- 5 Pipeline & forecasting — found from sitemap www.weclapp.com Checked 1 Oct 2026 Details →
- 6 Pipeline & forecasting — found from sitemap www.weclapp.com Checked 1 Oct 2026 Details →
- 7 Integrations & API — found from sitemap www.weclapp.com Checked 1 Oct 2026 Details →
- 8 Integrations & API — found from sitemap www.weclapp.com Checked 1 Oct 2026 Details →