User-Generated Company Loop
Align incentives so a community builds, uses, and distributes the product
- Difficulty
- Expert
- Time to result
- ~ongoing to results
- Steps
- 6
- Confidence
- 97%
A user-generated company extends the logic of user-generated content into the product itself. Community members contribute infrastructure, data, designs, or other productive inputs; receive an incentive for doing so; and can also become customers of what the network creates. The operating loop is community to product construction to customer participation and back to community. Because contributors hold an economic or practical stake, they also become motivated distributors and advocates. Unlike conventional community marketing, this process begins before product-market fit because the community is required to build and validate the product. The company must define a verifiable contribution, reward useful behavior, distribute resulting value fairly, and ensure the resulting network offers real utility beyond its incentive token.
Origin
Extracted from Marketing Against The Grain using Helium, Hivemapper, and Superlocal as examples of community-built products.
Core principles
- 01Community members can be builders and customers simultaneously
- 02Contributors need direct participation incentives
- 03Community involvement begins before product-market fit
- 04Value and revenue should be distributed to the people creating the network
- 05Aligned contributors become advocates without requiring constant persuasion
How to run it
- 1
Identify a distributable input
Choose an essential product input that many participants can supply, such as network coverage, mapped roads, local observations, designs, or materials.
Pro tip Favor inputs that become more useful as geographic or participant coverage increases.
Watch out Do not decentralize work that a centralized team can perform more efficiently without losing value.
- 2
Define verified contribution
Specify what counts as a useful contribution and how the system will validate it. Connect rewards to quality, uniqueness, or actual network use.
Pro tip Design fraud resistance before assigning monetary rewards.
Watch out Unverifiable activity invites gaming and destroys trust.
- 3
Align the incentive
Reward contributors with money, ownership, access, tokens, or revenue participation that reflects the value they create.
Pro tip Make the reward more valuable when the network becomes genuinely useful.
Watch out Speculation cannot substitute for sustainable product demand.
- 4
Convert builders into customers
Let contributors use the product they helped construct. Their dual role should produce feedback and reveal whether the network solves a real problem.
Pro tip Track product usage separately from reward-claiming behavior.
Watch out A network of contributors without customers is not a functioning company.
- 5
Build community before fit
Recruit and collaborate with participants early because their contributions are part of the product-development process. Use their behavior to refine the value proposition.
Pro tip Start with a concentrated community where density can create immediate utility.
Watch out Premature geographic expansion can create a large but unusable network.
- 6
Reinvest the network effect
Use increasing coverage, data, or inventory to attract more customers and contributors. Share enough of the resulting value to preserve alignment.
Pro tip Publish transparent contribution and reward rules.
Watch out Centralizing the upside after relying on community labor breaks the loop.
In the wild
Participants install wireless routers and earn network tokens when their equipment supplies useful coverage. They can also use the resulting network, while broader coverage attracts additional users and hosts.
→ The community builds physical network infrastructure that would otherwise require large centralized capital expenditure.
Drivers mount dash cameras that record roads during normal journeys. Verified mapping contributions earn rewards, and the accumulated data becomes a map product that contributors and other customers can use.
→ Routine participant activity creates and refreshes a distributed mapping dataset.
Common mistakes
Building a token before utility
A reward mechanism cannot sustain a product that customers do not need.
Treating contributors as free labor
The model depends on distributing meaningful value to those who build the network.
Waiting until after product-market fit
When community contributions constitute the product, community formation must begin during product development.
Is it for you?
Best for
It is best for network products where distributed participants can supply infrastructure, data, designs, inventory, or local coverage.
Not ideal for
It is not ideal when user contributions cannot be verified, create regulatory risk, or add little value to the finished product.
From the transcript
“It's how do I get people to actually build the product itself through incentives?”
“we're really going from community to build in the product to customer, right?”
“But now community is part of how you get product market fit.”
From the episode
Twittersode! Licensing Bored Apes, A Crazy Franchise Story and The Role of AI in Creativity