Cottage

Designing a New B2B Customer Onboarding Experience

About the Project

Cottage is a startup that connects freelance developers with companies in need of short-term task-based development support. I worked directly with Cottage co-founders Hunter Hodnett and Neil Granberry as our clients.

Timeline: 3-week design sprint
UX team: 4 person team
Project Scope: Design a new customer onboarding experience
My Roles:
  • Lead point of client contact
  • User Research & Testing
  • Information Architecture
  • Content Writing
  • User Flows
  • Figma Prototyping

Discovery & Research

The UX process began with a client discovery meeting and user research. I created a detailed task analysis as part of the research phase because the Cottage client did not have existing documentation about the complete customer onboarding process.

Client Discovery

As a business which connects hiring companies to qualified freelancers, Cottage serves several types of users. The project brief was to focus on new "Demand-Side" customers only, and design an onboarding experience for this group of users. The sign-up process for "Supply-Side" expert freelancers was not part of the project scope.

Cottage's Demand-Side Customers
Non-Technical Founders

Startup founders and CEOs with limited coding knowledge.

Startup Dev Leads

May lead a small in-house dev team, or act as a one-person product and dev team writing all the code themselves.

Supply-Side Experts
Freelance Developers

Experienced development professionals looking for full-time or part-time freelance work.

Cottage was in private beta with a minimum viable product (MVP) and was preparing for a public launch. In discovery meetings with Cottage I learned that:
  • Prospective customers get excited about the Cottage platform in pitch meetings but don’t complete onboarding.
  • The Cottage MVP included an integrated cloud development environment (IDE) and a basic UI with a Kanban-style task management dashboard.
  • Cottage had no UI for customer sign-up.
  • Cottage co-founders had to manually create new customer accounts - not scalable!
  • Onboarding process includes some technical steps, such as importing customer’s code base from GitHub to Cottage cloud environment.
  • There was no written documentation explaining full onboarding process.

User Interviews

Interview participants fell into two broad categories:
Existing Cottage Prospects
  • Prospective customers already aware of Cottage
  • Contacts were provided by Cottage clients
  • Startup founders and technical leads
Software Development Professionals
  • Participants recruited by UX team
  • Not previously aware of the Cottage platform
  • Professionals with 5+ years in the field
Key Findings:
  • Obstacle for the non-technical founder is not understanding exactly what to specify for freelance work.
  • Cottage’s cloud-based IDE is a strong product differentiator, but participants want clearer information on how it works.
  • Varying levels of concern for security and intellectual property.
  • Security on variable keys and  permissioning was most common concern.
  • Quality of work and trustworthiness of short-term freelancers is also an important concern.

Task Analysis

The customer onboarding process was more than just creating a new Cottage account. I met with the Cottage client team to understand and document all critical steps and dependancies.

What technical steps must a customer complete to get up and running with Cottage?
  • Customer must already have source code stored in GitHub to use Cottage as a self-service plan.
  • Source code is imported from GitHub to Cottage's cloud-based IDE so freelancers can access it to complete work.
  • Customer must provide any variables and initiation codes that freelancers will need to Cottage.
  • Billing must be set up through Stripe (3rd-party payment system). This step is completed outside of the Cottage platform.

I divided the onboarding process into three parts due to its complexity and number of steps. I grouped only the few most critical steps into the sign-up flow, and opted to use a progressive onboarding feature to walk customers through the remaining steps at their leisure to make set up feel less cumbersome.

1 - Plan Selection
  • Landing page and Plan Pricing page
  • Introduces Cottage platform and benefits to customer
  • Covers pricing options and plan selection and drives users to sign-up flow
2 - Sign-Up Flow
  • Dedicated sign-up screens leading to customer dashboard
  • Covers account creation, GitHub link, and source code import
  • Under 4-5 screens long per UX best practices
3 - Progressive Onboarding
  • Further set up prompts layered over customer dashboard
  • Covers creating a task, adding variables and codes, and billing via Stripe
  • Customer can choose to complete all steps immediately or later

User Flow

After outlining all the steps a new customer must complete to be fully up and running with Cottage, I mapped these out in a user flow diagram using FigJam. After several iterations the final version below served as the basis for our design.

Content Development

In the design phase I focused on content and copywriting while some of my UX teammates focused on visual design ideas and design system creation. Design iterations included two rounds of usability testing, the first with a low-fidelity prototype and the second with a revised high-fidelity prototype, before arriving at our final design.

Pricing Page

I included the text from the client's existing pricing page in our low-fidelity prototype and first round of usability testing.

  • 2 out of 3 usability testers wanted more details and clarification about each plan before moving forward with sign up.
  • Users were not clear what the "free" plan included, or how the transaction fee would apply here.
  • One user wanted more information about Strong Network and the security features in the second plan.
  • The term "fractional CTO" was unfamiliar and confusing to 2 out of 3 users.
  • Users didn't grasp that the third plan was a full-service consulting option and one user noted "We create the tasks for you" as a perplexing statement.
Cottage's existing pricing page content in low-fidelity prototype. Our usability testers didn't feel the pricing was simple and had questions.

Based on user feedback I rewrote the pricing page copy with these improvements:

  • Emphasized that the cloud IDE is part of all service plans
  • Highlighted flexibility of plan options "that fit you"
  • Gave clear explanation of what is included for free in the basic plan
  • Added link to learn more about 3rd party vendor Strong Network
  • Clarified that option three is a full-service custom contract
  • Revised layout with scannable side-by-side comparison of pricing and features
  • Revised button copy to be more action-oriented in line with call-to-action best practices
My revised pricing page content addressed users' questions and performed well in our high-fidelity usability test.

Sign Up Flow

I aimed to keep the initial sign-up flow as quick and easy as possible while still including the critical GitHub import step. The final flow include a 3-step process - Create Account, Login to GitHub, and Import GitHub Repository - and a confirmation message before directing new customers to their account dashboard.

1 - Create your Cottage Account
2 - Login to GitHub
3 - Select GitHub Code Repository to Import
4 - Success! Cottage sign-up complete.

The low-fidelity design included explanatory details on each step.

In the final design I replaced this with a message at the beginning which explained all the steps. This set clearer expectations for users from the start and made it possible to streamline the rest of the flow.

Since the GitHub import steps are required for all self-serve plans, users without a GitHub have an option to learn about Cottage full-service instead.

Early low-fidelity version of GitHub login page. Informative but cluttered.
The final content explained the steps at the start of the flow instead.

Progressive Onboarding

Cottage's existing customer UI consisted of a simple Kanban-style dashboard for managing developer tasks. I layered the progressive onboarding steps - which covered creating a task, adding coding details, and setting up billing with 3rd party vendor Stripe - over a version of this dashboard.

Given the volume of information, I opted for a large overlay that the user could choose to dismiss and return to later via a reminder message in the lower right corner of the screen.

Throughout the process I sought feedback from our clients and from our usability testers to ensure I was using terminology that was technically correct and commonly understood by our target audience of software professionals.

One-time Welcome Message provides a checklist of remaining steps which users can complete now or later.
Reminder message appears in lower right until customer has completed all steps.
Reminder message expands to show details on remaining steps.

Client Deliverables

The final client deliverables included high-fidelity Figma wireframes and prototype, a basic style guide, ideation for a next-step dark theme option, and primary and secondary user personas based on our user research.

The Cottage clients were excited about our new designs and research insights, and started incorporating some of our feedback into their landing and pricing page content right away. Seeing the user personas during our research presentation was especially powerful for our clients because it helped them "see" their prospective customer's wants and needs clearly articulated for the very first time, based on research.

Let's Work Together!

Reach out in the contact form below or find me on LinkedIn.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.