AI agents trained on Asana + Fathom data
Linked Asana and Fathom history pairs work-tracking history with sales history. That joined record is what lets an AI agent follow a job from one team to the next.
Get matched with buyersFree. No obligation. You approve every step.
We may earn a referral fee from buyers we list. Buyers, not us, pay you, and fees can affect which offers we show. See how we make money.
What happens between Asana and Fathom today
Zapier publishes 1 named template connecting these two apps (Zapier integration page). In plain terms, the most common hand-offs are:
- A new Fathom Action Item creates an Asana Task.
On the Asana side the trail runs through Task, Project, Subtask, Section; on the Fathom side through Action Item, Video, Recording, AI Summary.
Beyond this pair, Zapier users most often connect Asana to Google Calendar, Gmail, Google Forms, and Fathom to Notion, Google Drive, ClickUp.
What an agent trained across both could do
Each of these needs records from both systems at once:
- Sales-to-delivery hand-off. An agent that turns Fathom Action Item records from the sales conversation into Asana Task plans, so delivery starts with the agreed scope.
- Action items from calls. An agent that creates Asana Task items from each Fathom Transcript with the right owner.
- Cross-system look-ups. An agent that answers questions that need both Fathom Action Item records and Asana Task records at once, such as what happened to a customer after a hand-off.
Why buyers pay more for linked histories
Joined Asana and Fathom records let a model see a full workflow, not two disconnected logs. SourceX says it prefers many in-scope systems: a complete application list of five or more, with at least three needed to submit (SourceX seller guidance).
Side by side
| Asana | Fathom |
|---|---|
| Task | Action Item |
| Project | Video |
| Subtask | Recording |
| Section | AI Summary |
| Comment | Highlight |
| Story | Transcript |
| Attachment | - |
| Workspace/Organization | - |
| Comment/Story | - |
| File | - |
| Task Comments | - |
| Task Attachments | - |
Buyers that want either side
Buyers that license project and work-tracking history or crm and sales records, quoted as published.
Turing (Lazarus) buyer
- What they buy
- “Communication, work tracking and operating history; licensed non-exclusively”
- Size fit
- Not published
- Closed companies
- Not published
- Payout as published
- “Revenue share: paid each time the record sells (no fixed price published)”
micro1 buyer
- What they buy
- “Operational records: SOPs, process docs, knowledge bases, internal comms, CRM and support history”
- Size fit
- 30+ employees
- Closed companies
- Yes: “Separate program for defunct companies”
- Payout as published
- “$100K–$3M+ (marketed range for approved data packages)”
SourceX buyer
- What they buy
- “Support conversations, CRM, engineering and workflow histories”
- Size fit
- 50+ full-time employees at peak
- Closed companies
- Yes: “Operating, acquired and wound-down companies can qualify”
- Payout as published
- “Up to $4M (SourceX says this is an upper bound for the largest datasets, not typical)”
Replay buyer
- What they buy
- “Code and commits, decision threads, financial records, product logs, CRM”
- Size fit
- 20+ employees (lowest band shown)
- Closed companies
- Not published
- Payout as published
- “Shows bands by headcount (20–50, 50–250, 250+); see Replay's page”
AfterQuery buyer
- What they buy
- “Records of how teams work across email, chat, tickets, CRM, finance and industry systems”
- Size fit
- Not published
- Closed companies
- Not published
- Payout as published
- “Not published (terms proposed after reviewing a sample)”
Ventra broker
- What they buy
- “Email, chat, tickets, CRM, documents; CAD, video and game files”
- Size fit
- 30+ staff in US, UK or Canada (reported)
- Closed companies
- Not published
- Payout as published
- “$100K–$2M potential deals (reported by AI Data Payout)”
Buyer terms are quoted from each program's published page as of 2026-11-16; we don't edit them. How we check them: methodology.
What to strip before licensing
- Staff names and contact details (PII) are pseudonymised.
- Client names and confidential project details are tokenised or excluded per client contracts.
- Attachments containing personal data, contracts or HR material are excluded.
- Time entries tied to individuals are aggregated if the buyer's scope allows.
- Customer and prospect names, emails and phone numbers (PII) are removed or tokenised.
- Call recordings and transcripts are de-identified; consent rules for recorded calls are checked.
- Payment card numbers or bank details pasted into notes are stripped.
- Personal notes about individuals that are not business records are excluded.
- Buyers de-identify records before training, and you can ask for their method in writing.
- An NDA is signed before any sample leaves your systems.
- You approve the data scope: which systems, which years and which fields.
What it could be worth
- micro1's own estimator API returns about $184,925 for a US company with 30 employees and 3 years of records, and about $239,192 at 50 employees and 5 years (low end of its range). Published calculator output (low end), not a quote Source: micro1 data estimate.
- SourceX's public estimator starts at $50,000 for 50-99 employees and $100,000 for 100-999 employees (low end of each band); 50+ peak full-time employees required. Published band (low end) Source: SourceX estimator.
Buyers price the company's whole dataset: how many systems, how many years and how many people produced it, not a single app. No per-app price exists, and these figures are not a quote or a guarantee.
Sources
- Zapier: Asana + Fathom integrations
- Zapier: Asana
- Zapier: Fathom
- micro1 data estimate
- SourceX estimator
- SourceX seller guidance on in-scope systems (no public URL; summarised)
FAQ
Which Asana and Fathom records connect?
Mostly Task and Project records in Asana, and Action Item and Video records in Fathom. The agent jobs above (sales-to-delivery hand-off, action items from calls, cross-system look-ups) show how they combine.
Do I need both Asana and Fathom to sell data?
No. Either can be licensed alone, but buyers price the whole company dataset, so linked Asana and Fathom history is usually worth listing together.