Private demo
A private demo before you commit to a website rebuild.
A proposal asks you to imagine the outcome. A private demo turns the direction into something you can open, read and judge.
The current site is weak, but the fix is unclear.
A full redesign feels too abstract.
The business needs to see direction before committing budget.
What is failing
Most redesign conversations start with pages, moodboards and promises. Those may be useful, but they do not answer the practical question: will this new direction make the business easier to understand and contact?
A private demo lowers that risk by showing a focused version of the site, flow or landing page before the full build is scoped.
Signs you are ready
You cannot judge the proposal from words alone
The brief describes deliverables, but the commercial direction still feels vague.
The problem may be smaller than a rebuild
A better offer page, intake route or booking path may fix more than a full visual reset.
Several people need to agree
A clickable demo makes internal discussion more concrete than a document.
What Merki builds
A private URL
A no-index page with representative copy, structure and interaction for the decision at hand.
A narrow before-and-after
The demo focuses on the workflow or page that matters most instead of pretending to rebuild the whole site at once.
A scoped next proposal
If the direction works, the demo becomes the reference for a fixed build.
What should improve
- 01Less risk before committing to a rebuild.
- 02A clearer shared target for design, copy and launch.
- 03A smaller first project when the full redesign is not needed.
Questions
Is the private demo the final website?
No. It is a decision artifact: real enough to judge, small enough to change quickly before the full build.
Can the demo become the final build?
Yes, when the direction works. It becomes the reference for the production version.
Related notes