isvcosell.com — decision tree, every scenario
Every Google Cloud scenario
The same decision tree as the interactive wizard, expanded as one document: every question, every branch, every reachable outcome. Nothing here is hand-written — it is derived from the knowledge graph and proven exhaustive by lib/decisionTree.test.ts.
473 reachable outcomes for Google Cloud.
Did you source this pursuit yourself, rather than receiving it from the cloud field team?
Before anything is registered, establish who controls customer access, technical validation, funding, procurement, and record repair.
Yes — Self-sourced
Is the pursuit qualified?
Opportunity is qualified for sales: a real buyer is named, verified customer evidence is documented, the workload aligns to our solution, services support is justified, and there is a viable route to production.
Yes — Qualified
Do you already know the Google Cloud field seller for this account?
The correct field seller is known or a partner-record route is selected
Yes — Owner known
Did the seller explicitly accept ownership, the partner role, and a next customer action?
Seller confirms ownership, partner role, support, and customer action
Yes — Accepted
Did the design pass production review?
The design is production-ready or the repair scope is explicit
Yes — Pass
Are you seeking Google Cloud funding for a proof activity?
Technical approval, cloud route, services scope, procurement, attribution path, and customer approval align
Yes — Funding sought
Does the activity clear funding pre-qualification?
Pre-qualify eligibility before presenting funding to the customer. Customer demand, sponsor, workload, success measure, and a production conversion all have to exist.
Yes — Request funding
Was the request approved as submitted?
Preserve the pursuit only when customer value survives the funding decision.
Yes — Approved
Did the customer approve production scope after the proof?
The customer approves production scope or documents the failure
Yes — Convert
Is there an eligible marketplace offer for this transaction?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Marketplace
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Not marketplace
Can it close on direct or existing cloud terms?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Direct or existing
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Blocked
Resolve route or eligibility — repair, then re-enter
Offer · agreement · legal · commitment
Re-enter at: Procurement choice
No — Repair the proof
Resolve the conversion failure — repair, then re-enter
Measure · sponsor · scope · procurement
Re-enter at: Measured activity
No — Not approved
Was it approved at a reduced size?
Preserve the pursuit only when customer value survives the funding decision.
Yes — Resized
Did the customer approve production scope after the proof?
The customer approves production scope or documents the failure
Yes — Convert
Is there an eligible marketplace offer for this transaction?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Marketplace
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Not marketplace
Can it close on direct or existing cloud terms?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Direct or existing
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Blocked
Resolve route or eligibility — repair, then re-enter
Offer · agreement · legal · commitment
Re-enter at: Procurement choice
No — Repair the proof
Resolve the conversion failure — repair, then re-enter
Measure · sponsor · scope · procurement
Re-enter at: Measured activity
No — Not resized
Will the customer fund the activity themselves?
Preserve the pursuit only when customer value survives the funding decision.
Yes — Customer-funded
Did the customer approve production scope after the proof?
The customer approves production scope or documents the failure
Yes — Convert
Is there an eligible marketplace offer for this transaction?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Marketplace
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Not marketplace
Can it close on direct or existing cloud terms?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Direct or existing
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Blocked
Resolve route or eligibility — repair, then re-enter
Offer · agreement · legal · commitment
Re-enter at: Procurement choice
No — Repair the proof
Resolve the conversion failure — repair, then re-enter
Measure · sponsor · scope · procurement
Re-enter at: Measured activity
No — Not customer-funded
Is there a compelling event worth deferring to, with demand still intact?
Preserve the pursuit only when customer value survives the funding decision.
Yes — Deferred
Defer until compelling event — repair, then re-enter
Eligibility · timing · evidence
Re-enter at: Funding choice
No — Exit
Exit when demand depends on funding — ends here
No customer-backed route
No — Proceed without funding
Is there an eligible marketplace offer for this transaction?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Marketplace
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Not marketplace
Can it close on direct or existing cloud terms?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Direct or existing
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Blocked
Resolve route or eligibility — repair, then re-enter
Offer · agreement · legal · commitment
Re-enter at: Procurement choice
No — Direct close
Is there an eligible marketplace offer for this transaction?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Marketplace
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Not marketplace
Can it close on direct or existing cloud terms?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Direct or existing
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Blocked
Resolve route or eligibility — repair, then re-enter
Offer · agreement · legal · commitment
Re-enter at: Procurement choice
No — Rework
Revise the production design — repair, then re-enter
Architecture · security · data · scope
Re-enter at: Technical validation
No — Declined or silent
Did the seller never respond at all?
Tie the failure to one actionable cause before repairing anything. Use evidence from the seller, the portal, the customer, and the account map.
Yes — Seller silent
Re-present the repaired pursuit — repair, then re-enter
New evidence · corrected owner · revised scope
Re-enter at: Cloud seller pre-wire
No — Not seller silent
Did it reach the wrong account owner?
Tie the failure to one actionable cause before repairing anything. Use evidence from the seller, the portal, the customer, and the account map.
Yes — Wrong owner
Re-present the repaired pursuit — repair, then re-enter
New evidence · corrected owner · revised scope
Re-enter at: Cloud seller pre-wire
No — Not wrong owner
Does an existing pursuit already own this opportunity?
Tie the failure to one actionable cause before repairing anything. Use evidence from the seller, the portal, the customer, and the account map.
Yes — Duplicate
Attach and preserve contribution — repair, then re-enter
Merge records · classify role
Re-enter at: Linked opportunity governance
No — Not duplicate
Is the customer's timing, budget, or priority the blocker rather than the pursuit itself?
Tie the failure to one actionable cause before repairing anything. Use evidence from the seller, the portal, the customer, and the account map.
Yes — Bad timing
Record the compelling event — repair, then re-enter
Owner · event · evidence
Re-enter at: Pursuit qualification
No — Not bad timing
Is the customer evidence too weak — no champion, no confirmed buyer, no discovery commitment?
Tie the failure to one actionable cause before repairing anything. Use evidence from the seller, the portal, the customer, and the account map.
Yes — Weak evidence
Re-present the repaired pursuit — repair, then re-enter
New evidence · corrected owner · revised scope
Re-enter at: Cloud seller pre-wire
No — Not weak evidence
Is the consumption case or the differentiation too weak to justify seller time?
Tie the failure to one actionable cause before repairing anything. Use evidence from the seller, the portal, the customer, and the account map.
Yes — Weak economics
Does customer demand support the rescoped production case?
Production value, cloud use, and services scope are credible
Yes — Rescoped
Re-present the repaired pursuit — repair, then re-enter
New evidence · corrected owner · revised scope
Re-enter at: Cloud seller pre-wire
No — Withdraw
Withdraw the pursuit — ends here
Fit not restored
No — Incumbent or trust gap
Can you define a distinct delivery role the seller will accept alongside the incumbent?
The seller accepts the role or the pursuit is withdrawn
Yes — Distinct role defined
Re-present the repaired pursuit — repair, then re-enter
New evidence · corrected owner · revised scope
Re-enter at: Cloud seller pre-wire
No — Withdraw
Withdraw the pursuit — ends here
Fit not restored
No — Owner unknown
Was the registration accepted and routed to a field owner?
The record is valid and the correct field owner can engage
Yes — Routed
Did the seller explicitly accept ownership, the partner role, and a next customer action?
Seller confirms ownership, partner role, support, and customer action
Yes — Accepted
Did the design pass production review?
The design is production-ready or the repair scope is explicit
Yes — Pass
Are you seeking Google Cloud funding for a proof activity?
Technical approval, cloud route, services scope, procurement, attribution path, and customer approval align
Yes — Funding sought
Does the activity clear funding pre-qualification?
Pre-qualify eligibility before presenting funding to the customer. Customer demand, sponsor, workload, success measure, and a production conversion all have to exist.
Yes — Request funding
Was the request approved as submitted?
Preserve the pursuit only when customer value survives the funding decision.
Yes — Approved
Did the customer approve production scope after the proof?
The customer approves production scope or documents the failure
Yes — Convert
Is there an eligible marketplace offer for this transaction?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Marketplace
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Not marketplace
Can it close on direct or existing cloud terms?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Direct or existing
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Blocked
Resolve route or eligibility — repair, then re-enter
Offer · agreement · legal · commitment
Re-enter at: Procurement choice
No — Repair the proof
Resolve the conversion failure — repair, then re-enter
Measure · sponsor · scope · procurement
Re-enter at: Measured activity
No — Not approved
Was it approved at a reduced size?
Preserve the pursuit only when customer value survives the funding decision.
Yes — Resized
Did the customer approve production scope after the proof?
The customer approves production scope or documents the failure
Yes — Convert
Is there an eligible marketplace offer for this transaction?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Marketplace
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Not marketplace
Can it close on direct or existing cloud terms?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Direct or existing
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Blocked
Resolve route or eligibility — repair, then re-enter
Offer · agreement · legal · commitment
Re-enter at: Procurement choice
No — Repair the proof
Resolve the conversion failure — repair, then re-enter
Measure · sponsor · scope · procurement
Re-enter at: Measured activity
No — Not resized
Will the customer fund the activity themselves?
Preserve the pursuit only when customer value survives the funding decision.
Yes — Customer-funded
Did the customer approve production scope after the proof?
The customer approves production scope or documents the failure
Yes — Convert
Is there an eligible marketplace offer for this transaction?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Marketplace
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Not marketplace
Can it close on direct or existing cloud terms?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Direct or existing
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Blocked
Resolve route or eligibility — repair, then re-enter
Offer · agreement · legal · commitment
Re-enter at: Procurement choice
No — Repair the proof
Resolve the conversion failure — repair, then re-enter
Measure · sponsor · scope · procurement
Re-enter at: Measured activity
No — Not customer-funded
Is there a compelling event worth deferring to, with demand still intact?
Preserve the pursuit only when customer value survives the funding decision.
Yes — Deferred
Defer until compelling event — repair, then re-enter
Eligibility · timing · evidence
Re-enter at: Funding choice
No — Exit
Exit when demand depends on funding — ends here
No customer-backed route
No — Proceed without funding
Is there an eligible marketplace offer for this transaction?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Marketplace
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Not marketplace
Can it close on direct or existing cloud terms?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Direct or existing
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Blocked
Resolve route or eligibility — repair, then re-enter
Offer · agreement · legal · commitment
Re-enter at: Procurement choice
No — Direct close
Is there an eligible marketplace offer for this transaction?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Marketplace
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Not marketplace
Can it close on direct or existing cloud terms?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Direct or existing
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Blocked
Resolve route or eligibility — repair, then re-enter
Offer · agreement · legal · commitment
Re-enter at: Procurement choice
No — Rework
Revise the production design — repair, then re-enter
Architecture · security · data · scope
Re-enter at: Technical validation
No — Declined or silent
Did the seller never respond at all?
Tie the failure to one actionable cause before repairing anything. Use evidence from the seller, the portal, the customer, and the account map.
Yes — Seller silent
Re-present the repaired pursuit — repair, then re-enter
New evidence · corrected owner · revised scope
Re-enter at: Cloud seller pre-wire
No — Not seller silent
Did it reach the wrong account owner?
Tie the failure to one actionable cause before repairing anything. Use evidence from the seller, the portal, the customer, and the account map.
Yes — Wrong owner
Re-present the repaired pursuit — repair, then re-enter
New evidence · corrected owner · revised scope
Re-enter at: Cloud seller pre-wire
No — Not wrong owner
Does an existing pursuit already own this opportunity?
Tie the failure to one actionable cause before repairing anything. Use evidence from the seller, the portal, the customer, and the account map.
Yes — Duplicate
Attach and preserve contribution — repair, then re-enter
Merge records · classify role
Re-enter at: Linked opportunity governance
No — Not duplicate
Is the customer's timing, budget, or priority the blocker rather than the pursuit itself?
Tie the failure to one actionable cause before repairing anything. Use evidence from the seller, the portal, the customer, and the account map.
Yes — Bad timing
Record the compelling event — repair, then re-enter
Owner · event · evidence
Re-enter at: Pursuit qualification
No — Not bad timing
Is the customer evidence too weak — no champion, no confirmed buyer, no discovery commitment?
Tie the failure to one actionable cause before repairing anything. Use evidence from the seller, the portal, the customer, and the account map.
Yes — Weak evidence
Re-present the repaired pursuit — repair, then re-enter
New evidence · corrected owner · revised scope
Re-enter at: Cloud seller pre-wire
No — Not weak evidence
Is the consumption case or the differentiation too weak to justify seller time?
Tie the failure to one actionable cause before repairing anything. Use evidence from the seller, the portal, the customer, and the account map.
Yes — Weak economics
Does customer demand support the rescoped production case?
Production value, cloud use, and services scope are credible
Yes — Rescoped
Re-present the repaired pursuit — repair, then re-enter
New evidence · corrected owner · revised scope
Re-enter at: Cloud seller pre-wire
No — Withdraw
Withdraw the pursuit — ends here
Fit not restored
No — Incumbent or trust gap
Can you define a distinct delivery role the seller will accept alongside the incumbent?
The seller accepts the role or the pursuit is withdrawn
Yes — Distinct role defined
Re-present the repaired pursuit — repair, then re-enter
New evidence · corrected owner · revised scope
Re-enter at: Cloud seller pre-wire
No — Withdraw
Withdraw the pursuit — ends here
Fit not restored
No — Correction required
Correct and reroute — repair, then re-enter
Fields · evidence · ownership
Re-enter at: Google Cloud opportunity record
No — No fit
Disqualify and reallocate — ends here
No fit · no demand · no production path
No — Field-routed
Did the design pass production review?
The design is production-ready or the repair scope is explicit
Yes — Pass
Are you seeking Google Cloud funding for a proof activity?
Technical approval, cloud route, services scope, procurement, attribution path, and customer approval align
Yes — Funding sought
Does the activity clear funding pre-qualification?
Pre-qualify eligibility before presenting funding to the customer. Customer demand, sponsor, workload, success measure, and a production conversion all have to exist.
Yes — Request funding
Was the request approved as submitted?
Preserve the pursuit only when customer value survives the funding decision.
Yes — Approved
Did the customer approve production scope after the proof?
The customer approves production scope or documents the failure
Yes — Convert
Is there an eligible marketplace offer for this transaction?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Marketplace
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Not marketplace
Can it close on direct or existing cloud terms?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Direct or existing
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Blocked
Resolve route or eligibility — repair, then re-enter
Offer · agreement · legal · commitment
Re-enter at: Procurement choice
No — Repair the proof
Resolve the conversion failure — repair, then re-enter
Measure · sponsor · scope · procurement
Re-enter at: Measured activity
No — Not approved
Was it approved at a reduced size?
Preserve the pursuit only when customer value survives the funding decision.
Yes — Resized
Did the customer approve production scope after the proof?
The customer approves production scope or documents the failure
Yes — Convert
Is there an eligible marketplace offer for this transaction?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Marketplace
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Not marketplace
Can it close on direct or existing cloud terms?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Direct or existing
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Blocked
Resolve route or eligibility — repair, then re-enter
Offer · agreement · legal · commitment
Re-enter at: Procurement choice
No — Repair the proof
Resolve the conversion failure — repair, then re-enter
Measure · sponsor · scope · procurement
Re-enter at: Measured activity
No — Not resized
Will the customer fund the activity themselves?
Preserve the pursuit only when customer value survives the funding decision.
Yes — Customer-funded
Did the customer approve production scope after the proof?
The customer approves production scope or documents the failure
Yes — Convert
Is there an eligible marketplace offer for this transaction?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Marketplace
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Not marketplace
Can it close on direct or existing cloud terms?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Direct or existing
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Blocked
Resolve route or eligibility — repair, then re-enter
Offer · agreement · legal · commitment
Re-enter at: Procurement choice
No — Repair the proof
Resolve the conversion failure — repair, then re-enter
Measure · sponsor · scope · procurement
Re-enter at: Measured activity
No — Not customer-funded
Is there a compelling event worth deferring to, with demand still intact?
Preserve the pursuit only when customer value survives the funding decision.
Yes — Deferred
Defer until compelling event — repair, then re-enter
Eligibility · timing · evidence
Re-enter at: Funding choice
No — Exit
Exit when demand depends on funding — ends here
No customer-backed route
No — Proceed without funding
Is there an eligible marketplace offer for this transaction?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Marketplace
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Not marketplace
Can it close on direct or existing cloud terms?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Direct or existing
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Blocked
Resolve route or eligibility — repair, then re-enter
Offer · agreement · legal · commitment
Re-enter at: Procurement choice
No — Direct close
Is there an eligible marketplace offer for this transaction?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Marketplace
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Not marketplace
Can it close on direct or existing cloud terms?
Validate commitment treatment and offer eligibility before presenting assumptions to the customer.
Yes — Direct or existing
Is managed services being sold alongside implementation?
Scope, acceptance, dependencies, staffing, security, and production start are agreed
Yes — Managed services sold
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Implementation only
Are all contracts, approvals, and dependencies in place to authorize production?
Selected contracts, procurement, security, funding milestones, acceptance, and start align
Yes — Authorized
Did attribution verify — records current, identifiers linked, usage visible, partner contribution preserved?
Registration, billing, usage, and seller credit are separate checks. All four have to hold.
Yes — Verified
Does the next workload have a buyer, services value, customer evidence, and a production route?
Treat expansion as a new qualified pursuit, not an automatic extension.
Yes — Qualified
Ask for the account map — new pursuit begins
Earned by delivered, attributed consumption — not guaranteed
Re-enter at: Partner-sourced or self-sourced qualification
No — Not ready
Nurture the adjacent workload — repair, then re-enter
Event · owner · evidence
Re-enter at: Expansion ensure
No — Exception
Is production usage invisible in billing or telemetry?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Usage missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not usage missing
Are required identifiers missing from the record?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Identifier gap
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Not identifier gap
Do the opportunity records disagree across systems?
Identify the exact failed evidence check, then assign it to the owner who can correct the source system.
Yes — Record mismatch
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Partner role missing
Correct records and evidence — repair, then re-enter
Fields · identifiers · usage · role
Re-enter at: Attribution ensure
No — Dependency missing
Resolve the missing dependency — repair, then re-enter
Contract · approval · security · start
Re-enter at: Procurement choice
No — Blocked
Resolve route or eligibility — repair, then re-enter
Offer · agreement · legal · commitment
Re-enter at: Procurement choice
No — Rework
Revise the production design — repair, then re-enter
Architecture · security · data · scope
Re-enter at: Technical validation