Freedcamp

How much real multi-person project work the tool carries: shared planning, assignments, dependencies, workload, comments, guest access.

0 — A personal task list; a second user has no defined place in it.

3 — Tasks can be shared and assigned, but planning stays per-person — no shared timeline, workload or dependency view.

5 — Solid shared projects with assignments, comments and at least one team-level planning view; gaps appear in cross-project or capacity planning.

8 — Team-level planning is first-class: cross-project views, workload/capacity, dependencies, guest or client access with sane permissions.

10 — Handles the full span from two freelancers to a structured department in one model — planning, capacity, permissions and client involvement all without workarounds.

Whether the tool can answer questions about the work: progress, time, budgets, utilization — and export the answer.

0 — No reporting beyond looking at the board.

3 — Fixed per-project status views only; nothing aggregates across projects and nothing exports cleanly.

5 — Useful standard reports (progress, tracked time) with basic filters and CSV export, but limited customization and no budget/utilization depth.

8 — Configurable cross-project reporting incl. time, budgets and utilization, with dashboards and reliable exports.

10 — Reporting is a product in itself: custom report builder, scheduled delivery, API access to every metric the UI shows.

How well the tool connects to the rest of the stack: native integrations, calendar/comms hooks, API and webhooks, import/export paths.

0 — A closed box — no API, no integrations, CSV out if anything.

3 — A handful of marquee integrations, no public API or an API that covers a fraction of the product.

5 — The common set (calendar, Slack/Teams, file storage) plus a documented public API; automation platforms partially covered.

8 — Broad native catalogue, well-documented API and webhooks, first-class automation-platform support and real import paths from competitors.

10 — Ecosystem-grade: everything in 8 plus the tool is itself extensible (apps/plugins, AI/MCP surfaces) and exit via API export is complete.

Time and friction from signup to first real value for a small team, without paid services.

0 — No self-serve path — onboarding starts with a sales call and an implementation project.

3 — Self-serve exists but the first project requires configuration a newcomer cannot judge yet (workflows, custom fields, permissions) before anything works.

5 — A team gets a first project running within a day; trial requires payment details or key steps live behind docs.

8 — Signup to working project inside an hour: guided setup, sensible defaults, templates, trial without payment details.

10 — Minutes to value even for non-tool-people, importers pull existing work in, and the tool teaches its own advanced features as the team grows into them.

Where the company and the data actually sit: legal entity, ownership control, data residency, and subprocessor exposure to non-EU jurisdictions.

0 — Non-European vendor, data on US infrastructure under US law, no DPA worth the name.

3 — DPA and GDPR language present, but hosting defaults to the US or ownership sits outside Europe — compliance paperwork over substance.

5 — EU data residency is available and contractually fixed, but the vendor or its controlling owner is non-European, or core subprocessors put data within CLOUD Act reach.

8 — European company under European control with EU-resident data and a public DPA; remaining exposure is limited to identifiable subprocessors (e.g. a US hyperscaler's EU region) and is documented.

10 — European company, European control, EU-only data residency on European infrastructure, subprocessor list free of extraterritorial reach — verifiable, not asserted.

Whether a stuck user gets unstuck: docs quality, support channels and their availability per plan, and the health of the learning surface.

0 — No docs beyond marketing pages; support is a contact form that may answer.

3 — Docs exist but are thin or stale; support on entry plans is effectively email-only with slow turnaround.

5 — Searchable help center covering the core product; chat or email support on all plans with reasonable response times.

8 — Deep, current docs incl. onboarding guides and templates; fast chat support not gated to top tiers; visible changelog.

10 — Docs, academy, community and support so good they are a reason to buy; SLAs published, support quality independent of plan.

Can a buyer determine the real, payable cost of the tool for their team before talking to anyone?

0 — No public pricing at all — every number sits behind "contact sales".

3 — Some tiers are public, but a deciding factor (seat minimums, mandatory add-ons, billing-period surcharge, tax treatment) only surfaces at checkout or in fine print.

5 — Self-serve tiers are publicly priced and the billing-period difference is stated, but the headline number still needs qualifying — e.g. annual-only headline, taxes excluded without saying so, or an opaque enterprise tier doing real work.

8 — Every self-serve tier is fully priced with billing periods and tax treatment plain on the page; only genuinely custom enterprise work lacks a number.

10 — Every tier including enterprise has a public price or published price formula, and the headline number is the number on the invoice.