CASE STUDY
Overview

FinSH CPA Advisory

Turning complex financial services into a clear, trust-led experience that guides growing businesses toward confident action.

UI/UX Design
Web Design
Webflow Development
View Prototype / Live Site
Project hero visual
TIMELINE
2026 · End-to-end client project
PROJECT TYPE
CPA Advisory Website
PLATFORM
Figma + Webflow
MY ROLE
UI/UX Designer & Webflow Developer
TEAM
Solo Designer/Developer + Founder

[OVERVIEW]

The project in 30 seconds

THE PROBLEM

FinSH offered accounting, tax and advisory services, but the breadth of the offer needed a clearer structure so visitors could quickly understand what the firm does, who it serves and where to go next.

MY ROLE

I led the experience from information architecture and visual design through responsive prototyping, stakeholder review and Webflow implementation.

THE OUTCOME

A three-page, trust-led website system that makes services easier to scan, strengthens credibility and creates clearer paths toward consultation.

PROJECT CONTEXT

FinSH is a solo CPA advisory practice serving founders, growing businesses, nonprofits, families and other organizations. The founder wanted the website to feel more strategic and premium than a traditional accounting site while remaining personal, credible and easy to understand.

[CHALLENGE]

What needed to become clearer?

FinSH needed to communicate several interconnected services without forcing visitors to decode long explanations or understand accounting terminology before knowing what was relevant to them.

Current or before experience

WHY IT MATTERED

Visitors are making high-trust decisions. If the offer feels complicated, generic or difficult to navigate, the website creates more uncertainty instead of reducing it.

PROBLEM 01

Services, industries and advisory content could easily become dense without a strong scanning structure.

PROBLEM 02

As a solo CPA practice, the experience needed to communicate credibility and expertise without presenting FinSH like a large corporate firm.

WHAT SUCCESS NEEDED TO FEEL LIKE

The website should feel like a strategic advisor guiding the visitor—not a catalogue of accounting services.

[CONTEXT]

Designing for the real context

CONSTRAINT 01

Messaging and UI had to reinforce a personal CPA relationship without implying a large internal team.

CONSTRAINT 02

Services, testimonials, FAQs and process content changed during review, so the system had to absorb new information without breaking the visual hierarchy.

CONSTRAINT 03

Layouts needed to translate into reusable, responsive Webflow structures—not just look good at 1440px in Figma.

SUCCESS CRITERIA

01

A first-time visitor should understand what FinSH offers and who it serves within the opening scroll.

02

Services and industries should be easy to scan before visitors commit to reading detailed content.

03

The experience should remain consistent and usable across desktop, tablet and mobile.

EVIDENCE

Research or audit evidence

RESEARCH / AUDIT

I mapped the growing service content into page goals, hierarchy and reusable content patterns before refining the visual system.

Competitor or data evidence

COMPETITOR / DATA

Financial-service references consistently used trust markers, service summaries and process explanations—but many became text-heavy or visually generic.

User or stakeholder evidence

USER / STAKEHOLDER INPUT

Stakeholder review repeatedly emphasized stronger readability, natural imagery, clearer service emphasis, process transparency and visible social proof.

[THE KEY INSIGHT]

The site didn't need more information. It needed a better order for the information visitors already needed.

That became the rule for every page: explain the value → prove credibility → make the offer scannable → deepen the detail → provide a clear next step.

PROCESS

A compact view of how the work moved forward

01

Discovery

Understand the problem, users, business context and constraints before deciding what to design.

02

Strategy

Turn evidence into a clearer information structure, flow and product direction.

03

Solution

Test the strongest direction, refine the interface and prepare the experience for delivery.

Audit: reviewed FinSH’s growing accounting, tax and advisory content, stakeholder feedback, and reference sites to identify where the experience needed stronger hierarchy, trust and clarity.

Structure: mapped the three-page journey across Home, Accounting Services and Tax Services, then organized services, industries, testimonials, process content and CTAs into a clearer narrative.

Design: created the visual system, refined the page hierarchy through multiple review cycles, and developed responsive high-fidelity designs that balanced credibility, readability and conversion.

Development: translated the approved Figma designs into Webflow, building reusable classes, responsive layouts, interactions, accordions and testimonial patterns across desktop, tablet and mobile.

Handoff: structured the Webflow project for client ownership, with clear hosting, domain and maintenance responsibilities so the site could be launched and managed beyond the design phase.

KEY DECISIONS

The decisions that shaped the experience

DECISION 01

Make social proof part of the journey, not an afterthought

Rather than placing testimonials at the very bottom of the experience, I used a short proof point near the homepage opening and a fuller client story deeper within the Accounting Services journey. This gives new visitors an early credibility signal while preserving depth for people actively evaluating the service.

Design decision 1 visual
Design decision 2 visual
DECISION 02

Let visitors scan first, then choose how deep to go

Accounting and advisory content can become overwhelming quickly. I introduced summary cards with concise descriptions before the detailed service sections so visitors could understand the offer at a glance and navigate directly to the service most relevant to them.

DECISION 03

Turn a generic process into a visible client journey

The original tax-process presentation treated every step like an equal card. As the content became more detailed, I redesigned it as a week-by-week timeline with deliverables and milestones, helping visitors understand not only what happens—but what they receive at each stage.

‍

Design decision 3 visual

FINAL EXPERIENCE

See the experience in motion

PROJECT PROOF

Designed to work beyond the desktop

The FinSH experience was translated into a responsive Webflow system across desktop, tablet, and mobile, preserving hierarchy, readability, and conversion paths at every breakpoint.

Project proof image 1
Project proof image 2
Project proof image 3

DESIGN EVOLUTION

Compare the evolution

Use this module to compare two meaningful stages of the work — from exploration to final execution.

BEFORE

Before redesign view

AFTER

After redesign view
LO-FI | HI-FI

DELIVERY

How the work became usable beyond the design file

Delivered: The FinSH experience was taken from early structure and stakeholder feedback through high-fidelity UI and into a responsive Webflow build, covering the Home, Accounting Services and Tax Services journeys.

Scope: Three core pages, a reusable visual system, responsive desktop/tablet/mobile layouts, service and industry patterns, testimonials, FAQ interactions, tax-process timeline, conversion CTAs and the supporting Webflow implementation.

Important: FinSH is a real client project, but I’m not attaching invented conversion or engagement metrics to the outcome. The strongest evidence at this stage is the completed design system, responsive implementation and clearer structure created for the client experience.

REFLECTION

Key Takeaways

Approval points matter as much as design decisions. The project reinforced the value of defining clear review checkpoints before moving from design into development, especially when content and stakeholder feedback continue to evolve.

Trust should be designed into the journey. Testimonials, process transparency, service hierarchy and clear calls to action worked together to make the experience feel more credible without relying on decorative “trust” elements.

Responsive design is not desktop scaled down. Moving the approved Figma direction into Webflow required deliberate changes to spacing, hierarchy, card behavior and content flow across tablet and mobile rather than simply shrinking the desktop composition.