Cooperation Between Entrepreneurs
Entrepreneurs can create more together than alone, but cooperation only stays healthy when responsibility remains clear.
DKWS helps entrepreneurs work together without hidden claims, vague expectations or silent pressure.
Cooperation may involve shared projects, referrals, commissions, joint purchasing, shared sales, temporary support, client distribution, operational help, Source Space, or the use of each other’s network, knowledge, materials, tools or Carrying Capacity.
Within DKWS, cooperation is not treated as vague goodwill.
When people work together, something is being carried: time, attention, responsibility, risk, money, reputation, access, execution, continuity, Source Space or Carrying Capacity.
That is why cooperation must remain visible and discussable before it becomes too heavy.
Practical Cooperation Without Hidden Claims
DKWS creates space for entrepreneurs to work together in a clear, practical and responsible way.
Cooperation may involve shared projects, referrals, commissions, joint purchasing, shared sales, temporary support, client distribution, operational help, Source Space, shared logistics or the use of each other’s network, knowledge, materials or capacity.
Within DKWS, cooperation should not become a soft way to claim what someone else has built.
A proposal may invite cooperation.
It may not silently create ownership, control or entitlement.
Where cooperation begins, DKWS helps ask what is actually being carried, by whom, under which conditions, and with what kind of Return Flow.
A Client is not Automatically Collective
A client, opportunity or project does not automatically become collective property simply because it enters the DKWS field.
When an entrepreneur brings in a client, relation, lead, opportunity or project, that original client line remains visible until something else is clearly agreed.
This protects the person who built the relationship, opened the door or carried the first responsibility.
Shared cooperation is possible, but it must be agreed, not assumed.
A client line may become more shared over time, but only when responsibility, contribution, Field Trust and Return Flow grow with it.
Shared Earning Requires Shared Carrying
.DKWS recognises that entrepreneurs may earn together.
But shared earning only becomes fair when shared carrying is also clear.
Before a client, project or opportunity is treated as shared, the following questions should be made visible:
- Who brought the client or opportunity in?
- Who carries the relationship?
- Who is the main point of contact?
- Who performs the work?
- Who carries financial, operational or reputational risk?
- Who invests time, materials, network or preparation?
- Who provides infrastructure, tools, space, stock, Source Space or coordination?
- Who carries continuity after the first movement?
- What Context Weight is present?
- How will payment, recognition, Lumen or Return Flow be divided if applicable?
- What happens if the cooperation changes, pauses or ends?
These questions are not meant to create distrust.
They prevent confusion from becoming conflict later.
Shared earning without shared carrying can create Air Value, pressure or unfair extraction.
Forms of Cooperation
Cooperation between entrepreneurs within DKWS may include:
- referrals
- commission agreements
- temporary project support
- shared service delivery
- joint purchasing or sales
- shared logistics
- client handover or client distribution
- shared preparation, planning or execution
- Source Space
- access to network, space, materials, tools or Carrying Capacity
Each form of cooperation can be valuable, but each form carries different responsibilities.
A referral is not the same as execution.
Execution is not the same as client ownership.
Bringing a client in is not the same as carrying all future responsibility.
Helping once is not the same as becoming permanently attached to a project.
Providing Source Space is not the same as giving unlimited access to a source.
DKWS makes these differences visible.
No Silent Takeover
Where the phrase “this client is ours” is used without clear agreement, there is a risk of silent takeover.
DKWS does not allow cooperation to become a soft way of taking over what someone else has built.
At the same time, DKWS does not lock every client or opportunity into one person forever.
A client line can become more shared over time, but only when responsibility, trust, contribution, Field Trust and Return Flow grow with it.
The purpose is not possession.
The purpose is fair carrying.
No party should use cooperation to claim Source Space, clients, future work or Return Flow without carrying the responsibility connected to it.
Larger Carriers and Clear Limits
In some cooperations, one entrepreneur or party may carry more than others.
This may happen when someone brings the client, provides stock, opens Source Space, pays costs upfront, carries operational risk, offers infrastructure, coordinates the project or protects continuity.
Carrying more may create more Context Weight within that specific cooperation.
But carrying more does not create ownership over the whole field.
It also does not give one party unlimited control over other entrepreneurs, client lines, Source Space or future movement.
Within DKWS, greater carrying must remain visible, explainable and bounded.
The question is not who is the biggest.
The question is what is actually being carried, where the limits are, and what Return Flow is fair within that specific context.
A heavier role means more responsibility, not higher human value.
Cooperation Must Stay Workable
Good cooperation does not require everyone to do the same amount of work.
It does require that differences are visible.
One person may bring the client.
Another may carry the execution.
Another may provide materials, space, transport, preparation, Source Space or specialist knowledge.
Another may carry risk, administration, communication or follow-up.
DKWS does not force these contributions into one fixed formula.
It helps participants see what is actually being carried, so agreements can match reality.
Cooperation stays workable when Carrying Capacity, Source Boundaries and Return Flow remain clear enough to carry the movement.
Return Flow and Carrying Capacity
Return Flow should stay connected to what is actually carried.
A person who brings a lead may deserve recognition or a referral return.
A person who performs the work may deserve operational return.
A person who carries cost, risk, tools, space, infrastructure, stock, preparation, Source Space or responsibility may deserve a different form of Return Flow.
A person who maintains the client relationship over time may carry continuity that should remain visible.
Lightpoints may help recognise contribution.
The Field Log may preserve context.
Draagwaarde / Carrying Value may show where recognised contribution also carries practical weight.
DKWS helps clarify whether that Carrying Value can support Return Flow, payment, Lumen or another form of exchange.
Where Lumen are involved, they may only move where practical exchange is supported by context, Field Trust, Source Space, Carrying Capacity and Return Flow.
Field Trust Between Entrepreneurs
Field Trust is rooted in the Dutch term Veldvertrouwen.
Between entrepreneurs, Field Trust grows when contribution, risk, Source Space, client lines, responsibility and Return Flow remain readable.
Field Trust weakens when roles become vague, when one party silently carries more than agreed, or when another party receives more than it actually carried.
Field Trust also weakens when Lumen are expected without Carrying Capacity, or when Source Space is treated as if it can be claimed.
DKWS protects cooperation by making the carrying visible before trust is damaged.
Where Field Trust becomes weak, Source Space may naturally become less available.
Core principle
Cooperation becomes clear when contribution, responsibility, risk, cost, client relation, Source Space and Return Flow are visible before the work begins.
DKWS supports cooperation between entrepreneurs, but it does not romanticise it.
Working together can create more value than working alone, but only when contribution, risk, responsibility, cost, client relation, Source Space and Return Flow are not hidden.
A client line may be shared.
A project may be shared.
Revenue may be shared.
Lumen may move where the DKWS conditions are clear enough.
But within DKWS, shared earning always asks one question first:
Who is carrying what?
What DKWS Should Prevent in Cooperation
DKWS should help prevent:
- silent takeover
- unclear client claims
- vague commission expectations
- shared earning without shared carrying
pressure after the fact - Source Space being claimed without consent
- Return Flow being disconnected from what was actually carried
- one entrepreneur becoming the invisible buffer for others
- Lumen movement without Carrying Capacity
- Air Value
- Source Depletion
- Essence Extraction
Cooperation should remain practical, voluntary and clear.
It should not become a hidden ownership model.
It should not become a soft way to control another entrepreneur’s client line, source, network or future movement.
In Essence
DKWS helps entrepreneurs cooperate without hidden claims.
It protects client lines, makes roles visible, and keeps Return Flow connected to real carrying.
It does not make every opportunity collective by default.
It does not let the strongest party quietly take over.
It does not turn goodwill into vague obligation.
It does not allow Lumen to move without Carrying Capacity.
An entrepreneur or party may carry more within a specific cooperation, but that weight must remain contextual, explainable and bounded.
A heavier role may carry more Context Weight.
It does not create higher human value.
Cooperation becomes healthier when contribution, responsibility, risk, cost, client relation, Source Space, limits and Return Flow are clear enough to be discussed before imbalance grows.