By separating specifications to Must-have and Nice-to-have lists, we are helping clients better understand the process and have more control over the product and the budget.<\/p>\n
Clients are usually not familiar with the complexity of certain features. Something that occupies small area on the interface \u2014 for instance, a newsletter subscription form or “send to a friend” \u2014 might be more complex than the rest of the site.<\/p>\n
When glancing over the request for a proposal that is full of tiny little add-ons, you already know \u2014 it will boost the quote up to the sky. Most of the functionalities are in their original form simple and straight-forward, but each project has it’s own twists. Ideally, each detail have to be tailored to perfectly fit the rest of the site.<\/p>\n
When the prospect is able to bare her requirements down to absolutely essential parts, the “core”, you are half way there.<\/p>\n
This is not a single player match. We as an experienced professionals should help and educate clients \u2014 and finally: make them confident in our abilities.<\/p>\n
Depending on the nature of the relationship with the client, ask simple questions:<\/p>\n
\u2014 “If you’d ask someone to create a web site as a favor, what would be the absolutely necessary parts?”.<\/p><\/blockquote>\n
Break it by milestones<\/h2>\n
It is a win-win situation. Quoting a Must-have list is so much easier! When you’re both settled with the features\/price, call it a milestone, a phase in a process.<\/p>\n
During the first phase, you’re about to show the client that you are worth her money. Release this first “essential” version. If she’s satisfied with the results, price and timeline, you gained the trust.<\/p>\n
From that point on, discussing the Nice-to-have features is a breeze.<\/p>\n","protected":false},"excerpt":{"rendered":"
By separating specifications to Must-have and Nice-to-have lists, we are helping clients better understand the process and have more control over the product and the budget. Clients are usually not familiar with the complexity of certain features. Something that occupies small area on the interface \u2014 for instance, a newsletter subscription form or “send to […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[17,19],"tags":[48,47,45],"_links":{"self":[{"href":"http:\/\/www.maratz.com\/blog\/wp-json\/wp\/v2\/posts\/709"}],"collection":[{"href":"http:\/\/www.maratz.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.maratz.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.maratz.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.maratz.com\/blog\/wp-json\/wp\/v2\/comments?post=709"}],"version-history":[{"count":0,"href":"http:\/\/www.maratz.com\/blog\/wp-json\/wp\/v2\/posts\/709\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.maratz.com\/blog\/wp-json\/wp\/v2\/media?parent=709"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.maratz.com\/blog\/wp-json\/wp\/v2\/categories?post=709"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.maratz.com\/blog\/wp-json\/wp\/v2\/tags?post=709"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}