[drop_cap]T[/drop_cap]he signup form looks like the last obstacle before a trial starts. It is not. It is a routing decision wearing a form’s clothes — every field you put on it either helps you decide where this account should go next, or it is friction with no job to do. Most B2B signups are built by asking “what do we want to know about this person,” which is the wrong question. The right one is “what has to be true before we can route them correctly,” and the answer is almost always shorter than the form in front of you.
This is Stage 3 of the ATTRACT band: Identify. The Hook and Gift earned attention; Identify turns that attention into an account, with exactly enough structure to route it — self-serve or sales-assisted, high-fit or low-fit — without a call, a demo, or a guess.
Every Field Is a Toll Booth
Signup completion does not decline in a straight line as you add fields. It holds, then falls off a cliff at whatever point a founder or an evaluator on their lunch break decides this is taking too long for something they can try somewhere else in thirty seconds. Company size, job title, “what’s your biggest challenge,” a phone number nobody’s going to call — every one of these has a business case attached to it in a slide deck, and every one of them is a chance for someone to close the tab instead.
The minimum viable SaaS signup is close to three fields: work email, password (or an OAuth button that skips the password entirely), and a workspace name. That’s what it takes to create the account and let them into the product. Everything else you actually need — company size, use case, team size, how they found you — you can get after they’ve seen the product do something, when answering costs them nothing because they’re already in and already invested.
Progressive Profiling: Ask After Value, Not Before
The rule is simple to state and constantly violated in practice: ask for information at the moment it unlocks something for the person giving it, never before. A signup form that asks “how many people are on your team” before the person has seen the product is asking them to do work on faith. The same question asked while they’re inviting teammates from inside the app is asking them to do work they were already about to do.
Build the profile in layers, each one earning its keep:
- At signup — work email, password/OAuth, workspace name. Nothing else.
- First session, in-product — a use-case picker shown after the empty state, framed as “what are you trying to do” rather than “tell us about your company.” This one field, asked at the right moment, does more routing work than five fields asked too early, because it’s answered by someone who’s already committed.
- On the action that needs it — company size and role surface naturally when someone tries to invite a teammate, connect a paid integration, or hits a usage limit. The form appears exactly where the person already understands why you’re asking.
A signup form and a fully profiled account are two different artifacts built at two different times. Confusing them is the single most common way a SaaS company loses signups it should have kept.
The Work Email Question
Asking for a work email and quietly rejecting Gmail, Yahoo, and the rest is common practice, and it is worth being honest about what it does and doesn’t do. It filters out a share of low-intent personal-project signups and gives you a domain to match against a company database for firmographic enrichment without asking a single extra question. That’s real value, and it’s why the practice persists.
It also costs you every freelancer, every solo consultant, every founder of a two-person company who hasn’t set up a business email yet and isn’t going to stop and do it just to try your product. If your ICP includes any of those people, a hard block on personal domains is rejecting exactly the segment you’re trying to reach, in the name of a filter that was built for a different buyer. The honest move is to know which one you are: if you sell exclusively to companies past the point where everyone has a corporate address, block personal domains and route on the resulting domain match. If your ICP includes solo operators or very early-stage teams, don’t block — let a personal-domain signup through and use the email pattern only as a low-weight signal in scoring, not a gate.
The Routing Question: Who Goes Self-Serve, Who Gets a Human
Every B2B SaaS company with more than one price point eventually faces this question, and most answer it too late — after a $50k-ARR prospect has been left to click through a self-serve trial alone, or after a two-person startup has been assigned an account executive who spends thirty minutes qualifying a deal that was never going to be worth the call. The routing rule has to be decided before the signup form is built, because the fields you collect are what make the rule possible to apply automatically.
Three signals, gathered without a single extra form field, do the routing:
| Signal | Where it comes from | What it tells you |
|---|---|---|
| Company size | Enriched from work-email domain, or the in-product use-case/team-size question | Deal size ceiling — a 3-person team and a 3,000-person company are not shopping for the same thing |
| Stated use case | The in-product picker shown after first value, not the signup form | Whether the need matches your core product or a smaller edge case |
| First action taken | Product usage — did they connect data, invite a teammate, hit a paid-feature wall | Intent, measured by behavior instead of by what they claim |
Build a simple decision table from these three, filled in with your own thresholds:
Company size ≥ X employees AND first action = [connected data / invited team]
→ route to sales-assisted (human outreach within Y hours)
Company size < X employees AND first action = [explored solo, no invite]
→ route to self-serve (automated onboarding sequence, no human touch)
Company size ≥ X employees AND first action = none within Z days
→ route to sales-assisted anyway — a stalled large account is worth
a human nudge that a stalled small account is not
Fill in your own X, Y, and Z from your actual close rates and your actual sales capacity — a company with three reps cannot afford the same threshold as one with thirty. The shape of the rule matters more than the exact numbers: size sets the ceiling on what the deal is worth, and behavior tells you whether there’s a deal to chase at all. Neither signal alone is enough — a big company that never logs in isn’t a self-serve win waiting to happen, and a small company that connects every integration on day one might be worth more attention than its size implies.
Fit Scoring and Intent Scoring Are Not the Same Thing
The two get merged into one number more often than they should, and the merge is where sales ends up working the wrong accounts. Fit answers “is this the kind of company we can serve well” — company size, industry, tech stack, use case. It’s mostly static; it doesn’t change much between signup and week four. Intent answers “is this account behaving like it’s about to buy” — logins, invited teammates, features used, limits hit. It moves daily, sometimes hourly.
A high-fit, low-intent account is a good company that hasn’t found the product yet — the right response is nurture, not a call. A low-fit, high-intent account is someone using your product hard for a job it wasn’t built for — the right response is often to let them self-serve cheaply rather than spend a rep’s time on a deal that will never expand. The account that deserves a human today is high-fit and high-intent, and collapsing the two scores into one composite number is exactly how that distinction gets lost — a high-intent freelancer and a high-fit-but-quiet enterprise account can land on the same score and get the same treatment, when they need opposite ones.
AI Earns Its Place Here
This is where AI drafts the whole opt-in sequence from your inputs: your ICP definition, your actual plan tiers and their price points, your product’s core use cases, and your brand voice. Ask for the signup form copy (field labels, the one line of microcopy explaining why the form is short), the in-product use-case picker’s options and framing, and the routing rule’s plain-language version — the same decision table above, filled in with your numbers and written so a new sales rep can read it and know exactly which accounts land on their desk.
Feed it your real thresholds — your actual deal-size ceiling for self-serve, your actual rep capacity, your actual definition of a “connected” account — so the routing rule it drafts matches what your team can actually execute, not a generic SaaS playbook average. Then edit the way you’d edit anywhere else in this playbook: the model can hold the shape of a clean, short signup and a defensible routing rule, but only you know whether your rep capacity supports the threshold it just proposed.
What’s Next
A signup that asks little and routes accurately hands you an account that’s already sorted — self-serve or sales-assisted, worth a human’s time or not yet. That account now needs to actually get somewhere in the product, fast enough to feel the value before it drifts. That’s Stage 4, Engage — the start of the Convert band, where identification turns into activation.