Lead to Opportunity
Governed by the Customer Relationship Management Practice Area. Ownership is singular: one Practice Area is accountable for this Process Architecture, and every reading of it - public or authorized - resolves through that ownership.
Blueprint Preview
How BlueprintEA reads this process. Every reading below is a projection of the same governed record - nothing here is written for this record.
What happens?
Process Reading
Business flow
What transformation does this process perform?
Customer demand becomes qualified pipeline
Enters on
Lead accepted by sales
Concludes on
Qualified opportunity created
Governed observation
Marketing Automation participates in this process. Customer Relationship Management owns it.
BlueprintEA separates ownership from participation. Accountability stays singular even when the work crosses organizational boundaries, which is what keeps an architecture business-led rather than application-centric.
Business activities
What work happens inside it?
01
Lead Capture
Marketing
02
Qualification
SDR
03
Conversion
Sales
04
Opportunity Management
Sales
What participates?
Enterprise Reading
Enterprise participants
Which systems participate?
Business applications
Systems where people perform business work.
- Salesforce
- HubSpot
- Marketo
- Outreach
- Gong
- Drift
- HubSpot Chat
- Gainsight
- Chorus
Automation services
Services that perform governed work automatically.
- HubSpot Forms
- HubSpot Workflows
- Marketo Engagement Program
- Marketo Trigger Email
Integration services
Services that exchange information between participants.
- Marketo-SFDC Sync
- HubSpot-SFDC Sync
- Marketo Contact Sync
- HubSpot Contact Sync
External ecosystems
Platforms that participate but are governed outside the enterprise.
- ZoomInfo
- Clearbit
- Google/Facebook Ads
Relationships
How does it connect to other processes?
Hands off to Opportunity to Quote
Hands off: Qualified opportunity
Participates in Lead to Cash
How does BlueprintEA know this?
Understanding BlueprintEA
Everything below is captured directly from the governed BlueprintEA platform and preserved as evidence beside this published record. It is here to show where this record actually lives - not to show an interface.
Where this sits in the catalog
How much governed knowledge stands behind this one record?
A capture of the authorized Process Architecture Catalog, taken from the running platform rather than drawn for this page. The page shows the part of the catalog this record belongs to; the full capture opens on click. It is cropped, never composed: what a visitor sees here is what an authorized reader sees there.
Inside BlueprintEA
What does working with this record actually look like?
A capture of the authorized Architecture Workspace for this Process Architecture, taken from the running platform rather than drawn for this page. The page shows the coverage reading and the governed activities beneath it; the full capture opens on click. It is cropped, never composed: what a visitor sees here is what an authorized reader sees there, with client identity removed.
Reference coverage
Where is this process already governed to depth?
BlueprintEA governs 7 platforms in the Customer Relationship Management Practice Area. 2 declare a reference implementation of this process today.
Declared
- Salesforce
- HubSpot
Not declared
- Microsoft Dynamics 365
- Zoho CRM
- Freshworks
- Monday CRM
- Pega CRM
A reference implementation existing on a platform does not mean it applies to a given enterprise. Coverage reports where authored depth exists; whether that depth fits an organization is decided against that organization's own governed architecture.
Why this record is public
Lead to Opportunity is the Process Architecture BlueprintEA has authored to the greatest depth, and the one an outside reader most often already owns an opinion about. It is published on its own merits, not because CRM is public: it is the first published record where a visitor reads governed depth rather than governed identity.
Published Aug 9, 2026, on its own declaration.
Governed position
- Practice Area
- Customer Relationship Management
- Lifecycle family
- acquire
- Position in family
- 20
What this record does not claim
Publishing makes this record readable; it does not author anything new. Every fact above is read from the register that governs it.
What is published is a declared set of projections of this record, not everything an authorized reader works with. Client observations, recommendations, and project evidence are never published. Where a projection is empty, the absence is named with the rule behind it rather than approximated for a visitor.