How to correctly respond to orders like "pull the layout on cms"?

Question

CMS

Hello!
I'm a layout designer.
I want to expand the field of activity for layout under cms or a stretch of the finished layout.
I looked, often in tasks there are sites with modules. Let me explain. There is a design or layout design, which implies that the site should eventually have modules: news output, order form, calculator, slider. These are all trivial tasks if the desired module can be found in 5 minutes and installed / finished for yourself in 10-15 minutes.
But I monitored the market for these orders, googled the situation and noticed that very often I come across such sites / designs and tasks for them, for which there are no ready-made modules / components for a specific CMS. For example, a non-standard slider, a non-standard news output, a non-standard gallery, a company price calculator with the ability to change coefficients from the admin panel (in fact, there are such orders), and so on. How to be?
More precisely, how not to scare away the customer with words, they say there is no ready-made module / component for your site for cms X, you need to develop it from scratch, it will cost you even more than the site itself. But it will be so, the customer will be frightened or simply will not understand (you are a programmer), because development of a module/component from scratch is more labor-intensive than the layout of a finished design or stretching the layout. under cms

Answer 1

The most normal option is to wait until the orders from the area "pull the layout on the CMS" disappear. Well, or customers of this level will disappear.
There is no normal solution here. Obviously, in 90% of cases, the customer in this case is not particularly competent in the matter. Path 2:
- Try to explain the solutions: why is it difficult, how long it might take, is it needed in this form or should the requirements be simplified, etc.
- Try to solve all the problems for him.
In the first option, you risk losing the customer, in the second - time, money, reputation.

Answer 2

cms has an API that allows you to implement any necessary functionality. Know cms!=know the names of ready-made modules. You can't shut up all tasks with ready-made components, and that's fine.
Conclusion: you write "cms integration" in your resume - be kind enough to match.

Answer 3

Work in tandem with a programmer, what you can’t immediately find, he can add.