JwumaOwned delivery sites versus marketplaces, where the quality difference comes from
· 2 min read · procurement, supply model
A marketplace matches your task to whoever is available; an owned site runs it with employed staff at premises the supplier controls. The difference shows up in consent handling, workforce continuity and whether anyone can answer questions about how a specific item was produced six months later.
The short version
- Marketplaces optimise for supply elasticity; owned sites for continuity.
- Consent and provenance are materially easier to control at owned sites.
- Marketplace annotator churn erodes accumulated project knowledge.
- Marketplaces are genuinely better for sudden large-volume simple tasks.
- Corpshore operates owned sites with employed local teams across its markets.
Scoping something like this?
We would rather talk about the problem than quote against a volume figure.
See capabilitiesWhat actually differs structurally?
Who the worker's relationship is with. On a marketplace it is transactional and per-task; at an owned site the person is employed, trained and still there next quarter.
That single difference propagates into everything else. Continuity means accumulated project knowledge. Employment means enforceable process, including on consent and residency. Premises mean physical control over what devices touch the data.
Where does marketplace churn actually hurt?
On anything with a learning curve. A rubric with fifty edge cases takes real time to internalise, and a workforce that turns over every few weeks pays that cost repeatedly and never gets past it.
It shows up as agreement scores that plateau below where they should, and as recurring defects in the same slices, because the person who learned that slice has gone.
When is a marketplace genuinely better?
When you need large volumes of simple, unambiguous work quickly and the learning curve is shallow. Elastic supply is a real advantage and it would be dishonest to pretend otherwise.
If your task can be explained completely in a page and judged unambiguously, marketplace economics are hard to beat. The argument for owned sites is about tasks where that is not true.
- Marketplace: high volume, shallow learning curve, elastic demand
- Owned site: complex rubrics, regulated data, sustained programmes
- Owned site: where consent and residency must be enforced
- Either: as long as you know which problem you have
People also ask
Are owned delivery sites better than marketplaces for AI data?
For complex rubrics, regulated data and sustained programmes, yes, because continuity and enforceable process matter. For high-volume simple work with a shallow learning curve, marketplace elasticity is a genuine advantage.
Why does annotator churn affect data quality?
Because complex rubrics take time to internalise. A workforce that turns over quickly repeatedly pays the learning cost and never gets past it, which shows up as agreement plateauing below where it should.
Does Corpshore use a marketplace model?
No. Corpshore operates owned sites with employed local teams, which is what makes consent handling, data residency and workforce continuity enforceable rather than contractual.