Know where your company really stands with AI.

What's missing between rollout and routine?

Take the dive — the story in 90 seconds →
The problem

You are rolling out AI. But the big questions stay open.

The questions no dashboard answers.

Are our people actually using AI?

What do they expect from AI, and where do they get stuck?

Which training and tools do they really need?

Which ideas are hiding in the teams?

The answers already exist: inside employees' heads.

The solution

An agent that listens. And asks follow-ups.

Weekly, bi-weekly, or in step with your rollouts, for example every Friday: "How did you use AI this week?"

How it works

Three steps, on repeat.

  1. An invite lands in their inbox

    Teams, Slack, or email: no login, no coordination from you.

  2. A short one-on-one with the agent

    Adaptive follow-ups in real time, like a good conversation.

  3. You get the picture, cycle after cycle

    Themes, blockers, and quotes: captured pseudonymously, evaluated anonymously (aggregated, five or more people), ready to act on.

Experience a conversation →
Fathomly in action

Start with the question you already have.

Five examples of questions Fathomly answers. Different question, same system. Every example is synthetic and fictional.

Shadow AI

Bans don't stop shadow AI. They hide it.

People paste work into private ChatGPT or Claude accounts because the approved tools don't cover the job — and saying so out loud feels risky.

Fathomly gives every employee a protected channel to say what they actually use and need, and points to an approved alternative when one exists. You get an aggregated picture of shadow usage per area, the reasons behind it, and concrete tool needs: the basis for a whitelist decision instead of the next ban.

  1. Fathomly

    Which AI tools do you actually use for work, approved or not? Your answers stay pseudonymous, and reporting stays aggregated.

  2. Employee

    My private ChatGPT account. The approved tool can't read PDFs.

  3. Fathomly

    What would the approved setup need so you could switch?

  4. Employee

    Claude with PDF upload, for contract work.

Synthetic example Illustrative interface, not a product screenshot.

Released pattern Need · 14 mentions · Approved assistant that can read PDFs Illustrative

Automation discovery

Which automation ideas are hiding in your teams?

Employees don't need to know anything about AI. Fathomly asks about the work — repetitive tasks, hand-offs, rework — and the automation candidates emerge from the answers.

You get a shortlist of recurring tasks named across teams, each backed by how often it was mentioned and by supporting quotes. Feasibility and prioritization stay a human decision.

  1. Fathomly

    This takes 5 to 20 minutes. I'll ask about your daily work to find where AI could take work off your plate. What does a typical week look like, and which tools do you spend the most time in?

  2. Employee

    I'm in financial controlling. Most of my week is Excel: I pull exports from SAP and our billing tool, clean them up, and build the monthly reporting pack. Month-end is the worst.

Full conversation
  1. Fathomly

    The month-end pack sounds heavy. Where does the time actually go: collecting the data, checking it, or formatting the report?

  2. Employee

    Checking, mostly. The exports never match: different cost-center names, missing rows, currency formats. I reconcile them by hand with VLOOKUPs.

  3. Fathomly

    How often does that reconciliation happen, and roughly how long does it take each time?

  4. Employee

    Every month for the board pack, plus a smaller weekly one for my team lead. Maybe two days a month in total, just matching rows.

  5. Fathomly

    If that matching step were handled for you, what would you want checked before you trust the numbers?

  6. Employee

    A log of what was matched and what wasn't. I still want to see the exceptions myself.

Synthetic example Illustrative interface, not a product screenshot.

Released pattern Recurring task · 9 mentions · Cross-system reconciliation in Excel Illustrative

Adoption pulse

Where does AI already help, and where does adoption stall?

Everyone has access, yet teams progress differently. The first cycle sets the baseline, every cycle after it shows what moved: company-wide right away, and per area once enough people there have answered.

Short recurring conversations show which tasks AI already helps with and where quality or review effort slows people down — so you can aim training, templates, and support where they're needed next. Without evaluating individuals or leaders.

  1. Fathomly

    Quick check-in. Which task did AI actually help with this month?

  2. Employee

    Meeting summaries. I stopped writing them by hand.

  3. Fathomly

    And where did you stop using it?

  4. Employee

    Client reports. The tone is off and I rewrite everything.

Synthetic example Illustrative interface, not a product screenshot.

Released pattern Blocker · 10 mentions · Output tone unusable for client-facing work Illustrative

License decision

50 Copilot licenses: renew or cancel?

Telemetry shows logins, not value.

Recurring conversation cycles show where people get stuck and what is missing: a decision basis with PII-redacted quotes instead of gut feeling.

What three conversation cycles surface

  1. Cycle 1

    Which tasks the license actually supports today, and where use quietly stopped.

  2. Cycle 2

    What blocks value: rework, missing context, unclear prompts.

  3. Cycle 3

    What would change the decision: enablement, templates, or fewer licenses.

Released patterns arrive aggregated, with supporting quotes and without individual usage tracking.

Released pattern Blocker · 12 mentions · Drafts miss the project context Illustrative

Training transfer

Weeks after the AI training: what actually stuck?

Post-training surveys measure the mood on the day. Two and six weeks after each wave, the agent asks what people still actually use.

Recurring check-ins show which parts of the training made it into daily work, what got dropped and why, and where a follow-up would help — so the next enablement budget goes where transfer actually breaks down.

  1. Fathomly

    Two weeks ago you took the prompt workshop. What have you tried since?

  2. Employee

    The email templates. Those stuck.

  3. Fathomly

    What has not made it into your routine?

  4. Employee

    Longer documents. I do not trust the summaries yet.

Synthetic example Illustrative interface, not a product screenshot.

Released pattern Blocker · 8 mentions · Long-document summaries still not trusted Illustrative

From conversation to insight

One protected conversation, many voices, one released pattern.

See how recurring conversations become a released pattern and an owned next step.

Conversations

Employee · Editorial Synthetic
  1. Fathomly

    What did you last use AI for?

  2. Employee

    Drafting a research summary for a client.

  3. Fathomly

    What did you still have to fix?

  4. Employee

    Every citation. Checking sources takes almost as long as writing.

Employee · Marketing Synthetic
  1. Fathomly

    Where does the output need rework?

  2. Employee

    Claims without sources. I check each one.

Employee · Distribution Synthetic

Conversation queued in this cycle

Fathomly

Fathomly

  • de-identifying
  • clustering
  • privacy check

Pattern formingPattern released

Only aggregated patterns leave this stage — individual conversations stay reserved for authorized admins.

Released insights

Blocker · 11 mentions

High review effort

“Checking sources takes almost as long as writing.”

PII-redacted quote

Need · 12 mentions

Reviewed work examples

Human-owned action

Pilot a quality check for recurring tasks

From a released takeawayOpen

The results

An example evaluation

The real admin view, here on synthetic example data: consolidated themes with mentions per cycle.

The Fathomly admin interface showing the theme evaluation of Juniper Row Media's fictional demo campaign “AI Adoption Pulse”, English interface.
Synthetic example data The real admin interface: consolidated themes with mentions per cycle, from a fictional US media company.
Live demo on request →
Live today

What Fathomly does today.

Ten core capabilities, built and in use today: not a prototype, not a mockup.

Adaptive AI interviews

5–20-minute chats with smart follow-up questions, in German and English, including voice input.

A hard k≥5 anonymity floor

No individual-level reporting: data below the threshold never reaches the reporting model. Built for GDPR and German works-council rules.

Magic links, not an IT project

No login, no app to install: sent through your company's Teams, Slack, or email.

Recurring campaigns and cycles

Ready-made templates, flexible cadence, trends visible across cycles.

One sentence → a full interview guide

A short description becomes a versioned guide with automatic quality checks.

Automatic insight extraction

Consolidated themes, evidence-anchored narratives, drilldown to the PII-redacted quote.

“Ask the interviews”

Free-form questions against a campaign's released evaluations, any time.

Goal and evidence reporting

One quantified company goal, k-anonymous progress per cycle, exportable as a building block for your compliance documentation.

Action tracking (closed loop)

Turn insights into actions, track them, and see the impact in the next cycle.

Isolated deployment per customer

Its own database and subdomain per customer, fully separated from other tenants.

Why Fathomly

What changes with Fathomly.

DEPTH
Checkbox answers in a form Follow-up questions until the why is visible

Research shows conversational interviews yield substantially richer answers than form surveys — up to 39% more information and significantly less click-through answering.

Sources: Xiao et al., ACM TOCHI 2020 Kim et al., CHI 2019

SPEED
Weeks until the survey report Dashboard available right away

Answers aggregate continuously, not at project end.

COVERAGE
One survey a year, one sample Every employee can take part — in short cycles

Every voice can be heard, all year round.

ROLLOUT
Rollout as an IT project: months, interfaces, approvals Starts without a complex technical implementation.

We support your onboarding and get you started within hours.

Do the math

What do regular one-on-one conversations with every employee cost?

Move the sliders for your own numbers: employees, cycles per year, conversation length including analysis.

150
12
45
1.350 hours of qualified conversation work per year

0,8 full-time equivalents (FTE)

87.750 € internal cost per year

With Fathomly: it runs on the side.

Plain working-time arithmetic for structured one-on-one conversations including analysis. $75 per hour as a rough assumption for fully loaded internal cost (salary, overhead) — adjust the rate to your own numbers. No claim about productivity or outcome quality.

Discuss a pilot · 15 minutes

Let's talk about a pilot

  • From kickoff to your first cycle in a day or two. No long-term contract.
  • Not an IT project: nothing to install, no integration with your systems, nothing touches your existing software.
  • We reply personally.

A few details, and we'll get back to you personally.

* Required

or directly: [email protected]

Company

Where we stand. And why now.

Roadmap

From the first internal version to what comes after.

Five dated milestones from proof of concept to video conversations — plus the planned outlook for 2027+.

Open the timeline
Why now

Listening at scale is finally possible.

AI is rolled out top-down. Whether it lands in daily work stays invisible — the thesis behind Fathomly in three paragraphs.

Read the thesis

Roadmap

Delivered up to today, planned beyond it. Anything planned is not yet part of today's product.

  1. Q4 2025

    Proof of concept. First internal version: LLM-led conversations instead of static surveys.

  2. Q1 2026

    Production-ready core. Adaptive agent with automatic follow-ups (German/English), voice answers with automatic transcription, and an analysis pipeline with topic clustering and evidence quotes — personal data redacted before analysis model calls.

  3. Q3 2026 today

    Public launch. fathomly.ai and The Dive go live; pilot program underway.

  4. Q4 2026 Planned

    Where your team already works: Microsoft Teams and Slack integration — invitations go out straight from Fathomly, with no manual step in between.

  5. 2027 Planned

    Video conversations: interviews over video too, where text and voice aren't enough.

2027+ Planned

No fixed quarter and no promised date: the direction Fathomly takes from there.

  • Company SSO integration

    Single sign-on through your company's identity provider.

  • Personalized, branded campaigns

    Your own look and tone, tailored per department or team.

  • Anonymous mode and opt-in campaigns

    A toggle for anonymous participation, plus consent-based, attributed campaigns.

  • Follow-up engine

    Open items automatically resurface as follow-ups across future cycles.

  • HRIS and telemetry import

    Org data from Personio or HiBob, complemented by usage signals like Copilot telemetry.

  • Cohort comparisons

    Compare groups by campaign attribute, strictly k≥5 per cohort.

Why now

AI is being rolled out top-down almost everywhere: licenses bought, trainings run, targets set.

Whether it lands in daily work, though, is invisible. Usage dashboards count clicks, engagement surveys measure sentiment. The reasons stay below the surface.

The companies that win the coming years are the ones that close this feedback gap now. Listening at scale is finally possible — because the agent doing the listening is AI itself.

See the story: The Dive →