Collaborative agency models and contributor equity

By Marco Lopes · June 21, 2025 · Business & Culture

At Kordspace, we work across software, AI, Web3, hardware, and design as a remote collaborative studio. That combination brings an ownership question into focus: when value comes from a network of contributors, how should the rewards follow?

Traditional agency structures offer a straightforward answer. Owners hold equity, employees receive salaries, and contractors invoice for their work. Collaborative models open up more possibilities, but they also introduce ambiguity around responsibility, compensation, and control.

We think the goal should be neither ownership for everyone by default nor ownership reserved indefinitely for whoever arrived first. We need arrangements that connect contribution, risk, and long-term responsibility without making everyday work unnecessarily complicated.

Start with the collaboration model, not the cap table

Before discussing percentages, we need to decide what kind of organisation we are building.

A contractor network can assemble specialist teams while leaving ownership and accountability with a central studio. A partnership can give a smaller group shared responsibility for revenue, delivery, and governance. A worker cooperative can distribute member ownership under an appropriate legal structure. A venture studio can retain a core operating business while creating separate companies for selected products.

These models solve different problems. We should not choose a cooperative simply because collaboration sounds cooperative, or a venture studio because equity sounds more exciting than service revenue.

Our starting questions are practical: who signs the client contract, who covers a shortfall, who maintains the work after launch, and who can commit the organisation to future obligations? Until we can answer those questions, an equity discussion is mostly a discussion about expectations.

Separate payment, upside, and authority

We find it useful to separate three things that often get bundled together:

• Payment: compensation for work performed and expenses incurred.
• Upside: participation in future profits, distributions, or enterprise value.
• Authority: the right to make or influence decisions.

A contributor can receive all three, but they do not have to arrive in identical proportions. A specialist might earn a project fee and a defined success bonus without taking on studio governance. A long-term operator might receive ownership alongside responsibility for staffing, cash flow, and delivery quality.

Equity should not disguise an inability or unwillingness to pay. Where we discuss reduced cash compensation in exchange for potential upside, we need to make the risk explicit, respect applicable employment and wage rules, and recognise that some contributors cannot afford that trade-off.

We should also ask whether equity is necessary. A well-defined cash bonus or profit-sharing arrangement can sometimes reward collaboration more directly.

Define what the contributor actually owns

“Contributor equity” can describe several very different arrangements. We need to name the instrument and the entity rather than rely on the label.

Actual shares or membership interests can provide economic ownership, subject to the entity's governing documents. Options generally provide a right to acquire ownership under specified conditions. Phantom equity typically creates a contractual payment linked to value without making the recipient a shareholder. Profit sharing allocates a defined portion of profits, while revenue sharing uses a different calculation base.

These distinctions affect taxation, voting, dilution, administration, and what happens when someone leaves. We should never describe a discretionary bonus as ownership or imply that a profit share automatically creates shareholder rights.

We also need to identify the asset. Is the contributor participating in the whole studio, one product company, or a specific revenue stream? A meaningful agreement makes that boundary understandable without requiring a contributor to decode a presentation.

Keep studio ownership separate from project economics

A successful engagement does not automatically justify permanent ownership in the agency. Equally, years spent developing the studio's capabilities should not disappear inside individual project margins.

We can separate these layers by using project-level incentives for bounded delivery contributions and studio-level ownership for sustained responsibility across engagements.

For a hypothetical connected-device project, we might assemble industrial design, firmware, cloud, and application specialists. Their agreement could combine fees with a clearly calculated delivery bonus. If the team later decides to commercialise a reusable product, that should trigger a separate discussion about intellectual property, funding, ownership, and ongoing obligations.

We should not assume that reusable work belongs to us simply because we built it. Client contracts, contributor agreements, third-party licences, and confidentiality commitments determine what can be retained or commercialised. Those boundaries need agreement before we promise anyone product upside.

Make contribution visible without turning it into a contest

Hours are easy to count, but they are an incomplete measure of value. A short architectural decision can prevent expensive rework. Documentation, mentoring, accessibility work, and release coordination can improve outcomes without producing an obvious headline deliverable.

We recommend defining contribution categories before work begins. These might include delivery, business development, reusable intellectual property, operational stewardship, capital at risk, and continuing maintenance.

For each category, we need evidence and an accountable reviewer. We can use accepted deliverables, decision records, documented responsibilities, and agreed milestones rather than popularity or whoever speaks most confidently in meetings.

We should also avoid pretending that a scoring spreadsheet makes ownership objective. Any weighting reflects judgement. Contributors need visibility into the method, a way to question errors, and protection against retroactive changes. If the calculation becomes harder to explain than the work itself, we should simplify it.

Put the economics in writing

A promise to share “the profits” leaves too much room for disagreement. We need a written formula that defines the relevant revenue, eligible costs, overhead allocation, reserves, payment timing, and treatment of refunds or unpaid invoices.

We should test the formula against several scenarios: a profitable delivery, a delayed client payment, an engagement requiring substantial rework, and an early cancellation. If the agreement produces a surprising result, we should resolve it before anyone relies on it.

For equity, we need the same discipline around the number or class of interests, the basis of any stated percentage, vesting, dilution, transfer restrictions, and potential liquidity events. An ownership percentage is not a guaranteed payout.

We should budget for qualified legal and tax advice. Cross-border arrangements can involve employment classification, securities, payroll, withholding, and reporting obligations that a generic template will not settle.

Use vesting to clarify long-term commitment

Vesting can connect ownership to continuing contribution, but we should design it around the actual relationship rather than copy a startup template automatically.

Time-based vesting may suit ongoing operational responsibility. Milestone-based vesting may suit a defined product contribution, provided acceptance criteria and approval authority are clear. A hybrid can address both delivery and continuing stewardship.

We need to explain what happens during reduced availability, parental leave, illness, role changes, and termination. We should distinguish unvested awards from vested ownership and describe any repurchase rights without implying that every departure is misconduct.

We also need a process for adjusting future grants when responsibilities change. A contributor who moves from occasional implementation to running a major practice may warrant a new agreement. We should document that change rather than quietly reinterpret an old promise.

Give governance a workable shape

Shared ownership does not require every decision to become a referendum. We need clear domains of authority so delivery teams can act while contributors retain meaningful protection.

We can delegate routine technical and project decisions to named leads, set spending limits, and reserve major matters for broader approval. Reserved matters might include issuing new equity, taking on substantial debt, selling core intellectual property, or changing distribution rules.

Where contributors have economic participation but no voting rights, we should say so plainly. We can still provide reporting, consultation, and a dispute process without suggesting that consultation is a binding vote.

We should also plan for deadlock and conflicts of interest. A governance agreement is most useful when people disagree, not when everyone already wants the same outcome.

Treat remote collaboration as an operating discipline

In a distributed studio, ownership needs supporting infrastructure. We cannot expect contributors to behave like owners while leaving them without context, access, or reliable records.

We recommend maintaining a shared decision log, written role definitions, a current ownership register, and financial reporting appropriate to each person's rights. Important decisions should move from chat into durable records with a responsible person and a review date.

We also need a distinction between transparency and unrestricted access. Contributor participation does not automatically justify access to client secrets, personal data, production credentials, or every commercial negotiation.

Async proposals can help us include people across time zones. We can publish a decision brief, allow a defined feedback window, and record the outcome. This gives contributors a practical voice without making constant meeting attendance the price of participation.

Account for technology-specific risks

Our mix of disciplines makes responsibility harder to reduce to a single delivery date. Hardware can carry inventory and warranty exposure. AI work can involve continuing evaluation, model costs, and data-rights questions. Software requires maintenance, security updates, and incident response.

We should reflect those obligations in project reserves and incentive calculations rather than distribute all apparent margin immediately.

With Google Cloud as our preferred cloud platform, and AWS or Azure where appropriate, we should make account ownership, billing responsibility, spending alerts, and handover explicit. Credits can reduce early costs, but they are not recurring revenue or evidence of sustainable margins.

For Web3 work, we should distinguish technical mechanisms from legal rights. A token or multisignature wallet does not, by itself, establish corporate ownership, settle tax treatment, or replace an enforceable contributor agreement. We need governance and recovery procedures that remain understandable outside the code.

Design the exit before anyone needs it

Collaborative arrangements become fragile when leaving is treated as betrayal. We should make departures predictable enough that contributors can move on without putting clients or the studio at unnecessary risk.

Our agreements should cover notice, work in progress, credential transfer, documentation, outstanding payments, vested interests, and continuing confidentiality obligations. Where a buyback is possible, we need a valuation method, payment terms, and clarity about who can exercise it.

We should not promise immediate liquidity unless we can actually provide it. Private-company ownership may remain illiquid for a long time.

We also need periodic reviews. A structure that works for a small group may become administratively expensive or unfair as responsibilities change. Reviewing the model is good stewardship, not evidence that collaboration has failed.

A short checklist before we offer contributor equity

• Identify the entity, instrument, and rights being offered.
• Separate cash compensation from speculative future upside.
• Define contribution expectations, vesting, and acceptance criteria.
• Document calculation methods, reporting, and payment timing.
• Confirm intellectual property and client-contract boundaries.
• Establish decision rights, conflict handling, and exit terms.
• Obtain jurisdiction-specific legal and tax advice before implementation.

We see collaborative ownership as a design problem grounded in trust, but sustained by clear agreements. The strongest model is one we can explain, administer, and honour when circumstances become difficult. If this approach fits what we could build together, we invite you to start a project, or explore our related services pages to see where software, AI, Web3, hardware, and design can support your next step.