Tavare · 6-month contract · Norway

Making mending the easier option than buying new.

Tavare collects damaged clothing, sends it to a partner tailor and brings it back repaired, for individual customers and for fashion brands like Levi's and Tommy Hilfiger.

Hands stitching a tear in a pair of jeans
The Tavare iOS home screen: Get Repaired, then a priced catalogue
Role
Lead product designer, research to handoff
Team
Ole Cato Holden, founder · Sheo Shankar, product manager
Timeline
6 months · 2024–25
Shipped
iOS, web, iPadOS, partner portal

01 · The universe

One repair order, four businesses to keep happy.

Tavare collects damaged clothing, sends it to a partner tailor and brings it back repaired. Individual customers and fashion brands like Levi's and Tommy Hilfiger both send work through the same pipeline.

Circular-fashion targets Apple-first market Vipps for identity English + Norwegian

02 · The one big problem

Norwegians want to repair. Replacing is just easier.

Finding a tailor you trust, getting there, and paying close to the price of new is enough friction to send a torn jacket to the bin.

A tailor refitting the zipper on a jacket
Hands stitching a tear in a pair of jeans
A man trying to rub a mark out of his jacket sleeve

And what made it hard to design

  1. A three-sided marketCustomers, tailors and brands each need a different tool, but all of them work on one order.
  2. Two demand streamsA single shirt and a brand's bulk consignment go through one pipeline without it splitting in two.
  3. Price parity with newRepair only wins if the cost is visible before the customer commits.
  4. Trust while the garment is awayOnce the jacket is gone, every surprise charge reads as a hostage note.
  5. Four surfaces, one modelKept coherent while the business model shifted underneath.

03 · The user

Three people who would repair, for three incompatible reasons.

Interviews traced what happens when something breaks.

Market researchUser interviewsJourney mapping
A man trying to rub a mark out of his jacket sleeve
1Try a DIY fixSelf-service first.
2Check the warrantyStrong law, a slow process.
3Store itIn a drawer, "for later".
4Bin itA repairable garment, wasted.
25–40 · Time-constrained professional “If someone handled the whole repair for me, I'd actually do it.”

Designed for: fewest steps, doorstep pickup.

20–35 · Eco-conscious consumer “I want to repair instead of buying new, but I need to trust it.”

Designed for: status at every handoff.

35–55 · Cost-sensitive family “I'll repair if it makes sense, not if it costs more than new.”

Designed for: a price on every tile.

04 · Market & benchmarking

Five competitors. Nobody connected all three sides.

Consumer players owned convenience but had no channel to brands. B2B players owned the workflow but had nothing a customer would ever touch. The gap was the part that connects them.

  • Borrowed: a premium feel tied to brands people recognise.
  • Borrowed: repairs that are predictable and priced up front.
  • Borrowed: trust through a curated set of makers.
  • Borrowed: B2B coordination and operational insight.
  • Borrowed: circular, reuse-first community behaviour.

05 · The starting point

The existing repair flow began with paperwork.

Before any new design, I audited the interface brands were already sending customers to. It worked, technically. It just asked the customer to do the triage.

  1. The one action is the smallest thing on the page. "Order repair" is a thin outline button beside a full-bleed photo.
  2. Seven steps, and damage comes fourth. Warranty check, contact, product, damage, pick-up, return, summary.
  3. Controls sit on the photo. The logo and the language switch fight the image for legibility.
  4. A cost with no number. "Service charge is to be paid by you", and no price anywhere.
  5. It asks for what people don't have. Model and PO numbers off the care label, before anyone describes the tear.
The original repair web page on a tablet: a large photo, a small Order Repair button, and a seven-step contact details form
1 2
The original app landing screen: a workshop photo with the language switch laid over it
3 4
The original Product Details step asking for model name, model number and PO number
5

06 · Jobs to be done

Make repair as effortless as ordering food, for every side of the order.

Customer

When my jacket's zipper breaks, I want it fixed without hunting for a tailor, so I can keep wearing it.

iOS app · web
Retail staff

When a customer brings a damaged item into the store, I want to log it in one pass, so the queue keeps moving.

iPad dashboard
Tailor

When work arrives, I want to see what to do and why anything is stuck, so I can spend my time sewing.

Partner portal
Tavare

When a customer's first repair lands well, I want the second one to feel obvious, so repair becomes a habit.

Membership · pricing
North star

Remove every decision the customer shouldn't have to make.

07 · The full product cycle

One order, four people touching it. I designed the pipeline first.

Before any screens, I mapped a single order from placement to reorder. Each surface only exists to move the order one lane further.

A state the customer can see, with a timestamp The one moment that needs a decision from the customer

08 · Flows & information hierarchy

For every step, I wrote down what it had to earn, not what it had to show.

Customer7 steps · iOS + web

Onboardwho we are, why us
New orderfewest steps, visual
Profileleast friction
Paytrust, seamless
Tracktrust
Successfeedback, escalation
Dashboardreorder, explore

Tailor6 steps · partner portal

Active orderssorted by priority
Order detailone clear action
Repair flowvisual guidance
Damage inputconfidence, no typing
Journeyalways visible
Completeescalate if needed

Retailer4 steps · iPad

Active ordersscan in seconds
Approveclear actions
Paymentslimits and budgets
Successfeedback, escalation

Customer app · top-level hierarchy

HomeGet repaired, then a priced catalogue. No discovery detour.
OrdersActive repairs and tracking, where the worry lives.
CartOne scrollable checkout sheet.
ProfileMembership, details, help.

09 · The design system

Norway is an Apple market. I let the platform do the teaching.

I built on the Human Interface Guidelines instead of a custom visual language. The system gives up novelty and gains comprehension, which matters more to someone standing over a torn jacket.

Primary#36476F
Primary lt#EBEDF1
Base#000000
White#FFFFFF
Ground#F2F2F7
Positive#12AD48
Negative#BD2727
Rule
Green and red are reserved for order state, never decoration, so a tailor scanning a queue reads status before reading words.
Rule
Seven type steps, no more. Fewer sizes meant fewer decisions for engineering and less drift across four codebases.

Article tile · default / selected

Shirt59 Kr

–1+

Blazer199 Kr

Pants199 Kr

Damage choice · two-level taxonomy

Regular tearNo fabric damage
HoleFabric damage
Seam splitNo fabric damage

Actions · order state

Back to HomeProceed
CompleteOn hold · awaiting approvalRepair complete

Type scale

  1. Page header 32 / Bold
  2. Bottom sheet header 24 / Bold
  3. Section header 16 / Bold
  4. Sub-header 16 / Medium
  5. Body text 14 / Regular
  6. Support text 12 / Regular

10 · The solution

One pipeline, four doorways into it.

Every surface reads and writes the same order. Each one is shaped by who holds it and where they're standing.

Tavare iOS home: Get Repaired banner above a priced dry-clean grid
01Customer appEvery feature, for people who'll repair againiPhone · iOS
Tavare web: Add Articles beside a Personal Details form
02Customer webNo install, for people arriving from a brand's linkMac · any browser
Retail iPad dashboard: Repair, Alter and Dry Clean above active services
03Retail dashboardStaff logging repairs on a shop flooriPad · iPadOS
Partner portal: new orders list
04Partner portalTailors accepting, repairing, getting paidiPhone · web

11 · Customer app · entry

People arrive holding something broken. Don't make them register.

Vipps first
Around 99% of Norwegians already log into apps with Vipps, so the hardest screen became one tap.
a conveyor belt
If it's email, it's two short screens: address, then name and phone. Email and birthday are optional, and an address is saved once as Home, Work or Friends & Family.
spend the space on value
What a long form would have taken went to the offer: discounts, round-the-clock support and a six-month warranty on every order.
Login screen with email, password and a Login with Vipps button Sign-up address details with Save as Home, Work, Friends and Family, Other Sign-up personal details with optional email and date of birth

12 · Customer app · intent to repair

The catalogue is the home screen.

Interviews and affinity mapping agreed on one thing: people open the app to get something fixed. So nothing sits between Home and a placed order.

catalogue
The price is on the tile, not behind a step. That answers the cost-sensitive customer's question before they ask it.
quantity
No product pages. Tapping a tile turns it into a stepper in place, and a bar keeps count until you open the cart.
checkout
One sheet: items, a prompt to mention stains, the membership offer, delivery and payment, in reading order.
Home: Get Repaired banner and a priced grid of garments Shirt and Blazer tiles turned into quantity steppers, with a 3 articles added bar Cart: item details, a stains prompt, a membership offer and delivery location Order Placed with a Next Step card

13 · Membership

Membership pays for the service. I let users settle the explainer.

Revenue depended on getting customers subscribed, so how the offer was explained mattered more than how it looked.

A/B test the explainers instead of picking one in review. I ran several variants to take subjective opinion out of it and learn how people actually scan an offer.
One quiet entry point. "Become a member" is a single row at the top of Profile, and a one-line offer inside the cart, never a pop-up.
Profile with a Become a Member row above account details
INEntryOne row on Profile
Variant A: Monthly Plan Active sheet listing unlocked features
ABenefits as a listWhat you've unlocked
Variant B: Monthly or Yearly toggle with three benefit tiles
BBenefits as tilesMonthly or yearly, 20% off

14 · The hardest moment

The repair nobody agreed to.

A tailor finds more damage once the jacket is already with us. The customer can't see the garment and is being asked for more money.

Interrupt with one fully specified question: what was found, on which garment, what each fix costs.
Make refusal a first-class option. Skip sits beside Pay, and the original repair continues either way.
It follows the customer until it's answered, on Home and on the order in the list.
Home with a 2 additional damages found banner Action Required: tear on left shoulder and broken zipper, each 39 Kr, with Skip and Pay Orders list where one order carries the additional damages banner

15 · Delivery & logistics

Payment isn't the end. The next physical step is.

Several logistics partners sat behind one checkout. The design had to nudge the right one, then make sure the clothes actually left the house.

ranked choice
Three handover options, not a list of equals. Express, home pickup and parcel locker, each with cost and duration on one line.
confirmation
"Order placed" shows the next step, with the locker address and a map pin.
follow-through
Until the clothes are dropped off, tracking marks the handover as pending.
Delivery options: Express, Home Pickup and Standard parcel-locker delivery Order Placed with a Next Step card showing the Instabox address Tracking with Place clothes in Instabox marked pending

16 · Customer web

Nobody installs an app to fix one shirt.

Brand partnerships send customers in from a retailer's link: open it, fill one form, get it fixed.

Web is a direct copy of the app's components, not a sibling design. Same tiles, steppers and damage taxonomy.
One build, two jobs. The same flow runs dry cleaning with an article picker, and scales from phone to desktop.
9:41AAtavare.no
Web repair: Add Articles and personal details Product details: category, company, competence and type Damage details: main damage then sub damage Upload image: gallery, camera or enter manually

17 · Repair capture

Design the failure state first.

A photo was the fastest way to describe damage, and the likeliest thing to fail. Each state says what's happening and what to do next.

The photo stays in view while it's scanned, and the button itself becomes the progress.
Failure is said plainly, in red, with two ways forward: enter details, or re-upload.
9:41AAtavare.no
Upload image: gallery, camera or enter manually Scanning for repairs over the uploaded photo Looks like we need your help: enter details or re-upload Damage details: pick main and sub damage
  1. IdentifiedDamage confirmed, on to checkout

18 · Retail dashboard

Retail staff are on their feet. So it's an iPad.

A store assistant in a denim shop holding up the Tavare iPad dashboard
Large targets, self-explanatory hierarchy, for staff managing stock and repairs between customers.
Company-covered payment is a state of the order, not a separate flow.
Dashboard: Repair, Alter and Dry Clean above active services Repair details sheet with line items, company-covered total and Mark Delivered

19 · Retail · create order

The most repeated task is one form.

Staff log a repair while the customer waits at the counter, so the form follows the order of that conversation, top to bottom.

  1. CustomerName, phone, email
  2. ProductCategory, brand, type, competence
  3. DamagesPhoto, main and sub damage, price
  4. TotalService charge incl. VAT, then proceed
One continuous form, not a wizard. Repeated all day, it only becomes muscle memory if its shape never changes.
New Repair: customer details and product details Damage details with photos, main and sub damage, and a running total

20 · Repair partner portal

Tailors sew. The queue does the remembering.

An elderly tailor at a sewing machine in a busy workshop
New orders: customer names, dates and prices In progress: On hold awaiting approval; Repair complete with quality check Archive: completed orders

21 · Partner portal · damage check

Less control, on purpose.

Tailors are craftspeople, not software users. The damage check is system-led: one thing at a time, with the answers offered.

Damage is chosen from options, not typed. The note only covers what the options can't.
The camera tells you what a good photo is: "the damage should be clearly visible".
Order detail with bill and Start Damage Check Camera with the hint: the damage should be clearly visible Damage details with the photo and a list of damage options

22 · System-level solutioning

The damage taxonomy is the spine of all four products.

If hundreds of independent tailors typed damage freely, we'd have hundreds of vocabularies. The customer's price, the retailer's invoice and the brand's warranty claim all read this one field.

Customer sees a priceSomeone with no trade vocabulary can describe a fault accurately, two levels deep.
Tailor gets a checklistPick from options first; the note only covers what the options can't. Same structure as the customer's bill.
Retailer gets an invoice lineBulk orders reconcile without anyone reinterpreting them.
Brand gets a warranty claimConsistent data, so repair can become part of the brand experience.
One component library → four products Built for Norwegian string lengths, not patched per screen iPad specified in portrait and landscape

23 · Impact & closure

Repair became the easier option.

Tavare launched as one platform for every repair need. Clothes get a longer life, there's a responsible route when repair isn't possible, and independent tailors get steady work without doing their own marketing.

4surfaces from one component library
1 tapto get in, through Vipps
5visible, timestamped order states
3ranked handover options
2languages on every screen
2levels in one shared damage taxonomy
If I did it again I'd argue for constraining the tailor's input earlier. It was the least popular decision in review, and it protected pricing, invoicing and warranty data end to end.
A tailor laying out a jacket pattern
An older tailor inspecting a garment
A man steaming a checked blazer

Every problem, closed

  1. No idea what options exist→One destination for warranty, paid repair and dry cleaning, with no self-diagnosis needed.
  2. Costs as much as new→A fixed price on every tile, plus a membership that makes the second repair cheap.
  3. No tailor nearby→Doorstep pickup, lockers or express. Distance stops mattering.
  4. Afraid of surprises→Itemised approvals with a real Skip, and a named state at every handoff.
  5. Tailors chasing customers→A steady, prioritised queue, with blockers printed on the card.
  6. Brands with no repair channel→In-store iPad intake, and company-covered payment built into the order.

Thanks for reading.Working on something this tangled? Let's talk.