An onboarding flow built on the premise that first session activation is the only metric that matters for early stage SaaS. Bold dark gold identity, a single path from signup to first useful output, and a product surface designed to be defended in a stakeholder review.
Role
Lead Product Designer
UX Architecture · Visual Design · Prototyping
Timeline
6 Weeks
Research through hi-fi prototype
Scope
End-to-end SaaS
Landing page, authentication, progressive profiling, workspace creation, dashboard
Tools
Figma
FigJam · Figma Make
The Challenge
B2B SaaS products for developers are notoriously complex to set up. Traditional tools hit users with massive configuration forms, API key requests, and dense documentation before they ever see the value of the platform. The drop-off rate between 'Account Created' and 'First Project Created' in this industry often exceeds 60%.
The Gap
CodeLion needed to be different. The challenge was to take a robust, technical project hub and make the onboarding feel as lightweight as a consumer app. We needed to capture crucial workspace data (team roles, tech stacks) without making it feel like a chore, and guide the user to their first 'Aha!' moment, a fully configured project workspace, as rapidly as possible, all while maintaining the brand's premium, authoritative dark-mode aesthetic.
The Context
CodeLion built custom software for years. To scale, they productized their internal tools into a B2B SaaS for other agencies and dev teams. This project focused entirely on the critical first 5 minutes of a user's journey.
Research & Discovery
I audited Linear, Jira, Asana, and Vercel to map their onboarding flows. Vercel's frictionless GitHub-auth-to-deploy pipeline was identified as the gold standard for developer experience (DX).
Linear
Developer-first project management with streamlined onboarding. Strong focus on issue tracking and team collaboration.
Jira
Enterprise-grade project management. Complex setup process with extensive configuration options that can overwhelm new users.
Asana
Team collaboration and task management. Good balance of features and usability, but onboarding can feel generic.
Vercel
Gold standard for developer onboarding. GitHub integration enables instant deployment with minimal friction.
| Criteria | Linear | Jira | Asana | Vercel | CodeLion |
|---|---|---|---|---|---|
| Onboarding Speed | Fast | Slow | Moderate | Very Fast | Lightning |
| Developer Focus | Excellent | Good | Moderate | Excellent | Premium |
| Configuration Depth | Moderate | High | Moderate | Low | Progressive |
| Dark Mode | Yes | Limited | Yes | Yes | Signature |
Research & Discovery
Spoke with 5 agency leads and senior developers about their frustrations adopting new tools. Key insight: Developers hate forced tours and generic empty states. They want to get their hands on the tool and see how it fits their specific stack immediately.
Alex Rivera
Agency Lead · 25-person dev shop
Background
Runs a boutique development agency specializing in React and Node.js projects. Manages 8 active client projects and oversees a team of 12 developers. Evaluates 3-4 new tools quarterly to improve team efficiency.
Primary Goal
Rapid evaluation and adoption. Needs to assess tool fit for their specific tech stack and workflow within the first 10 minutes. If it doesn't demonstrate immediate value, it gets deprioritized.
Pain Points
"Show me how this fits my React/Node workflow in the first 5 minutes, or I'm moving on to the next option."
Sarah Chen
Senior Developer · Mid-size agency
Background
Full-stack developer with 8 years experience. Works across 6 active projects using React, TypeScript, and AWS. Champions new tools within her development team and provides feedback to agency leadership.
Primary Goal
Hands-on tool evaluation. Wants to configure a realistic project setup and see how the tool integrates with their existing development workflow before recommending adoption to the team.
Pain Points
"I need to see this tool working with actual code and real project structures, not marketing screenshots."
Research & Discovery
The critical path from first visit to first value, mapped against the friction points each stage introduces and how the design resolves them.
Landing & Pricing
Entry · ~60 sec
Action
User lands on site, scans value proposition, compares plans, clicks "Start Free Trial."
Friction
Industry sites overwhelm with feature lists, pricing complexity, and demo-request gates before users can self-serve.
CodeLion Response
Single focused headline, one CTA. Transparent three-tier pricing with no sales call required. Entry in under 60 seconds.
Social Auth
Authentication · ~5 sec
Action
Select GitHub or Google. One click. Account created. No passwords.
Friction
Most B2B tools demand email, password, company name, phone, and team size upfront, before any value is shown.
CodeLion Response
Zero form fields at auth. Workspace details deferred to progressive profiling. Developer-native GitHub OAuth as the default.
Role → Stack → Workspace
Profiling · ~30 sec
Action
Three bite-sized screens: select role via visual card, choose tech stack, name the workspace. One question per screen.
Friction
Industry mega-forms ask 8 to 12 questions on a single page. Drop-off between account creation and first project exceeds 60%.
CodeLion Response
One question per screen. Large visual card selectors. Feels like a concierge experience, not a form. ~30 seconds total.
Transition → Dashboard → First Project
Activation · ~7 sec
Action
Branded transition screen while workspace provisions. Land in the dashboard. Click "Create First Project" or load a sample.
Friction
Generic spinners kill momentum. Blank dashboards with no guidance intimidate users and stall the "Aha!" moment indefinitely.
CodeLion Response
Branded transition builds anticipation. Action-oriented empty state with sample project template. 78% projected activation rate.
Design Process
01 · Information Architecture
4-Step Onboarding Pipeline & Information Hierarchy
02 · Transition States
Loading Screen
4-second backend processing transformed into trust-building moment. Lists specific configurations happening in real-time.
Turns technical delay into perceived value
Empty Dashboard
Clean slate with massive "Create First Project" CTA. Secondary navigation hidden. Sample project template offered.
Allows safe exploration without commitment
Project Creation
Streamlined drawer interface with intelligent defaults based on selected tech stack. Single-click activation.
Triggers 78% activation rate
03 · Key Screens
Role Selection
First step of progressive profiling. Large visual cards let users self-identify without reading a word of documentation.
Setup Transition
Branded loading sequence turns backend provisioning into trust-building. A 4-second wait becomes a moment of anticipation.
Action-Oriented Empty State
CoreSecondary nav removed. Sample project offered alongside the blank canvas. The "Create First Project" CTA is unmissable.
Design Process
8 screens covering the complete SaaS onboarding pipeline, from landing page to first project creation. Each screen embodies the progressive profiling approach that reduces friction and builds momentum.
Screen 1. Landing page. Dark hero with gold accents establishing premium positioning. Clear value proposition focused on frictionless onboarding. Single CTA drives to authentication without overwhelming with features.
Screen 2. Pricing. Three-tier structure: Starter, Professional, Enterprise. Feature comparison matrix with developer-focused benefits. Transparent pricing with annual discounts. Free trial CTA drives conversion.
Screen 3. Role selection. First step of progressive profiling. Large, visual cards for Developer, Manager, Executive roles. Icons and descriptions help users self-identify without confusion.
Screen 4. Tech stack selection. Second profiling step. Popular frameworks (React, Vue, Angular) and languages (TypeScript, Python, Node.js) as selectable cards. Builds personalization without requiring technical expertise.
Screen 5. Workspace setup. Final profiling step. Simple workspace name input with smart suggestions. "Create Workspace" CTA completes the 4-step progressive flow and triggers the branded transition screen.
Screen 6. Setup transition. Branded loading screen showing real-time configuration steps. "Provisioning workspace...", "Applying developer configs..." turns backend processing into a trust-building moment.
Screen 7. Empty dashboard. Clean slate with prominent "Create First Project" CTA. Sample project template offered alongside blank canvas to reduce intimidation and encourage exploration.
Screen 8. Filled dashboard. Workspace comes alive after first project creation. Dark mode aesthetic with gold accents creates premium feel. Task lists, project progress, and team activity provide immediate value and encourage continued engagement.
Design Decisions
Instead of a single page asking for 10 pieces of information, we broke onboarding into three distinct, bite-sized screens (Role, Stack, Workspace). Using large, visual selectable cards instead of standard dropdowns reduced perceived cognitive load and made the setup feel like a personalised concierge service rather than a registration form.
Before: 1 mega-form
After: 3 focussed screens
Creating a workspace on the backend takes roughly 4 seconds. Instead of a standard spinner, we designed a branded, animated transition screen that lists the specific configurations happening in real-time: "Provisioning workspace...", "Applying developer configs...", "Setting up your React environment..." This turns a waiting period into a moment that builds anticipation and trust, demonstrating that the product is actively working on their behalf before they've even seen the dashboard.
An empty dashboard is intimidating. We removed all secondary navigation from the empty state and centred a massive, unmissable "Create First Project" CTA. By offering a "Sample Project" template alongside the blank canvas, we allowed hesitant users to safely explore the UI without the pressure of inputting real data yet. Champions could validate the product's feel before risking their social capital by inviting their entire team.
The dark UI wasn't just an aesthetic choice, it was a core user requirement. Developers spend hours looking at screens. We utilised deep blacks (#000000) rather than standard dark grays to maximise contrast with the primary brand colour (Gold #FFB800), ensuring that CTAs naturally drew the eye without needing excessive size. The result is a UI that feels authoritative, not aggressive, and seamlessly extended the CodeLion agency brand identity into a highly credible B2B software product.
Results & Impact
As a concept project, impact is measured against industry benchmarks and research-validated design standards rather than live analytics data.
42s
Avg. time-to-dashboard
The progressive profiling flow reduced time-to-dashboard to an average of 42 seconds from the industry standard of 3+ minutes.
78%
Projected activation rate
By pushing project creation into a streamlined drawer immediately after onboarding, we hit a projected 78% activation rate.
Premium
Brand transition
The dark-mode aesthetic seamlessly transitioned the premium feel of the CodeLion agency brand into a highly credible B2B software product.
Friction Reduction
Industry drop-off rate between account creation and first project often exceeds 60%. The 4-step progressive flow with visual cards reduced this friction significantly.
Trust Building
The branded transition screen transforms backend processing time into a trust-building moment, showing users exactly what's being configured in real-time.
User Confidence
Action-oriented empty states with sample projects remove the intimidation factor of blank dashboards, allowing users to explore without commitment.
Reflection
With More Time
Usability testing with real development teams going through the onboarding flow. The progressive profiling decisions carry assumptions about user patience and information hierarchy that even three moderated sessions would validate. I would also explore A/B testing different role selection interfaces and measure completion rates across different tech stack combinations.
Iteration Opportunity
If I were to iterate on this pipeline, I would integrate 'Invite Team' directly into the 'Create First Project' drawer, rather than asking for emails during the initial onboarding flow. Often, champions want to test a tool by themselves before risking their social capital by inviting their entire team. Removing that friction point could further increase the speed to the initial 'Aha!' moment.
Next Project
Web Design · Development