Hi, I'd suggest that you read The Lean Startup if you haven't, it should put you on the right track to determine priorities. Web development is a beast and ver

Hi, I'd suggest that you read The Lean Startup if you haven't, it should put you on the right track to determine priorities. Web development is a beast and very different from traditional thick clients as you often have to cater for multiple types of users (roles & permissions) as well as multiple portals (different user interfaces and interaction based on users). Most projects would typically require at least two distinct portals: traditional user portal and administration portal. For franchises there are usually two levels of administration (top level/standard level) that requires different views of the data (ex. across the franchise for administrators and impersonation of standard franchisees). In my experience there isn't really a simple crud application - the information you collect depends on the functionality you provide. Many users is also very abstract as it will impact your infrastructure requirements - too many unnecessary abstraction layers will really slow down development but is typically required for SOA/N-Tier/CQRS stacks. My advice is simple: Pick one thing and go through the process of validated learning. It's possible to run a successful business on an adhoc stack - it's not required to run perfect software from the beginning, but flexibility and adaptability sure helps. I'd almost say build something quick and dirty that you can change/scrap easily depending on your business requirements till you reach the point of the business being profitable, then you can invest more into it.