Skip to the diagram
07 / 08Commercial and delivery architecture · proposed

The emerging international network

The proposed seventh arm connects customers, commercial originators, independent specialists and firms around work with clear responsibility.

INTENT SOLUTIONS / THE PROPOSED NETWORK

ONE ENGAGEMENT · SELECTED ROLES, EXPLICIT AUTHORITY, DEFINED RESPONSIBILITY
ARRANGEMENT FOLLOWS CONTRIBUTION · COMMERCIAL MODELS TO VALIDATE
The emerging international network — relationshipsCustomers, originators and delivery specialists interact through an Intent coordinating layer inside one engagement boundary. Below them are three families of possible arrangements. The model is proposed, participants may hold multiple roles, and independent business remains outside the boundary. scope evidence context alignment scope deliveryscope evidence context alignment scope delivery

Problems · constraints · outcomes

Customers

Bring the operating context and the authority to define and accept the work.

  • Business owner · success criteria

Relationships · discovery · presales

Origination

Develop qualified opportunities and clarify why the work matters.

  • Referrals and customer relationships
  • Domain context and commercial judgment
  • Contribution documented per engagement

Coordination and accountability

Intent operating layer

Assemble the engagement and make responsibilities inspectable.

  • Qualification · agreements · architecture
  • Shared tooling · review · quality assurance
  • Customer responsibility · operations
Proposed model

Engineers · specialists · firms

Execution

Bring capable people, relevant assets and an agreed delivery commitment.

  • Implementation and technical judgment
  • Independent individuals or companies
  • Scope and capacity confirmed for the work

Opportunity contribution

Referral or presales

Define the opportunity, attribution and responsibility.

Proposed model

Delivery contribution

Subcontract or joint delivery

Define parties, scope, acceptance and risk allocation.

Proposed model

Ongoing responsibility

Managed work and support

Define ownership, service boundaries and the exit path.

Proposed model

Participants may hold multiple roles. Joining the network does not assign unrelated customers, business or intellectual property to Intent.

Intent must earn its role through identifiable value. Each engagement defines who contributes, who contracts and who answers for the outcome.
Work / artifact flowFeedbackControl / shared supportProposed boundarySelect a node to trace its connections.

What Intent has to contribute

The coordinating layer has to provide something the engagement needs. Its role can combine opportunity development, architecture, reusable engineering, contractual accountability, quality control and operations.

  • Identify the contribution before setting the arrangement.
  • Name the customer-facing accountable party for that engagement.
  • Avoid a universal claim that Intent owns every independent relationship.

International by design, explicit in execution

Independent people and firms can operate across countries, but a shared vision does not settle the legal form of their relationship. Geography, entity type and the actual work shape the appropriate arrangement.

  • Confirm jurisdiction, entity status and authorized signers.
  • Resolve IP, confidentiality, security and liability for the scope.
  • Use legal review to support the chosen commercial model.

What still needs validation

The network is a business model being developed. Repeatable customer acquisition, committed capacity, workable incentives and sustainable delivery economics must be established through actual engagements.

  • Choose a narrow initial offer and customer segment.
  • Prove one complete engagement and its operating responsibility.
  • Measure margin after delivery, coordination, support and risk costs.
  • Expand only from evidence about demand, delivery and contribution.

Commercial hypotheses to test

These are possible arrangements, not published offers or agreed terms. A signed engagement must identify the payer, deliverer, responsibility, costs and acceptance conditions.

ArrangementPossible payerWho contributesWhat Intent must addEvidence before expansion
Referral / originationContracting partyRelationship holderQualification and an attributable opportunityAttribution, conversion and acquisition cost
Presales / discoveryCustomer or delivery leadDomain and solution specialistsA usable scope and an accountable handoffDiscovery cost, acceptance and delivery fit
Subcontract / joint deliveryCustomer or lead contractorIndependent engineers or firmsArchitecture, coordination, QA or contract accountabilityCapacity, acceptance, cost and risk allocation
Managed deploymentCustomerDelivery team and operating ownerAn integrated outcome with a response and exit pathOperational evidence and sustainable support cost
Paid supportProduct or system userNamed support providerA defined maintenance or response responsibilityDemand, service boundaries and delivery cost
Technical educationLearner or sponsoring organizationPractitioners and instructorsIndependent learning value and practical feedbackLearning outcomes, delivery cost and permitted offer
Software subscriptionProduct customerProduct engineering and operationsA maintained solution to a repeated problemRetention, operating cost and willingness to pay
Read the relationships as text

Customers, originators and delivery specialists interact through an Intent coordinating layer inside one engagement boundary. Below them are three families of possible arrangements. The model is proposed, participants may hold multiple roles, and independent business remains outside the boundary.

  • Customers → Intent operating layer: scope (flow)
  • Intent operating layer → Customers: evidence (feedback)
  • Origination → Intent operating layer: context (flow)
  • Intent operating layer → Origination: alignment (feedback)
  • Intent operating layer → Execution: scope (flow)
  • Execution → Intent operating layer: delivery (feedback)

Basis and scope

Reviewed 2026-10-11. Public links support the named properties and capabilities. The relationships explain the operating method and owner-directed vision; they do not imply that every initiative is deployed or commercially proven.

Mermaid sourceComplete source graphWorkshop PDFPrint view