Product
Seven modules. One event-graph.
Customers see a clean shortlist. Inside it: a data factory turning raw events into explainable opportunities.
The platform
From raw event to named opportunity.
Luma, CSV, Telegram, event rosters.
Junk filter, generic-email flags.
Identity graph, dedupe across events.
Role, stage, chain, fund thesis.
Fit · Intent · Fresh · Safety.
Telegram + email sequences.
Meetings, replies, pipeline ROI.
Modules in detail
Each module earns its place.
No grab-bag of features. Seven jobs, each with a clear input, a clear output, and a reason to exist.
- 01
Import
Get every event into one place.
- Luma exports, Eventbrite, CSV, XLSX, manual paste.
- Telegram group exports and roster screenshots.
- Per-source tags, dates, and confidence captured at ingest.
Output
Raw event roster, normalized rows.
- 02
Clean
Kill the junk before it touches your graph.
- Generic-email, role-account and burner detection.
- Bounce, syntax and MX validation.
- Spam / scam handle flags from prior signals.
Output
Trustable contact rows with quality flags.
- 03
Resolve
One person across eight events is one person.
- Identity graph across email, handle, wallet, company.
- Cross-event dedupe with conflict reasons exposed.
- Merge UI for the 5% the graph won't auto-resolve.
Output
Stable person and project identities.
- 04
Enrich
Add the context your ICP filter needs.
- Role, seniority, decision power.
- Project stage, chain, vertical, fund thesis.
- Public on-chain and social signals.
Output
Filterable, sliceable account graph.
- 05
Score
Sort the room by who matters this week.
- Fit · Intent · Fresh · Safety · Reach layers.
- Per-tenant weights for audit, MM, infra ICPs.
- Every score is explainable — no black box.
Output
Composite 0–100 with reason codes.
- 06
Outreach
Touch the right channel without breaking it.
- Telegram and email sequences with channel consent.
- Per-handle throttles to protect deliverability.
- Reply detection and hand-off to humans.
Output
Replies, meetings booked, threads owned.
- 07
Report
Prove what worked. Cut what didn't.
- Pipeline by event, ICP, source, channel.
- Meeting → opportunity → revenue attribution.
- ROI per conference, per booth, per sponsorship.
Output
Boardroom-ready GTM report.
Account graph
A handle is a handle. Context is value.
Search stops being "find people." It becomes "find projects seen at three events, with a founder Telegram handle, matching the audit ICP." That's a knowledge graph, not a contact list.
Scoring in-app
Every score, explainable.
No black box. Open a record and see Fit, Intent, Fresh, Safety and Reach — with the reason codes that produced the number.
Opportunity · 0142
Helix Protocol
Pre-TGE · L2 perps · Token2049 Singapore
What goes into the score
- FitICP match — vertical, stage, chain, role90
- IntentEvent recency, role signals, public moves82
- FreshLast-verified date and source decay75
- ReachChannel availability — Telegram, corporate email68
- SafetySource confidence, opt-out, spam risk88
Data engine
Chaos in. Asset out.
The moat isn't the interface. It's a clean, deduplicated, explainable Web3 data graph.
- 01ImportCSV, XLSX, Luma exports, event lists, Telegram group exports, manual uploads.
- 02NormalizeNames, companies, domains, Telegram handles, email quality, role titles.
- 03DeduplicateOne person in 8 events and 5 files is not 13 leads.
- 04Source ledgerEvery contact stores source, date, confidence and allowed channels.
- 05RefreshStale contacts move down. Fresh event signals get priority.
Integrations
Plays well with your existing stack.
Sources flow in. Scored opportunities flow out. Your CRM stays the system of record — Web3crm is the GTM layer feeding it.
Source
Luma
Source
Eventbrite
Source
CSV / XLSX
Source
Telegram
Source
Twitter / X
Source
Etherscan
Source
Dune
Sync
HubSpot
Sync
Salesforce
Export
Notion
Export
Slack
Export
Webhook / API
Security & control
Provenance over guesswork.
Built for teams that get audited. Every contact knows where it came from, who can touch it, and how to leave.
Control
Source ledger
Every row carries the event, date, file and confidence it came from. Audit-grade provenance, not vibes.
Control
Channel consent
Telegram and email are tracked as separate channels with separate opt-outs. Break neither.
Control
Workspace roles
Owner, operator, viewer. Scoped exports. Per-workspace ICP weights and outreach guardrails.
Control
Data residency
EU-hosted by default. Per-tenant deletion and export on request. SOC2 roadmap public.
Modules, one graph
Sources & syncs
Search latency
Explainable scores
FAQ
Things buyers ask.
Six fast answers for audit firms, market makers and founders evaluating Web3crm.
Is this a CRM replacement?
No. Web3crm is the GTM layer that feeds your CRM — scored opportunities with source, role, intent and freshness. HubSpot and Salesforce sync both ways.Where does the data actually come from?
Your imports first: Luma rosters, event CSVs, Telegram exports. We enrich with public on-chain and social signals. Every row keeps its source and date.How are scores explainable?
Every score breaks down into Fit, Intent, Fresh, Safety and Reach layers, each with reason codes. You can see exactly why a lead is 84 and not 62.Can I export everything?
Yes. CSV, webhook, HubSpot/Salesforce sync, or API. Your data is yours — including the dedupe graph and score history.How do you handle Telegram responsibly?
Per-handle throttling, consent tracked separately from email, and hard caps on sequence volume. Built so you don't burn your handle or your reputation.How is this different from Apollo, Clay, or Common Room?
Those are great for Web2. Web3crm is built on the event-graph: conferences, Telegram, on-chain. ICP filters, scoring and outreach are tuned for token-economy GTM.