neilstancliff

I've looked at analytics for a bunch of web apps recently, and the drop-off pattern is almost always the same: huge chunk of users disappear right after signup, before they even reach the core feature. Not because the product is bad, but because the onboarding design wasn't actually designed, it was just whatever screens got built last. Too Many Steps Before ValueMulti-step signup forms, email verification, a tour popup, a "complete your profile" nag screen, and only then does the user finally see what the app actually does. Every extra step between signup and the first meaningful action is a chance for someone to bounce. The apps that retain well usually get users to one real "aha" moment fast, everything else can wait. Generic Tours Instead of Contextual GuidanceThose slideshow-style product tours at first login? Most users click through them without reading a word. What actually works better is contextual guidance, small hints that show up exactly when a user reaches a relevant part of the interface, not all dumped on them at once before they've done anything. Empty States Left as an AfterthoughtNew users almost always land on empty dashboards, empty project lists, empty everything. If that empty state is just a blank page with no direction, users don't know what to do next. A well designed empty state should tell the user exactly what action to take first, not just sit there looking unfinished. No Clear "First Win"Good onboarding design maps out one specific action that proves value fast, whether that's creating a first project, connecting an integration, or seeing a real result from their own data. If that path isn't intentionally designed, users wander and eventually give up. This is honestly one of the most underrated parts of the design process. We map out onboarding flows as their own dedicated stage on most projects now, Our approach to web app UI design touches on how we structure this alongside the rest of the UX work. Would be curious if anyone's run A/B tests on onboarding steps and actually seen the drop-off improve. What moved the needle for you?

Been going back and forth on this for a client project and wanted to get some outside perspective from people who've been on either side of this. We got quotes ranging from around $1,500 to $9,000 for what looks like the same 8-page business site on paper. Rather than assume the higher number is just padding or the lower one is a red flag, I wanted to understand what specifically drives that kind of gap. From what I've gathered so far, the biggest factors seem to be: Custom design work vs. a pre-built theme with light customization Number of unique page templates (not total page count) How many revision rounds are baked into the quote before extra charges kick in Whether content/copywriting is included or billed as a separate line What happens after launch maintenance retainer, and who owns the CMS/source files I came across a fairly detailed breakdown by pricing tier that lines up with most of this, but I'd rather hear it from people who've actually quoted or been quoted for real projects. For anyone who's run an agency, freelanced, or just been burned by a quote that didn't match what got delivered what's the one thing you'd tell someone to check before signing, besides the total price?

Not going to ask more questions, you've made it clear what you want, so here it is directly. I do full website UI/UX rebuilds, concept through launch, with a focus on making sites feel distinct rather than templated. Domain/hosting sites in particular tend to look nearly identical to each other, so there's real room to stand out if that's the direction you want to take it. You can see some past work about this space in www.pixxen.com/services/website-design/ if you want a sense of the style I'm talking about. If you want to send over the site, happy to put together a quick concept direction for you to react to, no pitch deck, just something visual to look at.