How much time as a percentage does it take you to design, layout, stretching, programming the site?

Question

CMS

How much time in percentage or hours does it take you to design, layout, stretching, programming a corporate website? For example, let's take a site with 3-5 templates. The sections are: home, about the company, news/news, services/products service/product, contacts. Functionality: slider on the main page, callback order, feedback form, news with pagination, goods / services with pagination, cost, Yandex map, Yandex metrics, Google analytics. Fixed width design. Content - fill 20 pages.

Answer 1

I don’t know how long the design takes, but layout + programming of a similar sample takes 10-14 days. In general, it is strange that you tried to hang everything on one. The designer has his own, and the frontend has the rest. In the studio, the situation looks like this: designer + layout designer + programmer (and then % would share 40% / 30% / 30% within 14 days)

Answer 2

We almost don’t deal with design (well, fuck it) and we mainly try to sell programming and solutions - it’s much easier this way - it either works here or not, and there are no problems with “Make me more interesting fonts and a brighter hat” and so on.
Therefore, it takes 50% of the time to draw up a clear TOR in Trello - and we do everything strictly according to it.
the remaining 50% implementation, as a rule, nothing from the add. We don’t do any wishlist until we hand over the TK. Dopa dopa separately for a fee.

Answer 3

About 2 weeks for everything, but it all depends on the "wants" of the customer.
40% design, 60% layout + programming.

Answer 4

From a week (if the deadlines are burning and the customer is ready to pay + 40-50% for urgency) to two weeks. Alone, provided that there is no exotic in the TOR, and the main time costs will not fall on negotiations, i.e., when the customer is mature and ready to work.

Answer 5

I counted h = 122+ working hours for three specialists (but we remember that frontend is very dependent on design, but backend can be run in parallel). If we add reality (k = 1.5), then we get h * k = 183+ working hours.