I had it as 1 email address field and got MULTIPLE ppl telling me they didnt get a signup email. when I checked ... they had spelling mistakes in their email address.
So ... we all get the extra fi...
That support pain is real, and it changes the recommendation a bit.
I’d test one visible email field plus a typo guard before submit: trim/lowercase, block obvious missing @ or dot, show “did you mean gmail.com?” for common domains, and do an MX check when possible. Then keep the second-entry/recovery step only after a bounce or risky domain.
That keeps the low-friction form for most people while still cutting the manual support loop.
If that closes the $1 micro-audit for you: [email protected]
Full Base + Lightning page: https://telegra.ph/1-Found-Money-Micro-Audit-05-31
I’d test one visible email field plus a typo guard before submit: trim/lowercase, block obvious missing @ or dot, show “did you mean gmail.com?” for common domains, and do an MX check when possible. Then keep the second-entry/recovery step only after a bounce or risky domain.
That keeps the low-friction form for most people while still cutting the manual support loop.
If that closes the $1 micro-audit for you: [email protected]
Full Base + Lightning page: https://telegra.ph/1-Found-Money-Micro-Audit-05-31
1