Basics
Lead-to-revenue lifecycle
Follow the full commercial path from visitor touch to CRM qualification, forecast, delivery, and customer context.
Use this guide when you need to understand how marketing, CRM, commerce, learning, support, and AI connect during the revenue journey.
The short version
- A visitor lands on a public page.
- Marketing records attribution and form activity.
- CRM creates or updates a lead.
- Sales qualifies, routes, enriches, and converts the lead.
- Deal work moves through pipeline, forecast, and reporting.
- After the sale, payments, delivery, support, and customer success attach to the same account context.
Lifecycle map
What each stage changes
Visitor to lead
- Marketing pages and forms create the first measurable touchpoints.
- Campaigns, funnels, landing pages, and CMS pages provide attribution.
- A public form submission creates or updates a CRM lead.
Open next:
Lead to qualified pipeline
- Sales reviews stage, owner, value, source, recent activity, and attribution.
- Routing rules, enrichment, duplicate review, and AI scoring help the team prioritize.
- Conversion creates downstream CRM records so pipeline work can begin.
Open next:
Qualified pipeline to forecast
- Deals become the shared source of truth for active revenue work.
- Saved views, forecast, reports, and activity history depend on stage hygiene.
- AI suggestions and quick communication logging help reps keep records current.
Open next:
Won deal to delivery and retention
- Payments, learning delivery, support tickets, onboarding, health, renewals, and expansion all attach to the same account story.
- This is where the platform stops behaving like separate departments and starts behaving like one customer operating system.
Open next:
- Manage offers, events, and payments
- Deliver training and certification
- Customer support and renewals
What to watch for
- Missing campaign or landing-page links before publishing public capture
- Leads staying unqualified too long without a next step
- Deals moving forward in reality but not in the CRM
- Payments, support work, or learning activity drifting away from the customer record