Objective: This paper aims to build an Effort Estimation Model for design, coding and testing Web Applications Based Fuzzy and Practical Models, which will help in optimizing the efforts in software development. Methods/Analysis: Soft computing approach is adopted and applied in the effort estimation and then compared with practical efforts in the development process with interpreting the historical data available for the existing functionalities. Findings: The effort estimation model presented in this paper focuses on the first level estimates published by Project Managers and the second level estimates presented by Project Leaders or Developers for any new requirement or enhancement for a web application built on 3-tier architecture using Microsoft technologies. The model considers the classification of each task as either Low or Medium or High complexity. These tasks pertain to the lowest level parts in bottom-up estimation. Efforts are estimated for designing, coding and unit testing of these tasks and the efforts are summed up to get the effort estimation for the higher level which is a feature to be implemented. Novelty/Improvement: The paper also discusses about the application of the effort estimation model by taking a new requirement as a case study. The first level estimates calculated using the effort estimation model has a variance of about 25% when compared with the actual effort. This variance is very much acceptable considering the fact that the first level estimates can be tolerable up to 35%. The proposed effort estimation tool would help the project managers to efficiently control the project, manage the resources effectively, and improve the software development process and also trade off analyses among schedule, performance, quality and functionality. Fuzzy logic is used to verify the claims made in efforts estimation. It is proposed a new relation between the number of data and efforts value membership for actual data. And converts it into crisp value in the range [0…1] which helps to classify the complexity of the task and subtask in the design, coding and testing phases.