"No Credit Card Required" Is a Funnel Tax: A Signup Teardown

Two SaaS products, same category, same price band. One asks for a card on the signup screen. One doesn't. The card-free one wins the metric everyone screenshots for the board deck — and loses the one that pays salaries.

This is a teardown of that trade, and an argument that the standard advice — never ask for a card up front — is cargo-culted from businesses that aren't yours.

Why "no credit card required" is advice borrowed from the wrong business

That line entered SaaS folklore through consumer and prosumer apps, where a signup is a distribution event. Every free user is a potential share, a potential invite, a potential piece of content. Free users literally produce growth.

If you sell a B2B tool at $20–$100 per seat, a signup is not a distribution event. It's the opening move in an evaluation that ends in a purchase decision made by someone who may not be the person signing up.

The costs of pretending otherwise:

Support load. Non-paying accounts generate tickets, onboarding calls, and "how do I export?" emails with no revenue behind them.
Infrastructure and seat cost. Every dormant trial is a row you're paying to store and a workspace you're paying to run.
Diluted activation data. When your trial population is mostly people who clicked a tweet, your activation and trial-to-paid numbers describe the crowd, not the product.
Founder time. The onboarding call you take with a card-free signup is an hour you didn't spend on the ten accounts that will actually convert.

Friction isn't automatically a bug. Some friction is a filter. The only real question is what it filters out — and whether you'd rather have that answer on day one or on day fourteen.

A teardown of two signup flows that made opposite calls

Flow A — card-free, four fields, instant access.

Headline: "Start your free trial"
Sub: "No credit card required. Cancel anytime."
Fields: work email, password, company name, team size
Button: "Create account"
Card requested on day 14, inside a modal

The shape of this funnel: signup completion looks excellent. Then every column to the right of it sags. Fewer people connect the integration that makes the product useful. Fewer people invite a teammate. Trial-to-paid sits flat no matter how many onboarding emails you write, because the denominator is full of people who never intended to buy anything.

Flow B — card-required, same fields, card on screen one.

Headline: "Start your 14-day trial"
Sub: "Add a card to start. You won't be charged until Day 15, and you can cancel in one click."
Fields: work email, password, company name, team size, card
Button: "Start my 14-day trial"
Pre-charge email three days before billing

The shape of this funnel: signup completion drops. Everyone notices. Then activation, teammate invites, and paid conversion all move up — because the population is now people who chose to put a card down.

Here's the part that gets skipped in most teardowns: Flow B is not automatically better. It's better when your product proves value in one session and your buyer is a business. It's worse when your growth depends on free users sharing, when your price is low enough that a card is a bigger decision than the product, or when you have a marketplace with a supply side to fill.

The real failure isn't Flow A. It's running Flow A while measuring the wrong thing — which is what most teams do. If you want to know which flow you're actually running, run a free audit on your signup flow and look at where the drop-off sits relative to the card moment.

The two numbers that decide it (a one-afternoon playbook)

Stop arguing about this in Slack. Go get two numbers.

Number one: paid accounts per 1,000 signup-page visitors, measured at 60–90 days.

Not signup completion. Not trial starts. Paid accounts, divided by visitors who actually saw the signup screen. This is the only number that card-required and card-free can be compared on, because it's the only one that includes the people who bounced at the card field.

Number two: cost to serve one non-paying account for 30 days.

Add up infra cost, support minutes, and the founder hours you spend on calls with trials that never convert. If you can't compute it, estimate it with one support ticket's fully loaded time cost. You don't need precision; you need a number that isn't zero.

Then:

Write both numbers on one line. That's your baseline.
Switch the policy for a full four-week window. Don't A/B test it across users on the same day — the two groups will differ by traffic source and intent, and you'll be measuring the ad campaign, not the card field.
Compare 60-day paid accounts per 1,000 signup-page visitors, not week-one signups.
Keep whichever wins. If it's a tie, keep the card-free version and spend the recovered effort on activation.

When the advice flips, keep the card off the screen: consumer apps with a sharing loop, products with a real network effect where a non-paying user creates value, anything under roughly $10/month, and marketplaces that need supply before demand.

The signup screen rewrite: what changes when the card stays

If you're keeping the card, the entire screen has one job: make the card feel like a formality, not a purchase.

Before

H1: "Start your free trial"
Sub: "No credit card required. Cancel anytime."
Fields: work email, password, company name
Button: "Create account"
Card requested on day 14 in a modal

Three things are broken