Spoiler: Because their telepathic abilities allow them to directly transmit information to the brain of the person who is developing the website for them.
And the customer probably thinks that the programmer, webmaster or someone else just wants to scam him out of money. And in vain. After all, how can you build a house without a project, without a drawing?
“I built it perfectly,” the client once answered me.
God bless him! In addition, so that his house would stand for two hundred years. However, he built for himself. That is, he himself acted as a performer (hired workers do not count - they simply do what they are told at the operational level). And it’s a completely different matter when the performer and the customer are completely different people.
Other customers motivate their reluctance to draw up technical specifications by showing them a competitor’s website and asking them to make the same one. Let's be honest, this way you can roughly understand what the client wants, but sometimes it only gets worse. The fact is that the customer of the website and the developer who will create it look at another website with different eyes. The customer sees an image, a picture. However, the developer immediately analyzes the functionality. Does the customer need it one to one? Exactly like this or a little different? Is everything needed? After all, implementing EVERYTHING can increase the budget. In addition, who knows how much that original competitor website cost? And we are talking only about the front end.
Yes, you need to pay attention to your competitors. Nevertheless, don't blindly copy their solutions. Walking along the same path, you are unlikely to overtake the one who went out earlier. In a good way, you need to explore the entire niche and take the best from everyone. Alternatively, do just the opposite. But this is the “technical specification”.
Advanced customers can turn to magic words like: “development using the Agile system,” etc. But, in fact, technical specifications are written there too. Simply for each individual stage of work.
Yes, the technical specifications often change during the development process. However, for this you need to at least have something that needs to be changed.
Let's summarize.
The terms of reference (TOR) for creating a website will help:
- save time on creating a website - the developer will know exactly what and when he will do.
- save your nerves on sorting things out with each other is priceless.
- save money - when there is no need to implement extra unnecessary functionality, and there is no back and forth, because often the customer pays based on the time spent by the programmer.
Write technical specifications! Either on your knee, or in Excel. If the site is simple. But there must be technical specifications.
