- Create and implement a high fidelity design.
- Include the project-specific requirements that every feature has... the auth system needs to work via ajax, connect with a legacy db, and include animated transitions. Private messaging needs responsive design and realtime updates. Etc. etc. etc.
- Deal with scope creep, clarifications of the specs, and hours of related discussions.
- Write automated tests.
- Do live QA.
- Fix inevitable bugs, browser and device inconsistencies, ux problems, etc. etc. etc.
- System administration and deployment.
- Load testing, caching, performance tuning.
If a client tried to tell me I should be able to do all this in a morning, I'd fire THEM on the spot.
My "morning", is literally plugging django-social-auth, a custom User Model, a private messaging Model and few views to make it all work.
I'll grant you that testing might eat up the afternoon, but these are all solved problems that ship in libraries, many of which include their own tests.
Perhaps the people downvoting need to change how they build stuff.
The people downvoting you live in reality...
And when you're behind, because you keep underestimating difficulty, and the client is tired of your excuses, one of us will swoop in and show them how a real developer works.
I'd just be careful if you're considering using this to quote your jobs. If somebody working for me quoted these sorts of numbers, I'd fire them on the spot. I wouldn't even give them a second chance. It would clearly demonstrate you didn't know what you were talking about.