Metrics Spotlight

About this block

Metrics Spotlight opens with a two-column grid. The left column holds a company name in a small semibold label, a heading that states the core outcome in one line, and a short narrative paragraph beneath it. The right column is a divided stat rail: three cells separated by thin borders, each showing a large numeric value and a one-line descriptor below it. Below the grid, a full-width ruled figure carries an oversized blockquote followed by an avatar, a name, and a job title.

The company name, heading, and paragraph are all independent copy fields. The stat rail takes any three numbers with short labels, and the quote figure can be rewritten or removed without affecting the grid above. The grid and quote section are separate layout regions, so you can also drop the figure entirely if you only need the narrative and numbers.

When to use

Use this block when a single customer story deserves more than a card but the page does not need a full narrative layout. It works well on a developer tools marketing site where one flagship customer result can anchor a section, and a direct quote from a growth or engineering lead adds credibility without requiring a separate testimonial block. It is a better fit than a story grid when you want depth on one story, and a better fit than a split layout when three distinct metrics matter more than a second prose column.

A natural flow around it on a Marketing Pro page:

Before

• A Heroes block to establish the product promise before proof arrives
• Features to show what the product does so the metrics have context

After

• Story Grid to follow up with a set of shorter supporting stories from other customers
• A CTAs block to convert readers who are persuaded by the result

What you can display

The block is built for a single flagship customer with quantified results. A few other ways to use the frame:

• Developer adoption metrics. Show time to first deployment, number of integrations shipped, or engineering hours saved to speak directly to a technical buyer.
• A team efficiency story. Lead with the headline outcome in the narrative column and back it up with three process metrics in the stat rail, such as cycle time, review rounds, or release cadence.
• A rollout narrative. Use the paragraph to describe how the product was adopted across a company, with the stats tracking speed of rollout, teams onboarded, and workflows replaced.

Tip: keep each stat label to five or six words so the cells stay balanced at all viewport widths and nothing wraps to a second line.