Every field you add costs you signups

Most teams will argue for a week about the headline and then let the signup form become whatever anyone asked for that quarter. Someone in sales wanted company size. Someone building the onboarding wanted a role. Someone wanted a phone number, once, for a campaign that ended eight months ago. Nobody ever argued for those fields, and nobody has ever removed one. Meanwhile the form is the narrowest place in the whole path — the exact spot where somebody who already decided to try your product can still change their mind.

The reason it hides is that the cost never shows up as a cost. Nobody writes to tell you they abandoned your form on the fourth field. They just stop, and the visit goes into the same pile as everyone who bounced off the headline. From the report, a person who read every word, agreed with all of it, and gave up when you asked for their phone number looks identical to a person who never scrolled.

Pricing a field

Run the arithmetic as arithmetic, with numbers you invent, because the point is the shape and not the precision. Say a thousand people reach your page in a month and 220 of them start filling in the form. If the form has three fields and 150 people finish, you got 150 signups. Now suppose — purely as an illustration — that each additional field costs you five percent of the people who started. Add three more fields and roughly 128 finish instead. That is 22 signups a month, 264 a year, traded for a company-size dropdown that nobody has filtered a list by since it was added.

Reverse it and the trade gets uncomfortable in a useful way. If you were told that removing three fields would produce twenty extra signups a month, would you do it? Almost certainly yes, and for free. It is the same decision, facing the other direction. We are simply much worse at noticing a cost that arrived gradually than at noticing a gain offered today.

The test that survives the meeting

For each field, ask one question: who reads this, and what do they do differently because of the answer? Not what it might be useful for someday — what happened last month. If it fed a segment, kept a salesperson from wasting a call, or changed what the first email said, it earned its place. If the honest answer is that it sits in a column somebody exports twice a year and looks at once, it is not a field, it is a tax on everyone who wanted to try your product.

The strongest answer to a field that cannot pass is usually not delete but later. You do not have to choose between knowing nothing and asking everything at the door. Ask for the role on the first screen after the account exists, when the person has already committed something and has a reason to expect a question. Ask for the phone number when they book a call, where it is obviously for them rather than for you. The same question at a different moment gets answered instead of abandoned, because by then you have given them something.

the cheapest lead is the one you never had to disqualify

When more fields is the right call

There is a real case for a longer form, and it is worth stating plainly instead of pretending short always wins. If your product is expensive, sold by a human, and you can only work through a handful of conversations a week, then forty people you can qualify beat a hundred and forty you cannot. The extra fields are doing work — they are the filter that decides whose call gets returned. Nobody on that team should feel bad about asking.

The deciding question is what waits on the other side. If a person is going to read each submission, longer is defensible. If the submission drops into an automated welcome sequence, every field past the ones that sequence actually uses is pure loss. Most self-serve products are firmly in the second case while carrying a form designed for the first, usually because the form was written back when a founder really was reading every single one.

The costs that are not fields at all

Some of the damage has nothing to do with how many things you ask for. A required marker on a field that could be optional turns a small annoyance into a wall. A phone input that rejects the way half the world writes phone numbers sends people away convinced they made a mistake. Errors that only appear after submitting, and helpfully clear what was already typed, are the single most reliable way to lose somebody who was trying to give you money. A password rule nobody can satisfy on the first attempt costs you people who were, at that exact second, sold.

Then there is the quiet one: rejecting anything that is not a work email. It is a defensible policy for some businesses and a silent filter in others, and either way it should be a decision someone made on purpose rather than a default that came with the form.

Two numbers, one week

You cannot fix this from a signup count alone, because that number compresses the whole path into a single figure. Measure two things instead: how many people started the form, and how many finished it. The gap between visits and starts tells you about the page — the headline, the price, the proof. The gap between starts and finishes tells you about the form, and it is usually the one nobody has looked at.

We will show you the signups that reach us, whether that is through an analytics tool you connected or events your site sends us directly, and we can tell you plainly when a week is worse than the week before. What we cannot see is the person who typed their email, hit the fourth field, and closed the tab. That happens entirely on your own page, so the measurement has to start there, and it costs about fifteen minutes to set up.

So here is the rule we would keep if we could only keep one: a form should ask for exactly what you will use this month, and every other question should move to a screen that comes after the account exists. And here is the version you can act on this week — count starts and finishes for seven days, remove the field you had the hardest time justifying, then count for seven more. If nothing changes, you lost a field you did not need. If something does change, you just found the cheapest growth available to you, and it was sitting inside your own page the whole time.