

Designing a seamless sign-up flow for Goosehead.
Designing a seamless sign-up flow for Goosehead.




PRODUCT CONCEPT
PRODUCT CONCEPT
Bringing existing policyholders into the app
Bringing existing policyholders into the app
Bringing existing policyholders into the app
Goosehead's customers already had policies, but none of them had an account. I designed one passwordless flow that recognises people from the policy they already hold, so they reach their coverage in a few taps.
Goosehead's customers already had policies, but none of them had an account. I designed one passwordless flow that recognises people from the policy they already hold, so they reach their coverage in a few taps.
My Role
My role
My role
Product Designer
Product designer
Product designer
Focus
Team
Team
Onboarding & Authentication
Product designer, PM, Researchers, Tech engineers.
Product designer, PM, Researchers, Tech engineers.
Team
Platforms
Platforms
Product, Research & Engineering
Native iOS and Android
Native iOS and Android
CHALLENGES
CHALLENGES
CHALLENGES
Shifting agent dependent journeys into self-service
Shifting agent dependent journeys into self-service
Shifting agent dependent journeys into self-service
Goosehead is a US insurance agency. We needed the app to get about a million existing users to their own policies, reduce service calls, and stay secure, since it shows policy data.
Clients relied on their agents to manage their policies, so none of them had an existing Goosehead account. Their policy data sat in Salesforce and carrier systems, with no link to the app’s sign-in.
Goosehead is a US insurance agency. We needed the app to get about a million existing users to their own policies, reduce service calls, and stay secure, since it shows policy data.
Clients relied on their agents to manage their policies, so none of them had an existing Goosehead account. Their policy data sat in Salesforce and carrier systems, with no link to the app’s sign-in.
Goosehead is a US insurance agency. We needed the app to get about a million existing users to their own policies, reduce service calls, and stay secure, since it shows policy data.
Clients relied on their agents to manage their policies, so none of them had an existing Goosehead account. Their policy data sat in Salesforce and carrier systems, with no link to the app’s sign-in.
1
Rare visits
People open an insurance app a few times a year. Any password could get forgotten.
2
Messy records
One person could match no record, or several.
3
Security
The app shows policy data. It had to be secure without adding steps.
1
Rare visits
People open an insurance app a few times a year. Any password could get forgotten.
2
Messy records
One person could match no record, or several.
3
Security
The app shows policy data. It had to be secure without adding steps.
research insights
research insights
research insights
Understanding what users wanted from the app
Understanding what users wanted from the app
Understanding what users wanted from the app
Our research team ran nine 45-minute interviews with people aged 22 to 48 across nine US states. Goosehead’s service team added what they hear most from users.
Our research team ran nine 45-minute interviews with people aged 22 to 48 across nine US states. Goosehead’s service team added what they hear most from users.
Our research team ran nine 45-minute interviews with people aged 22 to 48 across nine US states. Goosehead’s service team added what they hear most from users.
Digital over phone calls
Digital over phone calls
People strongly preferred sorting things out in an app or online rather than calling an agent.
People strongly preferred sorting things out in an app or online rather than calling an agent.
Easier and Safer Access
Easier and Safer Access
People rarely read their policy documents. They want their coverage, price and renewal date in front of them quickly and conveniently
People rarely read their policy documents. They want their coverage, price and renewal date in front of them quickly and conveniently
Logging in is a pain point
Logging in is a pain point
Goosehead’s team listed “logging in and seeing my policies” as one of users’ three most common pain points.
Goosehead’s team listed “logging in and seeing my policies” as one of users’ three most common pain points.
Digital over phone calls
People strongly preferred sorting things out in an app or online rather than calling an agent.
Easier and Safer Access
People rarely read their policy documents. They want their coverage, price and renewal date in front of them quickly and conveniently
Logging in is a pain point
Goosehead’s team listed “logging in and seeing my policies” as one of users’ three most common pain points.
What this meant for us?
What this meant for us?
What this meant for us?
Get every client to their own policies in a few screens, with no password to create or reset.
Get every client to their own policies in a few screens, with no password to create or reset.
Get every client to their own policies in a few screens, with no password to create or reset.
defining success
defining success
What a good sign-in should looked like?
What a good sign-in should looked like?
What a good sign-in should looked like?
For users
For users
For users
Reach their own policies in a few screens
Reach their own policies in a few screens
No password to create or reset
No password to create or reset
A next step whenever something goes wrong
A next step whenever something goes wrong
Measured by
Sign-in completion
For users
Reach their own policies in a few screens
No password to create or reset
A next step whenever something goes wrong
Measured by
Sign-in completion
For Goosehead
For Goosehead
For Goosehead
Reducing reliance on a service team handling around 5,000 calls daily.
Reducing reliance on a service team handling around 5,000 calls daily.
Better retention, with users coming back to the app
Better retention, with users coming back to the app
A secure sign-in that doesn’t raise privacy concerns
A secure sign-in that doesn’t raise privacy concerns
Measured by
New users signing up
Notification opt-in
Calls and emails to agents
For Goosehead
Reducing reliance on a service team handling around 5,000 calls daily.
Better retention, with users coming back to the app
A secure sign-in that doesn’t raise privacy concerns
Measured by
New users signing up
Notification opt-in
Calls and emails to agents
WIREFRAMES · EARLY EXPLORATION
ideation & iterations
ideation & iterations
Exploring onboarding and authentication approaches
From wireframes to the final flow
From wireframes to the final flow
From wireframes to the final flow
I started by mapping how existing policyholders would create their app accounts and securely access their policies. I explored different onboarding journeys and authentication methods to understand where we could simplify the experience.
I started with quick wireframes, then took the flow through three rounds of design. Each round cut a step between the client and their policies.
I started with quick wireframes, then took the flow through three rounds of design. Each round cut a step between the client and their policies.
I started with quick wireframes, then took the flow through three rounds of design. Each round cut a step between the client and their policies.

←
→
First-time onboarding
Explored feature introductions, account recognition and personal-details collection to help existing policyholders register for app access.
Iteration 1: In my initial wireframes, new clients went through a short feature introduction before creating an account with their personal details.
Iteration 1: In my initial wireframes, new clients went through a short feature introduction before creating an account with their personal details.

←
→
Returning user authentication
Compared phone-number and PIN-based sign-in approaches with Face ID to explore secure and convenient access on future visits.
Iteration 2: Simplified the initial flow while enabling faster and secured future sign-ins through PIN and Face ID.
Iteration 2: Simplified the initial flow while enabling faster and secured future sign-ins through PIN and Face ID.

V1 • INITIAL EXPLORATIONS
Starting with passcode and
Face ID for secure access
Starting with passcode and Face ID for secure access
Starting with passcode and
Face ID for secure access
Since the app contained sensitive policy information, I initially explored a familiar banking-style authentication flow, with passcode and Face ID setup for repeat access.
Since the app contained sensitive policy information, I initially explored a familiar banking-style authentication flow, with passcode and Face ID setup for repeat access.


V1 • INITIAL EXPLORATIONS
Starting with passcode and Face ID for secure access
Since the app contained sensitive policy information, I initially explored a familiar banking-style authentication flow, with passcode and Face ID setup for repeat access.

THE ASSUMPTION I CHALLENGED
Did clients really need another passcode to remember?
Did clients really need another passcode to remember?
Unlike banking apps, insurance apps are typically accessed only a few times a year. Requiring clients to remember a passcode they rarely used could introduce unnecessary friction when returning to the app.
Unlike banking apps, insurance apps are typically accessed only a few times a year. Requiring clients to remember a passcode they rarely used could introduce unnecessary friction when returning to the app.
V2 • SIMPLIFYING AUTHENTICATION
V2 DESIGNS
V2 DESIGNS
Removed passcodes to simplify account access
I replaced the passcode with a one-time SMS verification code to simplify sign-in and reduce the risk of lockouts for clients who rarely use the app.
I replaced the passcode with a one-time SMS verification code to simplify sign-in and reduce the risk of lockouts for clients who rarely use the app.
I replaced the passcode with a one-time SMS verification code to simplify sign-in and reduce the risk of lockouts for clients who rarely use the app.
I replaced passcodes with one-time SMS verification to reduce the memory burden for infrequent users. I also prioritised phone numbers for policy matching, as names and emails were less consistent in Goosehead’s records.
I replaced passcodes with one-time SMS verification to reduce the memory burden for infrequent users. I also prioritised phone numbers for policy matching, as names and emails were less consistent in Goosehead’s records.
I replaced passcodes with one-time SMS verification to reduce the memory burden for infrequent users. I also prioritised phone numbers for policy matching, as names and emails were less consistent in Goosehead’s records.
Sign up
→
Phone number
→
One-time SMS code
→
Onboarding
→
Home - Policy screens
Sign up
→
Phone number
→
One-time SMS code
→
Onboarding
→
Home - Policy screens

• key decisions
01. Passwordless verification
Removed passcode and Face ID setup, allowing clients to verify their identity through a one-time SMS code.
02. Phone first policy matching
Used phone numbers as the primary way to identify existing policyholders, with additional personal details as a fallback.
• key decisions
01. Passwordless verification
Removed passcode and Face ID setup, allowing clients to verify their identity through a one-time SMS code.
02. Phone first policy matching
Used phone numbers as the primary way to identify existing policyholders, with additional personal details as a fallback.


V2 DESIGNS
01. Passwordless verification
Removed passcode and Face ID setup, allowing clients to verify their identity through a one-time SMS code.
02. Phone first policy matching
Used phone numbers as the primary way to identify existing policyholders, with additional personal details as a fallback.

V3 • FINAL tweaks
V3 • full flow
V3 • full flow
Unifying sign-up and sign-in with clearer recovery paths
Iterative Validation
Iterative Validation
Iterative Validation
V3 testing revealed further friction. I merged sign-up and sign-in into one “Get started” journey, letting the system identify existing clients instead of making them choose an entry point. I also added recovery paths wherever verification or policy matching could fail.
Testing revealed remaining friction points. I merged sign-up and sign-in into a single “Get started” flow to remove the need for clients to choose between two journeys. Since they already had policies, the system could identify them and guide them through the right steps.
Testing revealed remaining friction points. I merged sign-up and sign-in into a single “Get started” flow to remove the need for clients to choose between two journeys. Since they already had policies, the system could identify them and guide them through the right steps.
Testing revealed remaining friction points. I merged sign-up and sign-in into a single “Get started” flow to remove the need for clients to choose between two journeys. Since they already had policies, the system could identify them and guide them through the right steps.
Step
Friction identified
UPDATES
Account entry
Users were unsure whether to sign up or sign in
A mistyped number, or not knowing which number had signed up with would leave people stuck.
→
Combined both into one “Get started” flow, letting the system identify the client
→ Errors show under the field, with email as a fallback.
Phone number
Incorrect or unrecognised phone numbers
A mistyped number, or not knowing which number had signed up with would leave people stuck.
→
Inline errors and an alternative email lookup
→ Errors show under the field, with email as a fallback.
One-time code
Invalid or expired verification codes
A wrong or expired code was a dead end.
→
Clear feedback and a resend option
→ “Invalid code” now offers Resend, or a switch to email.
Record lookup
No matching policy record
With no record for the number, the user had nowhere to go.
→
Additional personal details to help locate the client’s policy
→ Users confirm their details and we create the account.
Final flow
Splash screen
Get a quote or Log in
Keypad suggests saved numbers
Number accepted
Code autofills, resend after 10s
Accept terms, Get started
Example alerts, Turn on or Skip
The user's policy cards
Error under the field
Check the number or try email
Name, date of birth, state
Email to sign in
Code sent to the phone
Error under the field

OUTCOME
OUTCOME
OUTCOME

OUTCOME

Prototype




























→

Prototype




























→

success & impact
Measuring progress towards self-service
Measuring progress towards self-service
After launching in March 2025, we measured client onboarding, notification opt-ins and support usage over a 16-week period to see how the app was supporting the shift from agent-led service to self-service.
After launching in March 2025, we measured client onboarding, notification opt-ins and support usage over a 16-week period to see how the app was supporting the shift from agent-led service to self-service.
20,700
20,700
Clients successfully onboarded
Clients successfully onboarded
Within the first 16 weeks, 20,700 clients signed up through the passwordless flow and found their existing policies.
52.9%
52.9%
Opted into push notifications
More than half of clients enabled notifications during onboarding, after seeing how alerts could help them stay on top of their policies.
4.9%
Of active users contacted an agent by phone
Just 4.9% of active users called an agent in a month, while 3.9% reached out by email. An encouraging early indicator for our self-service goal.
4.9%
4.9%
Of active users contacted an agent by phone
Just 4.9% of active users called an agent in a month, while 3.9% reached out by email. An encouraging early indicator for our self-service goal.

success & impact
Measuring progress towards self-service
After launching in March 2025, we measured client onboarding, notification opt-ins and support usage over a 16-week period to see how the app was supporting the shift from agent-led service to self-service.
20,700
Clients successfully onboarded
Within the first 16 weeks, 20,700 clients signed up through the passwordless flow and found their existing policies.
52.9%
Opted into push notifications
More than half of clients enabled notifications during onboarding, after seeing how alerts could help them stay on top of their policies.
4.9%
Of active users contacted an agent by phone
Just 4.9% of active users called an agent in a month, while 3.9% reached out by email. An encouraging early indicator for our self-service goal.
4.9%
Of active users contacted an agent by phone
Just 4.9% of active users called an agent in a month, while 3.9% reached out by email. An encouraging early indicator for our self-service goal.


UP NEXT


DESIGN | RESEARCH | BRANDING | DEVELOPMENT

UP NEXT


DESIGN | RESEARCH | BRANDING | DEVELOPMENT
