DEV Community

loading...

Just because you can build something doesn't mean you should

happydragos profile image Dragos Bulugean ・1 min read

I could probably write a small book on the mistakes I've made in my first year as an entrepreneur.

Most of them come from the fact that I am an engineer at core, and my obsession with exhaustiveness. It's excellent to have as an engineer, really bad to have as a founder.

I wanted to silo the product from other products. Because I thought most of their features could be bundled into one and made better this way.

I've learned the hard way that: just because you can build something doesn't mean you should.

It will be harder to maneuver & pivot in the long run. Harder to market and sell a bunch of things put together. Harder to pitch to pre-seed level investors. Harder to network. Just harder overall, and for no good reason.

I am starting to correct it though. Yesterday I released 21 integrations for Archbee.

GraphQL, Swagger, Github Gist, Numeracy, Codepen, Mode Analytics, Slack, Airtable, Trello, LucidChart, Typeform, Mindmaster, Prezi, Miro, Invision, Figma, Framer, Abstract, Marvel, Google Analytics, Intercom.

Check them out right here: Archbee Integrations

No product is an island, the power of the ecosystem is huge. Why not benefit from it and at the same time make it better? Win-win.

I am curious and willing to learn from other people's mistakes as well. What mistakes did you make and what steps did you take to correct it?

Let me know down below!

Discussion (0)

pic
Editor guide