I built 70+ API endpoints before talking to a single user. 80% of them never get called.
Classic developer mistake and I made it anyway even though I knew better.
we spent three months building before showing the product to anyone. the logic was "let's make sure it's solid first." so we built. and built. and built.
70+ endpoints. search, scraping, outreach, inbox management, analytics, CRM, webhooks, conversation history, profile enrichment, company data, post publishing, comment replies, reaction tracking. you name it, we probably built it.
Launch day came. people started using it.
turns out 80% of usage comes from maybe 10 endpoints. the other 60 endpoints exist. people just don't use them. some have never been called in production. not once.
the endpoints I thought were clever and differentiating? barely touched.
The boring ones I almost didn't bother building because they seemed too simple? used every single day.
the thing that stings: I knew about this pattern before I started. I had read about it. I had nodded along to the "build less, talk to users earlier" advice approximately one thousand times.
and then I built 70+ endpoints before talking to a single user.
I think what happens is that building feels like progress. every new endpoint is a thing you did, a box you checked, a feature you can put on the landing page. talking to users is uncomfortable and inconclusive and slow.
so you keep building because building is the part you're good at.
the fix for our next version: we're shipping with 10 endpoints. if someone needs something else, they ask, we build it in 24 hours, we see if anyone else asks for the same thing. if three people ask for the same feature it gets added to the core. everything else stays custom.
What's the feature you built that nobody actually uses?