whats-best.ai
Search Sign in

CRM

folk

EU-Made Report an error

Panel 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 Folk SAS · www.folk.app

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 Data Protection Officer

Weighted verdict

Knows a CRM is a database of other people's personal data before it is a sales tool. Optimizes for GDPR posture: EU hosting, DPA, subprocessor hygiene, consent fields, retention and deletion that actually delete. Rejects US-default hosting and enrichment features that scrape contacts from the open web.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Data Protection Officer

Contact & data model

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.

Report an error

The Data Protection Officer

People, companies, deals and custom objects are modelled, with eight custom field types including cross-record references to contacts, workspace members and objects, and companies carrying native fields such as funding raised and employee range. We found no public information on deduplication, merge tooling, field validation or field-level permissions, and custom objects and deals sit behind the Premium plan. 4 5 2

Report an error

Pipeline & forecasting

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.

Report an error

The Data Protection Officer

Shared pipelines with customizable roles and permissions, stage sets from qualification through closed-won/closed-lost, and dashboards for deal velocity, win rate, pipeline coverage and conversion by stage are documented. We found no public information on required fields per stage, stage gates, quota tracking, weighted forecasting or historical snapshots, and dashboards are a Premium feature. 1 6 7 2

Report an error

Automation & workflows

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.

Report an error

The Data Protection Officer

The documented Workflow Assistant is a single structure — trigger on created or updated, optional filters, one automated email — with campaign analytics, and cross-group creation runs through Zapier, Make or a help recipe; we found no public information on branching, delays or per-step logs. Every workflow completion consumes one credit and the assistant is disabled when credits run out, so the feature is metered and capped rather than infrastructure. 8 9

Report an error

Integrations & API

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.

Report an error

The Data Protection Officer

A documented REST API over HTTPS with bearer auth, version pinning, documented rate limits and coverage of people, companies, deals, custom objects, notes, tasks, interactions and webhooks, alongside native Gmail, Outlook, Google Calendar, Google Contacts and WhatsApp sync plus Zapier and Make apps. API access is gated to the Premium plan, and we found no public information on calendar write-back or a public app marketplace. 10 13 11 2

Report an error

European sovereignty

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.

Report an error

The Data Protection Officer

The privacy policy names Folk Inc., a Delaware corporation, as data controller, while hosting runs on AWS in Ireland by default with a published data processing agreement and a full subprocessor list — a list that routes contact data to US enrichment processors including Apollo.io, OpenAI, People Data Labs and Perplexity. Deletion clears databases in seven days but backups persist for 730 days and application logs for up to 930 days, and we found no public information on consent fields for contacts. 3 11

Report an error

Import, export & exit

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.

Report an error

The Data Protection Officer

Export works group by group — the help pages state exporting from the whole workspace is currently not allowed — and produces two CSV files of contacts and notes, excluding interactions, reminders, contact custom fields and connection data unless every field is displayed beforehand. CSV import, a migration service and an API covering more objects give a partial path out, but API access requires the Premium plan. 12 2 13

Report an error

Pricing transparency

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.

Report an error

The Data Protection Officer

Standard at $24 /member/month billed $288 yearly, Premium at $48 /member/month billed $576 yearly and Enterprise from $80 /member/month billed $960 yearly are public, with annual billing saving 20% and unlimited members on every plan. However automation and AI run on a credit meter — 1,500 credits a month on Standard, 10,000 on Premium/Custom, one credit per workflow completion, disabled when exhausted — and we found no public information on VAT treatment or monthly-billed rates. 2 8

Report an error

European sovereignty — proven facts

1 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Ownership Not determined — uncited Report an error
Data residency Not determined ⚠ unverified — uncited Report an error
Subprocessors Not determined — uncited Report an error

Where this could be wrong

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.

Do you know more about folk? Tell us Report an error on this page

Sources (13)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage www.folk.app Checked 15 Sep 2026 Details →
  2. 2 Vendor pricing page www.folk.app Checked 15 Sep 2026 Details →
  3. 3 Privacy policy www.folk.app Checked 30 Sep 2026 Details →
  4. 4 Contact & data model — found from sitemap developer.folk.app Checked 1 Oct 2026 Details →
  5. 5 Contact & data model — found from sitemap developer.folk.app Checked 1 Oct 2026 Details →
  6. 6 Pipeline & forecasting — found from sitemap www.folk.app Checked 1 Oct 2026 Details →
  7. 7 Pipeline & forecasting — found from sitemap www.folk.app Checked 1 Oct 2026 Details →
  8. 8 Automation & workflows — found from sitemap help.folk.app Checked 1 Oct 2026 Details →
  9. 9 Automation & workflows — found from sitemap help.folk.app Checked 1 Oct 2026 Details →
  10. 10 Integrations & API — found from sitemap developer.folk.app Checked 1 Oct 2026 Details →
  11. 11 Integrations & API — found from sitemap www.folk.app Checked 1 Oct 2026 Details →
  12. 12 Import, export & exit — found from sitemap help.folk.app Checked 1 Oct 2026 Details →
  13. 13 Import, export & exit — found from sitemap help.folk.app Checked 1 Oct 2026 Details →