{"id":3041,"date":"2026-11-19T11:03:48","date_gmt":"2026-11-19T09:03:48","guid":{"rendered":"https:\/\/www.kaarne.fi\/superstore\/?p=3041"},"modified":"2026-11-19T11:04:04","modified_gmt":"2026-11-19T09:04:04","slug":"what-should-a-website-prototype-prove-in-a-sales-conversation","status":"publish","type":"post","link":"https:\/\/www.kaarne.fi\/superstore\/articles\/what-should-a-website-prototype-prove-in-a-sales-conversation\/","title":{"rendered":"What Should a Website Prototype Prove in a Sales Conversation?"},"content":{"rendered":"<p>You can spend the evening filling a prototype with pages and still leave the client unsure what they are being asked to judge. A sales conversation needs a clear question more than it needs a convincing impression of completeness.<\/p>\n<h2>Choose one decision the demonstration supports<\/h2>\n<p>Imagine a fictional designer pitching a website for a neighbourhood repair service. The client is unsure whether visitors should begin by choosing a service or describing the problem with their item. The prototype\u2019s question becomes: can we explain a useful route from the customer\u2019s problem to the appropriate enquiry? That is narrow enough to demonstrate and important enough to discuss.<\/p>\n<p>Avoid a purpose such as \u201cshow them what their new site could look like\u201d unless you can explain the decision that follows. Are you discussing a proposed information structure, a visual direction or a particular task? You can demonstrate more than one later, but the first conversation becomes easier to assess when its main purpose is explicit.<\/p>\n<h2>Prepare three moments of evidence<\/h2>\n<p>For the repair example, the first moment is arrival: the opening screen helps the visitor recognise the kind of repair being discussed. The second is choice: the visitor can distinguish the available routes without already knowing the company\u2019s internal service names. The third is the next step: the enquiry explanation shows what information the customer should provide.<\/p>\n<p>Build only enough sample material to make those moments understandable. One meaningful service example can reveal the proposed structure more clearly than twelve generic service pages. Use plainly marked illustrative information. Do not invent service availability, customer quotations or guarantees to make the demonstration feel commercially finished.<\/p>\n<h2>Explain what is real before the walkthrough<\/h2>\n<p>Start with a short boundary statement: \u201cThis is a working proposal for the enquiry journey. The sample content shows where the information would go. Today we are deciding the route, not approving final copy or confirming a live receiving process.\u201d Adjust the words to the actual prototype; do not call something simulated if it really performs a consequential action.<\/p>\n<p>Then describe what you will show and what remains to be built or verified. If the enquiry interaction is only a visual example, say so before anyone tries it. A polished appearance must not carry a stronger promise than your explanation. Keep that boundary in any follow-up material the client may forward.<\/p>\n<h2>Ask a question at each moment<\/h2>\n<p>At arrival, ask: \u201cWhat kind of help does this page appear to offer?\u201d At the choice point, ask: \u201cWhich route would you expect a customer with this problem to take?\u201d At the next step, ask: \u201cWhat would they think they need to send?\u201d Let the client answer before explaining the intended interpretation.<\/p>\n<p>You are collecting a response to a proposal, not conducting a measured usability study or proving a conversion rate. A client who knows the business is also different from an unfamiliar visitor. Their answer can reveal an unclear service distinction, but it cannot establish how every future customer will behave. Record observations in proportion to what happened.<\/p>\n<h2>Capture the decision and the unknowns<\/h2>\n<p>The client may agree with the problem-first route but identify one repair category requiring a separate instruction. Write that down as a specific structural change. Separate it from undecided details such as photographs, exact copy and the enquiry receiving arrangement. This prevents a positive reaction to the prototype from becoming accidental acceptance of everything it resembles.<\/p>\n<p>A useful meeting note has four lines: question demonstrated; proposed route; agreed change; unresolved dependencies. In the example, it might say that the service-selection approach needs a clearer specialist route, while the final content and receiving process remain open. That note is a better next-step brief than \u201cclient liked the demo\u201d.<\/p>\n<h2>Finish with the next piece of evidence<\/h2>\n<p>Agree what you will bring to the next conversation: perhaps a revised route using the client\u2019s confirmed service information. Ask for the smallest input that makes that possible. A prototype has done useful work when it helps the client make a bounded decision and shows what must be learned next. It need not pretend to be a finished website to earn its place in the sale.<\/p>\n<p>Choose what the prototype needs to demonstrate, then prepare only the sample material needed for that conversation. A prototype is easier to assess when its purpose is explicit.<\/p>\n<p>When the promised copy is missing, use <a href=\"https:\/\/www.kaarne.fi\/superstore\/articles\/the-client-copy-is-late-what-can-you-still-design\/\">a dependency plan for designing with late client content<\/a>. After implementation, keep <a href=\"https:\/\/www.kaarne.fi\/superstore\/articles\/resolved-is-not-the-same-as-ready-to-launch\/\">launch readiness separate from closed comments<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A focused prototype gives a prospective client something specific to assess. Decide which uncertainty the demonstration is meant to reduce before building it.<\/p>\n","protected":false},"author":1,"featured_media":3077,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_hide_featured_image":false,"_jetpack_featured_image_duplicate_dismissed":0,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[24],"tags":[],"class_list":["post-3041","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-customer-understanding"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"https:\/\/www.kaarne.fi\/superstore\/wp-content\/uploads\/sites\/7\/2026\/11\/sf-02-01.webp","_links":{"self":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3041","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/comments?post=3041"}],"version-history":[{"count":7,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3041\/revisions"}],"predecessor-version":[{"id":3157,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3041\/revisions\/3157"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/media\/3077"}],"wp:attachment":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/media?parent=3041"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/categories?post=3041"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/tags?post=3041"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}