How this checklist was built
Teardowns of other companies' pages go stale within a quarter and tend to reward whoever redesigned most recently. This guide does something plainer. It lists what a trial signup page has to contain, and for each item it points to a public source: Stripe's documentation for the trial and payment mechanics, ChartMogul's January 2026 study of 200 software products for the market numbers, and web.dev's guide for the form itself. No company's page is judged, and no company is named as a good or bad example. If a check below does not fit your product, the source tells you why it exists so you can decide for yourself.
The checks run in the order a visitor meets them. Use them as an audit: open your own page on a phone, tick or fail each row, and fix the failures from the top, because a problem near the top costs you more visitors than a problem near the bottom.
| Check | What to look for | Where it comes from |
|---|---|---|
| 1. The offer | Trial length, plan and what is included, in one sentence near the headline | Stripe trial documentation, ChartMogul trial length data |
| 2. The card decision | A deliberate choice to ask for a card or not, with the end of trial behavior set to match | ChartMogul, Stripe Checkout free trials |
| 3. Price and dates beside the button | The amount, the first charge date and how to cancel, where the eye lands | Stripe emails and reminders, ChartMogul |
| 4. A short form | Only the fields you need, labels, autofill and the right keyboards | web.dev |
| 5. Payment methods | Wallets and saved details offered where the buyer has them | Stripe Payment Element |
| 6. Errors | Messages that say what to change, shown beside the field | web.dev, Stripe declines |
| 7. The next screen and email | What happens now, and the first email before the first session | Stripe trial events and emails |
| 8. A number to watch | Visitor to trial rate and trial to paid rate, defined and cohort based | Metrics glossary |
Check 1: state the offer in a sentence
A visitor should know the length of the trial and the plan it covers before reading anything else. Stripe allows trials of up to two years in Checkout but says most businesses choose shorter ones, and it names two problems with long trials: payment methods that expire before the first charge and lower conversion. ChartMogul's study gives the market picture. Among the products studied, a 14-day trial is the one most often picked, at 62% of products, ahead of 7 days at 14% and 30 days at 14%.
Those figures describe what other products picked, not what converts best, so use them as a starting range and test from there. What matters on the page is that the number of days appears once, clearly, and that it is the same number the checkout and the confirmation email use. A page that says 14 days above the fold and a checkout that quotes 7 loses trust at the moment of payment.
Check 2: make the card decision on purpose
ChartMogul found that 20% of free trial products require a card up front and 80% do not. It reports a free-to-paid conversion of 30% for trials that require a card, against a median of 8% across all 200 products. The same report warns that a card requirement can reduce signups, so the right comparison is paying customers per thousand visitors, not conversion among those who signed up. The trial to paid conversion rate guide works through that arithmetic.
If you skip the card, Stripe makes you choose what happens when the trial ends without one. In Checkout and on subscriptions the missing payment method setting can cancel the subscription, pause it, or create an invoice that moves the subscription to past due if unpaid. Pick the behavior on purpose. A paused subscription keeps the relationship alive and lets the customer add a card later on a hosted page; a canceled one means starting over.
Check 3: put price and dates beside the button
The line directly above or below the signup button is the most read text on the page. It should carry the amount that will be charged after the trial, the date of the first charge and a way to cancel. Writing the actual date rather than "after your trial" removes arithmetic from the buyer. ChartMogul observes that the best companies earn trust by being open about how and when users can cancel, for example by promising a reminder 7 days before a trial ends. It adds that companies which are not open risk fewer trial signups, worse retention in months one to three and more refund requests from people who forgot to cancel.
Back the promise with the mechanics. Stripe can send a trial ending reminder 7 days before the end, and the reminder can point to a page on which the customer adds or replaces a card. Stripe also emits a trial will end event a few days before the trial moves to active, which is your cue to confirm a payment method exists and to send your own notice.
Check 4: keep the form short and let the browser fill it
web.dev's payment and address form guide is a checklist in its own right, and most of it applies to a trial form unchanged. Use a real form element with a label on every field. Do not rely on placeholders as labels, because they vanish as soon as the person types. Use the autocomplete attribute with the right values so browsers can fill name, email and card details. Avoid number inputs for card numbers, and use a text input with a numeric input mode instead. Ask for a name in a single field, do not ask for data you do not need, disable the submit button after the first tap, and validate while the person types rather than only on submission.
The guide also recommends descriptive button labels that show progress, and it advises testing in the field as well as in the lab, using page analytics, interaction analytics and real-user measurements across a range of browsers and devices. A trial form that works on your laptop and stalls on a mid-range phone is the most common hidden loss in a signup flow.
Check 5: offer the payment methods people already have
Stripe's Payment Element shows wallet options such as Apple Pay and Google Pay when the visitor has a card in that wallet, and it can offer saved details through Link. For a trial this is more than convenience, because a wallet payment replaces typing sixteen digits on a small screen. Stripe also notes that you can combine the Payment Element with an express checkout button, in which case wallets appear in the express button to avoid duplicates. Whatever you choose, confirm with your processor that every method you display can be used for a trial that charges later, because not every payment method supports a separate authorization or a saved charge.
Check 6: write errors that say what to change
A declined card on a trial page is a customer-facing event, not a log line. Stripe's decline guidance separates issuer declines from blocked payments and invalid requests, and the message you show should reflect the difference: a wrong security code is fixed in a second, an issuer decline needs another card, and a technical error needs a retry and a way to reach you. Put the message beside the field it concerns, keep the typed values in place, and never clear the form. If you hold the card at signup, a failed hold is your earliest and cheapest decline, so spend design time on it. The failed payments guide covers what to do after the trial starts.
Check 7: plan the screen and email after the click
The confirmation screen should repeat the offer in the same words as the page: plan, trial end date, first charge amount and date, and where to cancel. The first email should arrive before the first session and do two jobs, confirming the same facts and pointing to the one action that shows the product working. Everything after that belongs to onboarding, which is a separate subject, but the facts on the confirmation screen are part of the page, because they decide whether a buyer feels informed or tricked a fortnight later.
Check 8: pick the number you will watch
Two numbers describe a trial page. The visitor to trial conversion rate shows whether the page persuades. The trial to paid conversion rate shows whether the trial pays. Change the page and you will usually move both, in opposite directions if you add friction. Measure each by cohort, with the start week fixed, so a good week is not blended into a bad one.
The trial conversion rate calculator shows what a change is worth in customers. At its defaults it reads a rate of 15.0% and shows that adding 5 points would add 20 paying accounts and $980 of MRR a month. Enter your own trial counts and price to see your own version, and treat the output as arithmetic about your funnel, not as a forecast of what any page change will achieve.
Putting the audit to work
- Open your page on a phone and fail or pass each of the eight checks. Write the failures down in the order above.
- Fix the offer sentence and the line beside the button first. They are cheap and touch every visitor.
- Compare the form against the web.dev list and fix the missing labels, autocomplete values and input modes.
- Decide the card question on paper, with the end of trial behavior, before you change the page.
- Set up the trial ending reminder and the confirmation email so the promise on the page is kept.
- Record the visitor to trial rate and the trial to paid rate by start week, and change one thing at a time.
Is this a teardown of other companies' pages?
No. It lists what a trial page needs and cites public documents for each point. It does not rate or name any company's page.
Should every trial ask for a card?
Not necessarily. The reported conversion is higher with a card, but signups can fall, so compare paying customers per thousand visitors before deciding.
How long should the trial be?
The most common length in the ChartMogul study is 14 days. That is a market fact, not a rule, so test lengths against your own time to first value.
Where should the price and renewal date go?
Directly beside the signup button, with the actual date of the first charge and a plain way to cancel.
How often should I audit the page?
After any change to the offer, the form or the payment methods, and on a calendar every quarter.
Sources
- ChartMogul: The Conversion Report, read 19 Oct 2026
- Stripe: Configure free trials for Checkout, read 19 Oct 2026
- Stripe: Configure free trials on subscriptions, read 19 Oct 2026
- Stripe: Automate customer emails, read 19 Oct 2026
- Stripe: Payment Element, read 19 Oct 2026
- web.dev: Payment and address form best practices, read 19 Oct 2026