{"id":2969,"date":"2009-11-10T09:28:40","date_gmt":"2009-11-10T15:28:40","guid":{"rendered":"http:\/\/crowdspring.wpengine.com\/?p=2969"},"modified":"2025-11-30T17:09:39","modified_gmt":"2025-11-30T23:09:39","slug":"startup-technology","status":"publish","type":"post","link":"https:\/\/www.crowdspring.com\/blog\/startup-technology\/","title":{"rendered":"Choosing Technologies for Your Web Startup (Part 1)"},"content":{"rendered":"

You have a great idea, a viable business model, and investors lined up. Now, you need to build your website. You’ll likely start by hiring a consultant or consulting firm. Consultants can be valuable resources, and good relationships with them can be key to growing your company. The unfortunate flip side is that bad advice can lead to a stalled product, unable to scale and compete.<\/p>\n

Worse, you might find yourself locked into an expensive, tense relationship, with the consultants being the only ones who can get you out of the mess they put you in. Because development cycles for web services are measured in months if not years, you cannot afford to make mistakes.<\/p>\n

In this series of blog posts, I’ll offer advice on interpreting what consultants tell you and on better expressing your needs.<\/p>\n

One important point to always keep in mind is to be conservative. Consultants will attempt to pull you into newer technologies for various reasons that are attractive to them and possibly attractive to you. The risks may not be entirely obvious.<\/p>\n

Part 1: The Myth of Productivity<\/strong>
\n\"\"<\/a><\/p>\n

The word \u201cproductivity\u201d should be a red flag for you. Let’s unpack it. It seems to mean \u201cthe ability to produce results quickly.\u201d Anything \u201cproductive\u201d seems good, and you should strive for more.<\/p>\n

Who wouldn’t want to move more quickly from product design<\/a> to finished product? However, \u201cproductivity,\u201d as used in this context, can lead to the opposite. To understand this, we have to ask: What exactly is slowing down the process in the first place? Is it, in fact, slow?<\/p>\n

Part of the confusion is due to the process being obfuscated. Software engineers<\/a> are extreme specialists, and outsiders have little clue about what goes on.<\/p>\n

Software projects are fertile ground for buzzwords to take root. As an outsider, what you need to know is that there are components to the development process \u2013 drafting, prototyping, debugging, deployment, and testing (all of which happen before integrating the product into its social environment) \u2013 and that together, they compose a \u201ccycle,\u201d such that development moves back and forth between components. You might want to explore different software development methodologies<\/a> for a deeper understanding of these cycles.<\/p>\n

Incorporating security into this cycle, such as through a DevSecOps maturity model<\/a>, can ensure that security is built
\nin from the start rather than tacked on later.<\/p>\n

Want a free brand review?<\/div>
\"brand<\/div>
Answer 5 short questions and we will send a custom report with actionable insights and specific actions you can take to build a stronger brand.<\/div>
\n