There is a well-documented cognitive bias called the IKEA effect: people disproportionately value products they partially created. Researchers found subjects were willing to pay 63% more for furniture they assembled themselves than for equivalent pre-assembled items.
This applies directly to agent tooling. When a developer builds a workflow agent — scopes it, customizes it, iterates on it — they care about it. They want to improve it. They feel ownership over it. Compare that to a vendor-provided agent that does something generically: the developer has no attachment, no investment, and no motivation to make it better.
Platforms that lean into this dynamic — that make developers feel like the agents are theirs — generate far more engagement, far more iteration, and far more production value than the ones that ship pre-built agents and hope for adoption.
This extends to end users too. When the customer success team can submit ideas for how the agent should prioritize their work — when they can say "I want to see my ten highest-revenue accounts with no touch in the last two weeks" and watch that become a real capability — they are invested. They are co-building the system. That is a fundamentally different relationship than being handed a tool and told to use it.
The lesson for anyone building an agent platform is uncomfortable: do not over-finish the product. Leave room for the developer and the end user to put their hands on it. I've argued elsewhere that the moat sits in customization, not model quality, and the IKEA effect is the human side of that same argument. People defend what they helped build. Ship the assembly instructions, not the finished bookshelf.
Related Essays
Users Should Iterate on Agents, Not Developers
Agents are always slightly wrong when first built. The people who know what is wrong are not developers — they are the users who interact with the agent every day.
Customization Is the Moat, Not Model Quality
Frontier labs want workflow quality to be a function of model quality, because that is what they sell. The contrarian bet is that customization beats probability.
The Coordination Crisis AI Tooling Created
When everyone can build, nobody knows what has already been built. Five teams independently spin up the same Slack bot, and the duplication goes undetected for months.
Key takeaways
- The IKEA effect — people overvalue what they help create — applies directly to agent tooling.
- Developers who scope, build, and iterate on their own workflow agents care about them and keep improving them.
- End users who can submit prioritization rules become co-builders, not passive recipients.
FAQ
What is the IKEA effect?
A documented cognitive bias where people disproportionately value products they partially created. In one study, subjects were willing to pay 63% more for furniture they assembled themselves than for equivalent pre-assembled items.
How does this change platform design?
Lean into the dynamic. Make it easy for developers to scope, build, and iterate on their own agents. Make it easy for end users to submit ideas that turn into real capabilities. Both groups become invested in a way that vendor-shipped agents never replicate.