Self-serve Signup

Trying business software used to mean going through a person first. What sat on the homepage was not the product but a contact form, and filling in a name, a company and a phone number got you a call a few days later. After the call came a demo, and after the demo came a quote.

Theo's search for a new document tool shows the shape of that. He found a product he liked, and the only button on the page was one requesting a demo. He submitted the form, got a call two days later, and was asked about budget and rollout timing. Theo held no budget and was not choosing a company standard. He needed a document tool for that week. Meanwhile he opened the product another team was already using, and four months later that product held 200 of his documents.

Self-serve signup flips the order. Instead of showing the product to someone who has decided to buy, it opens the door to someone who wants to try. The buying decision comes later, made by the person already using it or carried by that person to whoever decides.

Putting nobody at the door is most of it. One email address creates an account, and with no card and no approval step, the next screen is a workspace. Four things make that work.

1. Cut the fields. Questions about company size and job title come out. That information is useful to a sales team, but to someone trying to write a document it is a gate, and every extra line costs completed signups.
2. Collect what you need later. Which company domain someone signed up with, and how many people edit the same document, accumulate while the product is in use. Both beat a survey for accuracy and neither holds anyone up.
3. Don't pull payment forward. Asking for a card during signup cuts completions sharply. The money conversation moves to the point where a limit is hit, which is what usage-based upgrade designs for.
4. Build the first screen with the door. Open the door and do nothing else, and the person who walks in faces an empty page. Four minutes alone with an empty page usually ends with a closed tab, so seeding an example document or writing the first paragraph for them shortens time to wow, the stretch between arriving and being impressed.

The place things break is usually not the signup form but what sits right behind it: a verification email landing in spam, a password rule that rejects three attempts, an extra step confirming a work domain. Fixing those three tends to move more than changing the color of the button.

The result gets read as two segments — the share of visitors who finish signing up, and the share of those who create a first document. Ten thousand visits, 1,000 signups and 340 first documents means the second segment leaks more than the first, and the screen after signup is where the work belongs.

Products with a free plan or a trial are the home case. When the price is published and one person can get value alone, there is little reason to route anyone through a human.

For products counting on bottom-up adoption — one practitioner, then a team, then an organization — this structure is the starting point. The first user has to be the person doing today's work rather than the person who decides, and that person has to get in without waiting for approval. From there, team invite takes over and pulls colleagues along.

Some products are a poor fit. When adoption requires a security review or a contract, or the product only does anything once it is connected to existing systems, signing up alone leaves nothing to do on the first screen. Opening the door there produces accounts and no users, and the signup chart looks healthy while nothing downstream of it moves.

Plenty of companies run both paths. At Pagedeck small teams sign themselves up, and when an account passes thirty active people or starts asking for security documentation, Sofia reaches out. What sales does in that order is closer to converting an organization that already uses the product into a company agreement than to persuading anyone. The call starts from usage data rather than from a pitch, which is why it tends to be shorter than a cold one.

"Let's drop company size and job title from the form. We can get that from the domain later."

Fewer gates, with the information collected inside the product instead.

"Self-serve account, but forty people used it this week. Should this go to sales?"

An account that signed itself up has reached the size where a company agreement makes sense.

"Signups are up and the share creating a first document hasn't moved."

The door got wider while the screen behind it stayed the same.

Pagedeck's signup screen holds one email field and one button. Last quarter Ravi added a field asking for job title, because marketing wanted the data, and over two weeks the completion rate fell from 62 percent to 51 percent.

Mia checked one thing before pulling the field: whether the people who filled it in behaved differently afterward from the people who skipped it. If both groups created a first document at the same rate, the field blocked signups and sorted nothing. In that case it comes out and the same question gets asked on day three inside the product, where more people answer it because they are already using the thing.

The most common conflation is treating self-serve signup and free access as the same idea, which happens because products you can sign up for usually carry a free plan. But this is a decision about who processes the signup, and how money gets collected is a separate one. A product that takes a card up front and starts charging on day fifteen is still self-serve, because no person was involved. Blur the two and a meeting about widening the door turns into a meeting about removing the price.

The other one is assuming fewer fields is always better, since signups rise every time a field comes out. What rises includes signups from people with no intention of using anything. If 1,000 signups become 1,400 while first documents go from 340 to 350, those extra 400 inflated a chart and left behind onboarding email and support replies that cost real money. Counting fields is less useful than reading the pass rate of the segment right after signup, because that is the number a wider door is supposed to move.