The sign-up wall, removed
Let them in first, verify later.
Measured before and after, with the effect kept separate, not as a clean A/B test.
Context
On MakerVerse a customer uploads a CAD part, gets an instant auto-quote and can order online. But saving a quote or placing an order sat behind a sign-up. I owned the registration funnel: everything between a visitor arriving and a usable account.
Someone who uploads a part has shown more intent than any ad click. The leak was worth about €760k in pipeline.
Question
Could we keep the people who had just uploaded a part, without buying more traffic?
Diagnosis
About 72% of people who uploaded a part dropped before they got through sign-up. The leak sat right after the highest-intent action on the site.
The funnel isolated the leak to the sign-up step, not the quote or the upload.
Recordings showed people stalling at account creation.
Two mandatory fields had no use downstream.
Upload-led sign-up converted about 10× better than the standalone “Sign up” button, so the fix belonged on the upload path.
Decision
The wall was premature, not necessary. I chose the cheapest credible fix: fewer fields, and email verification moved to the order.
SSO and passkeys promised bigger lifts, but they were multi-sprint builds; I kept them on the roadmap. Progressive access shipped in one sprint, was easy to reverse, and isolated one change so the result could be read.
Before the build, I flagged the risk of deferring verification in writing.
Delivery
- Two fields cut that Sales confirmed weren’t needed.
- Email verification moved from sign-up to Place Order: unverified users can upload, quote and explore.
- Billing, VAT and address captured in context at the order step.
- Mixpanel events defined so the move could be measured.
I wrote the proposal, recorded a Loom walkthrough and built a clickable Figma prototype; a partner engineering team built it.
Impact
Sign-up volume rose 41% in one sprint, and sign-up conversion went from 19% to 24%. It held for about seven months, so it wasn’t a launch spike.
Reflection
The win was real, and it created the debt I’d predicted.
Password reset broke for accounts that had never been verified, and unverified access invited throwaway accounts; the team later capped them at 5 open transactions. Next time I’d ship the guardrails with the friction removal, and run a persistent hold-out control.
A deferred wall doesn’t disappear. It relocates.