← All work

Case 02

TiriVelo

Turning checkout into confident bookings for an early-stage pet care marketplace.

Role
UX/UI design intern
Company
Pet care startup, Canada
Timeline
3 months · 2026
Team
Designers, team lead, founder
Tools
Figma
02
  1. Team audit
  2. My scope
  3. Redesign
  4. Weekly reviews
  5. Dev handoff

About the visualsTiriVelo is still in active development, so the product screens stay internal for now. This page focuses on the problems, my approach and what I learned.

Summary

Problem

People couldn't see what they'd actually pay until late in the booking, and the payment step mixed unclear options with a long form that was always open.

Solution

A clearer booking and checkout flow: the full price shown upfront, fees explained, payment methods that are easy to tell apart, and a plan for every error case.

Outcome

My designs went through TiriVelo's internal design review and were passed to the development team as part of their build process.

Context

My role

During a three-month internship with a Canadian startup, our design team first audited the existing product together. After the audit, each designer took ownership of a part of the experience.

As a team

  • UX audit of the existing product
  • Prioritising issues
  • Weekly reviews with the team lead and founder

My scope

  • Booking request and checkout
  • Payment methods and saved cards
  • Error and edge states
  • Subscription plans page
  • Pet owner profile
Approach

Design for trust

TiriVelo asks people to commit money and trust someone with their pet in the same moment. So every UI decision had to build trust. I gave checkout a clear step structure, made the total the strongest element on the page and kept continue, edit and confirm in the same places, so users always know what happens next.

I aligned components, spacing and interaction patterns with the rest of the product, and iterated through weekly reviews until the screens met development constraints.

The work

Problems & decisions

The audit gave us a long list of issues. These are the ones in my scope, and how I approached each of them.

01

Booking request

Problem
  • Users saw an estimated total, with taxes added later.
  • Fees had no explanation.
  • The next step wasn't obvious.
My approach
  • Show the full price before checkout, taxes included.
  • Explain each fee right where it appears.
  • Tell users when they will be charged.
  • One clear primary action, with a way back.
02

Checkout & payment

Problem
  • Payment options looked alike and were easy to confuse.
  • The card form was always open, even for returning users.
  • The main action was hard to find.
My approach
  • Make each payment method clearly distinct.
  • Let returning users pick a saved card and only open the form for a new one.
  • Put the summary, cancellation terms and confirm action in a predictable order.
03

Edge cases

Problem
  • The flow only covered the happy path.
  • Developers had no answer for errors or interruptions.
My approach
  • Design every state: invalid details, expired cards, a disabled confirm button.
  • Warn users before they leave checkout and lose what they entered.
  • Write error messages that say what to fix.
04

Subscription plans

Problem
  • Plans were hard to compare.
  • Billing details were easy to misread.
My approach
  • Side-by-side comparison with benefits written the same way for every plan.
  • Billing cues placed upfront, next to each price.
05

Pet owner profile

Problem
  • Photos took over the page.
  • Users couldn't tell what was missing from their profile.
My approach
  • A completion indicator with one clear next step.
  • Tabs to separate profile, pets, plan and settings.
  • Personal and contact details grouped in one place.
Impact

Results

Accepted

Checkout designs accepted in TiriVelo's internal design review

Passed on

Plans page passed to the development team as part of their build process

Weekly

Reviews with the team lead and founder that sped up iteration

My work helped move booking and checkout from concept screens towards development-ready flows within the team's process. Clear pricing at the point of purchase lowers the risk of people dropping off, asking for refunds or writing to support. And because the patterns match the rest of the product, the team can build faster.

Reflection

What I learned

  • Small inconsistencies in labels and component behaviour quickly turn into trust issues during payment and plan selection.
  • Stakeholder reviews work best when I bring specific options and trade-offs, not just one polished direction.
  • Designing for development means writing down assumptions early, especially for edits, cancellations and price changes.

Next steps

  • Usability-test the new checkout and plans to confirm users understand totals, billing frequency and next steps.
  • Create a lightweight design system page in Figma for shared components and content patterns.
  • Define success metrics with the founder, then track funnel drop-off and support tickets after release.
UX auditCheckout & paymentsEdge casesStakeholder reviewsDeveloper handoffWeb UI