<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Alexander Savelyev on Medium]]></title>
        <description><![CDATA[Stories by Alexander Savelyev on Medium]]></description>
        <link>https://medium.com/@alexandersavelyev_20262?source=rss-a41a236afb05------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*_JvGJoJn7ouoM3Z7.</url>
            <title>Stories by Alexander Savelyev on Medium</title>
            <link>https://medium.com/@alexandersavelyev_20262?source=rss-a41a236afb05------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 01:16:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alexandersavelyev_20262/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Developing in-house vs. using third party tools: 5 steps to help you decide & how to prioritise]]></title>
            <link>https://medium.com/@alexandersavelyev_20262/developing-in-house-vs-using-third-party-tools-5-steps-to-help-you-decide-how-to-prioritise-3ee11e21b49b?source=rss-a41a236afb05------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ee11e21b49b</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Alexander Savelyev]]></dc:creator>
            <pubDate>Thu, 07 Dec 2017 10:23:43 GMT</pubDate>
            <atom:updated>2017-12-14T09:23:10.972Z</atom:updated>
            <content:encoded><![CDATA[<p>It doesn’t matter if you are an individual developer starting to work on your first application, or if you’re a well funded startup with skyrocketing growth, your product owners will be often challenged with the question of <em>developing in-house</em> vs. <em>integrating a third party solution</em>. I was speaking about this challenge at the Product Manager Meetup in Hamburg last week, and as a result of the overwhelming feedback I got from attendees, I want to share a summary in the form of the blog post. This post covers the benefits of third party tools, advantages of development in-house, and provides an easy framework for decision-making when presented with both options.</p><p><strong>Why would you like to use 3rd party tools*?</strong></p><p>*It is important not to confuse development outsourcing and using third party tools — third party tools are ready-made solutions, whereas outsourcing is more comparable to in-house development from a resource allocation standpoint.</p><p>There are at least 6 points about using third party tools that you should keep in mind.</p><ol><li>Firstly, third party service is already developed service (even if it is in alpha/beta stages) and you can start using it right away. It is pretty easy to gather feedback about the service from the current users (e.g. your clients, trade shows and etc.).</li><li>Secondly, third party services are working with other companies (including your direct &amp; indirect competitors); they share best practices and offer a readymade solution for your problems (someone else out there has very similar challenges to yours). The service they offer is the core business for them.</li><li>Thirdly, third party tools are coming with a support services and integration supports. They have already integrated with similar products like yours and have analysed all the corner cases to provide smooth integration.</li><li>The fourth point is a pricing model that is usually reasonable, and often subject to negotiations (typically, the longer contract length or volumes you commit to, the cheaper it is).</li><li>Next, do not underestimate going through a testing mode. Do a proper check to get an accurate estimate of how scalable the solution is and how capable it is of addressing your needs. Testing options are often available.</li><li>Finally, do not forget that third party tools are quick wins for your business. Do not neglect the short cuts! Your competitors are already benefiting from them.</li></ol><p><strong>Why would you like to develop in-house?</strong></p><ol><li>For most, developing in-house would be the only option when there is no available solution in the market that answers your exact needs, or when the available tool only satisfies part of your needs (thus, you still need to fill the gap). Make sure that you do a proper research to cover it.</li><li>Secondly, development in-house would let you avoid unnecessary dependencies, inflexibility, and legacy features you don’t need. Third party tools require integration efforts from your side, and are typically not very flexible with additional tools you would like to use on top (e.g. internal monitor system).</li><li>Thirdly, in-house development allows you to avoid contract lock-in and allows for easier management of your cashflow.</li><li>Furthermore, you would own the technology. It would be possible to leverage it multiple times, e.g. by providing new services to your strategic partners, having additional USP and potentially, even a new business line.</li><li>Finally, the most important reason to develop in-house is flexibility and control to build on top of your products — that is what your own solution offers.</li></ol><p><strong>Examples</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/950/1*BUX32rfHWzckd84oyl-JmQ.png" /></figure><p>In my experience, it is pretty easy to find good and bad examples of when we developed something in-house or relied on the third party tools, and were pleased or unhappy with the results. While exact examples are not relevant at the moment, it is very important to note that in retrospect, I can clearly see product slackness and flaws.</p><p>One time, I spent ages integrating a third party tool that was not designed to solve even 25% of the most time-consuming tasks. Clearly, gathering detailed requirements and sitting hand-in-hand with stakeholders during the test phase would have helped a lot to avoid those mistakes.</p><p>Second, a “famous” case I recall was when the newest internal tool developed in-house produced so much data in first 2 days that it immediately became undigestible (producing 40k actionable rows). We had to switch it off by the end of the week and completely re-think the solution. The advice here is to think a few steps ahead and make sure that you have evaluated how the end user will interact with your product. It is pretty common for internal tools that their controls and functions are often under-researched, because they are not “client-facing”.</p><p>In terms of promising results, make sure to evaluate third party tools for the slice’n’dice data visualisation features. These are pretty sharp, and the only challenge I have experienced with them is the scalability issue (sometimes even resulting in a need to switch to an alternative product).</p><p><strong>N-(5 or less)-steps decision making</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/425/1*1n_D6-MILK40JLT2OIw7SA.png" /></figure><p>Going over the following 5 (or less) steps and asking relevant questions will help you make more accurate and data-driven decisions on whether to develop in-house or rely on the third party tools.</p><p><strong>Step 1</strong></p><p>This is a starting point for any evaluation. One should focus in-house resources (including development, knowledge, and research) on <strong>the</strong> <strong>core product</strong>, and use best practices and third party tools for <strong>all</strong> <strong>the supporting functions</strong> (operations team can be a great help here).</p><p>However, in reality, company or product needs can be so narrow, that there are simply no relevant third party tools available at the market yet, or when they are present they come at high monthly and integration costs. That is why you would need to go through the evaluation process. In my experience, it is a quite common product manager / product owner decision.</p><p><strong>Step 2</strong></p><p>Evaluate if your core product is <strong>able to pay for </strong>the third party tools and estimate the benefits from ready-made solutions.</p><p><em>Example</em>: there is a company offering a real-time reporting for your advertisers at the cost of $1000 per month. This feature would allow me to onboard 10 new advertisers per month for the foreseeable future. Each advertiser is generating $150 net profit for me per month. $1500-$1000=$500 of profit and $1500 in revenues that can be easily added to my business.</p><p><strong>Step 3</strong></p><p>If outcome of Step 2 is <em>no</em>, you should check what other alternatives there are. Is there any <strong>cheaper,</strong> maybe even <strong>more basic solutions</strong> that can solve 50% of problems? Can you <strong>split manual work</strong> between people in the team (so each one does 15 minutes a day and half of the problem is gone)? Can you hire a working student for this particular task? Have you reviewed <strong>free</strong> Google products?</p><p><strong>Step 4</strong></p><p>If outcome of Step 2 is <em>yes</em>, make sure to evaluate all <strong>hidden and indirect costs</strong>. Pay attention to the contract and additional fees, triple check i<strong>ntegration costs</strong>, evaluate upcoming <strong>maintenance costs</strong>, and evaluate scalability of the solution (would the tool still cover needs of your stakeholders <strong>in 3/6/12 months from now?</strong>).</p><p><strong>Step 5</strong></p><p>Do you know the true costs of developing in-house? Do you have the <strong>knowledge (technology wise) </strong>how to build what you need? Do you have the <strong>finalised requirements /</strong> <strong>roadmap / project timeline</strong>? Is the product <strong>homework</strong> done? Which features exactly are you <strong>deprioritizing </strong>because of this development? Is it <strong>OK with your stakeholders,</strong> do you have their sign off? Are the <strong>KPIs of success</strong> clear and agreed and timelined?</p><p><strong>Summing up</strong></p><p>Solely based on past experience, I would recommend everyone not to<strong> re-invent a wheel, </strong>and stick to the already pre-made receipts. My reasoning is very basic. You are experiencing challenges not related to your core business that prevent you from growing as fast as you want. There are companies out there offering you an affordable solution for your exact needs, companies for whom solving those very problems is a core business. If you are confident enough to believe that you can offer a better solution than presented at the market that can imply that this service would actually become your <strong>core product,</strong> and this is not the case. The motivation is simple: focus your resources on the where you can make the difference. You can always put your tech team to better use.</p><p><em>P.S. follow me on my new personal channel </em><a href="https://t.me/simhomer"><em>https://t.me/simhomer</em></a><em> if you like the article and would like to here more about product management and technologies that pique my curiosity</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ee11e21b49b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>