How Should a Webflow or Framer Freelancer Show Client Sites, Templates, and Cloneables?

A Webflow or Framer freelancer should separate approved client sites, marketplace templates, and public cloneables, then describe their exact role and link each project to the strongest stable proof.

A live site can prove visual quality but may no longer reflect the version you delivered. A template page proves a reusable product, while a cloneable can expose implementation. One portfolio page should explain those differences before a prospect opens any platform.

Which Webflow and Framer projects should be included?

Include approved client launches, original templates, useful cloneables, and public experiments that demonstrate the kind of work you want to sell.

Treat one client website as one project even if you handled design, CMS structure, animation, and launch. State those responsibilities in the description instead of splitting ordinary delivery phases into separate cards.

Exclude unmodified template practice and any client work you cannot reference. A confidential build can become an anonymised case only when the agreement permits enough detail to make it meaningful.

What is the fast way to create the freelancer portfolio with IndieShow?

The fast way is to claim an IndieShow page, add one card per client site or reusable product, and order the cards by relevance and current status.

Use the tag for a clear category such as Webflow build, Framer template, or cloneable. Describe the problem, your contribution, and current state, then point to the live site, marketplace listing, cloneable, or approved case study.

IndieShow's editor and live preview let you update the page after a redesign, domain change, or new template launch while keeping the same link in proposals and platform profiles.

Build your IndieShow pageClaim your handle, organise the evidence in the editor, then review the $15 one-year and $30 lifetime publishing options in the dashboard.

Should a client project link to the live site or a case study?

Use a case study when your contribution needs context, and use the live site when it remains representative, public, and approved by the client.

Record the delivered scope and period because clients can edit their sites later. If the current site no longer resembles your work, do not leave it as unexplained proof.

A template or cloneable should normally link to its maintained product page. Avoid creating duplicate cards for the listing, preview, and source when they all describe the same product.

How do you show outcomes without inventing conversion claims?

Explain the design or implementation outcome and publish performance or conversion numbers only when the client approves them and you can support the comparison.

Useful evidence can be the delivered CMS, responsive implementation, migration, component system, or interaction you owned. These details remain factual even when commercial analytics stay private.

Leave the optional IndieShow metric blank rather than turning an estimate or testimonial into a statistic. The destination and precise role should carry the case.

Why is IndieShow useful for a Webflow or Framer freelancer?

IndieShow is useful because it places client work, templates, cloneables, work in progress, and archives under one maintained personal URL without moving the projects from their platforms.

Audit links from a signed-out mobile browser, replace stale previews, and move retired templates or superseded client work to Archived with honest descriptions.

The resulting IndieShow page is a compact sales index: the prospect sees what each item proves before choosing which live site, listing, or case to inspect.