Sean Doherty’s Post

View profile for Sean Doherty, graphic

Zeplin VP WW Sales, Ex-Red Hat, Ex-NGINX, Ex-EnterpriseDB

Timeless dilemma: Build versus Buy There are always conversations during the sales cycle where a prospect brings up the possibility of building their own tool instead of buying yours--in fact, that topic may come up during pricing conversations. Building is *never* less expensive. That doesn't mean it's not the right option for you to choose. It means the reason you choose building shouldn't be for cost savings. If good software solutions were so easy to build, then software companies wouldn't exist. Tons of work goes in to: - user experience - features - ability to scale - integrations with other tools - compatibility - flexibility - security - ease of administration - updates, bug fixes, patches, general support When companies build a tool that's outside of their core competency, there's also opportunity cost. What would those employees be doing if they weren't working on building some other tool? What value could they have added to your product? Enhancing any of the bullet points I described above, likely. There's also lost time. You can have your solution now, or you can take 6,12,18 months to build your own....delaying any benefit that solution would provide. If you're a hobbyist, you'll spend your time and money on supplies to, say, build your own chair, or maybe knit your own blanket. You're gaining value that is more than the object itself. You're getting joy in the creation. Businesses, to be clear, is not a hobby. You want your teams to get value and joy from their work, for sure. The trick is to help them get that value and joy in a way that can also benefit your customers. When is building your own tool the best way forward? Please add your suggestions to the comments!

  • No alternative text description for this image

To view or add a comment, sign in

Explore topics