--- title: AnChain.ai HubSpot Setup — Lead-to-Deal Pipeline type: article created: '2026-04-05' updated: '2026-04-05' source_docs: - raw/2026-01-08-complimentary-strategy-session-eddie-fu-112941245.md tags: - hubspot - crm - anchain-ai - pipeline - lead-generation - sales-process - abm - web3 - crypto-compliance layer: 2 client_source: null industry_context: null transferable: true --- # AnChain.ai HubSpot Setup — Lead-to-Deal Pipeline ## Overview AnChain.ai uses HubSpot as its primary CRM. During the [[wiki/clients/anchain-ai/index|AnChain.ai]] discovery call, Eddie Fu confirmed HubSpot is in place but the pipeline is not yet systematically configured to support the ABM pilot. The goal is to wire HubSpot so that leads generated by Asymmetric's campaigns flow cleanly through qualification and into active deals that Eddie (the sole sales resource) can work to close. This article documents the recommended pipeline structure, lifecycle stage logic, and deal-creation criteria for the [[wiki/knowledge/abm/anchain-abm-pilot|90-day ABM pilot]]. --- ## Pipeline Architecture ### Lead Sources → HubSpot Ingestion All inbound and outbound lead sources should be mapped to HubSpot contacts at the point of first touch: | Source | Ingestion Method | |---|---| | Website demo request form | Native HubSpot form → Contact created automatically | | Apollo outbound sequences | Apollo ↔ HubSpot sync; contact created on reply or click | | Paid ad landing pages | HubSpot-hosted or embedded form per persona landing page | | Referrals / event contacts | Manual contact creation with source field set | Each contact should have **Original Source** and **Lead Source Detail** populated at creation. For the ABM pilot, add a custom property `ABM Persona` with values: - `Compliance Officer` - `Private Investigator` - `Bankruptcy Lawyer` This allows per-persona funnel reporting from day one. --- ## Lifecycle Stage Progression AnChain.ai's sales motion is high-touch and relatively low-volume (niche within a niche). Lifecycle stages should reflect deliberate qualification gates rather than automated bulk progression. ``` Subscriber → Lead → Marketing Qualified Lead (MQL) → Sales Qualified Lead (SQL) → Opportunity (Deal) → Customer ``` ### Stage Definitions **Lead** Contact has entered the system via any source. No qualification has occurred. Eddie should not be spending time here yet. **MQL** Contact has shown meaningful intent: completed a demo request, replied to an outbound sequence, clicked a persona-specific landing page CTA, or engaged with two or more content assets. Marketing (Asymmetric) owns progression to MQL. **SQL** Eddie has made first contact, confirmed the contact has budget authority or influence, and the use case maps to one of the three target personas. Eddie owns progression from MQL → SQL. Suggested SQL qualification criteria (adapt BANT to AnChain's context): - Works at a target account type (bank/fintech, PI firm, law firm with bankruptcy practice) - Has a crypto compliance, asset recovery, or AML pain point - Has decision-making authority or a clear path to the decision-maker - Is not a student, journalist, or competitor **Opportunity (Deal)** SQL has agreed to a follow-up meeting or demo. A Deal record is created in the pipeline at this point. Do not create deals for contacts who have not confirmed a next step. **Customer** Contract signed, subscription activated. --- ## Deal Pipeline Stages Create a single pipeline called **AnChain Sales Pipeline** with the following stages: | Stage | Description | Probability | |---|---|---| | Demo Scheduled | First meeting confirmed | 10% | | Demo Completed | Demo held, interest confirmed | 25% | | Proposal Sent | Pricing/scope sent to prospect | 40% | | Negotiation | Active back-and-forth on terms | 65% | | Verbal Commit | Prospect has said yes, paperwork pending | 85% | | Closed Won | Contract signed | 100% | | Closed Lost | No longer pursuing | 0% | ### Deal Properties to Populate at Creation - **Deal Name:** `[Company] — [Persona]` (e.g., `Mercury Bank — Compliance Officer`) - **Close Date:** Estimated (required for pipeline forecasting) - **Deal Amount:** Use AnChain's pricing tiers as a guide — entry $299/mo, mid $2,500/yr, high $25,000/yr - **ABM Persona:** Mirror the contact property - **Lead Source:** Carry over from the associated contact --- ## Practical Notes for Eddie **No-show management:** Cold outbound is currently producing no-shows (two on the day of the discovery call). HubSpot sequences should include an automatic one-touch follow-up email 30 minutes after a missed meeting, plus a task reminder for Eddie to attempt a same-day call. Do not let no-shows age into dead contacts without a second attempt. **Demo request follow-up SLA:** Historically, demo requests came in via the website and Eddie manually emailed to schedule. Set up a HubSpot workflow: when a demo request form is submitted → assign to Eddie → create a task due within 2 business hours → send an automated acknowledgment email to the prospect. Speed-to-lead matters. **Lifecycle stage automation:** Use HubSpot workflows to auto-advance contacts from Lead → MQL based on engagement scoring (form fill + landing page visit, or two email clicks). SQL progression should remain manual — Eddie confirms fit before the stage moves. --- ## Reporting Views to Configure Set up the following saved views and dashboards for the pilot: 1. **MQLs by Persona (last 30 days)** — confirms which persona campaigns are generating interest 2. **SQL Conversion Rate by Persona** — identifies where leads are dropping out of qualification 3. **Open Deals by Stage** — Eddie's working pipeline at a glance 4. **No-Show / Ghosted Contacts** — contacts with a meeting logged but no outcome recorded after 48 hours --- ## Related Articles - [[wiki/clients/anchain-ai/index|AnChain.ai Client Overview]] - [[wiki/knowledge/abm/anchain-abm-pilot|AnChain.ai 90-Day ABM Pilot]] - [[wiki/knowledge/outbound/apollo-crm-rebuild|Apollo CRM Rebuild — Outbound Sequencing]] - [[wiki/knowledge/sales-process/sql-qualification-framework|SQL Qualification Framework]] - [[wiki/knowledge/pricing/anchor-pricing-strategy|Anchor Pricing Strategy]]