Role: Frontend and CRO

Pulse is a sample product. It replaces a daily meeting with a short AI summary of what the team is working on, blocked by, and shipping. The page is a portfolio example, separate from the session signup, the benefits briefing, and the injury evaluation.

The first screen has one job: a team starts a free workspace. The digest card is the proof. A second link opens the same sample inside the product section. Pricing stays further down, with a monthly and annual price that updates in place. The email never leaves the browser.

The friction

A SaaS page that leads with a feature list asks a visitor to imagine the product. A standup tool is easier to judge when the morning digest is already on the screen. Asking for a credit card, a team name, and an integration before that digest exists adds steps a free plan does not need.

The opportunity

Show one digest, then ask for a work email. Keep the meeting-notes comparison, the status filters, and the price toggle on the page for someone who needs the reason. The free plan is the action. The Team plan is the later seat price, not the first ask.

How we measure it

• pulse_view against pulse_cta. That shows whether the hero, the price table, or the sticky bar earned the click.
• pulse_trial_start. That is the workspace. The email stays in the browser.
• The sample figures on the page are labeled as a sample team. They are not a customer result.

This page is a sample, so the rate is named here and not published as a result. Form data is kept for demonstration purposes only and will not be sold or shared.

How someone else reuses it

Copy the Pulse folder. Edit the digest, the plans, and the questions in the HTML. Leave the layout. The form does not post the email.