<?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 Adam Przymusiała on Medium]]></title>
        <description><![CDATA[Stories by Adam Przymusiała on Medium]]></description>
        <link>https://medium.com/@przymusiala?source=rss-d01f70757dfb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*-RtdvztBoLfIP9TS.jpg</url>
            <title>Stories by Adam Przymusiała on Medium</title>
            <link>https://medium.com/@przymusiala?source=rss-d01f70757dfb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 04:45:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@przymusiala/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[Software House Agreement? Use the checklist!]]></title>
            <link>https://medium.com/binarapps/software-house-agreement-use-the-checklist-ae397861987f?source=rss-d01f70757dfb------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae397861987f</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[agreement]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Adam Przymusiała]]></dc:creator>
            <pubDate>Thu, 26 Jan 2017 16:13:49 GMT</pubDate>
            <atom:updated>2017-01-26T16:13:49.705Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gEEIEPd-Tu1Iwwd7Nsm66w.jpeg" /></figure><p>Not so long ago, I had a TechHub workshop at Warsaw’s Google Campus on software company agreements, taking a closer look at coding for startups.</p><p>When participants begun to share their stories, I was struck how many of them were about “third-party failures” (for both freelancers and companies). Being one of those external contractors, I was in a shock: these projects were derailed by things easily avoidable — to me at least.</p><p>That’s why I’d like to show you my three checklists, named roughly by the topics they cover: tech stuff, copyright, and other stuff — obviously the most extensive of them all. I hope that the things mentioned below will not only help you save money, but also prevent many stressful situations.</p><h4><strong>The Tech Stuff</strong></h4><p>a.k.a. service provider requirements that have to be met in full before making any type of commitment. If your startup team doesn’t meet the criteria below, it’s a warning sign: you might be dealing with rookies or a team who have never taken on bigger projects.</p><ol><li>A code has to be kept in a repository, which means:</li></ol><ul><li>You can always roll back to an older version,</li><li>Teams can collaborate while working on a code,</li><li>A code is always available both on a local machine and a server (GitHub, GitLab, etc.),</li><li>It’s much easier to backup a code — on the GitHub, for the third-party, or GitLab, for a service provider,</li><li>You can run code quality auto checks on a remote server,</li><li>You can work on multiple features/revisions at the same time,</li><li>If you work with a freelancer and a repository is located in-house, you don’t lose access to your code when the project is completed.</li></ul><p>2. Auto tests — if you want to be a professional, you can’t do without them. You need them because:</p><ul><li>You have to be able to see whether adding/changing a functionality in Module A affects Module B,</li><li>Introducing a new person to the project team is more manageable (if “the new guy” breaks something while coding, you’ll know that before the code goes out to the production server),</li><li>You’ll have to think twice before any piece of functionality gets coded,</li><li>If you hand the development over to another team, they can’t “destroy” your work,</li><li>Speaking about tests, you should think about a Quality Assurance team. You won’t be required to have one, but it’s a testimony to the quality of your programming process.</li></ul><p>3. Code review, i.e. the process where every piece of code is analyzed by a different person. This is very important, as someone who didn’t create a particular piece of code can offer a new insight by:</p><ul><li>Finding a bug unnoticed by the author,</li><li>Offering a better solution to a given problem.</li></ul><p>4. CI (Continuous Integration), i.e. the additional server used after moving the code to the repository which will:</p><ul><li>Run all auto checks throughout the project,</li><li>Check for any outdated external libraries used in the code and also run a validation check,</li><li>Check for potential security breaches,</li><li>Prevent a code that didn’t pass tests from being used in the project’s main development pipeline.</li></ul><p>5. Mandatory use of English — seems like a secondary issue at first, but reading a code that is written in both English and another language:</p><ul><li>Is a bit inconvenient,</li><li>Makes a bad impression (looks kind of messy).</li></ul><p>6. Documentation — I can’t imagine how you’d expect a project to be maintained in the long term without a proper description of major functions or methods.</p><p>7. Known framework vs. custom systems (or spaghetti code) — this might be harder to verify by someone without a proper technical background. Using a known framework:</p><ul><li>Is a safety measure; you don’t have to rely on one company and their programmers, they’re not the only people in the world who know your code,</li><li>Allows new people/companies to join your project and get up to speed with ease,</li><li>Enables use of libraries made by global community,</li><li>Means that the community is responsible for maintenance, development, and security of your code base,</li><li>Results in you having access to an enormous component database that you don’t have to code yourself and that means savings.</li></ul><p>8. Staging, test, and production servers — the ability to preview the code and partial results in another environment (not the user server).</p><h4><strong>Copyright</strong></h4><p>It seems like there’s not much to worry about in the beginning stage. But, if your project is a major success, this can be a real setback:</p><ul><li>First of all, make sure the copyright is granted :) (by the service provider).</li><li>If you work with a company, check whether their contractors have waived copyright (e.g. as opposed to in-house staff).</li><li>AGPL libraries — that doesn’t have to be the case in all your projects, but if you don’t want your code to be open-source, make sure you stay away from those.</li><li>Include a “provision of a standard software” clause in your agreement. That covers what is yours, and what is granted to the other party. For example, a software house uses a portion of code from their library to solve a typical problem (like logging in). You’re not granted full copyright, but you get the product delivered faster.</li><li>Remember to take a look at license terms for free scripts and images — some of them will require a proper credit on your website.</li></ul><h4><strong>Other stuff</strong></h4><p>By now, at Binar::Apps, we’ve delivered dozens of projects (if not hundreds). I think that the negotiation process would be even smoother if our customers had certain issues thought out beforehand. For example:</p><ol><li>Rate per hour, project stage, or fixed for the whole project. This is one of the most important decisions:</li></ol><ul><li>Hourly rates allow maximum flexibility for both sides: you can modify ongoing projects to ensure everyone works toward a common goal; it equals the distribution of expenses, but it requires a certain degree of trust; you have to believe the company is honest and reliable and makes the best use of its time,</li><li>Fixed project price — you get the impression that you know exactly how much you’ll pay for… but this can be quite deceptive. In real-life situations, there are always some changes to be made, either in a project or indirectly, requiring an annex to be signed. The contractor or service provider will be more than reluctant to work beyond the project scope without additional payment. The contractor will do everything to minimize the overall effort; the client will do everything to get as much beyond the agreed specification as possible,</li><li>Staged billing — this is a hybrid model, you agree on a fixed price for modular pieces of work. Depending on the module size, you’ll have to deal with some of the pros and cons of the above :)</li><li>Before you make that kind of decision, I recommend reading “Lean Startup” by Eric Ries,</li></ul><p>2. Establish the delivery method: whether it’s a whole project or weekly updates with your feedback and user feedback.</p><p>3. Agree on delivery and acceptance phase for both sides — you can’t allow the acceptance process to take forever to complete.</p><p>4. Application maintenance after launch, SLA parameters — you have to include a provision that the contractor can’t just “abandon” you and the project after final delivery/launch. The real life-cycle of software begins when end users start using it.</p><p>5. You have to define both partial and final delivery terms &amp; conditions.</p><p>6. Difference between maintenance and further development — what level of service do you get when the contractor only maintains your system?</p><p>7. On what terms can you get out of the contract (either you or the contractor)?</p><p>8. Prepare an NDA, don’t waste time on writing a list of big contractual fines.</p><p>9. Include a clause on allowing/not allowing your product to be included in the provider’s portfolio.</p><p>10. Get to know who implements your application on a server and how. Define who is responsible for application server availability on and post-launch.</p><p>11. Contractual fines — see situations in which they can be imposed.</p><p>12. Last but not least: consult your lawyer :)</p><p>For more tips &amp; tricks on working with software house check our <a href="https://binarapps.com/blog">Binar::blog</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae397861987f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/binarapps/software-house-agreement-use-the-checklist-ae397861987f">Software House Agreement? Use the checklist!</a> was originally published in <a href="https://medium.com/binarapps">BinarApps</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Startup commandments]]></title>
            <link>https://medium.com/binarapps/startup-commandments-80a324336141?source=rss-d01f70757dfb------2</link>
            <guid isPermaLink="false">https://medium.com/p/80a324336141</guid>
            <category><![CDATA[vc]]></category>
            <category><![CDATA[venture-capital]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Adam Przymusiała]]></dc:creator>
            <pubDate>Wed, 04 Jan 2017 14:34:23 GMT</pubDate>
            <atom:updated>2017-01-04T14:34:23.937Z</atom:updated>
            <content:encoded><![CDATA[<h4>What you REALLY need to create a successful startup.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N-6vdg-eP1w_5Femejg5pA.jpeg" /></figure><p>In today’s world, building a startup is very often perceived as an alternative and more desirable career path than working in a big company. People with ideas more often tend to prefer working for themselves, rather than being on someone else’s pay list.</p><p>Therefore, the number of existing startups is growing rapidly, new ideas seem to emerge every day, yet most of them — even potentially great — fail in the long run. Why does this happen? Why is it so hard to maintain the initial momentum? Is it really that hard to build a successful startup?</p><h3>The only three things you need to consider when creating a startup.</h3><p>There is no magic formula on which you can build your startup to ensure its success. There are, however, three underlying foundations which will help you start your business the right way.</p><p><strong>First: People</strong></p><p>The most important factor are the people you’re going to work with. Usually there’s a rule that one founder is not enough to build a successful startup, because it’s very risky to have only one person going through the whole process. Building a startup means encountering plenty of setbacks and as a Founder, you’re going to need someone to help you.</p><p>So right from the start you should seek out some awesome founders and an awesome team, who will help you along the way and go with you through the process of building a startup with equal passion as yours.</p><p>If you create a startup strongly based on technology and you’re not 100% sure you can build a product yourself — work with a software house. Experienced and proactive software houses are pure gold when you’re trying to build a successful startup.</p><p><strong>Second: Market</strong></p><p>Even the greatest idea means nothing when there’s no market to which you can propose this idea. So when building a startup. you really need to take into consideration the market you’re trying to reach with your idea. You need to find a big enough niche for yourself, so that your idea can really make a difference and subsequently sell.</p><p>Of course, the ideal situation occurs when you have a so-called “Blue Ocean” — a niche where there’s no competition. But that rarely happens. This means you have to build your business differently in order to attract consumers.</p><p><strong>Third: Product</strong></p><p>The product exists somewhere between the people and the market. When creating a product, you must always consider your market and have the best people possible to build it. Only when you have a great product created by talented, passionate people, and a well-targeted market, can you expect some level of success.</p><p>These three foundations are not the recipe for instant success, but if you check all three boxes, you can sleep easy you’ve done the basics right.</p><h3>Make these foundations your priority. Not money.</h3><p>As counterintuitive as it may seem, this really is the best advice you can follow. And its constantly given by VC people, such as Marcin Zabielski from Hedgehog Found. “Take money as late as possible”.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F1AjcHfofzKU%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D1AjcHfofzKU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F1AjcHfofzKU%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/22575f2fd347498d7f22c446974e4eff/href">https://medium.com/media/22575f2fd347498d7f22c446974e4eff/href</a></iframe><p>Too many startup Founders today go after funds first, instead of focusing on their product. As a result of that attitude we see huge numbers of failed startups, poorly designed products, and crumbling businesses.</p><p>Investors like Hedgehog Fund try to eliminate such founders from their portfolio. Therefore, you should avoid focusing too much on financing your startup. Instead, focus on building awesome products which will sell and seek funding afterwards so as to scale up and speed up your growth.</p><h3>When you’re seeking funds to scale up your business, here is what you should look out for to attract investors.</h3><p>It is very important to understand that there’s no universal formula which investors use to hand over money to founders. It all depends on the startup, on the partner, on the region.</p><p>Usually though, investors back up startups on the basis of their experience and know-how. So if you’re looking for funds, you should pay attention to VC’s already backing similar businesses to yours.</p><p>You should also realize that when it comes to convincing an investor, everything counts.</p><p>It’s not enough to have a product to convince a VC to give you money. They will assess you and your business through everything you represent.</p><p>What are your values? What is your motivation? What is the genesis of your startup? What problems does it solve? — these are the questions you may encounter when seeking funds for your company.</p><p>On your part, it is very important to be knowledgeable about your niche and your product. But also — stay humble. There will always be someone brighter than you and that’s perfectly fine — use it and learn from such people. When looking for an investor try not only looking for the money, but also — for guidance. Surrounding yourself with people who are wiser than you also applies to searching for funds.</p><p>On the other hand — don’t be ashamed of your failures. Embrace them.</p><p>When an investor sees someone with a strong history of failures, he can assume that a certain founder had learned his lessons along the way. So treat your failures as opportunities. Not as something to be ashamed of.</p><h3><strong>The top quality required to build a successful startup and convince VC? Passion.</strong></h3><p>Passion is the most important thing, and should be present in you and your business every step of the way. Your product should be born of passion. Your business should be conducted with passion. And that passion should drive you, day in and day out.</p><p>That passion will ultimately grant you money, because when investors see a founder who is struggling every day and trying to break the wall they are more likely to give him money, rather than backing up someone focused solely on profit.</p><h3>Hedgehog concept — a simple explanation of what makes a success.</h3><p>It was Jim Collins, author of the book “From Good to Great” who came up with this concept. In short, it encompasses all of the areas you must understand to achieve success.</p><p><strong>First area: Doing everything you’re the best in.</strong></p><p><strong>Second area: Being focused on what’s attractive to you.</strong></p><p><strong>Third area: You must make money out of it.</strong></p><p>So in the end what it all boils down to is never losing your passion. Do what you can do best. Stay focused on that which you consider sexy, not what’s attractive to others. Find a way to make money out of it.</p><p>These are the core, underlining principles which you should hold on to, if you want to create a successful startup and not fail in the long run.</p><h3>How much money do you need to build a startup?</h3><p>That’s a very tricky question. Because sometimes, if you’re a developer or a businessman you need zero money. You can create a product with zero money. But it’s very rarely happening. So it also depends on the country, the region. In our region, central-eastern Europe I could say that (in seed) you need up to 200–300K Euro. This is this kind of money that can lead you to an MVP, to having first sales, first clients, trying to get some attention from the market.</p><p>After the seed stage you probably need a million or two for the growth stage.</p><p>That’s a pretty penny. How much of it can you gather from funds, from Venture Capital, financing rounds, etc.?</p><p>What usually happens is that Venture Capitals give you the rounds of money. For instance, in our funds we try to set up some KPI’s (Key Performance Indicators) just to achieve them. And after a founder of a startup achieves these KPI’s we raise and give another round of financing.</p><p>And what’s the other way around? If you don’t want to go through all of this financing, what can you do?</p><p>At the very beginning usually it’s like 3 “F”, which everybody knows — Friends, Fools and Family. So you take the money from these sources. I know some companies which have just used this kind of money and they’ve succeeded, so the rule I was talking about that you have to take the money as late as possible — it applies here.</p><p>The first thing that you need is to have a product which will sell, obviously, but afterwards you still can seek for some money just to scale it up.</p><p>Sometimes — even if your product is very good — you get as much money just to speed up the process. Just to scale up the resources. It’s pretty common for the companies. For example, you have big startups, big companies like Uber. They still take some financing just to scale it up.</p><p>For more articles about startups and working with programmers please check <a href="http://bit.ly/BinarBlog">Binar::Blog</a> and <a href="http://bit.ly/BinarTV">Binar::TV</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80a324336141" width="1" height="1" alt=""><hr><p><a href="https://medium.com/binarapps/startup-commandments-80a324336141">Startup commandments</a> was originally published in <a href="https://medium.com/binarapps">BinarApps</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Working with programmers. A simple guide for non-technical entrepreneurs.]]></title>
            <link>https://medium.com/binarapps/working-with-programmers-a-simple-guide-for-non-technical-entrepreneurs-dfbb6ba0c45a?source=rss-d01f70757dfb------2</link>
            <guid isPermaLink="false">https://medium.com/p/dfbb6ba0c45a</guid>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Adam Przymusiała]]></dc:creator>
            <pubDate>Wed, 26 Oct 2016 14:46:15 GMT</pubDate>
            <atom:updated>2016-10-26T14:56:06.876Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Everything you need to know about “the secret language of programmers” before coming to a software house.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BxHdyz9EaMYDlasXA5ilcQ.jpeg" /></figure><p>So you have this big idea for an application that will change people’s lives, allow you to expand your own business and make tons of money. But… you don’t really know much about coding and making apps. However you know exactly how you want this app to work, you just don’t know how to make a reality out of it.</p><p>Your best option is to come to people who do.</p><p>As stated by Michał Brodecki, a senior developer at Binar:Apps, around 80% of the clients coming to a software house are people just like you — with little to no knowledge about coding and developing an app.</p><p>From this short article you’ll learn basically everything you need to know before coming to a software house. At the end of this read you’ll know how the whole process of working with a software house look like and hopefully all of your angst related to working with skilled developers will vanish.</p><h4><strong>Do I need to possess any programing knowledge before coming to a software house?</strong></h4><p>In short — you don’t. Really.</p><p>Because it’s actually the programmer’s job to guide you through the entire process. As with building your startup, you will learn a lot as your product develops.</p><p>Just as you don’t have to possess any technical knowledge, you also don’t have to scan the web in search of programming jargon. Once again — it’s their job to understand your idea and translate it into a written code and a working product. Just like you go to a hairdresser — you simply tell him how you want to look (or show him some pictures) and he does his job from there. Same goes for developing an app. You need to have the idea. Figuring out the rest is up to developers.</p><p>However, if you want to acquaint yourself with some terminology, here are three words you may find helpful:</p><p>- Deploy — means “release”. When programmers are “deploying the app to the production” it means they are releasing it live, to people.</p><p>- Staging — if something is being “deployed to staging” that means it’s being deployed internally, for testing purposes</p><p>- Merge — combining additional functionalities (technically speaking — lines of code) with already existing ones. Adding small chunk of code to the big entity: the app.</p><p>Also, you don’t have to worry about being taken for totally ignorant by the programmers you work with. Even though when programmers are talking to each other it really sounds like some “secret language” you — as a client — will get explanations from them in a more “normal” fashion.</p><h4><strong>Working with a software house in practice.</strong></h4><p>It all begins with the initial meeting, where you and developer team are trying to figure out what it is exactly you need. What programmers try to determine at first, are possible pitfalls, possible issues and possible hard parts of your app.</p><p>This part is crucial for the following process, because the sooner you and the programmers spot all those possible drawbacks and hurdles, the easier the job will be later.</p><p>Sometimes a few minutes more during the initial meeting (or any of the further meetings, for that matter) would save programmers long hours of coding.</p><p>In most scenarios, you and the developer team are creating an MVP — Minimum Viable Product. The application that provides one main functionality that will earn money for you, as a client.</p><h4><strong>The first phase of creating MVP is isolating the scope of the MVP.</strong></h4><p>Your potential app cannot be all the things at the very start, even though you’d like to have all those bells and whistles and fireworks done in one take. Sorry, but… that rarely works.</p><p>That’s why isolating the scope of the MVP is so important and it’s both your and the programmers’ job to cut out all of the unnecessary parts of the idea and start simple.</p><p>What an experienced developer would tell you is that, in startup world, releasing a product as fast as possible is crucial, to get early feedback from the initial user base. And that obviously cannot be achieved if you try to cram all the functionalities in the world into the first-gen product. Imagine spending 3–4 months on developing an app. You’d burn money. You’d burn time. During that period, your business wouldn’t really grow and you wouldn’t have anything to offer to your clients.</p><p>But when you finally release the app, with all the bells and whistles it can turn out that… only one function generates revenue. And that you could have spent a small percentage of that 3–4 months period, and have an app with just one core functionality. And start to earn money sooner.</p><h4><strong>It’s all based on trust and quick communication.</strong></h4><p>One of the things that differentiate Binar::Apps from other software houses is direct communication between you — the client — and a dedicated developer team, assigned specifically to your project. Why is this so important? Because during the development period, you’d better be prepared for multiple meetings and long conversations.</p><p>As there is no middleman between you and the developer team, those meetings and getting feedback is much more efficient. You are saving time by connecting directly with developers, instead of wasting it by trying to explain everything to some middleman.</p><p>During that process, issues will come up which are not black and white. That’s why you have to put some trust in the experience of programmers working on your project. Because very often, their experience means that they’ve been through this before and they were right the last time! And the time before that… As you start working on the MVP, you’ll soon learn that sometimes it’s better to compromise at first and then expand and you should really trust your developers on that.</p><p>By trusting your programmers, you allow them to focus on core functionalities and making them more interesting and attractive. Your cooperation flourishes along the way, built on mutual trust.</p><p>What’s also very important (both on your side and on the programmers’ side) is being flexible with responding to feedback. Some companies have very strict rules as far as feedback goes — for instance: three rounds of emails and that’s it.</p><p>Such a strict attitude towards feedback is not advised. Because if you want to have your MVP done as quickly and efficiently as possible, you have to be ready to respond as quickly as possible, and give programmers feedback (in other words: permission to take further action) whenever it’s needed.</p><p>Limited number of feedback rounds would also be very risky if you try to maintain your app correctly after its release.</p><h4><strong>Almost done, but don’t celebrate just yet. Testing first.</strong></h4><p>One thing that’s far too often neglected by startup owners is proper testing of their app before its release to the public. Hence all the digital marketplaces are overflowing with products that seem unpolished at best.</p><p>To avoid that, you have to make sure that testing of your app is done properly.</p><p>At Binar:Apps the very first part of testing is done at the very beginning of the creation process. After gathering the specification, developers create automatic tests for the code. It automatically checks if something is broken. If anything new that’s being added would break the code created, for example,two months ago, you have a security measure for that. So that’s the first part of the testing process — automatic tests.</p><p>Second part of testing is done by a QA — Quality Assurance team. Those are the guys whose job is to do their best at crashing your app. They’ll do anything to spot any bugs.</p><p>Third part: the code is being released to you — so you can play around with it, check all the functionalities, perhaps provide some additional feedback.</p><p>Only after those three phases are done, you are ready to go into production and to ship the final product to the public.</p><h4><strong>Forget “perfect”. Embrace “good enough”.</strong></h4><p>When coming up with the idea for an app, what you need to remember at all times is that… no app is ever complete.</p><p>That’s why just like you shouldn’t try to cram all the functions into the MVP, you shouldn’t try to make your product perfect at the first try. Because — especially in your own eyes — it won’t ever be perfect.</p><p>Each time you take a look at your app after its release you’ll see some things that can be tweaked. Some functions that can be added. Some layout elements that can look better.</p><p>Therefore you don’t have to create a perfect and “complete” application at the first try. Because there will always be something you can improve on.</p><h4><strong>Careful with users feedback!</strong></h4><p>You may think that listening to your clients is the most important factor when it comes to improving your application. That it’s the core of sustaining the flow of money generated by an app. And sometimes it is. But sometimes — it’s not.</p><p>Let’s say that a couple of customers suggested adding some functionality, which they think would be “nice to have”. So you spend a couple of weeks and a bag of gold coins to develop this new “cool feature”. The result? Your revenue after the addition rises only slightly, if at all. Why? Because the general public don’t even notice.</p><p>On the other hand, sometimes you can spend very little time and virtually no money on developing a seemingly small function, which will generate tons of money for you, as it would change the way users interact with the app.</p><p>So always take notice of customer feedback, but be very cautious when it comes to actually incorporating it into your product.</p><h4><strong>There’s no “secret” to working with programmers. Only mutual trust.</strong></h4><p>You’ve probably noticed a recurring theme during this read. What matters most when it comes to working with a team of experienced developers when you have no technical knowledge is… trust.</p><p>That may sound bland and false to you, but it’s actually the truth.</p><p>When you first come to a software house, you need to trust that they’ll understand your intentions and your ideas.</p><p>When you’re working with developers, you need to trust that they won’t take you for totally ignorant just because you don’t code and don’t know their jargon. And don’t worry. They absolutely won’t.</p><p>When you’re creating a scope of the MVP, you need to trust that sometimes less is more and that finding a good compromise would result in better product and less spent money. The list goes on and on.</p><p>So if you are a non-technical guy, you really shouldn’t waste energy on trying to learn “the secret language of programmers”. Instead, try to learn how to trust their experience and expertise so you can make your cooperation more efficient and more beneficial for your business.</p><p>Find this article interesting? See <a href="https://youtu.be/hp4V9JzlUN4">full interview with Michał Brodecki</a>, developer from Binar::Apps. You can also download our free <a href="https://binarapps.com/ebook/how-to-work-with-a-good-software-house-in-8-practical-steps">ebook „How to work with a (good) software house in 8 practical steps”</a>.</p><p>Check also <a href="https://www.youtube.com/channel/UC8xroChoeq0dyLVSunHXGVg">Binar::TV channel</a> for more videos about technology and business.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dfbb6ba0c45a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/binarapps/working-with-programmers-a-simple-guide-for-non-technical-entrepreneurs-dfbb6ba0c45a">Working with programmers. A simple guide for non-technical entrepreneurs.</a> was originally published in <a href="https://medium.com/binarapps">BinarApps</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>