Skip to main content
A business-case page is the buyer-facing version of a deal artifact. It is not the internal deal page. Send it when a buyer needs a clear recap, proof, next step, and supporting material in one place. Business-case pages are part of the standard buyer package with the TLDR recap. The deal page keeps a review card visible so the seller can open the page, check the buyer-facing story, and draft the send email from the same context.

​
Layout

Business-case pages lead with a short title, a concise summary, and the recap video. The title should be skimmable; the page is meant to be forwarded inside the buyer’s company. The default layout places the video beside the headline and summary on wider screens. Theater mode switches to a stacked layout with the title, summary, and video in a larger viewing position.

​
Video controls

The player can support:
  • Theater mode
  • Full screen
  • Picture-in-picture while scrolling
  • Transcript display
  • Copy transcript
The transcript starts collapsed so the page leads with the business case, not raw notes.

​
CTA

The CTA should give the buyer a useful next step. For seller follow-up, use a mailto-style CTA that opens a draft to the seller with a short subject and starter body.

​
Product assets

Some teams have product material that should always be available on a business-case page: calculators, ROI sheets, screenshots, links, one-pagers, or buyer-specific files. Add these as product assets rather than embedding them in the recap video. The video should stay focused; the page can carry the supporting proof.

​
Analytics

Business-case pages can feed engagement back into Yuzu:
  • Page views
  • Video play progress
  • Video completion
  • CTA clicks
  • Link views when the page is shared through a Yuzu Link
Those events can become deal engagement events and influence signal or next actions.

​
Internal vs public

Use the internal deal page for team work. Use the public business-case page for buyers.