Who should own your D2C technology?

Knowledge Note

In most situations Cralgo has seen, the channel steadies once one person inside the organisation owns its outcome — even when most of the building happens outside.

One current Cralgo reading of this question — based on observed situations, repeated practice, and open to revision as context or evidence changes.

The current reading

• Ownership of an outcome and execution of the work are two different things, and only the first can be outsourced by mistake.
• Agencies can own delivery. They cannot own consequences.
• If no single name can be written next to revenue, availability and roadmap for the channel, the channel is unowned.
• Hiring a senior person does not create ownership; defining decision rights does.

What this usually looks like

Growth is real, the site works most days, and yet nobody can say who is accountable when it does not. Marketing asks the agency. The agency asks for a brief. The founder makes the final call on a Sunday evening.

The question is asked as a hiring question — in-house team, agency, or a senior hire — because that is the form the frustration takes. The frustration itself is about accountability.

• Symptom

  Every non-trivial decision escalates to the founder or the CEO.

• Symptom

  Priorities change depending on who spoke most recently.

• Symptom

  Incidents are resolved but never owned, so the same class recurs.

• Symptom

  The roadmap exists as a list of requests rather than a sequence of intent.

What is actually happening underneath

D2C is not one system. It is a chain: acquisition, storefront, catalogue, checkout, payments, order management, fulfilment, service, returns and the data that connects them. Each link often has a different owner, and several of those owners are external.

When the chain is split across vendors and internal functions, ownership defaults to whoever cares most — usually the founder. That is why the problem feels personal. It is structural.

The organisations that resolve it do not resolve it by insourcing everything. They resolve it by separating three things that had been collapsed into one: who decides, who builds, and who is accountable for the result.

Three ownership models, honestly compared

Model Works when Fails when What it costs you Agency-led The channel is young, scope is bounded, speed matters more than depth. The business starts depending on the channel and nobody internal can challenge the work. Institutional knowledge. It leaves with the contract. Fully in-house Volume, complexity and roadmap justify permanent capability across the whole chain. Hiring outruns the operating model, and you get a team without standards. Time. Twelve to eighteen months before it compounds. Owned inside, executed with partners Direction, standards and accountability sit internally; delivery capacity flexes. The internal owner is nominal and has no authority to say no. Discipline. It only works if decision rights are written down.

None of these is correct in general. Each is more useful under particular conditions, and the conditions change.

One way to examine this

Write the chain out — every link from first click to returned parcel. Against each link put one name for the decision and one name for the outcome. Not a team, not a vendor, a person.

Wherever the two names differ, or wherever a vendor's name appears in the outcome column, you have found the real problem. It is almost never in the same place people expected.

• Decision rights

  Who can approve, who must be consulted, and who is simply informed — per link, in writing.

• Standards

  What good looks like for performance, availability, data and release quality. Standards are what let you delegate safely.

• Escalation

  What triggers a decision moving up, and what returns it downwards afterwards.

What tends to change when ownership is explicit

The founder still cares about the channel and no longer arbitrates it. Vendors are held to standards rather than to opinions. The roadmap survives contact with a bad week.

Most importantly, capability stays with the organisation. When a partner changes, the operating model does not.

Deciding this month

Map the chain and assign two names per link. It takes an afternoon and it is usually uncomfortable, which is the point. You will not need anyone's permission to do it and you will learn more than a vendor review would tell you.

If ownership is unclear today

If the channel is early and one capable person can hold the whole chain in their head, formal ownership structures will slow you down. Revisit when a bad week costs more than a week of attention.

What this reading rests on

observed situations, repeated practice

Why it stays contextual

Organisations × Technology — the answer moves with the people and the environment, not only the technology.

What this note is not

A universal answer, a best-practice list, or evidence. It is a reusable reading that should be tested against your own situation.

What remains open

• Whether written decision rights hold the first time the founder disagrees with an outcome they have delegated.

What would change this reading

• Organisations where the chain is split across several vendors and accountability still holds without one internal owner.
• A stage or scale at which naming a single owner slows the channel down rather than steadying it.

Related reading at Cralgo

The D2C operating model Cralgo's fuller reading of how D2C organisations are structured. Centres of Excellence How ownership is made institutional rather than personal.

These informed the reading. They do not prove it.

Related Research

Questions Cralgo is currently exploring Open research questions, not conclusions.

Continue the reasoning

In-house, agency, or Centre of Excellence? Why does every technology decision come back to the founder? What a product and technology operating model actually is

This is a current reading, not a final answer.

Back to KnowledgeExplore related Research Work with Cralgo