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 RevOps Integrator

Weighted verdict

Treats the CRM as one system in a revenue stack. Optimizes for two-way email and calendar sync, a real API with webhooks, and native connections to the tools money already flows through. Rejects closed ecosystems and integrations that are one-way imports in disguise.

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

Scored by The RevOps Integrator

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 RevOps Integrator

The data model has genuine depth: companies with native firmographic fields linked to people, group-scoped custom fields in eight types including contact, user and object links to deals and custom objects, all reachable through the API. We found no public information on dedupe or merge tooling or field-level history, and removing a person from a group removes the custom field values with it — a hygiene landmine for a shared revenue database. 4 5 13 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 RevOps Integrator

Pipelines are collaborative kanbans with named stages through closed-won and closed-lost, and dashboards track deal velocity, win rate, pipeline coverage and conversion by stage. But we found no public information on stage-level required fields, forecast views, quota tracking or historical snapshots — there is nothing here a finance department could forecast from, and dashboards sit behind the Premium tier. 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 RevOps Integrator

The native Workflow Assistant is a trigger on created or updated plus optional filters plus one send-email action, metered at one credit per completion and hard-disabled when credits run out — automation as its own upsell. Multi-step logic appears only through Zapier and Make; we found no public information on branching, delays or routing inside folk itself. 8 9 6

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 RevOps Integrator

This is the strong suit: a documented REST API over the full core object set including deals, custom objects and webhooks, with versioning, rate limits, bearer-key management, plus native Gmail and Outlook conversation sync, WhatsApp, enrichment partners and MCP endpoints for AI tools. The calendar connection operates on a read-only scope — event import, not two-way writeback — and we found no public information on public OAuth apps; several directory entries also route through Zapier or Make rather than native connectors. 13 10 4 11 3

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 RevOps Integrator

Hosting is AWS Ireland with a published DPA and a region-labeled subprocessor list, but the captured privacy policy names Folk Inc., a Delaware corporation, as the data controller, while the vendor provenance in this sheet presents Folk SAS, Paris — the captured pages give different information about the entity. Core flows touch US-region subprocessors for contact and interaction sync (Google Workspace, Microsoft 365, WhatsApp) and enrichment (Apollo, OpenAI, People Data Labs), and deletion tails run to 730 days in backups and 930 days in application logs. 3

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 RevOps Integrator

CSV export covers contacts and notes only, per group rather than per workspace, and the vendor's own help page lists what is excluded — interactions, reminders, contact custom fields, strongest connection, people in the company view — with the export following whichever columns happen to be displayed. A migration service exists and the API reaches more objects than CSV does, but API access sits behind the Premium tier, and we found no public information on import dedupe or dry-run. 12 13 2

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 RevOps Integrator

Standard, Premium and Enterprise all carry public per-member figures with annual totals, and the credit system is unusually well disclosed — monthly credits per plan, one credit per workflow completion, and the disable-and-upgrade behavior when they run out. We found no public information on VAT treatment or monthly-billing prices, and the captured pages give different starting figures for the product — $20/user/month in the comparison article versus $24/member/month on the pricing page. 2 8 7

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.

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 →