Skip to content
Marketing block

Pricing Value Split

The case for the price, made beside the price — what the alternative costs, in the units a buyer already measures.

158 linesNo dependenciesAdded 9 Sept 2026
  • pricing
  • value
  • comparison
  • roi
  • split

What's included

  • components/pricing-value-split.tsx
  • No runtime dependencies

Works with

  • React
  • Next.js
  • Tailwind CSS
  • TypeScript

npx hoverlab add pricing-value-split

Or over MCP, from your editor's agent — no account needed.

License

Free to read, copy and install, for personal and non-commercial projects. Shipping it in client work or a paid product needs Pro ($79 once). The source lands in your repo and stops being ours — no attribution, nothing to upgrade.

Was this useful?

Start a page with this section — add more, order them, and leave with the page source.

Preview

Why this price

Cheaper than the week you would spend instead

A price defends itself against the alternative, not against a competitor's price. The alternative here is engineering time, so that is the unit.

  • One section, hand-builtHalf a day for the markup, another for the responsive and keyboard passes.
  • The same section hereOne command, and the accessibility decisions are already made and explained.
  • Where it stops being closeAround the fourth section. Before that, honestly, build it yourself.
  • What you are not buyingA dependency. The source lands in your repository and stops being ours.

Rendered live in your current theme — this is the same component whose source is below, not a screenshot of it.

Source

components/pricing-value-split.tsx
/**
 * <PricingValueSplit> — The case for the price, made beside the price — what the alternative costs, in the units a buyer already measures.
 *
 * A price defends itself against the alternative, not against a
 * competitor's price. The layout problem is that the alternative is
 * invisible — it is the week somebody would otherwise spend — so the
 * section has to make it concrete before the comparison means anything.
 *
 * The obvious wrong answer is a competitor comparison table. It moves the
 * argument onto price alone, which is the axis where somebody is always
 * cheaper, and it invites the reader to go and check the competitor.
 *
 * So the points are denominated in engineering time, and the third one
 * concedes: below about four sections, build it yourself. That concession
 * is doing the work of the whole block — a value argument with no boundary
 * is read as a sales page, and naming the point where the case fails is what
 * makes the other three credible.
 *
 * The last point is a different kind of claim and belongs at the end: what
 * you are not buying. "The source lands in your repository and stops being
 * ours" is the objection under most of these purchases, and it is the one
 * that has nothing to do with price.
 *
 * Accessibility: the tick is an inline <svg> with `aria-hidden` and
 * `fill="currentColor"`, so it inherits the text colour and is skipped
 * entirely by a screen reader — a decorative tick announced before every
 * point is four repetitions of nothing. The heading carries the section's
 * accessible name through `aria-labelledby`, and the points are a real <ul>
 * so the count is announced up front.
 *
 * The right-hand panel is drawn rather than an <img>: no asset to host, no
 * layout shift while it loads, and it themes with the page. A screenshot of
 * somebody's light-mode dashboard sitting in a dark page is the usual
 * version of this and it is always wrong in one theme. Pass `media` to
 * replace it.
 */

import * as React from 'react'

export interface PricingValueSplitPoint {
  label: string
  detail?: string
}

export interface PricingValueSplitProps {
  eyebrow?: string
  heading?: string
  intro?: string
  points?: PricingValueSplitPoint[]
  /** Your own visual. Omit for the drawn panel, which needs no asset. */
  media?: React.ReactNode
  className?: string
}

const POINTS: PricingValueSplitPoint[] = [
  { label: "One section, hand-built", detail: "Half a day for the markup, another for the responsive and keyboard passes." },
  { label: "The same section here", detail: "One command, and the accessibility decisions are already made and explained." },
  { label: "Where it stops being close", detail: "Around the fourth section. Before that, honestly, build it yourself." },
  { label: "What you are not buying", detail: "A dependency. The source lands in your repository and stops being ours." },
]

/*
  Per-instance id, hashed from the heading.

  The literal id this replaced collided the moment a second page used this
  block: `aria-labelledby` pointing at a duplicated id resolves to whichever
  element is first in the document, so the second copy of the section was
  announced with the first copy's heading. Server component, so there is no
  `useId` available -- hashing the heading gives each instance its own target
  without a hook, a prop or a counter, and stays stable across server and
  client renders in a way a counter would not.
*/
function instanceId(...parts: (string | undefined)[]): string {
  const text = parts.filter(Boolean).join('|')
  let hash = 0
  for (let i = 0; i < text.length; i++) hash = (Math.imul(hash, 31) + text.charCodeAt(i)) | 0
  return (hash >>> 0).toString(36).slice(0, 6)
}

export function PricingValueSplit({
  eyebrow = "Why this price",
  heading = "Cheaper than the week you would spend instead",
  intro = "A price defends itself against the alternative, not against a competitor's price. The alternative here is engineering time, so that is the unit.",
  points = POINTS,
  media,
  className,
}: PricingValueSplitProps) {
  const headingId = `pricing-value-split-heading-${instanceId(heading, eyebrow)}`
  return (
    <section
      aria-labelledby={headingId}
      className={`w-full bg-background px-6 py-16 sm:py-24 ${className ?? ''}`}
    >
      <div className="mx-auto grid max-w-6xl items-center gap-12 lg:grid-cols-2">
        <div>
          <p className="text-sm font-medium text-primary">{eyebrow}</p>
          <h2
            id={headingId}
            className="mt-2 text-3xl font-semibold tracking-tight text-foreground sm:text-4xl"
          >
            {heading}
          </h2>
          <p className="mt-4 text-base text-muted-foreground">{intro}</p>

          <ul className="mt-8 space-y-4">
            {points.map((point) => (
              <li key={point.label} className="flex gap-3">
                {/*
                  currentColor, not a token in a raw colour function. These
                  are complete oklch() values, so hsl(var(--primary)) is not
                  a colour and the declaration is dropped silently.
                */}
                <svg
                  aria-hidden="true"
                  viewBox="0 0 20 20"
                  className="mt-0.5 size-5 shrink-0 text-primary"
                  fill="currentColor"
                >
                  <path d="M16.7 5.3a1 1 0 0 1 0 1.4l-7.5 7.5a1 1 0 0 1-1.4 0L3.3 9.7a1 1 0 1 1 1.4-1.4l3.8 3.8 6.8-6.8a1 1 0 0 1 1.4 0Z" />
                </svg>
                <span>
                  <span className="block text-sm font-medium text-foreground">{point.label}</span>
                  {point.detail ? (
                    <span className="mt-0.5 block text-sm text-muted-foreground">
                      {point.detail}
                    </span>
                  ) : null}
                </span>
              </li>
            ))}
          </ul>
        </div>

        {/*
          The drawn panel rather than an <img>. No asset to host, no layout
          shift while it loads, and it themes with the rest of the page —
          which a screenshot of somebody's light-mode dashboard does not.
        */}
        <div className="rounded-xl border border-border bg-card p-6 shadow-sm">
          {media ?? (
            <div aria-hidden="true" className="space-y-3">
              <div className="h-3 w-1/3 rounded bg-primary/30 border border-transparent" />
              <div className="h-24 rounded-lg bg-muted border border-transparent" />
              <div className="grid grid-cols-3 gap-3">
                <div className="h-14 rounded-lg bg-muted border border-transparent" />
                <div className="h-14 rounded-lg bg-muted border border-transparent" />
                <div className="h-14 rounded-lg bg-muted border border-transparent" />
              </div>
              <div className="h-3 w-2/3 rounded bg-muted border border-transparent" />
              <div className="h-3 w-1/2 rounded bg-muted border border-transparent" />
            </div>
          )}
        </div>
      </div>
    </section>
  )
}

Before you paste

  • Styling is Tailwind utility classes on semantic tokens (bg-card, text-muted-foreground) — it inherits your theme instead of overriding it.
  • Nothing to install. No component library, no icon package.
  • Every prop has a default, so it renders standalone before you wire it up.

Where it goes

Drop it at components/pricing-value-split.tsx and import it where you need the section:

import { PricingValueSplit } from '@/components/pricing-value-split'

Customize

2 of this block’s props are simple enough to drive from here. Change them and the block below re-renders — it is the same component whose source is above, not a mock of it. Everything else it accepts is in the table underneath.

Props

Read out of the component’s own type and signature, so this cannot drift from the source below. Every prop has a default — the component renders standalone before you pass it anything.

PropTypeDefault
eyebrowstring"Why this price"
headingstring"Cheaper than the week you would spend instead"
introstring—
pointsPricingValueSplitPoint[]POINTS
mediaYour own visual. Omit for the drawn panel, which needs no asset.React.ReactNode—
classNamestring—

Not using React?

The same block rendered once to markup, wrapped as a file your framework compiles. Tailwind classes are framework-agnostic, so the design transfers intact — the behaviour does not.

pricing-value-split.html
<!--
  Pricing Value Split — markup from the Hoverlab catalog.

  This is the block rendered once to HTML and wrapped as a component
  file. It is not a port of the React source: the Tailwind classes carry
  the design, which is the part that took the work, and they are the same
  in every framework.

  This block has no interactive behaviour, so nothing is missing.
-->
<section aria-labelledby="pricing-value-split-heading-5go1qh" class="w-full bg-background px-6 py-16 sm:py-24 ">
  <div class="mx-auto grid max-w-6xl items-center gap-12 lg:grid-cols-2">
    <div>
      <p class="text-sm font-medium text-primary">Why this price</p>
      <h2 id="pricing-value-split-heading-5go1qh" class="mt-2 text-3xl font-semibold tracking-tight text-foreground sm:text-4xl">Cheaper than the week you would spend instead</h2>
      <p class="mt-4 text-base text-muted-foreground">A price defends itself against the alternative, not against a competitor&#x27;s price. The alternative here is engineering time, so that is the unit.</p>
      <ul class="mt-8 space-y-4">
        <li class="flex gap-3">
          <svg aria-hidden="true" viewBox="0 0 20 20" class="mt-0.5 size-5 shrink-0 text-primary" fill="currentColor">
            <path d="M16.7 5.3a1 1 0 0 1 0 1.4l-7.5 7.5a1 1 0 0 1-1.4 0L3.3 9.7a1 1 0 1 1 1.4-1.4l3.8 3.8 6.8-6.8a1 1 0 0 1 1.4 0Z"></path>
          </svg>
          <span>
            <span class="block text-sm font-medium text-foreground">One section, hand-built</span>
            <span class="mt-0.5 block text-sm text-muted-foreground">Half a day for the markup, another for the responsive and keyboard passes.</span>
          </span>
        </li>
        <li class="flex gap-3">
          <svg aria-hidden="true" viewBox="0 0 20 20" class="mt-0.5 size-5 shrink-0 text-primary" fill="currentColor">
            <path d="M16.7 5.3a1 1 0 0 1 0 1.4l-7.5 7.5a1 1 0 0 1-1.4 0L3.3 9.7a1 1 0 1 1 1.4-1.4l3.8 3.8 6.8-6.8a1 1 0 0 1 1.4 0Z"></path>
          </svg>
          <span>
            <span class="block text-sm font-medium text-foreground">The same section here</span>
            <span class="mt-0.5 block text-sm text-muted-foreground">One command, and the accessibility decisions are already made and explained.</span>
          </span>
        </li>
        <li class="flex gap-3">
          <svg aria-hidden="true" viewBox="0 0 20 20" class="mt-0.5 size-5 shrink-0 text-primary" fill="currentColor">
            <path d="M16.7 5.3a1 1 0 0 1 0 1.4l-7.5 7.5a1 1 0 0 1-1.4 0L3.3 9.7a1 1 0 1 1 1.4-1.4l3.8 3.8 6.8-6.8a1 1 0 0 1 1.4 0Z"></path>
          </svg>
          <span>
            <span class="block text-sm font-medium text-foreground">Where it stops being close</span>
            <span class="mt-0.5 block text-sm text-muted-foreground">Around the fourth section. Before that, honestly, build it yourself.</span>
          </span>
        </li>
        <li class="flex gap-3">
          <svg aria-hidden="true" viewBox="0 0 20 20" class="mt-0.5 size-5 shrink-0 text-primary" fill="currentColor">
            <path d="M16.7 5.3a1 1 0 0 1 0 1.4l-7.5 7.5a1 1 0 0 1-1.4 0L3.3 9.7a1 1 0 1 1 1.4-1.4l3.8 3.8 6.8-6.8a1 1 0 0 1 1.4 0Z"></path>
          </svg>
          <span>
            <span class="block text-sm font-medium text-foreground">What you are not buying</span>
            <span class="mt-0.5 block text-sm text-muted-foreground">A dependency. The source lands in your repository and stops being ours.</span>
          </span>
        </li>
      </ul>
    </div>
    <div class="rounded-xl border border-border bg-card p-6 shadow-sm">
      <div aria-hidden="true" class="space-y-3">
        <div class="h-3 w-1/3 rounded bg-primary/30 border border-transparent"></div>
        <div class="h-24 rounded-lg bg-muted border border-transparent"></div>
        <div class="grid grid-cols-3 gap-3">
          <div class="h-14 rounded-lg bg-muted border border-transparent"></div>
          <div class="h-14 rounded-lg bg-muted border border-transparent"></div>
          <div class="h-14 rounded-lg bg-muted border border-transparent"></div>
        </div>
        <div class="h-3 w-2/3 rounded bg-muted border border-transparent"></div>
        <div class="h-3 w-1/2 rounded bg-muted border border-transparent"></div>
      </div>
    </div>
  </div>
</section>
  • This is rendered HTML, not a translation of the React source. The Tailwind classes carry the design and work in any framework.
  • It is one frame: the component in its initial state, with no props applied beyond the defaults.
  • Requires Tailwind, and the design tokens the classes reference (bg-card, text-muted-foreground, and so on). The template ZIPs ship a globals.css that defines them.

What each framework gets across the whole catalog — effects convert properly; this rung is markup.

For AI

The component, its props, the design tokens it expects and the command that installs it — as one prompt. Paste it into Claude, Cursor, v0 or ChatGPT and what they build around it will match the rest of the catalog instead of inventing its own system.

See the prompt

Used in these pages

Want the whole screen instead of this one section? Open a page and copy it entire.

7 more blocks in Pricing

All of them free to read, copy and install — no account, no locked tiles, no watermarked preview. The whole catalog is open, and so are the API and the CLI.

Browse Pricing

Shipping one commercially

Copying the code is free. Putting it in client work or a paid product is what Pro is for — the licence, not the access.

  • A commercial licence for everything in the catalog
  • Unlimited bundle exports, in Vue, Svelte and Tailwind
  • One payment — no subscription, nothing to renew
Pro — $79 once

More Pricing blocks

View category
Open the full page for this block

Three-Plan Pricing Toggle

Three plans with a monthly/yearly switch, yearly prices derived from the monthly figure so the two can never disagree.

Pricing192 lines1 dep
Open the full page for this block

Single-Plan Price Card

One price given a whole card, with the objection a one-time price raises answered under the button rather than in a FAQ further down.

Pricing145 lines1 dep
Open the full page for this block

Tiered Usage Calculator

A slider that turns a rate card into the number a buyer actually cares about, with a per-tier breakdown so the total can be checked rather than taken on trust.

Pricing224 linesNo deps
Open the full page for this block

Plan Comparison Matrix

A real table with scoped headers, a sticky first column and screen-reader text behind every check and dash.

Pricing145 lines1 dep
Open the full page for this block

Prepaid Credit Packs

One-time packs with the per-credit price worked out for the reader and the saving stated rather than implied — the pricing shape for a product that sells quantity, not a subscription.

Pricing218 lines1 dep
Open the full page for this block

In-App Plan Picker

A native radiogroup of plans with the current one disabled and the prorated charge announced as it changes — the upgrade dialog, not the marketing table.

Pricing242 lines1 dep
Open the full page for this block

Plan Limits List

What actually runs out on each plan, including what happens when it does — the row a pricing table leaves off.

Pricing149 linesNo deps