GoCapital Auto Quest

Overview

A finance app for the moment before a first major purchase gets scary.

GoCapital Auto Quest is a UX case study for college-aged and young adult users preparing to buy a car for the first time. The project was framed around a very specific moment: the user knows they need transportation, has some idea of a monthly budget, but does not yet understand how credit, lender financing, dealer financing, down payments, insurance, taxes, and long-term ownership costs all fit together.

The product concept responds to that anxiety with guided education, personalized onboarding, calculators, saved vehicle review, plain-language finance explainers, and dealership preparation tools. Instead of assuming users already know how the system works, the experience teaches the system as the user moves through it.

First-time buyers were not missing motivation. They were missing a map.

Core design insight

The goal was not to make car buying feel artificially fun. The goal was to make it feel less opaque. The app acts like a calm, structured guide between the user and one of the first major financial decisions of adulthood.

Brief

The assignment was bigger than a polished mobile mockup.

The project asked for a product experience that could support people entering the car-buying process with limited knowledge. That meant the solution had to do more than display cars. It needed to explain money, sequence decisions, reduce intimidation, and help users recognize when they were ready to talk to a lender, dealership, parent, or advisor.

Lead Designer UX Research Survey Synthesis Interview Synthesis User Flow Wireframes Visual System Figma Prototype

User situation

A young buyer is excited about independence but unsure how loans, interest, credit, insurance, taxes, and dealer conversations actually work.

Product response

GoCapital organizes the process into a guided path: learn the basics, calculate affordability, review options, save decisions, and prepare before talking to a dealer.

Team and role

W

Wyatt Spicer — Lead Designer. Responsible for the visual direction, app structure, prototype quality, UI system, and case study presentation.

M

Melody Berungan — Project Manager. Helped coordinate deliverables and keep the team moving through research, synthesis, and design production.

T

Triston LaCroix — Lead Survey Researcher. Focused on quantitative insight gathering around user knowledge, confidence, and car-buying expectations.

T

Taivia Milligan — Lead Interview Researcher. Focused on qualitative input and user attitudes around decision-making, pressure, and uncertainty.

S

Sumayya Ali — Lead Developer. Supported the project from the implementation and feasibility side of the product concept.

Research

The research pointed to a confidence gap, not just an information gap.

The strongest research signals were not just that users lacked information. The bigger issue was that they did not know which information mattered when. A user can look up the definition of APR, but that does not automatically tell them how APR changes the monthly payment, why a credit score affects approval, or whether a dealership offer is better than lender financing.

58.2%had checked credit scores

60.9%did not understand lender vs dealer financing

47.3%expected family or friend guidance

1stmajor financial purchase context

Survey chart showing car finance knowledge findings — Survey results showed that users had partial awareness of finance concepts, but not enough confidence to apply them during an actual purchase.

Survey chart showing credit score knowledge findings — Credit score awareness existed, but understanding how credit affected the buying journey was uneven.

Survey chart about credit and car buying readiness — The research suggested a need for tools that translate credit knowledge into practical car-buying decisions.

Survey chart about financing confusion — Confusion around financing options became one of the strongest justifications for the glossary and lender/dealer explanation features.

Research interpretation

!

Users had fragments of knowledge. They knew terms like credit score, down payment, or monthly payment, but did not always understand how those terms interact.

!

Dealer pressure was a design problem. If users wait until the dealership to learn the vocabulary, they are already in the highest-pressure environment.

!

Support networks were uneven. Almost half expected family or friend guidance, which means the product needed to help users who did not have a knowledgeable person available.

+

The solution needed pacing. Throwing every finance concept onto one screen would recreate the confusion. The app needed to sequence learning into a path.

Product Strategy

From anxiety to a guided decision path.

The product strategy was to turn car buying into a journey users could move through one step at a time. Every feature had to answer one of three questions: What should I learn? What can I afford? What should I do next?

1. Personalized onboarding

Users enter their buying timeline, budget range, experience level, and comfort with financing so the app can adjust the path instead of treating every buyer as the same person.

2. Step-by-step auto quest

The central journey breaks the process into manageable sections: credit, budgeting, loan basics, dealership prep, insurance, ownership costs, and final review.

3. Plain-language glossary

Finance and dealership terms are explained before the user needs them, reducing the vocabulary gap that makes conversations feel intimidating.

4. Calculator and car review

Users can test payment scenarios, down payments, and affordability before becoming emotionally attached to a specific vehicle.

5. Saved decisions and profile tools

The experience remembers progress, saved cars, and user preferences so the app feels like a preparation workspace rather than a static article.

6. Short-form learning feed

A familiar video-style format lowers the barrier to financial education and makes preparation feel less like homework.

Information Architecture

The app structure had to make the next step obvious.

The user flow organizes the experience around progression, not browsing. A first-time buyer should never have to ask, “Where do I go now?” The dashboard, learning path, calculator tools, glossary, saved cars, and profile settings all connect back to the same core objective: helping the user prepare for an informed buying conversation.

GoCapital user flow diagram — The user flow connects onboarding, dashboard, learning modules, calculators, saved car review, glossary content, and profile tools into one preparation path.

GoCapital low-fidelity wireframes — Early wireframes tested navigation, learning hierarchy, and the relationship between education and task completion.

GoCapital additional wireframes — Additional wireframes explored how guidance, profile tools, and learning modules could live together without crowding the interface.

Visual System

Calm financial clarity instead of dealership chaos.

The visual system uses a clean mobile-app language: bright blue for action and trust, soft supporting colors for section distinction, high-contrast type, rounded cards, and icon-driven navigation. The design needed to feel credible enough for finance, but approachable enough for young buyers who may already feel intimidated.

Avoided

Dense banking dashboards, dealership-style hype, aggressive sales language, and intimidating finance terminology stacked without context.

Built instead

A guided, modular interface where each card has a clear job: teach, calculate, save, compare, or prepare.

GoCapital visual system with typography, color, icons, and UI components — Final visual system showing type, icons, color, imagery, and component direction for the GoCapital prototype.

GoCapital early visual elements — Early visual exploration connected the app to a financial-product tone while keeping the experience friendly and mobile-first.

GoCapital Auto Quest proposal cover — The project presentation framed the app as a structured auto-buying guide, not just a collection of screens.

Prototype

The final screens turn research into usable motion.

The prototype demonstrates how users move from onboarding into a dashboard, guided learning, video education, calculator tools, saved items, and profile support. The final app experience gives users a sense of forward movement: they are not just reading about buying a car; they are completing a preparation process.

Final GoCapital prototype screens — Final prototype screens showing onboarding, dashboard, education modules, learning feed, car review, and profile tools.

GoCapital mid-resolution dashboard and learning screens — Mid-resolution screen set defining the dashboard, learning paths, and primary app structure.

GoCapital mid-resolution feature screens — Feature screens for AI support, calculators, lender/dealer education, videos, and profile settings.

Interactive prototype

The embedded Figma prototype preserves the interaction model and lets viewers move through the app in the same sequence a first-time buyer would use.

Evaluation

What makes the case study stronger than a screen gallery.

The strongest part of the project is the connection between research findings and feature decisions. The app does not simply say, “car buying is confusing,” then show polished screens. It names the specific confusion: credit knowledge, lender/dealer financing, ownership costs, and reliance on informal support networks. The feature set follows from those findings.

✓

Clear audience. The project is not trying to serve every driver. It is focused on young, first-time buyers preparing for a major financial decision.

✓

Research-to-feature traceability. Survey and interview insights map directly into glossary content, calculators, step sequencing, and dealership preparation.

✓

Mobile-first realism. The experience assumes users will prepare on a phone, not sit down with a desktop spreadsheet.

✓

Credible financial tone. The interface is friendly without becoming childish, which matters when the subject is debt, credit, and ownership cost.

!

Next improvement: stronger usability testing. A future pass should include moderated prototype tests and task-success metrics for calculator use, glossary comprehension, and dealership-prep confidence.

!

Next improvement: content validation. Finance explanations should be reviewed against current lending terminology before a public release, especially if the product were tied to a real financial institution.

Takeaways

A case study about giving users leverage before a conversation starts.

GoCapital Auto Quest is strongest when understood as preparation software. The user is not buying the car inside the app. The app gives them the vocabulary, calculations, questions, and confidence they need before they enter a dealership or financing conversation.

That makes the design problem more interesting than a simple car marketplace. The real product value is psychological and educational: helping someone feel less alone, less pressured, and less likely to be surprised by the cost of a decision they cannot easily undo.

The question this project answers.

How do you design a mobile experience that turns a confusing, high-pressure financial milestone into a sequence of small, understandable decisions?

Open Prototype Back to UX Work