4 ways to prepare before reaching out to developer !!

  • 158

 

The time before starting your own company or launching your product is the most exciting time. Here you spend hours doing research, you keep reading about the competitors, have a lot of new ideas, there is motivational content all around you, and you feel all ready to start building your website or mobile application. You want to get your idea developed, become the next Steve Jobs and build a brand like Apple. And you very well shall become that if you plan it properly and avoid the cliche mistakes.

 

One such mistake is made by the founders while they are getting their application made. It is being unprepared and keeping the scope of assumption on what you want to get build. What may be an assumption for you may not be such an obvious assumption for your technical partner. Hence things can get nasty. At Graffersid, we spend initial 14 days only researching and documenting the client’s market’s tech domain and finalizing the features.

 

Don’t wear sneakers for a morning walk; Difference between Development Preparation and Business Preparations

 

Your market research, competitor analysis, business model planning and your launch planning are the preparation on how you would run your startup. But your product preparations are different, the same amount of effort goes into finalizing how your needs to be built. Although, it is your tech partners role to guide you, however, companies in today’s highly competitive market may not dedicate so much time. Therefore, it is better to spend some extra days making a written document of everything that you desire.

 

And NO, I don’t mean you become a geek or a coder, all you need to do is make a detailed document on how things will work on your website or mobile application, a couple of documents mentioning the list of features with the URLs, and a list of competitors. Now let’s discuss this in detail to understand how it can be useful and what things should you take care of while creating it. Below I will also explain how is your competitor analysis different than your Technical Competitor analysis.

 

 

When you prepare for a WAR, it is better to know your enemy

 

This list will be the foundation of your preparation and will act as the backbone for your other documents. Let’s say you are making a grocery application for Indian Market, try to find out other competitors in this domain. In this case, the Competitors could include Groffers, BigBasket, Nature’s Basket, all these are your Indian competitors in the e-commerce segment. While creating a market competitor analysis you might also include, Kirana Stores, Walmart, etc. which are your offline competitors, however, they may not be required for the Technical Competitor analysis.

 

Break your competitors in 3 to 4 segments:

 

  • Local competitors:
  • Local competitors are the other startups in your city or state but haven’t expanded much in other parts of the country. For example: OnDoors (Bhopal based e-store), O2Onow (Hyderabad based e-store), ShopKirana (Indore based e-store).

     

  • Across country competitors,
  • There are the famous startups that you know of like Groffers, BigBasket, Beelivery, etc.

  • International competitors,
  • International competitors could be startups who are operating in multiple countries or could simply be successful starts in any specific country. Example: InstaCart, Shipt

  • Unspecific Competitors
  • There competitors are the once who are more diversified. They operate in multiple domains including your domain. Example: Amazon, UberEats, Flipkart.

     

 

This particular document will come in handy for gathering new ideas in which mobile app could be used to generate additional business and attract more customers. If technology is used properly it could save you 30% of the marketing cost. Let’s see what all information can get out of a list of competitors that we have just created.

 

 

Finalizing feature is like a girl in a mall to buy 1 dress (Sounds easy ?) :

Features are the most important part of the application, it could be the deciding factor on how users would use your product. Even if you make the most beautiful product in the world but the user does not have the required functionality to reach to his end result, it is very likely that he won’t use your product twice. Moreover, it is better to discover all the required features before-hand because adding a new feature in development phase or after the product is built could take significant efforts and delay the release of your product.

 

Make a list of all the features:

 

The most common features are the most likely ones to be missed out. It could prove to be disastrous in the later stages of the development. Hence, list down everything you see in any of the competitor’s application. Things even as small as login button, cart option on the left top corner, etc. There are 2 reasons for doing such a tedious work.

 

  1. Discovery and Finalisation of Features:
  2. When you have a detailed list of all the features that currently exist in the particular domain, it becomes easier to discover new features which could help your end users. You can find interesting combinations of features which could dramatically improve the UX. 

     

  3. Ease of explaining:
  4. When you share this document with your IT partner, it would be easier for them to understand your idea in depth. Moreover, it would also reduce the chances of confusion and assumptions.  This would help you in reducing the time for getting the work started. And, ensuring that the development goes smoothly without any surprises.

 

Your product is like your health and your documents are like the gym:

If you don’t go to the gym you won’t die, at least not immediately, but if you do go to the gym you surely live more healthy and longer. Once your list of features is ready, you can now start to analyze which are the absolutely necessary and which features are just and overheads. As a new product in the market, you don’t want to be too bulky or tough to understand. So try to keep the UI very simple and self-explanatory. Have only those features which are necessary and highlight your USP maximum.

 Create a flow diagram for all types of users, as the last step, create a separate excel sheet document with all the types of user roles written on top and all the final features on the left. While noting the feature make sure you write them down in the flow they occur. Like,

 

  1. Signup 
  2. Login
  3. OTP
  4. Profile
  5. Product Discovery
  6. Categories
  7. Search, etc.

 

The reason to write it in a flow is so that you don’t miss any point and the reader of the document can understand your mindset towards the application.

 

Beneath each user role writes in detail about the information required and the next possible actions he could take from his current stance. Mention it in as detail as possible, to a level that you never have to use “ETC.” in the complete document. Moreover, try to also depict how an action of one user role affects the other user roles. For ex: if the delivery boy is out for delivery then all the other users will receive a notification about the same.

Conclusion

 

Do this and you would reduce the chances of entering into dispute by 80%. For all future reference, you can refer to this document as the agreed deliverables. It does take some time and lot of efforts but then again the startup is your dream it is completely worth every second invested. Wish you all the best, hope you have a great experience and build some beautiful products. Achieve all the success you deserve.

justify

no-repeat;center top;;

auto

54 thoughts on “4 ways to prepare before reaching out to developer !!

  1. Amazingly writing, it tackles so many real-world problems. I was almost taken back to the days when I started my venture. I have fallen in all the mentioned traps but luckily for me, we had good investors and they gave us the support needed to carry on. I wish I could have read this earlier. Nonetheless, cheers to your spirit of Entrepreneurship.

  2. I have had multiple interactions with the IT companies because of the nature of my job and till date, I have not met a single consultant who has given me so much power as your article does. Becuase of my non-IT background all I can do is research and finally surrender to the explanation of the developer as I don’t understand a word of logic they throw at me. Thanks, I leave in a much better feeling and I shall be getting in touch soon with some new opportunities for us to collaborate.

  3. I have been following you on Linkedin and Quora for quite some time now. I think you write great stuff and it is really motivative for us as Entrepreneurs. This is a fairly useful article and hope to reach more from you in the future.

    1. It’s a pleasure to know that our readers are liking the sharing the articles. Our aim is to increase the startup success rate which currently stand at <10% to >80% and it is just a small step and the way ahead.

  4. I have read a couple of your articles and it feels like here is a step by step guide on how to think of an idea to how we can have a successful startup. I have loved the articles that I have read so far, would it be possible to create a proper series with sequential articles?
    I would really benefit us as the early stage entrepreneurs to learn from you.

    1. Thanks for the kind words. We never thought in this way. Appreciate you taking time to reflect on a more efficient way to reach the audiences. we share be doing it soon, so stay in touch.

  5. Aah, why so late? I am one of those founders who made the mistake of diving right into the development, no wonder I failed so bad. I have invested almost $0,000 and the learning I took in this past 8 months is eactly what you have mentioned here. Retrospecting it, I think I should have to know exactly what the customers wanted in advance. Fo development company it is just a project so the more you are prepared the better it is. Appreciate your efforts, this is a very precise and to the point article. I will follow your strategy next time I decide to do a startup. Keep doing the good!!

    1. Hahaha, we wish we could have reached you earlier. Nonetheless, it is not the last day and it is better to fail fast and fail early than to just keep thinking. I am sure you will be a great entrepreneur. Will wait for your next startup.

  6. All the details mentioned are simple to understand and beautifully written. I am a non-technical person and was about to start my startup. This phase is super confusing as to where to take the first step. Now I have a much better understanding of where I am and where I need to be. Thanks a top for sharing this information. Kudos to you!!

  7. In the recent events, I hired a development company and we started working on one of my ideas. Almost 2 months were wasted just in streamlining things and filling the spots. I still had to pay them while the majority of the work was done by me. As I go through the points mentioned in this article I realize that these were exactly the points which I didn’t care about and lost almost $10,000 for no reason.

    Thanks for sharing, it is of tremendous help for early-stage entrepreneurs like me. Highly recommended.

  8. I spent a lot of time to find something similar to this but nothing worked. The articles and strategies are unique and very simple to understand. Thanks for sharing!!

  9. We are into the dating industry and were about to get our app developed from one of the vendors here in UK. However, we then came across your article and tried your approach only to find that the vendor was not the right fit for us. It saved us a fortune. Highly recommended !!

  10. A while back I read an article by Steve Jobs and I simply loved it. After a long time, I have liked an article and felt like the author genuinely wants to help and not just advertising. Kudos to you!!

  11. As a non-technical person, I have never understood what these people said and how to validate them. Finally, something I can relate to. Thanks for the effort.

  12. We have been a variety of volunteers in addition to starting up a whole new system in this local community. Your web site provided us with beneficial information and facts to help artwork for best domains. You’ve completed a new challenging hobby along with our own whole area will probably be thankful to you.

  13. I hired some of the most hyped companies here in Europe and the projects have come crashing down. Working with you was a much smoother experience. Although I didn’t read this blog rehandedly but I am sure to use these tips next time I am in such a spot.

  14. Couldn’t agree with you more. I got my first application developed and was left devastated by the results. Not the developer’s fault but my requirement kept changing. Now I realize what was the issue and how I don’t repeat it.

Leave a Reply

Your email address will not be published. Required fields are marked *