The Paper Form That Fixed a Digital Product

The Paper Form That Fixed a Digital Product

How I tripled invoice issuance for small business owners at Paywork

How I tripled invoice issuance for small business owners at Paywork

Shipped

Web

B2C SaaS

Timeline

July 2023 - Sep 2023

July 2023 - Sep 2023

My Role

UX Research

User Interview

User Testing

Amplitude Analysis

UX Research

User Interview

User Testing

Amplitude Analysis

Team

1 Product Designer(Me)

1 Product Owner

3 Front-end Developers

2 Back-end Developers

1 Product Designer(Me)

1 Product Owner

3 Front-end Developers

2 Back-end Developers

Tool

Figma

Amplitude

Jira

Confluence

Figma

Amplitude

Jira

Confluence

Overview

Paywork is an invoicing and payment management service for small business owners who prioritize speed and efficiency in their daily operations. Users can handle the entire business transaction workflow in one place, from estimates to tax invoices to settlements, across both mobile and web.


In this project, I redesigned the entire tax invoice experience by restructuring the form layout and automating the data entry workflow to lower the barrier to Paywork's core paid feature and drive user activation.

Key Objectives

Paywork’s priority was increasing paid plan conversion. Tax invoicing was the core feature of the paid tier, yet in-product usage sat at just 13%. Low adoption of a paid feature meant users weren't experiencing the value that would justify paying.


Before we could move the conversion needle, we needed to remove the usability barriers around this feature so users could actually feel what the product was for.

Problem Statement

Problem Statement

Problem Statement

Tax invoicing is a required step after creating an estimate.

So why were users completing estimates in Paywork, then leaving to issue the invoice elsewhere?

Tax invoicing is a required step after creating an estimate. So why were users completing estimates in Paywork, then leaving to issue the invoice elsewhere?

Tax invoicing is a required step after creating an estimate. So why were users completing estimates in Paywork, then leaving to issue the invoice elsewhere?

Research

I conducted interviews with 30 small business owners who issued 50–60 tax invoices per month on average.

The core question: if users were already creating estimates in Paywork, why were they leaving to issue tax invoices elsewhere?

Key Findings

Users were blocked by two things: an unfamiliar form structure and repeated manual data entry.

Problem 01: The input form felt unfamiliar

"How am I supposed to fill this out?"

The input list format made it unclear

how to fill out the form.

Users familiar with paper forms found the input list format confusing.

"Where should I enter this information?"

The long scroll made it hard to understand

where each field belonged.

Paywork’s form stacked every field on one long page,

making a familiar tax invoice task feel unfamiliar and overwhelming.

Paywork’s form stacked every field on one long page, making it feel unfamiliar and overwhelming compared to the paper tax invoice format users already knew.

Problem 02: Users had to re-enter existing data

"I already have all this data."

Item and client details already existed in Excel,

but users had to enter them again from scratch.

Item and client details were already managed in Excel, yet had to be re-entered from scratch.

Item and client details were already managed in Excel, yet had to be re-entered from scratch.

"What if I make a mistake?"

Re-entering everything manually meant more chances for errors.

Users felt anxious about getting amounts or client details wrong.

Re-entering everything manually meant more chances for errors. Users felt anxious about getting amounts or client details wrong.

Re-entering everything manually meant more chances for errors.

Users felt anxious about getting amounts or client details wrong.

Moving from an estimate to a tax invoice required users to re-enter line items, amounts, and client details from scratch.

For new users, this took around 20 minutes on average.

Moving from an estimate to a tax invoice required users to re-enter line items, amounts, and client details from scratch, taking new users around 20 minutes on average.

Every time a user moved from an estimate to a tax invoice,

they had to re-enter all line items, amounts, and client details from scratch. Before getting used to it, this took around 20 minutes on average.

Design Solution

Solution 01: Mirror the paper tax invoice format

Redesigned form layout

I redesigned the form layout to follow the tax invoice format users were already familiar with.

In Korea, many small business owners handle tax invoices as part of their daily business operations, so the format was already familiar to Paywork’s core users.


By bringing that familiar structure into the product, users could start filling out the form without having to learn a new layout.

Before

All fields stacked on one scrolling page, nothing like the paper form they knew

All fields stacked on one scrolling page, nothing like the paper form they knew

After

The layout followed the familiar tax invoice format,

making each section easier to recognize.

The layout followed the familiar tax invoice format,

making each section easier to recognize.

Solution 02: Turn existing data into a one-click invoice

One-click conversion

Users who created an estimate in Paywork already had the necessary client, item, and amount information saved.

I designed a one-click conversion flow that turned an existing estimate into a tax invoice, eliminating the most repetitive step in the workflow.

Bulk upload

For users issuing tax invoices without an existing estimate, item and client details still had to be entered line by line.

Since many users already managed this information in spreadsheets, I designed a bulk upload flow that let them import multiple invoice items at once.

Before

Manually entering item details and amounts increased the risk of errors.

After

Uploading a spreadsheet populated item and client details at once, reducing manual entry and error risk.

Uploading a spreadsheet populated item and client details at once, reducing manual entry and error risk.

Impact

3x

increase in tax invoice issuance rate, from 13% to 42%.

2

enterprise partnerships with Hana Bank and KG Mobilians, a leading Korean payment processor.

Before, I had to manually enter all invoice details into a separate government tax system. Now, with automation and one-click conversion from estimates, it saves so much time and makes the process much easier to manage.

small business owner in their 50s

Takeaways

Standard doesn't mean optimal

Standard doesn't mean optimal

The highest-impact decision in this project wasn't a feature. It was copying a piece of paper. Users didn't need a better form. They needed a familiar one.


What's a standard layout for people in tech was a source of cognitive friction for independent business owners. The best interface isn't what we believe is right.

It's what users already know.

Research changes how you define the problem

Research changes how you define the problem

I went in assuming the issue was price. Interviews told me it was workflow fragmentation and an unfamiliar form. That redefinition changed every design decision that followed. This project showed me how much it matters to find the real problem through research rather than assumption.

I went in assuming the issue was price. Interviews told me it was workflow fragmentation and an unfamiliar form. That redefinition changed every design decision that followed. This project showed me how much it matters to find the real problem through research rather than assumption.

THANK YOU
FOR VIEWING

THANK YOU
FOR VIEWING

THANK YOU
FOR VIEWING