When an intake form becomes a barrier.

A form is a negotiation. The business wants information. The person filling it out wants to be done. Every question costs the person something, in time, in trust, or in the feeling that they are being judged, and most forms never ask what each question costs.

This is a note on an intake form I built for a grant-funded program that helps small business owners in San Diego with their websites, online ordering, and digital presence. The owners are busy, many prefer Spanish, and most are filling this out on a phone between customers. The form had to collect enough to prepare for a first meeting without becoming the reason the meeting never happened.

Qualifying versus scaring

There are two kinds of hard questions. A qualifying question filters out people who aren't a fit. A scaring question filters out people who are a fit but don't trust you yet. The same question can be either one, depending on when you ask it and how.

"What are your monthly sales?" is the clearest example. It's useful: it tells you what kind of help the business needs. It's also the question most likely to make someone close the tab. Asked cold, on a page with no context about who is asking or why, it reads as an audit.

So the job is not to remove hard questions. It is to earn them.

What the form does, and why

Who is asking comes first. The program's name, the organization behind it, and the line acknowledging the funder all appear above the first question, not in a footer. An owner should know who is behind the form before they type their name into it. This was the single change with the clearest reasoning: the funder acknowledgment had been sitting at the bottom, below the submit button, where it satisfied a requirement and informed nobody.

Language is a switch at the top, not a buried setting. English and Spanish, one tap, and the whole form changes, including the labels and the hints. An owner who prefers Spanish should not have to read English to find the option.

Revenue is asked gently, and then verified. The sales question offers "your best number is fine" and allows a blank. It is followed by a second question: how did you calculate that? Register, bank deposits, accounting records, an estimate, or "I need help calculating it." That second question turns a number into a piece of information. An estimate and a figure from the register are different things, and the follow-up captures which one you have without making anyone feel caught out.

Progress is saved. A phone rings, a customer walks in, the browser is closed. When the owner comes back, their answers are still there, with a line saying so. On a form for people who are working while they fill it out, this is not a nicety.

One consent line, in plain words. The program reports its results to the funder. The form says that in one sentence and asks for a checkbox. No legal wall, no scrolling agreement.

A way out if the form breaks. If submission fails, the error message includes a link to a plain fallback form. A form that fails silently teaches the owner that the program is fragile, before the program has done anything.

After submitting, one more step, not a dead end. The thanks page says "step 1 of 2" and offers a booking link for the first meeting. If the owner doesn't book, they are still contacted by the channel they chose on the form. The form's job is to start a relationship, not to collect a record.

What is not known yet

The redesign shipped in mid-September, partway through a program cohort. Whether it completes at a higher rate than the form it replaced is being tracked, but the comparison will not be clean: the cohort changed at the same time the form did, and the group is small. Any before-and-after number from this would be suggestive at best, and I'd rather say that than publish one.

What the redesign can claim is narrower: it moved the questions people find hardest behind the context that makes them answerable, and it made the form survive the interruptions its users actually have.

Methods and assumptions

What "completion" would mean. A start is the first field touched. A completion is a successful submission. Drop-off by field is the fraction of starts that stop at each question, which is the only view that tells you which question is the barrier.

Why the before-and-after isn't clean. Different owners, different weeks, a small group, and a form change that coincided with a change in how the program introduced it. A rise in completion could be any of those.

What would change the conclusion. If drop-off still clusters at the revenue question after moving the program identity above it, the context wasn't the fix, and the question itself needs to change or move later.