CRM
eWay-CRM
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 4 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by eWay System s.r.o. · www.eway-crm.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
eWay-CRM, from Prague vendor eWay System s.r.o., is an Outlook-native CRM built for the Microsoft stack. The bench scored it highest on pricing transparency — every base tier and both Sales and Projects add-ons carry public per-user yearly prices — and on contact & data model, a flat 7, where fields scale from 50 on Standard to unlimited with mandatory, unique and field-level permissions on Plus. It is weakest on import, export & exit, a flat 2: import help exists only as professional services at $960 per day and no export appears anywhere in the evidence. Pipeline & forecasting scored 2-4, the widest spread; the low end marks the absence of stage probabilities, win/loss capture and forecast views — reporting means canned Power BI dashboards — while the high end still credits Deals, Goals and auto-calculated Est. Revenue. Sovereignty split 4-5 between the hosting on record — EU partner AUTOCONT a.s., on-premises, region-bound Azure AI — and missing paperwork: no published DPA or subprocessor list, with eWay System LLC of Kansas City in the footer. Weighted totals ran 4.2 to 5.3.
Speaks for it
- Every base tier and both Sales and Projects add-ons carry public per-user yearly prices with stated storage limits.
- Custom fields scale from 50 on Standard to unlimited on Plus with mandatory, unique and field-level permissions, plus a duplicity checker on Standard.
- Native Microsoft-stack coverage across Outlook, Teams, SharePoint, Power BI, Power Automate, Word/Excel add-ins and QuickBooks, plus a developer portal.
- Free Contacts & Companies tier at $0 for unlimited users, with a 14-day Plus trial that then reverts to Free.
- EU cloud partner on record (AUTOCONT a.s., Czech Republic), on-premises installation available, and AI processing bound to the deployment region.
Held against it
- No export path is evidenced, and the only import assistance is professional services at $960 per day.
- Workflows cap at 5 per module on Standard (unlimited only on Plus), with no branching, delays or routing evidenced.
- No DPA or subprocessor list is published, and the registry records "no sovereignty attributes on record".
- Monthly-billing rates and "extendable" storage pricing are never separately stated.
Best for
- You run an Outlook-and-Teams-first shop and want a CRM that lives inside the Microsoft stack.
- You want a publicly priced CRM with a $0 tier for unlimited users before committing to paid seats.
- You need field-level data discipline — mandatory, unique and permissioned fields — and can run the Plus tier.
- You want an on-premises installation or a Czech EU cloud partner (AUTOCONT a.s., Czech Republic) rather than cloud-only hosting.
Avoid if
- You need in-CRM forecasting — stage probabilities, weighted views, win/loss capture — rather than reporting handed to Power BI dashboards.
- You need self-serve import and a documented export or exit path; the evidence offers neither, with the only theoretical exit (the API) gated to Standard tier.
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 with mandatory and unique constraints, a duplicity checker on Standard, and field-level permissions with unlimited fields on Plus — real hygiene without forcing me to configure an object model. Missing is merge tooling (a checker is not a merge) and any custom-object or field-level history evidence. 2
The Data Protection Officer
Custom fields run from 50 on Standard to unlimited on Plus with mandatory, unique and field-level permissions, plus a duplicity checker and relations beyond the standard trio (deals convert to projects with subprojects) — real validation and permissioned access. But no merge tooling, field-level history or custom objects is evidenced, so it sits just under the 8 anchor. 2
The Sales Ops Lead
Plus tier delivers the required-field discipline I need: unlimited custom fields, mandatory fields, unique fields and field-level permissions. Dedupe is only a 'duplicity checker' with no merge tooling, and custom objects and field-level history are entirely unevidenced, so it stops short of rubric level 8. 2
The RevOps Integrator
Plus tier shows real data-model governance: unlimited custom fields with unique and mandatory field types, field-level permissions, custom forms, and a duplicity checker — but it's all gated to the top tier (Standard caps at 50 fields) and merge tooling, custom objects and field-level history are unevidenced. 2
The Migrator
Contacts, companies, deals, projects with subprojects and bookkeeping documents give me the relations I need to migrate intact, and Plus offers unlimited custom/mandatory/unique fields, field-level permissions and a duplicity checker — that is most of the hygiene I demand. But merge tooling appears nowhere in the evidence and the strong validation is Plus-gated, so bulk hygiene is a maybe rather than a promise. 2
The Skeptic
Real hygiene is on the page — duplicity checker, 50 custom fields on Standard, then mandatory, unique and field-level permissions at Plus — but the good half of the model is gated to the top tier and there is zero evidence of merge tooling or field-level history. 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
Deals, Goals (Plus), expiring-deal notifications and Power BI dashboards exist, but the evidence is silent on stage probabilities, win/loss capture and any forecast view. Reporting is outsourced to external Power BI rather than enforced in-product process. 2
The Data Protection Officer
Deals exist with discount lists, expiring-deal notifications, Goals and auto-calculated est. revenue from quotations on top tiers, but the evidence is silent on multiple pipelines, stage probabilities, stage-required fields and forecast views. Reporting appears as canned Power BI dashboards — squarely the anchor-3 profile. 2
The Sales Ops Lead
The whole forecast story is Deals, Goals at Sales Plus and Power BI canned dashboards — no stage probabilities, no stage-gated requirements, no weighted views, no snapshots, no attainment history. Mandatory fields exist only as general customization, not tied to stages, and reporting that stops at a dashboard is something my CFO will not sign. 2
The RevOps Integrator
The evidence evidences Deals with amounts, Goals at the Sales Plus tier, auto-calculated Est. Revenue from quotations, and canned Power BI dashboards — but no multiple pipelines, stage probabilities, win/loss capture or native forecast view appears anywhere. A finance department would get its reporting from Power BI, not from this pipeline. 2
The Migrator
Deals exist with Goals and auto-calculated Est. Revenue from Quotations, and reporting means pre-built Power BI dashboards — canned reports in the anchor's own language. Nothing on stages, required fields per stage, win/loss capture or any forecast view a finance department would recognize. 2
The Skeptic
What's evidenced is Deals, discount lists and expiring-deal notifications, with Goals and Est.-Revenue-from-Quotations held back for Sales Plus; no stage gates, win/loss capture, forecast views or quota tracking appear anywhere, and reporting means canned Power BI dashboards. 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
Workflows with rules and actions in Basic and Advanced flavors, capped at 5 per module on Standard and unlimited only on Plus — the textbook tier cap. No webhooks as steps, no sequence analytics, no versioning or error handling evidenced. 2
The Data Protection Officer
Workflows are genuine ("Basic or Advanced", rules, actions, group-level actions) but capped at 5 per module on Standard with unlimited only on Plus — automation as a tier lever. No evidence of delays, branching, sequences or routing, which the 5 anchor requires. 2
The Sales Ops Lead
Workflows (Basic or Advanced) with rules and actions exist, capped at 5 per module on Standard and unlimited on Plus, plus forced automatic email saving. No evidence of delays, branching, sequences, lead routing or webhooks as steps — it sits above simple if-this-then-that but below the multi-step anchor on what's published. 2
The RevOps Integrator
Workflows are tier-capped rule/action pairs (5 per module at Standard, unlimited only at Plus) with no evidence of branching, delays, sequences or routing; the native builder is if-this-then-that. The Power Automate integration is the real workflow engine here — I'd rather have that escape valve than not, but it's an admission the CRM can't carry automation itself. 2
The Migrator
Workflows exist — 'Basic or Advanced (5 per module)' on Standard, unlimited on Plus — plus workflow group-level actions and triggered SharePoint folder creation, so it is more than single if-this-then-that. No delays, branching, webhooks-as-steps, routing or analytics are evidenced, and the per-module count cap is exactly the upsell pattern I distrust. 2
The Skeptic
'Workflows - Basic or Advanced (5 per module)' is the textbook capped automation of the anchor-5 world — workflow count as a tier lever, unlimited only at Plus — with no evidence of webhooks as steps, lead routing, or per-step logs. 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
Deep in the Microsoft stack — Outlook email/calendar sync, Word/Excel add-ins, Teams, SharePoint, Power Automate, Power BI — plus a developer portal and 3000+ apps. But there is zero evidence of Google/Gmail sync, and the API itself is gated behind the Standard tier. 1 2
The Data Protection Officer
Its Outlook-native core is deep — automatic email saving by domain, calendar and contacts sync, Word/Excel add-ins — with Teams, Power BI, SharePoint, QuickBooks, 3CX and a developer portal with API and code samples. But the API is gated to Standard tier and up, "3000+ apps" reads as a marketplace claim, and webhooks and OAuth apps are unevidenced, so it cannot reach 8. 1 2
The Sales Ops Lead
Real depth on the Microsoft stack: Outlook-native CRM, calendar and contacts sync, Word/Excel add-ins, Teams, Power Automate, SharePoint, 3CX, QuickBooks, plus a developer portal. But there is no Gmail/Google sync evidence, the API is gated to Standard tier, and '3000+ apps' is an unattributed marketplace claim, not a documented native directory. 1 2
The RevOps Integrator
Genuinely deep native coverage of the Microsoft stack — Outlook add-in with automatic and even forced email capture, two-way calendar sync up to unlimited calendars, Teams, Power BI, SharePoint, QuickBooks, 3CX/TAPI, plus a developer portal. But email flow is one-way logging into the CRM, Google Workspace is nowhere in the evidence, webhooks are unevidenced, and the API is a Standard-tier line item rather than a birthright — the '3000+ apps' number smells like a connector platform, not a native directory. 1 2
The Migrator
This is a deep Microsoft-stack play — Outlook, Teams, SharePoint, Power BI, Power Automate, Word/Excel add-ins, QuickBooks — with a Developer Portal carrying API and code samples. But the API sits in the Standard tier, '3000+ apps' is Zapier-count marketing, and there is no Google Workspace, webhook, OAuth-app or marketplace evidence anywhere in the evidence. 1 2
The Skeptic
Genuine Microsoft-stack depth (Teams app, M365 web version, Word/Excel add-ins, tiered Outlook calendar sync) and a developer portal, but sync is Outlook-only with no Google/Gmail story in evidence, the API itself is a Standard-tier feature, and '3000+ apps' is a number with no connector platform named behind it. 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
EU region selectable with a named Czech provider (AUTOCONT), on-premises available, and AI processing bound to the deployment region — but no published DPA or subprocessor list, a US LLC in the legal footer, and AI running on unspecified 'other approved infrastructure'. 1 2
The Data Protection Officer
The legal footer is eWay System LLC of Kansas City, MO, hosting is "US or Europe based on what is closer to your location" with OVH US LLC as the US partner, and there is no published DPA, subprocessor list, retention, deletion or consent-field evidence anywhere in the evidence — the registry itself says "no sovereignty attributes on record". Credit for an EU region on AUTOCONT a.s. in Czechia, region-bound Azure AI processing and a genuine on-premises option lifts it above 3, but rubric level 5's floor (published DPA and subprocessor list) is not met. 1 2
The Sales Ops Lead
Czech vendor with an EU region hosted by AUTOCONT a.s. in Czechia, on-premises available, and Azure AI processing bound to the deployment region. But no DPA, subprocessor list, deletion or retention controls are evidenced anywhere, and a US LLC (eWay System LLC, Kansas City) sits in the footer with the controlling side unverified — a DPO cannot sign this without a caveat file. 1 2
The RevOps Integrator
The hosting posture is better than most: EU region selectable at signup with a Czech cloud partner (AUTOCONT), on-premises install available, and AI processing bound to the deployment region on Azure. But no DPA and no subprocessor list are evidenced anywhere, a Kansas City US LLC sits alongside the Prague parent, and the sovereignty attribute record is empty — a DPO gets good hosting and no paperwork. 1 2
The Migrator
Czech vendor, EU cloud via AUTOCONT a.s. in Czechia, on-premises installation on your own servers, and AI processing bound to the deployment region — real bones. But the footer legal entity is eWay System LLC of Kansas City, no DPA or subprocessor list is evidenced, and the structured sovereignty attributes are empty, so the paperwork a DPO would sign is simply not there. 1 2
The Skeptic
EU hosting on AUTOCONT a.s. (CZ), region-bound Azure AI processing and an on-premises option are real assets, but regions default to whichever is 'closer', OVH US LLC is a peer region, the copyright footer belongs to eWay System LLC of Kansas City, and no DPA, subprocessor list or deletion controls are on record. 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 import assistance on the evidence is $960/day professional services, and there is not one word about export. The Standard-tier API is the sole theoretical exit path, with nothing confirming it carries notes, activities or files. 2
The Data Protection Officer
The only import path on the evidence is professional services at $960 per day, and there is not one fact about export — no CSV tooling, no migration guides, no data-return terms. An API exists from Standard tier, which is the sole reason this is not lower; exit here is a project, not a feature. 2
The Sales Ops Lead
The only import path in evidence is vendor professional services at $960/day — migration as a paid engagement, not self-serve. Export is completely silent: no CSV export, no migration tooling, no documented full-fidelity exit; the tier-gated API is the only theoretical way out. 2
The RevOps Integrator
The evidence evidences no self-serve import and no export path at all — data import is literally sold as professional services at $960/day, and the only hint of an exit is the API itself, which is gated to Standard tier. That's a one-way door dressed as a free trial. 2
The Migrator
The evidence says nothing about export — no CSV export, no full-object dump, no migration tooling, no data-return contract terms — and the only import path evidenced is paid professional services at $960 per day. A Developer Portal API on the Standard tier means exit is possible only by building it yourself, which is exactly the exit-as-a-project profile I reject. 1 2
The Skeptic
The only migration path in evidence is 'our team can assist with data import... $960 per day' — export formats, exit tooling and migration features are entirely absent from the evidence, and the API that might rescue an exit sits behind the Standard paywall. 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
Every base tier and both add-on modules (Sales, Projects) carry public per-seat prices with tax treatment, billing cycles and storage limits stated; no seat minimums, card payment accepted, and the free tier is genuinely free for unlimited users. Only the monthly-billing rate and storage-extension pricing are unpublished. 2
The Data Protection Officer
Every core tier and add-on (Sales, Projects) carries a public per-user yearly price with billing periods, tax exclusion, storage caps, payment methods and plan-switching rules — a 30-seat invoice is a two-minute exercise. Deducted slightly because monthly-billing prices and the "extendable" storage rates are unpublished. 2
The Sales Ops Lead
Every base tier and the Sales/Projects add-ons carry real numbers with per-user/year maths, storage limits, tax treatment ('exclude applicable taxes'), billing cycles and switching rules — a 30-seat invoice is mostly a two-minute exercise. Monthly-billing and 3-yearly rates are never separately stated and storage extension is unpriced, keeping it short of rubric level 8. 2
The RevOps Integrator
Every tier and every add-on ladder (Sales, Projects) carries public per-user numbers with the monthly/yearly split shown, storage limits stated per tier, taxes declared excluded, and upgrade/downgrade timing spelled out — I can compute a 30-seat invoice in under a minute. Only the 'extendable' storage pricing is an unstated meter. 2
The Migrator
Every tier and both add-ons carry real public numbers with yearly billing, storage limits, USD-excluding-tax treatment, switching rules and even a $960/day services rate, so the invoice is computable. It falls short of an 8 because the monthly-billing price never appears separately, 'extendable' storage is unpriced, and the CRM x Sales x Projects plan matrix is a three-dimensional spreadsheet rather than a two-minute table. 2 2
The Skeptic
A full public matrix — base plans plus per-tier Sales and Projects add-ons, three billing cycles, taxes-excluded stated, upgrade/downgrade rules — but the $216/$432 figures ride on struck-through list prices that smell like first-year discounts, monthly-billing prices are never separately stated, and 'extendable' storage extension costs nothing publicly, which is to say it costs something privately. 2
European sovereignty — proven facts
2 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 | EU optional ⚠ unverified | 1/3 pts | 2 Report an error |
| Subprocessors | US CLOUD Act reach ⚠ unverified | 0/2 pts | 2 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 — Data residency. The region is assigned by proximity rather than an explicit EU default, so customers near the US land on US hosting, and AI data is processed on Microsoft Azure according to the deployment's region.
- Weak sourcing — Subprocessors. OVH US LLC is the US arm of the French OVHcloud group and applies only to US-region hosting, though AI features additionally run on US-based Microsoft Azure regardless of region.
- 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.
- 24 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
- 14 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 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 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 (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.eway-crm.com Checked 16 Sep 2026 Details →
- 2 Vendor pricing page www.eway-crm.com Checked 16 Sep 2026 +1 earlier capture: 11 Sep 2026 Details →
- 3 Contact & data model — found from sitemap kb.eway-crm.com Checked 1 Oct 2026 Details →
- 4 Contact & data model — found from sitemap kb.eway-crm.com Checked 1 Oct 2026 Details →
- 5 Pipeline & forecasting — found from sitemap kb.eway-crm.com Checked 1 Oct 2026 Details →
- 6 Pipeline & forecasting — found from sitemap kb.eway-crm.com Checked 1 Oct 2026 Details →
- 7 Automation & workflows — found from sitemap kb.eway-crm.com Checked 1 Oct 2026 Details →
- 8 Automation & workflows — found from sitemap kb.eway-crm.com Checked 1 Oct 2026 Details →
- 9 Integrations & API — found from sitemap kb.eway-crm.com Checked 1 Oct 2026 Details →
- 10 Integrations & API — found from sitemap kb.eway-crm.com Checked 1 Oct 2026 Details →
- 11 Import, export & exit — found from sitemap kb.eway-crm.com Checked 1 Oct 2026 Details →
- 12 Import, export & exit — found from sitemap kb.eway-crm.com Checked 1 Oct 2026 Details →