Login | Register   
LinkedIn
Google+
Twitter
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX


advertisement
 

10 Software Development Tips to Get Early Funding for your Startup

This article covers some of the early techniques and strategies to help your startup be well positioned to receive the initial round of investment.


advertisement
If you’re thinking about, or are already working, on a startup, it’s likely that at some point you will attempt to raise an initial round of funding for your venture. This article covers some of the very early development techniques and strategies to help your startup be well positioned to receive the initial round of investment capital.

1) Understanding What Investors Want

Professional early-stage investors typically look for a number of things in early Web startups. While investors often tend to look at things like the market the startup is in, and the product potential, these often have little to do with actual software development of the project. When it comes to the software development of the actual product, investors look for a high quality balance of technical skills on the founding team. High quality here implies that the people are not intern-level, but rather competent professionals at their craft.

[login]



Investors will look for the product to have good design as well as compelling and innovative features. That already implies at least 3 skill sets: design, engineering and product vision.

Potential investors will also most likely only consider the company as an investment if the company has a product in the market, and there are measurable signs that the product is gaining some traction with users. This tells the investors that the team can work together to produce things, and the things that are produced are of high quality and savvy.

2) Battling Limited Resources

Prior to securing funding, startup teams tend to be comprised of under five people and sometimes just one person. Commonly, there are one or a few engineers, and one or two business people. That means that the innovative feature set your new company is creating may not be completed in its entirety any time soon. You must decide which features will be crucial to the core business and which are just very nice to have.

Remember, since we are discussing the pre-funding stage of your company, if you spend too long before you get your product to market, that will be coming out of your own pocket. Your goal at this stage is to create the type of business-requirement to software engineering cycle that will help you rapidly release the very initial product and ensuing features, so that the first customers can begin taking a look at it.

3) Perfect Development Capacity

During the intense push to bring the product into the market, your team must be firing on all cylinders. Just about everyone should be contributing about 6-7 days/week and definitely over 8 hours on most days. The way your team functions at this most crucial point is the way things will be from here on out. The initial company culture is set, and as one of the core founders you must be vigilant and search for weak links in the product development team.

The early-stage development team must also pay attention to detail and focus on product quality. I realize this is a bit of a contrary point to the suggestion of working fast, but the emphasis here is to strive for very high quality with the features you do decide on building. Whatever you do put out into the market will reflect on your sense of professionalism.

If the product is of low quality, after it goes live, your marketing efforts will face continuous uphill battles as potential customers and sometimes investors will be underwhelmed and leave the site right away.

4) Inevitability of Cutting Corners

Considering that your resources are limited, a practical approach might be to very carefully choose which features you can forego, and which parts of the product must absolutely be there. This decision will be crucial to spending the right amount of existing resources (time and the very limited money you have) on the very necessary features.

Since the first impression your product makes on people will come from the product's appearance, design and logo are something that you absolutely cannot skip. Even if you do not have a professional designer on your team, allocate the most visual person to stitch together the most workable design that possible, so that it does not drive investors away.

Some people may argue that smart investors would not look at design. For that argument, I should clarify that the investors will not be looking at your design for the sake of beauty. The design of your site will be their first chance to gauge your level of attention to detail, understanding necessity and right focus on product quality, and your level of aspiration to professionalism.

5) Where to Cut Corners

Since the UI and design must be the absolute best they can be in order to make your team appear as a type of a team that aspires to build great products, you must look for other places in your architecture to cut corners. There isn't much place to cut corners on the database architecture

side of things. Just don't over-optimize it for scalability by building various levels of cache. In the beginning you likely won't need scalability. This is something that is more of an appropriate focus for a later stage if the product takes off.

The last place where you can cut corners is on the server and business login side of the application. I hate to suggest it, but since we must choose a place to cut corners in order to gain development speed, you may consider having an extensive test suite, or refraining from using an interesting new technology that may require a bit of time for a learning curve. You can always get to those things later, but when you are rushing to push a product to market, and let the product have a chance to gain traction, you may want to consider skipping whatever can be done later.

Consider as an analogy how things operate in even an established restaurant. The customers walk in and the presentation layer is spotless. The tables are lined up perfectly, the table cloths are clean, with wine glasses and silverware sparkle, and the place looks impeccably clean. You have a great impression. The same restaurant may have an incredible mess of a kitchen where the people working there are rushing and scrambling to feed the people waiting for their food. If the customers ever saw the mess and chaos that goes on in the kitchens of even the good restaurants, many of them would never come back. But the customers never see the kitchen. They just see the presentation layer and taste the eventual food which was hacked together by the chaotic kitchen.



Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap